[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: out-of-date v.1.13 -- LIB_DEPENDS reporting problem
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Re: out-of-date v.1.13 -- LIB_DEPENDS reporting problem
- From: Marc Espie <espie_(_at_)_nerim_(_dot_)_net>
- Date: Tue, 18 Oct 2005 17:20:18 +0200
- Mail-followup-to: ports_(_at_)_openbsd_(_dot_)_org
- Reply-to: espie_(_at_)_nerim_(_dot_)_net
On Tue, Oct 18, 2005 at 09:03:11AM -0400, Josh Grosse wrote:
> I've seen this odd report from the new out-of-date that I do not
> understand. Is this an error? I had it start up some days ago, but, even
> after a complete re-sync of cvs and a rebuilding of my kernel, userland, and a
> complete removal and rebuild of all my ports ... I can't seem
> to stop this particular "outdated" message:
> -------
> Collecting installed packages
> Collecting port versions: complete
> Collecting port signatures: complete
> Outdated ports:
>
> textproc/p5-XML-Parser # expat.4.0 -> expat.5.0
> -------
> textproc/expat, the LIB_DEPENDS for p5-XML-Parser, is expat-1.95.6.
> And textproc/p5-XML-Parser is p5-XML-Parser-2.34; make for the latter shows:
> -------
> .... >> Checksum OK for XML-Parser-2.34.tar.gz. (sha1)
> ===> p5-XML-Parser-2.34 depends on: expat-* - found
> ===> Verifying specs: expat.2
> ===> found expat.5.0
> ===> Extracting for p5-XML-Parser-2.34....
> -------
> Any suggestions as to what might be the cause of the out-of-date error?
This is a known problem. We've got a fix around... Basically, those
ports get confused between X11R6 and the ports tree.
Visit your host, monkey.org