| 1 |
On Fri, 03 Jul 2015 19:20:21 -0500 |
| 2 |
Brent Busby <brent@×××××××××.org> wrote: |
| 3 |
|
| 4 |
> Tiago Marques <tiagomnm@×××××.com> writes: |
| 5 |
> |
| 6 |
> > Besides that, were you actually able to use the desktop? A good while |
| 7 |
> > back I was having issues with newer GCCs, HAL, consolekit and other |
| 8 |
> > parts of the desktop's subsystem. |
| 9 |
> > |
| 10 |
> > My experience is ABI_X86 has unfortunately introduced conflicts |
| 11 |
> > everywhere, not just on this overlay. |
| 12 |
> |
| 13 |
> But I've got no solution for this. It doesn't appear to be all |
| 14 |
> multilib's fault though. It looks like all packages that used to be |
| 15 |
> under kde-base/ in main Portage are now under kde-apps/, and this |
| 16 |
> expectation has carried across into the overlay somehow. Since the |
| 17 |
> overlay is not updated for this, it's causing most of KDE 3 to appear to |
| 18 |
> be missing to Portage...or at least that's how it looks so far. |
| 19 |
|
| 20 |
It's fixable: |
| 21 |
|
| 22 |
cd /var/db/pkg/ |
| 23 |
cp -r kde-apps/* kde-base/ |
| 24 |
|
| 25 |
The last set of profile changes performed a slot-move on a bunch of KDE |
| 26 |
packages in a way that was inappropriate for KDE3. This copies the files |
| 27 |
involved back to their old locations, making Portage acknowledge the packages |
| 28 |
under their old names again. Check kde-base afterwards for unmoored |
| 29 |
symlinks and delete any you find. |
| 30 |
|
| 31 |
E. Liddell |
Archives