Yves-Alexis Perez wrote: > Thanks. Although it seems your _multi.changes might have issue. How > exactly did you made it? It apparently references twice the debian > changes: > > b05bf69385554dddaa22629327ac647c384c1585 15413 > unbound_1.4.17-3+deb7u2.debian.tar.gz > d4addd58c211ff20d707e52d961befce855cd401 13864 > unbound_1.4.17-3+deb7u2.debian.tar.xz > > the latter beeing non existent.
Oh, hrm. I built a source package with git-buildpackage from my sid environment, generating a _source.changes: Checksums-Sha1: db46cc396cd2e8827971278f7bbe647f67e1fb79 1480 unbound_1.4.17-3+deb7u2.dsc fea4d812c03af4737ef671ac30b7b7400d346516 3585122 unbound_1.4.17.orig.tar.gz d4addd58c211ff20d707e52d961befce855cd401 13864 unbound_1.4.17-3+deb7u2.debian.tar.xz Then I built the source package with a wheezy pbuilder, generating an _amd64.changes: Checksums-Sha1: 22ac970c5f8cbc50a71bfd9227e643ea12e0a780 1430 unbound_1.4.17-3+deb7u2.dsc b05bf69385554dddaa22629327ac647c384c1585 15413 unbound_1.4.17-3+deb7u2.debian.tar.gz bca4248d66065d4c906e94cbc73c0ce03c18a2a3 676630 unbound_1.4.17-3+deb7u2_amd64.deb d31419811533519ec5e01f16f04b111e3cfd4316 92722 unbound-anchor_1.4.17-3+deb7u2_amd64.deb d86e2f4c9d0e3ac7a5941894c51042c5c4e58bba 81086 unbound-host_1.4.17-3+deb7u2_amd64.deb 5e1f6af75500821edc0aba547a52a3acdb70c08a 309792 libunbound2_1.4.17-3+deb7u2_amd64.deb 31967459a5d928c7aa660dbbe67176f1bdf0f8fe 3482478 libunbound-dev_1.4.17-3+deb7u2_amd64.deb 08e60f3154dc1e5985dd202fabf07ebe20136b89 113752 python-unbound_1.4.17-3+deb7u2_amd64.deb Then I ran mergechanges -f on the two .changes files. Do you want me to re-build the source package in a pure wheezy environment? (And if so, should I re-use the +deb7u2 version number or bump it to +deb7u3?) -- Robert Edmonds [email protected] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
