"Eugene V. Lyubimkin" <jac...@debian.org> writes:
> [ sorry for not proper 'mail-reply', used wrong mail address before ]
>
>> Huh? The presense of Replaces allows the two to be both unpacked. The
>> Repalces specifically disables the file conflict.
>
> Replaces is one-way dependency, Breaks is two-way one. If I unpack two
> packages, one having Breaks+Replaces, in the other order, I will have a file
> conflict. And a high-level package manager have right to do it, by the
> definition of Breaks, because "slave" package is not configured.
That was a bug in dpkg that has been fixed a while now I think. Replaces
has to be two-way so that unpacking the replaced package after the
replacing one does not give a file overwrite error.
If you think the issue still exists then please create a unit test in
dpkg and file that as seperate bugreport against dpkg.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
