Our automated repository checks [1] have detected that the 'ultrabug' repository contains ebuilds that trigger fatal errors during the cache regeneration. This usually means that the ebuilds call 'die' in global scope indicating serious issues. Global-scope failures prevent the ebuild not only from being installed but also from being properly processed by the Package Manager. Since metadata can not be obtained for those ebuilds, no cache entries are created for them and the Package Manager needs to retry running them every time it stumbles upon them. This involves both a serious slowdown and repeating error output while performing dependency resolution. The most common cause of global-scope failures is use of removed or banned APIs in old ebuilds. In particular, this includes eclasses being removed or removing support for old EAPIs. Nonetheless there are also other issues such as performing illegal operations in global scope (external program calls), malformed bash in ebuilds or malformed metadata.xml. The error log for the repository can be found at: https://qa-reports.gentoo.org/output/repos/ultrabug.html In particular, please look for highlighted '!!! ERROR' and '!!! caught exception' lines. The former usually mean failures coming from eclasses and the ebuild itself, while exceptions usually mean malformed ebuilds or metadata.xml. While at it, please consider fixing global-scope 'use' call warnings (if any). They are not fatal but are considered a serious QA violation. 'use' functions must not ever be called outside of phase functions. Please fix the issue ASAP, possibly via removing unmaintained, old ebuilds. We reserve the right to remove the repository from our list if we do not receive any reply within 4 weeks. [1]:https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI
Ping.
Last ping. Please at least reply or the repository will be removed.
Sorry Michal, I will eventually take the time for this but I'm really doing my best around.
I dropped offending ebuilds, sorry for the inconvenience and the silly time it took me to do so. I want to take this chance to thank you for your time and work on this mate! Finally, I noted to do a more global QA check on the most likely obsolete ebuilds I still have around on my overlay.
Still more. Please look for all ebuilds inheriting distutils/python.
done :) [master 4bfcefb] remove all obsolete distutils based ebuilds wrt #613086 Date: Wed Aug 9 11:14:43 2017 +0200 20 files changed, 320 deletions(-) delete mode 100644 dev-python/flask-restful/Manifest delete mode 100644 dev-python/flask-restful/flask-restful-0.1.6.ebuild delete mode 100644 dev-python/flask-restful/flask-restful-0.2.1.ebuild delete mode 100644 dev-python/gevent-socketio/Manifest delete mode 100644 dev-python/gevent-socketio/gevent-socketio-9999.ebuild delete mode 100644 dev-python/pybrowscap/Manifest delete mode 100644 dev-python/pybrowscap/pybrowscap-2.0.ebuild delete mode 100644 dev-python/python-ultramemcached/Manifest delete mode 100644 dev-python/python-ultramemcached/python-ultramemcached-9999.ebuild delete mode 100644 dev-python/tweetstream/Manifest delete mode 100644 dev-python/tweetstream/tweetstream-1.1.1.ebuild delete mode 100644 dev-python/uasparser/Manifest delete mode 100644 dev-python/uasparser/uasparser-999.ebuild delete mode 100644 dev-python/ultramemcache/Manifest delete mode 100644 dev-python/ultramemcache/ultramemcache-9999.ebuild delete mode 100644 dev-python/validictory/Manifest delete mode 100644 dev-python/validictory/metadata.xml delete mode 100644 dev-python/validictory/validictory-0.9.0.ebuild delete mode 100644 www-apps/circus-web/Manifest delete mode 100644 www-apps/circus-web/circus-web-0.5.ebuild
