Found this in the junk e-mails today...
Am 23.02.21 um 19:20 schrieb Sebastiaan Couwenberg:
There is still a test failure, though. Refer to the attached buildlog
for details.
This seems unrelated to PROJ 8.0.0.
The failing test creates a QTemporaryFile, removes all permissions from
the file
Am 24.02.21 um 08:46 schrieb Sebastiaan Couwenberg:
On 2/24/21 8:04 AM, Kai Pastor, DG0YT wrote:
I would agree that many projects have shortcoming in how they use CMake,
partly due to past shortcomings of CMake and its documentation, partly
due to ignorance of cross-platform building and
Am 24.02.21 um 05:55 schrieb Sebastiaan Couwenberg:
On 2/24/21 12:58 AM, Kai Pastor, DG0YT wrote:
Am 23.02.21 um 19:53 schrieb Sebastiaan Couwenberg:
It's good practice to include the Find modules for any dependencies that
are not part of cmake itself to not need upstream projects to in
Am 23.02.21 um 19:53 schrieb Sebastiaan Couwenberg:
A patch for that was just submitted to this bugreport.
Thanks.
It's good practice to include the Find modules for any dependencies that
are not part of cmake itself to not need upstream projects to install
cmake modules for them.
I think i
Am 21.02.21 um 16:32 schrieb Bas Couwenberg:
Source: openorienteering-mapper
Version: 0.9.4-2
Severity: important
Tags: upstream ftbfs
User: debian-...@lists.debian.org
Usertags: proj-8.0
Control: forwarded -1 https://github.com/OpenOrienteering/mapper/issues/1214
Dear Maintainer,
Your package
Am 25.11.20 um 19:05 schrieb Dmitry Shachnev:
On Wed, Nov 25, 2020 at 06:15:53AM +0100, Kai Pastor, DG0YT wrote:
I also left a link to this Debian bug in Qt's code review for the offending
change.
Can you please share a link to the mentioned code review?
https://bugreports.qt.io/browse/
Am 24.11.20 um 19:24 schrieb Dmitry Shachnev:
Hi Kai!
On Thu, Oct 15, 2020 at 07:48:49AM +0200, Kai Pastor, DG0YT wrote:
This patch fixes the creation of the offending timestamp, by clamping to
SOURCE_DATE_EPOCH as specified.
Thank you for the patch and sorry for delayed response!
I also
Am 10.11.20 um 11:35 schrieb Simon McVittie:
On Fri, 16 Oct 2020 at 08:29:48 +0200, Kai Pastor, DG0YT wrote:
So far, all cases in openorienteering-mapper were tests which were expected
to be run in the build environment and indeed access the pristine test data
in the source directory.
The
Am 10.11.20 um 01:00 schrieb Vagrant Cascadian:
On 2020-10-16, Kai Pastor, DG0YT wrote:
Am 16.10.20 um 01:19 schrieb Vagrant Cascadian:
When the reproducible=+fixfilepath feature is enabled (either through
DEB_BUILD_OPTIONS, or using a dpkg that enables this by default),
openorienteering
Am 16.10.20 um 01:19 schrieb Vagrant Cascadian:
Package: openorienteering-mapper
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fixfilepath ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
When the reproducible=+fixfilepath feature is enable
This patch fixes the creation of the offending timestamp, by clamping to
SOURCE_DATE_EPOCH as specified.
I also left a link to this Debian bug in Qt's code review for the
offending change.
Best regards,
Kai
Clamp registered collection time-stamp to SOURCE_DATE_EPOCH if set.
--- a/src/assistan
Am 13.10.20 um 20:05 schrieb Dmitry Shachnev:
Source: openorienteering-mapper
Version: 0.9.3-1
Severity: important
Tags: ftbfs
User: debian-qt-...@lists.debian.org
Usertags: qt5.15
Dear Maintainer,
openorienteering-mapper fails to build with Qt 5.15, currently available in
experimental:
/bu
Am 21.10.19 um 15:11 schrieb Peter Palfrader:
Evan Jones schrieb am Monday, dem 21. October 2019:
THANK YOU and whoever else is involved in maintaining this. Just letting
you know that I appreciate the work here. I don't work for Google, but I do
use Distroless [1], a lightweight Debian-based c
This is probably the same issue as #941903.
Source: zlib
Severity: normal
Dear Maintainer,
a) the zlib 1:1.2.11.dfsg-1 copyright file claims to be based on sources
from zlib-1.0.4.tar.gz which is obviously wrong.
b) the Files-Excluded field is not up-to-date for
zlib_1.2.11.dfsg.orig.tar.gz. The listed contrib/testzlib is in the DFSG
Am 08.07.2018 um 06:03 schrieb Simon Quigley:
Source: openorienteering-mapper
Version: 0.8.1.1-1
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qt5.11.1
Dear Maintainer,
Your package fails to build from source against Qt 5.11.1 in
Experimental with the following error:
..
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
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
Am 04.03.2018 um 10:03 schrieb Sebastiaan Couwenberg:
severity 889931 serious
severity 876934 serious
severity 889936 serious
thanks
The proj transition (#891966) has started, these build failures are now RC.
Kind Regards,
Bas
Again, 876934 was reported for FTBFS in reproducible builds. This
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,
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
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
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
Relevant upstream changes for Big Endian builds are
aed9a2d7d20d019c8cf5dff0d8e5edeee2b4d2d8
14a683b07b7657f766b84c6c67f9080bef8af7c5
Cf.
https://github.com/OpenOrienteering/mapper/commits/14a683b07b7657f766b84c6c67f9080bef8af7c5/CMakeLists.txt
Am 15.08.2017 um 21:48 schrieb Graham Inggs:
Source: openorienteering-mapper
Version: 0.6.7-1
OpenOrienteering Mapper is unable to open files with spaces in their
names from the command line. This also prevents users from
double-clicking on a map with a space in its name from a file manager;
e.
The only relevant change in the environment I see is gcc-7.
According to https://tracker.debian.org/pkg/gcc-7:
"[2017-08-08] Accepted gcc-7 7.1.0-13 (source) into unstable"
According to
https://tests.reproducible-builds.org/debian/history/openorienteering-mapper.html,
openorienteering-mapper 0
Mapper contains binary file format implementations which are known to
break on Big Endian machines. Mapper remains usable without these file
formats since the current native format is based on XML. However, the
loss of the OCD format would harm exchange with common proprietary
software. This mi
Package: openorienteering-mapper
Version: 0.6.3-2
Dear Maintainer,
OpenOrienteering Mapper is developed on Github
(https://github.com/OpenOrienteering/mapper/).
The current release is 0.6.5.
The watch file in Debian needs to be corrected to point to Github
instead of Sourceforge.
Thanks.
28 matches
Mail list logo
