| 1 |
On Saturday 06 June 2009 18:23:26 walt wrote: |
| 2 |
> William Kenworthy wrote: |
| 3 |
> > After each update, these appear, and for libusb, the number slowly |
| 4 |
> > increases (up to 185 now). so far I have done the suggested "emerge |
| 5 |
> > @preserved-rebuild", plus tried rebuilding every package mentioned but |
| 6 |
> > after building, there is no change ... |
| 7 |
> > |
| 8 |
> > !!! existing preserved libs: |
| 9 |
> >>>> package: dev-libs/libusb-0.1.12-r5 |
| 10 |
> > |
| 11 |
> > * - /lib/libusb.so |
| 12 |
> > * used by /lib/udev/check-mtp-device (media-libs/libgphoto2-2.4.3) |
| 13 |
> > * used by /usr/bin/dfutool (net-wireless/bluez-utils-3.36) |
| 14 |
> > * used by /usr/bin/evolution (mail-client/evolution-2.26.2) |
| 15 |
> > * used by 185 other files |
| 16 |
> > |
| 17 |
> >>>> package: x11-libs/libXaw-1.0.5 |
| 18 |
> > |
| 19 |
> > * - /usr/lib/libXaw.so.8 |
| 20 |
> > * - /usr/lib/libXaw8.so |
| 21 |
> > * - /usr/lib/libXaw8.so.8 |
| 22 |
> > * - /usr/lib/libXaw8.so.8.0.0 |
| 23 |
> > * used by /usr/bin/xgpsspeed (sci-geosciences/gpsd-2.38) |
| 24 |
> > Use emerge @preserved-rebuild to rebuild packages using these libraries |
| 25 |
> > rattus ~ # |
| 26 |
> |
| 27 |
> Are you using an unstable version of gentoo, e.g. ~x86 or ~amd64? The |
| 28 |
> only reason I know of for 'preserving' an old version is if there is also |
| 29 |
> a newer one, i.e. libusb-1.0.1, which is a ~ version. |
| 30 |
> |
| 31 |
> On my ~amd64 machine I had both libusb-0.1.12-r5 and libusb-1.0.1. |
| 32 |
> I just deleted the 0.1.12 and revdep-rebuild found and rebuilt usbutils, |
| 33 |
> hal, and sane-backends with no problems, so there seems to be no reason |
| 34 |
> to have the old version unless you perhaps have the new version masked |
| 35 |
> on your machine for some reason? |
| 36 |
|
| 37 |
Your assessment of the problem is incorrect. preserved-rebuild happens when |
| 38 |
you upgrade a package which other packages link to and causes brokenness. When |
| 39 |
the "used by" package is rebuilt, there is no need for the old live version to |
| 40 |
be kept (it's only consumers no longer do so) so it is unmerged. |
| 41 |
|
| 42 |
Think of it this way: |
| 43 |
revdep-rebuild finds broken packages after the fact when they are already |
| 44 |
broken. |
| 45 |
preserved-rebuild detects those problems before they occur and takes measure |
| 46 |
to keep the system working meanwhile. |
| 47 |
|
| 48 |
You will notice that after running "emerge @preserved-rebuild", revdep-rebuild |
| 49 |
almost invariably returns null results. |
| 50 |
|
| 51 |
As for the OP, I can only guess what might be causing this. Let's start with |
| 52 |
obvious stuff: |
| 53 |
|
| 54 |
1. Is portage the latest version for your arch? |
| 55 |
2. What does revdep-rebuild return? |
| 56 |
3. What is your arch, and is it a mixture of stable and ~? |
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
alan dot mckinnon at gmail dot com |
Archives