| 1 |
Oh, and one other thing. This should also be done for packages that |
| 2 |
get moved to different categories, because I've been getting errors |
| 3 |
like the following lately... |
| 4 |
|
| 5 |
Calculating world dependencies | |
| 6 |
emerge: there are no ebuilds to satisfy ">=dev-perl/PodParser-1.22". |
| 7 |
(dependency required by "mail-filter/spamassassin-3.1.0" [binary]) |
| 8 |
|
| 9 |
In this case, this simply means that dev-perl/PodParser has moved to a |
| 10 |
different category, and the old spamassassin binary package couldn't |
| 11 |
find it anymore, because it only knows about the PodParser in the old |
| 12 |
category, not the new category. I checked the xorg-x11 ebuild, and it |
| 13 |
was fine. It was the binary that still had problems, so I had to |
| 14 |
re-merge it without --usepkg. If I recall correctly, I also would |
| 15 |
have had to remove the file "/var/cache/edb/remote_metadata.pickle", |
| 16 |
but I started using NFS for my portage instead. That file has |
| 17 |
information about packages, and their dependencies, so I looked in it, |
| 18 |
and it had the wrong information. It had the "dev-perl/PodParser" |
| 19 |
info, instead of the "perl-core/PodParser" info. |
| 20 |
|
| 21 |
On 1/5/06, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 22 |
> On Thu, 5 Jan 2006 16:08:04 +0000, Tom Martin wrote: |
| 23 |
> |
| 24 |
> > > if_blocked_by('openmotif') |
| 25 |
> > > ewarn "You must unmerge openmotif before proceeding" |
| 26 |
> > |
| 27 |
> > An error message like that doesn't really tell the user anything that he |
| 28 |
> > doesn't already know. |
| 29 |
> |
| 30 |
> It may not say anything you or I don't know, but from the number of posts |
| 31 |
> to this list about blockers, it would clearly help some people. |
| 32 |
> |
| 33 |
> > It would be more useful if some information was provided: |
| 34 |
> > |
| 35 |
> > if blocked_by >=x11-libs/openmotif-1.2.3 ; then |
| 36 |
> > eblockinfo "Due to changes with blah, it is recommended that" |
| 37 |
> > eblockinfo "you foobar. See http://bugs.gentoo.org/123456." |
| 38 |
> > fi |
| 39 |
> > |
| 40 |
> > But then, at what point would this information be echoed to the user? |
| 41 |
> > It would have to be during the same pre-merge phase that the blocking |
| 42 |
> > errors appear. |
| 43 |
> |
| 44 |
> Yes, so instead of rushing to this list or the forums, they can do what |
| 45 |
> the message tells them and be on their way. The current messages are only |
| 46 |
> useful if you already understand how and why blocks happen, and how to |
| 47 |
> deal with them. |
| 48 |
> |
| 49 |
> |
| 50 |
> -- |
| 51 |
> Neil Bothwick |
| 52 |
> |
| 53 |
> If you got the words it does not mean you got the knowledge. |
| 54 |
> |
| 55 |
> |
| 56 |
> |
| 57 |
|
| 58 |
-- |
| 59 |
gentoo-user@g.o mailing list |
Archives