Bug#798563: cernlib: build-arch-dependent paths end up in source package

Wookey wookey at debian.org
Thu Sep 10 14:43:47 UTC 2015


Package: cernlib
Version: 20061220+dfsg3-4.1
Severity: normal

Dear Maintainer,

Whilst fixing cernlib to build on arm64 I noticed that the source
tarball produced by dpkg-buildpackage -S ends up containing multiarch
library paths specific to the arch the tarball happens to be built
on. This is wrong - the source should be the same whichever arch it is
built on. Essentially the source seems to contain
generated/regenerated files. Hopefully the fix is a simple as removing
them

The first issue is debian/patches/304-update-Imake-config-files.dpatch
which is generated from the arch-independent 
debian/patches/304-update-Imake-config-files.dpatch.in
but is part of the source tarball. So after regeneration on a new arch you get: 
-## DP: Move kuesvr into /usr/lib/x86_64-linux-gnu/libpacklib1-gfortran in conformance
+## DP: Move kuesvr into /usr/lib/aarch64-linux-gnu/libpacklib1-gfortran in conformance
and
-+    line = strdup( "/usr/lib/x86_64-linux-gnu/libpacklib1-gfortran/kuesvr -p " );
++    line = strdup( "/usr/lib/aarch64-linux-gnu/libpacklib1-gfortran/kuesvr -p " );

The build still works if
debian/patches/304-update-Imake-config-files.dpatch is removed from
the source but it then doesn't end up in debian/patches/00list so I'm
not sure if in fact that means that it's actually not applied? I see
from the readme that 00list is generated on clean. Can it be made a
bit smarter to notice that there is a .in file and use that to add a
suitable 00list line without the .in? I don't grok the build system
enough to know if this is the right solution.

if you do a second build 2 more more files get changed:
src/packlib/kuip/code_kuip/kiinit.F
src/packlib/kuip/code_kuip/kuipcdf.cdf

presumably these are both generated files (I have no idea what they
are for, sorry)? Can they simply be cleaned so that they are not in
the tarball but will be properly regenerated or is there more to it
than that?

Removing them from the build still lets the package build OK, but I've
not checked to see if everything is as it should be.

Hope this is helpful.


-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



More information about the debian-science-maintainers mailing list