[00:01] <mwhudson> er hm
[00:01] <mwhudson> i hope nothing dynamically links to /usr/lib/x86_64-linux-gnu/libSegFault.so
[00:02] <mwhudson> sarnold: can you do searches of binaries too?
[00:02] <sarnold> mwhudson: I think so, I'll have to re-read jamie's notes :)
[00:04] <bdmurray> mwhudson: I see some new ubiquity / glibc test failues for focal. I'll have a look at those.
[00:05] <mwhudson> bdmurray: oh thanks
[00:06] <mwhudson> well nothing on my system seems to link to libSegFault.so at least
[00:07] <mwhudson> sarnold: yea so if you can scan for ELF binaries with a DT_NEEDED of libSegFault.so that would be reassuring
[00:12] <sarnold> mwhudson: sweet; I started one with just a search for libSegFault and found a few SONAME entries -- so I'm hopeful if there's DT_NEEDED entries, they'll show up
[00:13] <mwhudson> sarnold: great
[01:33] <mwhudson> vorlon or anyone else, want to do a really boring package review? https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=glibc-tools
[01:41] <vorlon> sorry I'm already doing a really boring bisect of botan test cases
[02:51] <mwhudson> vorlon: it's ok i was learning minutae about locale definitions
[02:51] <mwhudson> https://sourceware.org/pipermail/libc-alpha/2022-January/135703.html
[07:58] <slyon> vorlon: from what I found, it is not using RFC 5227 via networkd but rather the arping standalone tool is being called during ifup (https://support.hpe.com/hpesc/public/docDisplay?docId=kc0125971en_us)
[09:00] <schopin> Do we have some usage data similar to popcon in Ubuntu?
[09:12] <tuxinator> Hi everybody, is there any best-practice to keep older packages available (for downgrade of fixed version= install) in a Repo under our own control=
[09:12] <tuxinator> ?
[11:05] <schopin> Looking for a sponsor for LP: #1959095 to hopefully unblock the src:breezy situation :)
[12:02] <slyon> schopin: looking
[12:02] <schopin> thanks!
[12:14] <schopin> slyon: just seen your rejected upload. The archive has an orig.tar.xz whereas your upload refers to a orig.tar.gz, I'm curious as to what happened there?
[12:15] <schopin> (thanks for the sponsoring btw :) )
[12:16] <slyon> Ups, will redo after lunch. I was using "uscan --download-curren-version" to get the orig tarball, so maybe debian/watch is wrong :)
[12:17] <schopin> Huh. I didn't know this could even happen!
[13:04] <slyon> schopin: done
[13:32] <ogayot> hello! I am looking for a sponsor for a sysvinit merge in Jammy: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1958666 Thanks!
[14:10] <tuxinator>  Hi everybody, is there any best-practice to keep older packages available (for downgrade of fixed version= install) in a Repo under our own control?
[14:12] <rbasak> tuxinator: this channel is for the development of Ubuntu itself. Try #ubuntu for support.
[14:13] <rbasak> You might have better luck getting an answer for that on somewhere like askubuntu.com though.
[14:17] <rbasak> cpaelzer: do you realise that https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953338 still has its Focal task Incomplete? But there's an upload in the queue.
[14:18] <rbasak> Which is correct?
[14:18] <rbasak> And should that be block-proposed-focal rather than block-proposed?
[14:20] <rbasak> I think the bug is also missing an explanation of the user story that is failing, and the test plan should really be testing that story rather than something intermediate.
[14:20] <cpaelzer> rbasak: the upload is right
[14:21] <cpaelzer> I forgto to set the status in in progress when they provided the good backports a few days ago
[14:21] <cpaelzer> I liked the explanation that frank added, but I can add another/differnt user story as well
[14:21] <cpaelzer> *adding* ...
[14:27] <cpaelzer> rbasak: last section in the [impact] section holds the user-story that you might have been looking for
[14:27] <cpaelzer> let me know if that is better now
[15:21] <tuxinator> rbasak: well as its a question about best practice on how to maintain a repository i thought dev matches better
[15:21] <tuxinator> :D
[15:29] <vorlon> slyon: does this (IP collision detection) seem like something you think we should support in netplan?
[15:32] <slyon> vorlon: yes, it sounds like a nice feature and we should at least enable the existing RFC 5227 detection in networkd (maybe something similar in NetworkManager). I already created a 'RoadmapIdea' card for that.
[16:21] <vorlon> slyon: ok cheers.  should we open a public bug for tracking also and point the askubuntu question to it?
[16:23] <slyon> sure, I can do that!
[18:03] <dbungert> retest click please?  https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=ppc64el&package=ruby-sqlite3&trigger=ruby3.0/3.0.2-7&trigger=sqlite3/3.37.2-2&trigger=ruby-sqlite3/1.4.2-3ubuntu1
[18:09] <bdmurray> dbungert: done
[18:09] <dbungert> bdmurray: thanks!
[23:40] <bdmurray> I forget is there a tool to search autopkgtest logs for a certain failure string?