#11524 Unable to push initial dist-git commit for rust-libcryptsetup-rs0.8 compat package for F38 (and maybe F37)
Closed: Invalid by zlopez. Opened by bgurney.

NOTE

If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.

Describe what you would like us to do:


I'm performing an initial package update for a Rust compat package, rust-libcryptsetup-rs0.8, which will be providing a compatibility package for rust-libcryptsetup-rs version 0.8.0, as I build and release rust-libcryptsetup-rs 0.9.0, in a side tag.

(The Stratis project's upstream issue for this release is here: https://github.com/stratis-storage/project/issues/658 )

(The Upstream Release Monitoring BZ for rust-libcryptsetup-rs-0.9.0 is here: https://bugzilla.redhat.com/show_bug.cgi?id=2238430 )

The repo was requested with this command: "fedpkg request-repo rust-libcryptsetup-rs0.8 --no-initial-commit --exception" ...and that may have resulted in something missing, as I was able to run "git push -u origin rawhide" for the initial Rawhide commit (as the remote had no branches set up), as well as "git push -u origin f39".

However, on trying to push the f38 branch, I see this:

$ git push -u origin f38
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
remote: Unspecified ref refs/heads/f38 is blocked
remote: Denied push for ref 'refs/heads/f38' for user 'bgurney'
remote: All changes have been rejected
To ssh://pkgs.fedoraproject.org/rpms/rust-libcryptsetup-rs0.8
 ! [remote rejected] f38 -> f38 (pre-receive hook declined)
error: failed to push some refs to 'ssh://pkgs.fedoraproject.org/rpms/rust-libcryptsetup-rs0.8'

...and I need to do an f37 release for this package, and fear I might encounter the same error for f37.

Is there something on the server side that's missing, preventing an F38 and F37 dist-git commit from being pushed?

When do you need this to be done by? (YYYY/MM/DD)


It would be nice if this could be done by 18:00 EDT (UTC - 4) on September 15, 2023, but if it needs to wait for a few days, that's not too much of a problem. The stratisd package may need the compat package to be available to continue building. (I say "may", because I haven't seen a failure yet, but the compat package is being created to avert a build failure of stratisd.)


I looked at the repo and there are no branches for F37 and F38. You should fill this issue in releng tracker

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

Metadata