On Thu, May 12, 2005 at 05:59:07PM +0200, Christian Aichinger wrote: > On Thu, May 12, 2005 at 01:15:37AM +0200, Frank Lichtenheld wrote: > > On Wed, May 11, 2005 at 08:23:59PM +0200, Christian Aichinger wrote: > > > The problem is that we are missing a versioned conflict against > > > older versions of python-apt, which contains the same files as > > > python2.3-apt does now. > > Wouldn't a Replaces actually suffice? > Ok, after re-reading that part of the Debian Policy, I think we need > Conflicts+Replaces. I don't think that Replaces alone will do the > job. > Citing the policy manual: > >> This usage [a Replaces: line] only takes effect when the two > >> packages do conflict, so that the two usages of this field do not > >> interfere with each other. Eh, "this usage" is the wrong usage. You want the one that means "this package permanently replaces files found in the other package", which is the one that you get without a Conflicts line. There's no reason to force the removal of the other package here, AFAICT. -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature