Date: Tue, 30 Sep 2014 08:40:19 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: pkg/ports system terribly messed up? Message-ID: <alpine.BSF.2.11.1409300834010.30046@mail.fig.ol.no> 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
On Tue, 30 Sep 2014 08:13+0200, O. Hartmann wrote: > > 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 What happens if you manually upgrade ports-mgmt/pkg, assuming it's out of date? I've noticed running make missing from /usr/ports/ports-mgmt/pkg produces some interesting results _only_ when pkg is up-to-date: trond@enterprise:/usr/ports/ports-mgmt/pkg>make missing /usr/ports/workdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.3.8/src/pkg-static: not found *** [missing] Error code 127 Stop in /usr/ports/ports-mgmt/pkg. Using portupgrade, I finally created a script to help me get past some of the deficiency of the duo pkg and portupgrade. The script checks to see if ports-mgmt/pkg needs an upgrade and upgrades pkg before proceeding with the remaining outdated ports. As portupgrade doesn't always properly install _new_ dependencies, my script also checks for any missing ports and installs them prior to upgrading the outdated ports. If anyone's interested, here's my script: http://ximalas.info/~trond/create-zfs/canmount/upgrade-outdated-ports.sh -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-ports@FreeBSD.ORG Tue Sep 30 06:43:45 2014 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 113E2B0E; Tue, 30 Sep 2014 06:43:45 +0000 (UTC) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8E9B2671; Tue, 30 Sep 2014 06:43:44 +0000 (UTC) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.14.9/8.14.9) with ESMTP id s8U6hdtC006299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Sep 2014 08:43:39 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.14.9/8.14.9/Submit) with ESMTP id s8U6hdYZ006296; Tue, 30 Sep 2014 08:43:39 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 30 Sep 2014 08:43:39 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Sender: Trond.Endrestol@fagskolen.gjovik.no To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Subject: Re: pkg/ports system terribly messed up? In-Reply-To: <alpine.BSF.2.11.1409300834010.30046@mail.fig.ol.no> Message-ID: <alpine.BSF.2.11.1409300842300.30046@mail.fig.ol.no> References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de> <alpine.BSF.2.11.1409300834010.30046@mail.fig.ol.no> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.fig.ol.no Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 30 Sep 2014 06:43:45 -0000 On Tue, 30 Sep 2014 08:40+0200, Trond Endrestøl wrote: > On Tue, 30 Sep 2014 08:13+0200, O. Hartmann wrote: > > > > > 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 > > What happens if you manually upgrade ports-mgmt/pkg, assuming it's out > of date? > > I've noticed running make missing from /usr/ports/ports-mgmt/pkg > produces some interesting results _only_ when pkg is up-to-date: > > trond@enterprise:/usr/ports/ports-mgmt/pkg>make missing > /usr/ports/workdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.3.8/src/pkg-static: not found > *** [missing] Error code 127 > > Stop in /usr/ports/ports-mgmt/pkg. > > Using portupgrade, I finally created a script to help me get past some Oh, that's bad wording on my part, it should read: I'm only using portupgrade, so I finally created a script to help me get past some > of the deficiency of the duo pkg and portupgrade. The script checks to > see if ports-mgmt/pkg needs an upgrade and upgrades pkg before > proceeding with the remaining outdated ports. As portupgrade doesn't > always properly install _new_ dependencies, my script also checks for > any missing ports and installs them prior to upgrading the outdated > ports. If anyone's interested, here's my script: > http://ximalas.info/~trond/create-zfs/canmount/upgrade-outdated-ports.sh -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-ports@FreeBSD.ORG Tue Sep 30 06:56:14 2014 Return-Path: <owner-freebsd-ports@FreeBSD.ORG> Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFF0ED25; Tue, 30 Sep 2014 06:56:14 +0000 (UTC) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4D12D7AB; Tue, 30 Sep 2014 06:56:13 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.82) with esmtp (envelope-from <ohartman@zedat.fu-berlin.de>) id <1XYrM4-0026fq-8H>; Tue, 30 Sep 2014 08:56:12 +0200 Received: from f052143071.adsl.alicedsl.de ([78.52.143.71] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.82) with esmtpsa (envelope-from <ohartman@zedat.fu-berlin.de>) id <1XYrM4-003k0c-5D>; Tue, 30 Sep 2014 08:56:12 +0200 Date: Tue, 30 Sep 2014 08:56:09 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Trond =?ISO-8859-1?Q?Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Subject: Re: pkg/ports system terribly messed up? Message-ID: <20140930085609.3f54d01f.ohartman@zedat.fu-berlin.de> In-Reply-To: <alpine.BSF.2.11.1409300834010.30046@mail.fig.ol.no> References: <20140930081301.55bc5629.ohartman@zedat.fu-berlin.de> <alpine.BSF.2.11.1409300834010.30046@mail.fig.ol.no> Organization: FU Berlin X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/L=SC4_WMNXcfYl7AmHe0.Q_"; protocol="application/pgp-signature" X-Originating-IP: 78.52.143.71 X-ZEDAT-Hint: A Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 30 Sep 2014 06:56:14 -0000 --Sig_/L=SC4_WMNXcfYl7AmHe0.Q_ Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Am Tue, 30 Sep 2014 08:40:19 +0200 (CEST) Trond Endrest=F8l <Trond.Endrestol@fagskolen.gjovik.no> schrieb: > On Tue, 30 Sep 2014 08:13+0200, O. Hartmann wrote: >=20 > >=20 > > Hello. > >=20 > > I just made the last update of the ports yesterday (I use portmaster -d= a performing > > this task) and obviously or superficially everything went all right. > >=20 > > I'm running on the boxes in question most recent CURRENT. > >=20 > > 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, especia= lly > > devel/binutils, but the port looping on isn't specific and varies. > >=20 > > 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): > >=20 > > =3D=3D=3D>>> Gathering distinfo list for installed ports > >=20 > > =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 > >=20 > > =3D=3D=3D>>> All >> openldap-sasl-client-2.4.39_2 (1/1) > >=20 > > =3D=3D=3D>>> Currently installed version: openldap-sasl-client-2.4.39_2 > > =3D=3D=3D>>> Port directory: /usr/ports/net/openldap24-sasl-client > >=20 > > =3D=3D=3D>>> Launching 'make checksum' for net/openldap24-sasl-client i= n background > > =3D=3D=3D>>> Gathering dependency list for net/openldap24-sasl-client f= rom ports > > =3D=3D=3D>>> Launching child to install net/openldap24-sasl-client/../.= ./ports-mgmt/pkg > >=20 > > =3D=3D=3D>>> All >> openldap-sasl-client-2.4.39_2 >> > > net/openldap24-sasl-client/../../ports-mgmt/pkg (2/2) > >=20 > > =3D=3D=3D>>> Port directory: /usr/ports/net/openldap24-sasl-client/../.= ./ports-mgmt/pkg > >=20 > >=20 > > =3D=3D=3D>>> Update for net/openldap24-sasl-client/../../ports-mgmt/pkg= failed > > =3D=3D=3D>>> Aborting update > >=20 > > =3D=3D=3D>>> Update for openldap-sasl-client-2.4.39_2 failed > > =3D=3D=3D>>> Aborting update > >=20 > > You have new mail. > >=20 > >=20 > > This isn't, so far, OpenLDAP specific, on other systems without LDAP th= e update fails > > on another port. > >=20 > > Oliver >=20 > What happens if you manually upgrade ports-mgmt/pkg, assuming it's out=20 > of date? I tried this already, each port in particular, reinstalled via "make clean = reinstall clean" works fine. I did this with ports-mgnt/pkg and ports-mgmt/portmaster= in the first place. >=20 > I've noticed running make missing from /usr/ports/ports-mgmt/pkg=20 > produces some interesting results _only_ when pkg is up-to-date: >=20 > trond@enterprise:/usr/ports/ports-mgmt/pkg>make missing > /usr/ports/workdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.3.8/src/pkg-stati= c: not found > *** [missing] Error code 127 >=20 > Stop in /usr/ports/ports-mgmt/pkg. >=20 > Using portupgrade, I finally created a script to help me get past some=20 > of the deficiency of the duo pkg and portupgrade. The script checks to=20 > see if ports-mgmt/pkg needs an upgrade and upgrades pkg before=20 > proceeding with the remaining outdated ports. As portupgrade doesn't=20 > always properly install _new_ dependencies, my script also checks for=20 > any missing ports and installs them prior to upgrading the outdated=20 > ports. If anyone's interested, here's my script:=20 > http://ximalas.info/~trond/create-zfs/canmount/upgrade-outdated-ports.sh >=20 I'm running portmaster and an update of ports now on an Laptop with CURRENT= that hasn't been touched for two days by now and there the update runs quite well and p= asses through. All boxes I ran an update of ports by yesterday fail! --Sig_/L=SC4_WMNXcfYl7AmHe0.Q_ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJUKlQJAAoJEOgBcD7A/5N8qjkIANpoGeCDoNbQhfEcYpBi6cZ3 1HpreTm8KjAld4fe41mEr4k+UChWoWJCU0RfbL+naylQa7O6m/4mwNrqBmnVlTsA 8OkKDKGpXC6KsMB5lPZaL+BOIYZY8rKlFBb0fY4djvbqKIQhb6OpE6I2ZkZkfqKT d8qa9cWd4f6ib+bIkLA9gi6HluDZi0SbK2gzKJfpmcvFSsjoXCKpR/69CezWVRxc 8SCEFECO+Vdbsnm7UTfk135D8I4f/KaP4xj9pyUH6d34UsmPxVaX3y26yklwdAEV C87KMh83o4Fd3hbU+ZWmtga4ZXIE6OrfzCgHeztZ1jUCJ40fkMnIzELJNdlzYWA= =WKew -----END PGP SIGNATURE----- --Sig_/L=SC4_WMNXcfYl7AmHe0.Q_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1409300834010.30046>