Our automated repository checks [1] have detected that the 'shnurise' 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 or have other serious QA violations. 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/shnurise.html In particular, please look for highlighted error messages. 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
Ping.
https://github.com/gentoo/dotnet/pull/507
(In reply to Arsen Shnurkov from comment #3) > https://github.com/gentoo/dotnet/pull/507 I don't think that'll fix the issues in your repo, no?
That will not fix my bugs, but it will now not stand on the way. Thanks for the removing.
(In reply to Arsen Shnurkov from comment #5) > That will not fix my bugs, but it will now not stand on the way. Thanks for > the removing. No problem! By the way, do you have commit access for the dotnet repo? If not, do you want it?
I don't have the access. I asked that question here - https://forums.gentoo.org/viewtopic-t-1147218-highlight-.html But both moderators severely discouraged me (and also they broke "Gentoo kind guidelines" - https://wiki.gentoo.org/wiki/Project:Council/Code_of_conduct). As I understood what I need is a write access to https://gitweb.gentoo.org/repo/proj/dotnet.git and for that I need to have the "Gentoo Developer" status. That is impossible to achieve, because there are no me mentors on that development direction. That's why I shelved the idea to get the access.
(In reply to Arsen Shnurkov from comment #7) > I don't have the access. > I asked that question here - > https://forums.gentoo.org/viewtopic-t-1147218-highlight-.html > But both moderators severely discouraged me (and also they broke "Gentoo > kind guidelines" - > https://wiki.gentoo.org/wiki/Project:Council/Code_of_conduct). > Their comments seem reasonable there.. I don't think they were being mean. But I don't think they realised you've been contributing to a long time to the overlay. > As I understood what I need is a write access to > https://gitweb.gentoo.org/repo/proj/dotnet.git > and for that I need to have the "Gentoo Developer" status. There are other non-developers with +w to the overlay. I think we can probably arrange it. Normally, you should be a full Gentoo developer, yes, but there's a few overlays we don't stick to this guideline for, and the dotnet overlay already has non-developer committers, so I don't see how one more is any different. > That is impossible to achieve, because there are no me mentors on that > development direction. There are people willing to mentor, but there's very few/no developers working on dotnet.git/in areas you work in, so it's currently hard for you to meet them. I'm interested in .NET but no real time to work on it with everything else.
(In reply to Sam James from comment #8) > (In reply to Arsen Shnurkov from comment #7) > > I don't have the access. > > I asked that question here - > > https://forums.gentoo.org/viewtopic-t-1147218-highlight-.html > > But both moderators severely discouraged me (and also they broke "Gentoo > > kind guidelines" - > > https://wiki.gentoo.org/wiki/Project:Council/Code_of_conduct). > > > > Their comments seem reasonable there.. I don't think they were being mean. > But I don't think they realised you've been contributing to a long time to > the overlay. > > > As I understood what I need is a write access to > > https://gitweb.gentoo.org/repo/proj/dotnet.git > > and for that I need to have the "Gentoo Developer" status. > > There are other non-developers with +w to the overlay. I think we can > probably arrange it. > > Normally, you should be a full Gentoo developer, yes, but there's a few > overlays we don't stick to this guideline for, and the dotnet overlay > already has non-developer committers, so I don't see how one more is any > different. > > > That is impossible to achieve, because there are no me mentors on that > > development direction. > > There are people willing to mentor, but there's very few/no developers > working on dotnet.git/in areas you work in, so it's currently hard for you > to meet them. > > I'm interested in .NET but no real time to work on it with everything else. In fact, juippis (who commented last, and is a developer and a recruiter) specifically said you *can* have access if you request it.. https://forums.gentoo.org/viewtopic-p-8691435.html#8691435
ping. Is this related to bug 797043 ?
«Is this related to bug 797043 ?» My overlay have dotnet overlay as one of parent overlays. But I think I am able to fix all errors in my overlay independently.
To be clear, do you accept nobody broke COC here?
should be resolved now https://github.com/ArsenShnurkov/shnurise/commit/8ab873e47276a7c86b4211d65b2166b86ed7721b
