15:02 #startmeeting Weekly Ubuntu Foundations team 15:02 Meeting started at 15:02:36 UTC. The chair is juliank. Information about MeetBot at https://wiki.ubuntu.com/meetingology 15:02 Available commands: action, commands, idea, info, link, nick 15:02 #topic Lightning rounds 15:02 #link https://discourse.ubuntu.com/t/foundations-team-updates-thursday-2024-08-08/ 15:03 o/ 15:04 seems like a meeting topic made its way to the channel topic lol 15:05 o/ 15:05 Fixing topic shortly 15:06 bdrung: Where did you run your "archive query"? 15:06 bdmurray, Code and resulting database can be found on https://github.com/bdrung/bdrung-scripts/tree/lp-2075337-find-affected 15:07 bdmurray, the test is run in a schroot container 15:07 bdrung: but you ran it in your "office"? 15:07 I just wonder if there is a better spot closer to a mirror / the archive to do queries like that 15:08 bdmurray, the package installation is where the most time is spent (not the dowloading the packages) 15:09 bdmurray, "select avg(install_duration) from package_affected;" gives me 2.75078125768356 (seconds) 15:09 bdrung: okay 15:10 it is running on my desktop with an apt-cache-ng in between + all writes on tmpfs overlays 15:12 alright moving on 15:13 #topic Release incoming bugs 15:13 >#link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-oo-incoming-bug-tasks.html#foundations-bugs 15:13 #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-oo-incoming-bug-tasks.html#foundations-bugs 15:13 Now I don't quite know why bpftrace is showing up as unknown 15:13 but 15:13 bug 2069953 15:13 I filed it and forgot about it? 15:15 foundations-bugs is subscribed to the bpftrace package so it must be something with the reporting code 15:15 the ones filed by Adrien are probably ours too. 15:16 He tagged them. 15:16 So well yes libtracefs is also foundation-bugs 15:16 I guess the script did not pick up new subscribers since a while? 15:17 where does the code for the script live? 15:17 bdmurray: ^ 15:18 https://code.launchpad.net/~arsenal-devel/arsenal/2.x 15:18 Oh wow. I would never have guessed that one :) 15:18 The others are bug 2062118 and bug 2062119 15:19 I guess we can take them all but also Adrien is out this month 15:19 He tagged them back in April, I think we just never noticed until now? 15:20 Well yes 15:20 But I guess he could fix them in September too 15:20 these were followup from the MIR 15:21 Anyway, I say add them to the backlog and let adrien follow up on them :) 15:21 I'll todo all three 15:22 #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-nn-incoming-bug-tasks.html#foundations-bugs 15:22 bug 2075968 15:23 This sounds awkward but also not reproducible 15:24 It does seem _somehow_ the password was deleted for the user 15:25 I can consistently reproduce this 15:25 is it through pam or passwd? 15:26 OK; then I guess can take this for further investigation 15:26 I guess we need to simply do a diff after the upgrade of a "broken vs after-passwd" and see what changed 15:26 schopin: I think it's pam because it happens on graphical login, non-graphical, or attempting to use passwd to reset the password 15:26 And see if shadow file changed between upgrade 15:27 Sadly ugh this will fall on enr0n I guess 15:27 or we do "pair reproducing" 15:27 I can try the "check if there is a diff" option. 15:28 I don 15:28 bug 2075969 15:28 I don't necessarily have time to try on a bunch of flavors. Help appreciated there 15:29 This seems like a bunch of effort to get right vs requiring multiple upgrades on old-releases IMO 15:29 this should say "to noble" 15:30 We'd need to do like upgrade tests for full desktop installs too 15:30 Our intent for years has been this upgrade path to work. 15:30 i.e. from K to N 15:31 or e.g. 15:31 So we need to restore the files from interim releases, then merge in any changes needed from .jammy/.mantic 15:31 And AFAIK there no issue with the interim releases between B and F 15:32 We can fix this but that's for after the point release I'd say 15:32 So I am going to tag it todo, this can be done next pulse 15:33 #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-jj-incoming-bug-tasks.html#foundations-bugs 15:33 empty 15:33 #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html#foundations-bugs 15:33 empty 15:33 #topic Team proposed-migration report 15:34 #link https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses_by_team.html#foundations-bugs 15:34 ooh 15:35 py-openssl is with adrien but he's out the entire month, we probably should reassign it? 15:35 it is with anderson123 now 15:36 Where is that tracked? 15:36 The JIRA still says Adrien 15:36 *andersson123 15:36 there is an MP from andersson123 linked to update-excuse bug 15:36 I see 15:36 Well I'll reassign the jira 15:37 rust-defaults vs rustc is with dv 15:37 * dviererbe 15:38 glibc blocking linux-meta with schopin 15:38 it seems usbmuxd is unassigned 15:38 Ah it waits for a dependency 15:39 OK but that one needs an mir, so let just assign it, it requires checking with desktop on the MIR process or whatnot 15:39 patches for the regression packages for golang-defaults/1.23 are on the way, no need to assign currently. 15:40 usbmuxd depends on libimobiledevice: mwhudson - quick check with desktop perhaps what's up with libmobiledevice 15:41 initramfs-tools blocking iproute2: bdrung probably wants this, but I'd be happy to assign to paride too 15:42 juliank, this should resolve itself. i just retrigged the tests against the fixed initramfs-tools/0.142ubuntu31 15:42 ok 15:42 ack, thanks bdrung 15:42 nvme-cli ftbfs paride 15:42 libxs-parse-keyword-perl remains with waveform 15:43 adduser vs show remains with tobhe 15:43 ack 15:43 It seems we did not assign shadow vs itself 15:43 i was assuming that's also with me 15:44 ack 15:44 I'll update the jira ticket 15:45 apt blocking systemd: juliank 15:45 Weird apt test suite failures 15:46 openssh blocking systemd I'll leave with enr0n 15:46 s/leave with/assign to/ :) 15:46 juliank: ack 15:46 boost1.83 15:47 I think doing a blanket assign there 15:47 tobhe: on the shadow thing ping me if you need a hand, I sponsored the merge 15:47 juliank: I can take boost 15:47 ok, thx! The adduser fallout is pretty obvious 15:48 boost1.83: schopin 15:48 ok if you want too 15:48 it seems badpkg 15:48 xfsdump: liushuyu 15:49 libheif: andersson123 15:49 zlib: doko? 15:50 I mean he uploaded it 15:50 juliank: andersson123 already has pyopenssl 15:50 cmake is with vpa1977 15:50 ginggs: yes we sorted that out a while ago 15:51 golang-defaults is in progress and zhsj doesn't want it assigned 15:51 juliank: so he gets libheif as well? 15:51 ginggs: ah I see 15:51 libheif: chrisccoulson_ 15:51 #topic AOB 15:52 I'll be off tomorrow 15:52 bdmurray, juliank: bug 2058648 is going back in the milestone after all 15:52 i'll be on vacation next week 15:53 enr0n: +1 15:53 Ah good we're playing Rush now 15:54 I'll refill my water and brb 15:54 I could use some help with https://code.launchpad.net/~tobhe/ubuntu-seeds/+git/ubuntu-seeds/+merge/470886 if any core dev has a few spare minutes ;) 15:56 Oh I don't know the differences that c paelzer pointed out so I'd want mwhudson to take a look at that 15:57 COVID update: It was like a solid black line on Tuesday on the self-test but it's barely visible now; all tests are same batch 15:57 juliank: if you want an easier one I also have https://code.launchpad.net/~tobhe/ubuntu-seeds/+git/ubuntu-seeds/+merge/467849 15:58 tobhe: Does this need the other one, though? 15:58 no 15:58 Did you already add a metapackage in another seed? 15:58 no 15:58 So we can't merge that, because it will break stuff? 15:59 It says they should be pulled in by a meta package where needed, so that should be done some way 15:59 I think we can. It won't remove anything on working installations right? 15:59 it isn't enough to make the machine work anyway 15:59 the packages will become auto-removable 16:00 they will be removed on release ugprades 16:00 Anyway we can continue this on the merge 16:00 #endmeeting