| 1 |
daid kahl <daidxor@×××××.com> writes: |
| 2 |
|
| 3 |
>> Don't worry about it. I'm not sure if portage-2.1.9.20 will deal with this |
| 4 |
>> automagically (I *think* it does these days and 2.2 definitely does) but if |
| 5 |
>> not just |
| 6 |
>> |
| 7 |
>> emerge -C shadow ; emerge -1 shadow |
| 8 |
>> |
| 9 |
>> then emerge -avuND world. |
| 10 |
>> |
| 11 |
>> No good technical reason for doing shadow first apart from getting it over and |
| 12 |
>> done with while you watch and confirm it works fine. Then do world and wander |
| 13 |
>> over to the kettle letting portage go on with doing it's thing unattended |
| 14 |
> |
| 15 |
> For my own comfort, on a case like this, if I didn't have the portage |
| 16 |
> FEATURE buildpkg or buildsyspkg turned on, I'd make sure that was on |
| 17 |
> and that I had a functional backup of shadow to install from binary, |
| 18 |
> in case something went very wrong. But I tend to be extremely |
| 19 |
> cautious in terms of how I maintain my system, and a lot of that |
| 20 |
> caution is just paranoia. |
| 21 |
|
| 22 |
Thanks for the advice. I do use quickpkg as well. |
| 23 |
|
| 24 |
allan |
Archives