On Fri, 28 Oct 2011, Sven Joachim wrote: > > Well, if it finds a system library with a shlibs/symbols file, the > > generated dependency can't really be wrong. > > It can, because some symbols may be missing from the system library that > are present in the just-built one.
Well, that can only happen with shlibs, not with symbols. > > When people put debian/compat 9, they want all the features of the new > > mode (including multiarch support) and they don't expect the feature to be > > enabled only in some cases. Note that debhelper build-depends on dpkg-dev > > (>= 1.16.0) and apparently (from what you say) the backport changes that > > requirement, it's not a very good backport. Hum I meant "depends" and not build-depends here. > I think it would be better to backport dpkg-dev and make > dpkg-architecture report the empty string as $DEB_HOST_MULTIARCH, but > nobody has done that yet (and I'm not volunteering). I plant to backport dpkg but changing the behaviour associated to version >= 1.16 doesn't seem to be a good idea. Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/go/ulule-rh/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
