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