[07:39] <LocutusOfBorg> mitya57, fixed in lunar-proposed
[07:49] <mitya57> LocutusOfBorg: thanks a lot!
[07:50] <LocutusOfBorg> I'm trying to open a merge request on sourceforce.net, but its incredibly difficult
[07:51] <mitya57> I managed to do that a couple of times :)
[07:51] <LocutusOfBorg> I created the fork
[07:51] <LocutusOfBorg> https://sourceforge.net/u/locutusofborg1/simgear/ci/next/tree/
[07:51] <LocutusOfBorg> pushed my "latomic" branch
[07:51] <LocutusOfBorg> and now?
[07:52] <LocutusOfBorg> meh, afk now
[07:52] <LocutusOfBorg> will look later
[07:53] <mitya57> https://wiki.flightgear.org/Making_a_SourceForge_Merge_Request check step 16
[08:14] <arraybolt3> Step 1: Move to Git(Hub/Lab)/LaunchPad.
[08:14] <arraybolt3> :P
[10:57] <mitya57> LocutusOfBorg: and another question to you. Do you think we have a chance to get hedgewars build-deps installable in the nearest time?
[10:57] <mitya57> See https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4966/+build/24922404
[12:50] <LocutusOfBorg> mitya57, yes, I'm at level8 of rebuilds
[12:51] <mitya57> Good, thanks!
[12:54] <LocutusOfBorg> error, level 11
[12:58] <mitya57> I wonder how many levels are there :)
[15:22] <LocutusOfBorg> mitya57, 26? or something like that
[15:55] <arraybolt3> Is anyone else getting odd BADSIG errors while trying to update their Lunar systems? For some reason I can update an LXD container in the cloud, but my main laptop and a Lunar schroot are both unable to update because apt chokes on InRelease. Strangely enough, I can manually download the InRelease file and check it with GPG, and it comes back clean.
[15:56] <arraybolt3> The version of apt is the same on all my systems, so I'm pretty sure that's not the problem.
[15:59] <arraybolt3> And the same mirror is in use on both systems.
[16:00] <arraybolt3> (The schroot is using just the standard archive.ubuntu.com, while my laptop and cloud container are using us.archive.ubuntu.com.)
[16:12] <arraybolt3> This is the pastebin of the exact error: https://dpaste.com/FFCF6LX7F
[16:16] <arraybolt3> (Also changing mirrors didn't have any effect.
[16:22] <arraybolt3> (Actually I just switched to an HTTPS mirror and that seems to be working. Maybe something's truncating the file on accident, or perhaps someone actually is trying to mess with me :P)
[16:45] <arraybolt3> Scratch everything I said above, turned out it was just apt-cacher-ng causing chaos like it seems to do every week or so. It had a corrupted InRelease file cached, removing it (and also restarting apt-cacher-ng) seems to have solved the problem.
[17:20] <LocutusOfBorg> mitya57, eureka! the merge button is visible if I visit my fork
[17:21] <LocutusOfBorg> so to open an upstream MR, I have to start from local fork LOL
[20:06] <arraybolt3> Is anyone around who can change what teams have upload privileges to certain packages? There's a package, qtxdg-tools, that was split off from libqtxdg (I believe) in upstream LXQt. Members of the lubuntu-dev team (of whom I am one as of a few days ago) should be able to upload to there, but it appears that package is not "owned" by ~lubuntu-dev currently, as I just tried to upload to there
[20:06] <arraybolt3> and it was rejected.
[20:07] <arraybolt3> (I don't know if a Core Dev can do this or not, but if so, tsimonq2: ^)
[20:07] <tsimonq2> MOTU+
[20:07] <tsimonq2> Needs to be added to the packageset
[20:07] <tsimonq2> Which is teward territory :0
[20:07] <tsimonq2> s/0/P/
[20:08]  * tsimonq2 summons chaosadmin with a gallon of coffee
[20:08] <rbasak> Please ask devel-permissions@ to fix it
[20:08] <teward> ^^ that
[20:08] <arraybolt3> Well that cascaded fast. Will od.
[20:08] <arraybolt3> s/od/do/
[20:08] <rbasak> The automated packageset generation code needs attention, but we haven't had anyone touch it in a while :-(
[20:09] <arraybolt3> I dunno if this is anything that even could have been autodetected - AFAIK, qtxdg-tools just popped up out of thin air, so it's not exactly something that an automated tool would have known needed to be ~lubuntu-dev territory.
[20:09] <arraybolt3> Anyway, writing email.
[22:56] <Piraty> eh, i get a few 401 from esm.ubuntu.com during release upgrade . https://ttm.sh/0vh.txt
[23:05] <Piraty> eh, i get a few 401 from esm.ubuntu.com during release upgrade . https://ttm.sh/0vh.txt
[23:05] <Piraty> coming from 20.04
[23:06] <Piraty> not sure why this machine tries to pull from there... ?
[23:07] <Piraty> well i got `/etc/apt/sources.list.d/ubuntu-esm-apps.list.distUpgrade` here
[23:07] <Piraty> so i guess this is what the do-release-upgrade tool created