| 1 |
Am Thu, 27 Jul 2017 17:14:17 +0200 |
| 2 |
schrieb Arve Barsnes <arve.barsnes@×××××.com>: |
| 3 |
|
| 4 |
> > |
| 5 |
> > On Thursday 27 Jul 2017 09:48:43 symack wrote: |
| 6 |
> > > There must be an easy way to do this. Something like download the |
| 7 |
> > > latest portage and source package. Untar on live system and |
| 8 |
> > > rebuild! That would be so amazing if possible. |
| 9 |
> > |
| 10 |
> |
| 11 |
> It does not seem like the installation is super old, maybe worth a |
| 12 |
> try to update the portage tree in steps, by pulling from git at some |
| 13 |
> set intervals, and just do updates after each sync. |
| 14 |
|
| 15 |
Is there a list of portage timestamps which would break upgrading old |
| 16 |
systems? |
| 17 |
|
| 18 |
My idea would be to download portage trees from specific points in |
| 19 |
time, run an upgrade, then download the next, until I'm back in a sane |
| 20 |
state to do normal sync and update. |
| 21 |
|
| 22 |
|
| 23 |
-- |
| 24 |
Regards, |
| 25 |
Kai |
| 26 |
|
| 27 |
Replies to list-only preferred. |
Archives