Axel Beckert <a...@debian.org> writes: > A) Add an option to screen so the screen client speaks the old > protocol to the running server protocol. This IMHO would be best > solution and one without a big impact. It's also something which > could be Debian-only, i.e. a patch. (It of course would be better > if upstream could be convinced to add such an option. :-)
That does sound like the best option. Reading upstream's latest response, they don't seem to have expressed a position on accepting such a change if someone does the work to implement it. > B) Take care that nobody upgrades the screen package while running > inside a screen without being aware of the possible problems. There > are few ideas how to implement this: > > 1) Mention it in the release notes that screen has to be upgraded > to the very end of the dist-upgrade process if the dist-upgrade > is running inside screen. > > Disadvantage: Many admins don't read the release notes. […] > 3) Tell people via the release notes that they should not run the > dist-upgrade inside screen, but inside tmux instead. > > Disadvantage: Many admins don't read the release notes. The release notes (by which I assume you mean ‘changelog’ and ‘changelog.Debian’) are not displayed by default, but I think the ‘NEWS.Debian’ file is intended for this sort of “you need to know this before upgrading the package to this version” information. See the Developer's Reference §6.3.4. -- \ “I am as agnostic about God as I am about fairies and the | `\ Flying Spaghetti Monster.” —Richard Dawkins, 2006-10-13 | _o__) | Ben Finney <b...@benfinney.id.au> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ty4e20xo....@benfinney.id.au
