Fwd: Don't break my ports! Help! I can't patch my s417....

[Jason de Cordoba]

-------- Forwarded Message --------
Subject: 	Don't break my ports! Help! I can't patch my s417....
Date: 	Sun, 3 Dec 2017 21:25:59 +0100
From: 	Jason de Cordoba <jason at aventia.pw>
Organization: 	aventia.pw
To: 	feedback at bsdnow.tv



Hey Benedict, Allan and JT!

Love the show, such an important resource for the BSD community!

My question is:
Sometimes ports are broken, this means that no other ports can
automatically get updated until that glaring oversight by a contributor
is resolved.
Sure usually reading /usr/ports/UPDATING helps, but not always, and in
this situation it did not help me much....

Could by chance one of you explain how to get portmaster running again?

Thanks in advance,

Oclair (freenode)


What happened:

    # portsnap fetch update
    Looking up portsnap.FreeBSD.org mirrors... 6 mirrors found.
    Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done.
    Fetching snapshot metadata... done.
    Updating from Wed Nov 29 22:37:56 CET 2017 to Sun Dec  3 19:53:33
    CET 2017.
    Fetching 5 metadata patches... done.
    Applying metadata patches... done.
    Fetching 5 metadata files... done.
    Fetching 2789 patches.
    (2789/2789) 100.00%  done.   

2789 ports have been changed in 4 days?

Of course someone needs to change flavors nothing can go wrong right?

    ===>>> Returning to update check of installed ports

    ===>>> Launching child to update py27-docutils-0.14 to
    py27-docutils-0.14_1

    ===>>> All >> py27-docutils-0.14 (8/8)

    ===>>> Currently installed version: py27-docutils-0.14
    ===>>> Port directory: /usr/ports/textproc/py-docutils

    ===>>> Launching 'make checksum' for textproc/py-docutils in background
    ===>>> Gathering dependency list for textproc/py-docutils from ports
    ===>>> Initial dependency check complete for textproc/py-docutils

    ===>>> Returning to update check of installed ports

        ===>>> The devel/py27-setuptools port moved to
    devel/py-setuptools at py27
        ===>>> Reason: Moved to a flavored, generic, version

    ===>>> Launching child to reinstall py27-setuptools-36.5.0

    ===>>> All >> py27-setuptools-36.5.0 (9/9)

        ===>>> The devel/py27-setuptools port moved to
    devel/py-setuptools at py27
        ===>>> Reason: Moved to a flavored, generic, version

    ===>>> No valid installed port, or port directory given
    ===>>> Try portmaster --help

    ===>>> Update for py27-setuptools-36.5.0 failed
    ===>>> Aborting update

FreeBSD is not only used by programmers, but Sysadmins AND hopefully
Anyone!  If I truly cannot understand this how are normal users going to
keep a system updated via ports maintained?

      AFFECTS: */py*
      AUTHOR: mat at FreeBSD.org

      Ports using Python via USES=python are now flavored.  All the
    py3-* ports
      have been removed and folded into their py-* master ports.

      People using Poudriere 3.2+ and binary packages do not have to do
    anything.

      For other people, to build the Python 3.6 version of, for example,
      databases/py-gdbm, you need to run:

        # make FLAVOR=py36 install


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-python/attachments/20171203/695f70e3/attachment.sig>