Il 14/11/2013 05:38, Johann Schmitz ha scritto:
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.
Updating from old portage versions or
profiles isn't fun but it basically boils down to
Il 13/11/2013 20:12, Rich Freeman ha scritto:
On Wed, Nov 13, 2013 at 1:58 PM, Francesco R. viv...@gmail.com wrote:
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.
Why not keep a copy on the
Am Wed, 13 Nov 2013 14:12:24 -0500
schrieb Rich Freeman ri...@gentoo.org:
On Wed, Nov 13, 2013 at 1:58 PM, Francesco R. viv...@gmail.com
wrote:
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
On Thu, Nov 14, 2013 at 8:17 AM, Francesco R. viv...@gmail.com wrote:
Rich, that made me smile, none of my remote machine has cvs since a
_very_ long time say 2006.
We are speaking of box that have troubles to emerging anything new, plus
me and most of the internet barely remember cvs up :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 14/11/13 08:19 AM, Lars Wendler wrote:
Once you go the route to use mirror://gentoo in ebuilds as
SRC_URI people are screwed as soon as the ebuild vanishes from
portage. I'd love to see this (mis-)behavior being more vigorously
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.
Why not keep a copy on the servers? I mean
http://distfiles.gentoo.org/snapshots/
thanks,
Francesco Riosa
On Wed, Nov 13, 2013 at 1:58 PM, Francesco R. viv...@gmail.com wrote:
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.
Why not keep a copy on the servers? I mean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/13/2013 01:58 PM, Francesco R. wrote:
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.
Why not keep a copy on the servers? I mean
On 2013.11.13 19:12, Rich Freeman wrote:
[snip]
Going back in time with portage is the easy part - it is in CVS.
The real problem is all the distfiles themselves, especially things
like out-of-tree patch tarballs hosted by devs.
Rich
Rich,
The GPL obliges us to keep such patches
On Wed, Nov 13, 2013 at 3:49 PM, Roy Bamford neddyseag...@gentoo.org wrote:
The GPL obliges us to keep such patches around for three years, iirc.
Don't we do that ?
Why? We own the copyright on the patches (to whatever degree that
they're copyrightable), so we don't need a license to
On Wed, 13 Nov 2013 14:12:24 -0500
Rich Freeman ri...@gentoo.org wrote:
On Wed, Nov 13, 2013 at 1:58 PM, Francesco R. viv...@gmail.com
wrote:
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
-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
12 matches
Mail list logo