#45337: py-graveyard: avoid useless binary package download and buildbot errors --------------------+-------------------------- Reporter: petr@… | Owner: larryv@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: py-graveyard --------------------+-------------------------- The current implementation of the Python graveyard causes quite some useless actions on the buildbots. When the list of buried ports grows larger, this may create a significant extra load. (1) It tries to get a binary packages for `py-graveyard`: {{{ sudo port install py-graveyard ---> Fetching archive for py-graveyard ---> Attempting to fetch py-graveyard-0.0_0.darwin_12.noarch.tbz2 from http://nue.de.packages.macports.org/macports/packages/py-graveyard ---> Attempting to fetch py-graveyard-0.0_0.darwin_12.noarch.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/py- graveyard ---> Attempting to fetch py-graveyard-0.0_0.darwin_12.noarch.tbz2 from http://lil.fr.packages.macports.org/py-graveyard ---> Fetching distfiles for py-graveyard Error: This is a metaport for obsolete Python subports. Error: org.macports.fetch for port py-graveyard returned: non-installable metaport Please see the log file for port py-graveyard for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-graveyard/py-graveyard/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port py-graveyard failed }}} (2) The buildbot fails on all buried port and on `py-graveyard` itself. Can this behavior be avoided? -- Ticket URL: <https://trac.macports.org/ticket/45337> MacPorts <http://www.macports.org/> Ports system for OS X