public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update After A Year
Date: Thu, 10 Jan 2008 12:57:57 +0200	[thread overview]
Message-ID: <200801101257.57487.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <b869f3c10801100229q45e10f4bief9a0582b6b8798b@mail.gmail.com>

On Thursday 10 January 2008, Tamas Sarga wrote:
> Hi,
>
> I moved from my flat a year ago, and now I' went back. At my
> temporary place I wasn't be able to reach the internet, so I didn't
> update the system. Now I'd like to update it. Should I do anything
> special in addition to an emerge -e system; emerge -e world? Are
> there anything I should attend to?

Generally you can just emerge -uND world and we done with it. But life 
isn't always so simple. I can think of a few updates in the last while 
that were problematic, but I think they were all more than a year ago:

Xorg 6.x -> 7.x  - there's wiki pages for that at gentoo-wiki.com
gcc-3.3.x -> 3.4.x - check gentoo.org/docs for the full info
glibc-2.3 -> 2.4 - there was something about that too, I forget...
The update to python-2.5 had a specific procedure (?)
And there was a portage update as well with a change in on-disk format. 
This one caught me, as an upgrade path was maintained for several 
versions, then dropped. My upgrade fell in that window. But that was 
way back in the early 2.0 versions, I think you will be safe.

Oddly, kde-3.5.7 to 3.5.8 recently was a pain for me. I hadn't updated 
in two months and the first emerge world failed about 8 times, all on 
kde stuff. It felt as if the DEPENDS were evaluated in the wrong order 
as emerge --resume --skipfirst allowed it to continue. Then I would 
emerge world again with less failures, and do it again. IIRC it took 4 
runs thorough, but once it was done everything did seem to work 
correctly.

With long intervals between updates like you have here, I prefer to make 
a quickpkg of vital system stuff (gcc, glibc, python, portage, bash) as 
a safety measure, then run emerge -pvuND system and update those vital 
packages manually - the reason is to force me to look at the portage 
output and not miss important messages. Then emerge the rest of system 
followed by the rest of world. It's the long way round but it gives me 
the warm fuzzy safety net feeling.


-- 
Alan McKinnon
alan dot mckinnon at gmail dot com
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-01-10 11:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 10:29 [gentoo-user] Update After A Year Tamas Sarga
2008-01-10 10:57 ` Alan McKinnon [this message]
2008-01-10 11:19   ` Neil Bothwick
2008-01-10 19:22     ` [gentoo-user] expat update (was:Update After a Year) b.n.
2008-01-10 19:39       ` Neil Bothwick
2008-01-11  6:49       ` Alan McKinnon
2008-01-11  7:13         ` [gentoo-user] expat update Dale
2008-01-10 23:45     ` [gentoo-user] Update After A Year Hal Martin
2008-01-11  1:17       ` Stroller
2008-01-11  2:04         ` Stroller
2008-01-11  3:58           ` Randy Barlow
2008-01-11 17:30             ` [gentoo-user] " reader
2008-01-10 10:58 ` [gentoo-user] " Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801101257.57487.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox