This package exists in main tree, so it should be deleted in ::dotnet repository. right now it prevent cache regeneration: https://qa-reports.gentoo.org/output/repos/dotnet.html $ pmaint --config /var/lib/repo-mirror-ci/data/etc/portage regen --use-local-desc --pkg-desc-index -t 32 dotnet * www-servers/xsp-4.6: failed sourcing ebuild: inherit requires unknown eclass: user.eclass [FATAL] * Cache regen failed with 1 I am unable to remove it myself, because I don't remember how to do that, and obvious steps give: /var/db/repos/dotnet $ git push FATAL -- ACCESS DENIED Repo repo/proj/dotnet User Arsen.Shnurkov@gmail.com Stage Before git was called Operation Repo write FATAL: W any repo/proj/dotnet Arsen.Shnurkov@gmail.com DENIED by fallthru (or you mis-spelled the reponame) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Reproducible: Always
And my access (https://bugs.gentoo.org/843380) was removed without notice: $ ssh git@git.gentoo.org info | grep " W" R W proj/test
Your access was removed because you hadn't pushed anything since 2016. Should be a simple matter to restore it.
Maybe an error if missed https://github.com/gentoo/dotnet/commit/79b95c4f839396323d4dbd3033be3de3fb7cbaa8
Indeed, it may have been an error; I was just quoting ajak's email to gentoo-core.
Ah, you're not using your email in the git author/S-o-b. That'd be why I missed it. Please use that email instead of a fake one.
Your access should be restored. Again, please use the correct email address. I don't think the hooks are supposed to allow what you're doing.
yes, restored. I used long fake email, because if i use a short one it doesn't work: /var/db/repos/dotnet $ git push Enumerating objects: 3, done. Counting objects: 100% (3/3), done. Delta compression using up to 4 threads Compressing objects: 100% (2/2), done. Writing objects: 100% (2/2), 989 bytes | 989.00 KiB/s, done. Total 2 (delta 1), reused 0 (delta 0), pack-reused 0 remote: FATAL: VREF/proj-gentoo-06-copyright: helper program exit status 256 remote: 312da2cd3c58aec9b3f2f485cb83771121564b4b: no Signed-off-by line matching committer's e-mail address found! remote: expected: ArsenShnurkov@users.noreply.github.com remote: last found: Arsen.Shnurkov@gmail.com remote: remote: Please make sure to read the copyright policy before adding Signed-off-by! remote: https://www.gentoo.org/glep/glep-0076.html remote: error: hook declined to update refs/heads/master To git+ssh://git.gentoo.org/repo/proj/dotnet.git ! [remote rejected] master -> master (hook declined) error: failed to push some refs to 'git+ssh://git.gentoo.org/repo/proj/dotnet.git'
No, the issue is that your git author has to align with Signed-off-by.
I agree. I need to reread https://docs.github.com/ru/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address and revert email in git settings, because commit goes to gentoo, not github.
But that email will become visible on github after synchronization between gentoo and github. So I need another email (preferably on gentoo project). I don't have one, because I am not a gentoo developer. And I am not a gentoo developer because there are no mentors who are willing to assign that status to me.
Arsen.Shnurkov AT gmail.com is already on Github. See 7a97cafed5761149784e0b0ac47983ce9e88a1a4 for example. You're not hiding anything by keeping it out of your commits.
In that 2016 i just had no knowledge about that feature. Later I learned it. If github provide that security guideline, why am i to act differently?
(In reply to Arsen Shnurkov from comment #12) > In that 2016 i just had no knowledge about that feature. Later I learned it. > If github provide that security guideline, why am i to act differently? You don't push to Github; you push to Gentoo's infra and we mirror it to Github. Gentoo would strongly prefer that you not use a fake/masked email address when committing. I'm not sure if we have that written down anywhere as policy, but if you insist we can make an official issue out of it.
The lack of sufficient validation in our git hooks is what's raised in bug 882435. As far as I can tell it's not expected that our hooks allow the usage of emails that aren't what gitolite knows.
