public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: how to recover a portage that wasn't in use for very long time
Date: Wed, 13 May 2009 15:16:10 +0100	[thread overview]
Message-ID: <73326D2F-33AC-4BC8-9118-4782D4D700BB@stellar.eclipse.co.uk> (raw)
In-Reply-To: <200905131217.11212.alan.mckinnon@gmail.com>


On 13 May 2009, at 11:17, Alan McKinnon wrote:
> ...
> Why are you doing this? Is it to learn how to cope with such things?
>
> If not, you are really wasting time that you will never get back. ...
>
> Trust me, if this is not a learning exercise, just unmount your data  
> volumes
> and reinstall the machine. The pain is not worth it. Really. ...

I'm inclined to disagree with you here. Obviously, it depends on the  
user - as I've undertaken this, I knew not to bother asking here  
because I knew I'd receive exactly this response. I examined ebuilds  
to see the blockers & looked up compatible versions in the portage  
attic, and I did my own searches when I came to problems like this  
one. And so far I've been ok.

In my case, reinstallation would be a huge pain. I would be massively  
worrying about which services on the machine I need to configure  
again, and whether everything I needed had been backed up properly. I  
have forgotten the original procedures I followed setting up many of  
these services, and it could easily take a week to set the machine up  
from scratch.

If I upgrade the "obsolete portage" incrementally, I know that  
everything is still working, and I update the machine without  
disruption to the users who depend upon the machine. If a service  
fails during the procedure, then it is only ONE service that I have to  
fix, not several. As I upgrade a package & run etc-update I can back  
up the original config files, and if I find the new ones are vastly  
different then I can refer to the originals &/or diff them in.

If this upgrade procedure is undertaken cautiously, then it is no  
worse or different than it was when the changes originally entered the  
portage tree. One can `emerge -pv world` and then emerge the first  
package with --oneshot, rinse & repeat. Sure, this is potentially time- 
consuming, but I can leave packages compiling whilst I'm doing other  
things - reinstalling from scratch a base Gentoo installation isn't  
too bad (hardware, logger, housekeeping), but once you add in a number  
of services then I'm going to need to dedicate some time to the job.

I'm not reading Alexey too clearly, but it seems to me that he is  
saying he has a full system backup. In this case one can restore to  
that in minutes if something goes hosed badly during an emerge or if  
the users come in the next morning & complain that $facility isn't  
working.

I'm NOT saying that this procedure is for everyone, but equally I  
don't think it's fair to say there's NEVER any justification for it.

Stroller.




  reply	other threads:[~2009-05-13 14:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10  0:58 [gentoo-user] how to recover a portage that wasn't in use for very long time Alexey Luchko
2009-05-10  1:54 ` Mike Kazantsev
2009-05-10  1:56   ` Mike Kazantsev
2009-05-10 12:20 ` Stroller
2009-05-10 17:31 ` Alan McKinnon
2009-05-10 19:25   ` [gentoo-user] " Francesco Talamona
2009-05-10 22:31 ` [gentoo-user] " Nick Fortino
2009-05-12 13:56   ` Alexey Luchko
2009-05-13 10:03 ` [gentoo-user] " Alexey Luchko
2009-05-13 10:17   ` Alan McKinnon
2009-05-13 14:16     ` Stroller [this message]
2009-05-13 14:27       ` Alan McKinnon
2009-05-13 14:49         ` Stroller
2009-05-13 15:00           ` Alan McKinnon
2009-05-13 15:14             ` Paul Hartman
2009-05-13 15:30               ` Graham Murray
2009-05-13 15:44                 ` Paul Hartman
2009-05-13 16:55                 ` Neil Bothwick
2009-05-13 14:33   ` Stroller

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=73326D2F-33AC-4BC8-9118-4782D4D700BB@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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