Opened 10 years ago
Closed 10 years ago
#45337 closed defect (wontfix)
py-graveyard: avoid useless binary package download and buildbot errors
Reported by: | petrrr | Owned by: | larryv (Lawrence Velázquez) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.1 |
Keywords: | Cc: | skarulkar@…, jmroot (Joshua Root) | |
Port: | py-graveyard |
Description
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?
Change History (5)
comment:1 follow-up: 2 Changed 10 years ago by larryv (Lawrence Velázquez)
Cc: | skarulkar@… jmr@… added |
---|
comment:2 follow-up: 3 Changed 10 years ago by jmroot (Joshua Root)
Replying to larryv@…:
I don’t know how Buildbot decides which ports to try rebuilding. I assume that the buildslaves reindex their ports trees and process the ports that have changed.
It simply builds all portfiles touched by each changeset.
comment:3 Changed 10 years ago by larryv (Lawrence Velázquez)
Could we filter out graveyards specifically? Something like this?
Index: master.cfg =================================================================== --- master.cfg (revision 126498) +++ master.cfg (working copy) @@ -189,7 +189,8 @@ # paths should be dports/category/portdir(/...) for f in self.build.allFiles(): comps = f.split('/') - if len(comps) >= 3 and comps[0] == 'dports' and comps[1] != '_resources': + if (len(comps) >= 3 and comps[0] == 'dports' and comps[1] != '_resources' and + !comps[2].endswith('-graveyard')): portset.add(comps[2]) portlist += ' ' + ' '.join(portset) self.setProperty('portlist', portlist)
comment:5 Changed 10 years ago by larryv (Lawrence Velázquez)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Hm. Seems simple enough, but probably not worth the special treatment.
I certainly don’t care enough about the buildslaves to put any more thought into this.
Replying to petr@…:
I cleared
archive_sites
in r126541.I don’t know how Buildbot decides which ports to try rebuilding. I assume that the buildslaves reindex their ports trees and process the ports that have changed.