releng

#7834 Updates blocked to sysusage for f28 & f29
Closed: Fixed Opened by frankcrawford.

Closed: Fixed
Reopen Issue
  • Describe the issue
    I'm the main admin (and only admin) for the package sysusage, but appear to be blocked from performing updates on the branches for f28 and f29.

When attempting a git push I get:

[frank@agc sysusage]$ git push
Enter passphrase for key '/home/frank/bits/.ssh/id_fedoraproject.org':
Warning: No xauth data; using fake authentication data for X11 forwarding.
X11 forwarding request failed on channel 0
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 823 bytes | 274.00 KiB/s, done.
Total 5 (delta 3), reused 0 (delta 0)
remote: FATAL: W refs/heads/f28 rpms/sysusage frankcrawford DENIED by refs/heads/f[0-9][0-9]
remote: error: hook declined to update refs/heads/f28
To ssh://pkgs.fedoraproject.org/rpms/sysusage.git
! [remote rejected] f28 -> f28 (hook declined)
error: failed to push some refs to 'ssh://frankcrawford@pkgs.fedoraproject.org/rpms/sysusage.git'

  • When do you need this? (YYYY/MM/DD)
    ASAP, for f29, to make t into the new release.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    No end date.

  • If we cannot complete your request, what is the impact?
    Won't be able to push any updates going forward.

@frankcrawford Can you check your krb ticket? If it is expired try kinit and try to push again.

@mohanboddu I've just retried it and still no go. Also, it works fine for older branches (master, f27, el6, epel7) but not for f28 or f29.

@frankcrawford Can you give it a try now, I regenerated the gitolite config.

@mohanboddu Yes, that fixed the issue. Thanks.

@frankcrawford Cool, happy building :smile:

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

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

Metadata Update from @frankcrawford:
- Issue status updated to: Open (was: Closed)

Metadata Update from @frankcrawford:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.