On Fri, Oct 03, 2003 at 02:21:05AM -0500, Chris Cheney wrote: > I was wondering what other people think about making a policy change > stating a library -dev arch: any package must not depend on a arch: all > package in the same source. The reason for this is that whenever a > package is out of sync on one arch it can no longer satisfy its > dependencies and thus can not be used for building. An example of this > is qt-x11-free.
This only happen because of a strict versionned dependency, so it should not be very common. The only case that cause problem is when a arch:any package depend n the same version of a arch:all package in the same source, and even there only if the first FTBFS on one arch where it was previously built successfully, which is alread a RC bug. The problem with building packages is only a side-effect of an uninstallable package condition, which is a bug in is own right. > Package: libqt3-mt-dev > Architecture: i386 > Depends: xlibs-dev (>= 4.2.1), libmng-dev (>= 1.0.3), libpng12-0-dev, > libjpeg62-dev, zlib1g-dev, libfreetype6-dev, libc6-dev, libqt3c102-mt (= > 3:3.2.1-5), libqt3-headers (= 3:3.2.1-5), qt3-dev-tools (= 3:3.2.1-5), > xlibmesa-gl-dev | libgl-dev, xlibmesa-glu-dev | libglu1-mesa-dev | > libglu-dev, libxft2-dev, libxrender-dev, libxcursor-dev, libaudio-dev > > Package: libqt3-headers > Architecture: all > > Since libqt3-mt-dev depends on libqt3-headers (= 3:3.2.1-5) if > libqt3-mt-dev hasn't built on an arch libqt3-headers is newer than what > libqt3-mt-dev requires and thus packages can't be built. Maybe you can weaken the dependency to libqt3-headers (= 3:3.2.1) ? The would lessen the impact of the problem. Do you actually make incompatible changes in libqt3-headers between Debian revisions ? > ps - cc: me (BTW - How do i make that happen automatically with mutt?) .muttrc: lists debian-policy@lists.debian.org Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here.
