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>

next in thread | raw e-mail | index | archive | help
--Sig_/AFG.sut9tWCkpA6z9jS3Emt
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable


Hello.

I just made the last update of the ports yesterday (I use portmaster -da pe=
rforming 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 whe=
n 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):

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

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

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

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

=3D=3D=3D>>> Launching 'make checksum' for net/openldap24-sasl-client in ba=
ckground
=3D=3D=3D>>> Gathering dependency list for net/openldap24-sasl-client from =
ports
=3D=3D=3D>>> Launching child to install net/openldap24-sasl-client/../../po=
rts-mgmt/pkg

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

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


=3D=3D=3D>>> Update for net/openldap24-sasl-client/../../ports-mgmt/pkg fai=
led
=3D=3D=3D>>> Aborting update

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

You have new mail.


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

Oliver

--Sig_/AFG.sut9tWCkpA6z9jS3Emt
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

--Sig_/AFG.sut9tWCkpA6z9jS3Emt--



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