Oh, and one other thing. This should also be done for packages that
get moved to different categories, because I've been getting errors
like the following lately...
Calculating world dependencies |
emerge: there are no ebuilds to satisfy ">=dev-perl/PodParser-1.22".
(dependency required by "mail-filter/spamassassin-3.1.0" [binary])
In this case, this simply means that dev-perl/PodParser has moved to a
different category, and the old spamassassin binary package couldn't
find it anymore, because it only knows about the PodParser in the old
category, not the new category. I checked the xorg-x11 ebuild, and it
was fine. It was the binary that still had problems, so I had to
re-merge it without --usepkg. If I recall correctly, I also would
have had to remove the file "/var/cache/edb/remote_metadata.pickle",
but I started using NFS for my portage instead. That file has
information about packages, and their dependencies, so I looked in it,
and it had the wrong information. It had the "dev-perl/PodParser"
info, instead of the "perl-core/PodParser" info.
On 1/5/06, Neil Bothwick <[EMAIL PROTECTED]> wrote:
> On Thu, 5 Jan 2006 16:08:04 +0000, Tom Martin wrote:
>
> > > if_blocked_by('openmotif')
> > > ewarn "You must unmerge openmotif before proceeding"
> >
> > An error message like that doesn't really tell the user anything that he
> > doesn't already know.
>
> It may not say anything you or I don't know, but from the number of posts
> to this list about blockers, it would clearly help some people.
>
> > It would be more useful if some information was provided:
> >
> > if blocked_by >=x11-libs/openmotif-1.2.3 ; then
> > eblockinfo "Due to changes with blah, it is recommended that"
> > eblockinfo "you foobar. See http://bugs.gentoo.org/123456.";
> > fi
> >
> > But then, at what point would this information be echoed to the user?
> > It would have to be during the same pre-merge phase that the blocking
> > errors appear.
>
> Yes, so instead of rushing to this list or the forums, they can do what
> the message tells them and be on their way. The current messages are only
> useful if you already understand how and why blocks happen, and how to
> deal with them.
>
>
> --
> Neil Bothwick
>
> If you got the words it does not mean you got the knowledge.
>
>
>
--
[email protected] mailing list
