What to I need to do to be able to push to the repo of something I've got un-orphaned? I currently see:
$ fedpkg push Counting objects: 10, done. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 877 bytes | 0 bytes/s, done. Total 7 (delta 4), reused 0 (delta 0) remote: Branch refs/heads/master is unsupported remote: Denied push for ref 'refs/heads/master' for user 'loveshack' remote: All changes have been rejected To ssh://loveshack@pkgs.fedoraproject.org/rpms/powerman ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'ssh://loveshack@pkgs.fedoraproject.org/rpms/powerman' Could not execute push: Failed to execute command.
Although I haven't changed them, none of the hooks under the project settings show as active.
On 9/10/19 8:58 AM, Dave Love wrote:
What to I need to do to be able to push to the repo of something I've got un-orphaned? I currently see:
$ fedpkg push Counting objects: 10, done. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 877 bytes | 0 bytes/s, done. Total 7 (delta 4), reused 0 (delta 0) remote: Branch refs/heads/master is unsupported remote: Denied push for ref 'refs/heads/master' for user 'loveshack' remote: All changes have been rejected To ssh://loveshack@pkgs.fedoraproject.org/rpms/powerman ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'ssh://loveshack@pkgs.fedoraproject.org/rpms/powerman' Could not execute push: Failed to execute command.
Although I haven't changed them, none of the hooks under the project settings show as active.
it's still retired on all the Fedora branches. See:
https://pagure.io/releng/issue/8723#comment-594936
The hook thats blocking it is a check against pdc, which rejects commits when the package is eol/not currently supported.
So, you need a re-review and unretirement...
kevin
Kevin Fenzi kevin@scrye.com writes:
it's still retired on all the Fedora branches. See:
https://pagure.io/releng/issue/8723#comment-594936
The hook thats blocking it is a check against pdc, which rejects commits when the package is eol/not currently supported.
So, you need a re-review and unretirement...
Thanks. I didn't see the pagure comments because I don't get notifications, and just saw I'd got ownership of the project, and the notice about orphaning said it needed adopting to prevent it being retired.
I'm puzzled why it needs re-reviewing when branches are maintained, but anyhow is it possible just to maintain EPEL branches? I doubt anyone is going to run Fedora on the sort of cluster for which it's intended anyhow.
On 11. 09. 19 11:14, Dave Love wrote:
I'm puzzled why it needs re-reviewing when branches are maintained,
Because it was only maintained in EPEL, not Fedora. IF you want to maintian it in Fedora (but I assume you don't), it needs a re-review, because it was retired in Fedora 3 years ago.
but anyhow is it possible just to maintain EPEL branches?
Yes, it is. That was the intention you've stated when you requested the package to be unorphaned. Why have you requested the f31 branch at all? It is not needed.
I recommend you retire on f31 once again and only keep this in epel.
Miro Hrončok mhroncok@redhat.com writes:
On 11. 09. 19 11:14, Dave Love wrote:
I'm puzzled why it needs re-reviewing when branches are maintained,
Because it was only maintained in EPEL, not Fedora.
I just don't understand why it would be OK for EPEL but not for Fedora, but no matter.
(I don't remember ever being asked to take it over, though a notification may never have got through to me.)
but anyhow is it possible just to maintain EPEL branches?
Yes, it is. That was the intention you've stated when you requested the package to be unorphaned. Why have you requested the f31 branch at all? It is not needed.
I misunderstood that it was needed.
I recommend you retire on f31 once again and only keep this in epel.
Thanks. I'm rather inclined to do that with other things to avoid hassle.