| 1 |
On Mon, Mar 21, 2011 at 8:03 AM, Helmut Jarausch |
| 2 |
<jarausch@××××××××××××××××.de> wrote: |
| 3 |
> On 03/21/2011 10:19:07 AM, Helmut Jarausch wrote: |
| 4 |
>> Hi, |
| 5 |
>> |
| 6 |
>> probably, portage-2.2.0_alpha28 has broken my system. |
| 7 |
>> |
| 8 |
>> I have reinstalled a binary version of portage-2.2.0_alpha27, but ... |
| 9 |
>> |
| 10 |
>> For many packages, portage installs libraries into /usr instead of |
| 11 |
>> /usr/lib64 or /usr/lib32 |
| 12 |
>> |
| 13 |
>> Probably, the function get_libdir |
| 14 |
>> (defined in /usr/portage/eclass/multilib.eclass) |
| 15 |
>> returns an empty string. |
| 16 |
>> |
| 17 |
> |
| 18 |
> I've just nuked /usr/portage/profile and restored it from a |
| 19 |
> machine which hasn't been updated the last few days. |
| 20 |
> |
| 21 |
> Now, it looks as if this has fixed my machine. |
| 22 |
> |
| 23 |
> So, beware of portage-2.2.0_alpha28 ! |
| 24 |
> |
| 25 |
> Helmut. |
| 26 |
> |
| 27 |
> |
| 28 |
|
| 29 |
vapier made some changes to the multilib profile stuff around 20 hours |
| 30 |
ago. Maybe related? |
Archives