[01:25] <Unit193> mapreri: So far I've only been backporting two packages I maintain, since I know them better, which interact with websites so are more likely to break.  On that line, there's also streamlink which interacts with streams, I think this could be useful too.  What do you think?
=== cpaelzer_ is now known as cpaelzer
=== sem2peie- is now known as sem2peie
[15:00] <KBar> Hello. I'm a bit confused. Am I obliged to sign the Canonical Individual Contributor License Agreement before sending out patches or translations?
[15:05] <KBar> If that's off-topic for this channel, please tell me so. Thanks.
[15:06] <seb128> KBar, depending of the project you are contributing to but for most of Ubuntu now, only a few specific codebases
[15:07] <seb128> KBar, you can find the list of projects on https://canonical.com/projects/directory
[15:13] <KBar> seb128 so launchpad is there. Does that mean Launchpad itself (its code) or the entirety of the platforms and all projects in it? Also, translations to those listed projects are covered under this agreement, correct? Apologies if it's out of scope for this channel. I thought there would be an #ubuntu-legal channel or something, but alas!
[15:13] <KBar> s/platforms/platform
[15:13] <seb128> KBar, it's fine for this channel, and it means launchpad itself as in http://launchpad.net/launchpad
[15:15] <seb128> KBar, translations is a bit of a border line topic, I don't think it's really copyright material
[15:15] <seb128> but some of the projects are more strict and want CLA for anything commited to their Vcs
=== paride9 is now known as paride
[15:20] <KBar> hmm i see. im still kinda conflicted. on one hand, i dont contribute to the listed projects (apart from translations), but on the other, in the FOSS ecosystem, your code is bound to "leak" or "flow" into them.
[15:34] <enr0n> bdmurray: Can you please kill my remaining PPA autopkgtests for systemd/251.2-2ubuntu1~ppa1? I am not sure what is going on with them, and I would like to trigger tests against my new version.
[15:35] <enr0n> The "Running for" duration has decreased since yesterday for arm64 and ppc64el.
[15:40] <bdmurray> enr0n: I'm gonna try and figure out a bit more what is going on with them but will kill them at my EOD.
[15:41] <enr0n> bdmurray: Okay, is it OK if I have new tests triggered in the mean time? Or would you like me to wait until tomorrow?
[15:41] <KBar> Which scripts do y'all use the most from the devscripts (included in ubuntu-dev-tools) package?
[16:23] <bdmurray> enr0n: I'm just going to go ahead and kill them
[16:23] <enr0n> bdmurray: ack, thanks for looking into this
=== sem2peie- is now known as sem2peie
[17:05] <teward> waveform: for awareness, the quassel in kinetic is held up by a missing risc build, i'm assuming that is because riscv is backed up to no end on the builders
[17:15] <bdmurray> It looks like its missing a dependency https://launchpad.net/ubuntu/+source/quassel/1:0.14.0-1ubuntu1/+build/23846308
[17:30] <waveform> that's ... a little odd; it's got a dep-wait on 5.94.0-0ubuntu1, but knotifyconfig is already on 5.95.0-0ubuntu1 in kinetic (including on riscv)
[17:31] <waveform> does that mean it "read" the dep and then took so long waiting to build it that a new version of the dep appeared in the meantime and now it'll never be satisfied by that specific version (despite it being later)?
[17:32] <bdmurray> I'll click rebuild to see what happens
[17:34] <bdmurray> quassel tried ot build at 2022-06-13T15:17:42Z and knotifyconfig was published after that (19 hours ago)
=== rs20090 is now known as rs2009
=== sem2peie- is now known as sem2peie
=== vogelfrei2 is now known as vogelfrei
=== sarnold_ is now known as sarnold
[21:26] <diddledani> some of ya'll might be interested in this stream I just did - the recording will be available in ~10 minutes: https://youtu.be/OrMjQtPxo5Y (Intel binaries using Rosetta from macOS inside an Ubuntu 22.04 VM!)