=== kostkon_ is now known as kostkon
=== chris14_ is now known as chris14
ChmEarlneovim checkhealth in Jammy: https://pb.dynavirt.com/view/raw/e48b889806:24
ghavilWould there be any accurate way to figure out when the systemd 249.11-0ubuntu3.7 package would have been pushed & visible in the security repositories? I'm trying to figure out a timeline with unattended-upgrades 17:34
andolghavil: I think you can get a reasonable good timeline by either looking at the https://launchpad.net/ubuntu/+source/systemd published dates or the http://security.ubuntu.com/ubuntu/pool/main/s/systemd/ "Last modified" info17:42
ghavilAh good point, so maybe around "2023-03-07 06:54" (I assume that's UTC) 17:43
ghavilI think that'll work for now, thanks!17:43
andolI wouldn't rely to heavily on the exact time, since the mtime could possibly have been orginated on some other server, and simply propated by rsync preserving that info.17:45
ghavilYeah, makes sense 17:59
sdezielghavil: `/var/log/apt/history.log` contains information around install time21:47
ghavilThanks, yeah I've got that. I'm trying to figure out why some hosts didn't see the package when they ran their unattended-upgrades so, knowing when it was published is what I'm after. 21:48
sdezielghavil: you can potentially check the Last modified time on your archive mirror like this random example: http://us.archive.ubuntu.com/ubuntu/pool/main/a/a11y-profile-manager/22:35
ghavilYeah, that's what andol mentioned earlier. Since it was a security update, I think http://security.ubuntu.com/ubuntu/pool/main/s/systemd/ (systemd_249.11-0ubuntu3.7_amd64.deb) is the right place to check so, ~2023-03-07 06:54. Although andol pointed out that might be the timestamp of when it was created if rsync preserved the mtime on the file. 22:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!