| 1 |
on 05/21/2012 08:49 PM Michael Mol wrote the following: |
| 2 |
> On Mon, May 21, 2012 at 1:28 PM, Thanasis <thanasis@××××××××××.org> wrote: |
| 3 |
>> After a recent update of dev-libs/libffi from version 3.0.10 to 3.0.11 |
| 4 |
>> the ebuild log suggests to run: |
| 5 |
>> |
| 6 |
>> # revdep-rebuild --library '/usr/lib64/libffi.so.5' |
| 7 |
>> |
| 8 |
>> and once finished running revdep-rebuild, it should be safe to |
| 9 |
>> delete the old libraries, like so: |
| 10 |
>> |
| 11 |
>> # rm '/usr/lib64/libffi.so.5' |
| 12 |
>> |
| 13 |
>> However by querying: |
| 14 |
>> |
| 15 |
>> equery b /usr/lib/libffi.so.5 |
| 16 |
>> * Searching for /usr/lib/libffi.so.5 ... |
| 17 |
>> dev-libs/libffi-3.0.11 (/usr/lib64/libffi.so.5) |
| 18 |
>> |
| 19 |
>> we see that /usr/lib64/libffi.so.5 is reported as belonging to |
| 20 |
>> dev-libs/libffi-3.0.11. Is that normal? |
| 21 |
> |
| 22 |
> I think so. It might be clearer if equery omitted the version number, |
| 23 |
> or if it tracked which versions of a package a file belonged to. |
| 24 |
|
| 25 |
So, are you saying that libffi.so.5 does *not* actually belong to |
| 26 |
dev-libs/libffi-3.0.11 ? |
| 27 |
|
| 28 |
> |
| 29 |
> (If I'm wrong, then I suspect you found a bug) |
| 30 |
> |
| 31 |
> |
Archives