Your message dated Sat, 18 Nov 2017 10:26:00 +0000 with message-id <be71d6da-7f73-b9f8-1ee6-932488d8b...@thykier.net> and subject line Re: release.debian.org: [patch] consider arch:all binaries on non-release architectures as cruft has caused the Debian Bug report #859566, regarding Britney: Should ignore irrelevant out of date arch:all binaries kept for non-release architectures to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 859566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: britney Dear Release Team, a fix for postgis is currently not migrating to testing, even though it got unblocked. AFAIUI this is caused by missing builds on mips and mipsel. On those architectures, the dependent package sfcgal FTBFSs due to out of memory errors during compilation. Only sid is affected, though. The older version of sfcgal in stretch builds just fine even on mips{,el}. postgis-2.3.1+dfsg-1, i.e. the version just before the fix built fine on mips{,el}, so I'm fairly confident 2.3.1+dfsg-2 will build perfectly fine on stretch as well (where sfcgal is available even for those mipsen). Please help resolving that situation, thanks. Kind Regards Markus Wanner
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---On Fri, 17 Nov 2017 19:42:25 +0100 Paul Gevers <elb...@debian.org> wrote: > Package: release.debian.org > Followup-For: Bug #859566 > User: release.debian....@packages.debian.org > Usertags: britney > > Because this bug is hampering migration of fpc with every new upstream release > and lazarus with every minor upstream update, I spent some time on > investigating the issue in britney. As always with nicely written code, the > fix > needs minimal changes. > > Travis¹ already ran on my push to github², but it seems that the test-suite is > out-of-date (pun intended) on the current state of britney. I'll fix the > test-suite ASAP. I manually tested the runtests framework and I had no > regressions there and as expected the current two "expected failure" test > cases > for this bug now pass. > > Please consider my patch to enable migration of fpc and lazarus without human > interaction. > > Paul > > ¹ https://travis-ci.org/Debian/britney2/ > ² > https://github.com/Debian/britney2/commit/0b58a313cbc8db17befbff36907af4fbd6f663d5 > > [...] The patch has been merged, pushed and is now used on release.d.o (along with the tweaks to the test suite to update which tests that passes). After that fpc and lazarus migrated and this bug is now fixed. :) Thanks, ~Niels
--- End Message ---
