[05:44] <knaccc> hey all, I am trying to figure out if it's possible to tell which unattentded-upgrades packages require a reboot. I can monitor for the existence of the /var/run/reboot-required file, and I can scan the OVAL XML feed to see which CVEs have a severity of high, but I can't tell which fixes will only be in place if there is a reboot. It would be nice to be able to check whether I can benefit
[05:44] <knaccc> from a reboot before taking the server down temporarily.
[06:17] <cpaelzer> good morning
[06:19] <utkarsh2102> o/
[06:19] <cpaelzer> knaccc: while /var/run/reboot-required is the yes/no there also is /var/run/reboot-required.pkgs
[06:19] <cpaelzer> knaccc: that would tell you which packages triggered it
[06:19] <cpaelzer> knaccc: so you might not know the individual file, but at least the individual packages
[06:20] <cpaelzer> and well, dpkg -L $pkg for this list of packages would then even give you the list of files
[06:20] <cpaelzer> knaccc: is that what you were looking for?
[06:20] <knaccc> cpaelzer perfect, thank you! i can cross-reference that against the CVEs and then figure out if i need the reboot
[06:31] <kenyon> I'd say only kernels and libc need reboots, almost everything else you can restart, and `checkrestart` from the debian-goodies package tells you what needs a restart
[06:42] <knaccc> kenyon wow, that's really great, thanks!
[06:45] <cpaelzer> and in addition to checkrestart there is needrestart (which some prefer others don't)
[06:45] <cpaelzer> the latter even is default to infom you after an upgrade in more recent releases
[06:50] <knaccc> oh wow, and it has a nice gui
[06:58] <cpaelzer> it does, but it an also be used non interactively if needed
[07:05] <cpaelzer> bryceh: You seem to have hit this on triage. FYI this is a common issue on indep build depends on non x86  https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1960592
[07:14] <bryceh> @cpaelzer, ok well I leave qemu expertise to you :-)
[08:19] <mirespace_> good morning
[12:03] <athos> good morning :)
[14:04] <athos> sergiodj: all OCI builds are now complete. I am tagging the images now
[14:15] <ahasenack> athos: iirc you need sponsoring for bind9?
[14:29] <athos> ahasenack: yes, I will; bind9 is not under https://people.canonical.com/~ubuntu-archive/packagesets/jammy/ubuntu-server
[14:29] <ahasenack> k
[14:29] <ahasenack> athos: ok to sponsor then? Anything else to do?
[14:29] <ahasenack> (from your side)
[14:30] <athos> ahasenack: yes, please (nothing from my side)
[14:30] <ahasenack> ok
[14:54] <ahasenack> mdeslaur: hi, wondering how you generated the dfsg tarball for your samba cve updates, when you went ahead of debian
[14:54] <ahasenack> 2:4.13.17~dfsg-0ubuntu1
[14:54] <ahasenack> gbp? uscan? manually?
[14:54] <ahasenack> it's 3 exclusions: 'source4/heimdal/lib/wind/rfc*txt', 'source4/ldap_server/devdocs', '*chm',
[14:56] <mdeslaur> ahasenack: I did it manually, those three exclusions, is there anything wrong with it?
[14:56] <ahasenack> nope
[14:56] <ahasenack> it's just I'm going to do it again (4.15.5) :)
[14:57] <mdeslaur> oh, sweet :)
[14:57] <ahasenack> uscan almost gets it, but it doesn't know about '*.chm'
[14:57] <ahasenack> since it's not in debian/copyright
[14:57] <ahasenack> (Files-Excluded)
[14:57] <ahasenack> not even sure it can be there, without a path
[15:00] <mdeslaur> yeah, I tried a couple of things, and lost patience and just removed the files by hand
[15:01] <ahasenack> nice ~dfsg trick (instead of +dfsg)
[15:01] <orndorffgrant> rbasak: Hi I know you're +1 maintenance so you don't need to prioritize this this week, but I wanted to make sure you saw my request for your review on https://github.com/canonical/ubuntu-advantage-client/pull/1930 :)
[15:01] <ahasenack> I hadn't thought of that in the previous times I had to do repacking
[15:02] <mdeslaur> yeah! I just thought about doing that recently
[15:02] <mdeslaur> and nothing in debian/rules or anywhere else was trying to parse the version
[15:02] <rbasak> orndorffgrant: yes, and I was hoping to get to it this week only +1 maintenance :-/
[15:02] <rbasak> Sorry
[15:03] <orndorffgrant> All good!
[15:04] <ahasenack> Successfully repacked ../samba-4.15.5.tar.gz as ../samba_4.15.5~dfsg.orig.tar.xz, deleting 39 files from it.
[15:04] <ahasenack> might have worked
[15:04] <ahasenack> (uscan)
[15:04] <ahasenack> but need to check *.chm
[15:04] <ahasenack> oh, and it missed the "1"
[15:04] <ahasenack> dfsg1
[15:04] <ahasenack> hmpf
[15:04] <ahasenack> ok, lunch time
[15:37] <sergiodj> athos: thanks
[16:27] <bryceh> lena, btw iirc there's code in the mysql packaging that munges obsolete conf values.  I never tinkered with that but my guess is that'd be the solution for that bug with ancient config params.  I recall seeing other bugs like that in the past, but presumably they've either been fixed or expired.
[16:41] <lena> bryceh: yeah rbasak showed it to me, thanks! I'll look into expire-logs-days and see if it should be added alongside query_cache_limit
[18:12] <utkarsh2102> uh, I added a patch to fix this. :)
[18:37] <athos> j/33
[18:37] <athos> :|
[21:07] <ahasenack> rbasak: hi, git-ubuntu just "exploded" a little in jammy for me (granted, git-ubuntu.recontruct-changelog): https://pastebin.ubuntu.com/p/KT8Fr55GF2/
[21:07] <ahasenack> fyi
[21:07] <ahasenack> I have proposed enabled, I'm guessing it's related to the perl transition
[21:15] <rbasak> ahasenack: that's odd. I wonder if it's using your system's Perl instead of the one inside the snap.
[21:17] <ahasenack> rbasak: I have perl-base 5.34.0-3ubuntu1, which is the proposed one
[21:17] <ahasenack> jammy release has 5.32.1-3ubuntu3
[21:17] <ahasenack> must be it