| 1 |
On Saturday 13 Aug 2016 16:26:21 hw wrote: |
| 2 |
> Andreas K. Hüttel schrieb: |
| 3 |
> > If you see this now, your production server hasn't been updated for a |
| 4 |
> > long time... |
| 5 |
> |
| 6 |
> About 1.5 years --- not really a long time. |
| 7 |
|
| 8 |
Au contraire. In a Gentoo world, this is comparable with the age of the |
| 9 |
universe. And leaving it that long almost guarantees that you'll have |
| 10 |
problems. (I update my system daily, but that's because I don't have |
| 11 |
anything more useful to do with my time. :) ) |
| 12 |
|
| 13 |
> > As a last resort, you should be able to run a "non-installed" portage |
| 14 |
> > version to update your system once. Manually download and unpack a |
| 15 |
> > recent portage tarball somewhere temporary and then run as root |
| 16 |
> > something like |
| 17 |
> > |
| 18 |
> > porto tmp # ./portage-2.3.0/bin/emerge -uDNav world |
| 19 |
> > |
| 20 |
> > This can update your system to the newest state, including updating the |
| 21 |
> > installed portage. Afterwards you won't need the temporarily unpacked |
| 22 |
> > portage anymore. |
| 23 |
> > |
| 24 |
> > Disclaimer: I haven't tested this for a while. It may delete your data, |
| 25 |
> > kill kittens or turn the sun into a nova. No guarantees made. |
| 26 |
> |
| 27 |
> Interesting idea :) I´d be afraid that this version of portage might |
| 28 |
> find files of the regular installation and get confused and kill the |
| 29 |
> kittens ... |
| 30 |
|
| 31 |
That's the idea, isn't it? You need it to root out the out-of-date bits and |
| 32 |
substitute new ones. It sounds like a rational scheme to me, especially if |
| 33 |
you quickpkg portage to keep some kittens wrapped up in the warm. |
| 34 |
|
| 35 |
-- |
| 36 |
Rgds |
| 37 |
Peter |
Archives