Re: Bug#807019: tracking bin-num - broken unison due to binnmu upload
* Stéphane Glondu <glondu@debian.org>, 2015-12-07, 16:23:
* is there a way to track down who uploaded -3+b1?
For "who", I don't know.
BinNMU are usually scheduled by the Release Team.
This package was part of the ncurses transition:
https://release.debian.org/transitions/html/ncurses.html
But for "why", cf
/usr/share/doc/unison2.40.102/changelog.Debian.amd64.gz:
unison2.40.102 (2.40.102-3+b1) sid; urgency=low, binary-only=yes
* Binary-only non-maintainer upload for amd64; no source changes.
* Rebuild against ncurses 6.0.
-- amd64 / i386 Build Daemon (babin) <buildd-babin@buildd.debian.org> Fri, 31 Jul 2015 09:50:21 +0200
...which is strange, because unison doesn't use ncurses AFAICT.
Not on amd64, but it does link to ncurses on some other architectures.
This is probably unintentional. For example, I see this in the mips
build log[0]:
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/unison2.32.52/usr/bin/unison-2.32.52 was not linked against libncurses.so.5 (it uses none of the library's symbols)
Also, the date is misleading; it corresponds to the last sourceful
upload, not the binNMU.
Looks like a fallout after #620112.
This change in sbuild should be reverted. It didn't fix binNMU
co-installability, and made binMNU changelog entries less helpful.
[0] https://buildd.debian.org/status/fetch.php?pkg=unison2.32.52&arch=mips&ver=2.32.52-7%2Bb1&stamp=1449193180
--
Jakub Wilk
Reply to: