Andreas Beckmann <andr...@abeckmann.de> writes:
> Andreas Beckmann wrote:
>> Another question: to all generated ia32-libf00 (1.2.3-4~23) packages a
>> dependency on libf00 (= 1.2.3-4) is added. This should only be
>> neccessary is some files/scripts (e.g. manpages, config files,
>> translations) have been removed during creation of the ia32- package to
>> prevent file conflicts when both ia32-libf00 and libf00 are installed.
>> If no such conflict exists, it should be possible to have ia32-libf00
>> installed and working without having libf00 installed, too.
>> Or a Conflicts: libfoo (<< 1.2.3-4), libfoo (>> 1.2.3-4) would work to
>> forbid mismatching versions to be installed.
>
> That one is really getting nasty if binary NMUs are involved:
>
> i386: libpcre3:
> Candidate: 7.8-2+b1
>
> amd64: libpcre3:
> Candidate: 7.8-2
>
> ia32-libpcre3 gets a dependency on libpcre3 (= 7.8-2+b1) which is
> unsatisfyable on amd64.
>
>
> Andreas
Yeah. That is one reason why I droped it already in the ia32-apt-get
branch. Policy 8.2 already forbids libraries to have conffiles, shared
data, binaries and so on. So anything that breaks by dropping the
i386->amd64 dependency will near certainly violate Policy 8.2. So if
things break a bugreport is in order instead of the ugly dependency
workaround.
Don't worry, this is pending.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
