Our automated repository checks [1] have detected that the 'necromancy- overlay' 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/necromancy-overlay.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
ok I'll add app-editors/enki-editor-14.07.2 to masked packages along with others I may have forgotten about. , 15.x is out so soon as I get dev-python/qutepart packed or if some has ebuild skell I'll give it a test drive in repo. https://github.com/hlamer/qutepart dev-python/qutepart tre (grep like tool ) app-text? /tre https://github.com/laurikari/tre sys-apps/tre ????/tre is an optional dep , however for dyslexic bastards like myself it seems useful , so I don't shoot myself in the foot... https://aur.archlinux.org/packages/enki-editor-git/ been using as cheat sheet. anyhow an ebuild for tre if any or a valid Atom name I will try and pkg. any sec packages that are low hanging fruit , feel ie need testing , Feel free to shove on my plate... if possible i can bang on them till they work.
a few are still WIP's many are nearing testing stages. I'll soft mask them when i get a chance.
I'm sorry for not expanding on this earlier. The problem with your enki-editor ebuild is that you're mixing different package name in directory and file name. You've got: app-editors/enki/enki-editor-... I suppose you want instead: app-editors/enki-editor/enki-editor-... I've reported a bug against pkgcore to get this kind of errors more readably described. To be honest, I don't think masking will help here. You just need to rename the directory or the file to match.
https://github.com/necrose99/necromancy-overlay/blob/master/app-editors/enki/enki-14.07.2.ebuild ebuild/s need to be condensed to one (I swiped parts of others) shortened https://github.com/necrose99/necromancy-overlay/blob/master/dev-python/qutepart/qutepart-2.20.ebuild ??? src_compile() { python setup.py install --include-dir=../pcre-8.37/build --lib-dir=../pcre-8.37/build/Release } this is a bit thornier than expected ... however for kde/kate its an optional depend as well I had mistakenly thought their was already an enki or same name package or a bug for it. fora differing sort of package. anyhow trying to get Q/A up on many a package so they can Go to Sunrise or the like. Qt4-fsarchiver , fsarchiver needs lzop also it seems. if using lzo as well. anyhow I've pushed updated manifest to tree, but have not had a chance to fully test however trying to hit a pull request to the gentoo main tree is a bit rough. gentoo-??? for review would be a plus. despite not being bumped in the main tree the ebuild endures version bumps well.
There is still a lot of issues as can be seen in linked output. It gets updated every 20 minutes.
The bug seems to be fixed in the repository. Closing.
Sorry, looks like the script output got broken somehow ;-f.
Hmm, it seems that this bug is stale after the rename.
