Portmanager output, what's it mean?

Michael C. Shultz reso3w83 at verizon.net
Tue Feb 15 23:12:24 GMT 2005


On Tuesday 15 February 2005 02:38 pm, Benjamin Dover wrote:
> Portmanager finished and I'm not sure what its trying to tell me.  Do
> I have to manually update gnupg-devel-1.9.14_1 or just run
> portmanager again?  It made a list of ports and they all showed
> current.  Here is the output:
>
> ---------------------------------------------------------------------
>--- OLD kdeutils-3.3.2 built with old dependency gnupg-1.4.0, current
> dependency isgnupg-1.4.0_1
> OLD kde-3.3.2 built with old dependency gnupg-1.4.0, current
> dependency is gnupg-1.4.0_1
> OLD gnupg-devel-1.9.14_1 built with old dependency gnupg-1.4.0,
> current dependency is gnupg-1.4.0_1
> ---------------------------------------------------------------------
>--- status report finished
> =====================================================================
>=== checkForOldDepencies 0.2.6_5 skip: kdeutils-3.3.2 has a dependency
> gnupg-devel-1.9.14_1 that needs to be updated first
> checkForOldDepencies 0.2.6_5 skip: kde-3.3.2 has a dependency
> gnupg-devel-1.9.14_1 that needs to be updated first
> checkForOldDepencies 0.2.6_5 skip: gnupg-devel-1.9.14_1 has a
> dependency gnupg-devel-1.9.14_1 that needs to be updated first
> ---------------------------------------------------------------------
>--- update of ports collection complete with either some errors,
> ignored ports or both
> =====================================================================
please send me the output of portmanager -u >& portmanager.log (send to 
ringworm01 at gmail.com)

right now I am guessing gnupg-1.4.0 failed to build but it should have
explicitly reported that fact, so maybe there is a bug here.

-Mike




More information about the freebsd-questions mailing list