[00:34] nteodosio (oh you are gone): done [05:03] bluesabre: have left feedback on the two MPs I know about; looks like one more round should get us there. [05:03] bluesabre: and just found the livecd-rootfs mp which I had lost track of - looks correct, I'll go ahead and merge it [09:38] hi! \o [09:38] when I use [09:38] ./copy-package --include-binaries -s lunar --from 'ppa:zhsj/ubuntu/go1.20-rebuild' --to 'ubuntu' google-osconfig-agent [09:39] I get a "b'Not permitted to upload directly to lunar; try lunar-proposed instead.'" [09:39] however, when I use lunar-proposed as the above error mentions, I get "Could not find source 'google-osconfig-agent/None' in lunar-proposed". D'oh? [09:39] how do I work around this? [09:40] utkarsh2102: --from-suite lunar --to-suite lunar-proposed ? [09:41] aaah, there is --from-suite and --to-suite? [09:42] I see it now [09:42] zhsj: thanks! and done! \o/ [10:53] kanashiro[m]: hey! this might contain some relevant bits for you wrt. feature freeze (i.e. update to the new puma 6.x release). Maybe we can get this merged from Debian experimental or even go ahead to the very recent 6.1 upstream release? https://bugs.launchpad.net/ubuntu/+source/puma/+bug/2006461/comments/1 [10:53] -ubottu:#ubuntu-devel- Launchpad bug 2006461 in puma (Ubuntu) "[MIR] Promote puma to main as a pcs dependency" [Undecided, New] [11:14] slyon: I need to check whether rails version we have in the archive supports puma 6, I belive this is the reason why it is in experimental. Otherwise a bunch of rails related packages will be broken. But the merge with the latest version in unstable is something I can do [11:15] OK. If this is the case, please give it as reasoning on the MIR bug why we can't upgrade at this time [11:15] Sure, I will do that today [11:21] thanks. I thought it might be in experimental just for the soft freeze [11:24] Thanks amurray, I checked the logs :) [11:33] Can you please trigger this one? https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=arm64&package=chromium-browser&ppa=canonical-chromium-builds/stage&trigger=chromium-browser/110.0.5481.77-0ubuntu0.18.04.1 [12:00] bdmurray: hi, any news on autopkgtest upstream? we are very very close to the v253 release and we have had no testing coverage on ubuntu for a while now, which is scary, don't really want to introduce regressions [12:50] vorlon: thanks for the review! I applied the requested fixes. [12:50] nteodosio: done also [12:50] Thank you [17:05] bluesabre: first xubuntu-minimal test build failed with: [17:05] ===== Publishing ===== [17:05] Tue Feb 14 16:46:29 UTC 2023 [17:05] No desktop image for amd64! [17:05] No images produced! [17:05] bluesabre: so we clearly missed something. I'll dig in a little later [17:06] bluesabre: (the message comes from lib/cdimage/tree.py but I don't know offhand why it's expecting a desktop image) [17:07] ah, lib/cdimage/tree.py:Publisher.publish_type [17:10] vorlon: I'm sure you've seen by now the MPs I threw on your lap. [17:11] Eickmeyer[m]: yah [17:12] 👍️ [18:06] bluesabre: voilà https://cdimage.ubuntu.com/xubuntu/daily-live/current/lunar-minimal-amd64.iso [18:07] bluesabre: however the image is the same size as the desktop image because livecd-rootfs hasn't propagated yet ;D [18:07] I'll try a PROPOSED=1 build just to see, but no guarantees that lunar-proposed is buildable [18:19] bluesabre: yeah the PROPOSED=1 build failed [18:25] vorlon: I need clarification on edubuntu.seed. From what I understand, the extras.ubuntu.com lines (1 & 2) can be dropped, but I most certainly needs likes 3 & 4, correct? [18:29] s/needs likes/need lines [18:54] Eickmeyer[m]: they don't do anything. this is d-i preseeding; we don't use tasksel in ubiquity [18:57] vorlon: Ok, so pretty much remove the ubiquity line then? [18:59] I'm mostly using the most recently updated .seed file (xubuntu) as an example. [18:59] Eickmeyer[m]: I'm saying there's nothing in that current preseed file which will do anything for a modern image; the only line that might is the ubiquity line but only if it's needed for pointing at currently-existing packages present on the live image [19:02] vorlon: If that's the case then I'll remove everything except the ubiquity line for now, as we may go with the new installer. It also seems to me like every other .seed file in the preseeds is mostly cruft at this point. [19:28] Hi, [19:28] Would it be possible to retry https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=entr&trigger=vim%2F2%3A9.0.1000-4ubuntu2 [19:28] (failed with Cannot initiate the connection to us.ports.ubuntu.com:80) [19:28] and https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=entr&trigger=vim%2F2%3A9.0.1000-4ubuntu2 [19:28] (tests pass locally) [19:32] vpa1977: Whend did that test fail to connect to us.ports.ubuntu.com? Can I see the log? [19:33] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/arm64/e/entr/20230206_121627_6a5da@/log.gz [19:33] Feb 6 [20:57] vorlon: Did you see https://code.launchpad.net/~edubuntu-dev/livecd-rootfs/+git/livecd-rootfs/+merge/437174 ? [21:00] Eickmeyer[m]: hadn't looked at it yet but was going there next [21:08] vorlon: 👍️ [21:27] bdmurray: I think they were restarted since then, but just silently died, so that the last available log