On Fri, Apr 9, 2010 at 17:18, Christoph Burgmer <cburg...@ira.uka.de> wrote: > Sandro, > > Am Freitag, 9. April 2010 schrieb Sandro Tosi: >> Compatibility bugs for 2.4 are no longer valid (but I'm not closing it >> since i'm neither the pacakge maitainer nor the original reporter). > > Thanks for the info. I know that 2.4 is not supported anymore, but as Debian > has no way of removing once shipped packages I assumed there's at least a way > to keep newer updates respecting left-over packages.
No, there's none. Also, if you had updated python-minimal, you would not have 2.4 in the supported versions list anymore. > I might be wrong but > something along the line of adding a Conflict: python2.4 would add minimum > compatibility. No, that's wrong, an hopefully no-one will do. every modules/extensions has to conflic with 2.4 "just in case"? the main python package? transitions are not done this way. > It's not really a bug so you can probably ignore this after all. > > Oh, and keeping 2.4 does serve a purpose for testing compliance of own > packages. :) That's sure, but if you decide to have an unsupported package for your own purposes, then probably reporting bugs about it is not that correct ;) Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
