Neil Schemenauer <[EMAIL PROTECTED]> writes: [...]
Looks fint to me! > I'm willing to build new version of packages with broken dependencies. > Can we handle the upgrade from Python by having a long list of conflicts > in the "python" package? Something like: > > Conflicts: python-some-extension (<< X.Y), ... > Hopefully, this list will not be very long, as many packages depend on python-base today. In sid, 37 packages depend on python, but I don't know how many of these place stuff in /usr/lib/python1.5/ I think this list is the best way to go. Those packages are broken, and the Conflicts: line is a nice fix. /Micce -- Mikael Hedin, MSc +46 (0)980 79176 Swedish Institute of Space Physics +46 (0)8 344979 (home) Box 812, S-981 28 KIRUNA, Sweden +46 (0)70 5891533 (mobile) [gpg key fingerprint = 387F A8DB DC2A 50E3 FE26 30C4 5793 29D3 C01B 2A22]
