1 |
Apparently, though unproven, at 23:10 on Sunday 12 December 2010, |
2 |
covici@××××××××××.com did opine thusly: |
3 |
|
4 |
> Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
5 |
> > Apparently, though unproven, at 22:35 on Sunday 12 December 2010, |
6 |
> > |
7 |
> > covici@××××××××××.com did opine thusly: |
8 |
> > > Mark Knecht <markknecht@×××××.com> wrote: |
9 |
> > > > On Sun, Dec 12, 2010 at 10:48 AM, <covici@××××××××××.com> wrote: |
10 |
> > > > > I have a fair number of preserved-libs, but it will not run at all |
11 |
> > > > > and gives the rather strange message: |
12 |
> > > > > Calculating dependencies... done! |
13 |
> > > > > |
14 |
> > > > > emerge: there are no ebuilds to satisfy "dev-tex/mplib:0". |
15 |
> > > > > (dependency required by "@preserved-rebuild") |
16 |
> > > > > |
17 |
> > > > > Now I have no such package and an eix seems to indicate that there |
18 |
> > > > > is no such, so how do I get this rebuild going again? |
19 |
> > > > > |
20 |
> > > > > Thanks in advance for all your help. |
21 |
> > > > > |
22 |
> > > > > -- |
23 |
> > > > > Your life is like a penny. You're going to lose it. The question |
24 |
> > > > > is: How do |
25 |
> > > > > you spend it? |
26 |
> > > > > |
27 |
> > > > > John Covici |
28 |
> > > > > covici@××××××××××.com |
29 |
> > > > |
30 |
> > > > Probably searching for packages that depend on mplib, (equery) then |
31 |
> > > > emerge -C them (it's what I'd probably do - depends...) then |
32 |
> > > > re-emerge them if you still use them? Note that I'd go back to |
33 |
> > > > finding what members of the world file need all this stuff and |
34 |
> > > > emerge that with -DuN, maybe even doing a -depclean after the emerge |
35 |
> > > > -C. It's all a guess though. |
36 |
> > > > |
37 |
> > > > Seems like this sort of thing happens when a package gets dumped in |
38 |
> > > > an upgrade but somehow the ebuilds or package manager don't get |
39 |
> > > > updated or just don't work perfectly. |
40 |
> > > > |
41 |
> > > > Again, all a guess but I can usually figure it out looking at equery |
42 |
> > > > output, etc. |
43 |
> > > |
44 |
> > > Well, there was a package, but no ebuild, so I deleted the package and |
45 |
> > > its going, but someone broke something. I wish you could not delete an |
46 |
> > > ebuild if you have the package, or it would put it somewhere to prevent |
47 |
> > > this kind of thing. |
48 |
> > |
49 |
> > That will make portage store gigantic numbers of old and since upgraded |
50 |
> > versions just in case maybe you might need it perhaps. Sounds like a lot |
51 |
> > of pain for no gain. Sounds like exactly the kind of thing any decent |
52 |
> > dev will reject. |
53 |
> > |
54 |
> > Besides, you can always get the old ebuild back from the Attic, or you |
55 |
> > could copy it somewhere safe from /var/db/pkg/ before you delete it. |
56 |
> > |
57 |
> > Mark has the correct solution. mplib is not needed and was deleted. |
58 |
> > However, it's in preserved-rebuild as being used by something. In all |
59 |
> > likelyhood that something uses mplib purely optionally and you should |
60 |
> > just rebuild that something. You provided no output so no-one here knows |
61 |
> > how to fix your problem. |
62 |
> |
63 |
> There was no output, but what I sent and the only thing depended on |
64 |
> mplib was the package with no ebuild, so I guess its fixed. But |
65 |
> something seems wrong here that you should have a package and the ebuild |
66 |
> would go away like that. I am not sure of the best solution. |
67 |
|
68 |
But you *don't* have the package, or it didn't uninstall cleanly. It's not in |
69 |
the tree, it's not in eix, so it no longer exists. There would have been at |
70 |
least 30 days notice in $PORTDIR/profiles/package.mask that it was going away, |
71 |
and emerge gives output that there is a package present without an ebuild. |
72 |
|
73 |
Or maybe you deleted the ebuild yourself out of a local overlay. |
74 |
|
75 |
There's lots of ways this can happen. preserved-rebuild tracks that some part |
76 |
of mplib is bieng used somehow, and it told you. Now you as the human being |
77 |
get to decide how to proceed because the software cannot decide for you. |
78 |
|
79 |
The software is working as designed. What else did you expect it to do? |
80 |
|
81 |
One thing that is NOT a solution is to not delete the ebuild. That results in |
82 |
your tree being out of sync with upstream. That is not allowed. |
83 |
|
84 |
|
85 |
-- |
86 |
alan dot mckinnon at gmail dot com |