From: Johann Schmitz <ercpe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] keep a gen 2013 snapshot on mirrors
Date: Thu, 14 Nov 2013 05:38:08 +0100 [thread overview]
Message-ID: <528453B0.8020105@gentoo.org> (raw)
In-Reply-To: <5283D015.5060102@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> long story short having a portage-20130126.tar.bz2 snapshot
>> (before the EAPI 5 switch) greatly simplified the upgrade of an
>> old server on a client.
I have done the switch to the current profile+portage on many server
recently and i don't think that it is neccessary to keep an old
portage snapshot around. Updating from old portage versions or
profiles isn't fun but it basically boils down to
- - Update python to latest 2.7/3.2
- - Run python-updater and select 2.7/3.2 as the main python version
- - Drop old python version
- - Update Portage, layman, eix
- - Switch to the current profile
- - Update the rest
If you switched to the new profile with an old portage too early
(happens to me *twice*), you will get at some point many blockers due
to EAPI=5 and have to hack either the ebuilds or update portage manually.
> The goal is to be able to update a device for a year. Not updating
> at least once a year is not supportable, and should be discouraged.
> I'm sorry for your pain, I really am, but I hope that it pushes you
> to update twice a year instead of zero times.
I think that even half a year is a very long period in Gentoo.
Updating the core packages (portage, openrc, udev, etc.) on a
(bi-)monthly basis makes sure that you don't run in such troubles.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJShFOwAAoJEKCEBkJ3xQHtVB8H/jTp17a1nuQP8N8wajkG90/o
pc353PvxW/JgRYBKBrdmWEqW0dS1wRsdbPVnZuOkWpWw4CXbXc7fTJ6gualYUx8L
6FgwsGwWRu/WpSVIvu9gYmtc+yWSPv3YBVmdi0d0KfzUU10sAZn74+0tHUKaSglE
TkunxAB6YSGRYj4VC6ZfaFK38gq5owgyzNjLa90rEPY4QFuTum16Y7Jr6RKtQGa1
LuJygufXPGxasW001dUmVTyQUH+vOxF3nWWaaj92zgGf33t67GeY6MMSnwFVXnnr
AYlHykYQr0RmPGmZShAnhr8B3HL7vDdm0CXzmg23noyiT67RqRXOqDJxwTw+29o=
=jQEK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-11-14 4:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 18:58 [gentoo-dev] keep a gen 2013 snapshot on mirrors Francesco R.
2013-11-13 19:12 ` Rich Freeman
2013-11-13 20:49 ` Roy Bamford
2013-11-13 21:18 ` Rich Freeman
2013-11-15 13:17 ` [gentoo-dev] " Duncan
2013-11-15 13:38 ` Rich Freeman
2013-11-15 15:24 ` Duncan
2013-11-15 15:59 ` Peter Stuge
2013-11-14 0:27 ` [gentoo-dev] " Tom Wijsman
2013-11-14 13:17 ` Francesco R.
2013-11-14 14:01 ` Rich Freeman
2013-11-14 13:19 ` Lars Wendler
2013-11-14 19:49 ` Ian Stakenvicius
2013-11-13 19:16 ` Rick "Zero_Chaos" Farina
2013-11-14 4:38 ` Johann Schmitz [this message]
2013-11-14 13:09 ` Francesco R.
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=528453B0.8020105@gentoo.org \
--to=ercpe@gentoo.org \
--cc=gentoo-dev@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