The build works as expected, I think "dh_install" is where the named binary got overwritten because "-pPACKAGE" is not mentioned.
Testing with "fakeroot debian/rules build" revealed:
$ md5sum build/bin/named/named 9f9fad4761dccb84801351a32c8c1a4f build/bin/named/named
$ md5sum build-singlethread/bin/named/named bbdff642ecbf573521c6143a7d21db15 build-singlethread/bin/named/named
While installing bind9 or bind9-single-thread, named binary have the same md5sum for both. So definitely the build part is working as expected, but the installation/copy goes wrong.
Hopefully that would do the trick:
- dh_auto_install -B build --destdir=$(CURDIR)/debian/tmp - dh_auto_install -B build-singlethread --destdir=$(CURDIR)/debian/tmp-singlethread + dh_auto_install -pbind9 -B build --destdir=$(CURDIR)/debian/tmp + dh_auto_install -pbind9-single-thread -B build-singlethread --destdir=$(CURDIR)/debian/tmp-singlethread
The build works as expected, I think "dh_install" is where the named binary got overwritten because "-pPACKAGE" is not mentioned.
Testing with "fakeroot debian/rules build" revealed:
$ md5sum build/bin/ named/named 4801351a32c8c1a 4f build/bin/ named/named
9f9fad4761dccb8
$ md5sum build-singlethr ead/bin/ named/named 521c6143a7d21db 15 build-singlethr ead/bin/ named/named
bbdff642ecbf573
While installing bind9 or bind9-single- thread, named binary have the same md5sum for both.
So definitely the build part is working as expected, but the installation/copy goes wrong.
Hopefully that would do the trick:
- dh_auto_install -B build --destdir= $(CURDIR) /debian/ tmp $(CURDIR) /debian/ tmp-singlethrea d $(CURDIR) /debian/ tmp single- thread -B build-singlethread --destdir= $(CURDIR) /debian/ tmp-singlethrea d
- dh_auto_install -B build-singlethread --destdir=
+ dh_auto_install -pbind9 -B build --destdir=
+ dh_auto_install -pbind9-