Control: severity -1 important
On Sat, Aug 5, 2017 at 3:44 PM, Adrian Bunk <b...@debian.org> wrote:
> On Mon, Jul 31, 2017 at 06:12:54PM +0200, László Böszörményi (GCS) wrote:
>> But the most important thing is that the fail always happened on
>> ppc64el-unicamp-01 - the other buildd, ppc64el-osuosl-01 can build it
>> without any problem. As such, I think it's the buildd that different
>> in some way than the source has any known problem.
>> Can you reschedule the build, first on ppc64el-unicamp-01, then on
>> ppc64el-osuosl-01 and see the results?
> I don't have any powers to reschedule anything.
OK, your involvement - quickly file and follow FTBFS bugs - assumed
more power on buildds.
>> Maybe the former is not up to
>> date and has some inconsistent package set installed?
> chroots on the buildds are regenerated twice per week.
OK, GCC 7.1.0 arrived to ppc64el and GraphicsMagick no longer FTBFS
even on ppc64el-unicamp-01. I don't close this bugreport but lower the
severity to let the security fixes finally migrate to Buster
(testing). I'll see how future builds do on ppc64el and will act