Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Sep 2014 08:13:01 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   pkg/ports system terribly messed up?
Message-ID:  <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de>

index | next in thread | raw e-mail

[-- Attachment #1 --]

Hello.

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 updateing
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
openldap-sasl-client-2.4.40

===>>> 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 net/openldap24-sasl-client/../../ports-mgmt/pkg

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

===>>> Port directory: /usr/ports/net/openldap24-sasl-client/../../ports-mgmt/pkg


===>>> 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.

Oliver

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJUKknyAAoJEOgBcD7A/5N8EcYIAL+Smy3ns0xZRn5KoDRUiJ4m
6zUvfTCQ8IdW3zq7oIjS+PWehj+G6+aIJFvZFiWb8Cu72diHMnnCX48kcAL7w8XR
UlJRFgMw34RORBuThE8UfgTR5fUnGWLKC12f0STWq3T9EbjIob9mnfMfA5Xwrh3F
AG0Nc64CQ4Yz7NjDIpJYSTGRJ1nbrUtmNW+Adrg8PTmYZvlo6KqZvmJaeOe/Gl/g
wgcH79ov3zIHpyZkJI4qStqVyuAM+5cc3RzAXQ0HkX7K8NAYa2ZbxsGZsu0Uu0+n
FZ+Gv+hnf80EsmuzFV/q2w6aUduMQT09Rmn2NpGOh/vaj3ksRnJ1Vj94/QnuUqk=
=9uPL
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140930081301.55bc5629.ohartman>