DistributionSourcePackageRelease page OOPS
Bug #536641 reported by
Julian Edwards
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Michael Nelson |
Bug Description
OOPS-1529EA4 NotOneError: one() used with more than one result available
https:/
It looks like maybe the cache got corrupted somehow?
tags: | added: oops |
Changed in soyuz: | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
Changed in soyuz: | |
assignee: | nobody → Michael Nelson (michael.nelson) |
status: | Triaged → In Progress |
Changed in soyuz: | |
milestone: | none → 10.04 |
status: | In Progress → Fix Released |
To post a comment you must log in.
Looking at https:/ /edge.launchpad .net/ubuntu/ lucid/+ source/ sun-java6 you can see there are actually 2 6.18-2 releases listed, which indicates that there are two releases with the save version in two separate distro archives.
Running a query on staging shows this is the case: pastebin. ubuntu. com/392585/ -+----- ----+-- -------
16:05 < noodles> Can you run this for me (on staging):
16:05 < noodles> http://
17:20 < bigjools> noodles: haha
17:20 < bigjools> id | version | name
17:20 < bigjools> -------
17:20 < bigjools> 549031 | 6-16-1 | primary
17:20 < bigjools> 468586 | 6-15-1 | primary
17:20 < bigjools> 618325 | 6.18-2 | primary
17:20 < bigjools> 620648 | 6.18-2 | partner
17:20 < bigjools> (4 rows)
So we might want to think about not allowing the same version to exist in the same series of two separate *distro archives* (MAIN_ARCHIVE_ PURPOSES, which also includes debug). It seems to break the url traversal and confuses apt locally (given that most people will have main and partner enabled). Are there other options?