PPA should not unpublish packages while they are referenced (within the PPA) - old sources where a single arch has failed, lock-step depends on sibling packages
Bug #215661 reported by
Jelmer Vernooij
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
it would be nice if launchpad allowed multiple versions of a package to be present in PPA. This can be useful if another package in the PPA has dependencies on an older version of a package, not necessarily the most recent one.
Changed in soyuz: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: ppa |
Changed in soyuz: | |
importance: | Low → Wishlist |
summary: |
- PPA should allow multiple versions of a package to be present + PPA should not unpublish packages while they are referenced (within the + PPA) - old sources where a single arch has failed, lock-step depends on + sibling packages |
Changed in launchpad: | |
importance: | Wishlist → Low |
To post a comment you must log in.
I've another use case for this. I need to maintain multiple upstream versions of a set of debs for a soss distribution PPA (https:/ /launchpad. net/soss). Since LP soss PPAs have a 1:1 mapping to Artifactory repos, this means that every new supported upstream version of a package needs its own soss PPA, a new Ubuntu PPA for building the package, a local Artifactory repo and virtual Artifactory repo. This is a lot of overhead, and non-deb soss PPAs do not have this problem.
Even if I still end up with multiple Ubuntu PPAs to build different upstream versions, being able to copy bits from those multiple build PPAs into a single soss PPA that publishes to a single set of Artifactory repos would be a very nice improvement.