(I think that a crosspost to -boot is deserved here) Quoting Frans Pop (firstname.lastname@example.org): > On Tuesday 20 June 2006 14:15, Frans Pop wrote: > > Currently X shows a very scary message that upgrades may go wrong > > (template: x11-common/upgrade_issues) on new installations. > > Note that Joey Hess filed this as http://bugs.debian.org/372077 a while > back. We are currently considering upgrading that to RC as we feel we > cannot release D-I Beta3 wile this note is still being displayed for new > installations. > > A reaction would be appreciated. David indeed reacted to a very similar message I posted (see below for my message and answers). My understanding is that David doesn't actually know how to handle this properly to be sure about warning when users upgrade (which seems important). I agree that this should be RC in D-I point of view. We certainly cannot ship with that message displayed on every default install. (personal note: too bad that I'm actually too busy at work and home to meet David who's currently in Paris.....:-|) Date: Sun, 11 Jun 2006 21:49:04 +0200 From: Christian Perrier <email@example.com> To: firstname.lastname@example.org Subject: Annoying warning note in fresh installs I was today testing the fresh install of Etch with the desktop task (D-I related work) and I have been very surprised to see the warning note about "possible problems during the major upgrade". I seem to remember reading Steve Langasek (this was actually Joey Hess) mentioning this, but this is something that definitely should go away, at least on fresh installs..:-) David Nusinow's answer: Right, I don't like it but I don't have a clean fix for it yet. The reason being that x11-common didn't exist in sarge so I can't simply check for an upgrade. Ideally I would look for xserver-common being on the system and put the note up in that case, but that package should be removed prior to x11-common's preinst being run due to the conflicts line. Maybe just checking for libx11 would get around it. Alternately, I think joeyh suggested looking for a running X server for the fix (that may be for a different bug though) but I don't think that's an optimal solution for this problem. Fundamentally, I need to check to see exactly what's in the sarge X packages to find out what we could look for. Joey Hess contribution later: If you don't mind depending on people upgrading with apt (rather than using dpkg directly), you could do the check in the config script, which will run before anything is removed in a dist-upgrade.
Description: Digital signature