Age | Commit message (Collapse) | Author | Files | Lines |
|
step once
|
|
|
|
|
|
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.
|
|
|
|
|
|
for all debian-edu live images
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the same number of packages
|
|
|
|
|
|
|
|
|
|
|
|
+ signs
|
|
|
|
anymore
|
|
|
|
|
|
|
|
|
|
number to /rb-pkg/* heads
|
|
|
|
|
|
|
|
|
|
build creates it nowadays)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
html_foot_page_buildinfo_note template
|
|
|
|
|
|
|
|
linking icon <-> status
|
|
|
|
|
|
|
|
|
|
outwhich which debbindiff version is used
|