Hi Andreas,
Op 26-11-2020 om 21:55 schreef Andreas Tille:
BTW, it seems to be the same example file in libcifpp. I'd consider it
a good idea to have this file only once and set dependencies
appropriately.
This file is very common, I use it in all my PDB related packages.
I agree that sticking to a single instance is way more convenient. But then
the question is, where do I put this. The libcifpp package contains a -dev
and -doc next to the library.
Intuitively I'd say -doc makes sense and let the Test depend from this
-doc package.
There's no -doc package for libcifpp, yet. And since the example file is
in -dev, I've added that as a dependency to tortoize's autopkg control
file. That seems to work fine now. I've checked this in, and since
libcifpp is accepted, everything is working now so tortoize is ready to
be uploaded.
However, I ended up with a package that builds fine when using sbuild,
but fails when using gbp buildpackage. The package created with gbp has
a lintian error telling me:
gbp:info: Running Postbuild hook
E: tortoize source: source-contains-unsafe-symlink config/m4/libtool.m4
N:
N: The source contains an unsafe symlink. If followed, the link will
escape
N: the source root. Note that all absolute symlinks are unconditionally
N: considered "unsafe" in this case (unlike in binary packages).
N:
N: If it is a part of the package's testsuite, Lintian may have failed to
N: recognise it as a test. In that case, please override the tag.
N:
N: Severity: error
N:
N: Check: cruft
N:
E: tortoize source: source-contains-unsafe-symlink config/m4/ltoptions.m4
E: tortoize source: source-contains-unsafe-symlink config/m4/ltsugar.m4
E: tortoize source: source-contains-unsafe-symlink ... use
--no-tag-display-limit to see all (or pipe to a file/program)
W: tortoize source: absolute-symbolic-link-target-in-source
config/m4/libtool.m4 -> /usr/share/aclocal/libtool.m4
Why is that? What's the difference here between gbp and sbuild?
regards, -maarten
