/srv/irclogs.ubuntu.com/2022/11/22/#ubuntu-devel.txt

=== sem2peie- is now known as sem2peie
=== sem2peie- is now known as sem2peie
=== cpaelzer_ is now known as cpaelzer
=== sem2peie- is now known as sem2peie
ahasenack+1 maintenance: since the queue is clogged, I'm going after FTBFSs. Current one is git on s390x (https://launchpad.net/ubuntu/+source/git/1:2.38.1-1ubuntu1/+build/24633504)12:42
kanashiro[m]ahasenack: thanks, git FTBFS is making docker.io a FTBFS as well12:45
ahasenackand ubuntu-advantage-tools12:48
ahasenackso, the heat is on!12:48
xypronHello, I am looking for a sponsor for LP #199737113:02
-ubottu:#ubuntu-devel- Launchpad bug 1997371 in flash-kernel (Ubuntu) "[SRU] add Sipeed Lichee RV Dock and Microchip PolarFire-SoC Icicle Kit in Jammy" [Undecided, New] https://launchpad.net/bugs/199737113:02
ahasenackkanashiro[m]: do you have a log to your failure related to git?14:00
ahasenackI got it once on amd64, but not anymore, and am still trying to spawn an s390x instance in canonistack14:00
ahasenackthe ftbfs is happening on s390x according to launchpad14:00
ahasenackbut canonistack is non-cooperative14:00
kanashiro[m]ahasenack: I did not reproduce the build failures locally, it failed only on s390x, in LP builders14:13
ahasenackbut what's the log? You said it was docker.io?14:13
kanashiro[m]yes14:14
ahasenack<ahasenack> but what's the log? You said it was docker.io?14:18
ahasenackthe log?14:18
kanashiro[m]ahasenack: sorry, it was a test failures because the binary is not available. The build is actually waiting for git in s390x: https://launchpad.net/ubuntu/+source/docker.io/20.10.21-0ubuntu1/+build/2484320314:30
ahasenackok, same thing I saw14:33
cpaelzerlvoytek: thanks for combining https://launchpad.net/ubuntu/+source/libvirt/8.6.0-0ubuntu4 with my uploads14:35
cpaelzerlvoytek: do you want to drive the 3 K and 2 L SRUs from here or do you want me to do so?14:36
cpaelzerI've updated my bugs - they have good SRU descriptions already IMHO, so it should be easy14:36
cjwatsonjbicha: that sbuild-launchpad-chroot issue should be fixed now14:40
lvoytekcpaelzer: I can drive the SRUs over the next few weeks, sure!15:00
cpaelzerlvoytek: oh, sorry I considered you busy after seeing no response and realizing your are in meeting with sally15:00
cpaelzerlvoytek: i've already MRs up :-/15:00
cpaelzerlvoytek: https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/433443 + https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/43344415:01
lvoytekcpaelzer: Ah thanks! The SRU mps look good to me at least in terms of my commit15:03
cpaelzeryou can review them at any time that you get to15:04
cpaelzerlvoytek: and add a proper SRU statement to your bug15:04
lvoytekcpaelzer: Alright, will do15:04
cpaelzerlvoytek: if you end up happy with that over today I can tomorrow upload them to -unapproved15:04
cpaelzerlvoytek: the overall context might still have some more work for you though :-)15:05
cpaelzerjust saw this15:05
cpaelzerlvoytek: https://launchpad.net/ubuntu/+source/libvirt/8.6.0-0ubuntu415:05
cpaelzerthat worked a bit back IIRC, so probably some other lunar changes made it break now15:05
cpaelzerwe need to analyze and fix those15:06
cpaelzerhmm - libxlxml2domconfigtest - seems like something xen related broke on lunar arm builds15:07
lvoytekyeah interesting15:07
cpaelzerlvoytek: suggestion, you'll have a look as that is a great debugging case. Then let me know where you end before leaving to thanksgiving and I can continue as time permits15:07
lvoytekcpaelzer: sounds good, I'll get started on that15:08
cpaelzerlvoytek: it is the value for shadow_memkb in xen. So whatever happens, the tests generate a different value than expected (smaller)15:10
cpaelzerexpected values are in ./tests/libxlxml2domconfigdata/...15:10
cpaelzerlvoytek: https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=2c992810854a15b41be920519ce83a4a328d516815:11
cpaelzerlvoytek: https://gitlab.com/libvirt/libvirt/-/commit/72d4709ab901dd3699d342f15ca3aff9bffddf9615:11
-ubottu:#ubuntu-devel- Commit 72d4709 in libvirt/libvirt "tests: Fix libxlxml2domconfigtest with latest xen"15:11
cpaelzerlvoytek: sorry I'm in the flow :-)15:12
cpaelzerlvoytek: I'll throw 72d4709 on top, if it builds fine - otherwise you can have a look15:12
cpaelzerlvoytek: hopefully has all we need https://launchpad.net/ubuntu/+source/libvirt/8.6.0-0ubuntu515:18
cpaelzerlvoytek: arm64 already built \o/15:26
lvoytekcpaelzer: Nice, thanks!15:27
ahasenackso I'm getting this build error:20:46
ahasenack git : Depends: git-man (< 1:2.37.2-.) but 1:2.38.1-1ubuntu2 is to be installed20:46
ahasenackgit comes from whatever image the builder is using20:46
ahasenack2.38.1-1u2 is in proposed20:46
ahasenackfor some reason, apt is refusing to upgrade the installed git20:46
ahasenackhttps://launchpadlibrarian.net/635412147/buildlog_ubuntu-lunar-s390x.ubuntu-advantage-tools_27.12~23.04.1_BUILDING.txt.gz20:46
ahasenackI'm suspiscious of that proposed pinning20:47
* ahasenack checks the build-deps of u-a-t carefully20:50
sergiodjisn't it too soon to retrigger the build?  you've uploaded git one or two hours ago, maybe it needs more time to reach the archive?20:50
sergiodj(just thinking out loud here)20:51
cjwatsonwhat installed git?20:51
cjwatsonsorry, that was confusingly phrased.  I mean, "apt is refusing to upgrade the installed git" is a confusing statement to me because I would not expect git to be installed yet20:51
ahasenackI checked with apt-cache policy that the new build is visible in lunar-proposed20:51
ahasenackand it takes a long time, indeed. Between 1h and 2h after the build is done20:52
cjwatsonrmadison seems to disagree at the moment so perhaps it was very recent20:52
cjwatson$ rmadison -s lunar,lunar-proposed git20:52
cjwatson git | 1:2.37.2-1ubuntu1 | lunar          | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x20:52
cjwatson git | 1:2.38.1-1ubuntu1 | lunar-proposed | arm64, armhf, riscv6420:52
cjwatson git | 1:2.38.1-1ubuntu2 | lunar-proposed | source, amd64, i386, ppc64el20:52
cjwatsonno lunar-proposed/s390x20:52
ahasenackapt-cache sees it in proposed20:52
ahasenackah, wait a sec, I did it on amd6420:52
ahasenackjiu9tu429thiH(#$U#(*@$!#()U$20:52
cjwatsonimportant detail there :)20:52
ahasenackand I don't have the s390x vm anymore20:52
ahasenackI did see discepancies between rmadison and apt before, that's why I was trusting apt more20:53
ahasenackbut I have to be in the right arch :/20:53
sergiodjheh.  just wait a couple more hours, I'd say20:53
cjwatsonlooks like it just finished publishing20:53
cjwatsonretry now20:53
ahasenackI don't see s390x yet in rmadison20:54
cjwatsonthe only reason you'd see discrepancies between rmadison and apt is if the publishing run completed only very recently and so the dists mirror used by rmadison hasn't quite caught up yet (or, rarely, if the mirroring process is stuck)20:54
cjwatsonthis is the "only very recently" case, but I checked ftpmaster logs20:55
ahasenackok, retrying20:56
cjwatson(rmadison shows it now)20:58
* ahasenack crosses fingers20:59
ahasenackit built \o/21:09
ahasenack" s390x (Accepted)"21:09
ahasenack(u-a-t)21:09
ahasenackkanashiro[m]: I'll kick the s390x build of docker.io too for youk21:12
ahasenackI think LP eventually retries, but I don't know when or what triggers it, so I'm clicking the button :)21:12
kanashiro[m]ahasenack: thanks!21:18
=== tuxifreund_ is now known as tuxifreund

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!