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
|
|
cpu type
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the same number of packages
|
|
|
|
|
|
|
|
The _supported variant uses the cross build method preferred by the gcc
maintainer. It relies on dpkg-cross instead of cross-gcc-dev. Adding
this variant, as it is not clear which one is to be used in the long
run. See: #766708
The _debbindiff variant compares the cross-built packages against their
in-archive natively-built counterparts. This processing takes
significantly longer, but can highlight errors in cross compilation.
This commit triples the number of rebootstrap jobs.
|
|
|
|
powerpcspe has no multilib, so it should be exactly the same as
rebootstrap_powerpcspe_gcc49.
|
|
Lunar for the initial patch!
|
|
|
|
|
|
|
|
+ signs
|
|
|
|
|
|
anymore
|
|
|
|
|
|
|
|
|
|
number to /rb-pkg/* heads
|
|
|
|
|
|
|
|
|
|
|
|
build creates it nowadays)
|
|
|
|
|
|
|