Bug#876934: openorienteering-mapper FTBFS: test failures

2018-03-26 Thread Kai Pastor, DG0YT
For the record, I now verified on SLE (s390x) that version 0.8.1 also builds for big endian systems. Packages for Debian users continue to be available on https://build.opensuse.org/package/show/home:dg0yt/openorienteering-mapper Bye, Kai

Bug#876934: openorienteering-mapper FTBFS: test failures

2018-03-11 Thread Kai Pastor, DG0YT
Dear maintainers, today I released OpenOrienteering Mapper 0.8.1. Now you have the following options for fixing bug#876934: a) Update to 0.8.1. 0.8.x builds successful with proj-5.0.0 and gdal/libpoppler for Debian Testing on build.opensuse.org. It also builds reproducible for openSUSE Tumb

Bug#876934: openorienteering-mapper FTBFS: test failures

2018-02-09 Thread Kai Pastor, DG0YT
Am 09.02.2018 um 16:03 schrieb Sebastiaan Couwenberg: In preparating of the proj transition openorienteering-mapper (0.7.0-1) was rebuilt in my cowbuilder chroot where these tests caused FTBFS too. I'll raise the severity of this issue to serious when the proj transition starts. Kind Regards,

Bug#876934: openorienteering-mapper FTBFS: test failures

2018-02-09 Thread Sebastiaan Couwenberg
On Mon, 9 Oct 2017 10:54:14 +0200 Graham Inggs wrote: > I've just tried sbuild in an amd64 sid schroot and > openorienteering-mapper builds fine for me. > > I noticed it also still builds in testing on the reproducible-builds > buildds. > > Why don't co-maintainers (uploaders) receive bug by de

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-11-15 Thread Ximin Luo
Kai Pastor, DG0YT: > Am 13.11.2017 um 20:15 schrieb Adrian Bunk: >>> I didn't find a recommendation how to solve the issue. I hope a custom macro >>> is okay. >> Based on the discussion in #876901 [1] it is still unclear how this >> should be resolved in general. >> > One more remark: > > Replacin

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-11-14 Thread Kai Pastor, DG0YT
Am 13.11.2017 um 20:15 schrieb Adrian Bunk: I didn't find a recommendation how to solve the issue. I hope a custom macro is okay. Based on the discussion in #876901 [1] it is still unclear how this should be resolved in general. One more remark: Replacing __FILE__ with an individual macro mak

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-11-13 Thread Kai Pastor, DG0YT
Am 13.11.2017 um 20:15 schrieb Adrian Bunk: On Sun, Nov 12, 2017 at 10:57:38AM +0100, Kai Pastor, DG0YT wrote: Am 11.11.2017 um 17:18 schrieb Adrian Bunk: I found what causes the problem: The failing tests use the following for finding the path to test files: QDir::addSearchPath(prefix, QFile

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-11-13 Thread Adrian Bunk
On Sun, Nov 12, 2017 at 10:57:38AM +0100, Kai Pastor, DG0YT wrote: > Am 11.11.2017 um 17:18 schrieb Adrian Bunk: > > I found what causes the problem: > > > > The failing tests use the following for finding the path to test files: > > QDir::addSearchPath(prefix, > > QFileInfo(QString::fromUtf8(__F

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-11-12 Thread Kai Pastor
v0.7.92 hopefully fixes the FTBFS in the reproducible builds environment. v0.7.92+2 (cd0aed9) might fix reproducibility. (At least, v0.7.92+1 deals with the time stamp in the help collection.) Kai.

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-11-12 Thread Kai Pastor, DG0YT
Am 11.11.2017 um 17:18 schrieb Adrian Bunk: I found what causes the problem: The failing tests use the following for finding the path to test files: QDir::addSearchPath(prefix, QFileInfo(QString::fromUtf8(__FILE__)).dir().absoluteFilePath(prefix)); In unstable reproducible builds the build pat

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-11-11 Thread Adrian Bunk
Control: tags -1 buster On Tue, Oct 17, 2017 at 03:47:37PM +0200, Graham Inggs wrote: > Hi Adrian > > binNMU against libpolyclipping22 is successful too: > https://buildd.debian.org/status/package.php?p=openorienteering-mapper&suite=unstable > > Should this report be reassigned to reproducible b

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-10-17 Thread Graham Inggs
Hi Adrian binNMU against libpolyclipping22 is successful too: https://buildd.debian.org/status/package.php?p=openorienteering-mapper&suite=unstable Should this report be reassigned to reproducible builds? Regards Graham

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-10-09 Thread Graham Inggs
Control: tags -1 + unreproducible sid Control: severity -1 normal I've just tried sbuild in an amd64 sid schroot and openorienteering-mapper builds fine for me. I noticed it also still builds in testing on the reproducible-builds buildds. Why don't co-maintainers (uploaders) receive bug by

Bug#876934: openorienteering-mapper FTBFS: test failures

2017-09-26 Thread Adrian Bunk
Source: openorienteering-mapper Version: 0.7.0-1 Severity: serious Some recent change in unstable makes openorienteering-mapper FTBFS: https://tests.reproducible-builds.org/debian/history/openorienteering-mapper.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openorienteer