[03:01] <mwhudson> where did libburnia upstream go?
[03:03] <mwhudson> oh the git bits are still around
[06:23] <icey> is there any way I can re-poke something that's marked ftbfs in proposed (Groovy)? It failed yesterday but I think it's not an issue with my package (Depends: python3 (>= 3.8.3-1~) but 3.8.2-0ubuntu2 is to be installed)
[06:39] <RikMills> icey: what package? If you have upload rights, there will be a retry button on the build
[06:41] <icey> RikMills: I don't have upload rights, https://launchpad.net/ubuntu/+source/python-os-traits/2.4.0-0ubuntu1/ is the package that failed to build
[06:42] <icey> RikMills: I do suppose I'll be working to get upload rights for the OpenStack packages sometime soon
[06:43] <RikMills> icey: ok. that is in main, so I can't do it. so you need a core dev to poke, unless as you say it in another set
[06:44] <RikMills> FYI the reason for that dep wait 'should' be fixed
[06:45] <icey> RikMills: yeah - I can't reproduce the failure locally this morning, and I heard some conversation about it yesterday :)
[06:49] <RikMills> jibel: this is still happening with ubiquity 20.10.8 https://i.imgur.com/4LTUds6.png
[06:51] <RikMills> icey: looks like it got poked ;) thanks LocutusOfBorg
[06:55] <icey> thanks LocutusOfBorg
[06:55] <icey> and RikMills: Where are you seeing who poked it?
[06:56] <RikMills> icey: You can't, which is a lack in launchpad. I know because I asked in another chat if someone could poke
[06:57] <jibel> RikMills, yeah, I saw the comment on the bug report.
[06:57] <jibel> looking at Mate now
[06:58] <RikMills> jibel: thanks. obviously I confirmed in a VM from that screenshot
[06:58] <icey> RikMills: well, now I'm wondering where else I should be :-D
[06:59] <icey> RikMills: any chance you could ask about getting neutron-vpnaas poked as well, seems to be the same failure :)
[06:59]  * icey goes back to hiding in the corner
[07:00] <Unit193> It's a pretty fun place to be, lurking the corner in the shadows. :3
[07:00] <icey> :-D
[07:00] <RikMills> icey: here is just fine. it was a not public telegram thing. there are plenty of core devs in here, but IRC lacks being able to see who is online (or recently so)
[07:01] <icey> RikMills: indeed it does lack that :)
[07:03] <LocutusOfBorg> icey, done
[07:03] <icey> thanks again LocutusOfBorg
[07:04] <Unit193> Closest you have is /wii $name, which shows you idle time.
[07:04] <LocutusOfBorg> I'm also mass retrying the last 69 packages in excuses age
[11:10] <juliank> trying to bisect make but shit this is though
[11:10] <juliank> There's all sorts of weird incarnations you have to do to bootstrap the build environment
[11:10] <juliank> e.g. po/ is empty
[11:10] <juliank> and then it complains about missing .po files
[11:11] <juliank> And doing this over SSH in a cloud on a different continent is not exactly fun
[11:11] <cjwatson> Doesn't ./bootstrap do the job?
[11:12] <juliank> cjwatson: In 4.3, yes, if you have git:// access
[11:12] <juliank> cjwatson: It's not there in 4.2, and I'm bisecting between those two
[11:13] <cjwatson> Ah
[11:13] <juliank> Now it's trying to rsync from translationproject.org - ugh
[11:13] <juliank> this ain't going to work
[11:13] <juliank> I can only do http*
[11:14] <juliank> If I do make make, it does nice things but ultimately fails with
[11:14] <juliank> /usr/bin/ld: /tmp/make/glob/glob.c:1342: undefined reference to `__alloca'
[11:14] <juliank> why can't people have decent build systems?
[11:42] <juliank> it's done
[11:43] <juliank> xnox: So, I finished bisecting make on s390x for the flatpak-builder/s390x issue. The cause of the issue was a change to make it use posix_spawn() instead of fork()/exec().
[11:44] <juliank> xnox: I'm not sure if there's an issue with posix_spawn() on s390x, or make's use of it, but I did upload a make 4.3-4ubuntu1 that passes --disable-posix-spawn to configure to make it work again
[11:44] <juliank> I also forwarded that change to Debian
[11:45] <juliank> This is the offending commit: https://paste.ubuntu.com/p/tYhbJFKN76/
[11:47] <juliank> Maybe there's undefined behavior in there and we compile s390x at -O3, could also be the reason, who knows
[11:47] <juliank> debian doesn't test s390x
[11:47] <juliank> debian bug 964541
[11:56] <xnox> juliank:  we should be compiling s390x at -O2, we only use -O3 for ppc64el by default
[11:56] <juliank> xnox: ah ok
[11:57] <xnox> juliank:  is there a launchpad bug about this too? we could try to escalate it to IBM
[11:57] <juliank> xnox: I don't think so
[11:57] <xnox> juliank:  ok, i can open a new one.
[12:00]  * xnox learns word heisenbug
[14:22] <seb128> bah, I don't understand the util-linux build failure in groovy :(
[14:22] <seb128> debian/bsdextrautils.install has
[14:23] <seb128> +#!/usr/bin/dh-exec --with=install
[14:23] <seb128> +usr/bin/write => usr/bin/write.ul
[14:23] <seb128> (well, that's the diff, the actual file doesn't have the +)
[14:23] <seb128> and the build fails on
[14:23] <seb128> dh_install: warning: Cannot find (any matches for) "=>" (tried in ., debian/tmp)
[14:23] <seb128> debian/tmp/usr/bin/write does exist
[14:24] <seb128> and the same .install / rules work in Debian (unless I overlooked a diff/change)
[14:27] <seb128> hum, it's just the error being misleading
[14:29] <Unit193> Silly question, but I presume that install file has +x?
[14:31] <ahasenack> I haven't seen --with=install in the sheban line before
[14:33] <seb128> Unit193, not silly at all, thanks a lot for pointing that out
[14:33] <ahasenack> was that it?
[14:34] <mdeslaur> TELL US WHAT IT WAS!!!
[14:34] <mdeslaur> WE WANT TO KNOW!!!
[14:35] <seb128> lol
[14:35] <Unit193> Uh oh, someone appears to have made mdeslaur's coffee too strong.
[14:35] <seb128> build is ongoing, ut it was missing a +x yes
[14:35] <Unit193> Happy to have been of help.
[14:36] <mdeslaur> Unit193: perhaps I didn't put enough rum in it
[14:36] <seb128> will teach me to merge by just applying the debdiff :p
[14:37] <Unit193> If the diff is generated correctly (eg, git) `patch` can understand to set the correct permissions.
[14:38] <seb128> right, well it wasn't in this case because I wrongly assumed it was a simple diff and doing complicated things wasn't needed :p
[14:38] <seb128> the error is really unhelpful though
[14:38] <seb128> 'dh_install: warning: Cannot find (any matches for) "=>" (tried in ., debian/tmp)'
[14:38] <seb128> it doesn't even tell you the item it tries to match
[14:39] <Unit193> It tried to install, literally, '=>'
[14:39] <seb128> not to mention the permission, feels like something could warn about a dh-exec script not being +x
[14:46] <seb128> ahasenack, but yeah, that was the issue :/
[14:46] <ahasenack> good to know
[14:47] <seb128> indeed
[14:47] <seb128> Unit193, thank you again!
[14:47] <Unit193> Sure thing.
[14:47] <ahasenack> it's in the same category of weird errors when you try to run a shell script what has windows line endings
[14:49] <seb128> right, 'fun ones" :)
[14:50] <Unit193> Or the error when pkg-config is missingg..
[17:34] <realtime-neil> How does one build the various artifacts listed here? https://releases.ubuntu.com/20.04/
[18:58] <sarnold> realtime-neil: I think this is the starting point https://code.launchpad.net/ubuntu-cdimage
[18:59] <realtime-neil> sarnold: much thanks
[20:09] <mwhudson> it's pretty hard to get going on your own machine unfortunately
[20:23] <ahasenack> hi +1 maintenance team, I'm looking over the nginx and python-certbot/python-acme migrations
[20:23] <ahasenack> is there a highlight word for this team, btw?
[21:00] <ahasenack> I'm noticing a larger than usual delay between a dep8 run disappearing from the /running url, and its result showing up in autopkgtest.u.c, anyone else wondering?
[21:00] <ahasenack> so much that earlier today I kicked another run, thinking "didn't I trigger this before?", and an hour later both results came back
[21:01] <ahasenack> specifically, I'm waiting for a result on http://autopkgtest.ubuntu.com/packages/p/python-certbot-apache/groovy/armhf
[21:16] <mwhudson> vorlon: should we seed shim-signed and grub-pc on all bootable amd64 images? some flavours currently end up with grub-efi-amd64 to satisfy shim-signed's alternate dep and then install fails