I should mention that I've got involved in this conversation because this issue was raised as a bugreport for the release-notes package, and thus copied to debian-doc: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649240 http://lists.debian.org/debian-doc/2011/11/msg00004.html
Axel Beckert wrote: > Steve Langasek wrote: >> Justin B Rye wrote: >>> Would it make sense to recommend putting screen on hold > > IMHO no. Most people won't read those recommendations. Well, the people who don't read the warnings aren't relevant to the question of what warnings should be given. Of course if a solution is found that won't inconvenience people doing dist-upgrades, debian-doc can forget it. > Besides I've > never read such a recommendation before, neither for udev nor for > gdm3. And I do read the release notes since approximately the > Sarge/Etch dist-upgrade. I imagine the reason nobody recommended putting udev on hold is that it wouldn't have worked - too many things depend on it. For screen, things are different. >>> and upgrading it separately after the dist-upgrade is finished? > > That's my current plan, but caused by a preconfigure or preinst script > which fails if active screen sessions are running like udev did if it > wasn't upgraded together with the kernel once. That can help block people from charging blindly into a situation where they've got lost screen sessions, but won't it be at the cost of derailing a multi-package install with a sudden dpkg error message? If people were warned to upgrade screen as a separate process they could avoid either problem. >>> (We'll need material for the release notes eventually, but first >>> screen 4.1.0 is obviously going to need to put some warnings and >>> recommendations in a NEWS.Debian file.) > > Ehm, Justin, you seem not aware that there is already a "first" 4.1.0 > package in Experimental which does exactly that: > > http://packages.qa.debian.org/s/screen/news/20111009T025041Z.html > > (Look for the string "NEWS".) Hurrah for NEWS.Debian and apt-listchanges! > The reason why I uploaded it to experimental and not to unstable is > exactly the one we're now discussion about. :-) It doesn't actually offer a solution yet, though, does it? My point was that once there's a consensus it'll go there before it needs to go in the release notes. -- JBR A long time ago this practice was followed, especially in the upper classes, but today even the children of the lower classes perform no executions, and this is extreme negligence. - "Hagakure", Yamamoto Tsunetomo (1716) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
