Your message dated Wed, 20 Jul 2016 23:07:26 +0200
with message-id <[email protected]>
and subject line Re: Bug#831865: d-shlibs: Claims libncbi-vdb.a is not a valid
shared library file name
has caused the Debian Bug report #831865,
regarding d-shlibs: Claims libncbi-vdb.a is not a valid shared library file name
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 [email protected]
immediately.)
--
831865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831865
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: d-shlibs
Severity: normal
Hi,
when trying to build ncbi-vdb[1] which has an admittedly hard to
understand self-made build system I end up with
d-shlibmove --commit \
--multiarch \
--devunversioned \
--exclude-la \
--movedev debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/*.a
usr/lib/x86_64-linux-gnu \
--movedev interfaces/ngs/ncbi/NGS.hpp usr/include/ncbi-vdb \
debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/libncbi-vdb.so
Library package automatic movement utility
/usr/bin/d-shlibmove:
[debian/tmp/usr/ncbi-vdb/linux/gcc/x86_64/dbg/lib/libncbi-vdb.a] is not a valid
shared library file name
debian/rules:43: recipe for target 'override_dh_auto_install' failed
I agree that *.a is no valid shared library file name - but why does
d-shlibmove assume this is regarded as a shared lib?
Jonas suggested to discuss this in BTS and so here is the according bug.
The build happended in an unstable pbuilder chroot - so the system
information below is irrelevant.
Kind regards
Andreas.
[1] https://anonscm.debian.org/git/debian-med/ncbi-vdb.git
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Wed, Jul 20, 2016 at 06:09:37PM +0200, Jonas Smedegaard wrote:
>
> Ahh - yes, d-shlibs "--movedev" option expects exactly two arguments
> (unlike common for dh_* tools) - as documented in its manpage:
>
> --movedev [filename] [relative dir-path]
>
> Further "arguments" are seen not as belonging to that option but the
> library path, as per its manpage:
>
> d-shlibmove [options] shared-library.so
That's fine.
> I will therefore say that there is at best a wishlist bug to change
> logic of argument parsing. That does make some sense - I will leave it
> to you to decide if you want this bugreport repurposed for that or not.
I consider it a broken case anyway where you have a set of *.a libs
instead of only one. So lets close this bug.
Kind regards
Andreas.
--
http://fam-tille.de
--- End Message ---
