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

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

Your message dated Wed, 13 Jun 2007 21:28:06 +0200
with message-id <46704546.9000100@ens-lyon.org>
and subject line Bug#428432: Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
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. Someone upgrading from potato, should probably upgrade to woody before upgrading to sarge and to etch, for example. 

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

--- End Message ---
--- Begin Message --- 
Jeremy Brand wrote:
> 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.
>
> 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.

For now, the chances that somebody kept 'xv' installed since potaty are
higher than the chances that a new 'xv' package arrives in Debian. If a
new 'xv' ever enters debian again, we'll change the conflict into a
versioned conflict or so.

Thanks,
Brice

--- End Message ---
Reply to: