Hi, It seems the wildcard patch you made reference to (bug #291939) has been put on hold for a lot of time now (almost 5 months). Moreover, I heard you have objections to it.
If there are problems with Guillem's patch (even if the problems are just lack of time to verify it), then please don't conditionalise fixing of this trivial FTBFS to the wildcard support. Just fix the FTBFS (which is the inmediate problem for what the etch release is concerned), and we'll talk later about wildcards if you like. Anyway, using wildcards in dpkg _itself_ would be a bad idea, since then you'd create a bootstrap problem for ports compiling the new version of dpkg. So if you want a smooth transition we still need to add the old "!kfreebsd-i386" to dpkg's debian/control. The fix for this bug is as simple as: -Build-Depends: [...], libselinux1-dev [!hurd-i386] +Build-Depends: [...], libselinux1-dev [!hurd-i386 !kfreebsd-i386] Thank you. -- Robert Millan
--- dpkg-1.13.11/debian/control~ 2005-08-14 20:56:53.000000000 +0200 +++ dpkg-1.13.11/debian/control 2005-12-22 13:45:17.470767960 +0100 @@ -5,7 +5,7 @@ Origin: debian Bugs: debbugs://bugs.debian.org Standards-Version: 3.6.1.0 -Build-Depends: debhelper (>= 4.1.81), libncurses5-dev | libncurses-dev, zlib1g-dev (>= 1:1.1.3-19.1), libbz2-dev, libselinux1-dev [!hurd-i386] +Build-Depends: debhelper (>= 4.1.81), libncurses5-dev | libncurses-dev, zlib1g-dev (>= 1:1.1.3-19.1), libbz2-dev, libselinux1-dev [!hurd-i386 !kfreebsd-i386] Package: dpkg Architecture: any
