On 2012-05-25 Samuel Thibault <sthiba...@debian.org> wrote: > reopen 623578 > found 623578 1.0.0-15 > thanks
> Debian Bug Tracking System, le Thu 21 Apr 2011 18:51:09 +0000, a écrit : > > #623578: gadfly: build wrong version of the packaging during a binNMU > > > > It has been closed by Matthias Klose <d...@debian.org>. > Err, no, the bug is still there, binNMUs still get built wrongly: > drwxr-xr-x 7 samy samy 300 mai 25 02:58 gadfly-1.0.0/ > -rw-r--r-- 1 samy samy 65K mai 25 02:58 > python-kjbuckets_1.0.0-15_amd64.deb > -rw-r--r-- 1 samy samy 896 mai 25 02:58 gadfly_1.0.0-15+b1_amd64.changes Hello, Afaict (Both by looking at 684625 which is not fixed and by checking the newest binNMU on my up to date testing system) we are currently still doing binNMUs with something equivalent to this: dch --bin-nmu foo && dpkg-buildpackage -B Which works perfectly fine with gadfly: -rw-r--r-- 64708 Oct 14 08:53 python-kjbuckets_1.0.0-15+b1_i386.deb -rw-rw-r-- 970 Oct 14 08:53 gadfly_1.0.0-15+b1_i386.changes I get the same result if I add ', binary-only=yes' to debian/changelog. Please describe how the issue can be reproduced? > This is apparently due to this: > dh_gencontrol -a -- -v'$(kjb_version)' > Why setting that particular version and not let it use the changelog > version? The python-kjbuckets package has a diferent binary version (with an epoch added) than source and the other binary packages. thanks in advance, cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org