[00:11] <vorlon> mwhudson: hmm I think I saw something from doko /somewhere/ about the armhf target in gcc-11 being different but I can't find it.
[00:12] <vorlon> mwhudson: related: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1939379
[00:12] <mwhudson> vorlon: there was a thing with the default fpu type causing problems
[00:12] <mwhudson> the dkms faceplants are something else though
[00:12] <vorlon> oh are they?
[00:12] <mwhudson> well i thought so anywayh
[00:13] <mwhudson> "isb" isn't a fpu instruction
[00:13] <mwhudson> i think it's probably v7?
[00:13] <mwhudson> so somehow gcc things it's targeting armv6
[00:13] <vorlon> mwhudson: are the failures happening with gcc-11 in 11.2.0-1ubuntu3 from -proposed?
[00:13] <vorlon> eew
[00:14] <vorlon> mwhudson: well anyway, I hinted these because they're not glibc-related regressions
[00:14] <mwhudson> vorlon: this build log i'm looking at is ubuntu2
[00:14] <mwhudson> vorlon: yes that's fair, thanks
[00:15] <mwhudson> oh or maybe this is an arm vs thumb thing
[00:18] <mwhudson> anyway my turn for lockdown childcare, biab
[06:03] <doko> mwhudson, schopin: yes, fixing is better, but that was a small lump for some work arounds. no retriggered the tests
[06:03] <doko> mwhudson, which package is the thumb/arm mode issue?
[07:23] <schopin> LukasM[m]: could you please sync git-remote-hg? (LP: #1940385) -> fix the autopkgtests
[07:23] <schopin> TIA :)
[07:25] <slyon> schopin: ACK, looking.
[08:42] <schopin> doko: on dh-python, do you remember if there was a technical reason why you disabled the nosetests in Ubuntu? I can run the autopkgtest from the current sid version in an impish and the nosetests run fine.
[08:44] <doko> schopin, they need adjustment for the supported and default version, which happens when Debian and Ubuntu are out of sync
[08:47] <schopin> doko: is that debian bug 975536 ?
[08:47] <doko> probably
[08:48] <schopin> OK. I'll have a deeper look but I think the package can be synced back :). Thanks for the answers, appreciated.
[09:56] <mwhudson> doko: e.g. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/x/xtables-addons/20210816_083905_62156@/log.gz
[10:32] <mwhudson> grar https://launchpad.net/ubuntu/+source/libuev/2.3.1-1ubuntu1/+build/21989755
[11:25] <schopin> slyon: another sync for you ;-) LP: #1940423
[12:03] <slyon> schopin: done!
[12:04] <schopin> thanks!
[13:32] <tsimonq2> Is this thing on?
[13:37] <RikMills> tsimonq2: no
[13:38] <RikMills> IRC is dead ;)
[13:38] <tsimonq2> Well, hi either way. :P
[13:39] <RikMills> hi indeed. good to see you
[13:40] <tsimonq2> Unit193 ping, I heard something about pastebinit?
[13:40] <tsimonq2> RikMills: Good to be back :)
[14:33] <schopin> slyon: another one, haveged! A bit more involved this time, a proper merge! LP: #1940439
[14:34] <slyon> will have a look in a bit!
[14:36] <jawn-smith> I'll put these here as well: LP: #1939728 LP: #1939739
[14:36] <jawn-smith> They could both use sponsorship if anyone has the time
[14:49] <bdmurray> Should this build be taking this long? https://launchpad.net/ubuntu/+source/sshguard/2.3.1-2/+build/21989457
[14:50] <bdmurray> The last one took 11 minutes so probably not.
[15:06] <jawn-smith> I'm pretty sure wcc just needs a rebuild with the new glibc in order to fix the failing tests. My reasoning is that when I run autopkgtests with the source.dsc they work every time, but if I just name the package I get the same failures as seen in current tests. Is a rebuild something a core dev can do or is there a process to get that done?
[15:15] <bdmurray> jawn-smith: look at example 1 here https://wiki.ubuntu.com/UbuntuDevelopment/NBS
[15:16] <laney> That sounds like it'd be a glibc bug though, if existing binaries break
[15:18] <jawn-smith> I suppose I'm not 100% sure it's glibc as when I'm running these tests I'm using the whole volatile toolchain ppa
[15:20] <jawn-smith> bdmurray thanks for the link, I'll prepare a no change rebuild after a little more poking at this package and it's tests
[15:31] <schopin> hmmm. How come 'git ubuntu clone notmuch' gives me a branch that points to the focal release?
[15:42] <jawn-smith> okay yeah just using --apt-pocket=proposed=src:glibc causes the segfault with the package name but not the source.dsc
[15:56] <schopin> jawn-smith: glibc 2.34 has migrated from -proposed, fwiw.
[15:57] <schopin> (or I have the -proposed libc on my system, which would be... less than ideal)
[15:58] <jawn-smith> schopin I think you have the -proposed libc on your system: https://launchpad.net/ubuntu/+source/glibc
[15:59] <ginggs> schopin: 'rmadison glibc' says no
[16:01]  * schopin goes check his apt logs, scratching his head...
[16:02] <schopin> Oh. Well. I didn't catch that one, then :/
[16:03] <schopin> That's good news, in a way. I've been using it for 2 days without any noticeable issue :)
[16:44] <bdmurray> ginggs: It seems to me like we should also add dolfin[x] to big_packages for stable releases too. Do you agree?
[16:47] <bdmurray> uh, disregard me
[16:47] <ginggs> bdmurray: are there separate autopkgtest-package-configs	 for stable releases?
[16:48] <bdmurray> ginggs: no, but maybe once its hinted we should retest the stable releases so that we have an adjusted baseline
[16:49] <ginggs> bdmurray: ack
[16:53] <ginggs> bdmurray: i'll schedule those tests tomorrow morning
[18:24] <jawn-smith> Would a core dev mind restarting a gnutls28 build on ppc? It failed to build and the logs indicate a timeout
[18:24] <jawn-smith> https://launchpad.net/ubuntu/+source/gnutls28/3.7.1-5ubuntu1/+build/21992250
[18:29] <mdeslaur> jawn-smith: done
[18:29] <jawn-smith> thanks!
[18:29] <mdeslaur> np
[19:14] <Unit193> tsimonq2: 1. Openstack moved their paste service, though there are redirects I'm not sure they're working.  https://paste.opendev.org/show/bFVbXF44VrHbyS1Fxpd0 would be the new config.  2. https://paste.opendev.org/show/bHXpSLHjS4nu7WVJy5ST segment one is needed for config file support of defining private pastes (iirc), and the latter is LP 1785821 which is leftover from the python3 port.  As a side
[19:14] <Unit193> note, you may want to see https://github.com/lubuntu-team/pastebinit/issues/6 too.
[20:51] <tsimonq2> Thanks Unit193
[20:54] <mitya57> tsimonq2: welcome back!
[21:39] <jawn-smith> bdmurray do you mind hinting dh-ada-library? The tests have been failing since well before glibc 2.34
[21:42] <Unit193> tsimonq2: Thanks for looking into it, I owe an openstack guy a ping back now. :P
 "Simon Quigley: welcome back!" <- Thanks! Good to see you
 "Simon Quigley: Thanks for..." <- You can thank teward for nagging me enough. :P
[21:49] <teward> *was prodded*
[21:50] <tsimonq2> teward: pastebinit
[21:50] <teward> Unit193: the other reason Simon is online is 'cause he got the equivalent of a mega lightning strike on him which brought him back to life xD
[21:50] <teward> tsimonq2: i know, it's typical when I get prodded randomly I show up and indicate i was pinged in case someone wanted to chime in
[21:50] <teward> i just had to read ;)
[21:51] <Unit193> At least it's all patches!
[22:05] <bdmurray> jawn-smith: not for every arch though right?
[22:06] <jawn-smith> It's the same error for amd64, arm64, ppc64el, and s390x
[22:07] <bdmurray> right so it only needs to be hinted for those arches correct?
[22:09] <jawn-smith> Sounds correct to me, though I don't see any runs for it on riscv64