Launchpad itself

A Rebuild of a Previously Failed Build still Failed while Telling a Depends on a Deleted Package

Asked by Pascal Mons

In my Launchpad PPA https://launchpad.net/~anton+/+archive/ubuntu/photo-video-apps
I am trying to build the packages from stock Precise source python-docutils.

Previously I tried tried to build from Trusty sources for Precise but understood later that it meant upgrading all the Python 2.7 packages and I deleted the failed builds from my PPA. I waited for 10 days for these to be effectively removed by Launchpad.

However, trying to build again from stock Precise source python-docutils still fails and give me a dependency on the deleted sources (mentioned above). Instead of looking for (stock Precise) dependencies mentioned in the debian/control file ... i.e.

The following packages have unmet dependencies:
 python-all : Depends: python (= 2.7.5-5pmo3~precise) but it is not going to be installed

The mentioned (=2.7.5-5pmo3~precise) was part of the deleted source ... Why is it still used now ?
Why Launchpad isn't using regular official packages ?
Is the deleted / failed build there forever ? (tough it has been deleted)

In the debian/control file I have for the current build :

Build-Depends-Indep: python-all (>= 2.6.6-3~),

which is a stock Precise dependency.

As well, when trying to rebuild a stock Precise source python-defaults I get the following error message :

The following packages have unmet dependencies:
 lsb-release : Depends: python (>= 2.7.1-0ubuntu2) but it is not going to be installed
               Depends: python (< 2.8) but it is not going to be installed
 python-docutils : Depends: python (>= 2.7.1-0ubuntu2) but it is not going to be installed
                   Depends: python (< 2.8) but it is not going to be installed
                   Depends: python-roman but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
Package installation failed
Trying to reinstall removed packages:
Trying to uninstall newly installed packages:
Source-dependencies not satisfied; skipping python-defaults

Again it looks like the old (deleted) sources failed builds are still there ...

Do you have any insight ?
Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
William Grant
Solved:
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said : 		#1

python-all comes from python-defaults, not python2.7. python-defaults 2.7.3-0ubuntu2.2.1~precise is still published for precise in that PPA.

Revision history for this message
Best William Grant (wgrant) said : 		#2

Oops, didn't read far enough into your question. The problem is what I said, just with a slightly different version and some obscure Launchpad behaviour:

You uploaded python-defaults 2.7.5-5pmo3~precise, which built the binaries with unsatisfiable dependencies. You then uploaded 2.7.5-5pmo4~precise, which failed to build due to the unsatisfiable dependencies. pmo4 superseded the pmo3 source, but not pmo3's binaries, since pmo4 never built any binaries to replace pmo3's. You then deleted pmo4, but that wouldn't have touched pmo3's binaries either.

You can fix the problem by heading over to +delete-packages, switching the "Published" status filter to "Any status" and searching for python-defaults, then deleting the superseded 2.7.5-5pmo3~precise. Packages will be buildable again within about 20 minutes.

Revision history for this message
Pascal Mons (anton+) said : 		#3

Thank you for your answer.

Revision history for this message
Pascal Mons (anton+) said : 		#4

Thanks William Grant, that solved my question.