Keep both sources and binaries for existing packages on Launchpad until the newer version has been successfully built on all specified platforms
Bug #606075 reported by
Ryan Oram
This bug report is a duplicate of:
Bug #39630: Older packages are removed when newer versions FTBFS.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
New
|
Undecided
|
Unassigned |
Bug Description
Currently only the latest source packages and binaries are listed on Launchpad. This leads to a problem where the existing successfully built package can not be accessed via the Launchpad interface, even if the build of the newer build has failed. Indeed, in this scenario, it is the older package that is installed when the PPA is added and the package is installed via apt.
This also poses a problem where the package will fail to copy to another PPA if the newer package has failed to build. (Bug 604469)
The best solution to this problem is to keep both the older sources and binaries on Launchpad until the newer package has successfully built.
To post a comment you must log in.
A good example of this problem is the "vala" package on vala-team/ppa.
http:// ppa.launchpad. net/vala- team/ppa/ ubuntu/ pool/main/ v/vala/
The sources for vala_0. 9.1-1~llvala1 AND vala_0. 9.2-2~llvala1 are available in the apt repo. However, only the binaries for vala_0.9.1-1~llvala are available.
https:/ /launchpad. net/~vala- team/+archive/ ppa
However, on Launchpad, only vala_0. 9.2-2~llvala1 is listed, indicating a failed build. This is misleading as both the sources and the binaries for vala_0. 9.1-1~llvala1 are available via apt, and it is vala_0. 9.1-1~llvala1 that will installed when the vala package is installed using apt-get.