We need to document how people will be expected to upgrade server installation, IMO.* I tried this evening and udev blew up.* I can probably work around it, but I think we should have this in the server guide (and other places).


I did try googling around the wiki and h.u.c, but found only references to using update-manager, which comes with a ton of gui dependencies, and so I assume is oriented to the desktop, so if there is documentation, it should be more prominent.


tia,
dan
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

On Feb 3, 2008 1:08 AM, Dan Trevino <dantrevino@gmail.com> wrote:

We need to document how people will be expected to upgrade server installation, IMO.* I tried this evening and udev blew up.* I can probably work around it, but I think we should have this in the server guide (and other places).



I did try googling around the wiki and h.u.c, but found only references to using update-manager, which comes with a ton of gui dependencies, and so I assume is oriented to the desktop, so if there is documentation, it should be more prominent.



tia,
dan

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server

More info: https://wiki.ubuntu.com/ServerTeam
I wonder if this is currently covered in the server guide?* I think it should be

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Me too.
It will be very critical.

El dom, 03-02-2008 a las 13:58 -0500, Jonathan Jesse escribió:
>
>
> On Feb 3, 2008 1:08 AM, Dan Trevino <dantrevino@gmail.com> wrote:
> We need to document how people will be expected to upgrade
> server installation, IMO. I tried this evening and udev blew
> up. I can probably work around it, but I think we should have
> this in the server guide (and other places).
>
> I did try googling around the wiki and h.u.c, but found only
> references to using update-manager, which comes with a ton of
> gui dependencies, and so I assume is oriented to the desktop,
> so if there is documentation, it should be more prominent.
>
> tia,
> dan
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam
> I wonder if this is currently covered in the server guide? I think it
> should be
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam



--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

I'd be happy to see a guide like that. I usually install the server edition and tweak it to my own preference, not actually using as a server

On Feb 4, 2008 10:18 PM, ultramajestic <ultramajestic@yahoo.es> wrote:

Me too.
It will be very critical.

El dom, 03-02-2008 a las 13:58 -0500, Jonathan Jesse escribió:

>
>
> On Feb 3, 2008 1:08 AM, Dan Trevino <dantrevino@gmail.com> wrote:
> * * * * We need to document how people will be expected to upgrade

> * * * * server installation, IMO. *I tried this evening and udev blew
> * * * * up. *I can probably work around it, but I think we should have
> * * * * this in the server guide (and other places).
>

> * * * * I did try googling around the wiki and h.u.c, but found only
> * * * * references to using update-manager, which comes with a ton of
> * * * * gui dependencies, and so I assume is oriented to the desktop,

> * * * * so if there is documentation, it should be more prominent.
>
> * * * * tia,
> * * * * dan
> * * * * --
> * * * * ubuntu-server mailing list
> * * * * ubuntu-server@lists.ubuntu.com

> * * * * https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> * * * * More info: https://wiki.ubuntu.com/ServerTeam

> I wonder if this is currently covered in the server guide? *I think it
> should be
> --
> ubuntu-server mailing list
> ubuntu-server@lists.ubuntu.com

> https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
> More info: https://wiki.ubuntu.com/ServerTeam




--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server

More info: https://wiki.ubuntu.com/ServerTeam

--
- nd.
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

On Sun, Feb 03, 2008 at 01:08:12AM -0500, Dan Trevino wrote:
> We need to document how people will be expected to upgrade server
> installation, IMO. I tried this evening and udev blew up. I can probably
> work around it, but I think we should have this in the server guide (and
> other places).

Agreed - It should be documented in the Server guide. Usually there is
also a note in the Release Notes (it was the case for Gusty).

> I did try googling around the wiki and h.u.c, but found only references to
> using update-manager, which comes with a ton of gui dependencies, and so I
> assume is oriented to the desktop, so if there is documentation, it should
> be more prominent.

The supported way to perform an upgrade is to use the command
do-release-upgrade. It comes with the update-manager-core package, that
doesn't have any graphical dependencies. The package should be installed
by default on a server.

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Hello,
*
Agreed - It should be documented in the Server guide. Usually there is

also a note in the Release Notes (it was the case for Gusty).


Attached is a diff adding an "Upgrading" section under the Installation section.* Basically it gives an overview of the do-release-upgrade command and why to use it.* If it looks good to everyone I'll go ahead and commit it.

--
Party On,
Adam
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Hi Adam,

On Mon, Feb 04, 2008 at 11:12:18AM -0500, Adam Sommer wrote:
> Attached is a diff adding an "Upgrading" section under the Installation
> section. Basically it gives an overview of the do-release-upgrade command
> and why to use it. If it looks good to everyone I'll go ahead and commit
> it.

> === modified file 'generic/server/C/installation.xml'
> --- generic/server/C/installation.xml 2007-12-12 17:17:38 +0000
> +++ generic/server/C/installation.xml 2008-02-04 16:03:38 +0000
> @@ -312,4 +312,42 @@
> </screen>
> </sect2>
> </sect1>
> + <sect1 id="installing-upgrading" status="review">
> + <title>Upgrading</title>
> + <para>
> + There are several ways to upgrade from one Ubuntu release to another. This section gives an overview of the supported upgrade method.
> + </para>

I'd mention that although dist-upgrade is available, it shouldn't be
used. We've seen some request on #ubuntu-server about fixing a
dist-upgrade failure. The basic answer is to use do-release-upgrade
instead of dist-upgrade.

People coming from a debian background are used to dist-upgrade.

> + <para>
> + Using <application>do-release-upgrade</application> is recommended is because it has the ability to handle one time
> + configuration changes to the system. For example, the <application>evms</application> package needed to be removed when
> + upgrading from Ubuntu 7.06 to Ubuntu 7.10. If the package was not removed during the upgrade the system could be left in
> + a non-bootable state.
> + </para>

I wouldn't explain why do-release-upgrade is better.

> + <para>
> + It is also possible to use <application>do-release-upgrade</application> to upgrade to a development version of
> + Ubuntu. To accomplish this use the <emphasis>-d</emphasis> switch:
> + </para>
> +<screen>
> +<command>do-release-upgrade -d</command>
> +</screen>
> + <warning>
> + <para>
> + Upgrading to a development release is <emphasis>not</emphasis> recommended for production environments.
> + </para>
> + </warning>

I like the mention about upgrading to the development version of Ubuntu.

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Mathias Gug wrote:
> I'd mention that although dist-upgrade is available, it shouldn't be
> used. We've seen some request on #ubuntu-server about fixing a
> dist-upgrade failure. The basic answer is to use do-release-upgrade
> instead of dist-upgrade.
>
> People coming from a debian background are used to dist-upgrade.

I have no Debian background but there are *lots* of docs around
recommending dist-upgrade on Ubuntu. In fact, following those guides is
how I did my upgrades from 4.10->5.04->5.10. Not always cleanly.

A couple of examples:
https://help.ubuntu.com/community/DapperUpgrades
https://help.ubuntu.com/community/HoaryUpgradeNotes

We seem to be on about the third or fourth iteration on the "correct"
way to do an upgrade.

Thanks and sorry for the rant,
Michael

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

On Monday 04 February 2008 11:43, Mathias Gug wrote:

> I'd mention that although dist-upgrade is available, it shouldn't be
> used. We've seen some request on #ubuntu-server about fixing a
> dist-upgrade failure. The basic answer is to use do-release-upgrade
> instead of dist-upgrade.

JFTR, I did Dapper -> Edgy -> Feisty -> Gutsy over the weekend on a Kubuntu
box using dist-upgrade. Dapper --> Edgy took some manual installing of
packages to get through and Edgy --> Feisty and Feisty --> Gutsy just worked.

I'd suggest that while dist-upgrade isn't the official way, it generally works
and to the extent it doesn't it's because of packaging problems we ought to
investigate and try to fix.

do-release-upgrade automates updating sources.list and works through a bunch
of special cases AFAICT. I'd suggest that making dist-upgrade work is a good
goal for improving the quality of our packaging. We probably won't get
there, but to the extent we get closer it makes do-release-upgrade's job
easier and lower risk.

Scott K

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

Thanks for the feedback Mathias,


I wouldn't explain why do-release-upgrade is better.



My intent was to explain why do-release-upgrade is recommended.* But I agree an example isn't strictly necessary.* Anyway, here's an updated diff, I also mentioned dist-upgrade.

Let me know what you think.

--
Party On,
Adam
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam