Date: Tue, 30 Sep 2014 16:42:51 +0200 From: Rainer Hurling <rhurlin@gwdg.de> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de>, FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: pkg/ports system terribly messed up? Message-ID: <542AC16B.5070202@gwdg.de> In-Reply-To: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de> References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 30.09.2014 um 08:13 schrieb O. Hartmann: > > 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 > I am afraid I am observing something similar to what Oliver reported. On a CURRENT box (r272295) I get the following for all ports execpt pkg itself: portmaster indexinfo-0.2 ===>>> Currently installed version: indexinfo-0.2 ===>>> Port directory: /usr/ports/print/indexinfo ===>>> Gathering distinfo list for installed ports ===>>> Launching 'make checksum' for print/indexinfo in background ===>>> Gathering dependency list for print/indexinfo from ports ===>>> Launching child to install print/indexinfo/../../ports-mgmt/pkg ===>>> indexinfo-0.2 >> print/indexinfo/../../ports-mgmt/pkg (1/1) ===>>> Port directory: /usr/ports/print/indexinfo/../../ports-mgmt/pkg ===>>> Update for print/indexinfo/../../ports-mgmt/pkg failed ===>>> Aborting update When I try to build other ports, it does not complain about ports-mgmt/pkg, but something else in the dependency list. For example, for net/mpich2 it complains about devel/binutils ... This does not happen on my other CURRENT boxes (they build ports as exected). All systems have pkg-1.3.8_2 installed. The main difference between these boxes is, that the boxes without problems come from older installations, which were converted via pkg2ng. Only the box in question has all ports built and installed from scratch after installing pkg, without any installations via pkg_* before. As far as I can say, all went well until r369572. After svn'ing to a more recent revision, I was not able to build ports any more ... HTH, Rainer Hurling
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?542AC16B.5070202>