I have the same issue on kmscon, that what I had on libtsm last month with: https://pagure.io/releng/issue/12865
fedpkg push Enumerating objects: 11, done. Counting objects: 100% (11/11), done. Delta compression using up to 12 threads Compressing objects: 100% (8/8), done. Writing objects: 100% (10/10), 5.84 KiB | 5.84 MiB/s, done. Total 10 (delta 1), reused 3 (delta 0), pack-reused 0 (from 0) remote: Branch refs/heads/rawhide is unsupported. Cannot push to a disabled branch (maybe eol?). remote: Denied push for ref 'refs/heads/rawhide' for user 'jfalempe' remote: All changes have been rejected To ssh://pkgs.fedoraproject.org/rpms/kmscon ! [remote rejected] rawhide -> rawhide (pre-receive hook declined) error: failed to push some refs to 'ssh://pkgs.fedoraproject.org/rpms/kmscon' Could not execute push: Failed to execute command.
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Metadata Update from @jnsamyak: - Issue tagged with: low-gain, low-trouble, ops
The package is retired for more than 8 Weeks as per https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming We require a re-review to unretire this package.
That is why it is blocked. Once you have BZ with fedora_review+, please reopen this ticket.
Metadata Update from @jnsamyak: - Issue close_status updated to: Get back later - Issue status updated to: Closed (was: Open)
Sorry, the required BZ with fedora_review+ is there: https://bugzilla.redhat.com/show_bug.cgi?id=2373128
Metadata Update from @jfalempe: - Issue status updated to: Open (was: Closed)
Than we will consider it as an unretirement ticket - what are the branches you need this to be retired for?
I currently need rawhide. I will see later if I can also target f43 and f42
The package is now unretired. For missing branches please use $fedpkg request-branch If there were some builds in rawhide (I suspect not) they were untagged, and it now unblocked from F44 so you should be able to build things in it.
$fedpkg request-branch
kmscon f44 jfalempe
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)