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

To: submit@bugs.debian.org
Subject: Bug#428432: Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?
From: Jeremy Brand <jeremy@nirvani.net>
Date: Mon, 11 Jun 2007 09:40:34 -0700
Message-id: <[🔎] Pine.LNX.4.64.0706110926310.32570@quaid.nirvani.net>
Reply-to: Jeremy Brand <jeremy@nirvani.net>, 428432@bugs.debian.org

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

IIRC 'xv' has been gone from debian since woody, or maybe evenpotato. In general, I think it would be nice ifdependencies/conflicts were related only to stable and oldstable.Someone upgrading from potato, should probably upgrade to woodybefore upgrading to sarge and to etch, for example.


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

Reply to:

Follow-Ups:
- Bug#428432: Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?
  - From: Julien Cristau <jcristau@debian.org>
- Bug#428432: marked as done (Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?)
  - From: owner@bugs.debian.org (Debian Bug Tracking System)

Prev by Date: Bug#377165: xserver-xorg: X reports duplicate keycodes for some keys
Next by Date: Bug#428432: Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?
Previous by thread: Bug#412349: marked as done (libgl1-mesa-dri: viewport shifted out of window in torcs)
Next by thread: Bug#428432: Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?
Index(es):
- Date
- Thread