Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL So 02.06.2024 00:00:07 61.862 0 3.431.311 55,5 Fosstodon 4.2.9 500 Sa 01.06.2024 00:00:16 61.862 +2 3.429.149 55,4 Fosstodon 4.2.9 500 Fr 31.05.2024 00:00:10 61.860 +1 3.425.635 55,4 Fosstodon 4.2.9 500 Do 30.05.2024 00:00:06 61.859 +2 3.422.265 55,3 Fosstodon 4.2.8 500 Mi 29.05.2024 00:00:07 61.857 +1 3.419.439 55,3 Fosstodon 4.2.8 500 Di 28.05.2024 00:00:11 61.856 +5 3.416.643 55,2 Fosstodon 4.2.8 500 Mo 27.05.2024 00:00:09 61.851 +1 3.413.281 55,2 Fosstodon 4.2.8 500 So 26.05.2024 00:00:08 61.850 -1 3.410.443 55,1 Fosstodon 4.2.8 500 Sa 25.05.2024 00:00:09 61.851 +2 3.407.482 55,1 Fosstodon 4.2.8 500 Fr 24.05.2024 00:00:07 61.849 0 3.404.186 55,0 Fosstodon 4.2.8 500
Klaus Zimmermann :unverified: (@kzimmermann) · 10/2020 · Tröts: 6.862 · Folger: 1.097
So 02.06.2024 18:20
So I think I finally found out why in one of my #Devuan #Unstable installs #apt fails to check signatures of packages (or so I hope).
It seems that apt's sig checking function is outsourced to the gpgv (not gpg) program, whose restricted usage is solely to check signatures. In the "broken" 2.2.40 version, apt passes some invalid command-line argumments resulting in failure. But in v2.2.43 this doesn't happen anymore. Not sure if this is surely the cause, but it's getting warmer.
[Öffentlich] Antw.: 0 Wtrl.: 1 Fav.: 1 · via tut-tui