Bug #16297
Different DEBIAN_SERIAL value in buster
0%
Description
Different DEBIAN_SERIAL
serial which results in:
│ ├── /etc/apt/sources.list.d/torproject.list
│ │ @@ -1 +1 @@
│ │ -deb http://time-based.snapshots.deb.tails.boum.org/torproject/2019010501 buster main
│ │ +deb http://time-based.snapshots.deb.tails.boum.org/torproject/2019010502 buster main
This is generated in ./auto/scripts/apt-snapshots-serials
… but I think this is a false-positive; ie. someone uploaded something to Debian / snapshots?
It’s probably just installing something entirely different too and I’m just not grokking the build system right now.
Subtasks
History
#1 Updated by lamby 2019-01-05 16:33:44
- blocked by
Feature #16285: feature/buster branch is not reproducible added
#2 Updated by lamby 2019-01-05 16:34:47
- QA Check set to Dev Needed
#3 Updated by intrigeri 2019-01-05 16:57:51
feature/buster does not use a frozen set of APT snapshots at the moment: it uses the latest snapshot for each repo (debian, debian-security, torproject) and we update the 4 times a day. So what you’ve seen is expected. But on Bug #15107 I’ve done the work needed so one can force a rebuild to use the same set of snapshots as the original build and once that branch is reviewed and merged, it’ll magically happen this way on Jenkins so this sort of problems will only happen when rebuilding manually, without using this new functionality.
=> closing as there’s nothing Buster-specific here and a solution for the underlying generic problem is waiting for QA elsewhere :)
#4 Updated by intrigeri 2019-01-05 16:57:57
- blocks deleted (
)Feature #16285: feature/buster branch is not reproducible
#5 Updated by intrigeri 2019-01-05 16:58:53
- Status changed from New to Rejected
- Assignee deleted (
lamby) - QA Check deleted (
Dev Needed)