[15:17] <segf4ult> hey guys, I'm trying to build a package on one of the build-servers delegated by launchpad, however I'm running into some trouble getting it to build. Is this the right place to ask?
[15:22] <segf4ult> ls
[19:53] <cjwatson> segf4ult: Yes, it's (probably) the right place, but it's usually best to just ask your question directly to save multiple multi-hour round trips.
[20:27] <segf4ult> Okay, I'm trying to package the latest stable for a library called ZeroMQ, which depends upon libSodium, which I've packaged and put into my ppa
[20:28] <segf4ult> it seems that libsodium-dev cannot be installed when I try to build my ZeroMQ library package.
[20:28] <segf4ult> even though it's a build-dependency
[20:38] <segf4ult> I've set up sbuild to get a clear picture of what is going on with the chroots on the launchpad servers, seems they're not importing the GPG key for my PPA
[20:47] <segf4ult> they don't have pkg-config installed either.. how am I supposed to build a package for my PPA if a dependency cannot be picked up properly from the same PPA?
[21:08] <cjwatson> I think I know what the GPG thing you're talking about is, and it is a red herring that you should ignore.
[21:08] <cjwatson> chroots won't have pkg-config installed; you need to build-depend on it.
[21:09] <cjwatson> If libsodium-dev "cannot be installed", that means it's uninstallable in your PPA due to a dependency error of some kind which you'll need to investigate.
[21:09] <cjwatson> I have to go now, but what you should normally do if you can't figure it out is to link to the failed build and somebody can look into it from there.
[21:10] <cjwatson> You also probably shouldn't package libsodium from scratch, just backport it from a newer Ubuntu release.  "backportpackage" can help.  That can save you from some mistakes.