Ubuntu – How to upload package with dependencies to the PPA

compilingdependenciesppa

I made a package for my PPA and uploaded it. It built without any problems.

Then I made another package that depended on the first and uploaded it. It failed because it couldn't find the files in the first package. This leads me to believe that the first package wasn't even installed.

How can I make sure the first package is installed before it tries to build the second package?

The control file for the first package (libjsoncpp):

Source: jsoncpp
Priority: extra
Maintainer: Nathan Osman 
Build-Depends: debhelper (>= 7)
Standards-Version: 3.8.3
Section: libs
Homepage: http://jsoncpp.sf.net

Package: jsoncpp-dev
Section: libdevel
Architecture: any
Depends: libjsoncpp (= ${binary:Version})
Description: JSON parsing library for C++
 jsoncpp is a C++ library that makes it easy to
 read / write JSON data.
 .
 This package contains the development tools necessary
 to create applications that use jsoncpp.

Package: libjsoncpp
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: JSON parsing library for C++
 jsoncpp is a C++ library that makes it easy to
 read / write JSON data.

The control file for the second (libsopp):

Source: sopp
Priority: extra
Maintainer: Nathan Osman 
Build-Depends: debhelper (>= 7)
Standards-Version: 3.8.3
Section: libs
Homepage: http://stackoverflow.quickmediasolutions.com

Package: sopp-dev
Section: libdevel
Architecture: any
Depends: libsopp (= ${binary:Version}), jsoncpp-dev
Description: A C++ library for interfacing with StackExchange sites.
 so++ is a C++ library that wraps the functionality of the StackOverflow
 API. It provides access to all of the StackExchange sites.
 .
 This package contains the development files necessary to write software
 that uses so++.

Package: libsopp
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, libjsoncpp
Description: A C++ library for interfacing with StackExchange sites.
 so++ is a C++ library that wraps the functionality of the StackOverflow
 API. It provides access to all of the StackExchange sites.

Best Answer

Your second package (sopp) needs to specify that it needs the first to build; the dependency you have specified (with Depends:) will only handle installation.

To add a build dependency, add this to the top (Source:) section of your control file:

Build-Depends: jsoncpp-dev

You should then be able to drop jsoncpp from the Depends line, as the shlibs:Depends macro should work that out itself.

Related Solutions

Ubuntu – How to build source package with `pbuilder` for PPA upload

The answer is that you don't. pbuilder takes the source package and builds binaries. It also can take the source code without a source package built and create the binaries that you would either host yourself or add to your own debian repository systems to host on your own.

That's not what you need for a PPA.

What you want to do, and what I strongly recommend, is that you follow traditional packaging procedures, and run debuild -S on the code, with the directory for the package there, containing the source code, the debian/ folder, and everything else.

Then, after you've built the source package by debuild -S, you can then upload the created .changes file in one directory above the source directory to the PPA via dput. (this step is referred to on Launchpad's PPA Uploading help docs).

You can in theory use pdebuilder to keep your system clean and build inside a chroot, but read on for my statements on this, as to why it failed previously for you.

Per the comments, you have correctly identified that debhelper is unable to find the autoreconf plugin.

Also as I said in my comments on this answer, pbuilder and pdebuilder are both not smart enough to determine the debhelper dependencies.

To solve your issue so that your stuff can build, you will have to manually use pbuilder or pdebuilder to login to the chroot. Then, you will have to manually install dh-autoreconf into the chroot, usually with apt-get install dh-autoreconf after you've logged into the chroot.

Once you've done that, and saved the state of the chroot, you should be able to pbuilder or pdebuilder your package.

_{(However, I prefer traditionally working with packages, and I don't care if my build system is entirely clean or not, all I really build are source packages, and the debhelper plugins aren't going to clutter my system that badly)}

Ubuntu – PPA package: Specify different dependencies for different Ubuntu versions

In the case libtool/libtool-bin, I think an OR relation might work:

Build-Depends: libtool-bin (>= 2.4.2-1.10) | libtool (<< 2.4.2-1.10)

The version numbers are that of utopic, when the split was imported from Debian. Note that in 2.4.2-1.10, libtool still depends on libtool-bin. The dependency was reversed in 2.4.2-1.11, which is why this change is now needed.

Depending on what you do, it might be simpler and safer to add a combined libtool to a separate PPA and depend on it. Since this is a B-D, it needn't be installed by your end-users, so depending on a separate PPA should be safe.

Best Answer

Related Solutions

Ubuntu – How to build source package with `pbuilder` for PPA upload

Ubuntu – PPA package: Specify different dependencies for different Ubuntu versions

Related Question