| Summary: | fedpkg does not seem to work | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bill C. Riemers <briemers> |
| Component: | fedora-packager | Assignee: | Dennis Gilmore <dennis> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | alexey.brodkin, dcantrell, dennis, jrincayc, rhbugs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-21 20:05:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Bill C. Riemers
2011-10-21 19:49:31 UTC
Your public key was denied, as fedpkg is using ssh to interact with git. Either you haven't completed your fedora packager group membership step, or your ssh public key hasn't been synced to the git server. Either way, this isn't a fedpkg bug, it's telling you what went wrong. In the mean time, you can clone with -a to bypass ssh and use git:// protocol and clone anonymously. I am not a member of the fedora packager group. That wasn't mentioned as a requirement for cloning, just for updating. Really there seems to be a catch-22 here in that the only way to become a member of the fedora packager group is to be invited for submitting quality builds. But the only way to do that is to already be a member of the group... I'll update the wiki with the instructions about using -a for anonymous access, as at least that will avoid others having the same confusion. Thanks for your help. Bill The section of the wiki page you linked to (Upload your package) doesn't deal with fedpkg at all. Perhaps you meant to link to https://fedoraproject.org/wiki/PackageMaintainers/Join#Check_out_the_module However that comes after https://fedoraproject.org/wiki/PackageMaintainers/Join#Get_Sponsored which does discuss getting into the packager group. Adding info about -a is helpful though, thank you. The same thing happens here - https://fedoraproject.org/wiki/Building_a_custom_kernel I don't see any mention of requirement to be a member of Fedora anything in that article, instead "This document provides instructions for __advanced_users__ who want to rebuild the kernel from some source." This article says: ------------------->8-------------------- Make sure you have installed all dependencies $ fedpkg clone kernel ------------------->8-------------------- And for me (since I don't have any rights to access Fedora servers via ssh) that's what happens: ------------------->8-------------------- Cloning into 'kernel'... Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Could not execute clone: Command '['git', 'clone', 'ssh://username.org/kernel', '--origin', 'origin']' returned non-zero exit status 128 ------------------->8-------------------- So I would assume this and other articles that mention use of "fedpkg" should explicitly cover this situation: Fedora maintainers use simple "fedpkg clone", others "fedpkg clone -a/--anonymous". Oops. That article I mentioned really has mention of "-a" switch for non-Fedora developers. Sorry for this. I encountered a similar problem and found this bug, and later this helpful documentation which would be useful for the next person who encounters this problem: https://docs.fedoraproject.org/en-US/ci/pull-requests/ |