| 1 |
On 01/29/2017 03:33 PM, Alan McKinnon wrote: |
| 2 |
> On 30/01/2017 00:25, Frank Steinmetzger wrote: |
| 3 |
>> On Sun, Jan 29, 2017 at 03:32:22PM -0600, Dale wrote: |
| 4 |
>> |
| 5 |
>>>>> I haven't updated my system for over a year (1year and 3-months). |
| 6 |
>>>>> I was trying to upgrade my firefox-bin and I'm already running into problems. |
| 7 |
>>>>> |
| 8 |
>>>>> What is my best option, re-install from scratch, upgrade in stages etc. |
| 9 |
>>>>> With firefox-bin I'm getting: |
| 10 |
>>>> |
| 11 |
>>>> 1 year 3 months isn't usually that bad and it can be done - I've done it |
| 12 |
>>>> many times myself. However there are gotchas: |
| 13 |
>>>> […] |
| 14 |
>>>> - go slowly and deal with one block at a time. A regular emerge world |
| 15 |
>>>> probably won't succeed so you gotta bite of small chunks |
| 16 |
>>>> |
| 17 |
>>>> With those basics out the way, it's a great learning experience. I |
| 18 |
>>>> recommend you do it at least once. |
| 19 |
>>> |
| 20 |
>>> Might I also add, the -t option can reveal what is causing what |
| 21 |
>>> sometimes. |
| 22 |
>> |
| 23 |
>> Add --unordered-display to that (I put it into my emerge default options). |
| 24 |
>> It will shrink the output by removing duplicate [nomerge] lines and give you |
| 25 |
>> an easier to understand overview. |
| 26 |
>> |
| 27 |
>> A short while ago I updated an old netbook that hadn't seen any action in |
| 28 |
>> probably 2 years. It took a while (I cloned the HDD and compiled on my main |
| 29 |
>> rig), but I prevailed, inlcuding KDE 4 upgrades. |
| 30 |
>> |
| 31 |
>>> Also, I'd start with @system first, then work on @world. |
| 32 |
>> |
| 33 |
>> I use custom sets (basic tools, system utilities, X stuff, media players |
| 34 |
>> etc) and dealt with one of them at a time, starting with the less intricate |
| 35 |
>> ones. |
| 36 |
>> |
| 37 |
>>> Only bad thing is, KDE, if you have it installed, is in @system because |
| 38 |
>>> of dependencies, last I checked anyway. |
| 39 |
>> |
| 40 |
>> Uhm, KDE will not become part of @system, but you probably can't update kde |
| 41 |
>> without @system first. Much fun comes from the package renaming from |
| 42 |
>> kde-base to kde-apps, and now KDE4 isn't even in the tree anymore. (The OP |
| 43 |
>> hasn't stated whether he actually uses KDE, though.) |
| 44 |
> |
| 45 |
> |
| 46 |
> KDE isn't IN @system, but gets pulled in if you use --update --deep |
| 47 |
> |
| 48 |
> However, there's a way out. @system is a defined set of packages (about |
| 49 |
> 50 or so), not a list of stuff plus all it's deps. So do this: |
| 50 |
> |
| 51 |
> emerge @system |
| 52 |
> |
| 53 |
> That should keep everything except the list of system packages out of |
| 54 |
> the dep graph |
| 55 |
|
| 56 |
Thank you Alan for suggestion. Indeed "emerge @system" it limits number |
| 57 |
of packages to be upgraded. |
| 58 |
|
| 59 |
-- |
| 60 |
Thelma |
Archives