[Pkg-javascript-devel] Bug#901297: libnode64-dev: rename to libnode-dev

Emilio Pozuelo Monfort pochu at debian.org
Mon Jun 11 07:59:39 BST 2018


Package: libnode64-dev
Version: 10.4.0~dfsg-1
Severity: important

Hi,

Your shared library package is named libnode64, since it ships libnode.so.64.
That is fine. However the development package should be named libnode-dev,
so that rdeps build-dep on libnode-dev and when upstream bumps the SONAME,
a binNMU is enough to rebuild them against the new SONAME. Otherwise if they
build-depend on libnode64-dev, rdeps would need sourceful uploads, making
transitions unnecessarily difficult.

Besides, libnode64-dev and libnode65-dev would never be co-installable and
would need to conflict against each other, so there's no point in versioning
them.

Cheers,
Emilio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libnode64-dev depends on:
pn  libnode64  <none>

libnode64-dev recommends no packages.

libnode64-dev suggests no packages.



More information about the Pkg-javascript-devel mailing list