[11:38] <shiftplusone> rbasak: tried a gpioexpander build with avahi. Not sure why, but it's not working. Won't go further here, since it's off topic here, but if you have ideas, there's always #raspberrypi.
[14:22] <shiftplusone> Are there any tools which take a source package and spit out a set of packages with an added changelog entry for each ubuntu release to upload to PPA. The documentation seems to suggest that with each update of the package you'd need to do that by hand or write your own script. Seems like there should be something that already does that.
[14:24] <cjwatson> Well I mean you don't write the packaging by hand for each release, you carry it over from the previous version
[14:24] <cjwatson> And use dch to help with the changelog
[14:24] <shiftplusone> right, but let's say I have a debian package and I want to upload it to launchpad and have it built for multiple ubuntu releases.
[14:25] <cjwatson> You might use recipes
[14:25] <cjwatson> https://help.launchpad.net/Packaging/SourceBuilds
[14:25] <shiftplusone> it looks like launchpad wants a different version number for each release... then I'd need to add a different changelog entry for each release and then keep a separate version of the changelog for each.
[14:25] <cjwatson> Alternatively, you usually don't actually have to build separately for each Ubuntu release - you can upload to the oldest of them and then copy forward once it's built
[14:26] <shiftplusone> Isn't that generally not recommended due to potential API changes in libraries?
[14:26] <cjwatson> It depends
[14:26] <cjwatson> You only need to rebuild if there's been a backward-incompatible change, usually indicated by a change in the library's SONAME or similar
[14:27] <cjwatson> But for lots of things it's unnecessary
[14:27] <cjwatson> I mean, lots of Ubuntu itself is just carried over from the previous release - we don't rebuild everything
[14:30] <shiftplusone> I think this is a case where I might not be able to do that, but I'll give it a go if the recipes thing ends up not being suitable. Just reading up on it now.
[14:42] <rbasak> shiftplusone: for what you're doing, a snap may work out easier for you. The only thing it may be missing right now is an interface to get you the USB connection.
[14:42] <rbasak> Since really the remote booting component is just a binary drop and doesn't need any interaction with the system except for the USB.
[14:43] <rbasak> And then one snap would work for all releases.
[14:44] <shiftplusone> I'm not convinced snap won't go the way of unity and mir.
[14:58] <shiftplusone> What's the difference between creating a branch and rebasing it on an existing external repo and requesting an import through launchpad?
[15:05] <cjwatson> If you request an import, then you can't push to it on LP directly
[15:05] <cjwatson> I mean, to the imported branch/repository
[15:05] <cjwatson> But you can branch from either an external repo or an import; it's a matter of style
[15:06] <cjwatson> (Though setting a default repo for the project in LP means that we can do some better storage and push optimisations)
[15:07] <shiftplusone> Is either one more suitable for use with recipes or does it not matter?
[15:10] <cjwatson> Depends what you're doing.  If you're nesting a branch with an isolated debian/ directory inside a checkout of upstream then you definitely want to request an import of upstream
[15:10] <cjwatson> Or if you're merging something into upstream as part of the recipe definition
[15:11] <cjwatson> If you're just building a single branch then it doesn't matter much
[15:11] <cjwatson> The constraint is just that recipes can only refer directly to things that are on LP
[15:12] <shiftplusone> Thanks. I'll see how far I get with that info and the rest of the documentation.
[16:09] <shiftplusone> Recipes seem to work well. Really liking launchpad so far.
[16:12] <shiftplusone> A nice feature would be 'build when changelog changes' but I'm probably pushing it now.
[16:20] <korrigan> afternoo
[16:21] <korrigan> can someone please have a look at https://answers.launchpad.net/launchpad/+question/661585 ?
[16:57] <cjwatson> korrigan: grepping logs (veeeerrrrry sloooowly)
[17:06] <korrigan> ok cjwatson
[17:06] <korrigan> thanks for not giving up and apologies if I sound pushy
[17:06] <cjwatson> hmm, finding no matches for 'POST.*korrigan' in our access logs between 2017-11-21 and 2017-12-11 (I'll sync, but that was what I had handy)
[17:08] <cjwatson> korrigan: can you give it one more try now so that I can guarantee there ought to be something in recent access logs ?
[17:09] <korrigan> not sure I understood what you mean cjwatson?
[17:09] <korrigan> what am I to do?
[17:09] <cjwatson> korrigan: try (again) importing your key into LP; tell me exactly what you did
[17:10] <cjwatson> no need to do the keyserver part, since that looks fine
[17:11] <korrigan> at the time I uploaded the key directly into http://keyserver.ubuntu.com
[17:11] <korrigan> and since then I'm expecting an email from LP to proceed
[17:11] <cjwatson> korrigan: That's fine, but you know there's another step where you associate it with your Launchpad account, right?
[17:12] <korrigan> but until today nothing
[17:12] <korrigan> how do I do that cjwatson?
[17:13] <cjwatson> korrigan: https://help.launchpad.net/YourAccount/ImportingYourPGPKey#Importing_your_key_into_Launchpad (or https://help.launchpad.net/YourAccount/ImportingYourPGPKey#Importing_your_key_into_Launchpad_with_gpg if you prefer to use gpg directly)
[17:13] <cjwatson> If you expected something to happen in response to pushing to the keyservers, then that entirely explains the confusion
[17:13] <korrigan> when I navigate to https://launchpad.net/%7Ekorrigan/+editpgpkeys all I see is Keys pending validation:  FED2F7CB46576D20458DCA8DF46939D088CEA558
[17:13] <korrigan> which is the one I'm trying to import
[17:15] <korrigan> which leds me to believe that I already made the step you mention
[17:16] <korrigan> cjwatson, for reference: http://imgur.com/3ZMz6oRl.png
[17:16] <cjwatson> korrigan: OK; please select that pending key, press "Cancel Validation for Selected Keys", and then try to do it again
[17:17] <cjwatson> korrigan: That way I can look at logs (we only keep three weeks of logs from the relevant systems so I can no longer look at what happened when you did this originally, which I appreciate isn't your fault)
[17:17] <korrigan> done as you request cjwatson
[17:18] <cjwatson> OK, just waiting for logs to sync
[17:18] <korrigan> LP msg->A message has been sent to korrigan@aeiou.pt, encrypted with the key 2048R/FED2F7CB46576D20458DCA8DF46939D088CEA558. To confirm the key is yours, decrypt the message and follow the link inside.
[17:18] <cjwatson> which takes about the square root of forever
[17:18] <korrigan> wow
[17:19] <korrigan> just got the email from LP
[17:19] <cjwatson> oh, that did it?  was probably just a glitch in the matrix first time round then
[17:19] <cjwatson> email does get lost sometimes
[17:19] <korrigan> thanks a lot for the help provided cjwatson
[17:19] <cjwatson> no problem, sorry for the delay!
[17:20] <korrigan> nah, no problem with that
[17:20] <korrigan> just going to close the question referring it was solved here
[17:21] <cjwatson> yep
[17:27] <korrigan> all set up
[17:27] <korrigan> again, thanks cjwatson
[17:30] <cjwatson> Great
[17:55] <shiftplusone> Is there a way to build from latest tag using recipes?
[18:11] <cjwatson> Not built-in.  You could automate something externally that pushed the latest tag to e.g. a "stable" branch
[18:21] <shiftplusone> alright