/srv/irclogs.ubuntu.com/2024/06/27/#ubuntu-devel.txt

=== guiverc2 is now known as guiverc
=== JanC is now known as Guest4647
philrocheahasenack_: As part of SRU duty would you be able to look livecd-rootfs 24.04.72 in noble queue https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=livecd-rootfs ?10:29
bdrung@pilot in11:00
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: bdrung
bdrung@adrien, do you mind me sponsoring https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2067672 to oracular (wearing my sponsoring hat)?11:26
bdrungahasenack_, Fix build failure on armhf with rdma-core 52.0-2 upload12:09
ahasenack_philroche: noted12:12
ahasenack_bdrung: you just uploaded to debian?12:12
bdrungahasenack_, yes12:15
ahasenackphilroche: ah, you meant unapproved12:51
philrocheyes unapproved12:52
ahasenack5 bugs12:53
ahasenackit's racing ubuntu-advantage-tools in number of fixes per upload :)12:53
ahasenackthere are 3 livecd-rootfs jammy uploads to unapproved13:01
ahasenackalso one for mantic13:01
ahasenackand mantic also has one in proposed13:01
ahasenackphilroche: should all but the most recent one be rejected? https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=livecd-rootfs13:02
ahasenackand the most recent one doesn't include the other two in the changes file13:03
philrocheyeah I just noticed that. They all need to be rejected. I can re-upload and ensure all versions and changes are included13:03
ahasenackok, all jammy ones13:03
ahasenackdone13:04
ahasenacklocutusofborg: hi, regarding gambas3 ftbfs in armhf, https://bugs.launchpad.net/ubuntu/+source/gambas3/+bug/201242013:05
-ubottu:#ubuntu-devel- Launchpad bug 2012420 in gambas3 (Ubuntu) "armhf patch no longer necessary, causes FTBFS with new poppler" [Undecided, In Progress]13:05
ahasenackI added some notes, fixed one build problem, but it's still failing elsewhere now. Some components weren't build for some reason, no clear error that I could see13:06
ahasenackmaybe that's what the original patch intended to fix, which I removed because it makes the build fail on armhf with new poppler and its c++20 standardization13:06
ahasenacklocutusofborg: current ftbfs in armhf in oracular-proposed: https://launchpad.net/ubuntu/+source/gambas3/3.19.1-1ubuntu2/+build/2860387513:07
ahasenacksame symptom as https://bugs.launchpad.net/ubuntu/+source/dia/+bug/207028413:08
-ubottu:#ubuntu-devel- Launchpad bug 2070284 in dia (Ubuntu) "FTBFS: ‘starts_with’ has not been declared in ‘std::string’" [Undecided, Fix Released]13:08
philrocheahasenack: livecd-rootfs for Jammy now re-uploaded including all changes to unapproved queue https://launchpad.net/ubuntu/jammy/+queue?queue_state=1&queue_text=livecd-rootfs13:16
ahasenackok13:16
ahasenacklivecd-rootfs is my current task13:16
tewardddstreet: mapreri: I made a backport request in #2071361 for a package I maintain in Debian, but because its my package and my bug I need at least one of you to approve it before I push the two backport packages to the repositories.13:40
tewardi say 'my package' because I'm also the Debian driver for it (it's a Universe package)13:41
ahasenackphilroche: could you please update the bug tasks of https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929?13:48
-ubottu:#ubuntu-devel- Launchpad bug 2062929 in livecd-rootfs (Ubuntu) "AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel" [Undecided, New]13:48
ahasenackit only has the devel task, and it's "new"13:48
tewardahasenack: does it need jammy and mantic targeted?13:49
tewardif so I can JFDI13:49
ahasenackteward: probably, but I ask algo because I was just reviewing a livecd-rootfs upload to mantic unapproved that mentions this bug13:49
ahasenackand I think there is a jammy unapproved one too, will check next13:49
ahasenackbut the latest upload in oracular doesn't mention the bug, so I want to see the status in oracular as well13:50
ahasenackwhich matters for SRU purposes13:50
tewardthat skips Noble in the thing so that's why i ask which series / tasks it needs targeted to13:50
tewardlooks like philroche got it13:52
philrocheyes jammy and mantic added13:53
tewardand just because you mentioned it i put Oracular on it too (though that's what the "bug task" is, it always defaults to CurrentDevel)13:53
teward*sips coffee*13:54
ahasenackI actually prefer to be specific in the case of devel releases13:54
ahasenackso many bugs are "fix released" in the main task, and to understand when that actually happened to which release, I have to look at the date13:55
ahasenackso me, personally, I tend to also add a task for the devel release in the bugs I work on, if I remember13:55
philrocheteward: Thanks. I have marked oracular invalid on https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929 and added reasoning why13:55
-ubottu:#ubuntu-devel- Launchpad bug 2062929 in livecd-rootfs (Ubuntu Mantic) "AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel" [Undecided, In Progress]13:55
tewardno i get it i'm just saying ahasenack13:55
tewardphilroche: ack no worries :)13:55
tewardjust doing Due Diligence with my bugcontrol buttons :p13:56
mirespaceHi, I would need a package review for sponsorship walinuxagent at14:03
mirespacelp:~mirespace/ubuntu/+source/walinuxagent:release-upgrade-oracular-devel (I have one approval already, but not from a packager)... thankyou14:03
mirespacebug is https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/206801914:04
-ubottu:#ubuntu-devel- Launchpad bug 2068019 in walinuxagent (Ubuntu) "Upgrade to v2.11.1.4 on Oracular (24.10)" [Undecided, In Progress]14:04
locutusofborgahasenack, what bothers me is that local pbuilder oracular env on armhf works :/14:08
ahasenacklocutusofborg: I actually reproduced the failure, what I pasted in the bug is from my local build on a raspberry pi14:08
ahasenackhost arm64, but armhd lxd container14:08
ahasenackI got a lot of "|| Unable to compile '<foo>' component14:09
ahasenackwhich then translates do the dh_install missing files error14:10
ahasenackmy poor pi4 took 49min to reach that error14:10
tewardddstreet: mapreri: fyi i uploaded to backports queue for my XCA bug requesting backport.  I can just handwave it but i want to get the normal process anyways done14:14
ahasenackphilroche: do you want 23.10.60 from mantic unapproved to go over what is in mantic-proposed (23.10.59)? The changes file implies so14:15
ahasenackthat was also a question from rbasak in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/comments/414:16
-ubottu:#ubuntu-devel- Launchpad bug 2062929 in livecd-rootfs (Ubuntu Mantic) "AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel" [Undecided, In Progress]14:16
loolPhilroche, ahasenack: thanks for the livecd-rootfs re-upload :) I had also forgotten to tag the new 2.765.44 release in git, I’ve done so with Phil’s latest changes, and pushed14:26
ahasenacklool: do you happen to know the answer to my question just above?14:26
ddstreetteward ack, reviewed and approved14:26
tewardddstreet: thank you kindly!14:26
loolahasenack: I don’t know about the mantic changes I’m afraid14:26
ahasenackphilroche: around? ^14:27
loolAnkush: ^ as well :)14:30
* ahasenack is drowning in the list of 10 bugs livecd-rootfs is tackling between jammy, mantic, noble, and oracular14:35
ahasenackhttps://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121 is also still open for oracular14:37
-ubottu:#ubuntu-devel- Launchpad bug 2061121 in livecd-rootfs (Ubuntu Oracular) "Mantic preseeding of LXD using incorrect track/channel" [Undecided, New]14:37
locutusofborgahasenack, RpcClient.class:112:13: error: Unknown identifier: XmlReader14:52
locutusofborgRpcServer.class:157:13: error: Unknown identifier: XmlWriter14:52
locutusofborgthis is the best clue I have14:52
ahasenackyeah, and I thought it was because the xml component failed to build14:52
ahasenackbut couldn't find an error there14:52
ahasenacker, rpc I mean14:52
ahasenackI don't know14:52
ahasenackcheck if libxml is a dep, and somehow it's missing/wrong in armhf?14:53
ahasenacklocutusofborg: well, just above that, it says14:53
ahasenackgbi3: warning: component not found: gb.xml.rpc14:54
ahasenackand before that it builds gb.xml14:54
locutusofborgwhy gcc-11 works?14:55
locutusofborgthis is what I can't understand14:55
ahasenackdoes it?14:55
ahasenackthe build with gcc-11 fails with that starts_with error from C++2014:56
ahasenackcan gcc-11 use -std=c++20?14:56
ahasenackmaybe that's what we need: stick to gcc-11, and make sure if gets that flag14:56
ahasenackif you check the build log which was still trying to use gcc-11, you see14:57
ahasenackgbi3: warning: component not found: gb.xml.rpc14:57
ahasenacker14:57
ahasenackchecking CXXFLAGS for gcc -std=c++11... no, obsolete14:57
ahasenackchecking CXXFLAGS for gcc -std=c++17... no, obsolete14:57
ahasenackchecking CXXFLAGS for gcc -std=c++20... no, obsolete14:57
ahasenackand then later, of course,14:59
ahasenackGooString.h:241:24: error: ‘starts_with’ has not been declared in ‘std::string’14:59
philrocheahasenack: RE https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121 and oracular. I have marked it as invalid as this is specific to the releases prior to Noble where preseeding of LXD was still supported so this unblockes mantic.14:59
-ubottu:#ubuntu-devel- Launchpad bug 2061121 in livecd-rootfs (Ubuntu Mantic) "Mantic preseeding of LXD using incorrect track/channel" [Undecided, Fix Committed]14:59
philrocheYes I am drowning in the bugs too :(14:59
* ahasenack entering barrage of meetings now, and then lunch14:59
bdrung@pilot out15:00
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: N/A
Ankushahasenack, lool RE: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929 As far as I understand the only reason the jammy approval should block on mantic approval is that the approvals must happen in the order of releases with later release being before an older release.15:30
-ubottu:#ubuntu-devel- Launchpad bug 2062929 in livecd-rootfs (Ubuntu Mantic) "AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel" [Undecided, In Progress]15:30
philrocheahasenack:  RE "do you want 23.10.60 from mantic unapproved to go over what is in mantic-proposed (23.10.59)? The changes file implies so that was also a question from rbasak in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/comments/4" Yes unless 23.10.59 can migrate now? Both bugs in 23.10.58 and  23.10.59 have been verified https://bugs.launchpad.net/cloud-images/+bug/2007419 and16:04
philrochehttps://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/206112116:04
-ubottu:#ubuntu-devel- Launchpad bug 2062929 in livecd-rootfs (Ubuntu Mantic) "AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel" [Undecided, In Progress]16:04
-ubottu:#ubuntu-devel- Launchpad bug 2007419 in livecd-rootfs (Ubuntu Mantic) "buildd daily kinetic, lunar, and mantic image missing systemd-resolved" [Undecided, Fix Committed]16:04
-ubottu:#ubuntu-devel- Launchpad bug 2061121 in livecd-rootfs (Ubuntu Mantic) "Mantic preseeding of LXD using incorrect track/channel" [Undecided, Fix Committed]16:04
kanashiro@pilot in17:39
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: kanashiro
philrocheahasenack: Thank you17:52
ahasenacko/17:52
ahasenackI'll look at unapproved again in a bit, just need to wait a bit for the lp machinery to run17:53
jbichadoko: do you have an estimate for when you'd try to switch Debian to gcc 14?18:29
ahasenackjbicha: thanks for sending those ftbfs fixes to debian, I had forgotten about that and mostly sent them to upstream when they weren't fixed there yet18:29
jbichaahasenack: thanks for the Ubuntu fixes, the Debian bugs allow me to put a bit more pressure later on if the fixes aren't applied18:30
ahasenackyep18:30
jbichaSalsa (& gitlab) is also annoying because it's not possible to tell if someone is subscribed to merge requests. I guess that's true for Debian bugs too for anyone not in the Maintainer field18:32
ahasenackright, salsa is hit or miss, whereas bugs are always the right choice18:32
=== dbungert1 is now known as dbungert
tewarddoes anyone know if https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2067523 is a debootstrap issue or a mk-sbuild (ubuntu-dev-tools) issue?  It's fairly important for those of us still building stuff against Debian (though I'm building an environment to address this that is Debian Unstable completely, it's still something that needs addressed, and is really a breakage in the tooling)18:50
-ubottu:#ubuntu-devel- Launchpad bug 2067523 in ubuntu-dev-tools (Ubuntu) "`mk-sbuild` on older Ubuntu versions like 22.04 are unable to build new Debian chroots" [Undecided, New]18:50
tewardwould there be any harm by me *backporting* debootstrap locally to see if that fixes the problem?18:57
teward(found if I backported debootstrap from Oracular to Jammy / Noble in my environment, it worked with Debian images.  Weird that sbuild exploded that way, but i guess it was the usrmerge stuff)19:20
ChmEarlteward my approach (using bookworm as builder) was to point pbuilder to mmdebstrap19:23
tewardChmEarl: i use sbuild not pbuilder19:23
ChmEarl in .pbuilderrc19:23
tewardbut you're right, i can use mmdebstrap in Debian for it19:24
teward(which is what my Unstable VM has)19:24
tewardbut i do a lot of crossbuilding19:24
tewardand ended up finding it was a debootstrap problem that I was able to fix19:24
teward(this isn't the first time i've had to backport debootstrap as a poweruser)19:24
ahasenackphilroche: Ankush: could any of you re-upload mantic's livecd-rootfs 23.10.60, as the one in unapproved currently also includes .59 and .58 which I released today? Otherwise, once I accept .60, it will add a comment to those already-fixed bugs again, and perhaps even flip them back to committed19:51
ahasenackif not, that's also fine, I can change the bugs manually after I think19:51
ahasenackn/m, I can fix that myself (the changes file)19:57
kanashiro@pilot out21:26
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: N/A

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