[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#428432: Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?



Thus spake Julien Cristau:

On Mon, Jun 11, 2007 at 09:40:34 -0700, Jeremy Brand wrote:

Package: x11-common
Version: 1:7.1.0-16


IIRC 'xv' has been gone from debian since woody, or maybe even
potato.  In general, I think it would be nice if
dependencies/conflicts were related only to stable and oldstable.

Why?

Because, since there is no package 'xv' in any current version of Debian, Debian (eg. x11-common in etch) should not prevent a package from being installed that goes by the name of 'xv' regardless of versions, as long as there are no _real_ conflicts.

Someone upgrading from potato, should probably upgrade to woody
before upgrading to sarge and to etch, for example.


Nothing forces removal of obsolete packages on upgrades, so people might
have upgraded to sarge and still have xv installed.

I don't understand why you think there's a bug here.

Bug is certainly a harsh term, but there is no _suggestions_.debian.org tracking system.

So, it's great 'xv' from potato apparently would survive in this situation (maybe I should test that ;). However, a package by the name of 'xv' with any version number _should_ be able to survive in etch, since etch has no 'xv' package, but this is the the case.

Cheers :)
Jeremy

--
"Prediction is very difficult, especially of the future."
                                   Niels Bohr
http://www.nirvani.net



Reply to: