1 |
Looks like that got it guys. Thanks tons for the help.... It seems I broke |
2 |
portage by running only part ~amd64 packages. revdep-rebuild found it but it |
3 |
took twice to fix..... depclean wants to get rid of tons of stuff though so |
4 |
I'm thinking this is a bad idea or I have bigger problems.... Kudos to AMD64 |
5 |
Gentoo for the best support team in open source. |
6 |
|
7 |
Nick |
8 |
|
9 |
On 11/1/05, Duncan <1i5t5.duncan@×××.net> wrote: |
10 |
> |
11 |
> Brian Litzinger posted <20051101173928.GA13381@localhost>, excerpted |
12 |
> below, on Tue, 01 Nov 2005 09:39:29 -0800: |
13 |
> |
14 |
> > Been ~amd64 since the day I got this laptop. |
15 |
> > |
16 |
> > The last time I hit the problem was on |
17 |
> > |
18 |
> > lrwxrwxrwx 1 root root 15 Oct 21 14:43 /usr/lib/libungif.so.4 -> |
19 |
> > libgif.so.4.1.3 |
20 |
> > |
21 |
> > when I finally got tired and created the link. |
22 |
> > |
23 |
> > Thus on Oct 21st at 13:43 (PST) you could still experience the |
24 |
> > problem as a ~amd64 type. |
25 |
> > |
26 |
> > I got slapped in the face as a small child for filing a duplicate |
27 |
> > bug. Thus I am, as an adult, unable to file bugs. :( |
28 |
> |
29 |
> Did you do what I and others have suggested, a revdep-rebuild? Note that |
30 |
> existing packages on your system may still be linked against the old |
31 |
> library. Once it's in their binaries... |
32 |
> |
33 |
> revdep-rebuild (as with anything portage related, run it with the -p the |
34 |
> first time thru to see what it's going to do) is designed to scan your |
35 |
> existing binaries to see what they need, and your existing library path |
36 |
> (that ld uses to find the libs it needs) to see what's provided. Then it |
37 |
> makes a list of all the binaries (both executables, and libs that load |
38 |
> other libs) that have unfilled dependencies using the existing libraries, |
39 |
> traces down the packages they belong to, and remerges them (or with -p, |
40 |
> displays what it would merge), the intent being to recompile and relink |
41 |
> anything that's missing dependencies, either linking against new or |
42 |
> alternate versions of same, or pulling in the required dependencies to |
43 |
> merge as well. |
44 |
> |
45 |
> Of course, this only works once that library has gone missing. If you run |
46 |
> revdep-rebuild with the library (or a symlink pointing to an alternate) |
47 |
> still there, it'll think everything is fine and not list the package |
48 |
> owning the library in question for remerge. |
49 |
> |
50 |
> Decently updated packages that formerly linked against libungif should now |
51 |
> link against libgif without difficulty. However, with existing package on |
52 |
> the system linked against libungif, it's only to be expected that said |
53 |
> binaries would have issues. The easiest way to fix them is to run |
54 |
> revdep-rebuild. In fact, revdep-rebuild, along with emerge --newuse |
55 |
> --update --deep world, should be a regular part of the routine to keep a |
56 |
> well maintained and upto date system. |
57 |
> |
58 |
> (Another part of the same routine should be emerge depclean, but be sure |
59 |
> the revdep-rebuild and emerge --newuse are completed first, and check the |
60 |
> output of a --pretend depclean for stuff you know you want to keep around, |
61 |
> before letting it do its thing. Then run revdep-rebuild again afterward, |
62 |
> just to be sure.) |
63 |
> |
64 |
> These apply to some degree to everyone, but a bit less to slower moving |
65 |
> stable, than to faster moving ~arch. Since ~arch may merge three versions |
66 |
> for every version that goes stable, including beta and rc versions on |
67 |
> occasion, cruft tends to buildup rather faster than it will on a stable |
68 |
> system. |
69 |
> |
70 |
> -- |
71 |
> Duncan - List replies preferred. No HTML msgs. |
72 |
> "Every nonfree program has a lord, a master -- |
73 |
> and if you use the program, he is your master." Richard Stallman in |
74 |
> http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
75 |
> |
76 |
> |
77 |
> -- |
78 |
> gentoo-amd64@g.o mailing list |
79 |
> |
80 |
> |