Builds for archives with purpose COPY shown on distro build listings

Bug #377534 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

Builds in an archive with ArchivePurpose COPY are shown in official distribution build listings, just like a PRIMARY or PARTNER build. They should not be, or should at least be shown very differently.

Tags: lp-soyuz
Revision history for this message
Celso Providelo (cprov) wrote :

Willian, can you provide example URLs ?

Changed in soyuz:
status: New → Incomplete
Revision history for this message
Michael Bienia (geser) wrote :

https://edge.launchpad.net/ubuntu/karmic/+source/ulex/+builds as an example.

The first item shows as "i386 build of ulex 1.1-1 in ubuntu karmic RELEASE" but it links to https://edge.launchpad.net/ubuntu/+archive/test-rebuild-20090513/+build/1023745
The correct entry for karmic is further down in that page but also titled "i386 build of ulex 1.1-1 in ubuntu karmic RELEASE".

Another example: https://edge.launchpad.net/ubuntu/karmic/+source/ledit/+builds
BTW: the pending build for the disabled archive "test-rebuild-20090406" are still listed in the +builds page as can be seen in the above link. I already wondered in the past why we still have pending builds for jaunty (it's not jaunty but the rebuild archive for jaunty).

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

Thanks, Michael. The SourcePackage:+builds context is considering builds in COPY archives and needs fixing.

Changed in soyuz:
assignee: nobody → Celso Providelo (cprov)
importance: Undecided → High
milestone: none → 2.2.5
status: Incomplete → Triaged
Celso Providelo (cprov)
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

r8101 (db-devel)

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
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.