/srv/irclogs.ubuntu.com/2024/04/04/#ubuntu-devel.txt

=== pushkarnk1 is now known as pushkarnk
=== JanC_ is now known as JanC
jamespageMy local issue is entirely self inflicted (need to check what apt is going todo before confirming actions - not enough coffee) but noble-release pocket upgrade resulted in removal of quite a bit of Ubuntu desktop - I think it’s some missing amd64 builds for some gnome packages?08:52
wgrantjamespage: Things are still very much in flux because of the xz-utils mitigation rebuilds. ~8000 sources had amd64 binaries removed from the release pocket and rebuilds are making their way through proposed-migration.09:24
wgrantIt's very much not wise to full-upgrade atm, heh.09:25
wgrantThe last known-good versions of removed binaries are in noble-updates for the moment, if that's helpful.09:25
=== pitti is now known as pitti_
pitti_hello everyone, how are you? Long time no see!09:53
pitti_I'm scratching my head about the current archive state of noble -- is there a summary somewhere what's going on?09:53
pitti_(1)  cloud images are almost a month old, not quite "daily": https://cloud-images.ubuntu.com/daily/server/noble/09:53
pitti_(2) noble-updates has *older* versions than noble release, even though -updates isn't even supposed to have anything before the release; see e.g. https://launchpad.net/ubuntu/+source/openssh but I've seen it on a lot of packages09:54
pitti_i.e. none of the recent updates are actually visible in apt upgrade, it keeps installing the old version09:54
wgrantpitti_: This is part of the xz-utils backdoor mitigation. We removed several thousand recent amd64 sources' binaries, revived the known-good versions in noble-updates (because we needed a third pocket :)), and then started a bunch of no-change rebuilds through -proposed. They're still making their way back to the release pocket, so the release pocket is indeed missing a bunch of amd6409:56
wgrantbinaries.09:56
ogra_pitti_, https://discourse.ubuntu.com/t/xz-liblzma-security-update-post-2/4380109:56
ogra_(and moin !!)09:56
pitti_wgrant: Ah I see, thanks!09:57
pitti_ogra_: cheers! *hug*09:57
ogra_😄09:57
adrienand all that after t64, which is the reason for the initial delay10:01
adrienbut also the reason xz-utils remained in proposed (and hardly installable)10:01
adrienpitti_: also, hey, I would maybe have mailed you instead but I have a question specifically for you! have you used (authored?) sbuild->autopkgtest->LXD?10:03
pitti_adrien: I did write the autopkgtest lxd backend, yes (in a previous lifetime)10:04
pitti_nothing in sbuild though, but perhaps you mean britney10:05
adrienpitti_: ah, that's probably the bit that I was missing: I thought the whole thing had been done by a single person10:07
adrienman sbuild says "[--chroot‐mode=schroot|sudo|autopkgtest|unshare]"10:07
jamespagewgrant: that was my guess; I've unpicked my laptops mess by using proposed for the time being10:08
jamespageI shall avoid any further updates for now!10:08
adrienmy goal was to offload builds to another machine that way but it seems it's a *really* uncommon setup10:08
pitti_adrien: I'm afraid I've never seen that; isn't that more a case of just running sbuild *on* the remote machine?  But it's an interesting idea, as autopkgtest totally can build packages, and supports half a dozen backends (even podman these days); and lxd remote is cool10:10
adrienI'm not sure and I can't really tell if it was my understanding which was wrong or if the feature in sbuild is not working (it's documented as experimental): I was seeing sbuild trying to use schroot inside ephemeral lxd containers it created which doesn't make sense (they were created without setting up schroot and using them failed on schroot not being set up)10:14
adrienI probably need to talk to sbuild maintainers about that but I had thought you had used that based on one of your blog posts years ago10:15
=== pushkarnk1 is now known as pushkarnk
bdrung@pilot in12:42
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Feature Freeze | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: bdrung
=== pushkarnk1 is now known as pushkarnk
xypronThe time_t problems seem to persist: "libelf1t64 : Breaks: libelf1 (< 0.190-1.1build3) but 0.190-1 is to be installed" in Launchpad on armhf when trying to build u-boot.17:24
liushuyuI wonder if there is currently a patch pilot shift?18:19
john-cabajvorlon, it seems sbuild is also having trouble pulling the apt deb for noble, same as pbuilder.18:22
ginggsliushuyu: topic says bdrung, but he must have fallen asleep at the wheel18:39
ginggscalendar says kanashiro18:40
liushuyuginggs: sleeping behind the wheels is illegal in many territories though18:48
vorlonjohn-cabaj: yes, "things are in flux due to xz-utils"19:22
john-cabajack, will try back later and get by with a VM for now19:23
=== pushkarnk1 is now known as pushkarnk
kanashirosorry, it is me indeed, I will work on it now20:41
kanashiro@pilot in20:41
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Feature Freeze | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: bdrung, kanashiro
kanashiroliushuyu any specific request?20:43
liushuyukanashiro: https://code.launchpad.net/~liushuyu-011/ubuntu/+source/libcdio/+git/libcdio/+merge/463629 this one, for fixing time_t issues for armhf20:44
liushuyuIt's also blocking seeded packages20:44
=== jfsimon1981_c is now known as jfsimon
kanashiroliushuyu done21:06
liushuyukanashiro: Thanks!21:07
bdmurrayarraybolt3: Is the milestone regarding lubuntu-update-notifier in bug 1673258 still important?21:09
-ubottu:#ubuntu-devel- Bug 1673258 in lubuntu-update-notifier (Ubuntu) "Remove aptdaemon and drop or port its reverse-dependencies" [Medium, Confirmed] https://launchpad.net/bugs/167325821:09
kanashirodoko are you working on gcc-13? I am trying to sponsor some uploads to noble but I cannot build them due to unmet dependencies21:41
kanashirohttps://chat.debianbsb.org/file/3/YLYcMabgq74lDDR721:41
arraybolt3bdmurray: that's actually fixed in Noble and has been for a while22:03
arraybolt3I should mark it as Fixed Released.22:03
arraybolt3done22:04
arraybolt3s/Fixed/Fix/22:04
bdrungAttention! This is your captain speaking. I have got good news and bad news. The good news is we'll be landing immediately. The bad news is we are crash landing.23:37
bdrung@pilot out23:37
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Feature Freeze | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: kanashiro

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