[10:05] <flag> LocutusOfBorg: https://launchpadlibrarian.net/740471663/bpftrace_0.21.0-1ubuntu6.debdiff
[10:05] <flag> LocutusOfBorg: this patch will remove two broken tests with 6.8 and 6.10
[10:06] <flag> with this applied, the package should finally pass autopkgtests
[10:06] <flag> LocutusOfBorg: can you upload it?
[11:18] <rbasak> @pilot in
=== 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: rbasak
[11:51] <LocutusOfBorg> flag, sure, but is export CI needed or not?
[12:00] <flag> LocutusOfBorg: some tests use it, so keept it
[12:00] <LocutusOfBorg> yeah, but is it effective?
[12:01] <LocutusOfBorg> I was wondering if it was wrongly exported
[12:01] <LocutusOfBorg> also, bpftrace needs a merge from sid now
[12:01] <flag> LocutusOfBorg: not sure if it works in autopkgtests since i run all tests manually (to see what's going on)
[12:02] <flag> LocutusOfBorg: before doing the merge from SID, please, do the upload of this one
[12:50] <LocutusOfBorg> flag, already done?
[12:54] <flag> LocutusOfBorg: what?
[12:55] <LocutusOfBorg> I have already uploaded your fixed package
[12:55] <flag> LocutusOfBorg: :O
[12:55] <LocutusOfBorg> and of course I wait for it before merging :)
[12:55] <flag> LocutusOfBorg: oh thanks, didn't notice that
[12:55]  * flag checks
=== blackboxsw_away is now known as blackboxsw
=== pushkarnk1 is now known as pushkarnk
[15:45] <mkukri> flag: i already had a patch on LP that fixes a test that seems to make it pass
[15:46] <mkukri> https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2073485
[15:46] -ubottu:#ubuntu-devel- Launchpad bug 2073485 in bpftrace (Ubuntu) "bpftrace autopkgtest failure" [Undecided, New]
[15:56] <rbasak> bdrung: could you review https://code.launchpad.net/~racb/ubuntu-sponsoring/+git/ubuntu-sponsoring/+merge/469860 please?
[15:57] <rbasak> Importantly, the sponsorship report is currently broken (last generated yesterday morning) and this (in addition to other things) fixes it.
[15:58] <bdrung> rbasak, i'll have a look after the dmb meeting
[15:58] <rbasak> Thanks!
[15:59] <bdrung> rbasak, nice: i see test cases in the MR
[16:06] <rbasak> !dmb-ping
[16:06] <ubottu> bdmurray, bdrung, rbasak, schopin, teward, tsimonq2, utkarsh2102: DMB ping
[16:06] <teward> rbasak: i'm here, had to reboot my internet though xD
[16:06] <teward> broken stuff is broke
[16:27] <rbasak> @pilot out
=== 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
[17:03] <ahasenack> enr0n: hey, I'm educating myself on ucf usage, and was looking at openssh. What are the 4 md5sums added for each package version in d/openssh-server.ucf-md5sum? One is the current sshd_config as shipped by the package, including all d/patches applied that might affect it, what are the other 3?
[17:16] <enr0n> ahasenack: the other three are for the possible combinations of changing the defaults of PermitRootLogin and PasswordAuthentication, because it is possible to change these with debconf
[17:17] <ahasenack> ah, ok, and I see the code to keep debconf and the config in sync
[17:19] <enr0n> yeah. And so with patches applied, you can basically generate the correct checksums with:
[17:19] <enr0n> cat sshd_config | md5sum
[17:19] <enr0n> cat sshd_config | sed 's/^#*PermitRootLogin .*/PermitRootLogin yes/' | md5sum
[17:19] <enr0n> cat sshd_config | sed 's/^#PasswordAuthentication .*/PasswordAuthentication no/' | md5sum
[17:19] <enr0n> cat sshd_config | sed 's/^#*PermitRootLogin .*/PermitRootLogin yes/' | sed 's/^#PasswordAuthentication .*/PasswordAuthentication no/' | md5sum
[17:23] <ahasenack> enr0n: and we don't want those changes (done via debconf) to trigger a ucf-conf prompt
[17:23] <enr0n> yeah exactly
[21:08] <mitchdz> Anyone taking a look at pydantic in -proposed? I'm planning on picking that up if no one else is :)
[22:01] <mitchdz> python3-defaults has a metric ton of autopkgtest armhf failures from the recent outage, do we have a good way to retrigger all the failed tests or should I go down the list retriggering each one?
[22:13] <jbicha> mitchdz: git clone https://git.launchpad.net/ubuntu-archive-tools
[22:14] <jbicha> ./retry-autopkgtest-regressions --help to see the syntax and suggestions on how to run. You'll want --blocks python3-defaults
[22:15] <mitchdz> wonderful, thanks :)