[18:39] <bandali> hi, anyone know if it's possible to use `snapcraft remote-build` in a fully non-interactive way (e.g. from terminal or a CI pipeline)?
[18:40] <bandali> as of now, it seems i have to manually authorize each one of canonical's launchpad build machines for every invocation of snapcraft remote-build, which is not feasibly doable in a non-interactive setting
[21:13] <cjwatson> bandali: It's supposed to store its credentials in its data directory, from what I can see from the snapcraft source.  But you'd really be best off asking the Snapcraft developers rather than us
[21:14] <cjwatson> bandali: (and no, you don't have to authorize build machines separately, LP API authentication doesn't work like that)
[21:34] <bandali> cjwatson, oh i see! hmm it might be because i'm not carrying that data dir between subsequent runs, so i'll try that; thanks for the clue!
[21:34] <bandali> (and actually i did try asking the snapcraft folks first, but they suggested i try asking here :p) thanks again
[21:44] <realtime-neil> Where is the launchpad-resident source repository for this? https://launchpad.net/debian/+source/orocos-kdl
[21:46] <realtime-neil> follow up question: how would I write a recipe that takes orocos-kdl and does a `merge` with my fork thereof?
[22:52] <cjwatson> realtime-neil: There probably isn't one.  https://tracker.debian.org/pkg/orocos-kdl links to https://salsa.debian.org/science-team/orocos-kdl, so you could create an import of that
[22:52] <cjwatson> bandali: Oh yeah, if you're not carrying over the data directory that would definitely do it!
[22:53] <realtime-neil> cjwatson: okay, just checking to make sure I wasn't polluting LP unnecessarily.
[23:01] <cjwatson> Should be fine