Binary domination removes arch-all binaries too soon

Bug #55030 reported by Malcolm Cleaton
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Medium
Unassigned

Bug Description

From the XXX in domination.py, _judgeSuperseded:

        # XXX: dsilvers: 20050922: Need to make binaries go in groups
        # but for now this'll do. An example of the concrete problem here
        # is:
        # - Upload foo-1.0, which builds foo and foo-common (arch all).
        # - Upload foo-1.1, ditto.
        # - foo-common-1.1 is built (along with the i386 binary for foo)
        # - foo-common-1.0 is superseded
        # Foo is now uninstallable on any architectures which don't yet
        # have a build of foo-1.1, as the foo-common for foo-1.0 is gone.

This causes packages to be uninstallable for a period of time, which is bad.

Changed in soyuz:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Curtis Hovey (sinzui)
tags: added: tech-debt
Revision history for this message
Robert Collins (lifeless) wrote :

This is a dupe of a newer, escalted bug whose number escapes me. Sorry for the lack of memory, but if you are interested you can search for it :)

Changed in launchpad:
status: Triaged → Invalid
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.