[14:15] <mop> hi all, there is a way to trigger a build on launchpad when one of its dependencies is updated ?
[14:16] <mop> s/a build/a build of a project/
[14:17] <cjwatson> that depends on what kind of build.  you might be looking for recipes: https://help.launchpad.net/Packaging/SourceBuilds
[14:23] <mop> cjwatson, I'm managing build of 2 packages and 1 depends on the other
[14:23] <mop> there is a way to rebuild the second if the first is changed ?
[14:24] <cjwatson> oh.  no, not out of the box, although you can often arrange such things with some webservice API scripting.
[14:24] <mop> (I agree with you that if some important change happens A version change and B deps must be updated ...)
[14:24] <cjwatson> why do you need to, though?  usually in such cases dependent packages only need to be rebuilt in quite limited circumstances (a compatibility break).
[14:25] <mop> ;) predictive answer
[14:25] <cjwatson> as such this sort of logic would be very specific to the situation at hand.
[14:26] <mop> My point was: I'm working on the HEAD of both masters ... A change something that breaks B
[14:26] <cjwatson> I know there are some situations where you do need it, e.g. languages with very unstable ABIs.  They should normally be accompanied with very specific dependencies.
[14:26] <mop> currently I must wait the daily build to know it
[14:26] <cjwatson> Anyway, my answer stands: this is something you'd need to arrange externally, although you may well be able to make use of the Launchpad webservice API to do it.
[14:27] <mop> cjwatson, ok tnx
[14:27] <mop> it was a plus, nothing blocking
[14:27] <mop> thank you , always helpful
[14:28] <mop> oh, a question if you know :
[14:28] <mop> I had the feel that the daily recipe run also when no changes happens to a code hosted on your git
[14:29] <cjwatson> Shouldn't in general be true, though there may be the occasional bug that leads to something like that.
[14:29] <mop> is it true or just a wrong impression ?
[14:30] <mop> ok, now I restarted my test so I will monitoring it, tnx again
[14:30] <cjwatson> It only runs when the recipe is internally considered "stale", and the only thing that marks a recipe stale is a push to one of its branches.
[14:31] <cjwatson> It's possible there's a race if you're also triggering builds manually: maybe the stale marker isn't cleared at quite the right point or something.
[14:32] <mop> yes, it was what I supposed, probably I interleaved manual and daily
[20:44] <benjaoming> Is there a work-around for the dput vs gpg2 signing issue? -> https://bugs.launchpad.net/ubuntu/+source/dput/+bug/1450287
[20:46] <benjaoming> I would guess the work-around is to export one's pubring.kbx to a pubring.gpg as this poster suggests... http://stackoverflow.com/a/34221494/405682 -- also, it seems to work...