Launchpad itself

Searching for component bugs on Ubuntu after the Jaunty series was added returns 0 bugs

Bug #291344 reported by Eleanor Berger
8
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Eleanor Berger

Bug Description

After the introduction of the Jaunty distro series on ~ 2008-10-30 1435 UTC, advanced bug searches for bugs on packages in components stopped returning any bugs.

It appears that the reason for this is that the new distro series, which is frozen, is now considered the current series and that there are no SourcePackagePublishingHistory records for this series.

Tags: lp-bugs
Revision history for this message
Eleanor Berger (intellectronica) wrote :

Marking as HIGH and assigning to myself, though this is probably not a malone bug (and more of a data problem anyway).

This is stopping people from searching for ubuntu bugs and the qa team from running a script.

Changed in malone:
assignee: nobody → intellectronica
importance: Undecided → High
status: New → Triaged
Revision history for this message
Eleanor Berger (intellectronica) wrote :

This seems to be working OK now. I don't know what changed since yesterday. Perhaps the relevant data was introduced.

Changed in malone:
status: Triaged → Invalid
Revision history for this message
Eleanor Berger (intellectronica) wrote :

The root cause for this was bug #55288

Revision history for this message
Celso Providelo (cprov) wrote :

Tom,

First, it's working now because jaunty was initialized. In this sense, I think the bug is still relevant (not invalid), since the rest of the system should not panic if a 'experimental' empty distroseries gets created.

For the record, bug #55288 wasn't exactly the cause of this issue, but instead another symptom of the problem.

Revision history for this message
Colin Watson (cjwatson) wrote :

Yes, I've been initialising Jaunty this morning. (Yesterday, I was waiting for confirmation that this was OK.)

Revision history for this message
Eleanor Berger (intellectronica) wrote :

After discussion with ~cprov, we have decided to re-open this bug and make it a duplicate of the relevant Soyuz fix.

If we fix Distribution.currentseries to be explicit, a problem like this will not happen again.

Changed in malone:
status: Invalid → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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