On Thu, 4 Aug 2011 14:23:20 +0200 Jonas Smedegaard <d...@jones.dk> wrote:
> Closing *again* as a non-bug. I follow, but here's my 2 cents from userland... If a 'python2.3' package existed in the current Debian distros, then this bug could be moved to that package. No 'python2.3' package currently exists in Debian. Must it therefore follow, (as has been argued), that there is no install bug? At least two users have been bitten, and have registered their doubts. Bug #630787 seems to be a systemic Debian meta bug, where incomplete or inaccurate metadata from an unmaintained "ex-package" _breaks_ the install for a current package update. From userland it's hard to see why such breakage should ever be allowed. If such a 'ghostly influence' meta bug already exists, then #630787 should be merged with it. If such a meta bug does not exist, then #630787 should be moved and renamed to the appropriate meta package. Otherwise we can expect that future maintainers will needlessly be distracted by users with similarly misdirected bug reports, perhaps forever... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
