Re: Debian safe-upgrade to 6.0.2 - don't run within X session
On 28/06/11 21:23, D G Teed wrote:
> On Tue, Jun 28, 2011 at 12:25 AM, Scott Ferguson
> <prettyfly.productions@gmail.com
> <mailto:prettyfly.productions@gmail.com>> wrote:
>
>
> Opening a vt will do nothing to "protect" any running x-apps. If
> concerned about x-apps whilst doing an upgrade - logout of x and login
> to a console then shutdown x.
>
>
> I'm afraid users could be confused by this and other statements.
> There is a point to the original post which seems to be missed.
Yes.
You are the only person I'm aware of reporting an incomplete upgrade.
(I've just checked again this morning)
Are you absolutely certain the update of the xserver package caused your
upgrade to fail??
Despite testing on a number of different Gnome and KDE desktops we saw
no problems with the upgrade - with the exception of a lack of a hint in
the Samba upgrade message on how to exit the message. Users were advised
how to exit that screen. If the updatemanager were not a safe and
convenient way to apply the 6.0.2 upgrade with minimal loss of
production - then apt-dater would have been run overnight.
If you did have a problem with that upgrade perhaps you should have
filed a bug report in addition to posting instructions on a work around.
Wheezy and Sid could be treated differently, but stable should be
treated as "it should work" and "if it doesn't work, fix it".
Not all users are administrators - for those users an updatemanager is
the preferred way of doing things.
It is not my intention to be rude by not addressing the many other
points you've made. They just don't seem relevant - even though I'd
digressed by addressing them in a previous post.
And I'm not saying you are being untruthful - but I have yet to find one
other case of an incomplete upgrade or any other problems where a fully
updated, unmixed repository build, required the user to use a vt and cli
to apply the 6.0.2 upgrade.
If you feel strongly that there is a problem (other than the samba
message) - then post your logs and details as a bug report. If there is
not a problem - posting a work-around that advices users to switch to a
vt *does* cause problems in an administered environment. Especially when
commercial vendors seize of the use of cli as a reason not to have
GNU-Linux on the desktop.
Cheers
--
"I just have one of those faces.
People come up to me and say, "What's wrong?"
Nothing.
"Well, it takes more energy to frown than it does to smile."
Yeah, you know it takes more energy to point that out than it does to
leave me alone?"
~ Bill Hicks
Reply to: