| 1 |
El mar, 19-02-2013 a las 14:27 -0800, Zac Medico escribió: |
| 2 |
> On 02/19/2013 12:12 PM, Pacho Ramos wrote: |
| 3 |
> > Hello |
| 4 |
> > |
| 5 |
> > For some time I am running portage-2.1.x with preserve-libs enabled to |
| 6 |
> > test it and try to prevent revdep-rebuild usage. Until now, I haven't |
| 7 |
> > had any problems with it, but I started to test it after being running |
| 8 |
> > udev-19x for a long time. Yesterday, my father mailed me because he got |
| 9 |
> > udev update from 17x to 19x and emerge @preserved-rebuild only rebuilt |
| 10 |
> > gcc, keeping other broken packages untouched (while revdep-rebuild |
| 11 |
> > rebuilt them) |
| 12 |
> > |
| 13 |
> > Do you know what kind of information could I demand him to help diagnose |
| 14 |
> > the problem? |
| 15 |
> |
| 16 |
> It only works if the broken packages have references to the libudev.so.0 |
| 17 |
> (or maybe libgudev-1.0.so.0) soname in their |
| 18 |
> /var/db/pkg/*/*/NEEDED.ELF.2 files. |
| 19 |
|
| 20 |
Will need to recheck in next breakage then :/ |
| 21 |
|
| 22 |
Any suggestion about how to proceed when I hit this kind of problem? (I |
| 23 |
mean, what can I provide you to try to fix this cases) |
| 24 |
|
| 25 |
Thanks |
Archives