lucid support timeframe information not updated for NEW packages in lucid-updates

Bug #660433 reported by Michael Vogt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Gavin Panella

Bug Description

For packages in lucid-updates that are NEW (like the kernel updates) there is currently no support timeframe information generated. E.g.

Package: linux-image-386
Depends: linux-image-2.6.32-25-386, linux-firmware
...
Supported: 5y

But

Package: linux-image-2.6.32-25-386

has no "Supported" field.

I attached a patch with the simplest possible approach (that I can think of) that just re-runs germinate for all supported
suites. The patch obviously needs formating changes, but I wanted to keep it minimal for now. Its not really necessary
to run the full germinate again, just the maintenance-check part (which is quicker to finish than the full script). I will work on a patch for this alternative approach next. Its a bit more complicated because it requires merging the updated maintenance info with the existing (and static) more-extras.override files.

Tags: lp-soyuz qa-ok

Related branches

Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Michael,

Can you make a branch with a merge proposal, and I'll run it on dogfood for you so you can test it!

Cheers.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks Julian,

I added a mock-environment and a test and send a merge request:
https://code.edge.launchpad.net/~mvo/launchpad/support-timeframe-fix-660433/+merge/38503

The branch tests that maintenance-check produces the expected output and prepares testing germinate
as well. However its not testing that yet. The test is shell based, I'm happy to rewrite it as a python unittest
if that is needed (and if the general direction is correct).

Changed in soyuz:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Michael Vogt (mvo) wrote :

Just FYI, the tests have been rewriten in python with unittest and all binary data in the mock environment is created on the fly now.

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
assignee: nobody → Gavin Panella (allenap)
milestone: none → 11.02
tags: added: qa-needstesting
Changed in launchpad:
status: Triaged → Fix Committed
Revision history for this message
Robert Collins (lifeless) wrote :

We're marking this qa-untestable for now as its not part of the nodowntime set; Julian will coordinate QA with Michael before the db-deployment which is when we will next deploy to the publisher machine.

tags: added: qa-untestable
removed: qa-needstesting
Revision history for this message
Robert Collins (lifeless) wrote :

Filed bug 707630 as a memo for Julian.

Revision history for this message
Gavin Panella (allenap) wrote :

Gah, should I have landed in db-devel instead?

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 660433] Re: lucid support timeframe information not updated for NEW packages in lucid-updates

On Wed, Jan 26, 2011 at 10:50 PM, Gavin Panella
<email address hidden> wrote:
> Gah, should I have landed in db-devel instead?

No? no schema change, no problem. The issue is that this requires qa
of the interaction with the publisher, which per julians mail to the
list, isn't easy yet.

-rob

Revision history for this message
Julian Edwards (julian-edwards) wrote :

This tested fine on dogfood, it's good for the rollout.

tags: added: qa-ok
removed: qa-untestable
Curtis Hovey (sinzui)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.