So, anyone else experienced this?Damn, you're right: http://deb.torproject.org/torproject.org/dists/tor-nightly-main-bullseye/InRelease Suite: tor-nightly-main-bullseye Codename: tor-nightly-main-bullseye Date: Fri, 09 Feb 2024 11:28:02 UTC Valid-Until: Wed, 20 Mar 2024 11:28:02 UTC root@boldsuck:~# apt update root@boldsuck:~# apt-cache show tor Package: tor Version: 0.4.9.0-alpha-dev-20230909T020422Z-1~d12.bookworm+1 So I also have the last version from September 9th, 2023, although one from February 9th, 2024 is in the archive. :-( Tor stable update is OK. Full log output: https://paste.debian.net/1307420/
Yes, and it's not an isolated case.Absolutely all relays and bridges are I have are in the same situation. Most probably a lot of users are in the same situation (that run on nightly) and they don't even know, given apt does not complain at all. Debian is our largest user base IIRC.
My guess is that something changed with more recent releases of Debian (Bullseye and Bookworm) because in previous Buster this was not happening, even it was the same version number in nightly, like 4.8.0-aplha-dev, if would update if same version was found but with newer timestamp.
Running on nightly has been important for me, to detect bugs and submit test reports to people that work on patches.
I will try to investigate more, again, but from the apt logs it looks like everything is nice and fine - except it ignores the newer package in deb.tpo with newer timestamp...
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays