Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
/rb-pkg/sid/
|
|
/dbd/sid/amd64
|
|
/buildinfo/sid/amd64
|
|
/rbuild/sid/amd64
|
|
the time it takes to ftbfs once) and save it in reproducible.db
|
|
reproducible_common.sh
|
|
This reverts commit 1891874d1866a9831de50f6e313de66f54fa47cc.
|
|
This reverts commit dfbc1df3a497beb9d156832d32f5420e254a7731.
|
|
|
|
|
|
not checked anymore
|
|
|
|
|
|
sources.lists
|
|
mess...
|
|
and the schroot accordingly, to jenkins-reproducible-sid-debbindiff
|
|
|
|
|
|
suites. yet hardcode suite in the file
|
|
|
|
|
|
|
|
|
|
|
|
This makes it not wrap onto a newline on my rather low-resolution laptop.
The URL is more than sufficient I feel; it's kinda implicit that its a
request for someone to do something anyway - why would we be reporting it
to IRC otherwise, etc.
Signed-off-by: Chris Lamb <lamby@debian.org>
|
|
|
|
comparing two builds
|
|
|
|
|
|
|
|
reproducibly in the past becomes unreproducible
|
|
|
|
It can happen that the first build was successful, but the second build
not (e.g. because of failing tests, which has already been observed).
In this case, the whole build has to be marked FTBFS and debbindiff
doesn't need to be called.
|
|
|
|
|
|
|
|
|
|
|
|
outwhich which debbindiff version is used
|
|
/userContent where possible
|
|
|
|
to timeout
|
|
|
|
debbindiff run also exited successfully...
|
|
|
|
else downloading of 0ad* sources fails...
|
|
sourced after common-functions...
|
|
This reverts commit bbc7e44fd215538aff947c652235305c88474fbf.
|