severity 557929 serious thanks Hi,
I'm going to set this bug report again to an release critical severity, for the plain reason that we cannot release Debian with this bug present. The bug severity is just a helper to make sure the release management knows about all release critical issues, and can monitor them. Nothing more but nothing less, so please keep this bug at that severity. About the bug itself: How about e.g. adding an transition package libkrb53 to unstable which depends on libk5crypto and also libk5crypto breaks the lenny libkrb53. That together would makes sure that the breakage doesn't happen? That transition package can then be dropped after one release cycle. (Please just say if that's a silly idea.) The same is true for all other split off packages of course. Please also remember that easy and painless upgrades are one of Debians major strength, together with really stable software and getting rid of all the minor hassels that make the life of system administrators hard. I'd like to see squeeze as another success story from Debian, as our previous release already are. Cheers, Andi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
