Re: pkg/ports system terribly messed up?
Am 02.10.2014 um 04:40 schrieb Chuck Burns: On Wednesday, October 01, 2014 7:48:08 AM Rainer Hurling wrote: Am 01.10.2014 um 05:44 schrieb Chuck Burns: On Tuesday, September 30, 2014 8:13:01 AM 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. snip It's portmaster actually. While it -usually- works great, I've noticed that occassionally it loops like that. kill the script, upgrade the port that is looping. Because it seems that I have the same problem as Oliver: What script you are talking about? That usually fixes it. portmaster is just a (not-so-)simple shell script. Kill portmaster (CTRL-C a few times) then build the offending port with make make deinstall reinstall clean Thanks for your answer. I tried it, but unfortunately, this does not change my problems with using portmaster for updating ports. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg/ports system terribly messed up?
Am 01.10.2014 um 22:17 schrieb NGie Cooper: On Mon, Sep 29, 2014 at 11:13 PM, O. Hartmann ohart...@zedat.fu-berlin.de 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): Are you using portmaster? If so, it might be fallout from r272282. Cheers, Yup, after defining setenv PORTSDIR /usr/ports my problems, described on my mail in this thread from 30th September, completely went away. Thanks for this hint. It helps a lot! Regards, Rainer Hurling ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg/ports system terribly messed up?
Am 01.10.2014 um 05:44 schrieb Chuck Burns: On Tuesday, September 30, 2014 8:13:01 AM 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. snip It's portmaster actually. While it -usually- works great, I've noticed that occassionally it loops like that. kill the script, upgrade the port that is looping. Because it seems that I have the same problem as Oliver: What script you are talking about? That usually fixes it. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg/ports system terribly messed up?
On Mon, Sep 29, 2014 at 11:13 PM, O. Hartmann ohart...@zedat.fu-berlin.de 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): Are you using portmaster? If so, it might be fallout from r272282. Cheers, ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg/ports system terribly messed up?
On Wednesday, October 01, 2014 7:48:08 AM Rainer Hurling wrote: Am 01.10.2014 um 05:44 schrieb Chuck Burns: On Tuesday, September 30, 2014 8:13:01 AM 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. snip It's portmaster actually. While it -usually- works great, I've noticed that occassionally it loops like that. kill the script, upgrade the port that is looping. Because it seems that I have the same problem as Oliver: What script you are talking about? That usually fixes it. portmaster is just a (not-so-)simple shell script. Kill portmaster (CTRL-C a few times) then build the offending port with make make deinstall reinstall clean -- Chuck ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
pkg/ports system terribly messed up?
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 signature.asc Description: PGP signature
Re: pkg/ports system terribly messed up?
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/pkgmake 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. | +---++ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg/ports system terribly messed up?
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/pkgmake 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. | +---++ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg/ports system terribly messed up?
Am Tue, 30 Sep 2014 08:40:19 +0200 (CEST) Trond Endrestøl trond.endres...@fagskolen.gjovik.no schrieb: 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 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. 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/pkgmake 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 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 passes through. All boxes I ran an update of ports by yesterday fail! signature.asc Description: PGP signature
Re: pkg/ports system terribly messed up?
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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: pkg/ports system terribly messed up?
On Tuesday, September 30, 2014 8:13:01 AM 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. snip It's portmaster actually. While it -usually- works great, I've noticed that occassionally it loops like that. kill the script, upgrade the port that is looping. That usually fixes it. -- Chuck Burns ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
