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_at_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.      |
+-------------------------------+------------------------------------+