[01:50] <karstensrage> i recall i resource i was following to test ppa's on sbuild chroots
[01:51] <karstensrage> i have an library which depends on another library both are ppa's
[01:51] <karstensrage> so how to get the chroot to know about the first one
[01:51] <karstensrage> cant find the resource anymore
[08:02] <mapreri> cjwatson: btw, is this main/debug suite documented somewhere?  I couldn't find it in https://help.launchpad.net/Packaging/PPA/*
[08:23] <cjwatson> karstensrage: Easiest way is to use a recent version of sbuild that has the --extra-repository and --extra-repository-key options.
[08:24] <cjwatson> mapreri: Possibly not.  I'm not quite sure where to put it; none of the existing pages there seem to be a very good fit.
[08:25] <mapreri> cjwatson: imho https://help.launchpad.net/Packaging/PPA/InstallingSoftware is the best place within /Packaging/PPA/
[08:25] <mapreri> but yeah, probably not great and that page is already quite long.
[08:35] <cjwatson> I don't want to risk confusing novice users further, really
[15:00] <karstensrage> cjwatson, Version: 1.0-1
[15:00] <cjwatson> karstensrage: That is not a credible version of sbuild
[15:00] <karstensrage> oh sorry
[15:01] <karstensrage> sbuild --version
[15:01] <karstensrage> sbuild (Debian sbuild) 0.62.6 (07 Dec 2011)
[15:01] <cjwatson> karstensrage: mm, it's much easier with 0.66.0 or newer.  If you can't upgrade to that then it's easiest to just edit /etc/apt/sources.list temporarily
[15:04] <karstensrage> cjwatson, am i correct in my interpretation that what your suggesting requires the ppa of the dependent library to already exist in launchpad?
[15:06] <cjwatson> karstensrage: I don't think so, but perhaps you could clarify your terms
[15:06] <cjwatson> maybe some concrete examples would help
[15:06] <karstensrage> sure
[15:06] <cjwatson> you said "both are PPAs" so I'm not sure why this is an issue
[15:06] <karstensrage> well i meant both WILL be PPA's
[15:06] <karstensrage> they are not yet
[15:07] <karstensrage> i mean they are, but there are updates
[15:07] <cjwatson> so, apt in the chroot needs to be able to resolve the build-dependencies of whatever you're building
[15:07] <karstensrage> yeah
[15:08] <cjwatson> you can achieve that by pointing it at a PPA containing those build-dependencies if they aren't in the primary archive, or just by building a temporary local archive and pointing it at that
[15:08] <karstensrage> with .66?
[15:08] <cjwatson> modern sbuild has --extra-package which makes this much less hassle, but you don't have that
[15:08] <cjwatson> with an older sbuild you can just edit /etc/apt/sources.list to point it wherever
[15:09] <karstensrage> but i have to modify that /etc/apt/sources.list in the chroot right?
[15:09] <cjwatson> given chroots it's probably easiest to have it on the network; PPAs will fulfil that for you and deal with the mechanics of building a repository, but it's perfectly possible to run apt-ftparchive over a local directory and slap that on a local web server
[15:10] <cjwatson> with your version of sbuild you'd either have to modify /etc/apt/sources.list in the chroot or just preinstall the relevant build-depended-on library packages in the chroot, yes
[15:10] <cjwatson> taking care to clean things up afterwards
[15:11] <karstensrage> can i update my sbuild?
[15:11] <cjwatson> all things are possible
[15:11] <cjwatson> I don't know how fiddly installing xenial's version of sbuild on precise is going to be
[15:12] <cjwatson> it doesn't sound like something I would want to do for fun
[15:12] <cjwatson> there are some complicated interactions with libdpkg-perl
[15:13] <cjwatson> you could try the backport in https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging/+packages, which has --extra-package and --extra-repository but not --extra-repository-key
[15:14] <cjwatson> so you could use that and not try to install from a PPA; instead, use --extra-package a few times to point to all the depended-on library .debs you've built locally
[15:15] <cjwatson> but disclaimer, I've only used that package in the context of Launchpad builders
[15:21] <karstensrage> hmmm
[15:21] <karstensrage> ok
[15:22] <karstensrage> oh hmm
[15:22] <karstensrage> my next question seems perfect for you
[15:23] <karstensrage> how do you handle the idea that nothing changes really in the changelog but the naming.. and since its linear only the last change actually is taken as the name
[15:24] <karstensrage> so for example... https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging/+sourcepub/6082554/+listing-archive-extra
[15:24] <karstensrage> the name is either sbuild - 0.65.2-1ubuntu2~ubuntu12.04.1~ppa8  or sbuild - 0.65.2-1ubuntu2~ubuntu14.04.1~ppa8
[15:28] <karstensrage> so its the same entry with different name and the time is 1 minute later
[15:32] <cjwatson> karstensrage: the name is just "sbuild"; the other bit is the version
[15:33] <cjwatson> karstensrage: and I normally just edit it directly with dch, it's not especially hard to do so, but you can automate that locally if you like
[15:40] <karstensrage> yeah i wrote a python script to template that out with jinja2
[15:40] <karstensrage> hm ok
[15:41] <cjwatson> templating seems rather too likely to end up dropping old entries
[15:41] <cjwatson> but depends how you do it I'm sure
[15:43] <karstensrage> i just template the last entry
[15:48] <karstensrage> this is the ppa i would add to my precise packaging machine to get all your newer stuff  ppa:launchpad/ppa  ?
[15:49] <karstensrage> cjwatson?
[15:51] <cjwatson> karstensrage: the one I pointed you at earlier was ppa:launchpad/buildd-staging, not ppa:launchpad/ppa
[15:51] <cjwatson> ppa:launchpad/ppa has a whole pile of random other stuff you probably don't want
[15:54] <karstensrage> oh ok, i was a little confused cause that page doesnt have the technical details about this ppa with the  stuff for adding
[15:54] <karstensrage> sorry
[15:56] <cjwatson> right, drop /+packages from the URL for that
[16:01] <karstensrage> woo
[16:01] <karstensrage> sbuild --version
[16:01] <karstensrage> sbuild (Debian sbuild) 0.65.2 (24 Mar 2015)
[16:02] <karstensrage> thanks cjwatson
[16:20] <cjwatson> np
[17:50] <karstensrage> hmm i use the --extra-package=mylib.deb and it doesnt seem to find it or use it
[17:51] <karstensrage> there is no reference to it in the build
[17:51] <karstensrage> other than having it on the command line
[17:52] <nacc> karstensrage: does it make any difference if you provide the full path?
[17:53] <karstensrage> ill try that
[17:53] <nacc> karstensrage: i've used --extra-package in some of my scripting, but i've always passed in full-paths it seems :)
[17:53] <nacc> karstensrage: was 'mylib.deb' was in . ?
[17:53] <nacc> err, without one of those was's :)
[17:53] <karstensrage> yes
[17:54] <karstensrage> it was in .
[17:56] <cjwatson> I believe relative paths should work, but you do still have to build-depend on something that causes it to be installed
[17:56] <cjwatson> --extra-package makes it available for resolution; it doesn't forcibly install it
[17:56] <nacc> cjwatson: ah yes, good point :)
[17:58] <karstensrage> well build-depends lists it
[17:58] <karstensrage> this all in debian-testing
[17:58] <karstensrage> its been ported to xenial
[17:59] <karstensrage> im working on testing things for backports to precise and trusty
[17:59] <karstensrage> it works flawlessly but they wont take my word for it
[18:00] <karstensrage> hmm still doesnt work
[18:01] <karstensrage> the .deb im using has the right thing in it, but how does it resolve the right thing?
[18:04] <nacc> karstensrage: iirc, --extra-package just creates a side repository with whatever you specified in it
[18:05] <nacc> karstensrage: you could pass -pnever and debug what is going on in it?
[18:10] <karstensrage> not sure what -pnever is
[18:11] <karstensrage> im doing -D to see if anything shows
[18:21] <karstensrage> nope
[18:21] <karstensrage> seems like it doesnt pass in the extra-package
[18:26] <dobey> is it the newest version available versus what is in other archives being used?
[18:28] <karstensrage> i updated to .66
[18:29] <karstensrage> sorry .65.2
[18:29] <karstensrage> with cjwatson's help
[18:33] <nacc> karstensrage: -p is the purge mode
[18:33] <nacc> karstensrage: if you tell it never, it'll leave your sbuild env around, so you can schroot over to it and see what it sees
[18:34] <karstensrage> qh
[18:34] <karstensrage> ah
[18:34] <nacc> karstensrage: i think dobey meant, though, for the package in question, is your version > the version in the archives?
[18:37] <karstensrage> the version in the archives?
[18:37] <karstensrage> sorry
[18:37] <dobey> well what isn't working exactly?
[18:38] <dobey> you haven't described what isn't working, only complained that it isn't
[18:38] <karstensrage> i am trying to sbuild my library on precise
[18:38] <karstensrage> my library is dependent on another library that builds on precise fine
[18:38] <cjwatson> I think nobody is going to be able to help you meaningfully unless you post your source package and the build log somewhere
[18:38] <karstensrage> but the chroot doesnt have that 2nd library
[18:39] <dobey> and the full sbuild command
[18:39] <cjwatson> without all that information that you have, anyone else is going to be wasting their time making guesses and playing infinity-questions
[18:39] <cjwatson> indeed, that too
[18:39] <dobey> so it's failing to satisfy the depends during the build?
[18:42] <karstensrage> yes
[18:47] <dobey> please pastebin the log and the sbuild command you used to run sbuild with then
[18:52] <karstensrage> ok
[19:09] <karstensrage> i get a build.gz and a build.summary
[19:09] <karstensrage> which would you like
[19:13] <karstensrage> http://pastebin.com/XfP3BTNn
[19:13] <karstensrage> there is the command at the top and the paste of
[19:13] <karstensrage> libpam-ufpidentity_1.0-1_i386-20160516-1142.build
[19:18] <dobey> karstensrage: as i suspected. you can't pass only the -dev package. you'd need to pass the libufpdidentity1 or whatever .deb also with --extra-deb. any additional packages which are required to satisfy the depends must *all* be passed with --extra-deb args
[19:18] <dobey> of course the -dev can't be installed when the binary package it depends on isn't available
[19:21] <karstensrage> --extra-package?
[19:22] <dobey> yes
[19:22] <karstensrage> trying again with three --extra-package
[19:27] <karstensrage> its slowed down since this morning
[19:27] <karstensrage> takes quite a while
[19:27]  * karstensrage will have another cappuccino
[19:36] <karstensrage> woot
[19:37] <karstensrage> success
[19:37] <karstensrage> thank you so much dobey, and nacc and cjwatson
[19:37] <karstensrage> thats cool
[19:38] <karstensrage> so i had no idea thats how the .deb's worked...i figured if the file needed was in the particular .deb, that would be all that was needed. sorry for the confusion