[01:04] Is any core dev available to restart the autopkgtest for software-properties version 0.99.3.1 in groovy? [01:08] JawnSmith: Done [01:08] cjwatson: thanks! [01:08] np === didrocks999 is now known as didrocks === juergh_ is now known as juergh === cpaelzer_ is now known as cpaelzer [09:50] rbalint: it seems my questons in regard to systemd autopkgtest status didn't reach you yesterday [09:51] rbalint: since today everything looks as bad or worse I've filed bug 1915126 about it [09:51] bug 1915126 in systemd (Ubuntu) "autopkgtest times out (or fails before that) in hirsute" [High,New] https://launchpad.net/bugs/1915126 [09:51] that way you can pick it up whenever you are around and everyone else blocked by the same can chime in there [09:51] mfo: ^^ FYI [09:51] bryce: ^^ FYI === lucas_ is now known as Guest76680 [13:23] ddstreet, hey, I'm mostly curious but what is the moving behind https://code.launchpad.net/~ddstreet/software-properties/+git/software-properties/+merge/396926 ? there is no description or rational nor bug linked to the change [13:34] tjaalton, do you have any idea about the libxcb/s390x build failure? [13:34] https://launchpadlibrarian.net/521797278/buildlog_ubuntu-hirsute-s390x.libxcb_1.14-3_BUILDING.txt.gz [13:34] inlined from ‘parse_display_negative_fn’ at ../../tests/check_public.c:153:2: [13:34] ../../tests/check_public.c:82:3: error: ‘%s’ directive argument is null [-Werror=format-overflow=] [13:34] 82 | ck_assert_msg(!success, "unexpected parse success %sfor '%s'", test_string[test_type], name); [13:34] unsure why that would be arch specific... [13:36] and only on ubuntu [13:36] but no, I don't [13:38] :( [14:09] seb128 the author of the MR appears to have wanted to remove the python-requests-unixsocket dep from software-properties, and based on the project having no upstream commits in ~1.5 years it's probably good not to rely on it [14:10] ddstreet, it's confusing, the vcs and mp is from you? [14:12] seb128 this was his original mr https://code.launchpad.net/~slingamn/software-properties/+git/software-properties/+merge/389182 [14:12] then this one, but i preferred to simplify it more https://code.launchpad.net/~slingamn/software-properties/+git/software-properties/+merge/396880 [14:12] so i opened the final mr [14:13] ddstreet, ah, thanks, the reference was missing, that one has useful details [14:13] makes sense now! === didrocks999 is now known as didrocks [15:34] cpaelzer, thanks for the bug, i'm working on the next upload [15:45] thanks rbalint [15:45] if you have any further insight to it please dump it to th bug [15:45] I've already got two other that are potentially looking into it and have told them to look&past at the bug to sync on it [15:47] cpaelzer, do i understand correctly that the tests pass locally for you? [15:47] rbalint: indeed [15:48] systemd-fsckd PASS [15:48] yep [15:48] I have not redircted the log, but can pass you a copy&poaste of the console if you think it would help (I don't think so) [15:49] This is the command that workss for me "sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --testname=systemd-fsckd --shell systemd_247.1-4ubuntu1.dsc -- qemu --ram-size=1536 --cpus 1 ~/work/autopkgtest-hirsute-amd64.img" [15:49] cpaelzer, no, your word is enough :-) [15:49] I have not yet iterated on running all/more testcases an or CPU/memory capacity [15:50] cpaelzer, ack, giving a try to running it on big vms worth trying imo, i'm rebasing my MP @ https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/383953 [16:03] Laney, please give a try to making systemd big on amd64 : https://code.launchpad.net/~rbalint/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/397740 [16:03] cpaelzer, ^ [16:04] cpaelzer, as i see ppc64el got better today [16:07] yes rbalint, at least I got through two tests [16:08] on ppc64el that is [16:38] rbalint: I'll try it manually first, we'll see [16:39] Laney, thanks! [16:39] cpaelzer's sizes there are the sizes of the instances we use currently though and it passed [16:39] do you know why having a too small instances ends up with you in emergency mode? [17:13] doko: I updated bug 1915009 with the requirements for MIR, should I ping someone from the ~ubuntu-mir and security team for reviews or is this bug update enough? [17:14] bug 1915009 in libmd (Ubuntu) "[MIR] libmd (dependency of libbsd)" [High,Incomplete] https://launchpad.net/bugs/1915009 [17:15] I am asking about the pings because I was told by mclemenceau that this is somewhat urgent [17:21] thanks tdaitx for updating the ticket [17:47] this will sound a tad like a "why are you asking" question, but at what point did /run and /boot get mounted with 'nodev' options, and is there a way to make that happen on older systems? Asking on the older systems part because a vuln management system is whining about /run and /boot not being mounted with nodev. [17:47] mounted with nodev option by default* [19:20] teward: initramfs-tools, systemd built'in, fstab will try to mount those end points. [19:20] teward: if you want them with nodev, you should be able to set that in fstab; and do update-initramfs -u. [19:20] teward: then on boot it will be mounted without nodev option; but should then be remounted with it. [19:20] teward: if it doesn't it's a bug in ubuntu. [19:21] teward: more comonly people tweak the tmpfs size of /run. or like umask of /boot => so it's not that uncommon to customize those. [20:03] Laney, how did the manual test go? [20:04] vorlon, sil2100: TB meeting? [20:16] rbalint: I didn't do it yet, I've been busy with .0 stuff [21:09] rbasak: oops im late.. LP #1901344 reminder [21:09] Launchpad bug 1901344 in cinnamon-screensaver (Ubuntu Groovy) "[SRU] Spotify album icon shows optimal CD disk instead of album/cover image" [Low,In progress] https://launchpad.net/bugs/1901344 [23:13] hi everyone [23:16] doko: note for whenever you can read: since a short time ago, I have been getting some kde packages built with files with the wrong owner [23:16] for example: [23:17] https://launchpadlibrarian.net/522205798/buildlog_ubuntu-hirsute-amd64.kwayland-integration_4%3A5.20.90-0ubuntu1~ubuntu21.04~ppa2_BUILDING.txt.gz [23:17] -rw-r--r-- buildd/buildd 18984 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so [23:18] this file ↑ should be owned by root [23:19] I have the impression that the new libc6 & friends triggered this, but I have no solid evidence [23:19] this doesn't happen without -proposed [23:21] I have *temporarily* available here the results of a test rebuild of our kubuntu kde WIP packages: http://tritemio-groomlake.duckdns.org/build-status/buildstatus_ubuntu-exp3/ [23:21] they are several packages affected from kde applications [23:22] so if you can give me a hand with this I would appreciate it very much [23:22] in case it's not libc6 & friends fault, sorry for the noise :)