Launchpad itself

PPA dependency fails for mine

Asked by A117

My PPA depends on another PPA to build, so I site "~dolik-rce/ubuntu/upp" in PPA dependency settings. I checked my code and found no "theide" anywhere.
But building complains as below,
** Using build dependencies supplied by package:
Build-Depends: debhelper (>= 8.0.0), theide (>= 5485)
Checking for already installed source dependencies...
debhelper: missing
theide: missing
theide: does not exist
Checking for source dependency conflicts...
  /usr/bin/sudo /usr/bin/apt-get --purge $CHROOT_OPTIONS -q -y install debhelper theide
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package theide
apt-get failed.
Package installation failed

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

You haven't stated exactly which build(s) you're talking about, but I assume you mean your most recent: the two builds from August 2013 on https://launchpad.net/~bon-ami/+archive/ubuntu/ezcomm/+builds?build_state=all.

Both of those builds failed more than 18 months ago, because your debian/control file specifies "theide" in its Build-Depends field, but that package doesn't exist in Ubuntu. Both builds are also for Ubuntu 13.04 (raring), which reached its end of life in 2013, so you'll need to increase the package version and upload them to a supported Ubuntu series before you can attempt to build them again.

Revision history for this message
A117 (bon-ami) said : 		#2

how did you know debian/control consisted theide? the current code does not.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

If you check https://launchpad.net/~dolik-rce/+archive/ubuntu/upp you should see that this PPA provides theide for all Ubuntu releases except for raring!
Try building you ezcomm package for a supported Ubuntu release.

Revision history for this message
A117 (bon-ami) said : 		#4

thanks. I created a recipe to build my current code without dependency on theide https://code.launchpad.net/~bon-ami/+recipe/ezcomm-daily
while umk (declared as depended in PPA, https://code.launchpad.net/~dolik-rce/+archive/ubuntu/upp) was still reported as not to be found. I need it to build the code.

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

When you configure your PPA to depend on another PPA, that just makes the other PPA's packages available as build dependencies. But your package still has to specify which packages it wants to install as build dependencies, in the Build-Depends field in http://bazaar.launchpad.net/~bon-ami/ezcomm/main/view/head:/debian/control.

Have you read through http://packaging.ubuntu.com/html/?

Revision history for this message
A117 (bon-ami) said : 		#6

yes I have gone over the manual and so on many times.

I changed it to
Build-Depends: debhelper (>= 8.0.0),upp (>=8227-1)
but this time it complains upp(>=8227-1) is not found.

then I changed it to
Build-Depends: debhelper (>= 8.0.0),upp ,ezcommon-dev (>=4.6.7)
and it complainsezcommon-dev (>= 4.6.7) not found.

at last I removed (>=4.6.7) and it passed that phase. So how to specify depended package versions, just as debhelper? the versions are the ones I got from dpkg -s.

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

From the most recent build log: "Setting up ezcommon-dev (4.6.7-0~23~precise1) ...". By Debian versioning rules, 4.6.7-0~23~precise1 is older than 4.6.7 ("~" is less than anything, even the empty string). Version interpretation is defined at https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version. If you really need the strict version relation, try "(>= 4.6.7-0~)".

Are you testing the builds locally before you try them on Launchpad? You should be using pbuilder or sbuild to get a quicker testing cycle that doesn't waste shared Launchpad build resources. See https://wiki.ubuntu.com/SimpleSbuild for a guide to getting sbuild up and running, for testing package builds in a clean environment.

Revision history for this message
A117 (bon-ami) said : 		#8

Thanks William Grant, that solved my question.

Revision history for this message
A117 (bon-ami) said : 		#9

I successfully built locally (bzr builddeb -S, pbuilder-dist, etc.) so I wondered why the servers could not. Sorry but I do not intend to test on the servers.