| 1 |
Neil Bothwick ha scritto: |
| 2 |
> On Sun, 27 Dec 2009 12:55:23 +0000, bn wrote: |
| 3 |
> |
| 4 |
>> ...I would like to update the thing piece-by-piece, to troubleshoot |
| 5 |
>> better whatever happens. |
| 6 |
> Start with a system update, then emerge --oneshot individual, |
| 7 |
> non-QT, packages to reduce the number of packages in the big emerge. |
| 8 |
> |
| 9 |
>>> If not, you can either |
| 10 |
>>> unmask portage, emerge portage and try again, or if you don't like |
| 11 |
>>> that approach, you must do it the older, longer way: |
| 12 |
>> I could do it, if I have some safety option that allows me to downgrade |
| 13 |
>> portage later, in case I find problems. I am quite conservative with |
| 14 |
>> this system (it's a machine I use for day-to-day work) and I wouldn't |
| 15 |
>> like to have it borked. |
| 16 |
> |
| 17 |
> Install and run demerge, then quickpkg your existing installed packages. |
| 18 |
> Demerge lets you roll back to any point at which you saved its config. |
| 19 |
|
| 20 |
I solved the block by unmerging and re-merging the qt's and then |
| 21 |
re-emerging all of KDE (for other qt software, I have to find it). |
| 22 |
|
| 23 |
Thanks a lot for your tips -didn't know of demerge, and I will for sure |
| 24 |
install it for the future. |
| 25 |
|
| 26 |
m. |
Archives