| 1 |
On Fri, Nov 19, 2010 at 12:17 PM, Alan McKinnon <alan.mckinnon@×××××.com>wrote: |
| 2 |
|
| 3 |
> Apparently, though unproven, at 20:54 on Friday 19 November 2010, Allan |
| 4 |
> Gottlieb did opine thusly: |
| 5 |
> |
| 6 |
> > > It seems, however, that you're still going down the path of emerge |
| 7 |
> > > |
| 8 |
> > > -e @world. Why is that? If it's just to be confident that everything |
| 9 |
> > > is back to the way it should be then I understand that. I've done it |
| 10 |
> > > myself many times in the last 12 years. |
| 11 |
> > |
| 12 |
> > Yes that is the reason. |
| 13 |
> |
| 14 |
> |
| 15 |
> Sounds like the big guns approach, can be valid at times. |
| 16 |
> |
| 17 |
> I'm usually the first one to chip in about emerge -e world being stupid |
| 18 |
> when |
| 19 |
> someone reads the gcc upgrade guide, but sometimes you have a box that just |
| 20 |
> will not fix itself despite hours of troubleshooting. In a case like this a |
| 21 |
> full remerge often fixes mysterious but actual real problems. |
| 22 |
> |
| 23 |
> |
| 24 |
I've had pretty much the same thing happen. In my case, 'eix' showed that I |
| 25 |
had 0.9.8p and 1.0.0 installed |
| 26 |
in two different slots. However the 3 files that belong to 0.9.8 were |
| 27 |
missing. Fortunately, I run with --buildpkg |
| 28 |
so I had a binary package lying around. Emerging it with -gK restored the |
| 29 |
files, and everything was okay. |
| 30 |
|
| 31 |
OTOH, a couple of years ago I did an emerge -e and regretted it. It kept |
| 32 |
stopping because something wasn't |
| 33 |
configured right, and I had to go through dispatch-conf on everything up to |
| 34 |
that point before I could get it to |
| 35 |
proceed. Good luck with your "few days". Mine was more like 2 weeks of |
| 36 |
stop-and-go. |
| 37 |
|
| 38 |
-- |
| 39 |
Kevin O'Gorman, PhD |
Archives