I just made the last update of the ports yesterday (I use portmaster -da 
performing this
task) and obviously or superficially everything went all right.

I'm running on the boxes in question most recent CURRENT.

On one system, a subsequent start of updating ports starts to freak out when 
lang/gcc: it loops over and over on some ports already updated, especially
devel/binutils, but the port looping on isn't specific and varies.

On every CURRENT box I tried this morning to update the ports again, I find this
frsutrating message (depends on installation, but it seems in principal the 
same, only
the affected ports in dependency chain varies):

 ===>>> Gathering distinfo list for installed ports

===>>> Starting check of installed ports for available updates
===>>> Launching child to update openldap-sasl-client-2.4.39_2 to

===>>> All >> openldap-sasl-client-2.4.39_2 (1/1)

===>>> Currently installed version: openldap-sasl-client-2.4.39_2
===>>> Port directory: /usr/ports/net/openldap24-sasl-client

===>>> Launching 'make checksum' for net/openldap24-sasl-client in background
===>>> Gathering dependency list for net/openldap24-sasl-client from ports
===>>> Launching child to install 

===>>> All >> openldap-sasl-client-2.4.39_2 >>
net/openldap24-sasl-client/../../ports-mgmt/pkg (2/2)

===>>> Port directory: 

===>>> Update for net/openldap24-sasl-client/../../ports-mgmt/pkg failed
===>>> Aborting update

===>>> Update for openldap-sasl-client-2.4.39_2 failed
===>>> Aborting update

You have new mail.

This isn't, so far, OpenLDAP specific, on other systems without LDAP the update 
fails on
another port.


Attachment: signature.asc
Description: PGP signature

Reply via email to