#7447 pkgs.fedoraproject.org rejecting git push with a legacy hook error
Closed: Fixed 5 years ago Opened 5 years ago by tkrizek.

  • Describe what you need us to do:
    Please remove/fix the legacy hook that prevents from pushing to knot-resolver dist git.
$ git push upstream master
Counting objects: 4, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 2.28 KiB | 2.28 MiB/s, done.
Total 4 (delta 2), reused 0 (delta 0)
remote: Running hooks for rpms/knot-resolver
remote: Running legacy hook pre-receive.pagureforcecommit. Please ask your admin to port this to the new plugin format, as the current system will cease functioning in a future Pagure release
remote: Traceback (most recent call last):
remote:   File "hooks/pre-receive", line 24, in <module>
remote:     run_hook_file(hooktype)
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 517, in run_hook_file
remote:     pull_request,
remote:   File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 435, in run_project_hooks
remote:     [hookfile] + args, cwd=repodir, stdin=subprocess.PIPE
remote:   File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
remote:     errread, errwrite)
remote:   File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
remote:     raise child_exception
remote: OSError: [Errno 2] No such file or directory
To ssh://pkgs.fedoraproject.org/rpms/knot-resolver.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://tkrizek@pkgs.fedoraproject.org/rpms/knot-resolver.git'
  • When do you need this? (YYYY/MM/DD)
    this blocks me from updating the package
  • When is this no longer needed or useful? (YYYY/MM/DD)
    N/A
  • If we cannot complete your request, what is the impact?
    no new builds of knot-resolver

Metadata Update from @pingou:
- Issue assigned to pingou

5 years ago

Metadata Update from @pingou:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

5 years ago

This has been fixed server side, the underlying issue has been resolved in git and @tkrizek confirmed it's fixed on IRC

Closing :)

Thanks for your report @tkrizek and sorry for the bother

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata