Bastian Blank wrote: > dh_gencontrol and dh_builddeb generates wrong filenames for udebs with > overwritten version: > > | dh_gencontrol -- -v2:1.02.30-1
So, unsuprisingly, debhelper commands *never* look at parameters passed on to lower-level commands after --. > | dpkg-gencontrol -plibdevmapper1.02.1-udeb -UHomepage > -nlibdevmapper1.02.1-udeb_2.02.44-1_amd64.udeb -ldebian/changelog > -Tdebian/libdevmapper1.02.1-udeb.substvars -Pdebian/libdevmapper1.02.1-udeb > -v2:1.02.30-1 Specifying -n here is not necessary with current versions of dpkg-gencontrol, which use the Package-Type control file field, and so this minor bug has been fixed in debhelper git. > | chmod 644 debian/libdevmapper1.02.1-udeb/DEBIAN/control > | chown 0:0 debian/libdevmapper1.02.1-udeb/DEBIAN/control > | dh_md5sums > | dh_builddeb > | dpkg-deb --build debian/libdevmapper1.02.1-udeb > ../libdevmapper1.02.1-udeb_2.02.44-1_amd64.udeb > | dpkg-deb: building package `libdevmapper1.02.1-udeb' in > `../libdevmapper1.02.1-udeb_2.02.44-1_amd64.udeb'. I could fix this by making dh_builddeb parse DEBIAN/control for the version, but a better fix would be to simply make dpkg-deb Package-Type aware, like the rest of dpkg-dev is (which would mean parsing debian/control in addition to its existing parsing of DEBIAN/control). Then debhelper would not need to specify a filename at all. In the meantime, the obvious fix is to pass --filename to dh_builddeb in your package. The realative simplicity of that fix, and the rarity of needing to override package versions at all, let alone for udebs, suggests that the severity of this bug report is inflated. -- see shy jo
signature.asc
Description: Digital signature
