On Mon, May 22, 2006 at 08:58:52AM +0200, Lupe Christoph wrote:
> On Sunday, 2006-05-21 at 01:23:35 -0500, Steve Langasek wrote:
> > On Sat, May 20, 2006 at 02:56:51AM -0400, Filipus Klutiero wrote:
> > > This bug moved to Etch.
> > > manpages-dev still needs to add a Conflicts: glibc-doc (<< 2.3.6-8)
>
> > You mean "Replaces".
>
> It's not a complete replacement. Consider this:
That isn't what "Replaces" means; it is just a not so fine-grained way
of allowing one packages files to overwrite those from another
package; see the policy document.
http://www.us.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
You seem to be thinking of the overloaded use "Replaces+Conflicts",
which indicates that one package supercedes the other, and that the
old package should be removed. There is talk of introducing a control
file field for this. Note that it isn't sufficient to add
Replaces+Conflicts to change a package's name, for example from
mozilla-firefox to firefox; it is necessary for the new source package
("firefox") to generate an empty (except for the copyright and
changelog files) package with the old name ("mozilla-firefox") which
depends on the new binary package name ("firefox"). I think you can
also do this with "Provides:".
Justin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
