post-2.6 stable uses now expired 2016091902 APT snapshot
Originally created by @anonym on #11851 (Redmine)
From a build of a branch based on
stable
:
09:14:44 Get:1 http://time-based.snapshots.deb.tails.boum.org jessie InRelease [7650 B]
09:14:44 Get:2 http://deb.tails.boum.org stable InRelease [9675 B]
09:14:44 Get:3 http://time-based.snapshots.deb.tails.boum.org jessie/updates InRelease [7597 B]
09:14:44 Get:4 http://time-based.snapshots.deb.tails.boum.org jessie-backports InRelease [7625 B]
09:14:44 Get:5 http://time-based.snapshots.deb.tails.boum.org sid InRelease [7653 B]
09:14:44 Get:6 http://time-based.snapshots.deb.tails.boum.org stretch InRelease [7655 B]
09:14:44 Get:7 http://time-based.snapshots.deb.tails.boum.org obfs4proxy InRelease [2522 B]
09:14:44 Get:8 http://time-based.snapshots.deb.tails.boum.org jessie InRelease [2520 B]
09:14:44 Get:9 http://time-based.snapshots.deb.tails.boum.org sid InRelease [2520 B]
09:14:45 E: Release file for http://time-based.snapshots.deb.tails.boum.org/debian/2016091902/dists/jessie/InRelease is expired (invalid since 2h 29min 19s). Updates for this repository will not be applied.
09:14:45 P: Begin unmounting filesystems...
09:14:45
Indeed, when I made the new snapshot late in the Tails 2.6 release process, I am sure I forgot to extend its expiry. Since this was a “creative” solution not part of the normal release process, I don’t think more documentation can help prevent this in the future.
What to do? Can we recreate it? Should I pick today’s snapshot? The first one after 2016091902 that still hasn’t expired?