releng

#11674 Unable to push initial dist-git commit for rust-libcryptsetup-rs0.8 compat package for F38 (and maybe F37)
Closed: It's all good by bgurney. Opened by bgurney.

Closed: It's all good
Reopen Issue
  • Describe the issue
    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 "remote: Denied push for ref 'refs/heads/f38' for user 'bgurney'". I suspect that the "f38" branch doesn't exist, because the repo was requested with the "--no-initial-commit" option.

I also need to create a release for this compat package for f37. I haven't tried f37 yet, because I wanted to wait until the f38 release was created in Bodhi.

  • When do you need this? (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.

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

  • If we cannot complete your request, what is the impact?
    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 quickly looked at the rust-libcryptsetup-rs0.8 repo and it's missing F37 and F38 branches. I'm not sure if these should be created automatically during repo creating or they should be created or requested by user.

I would assume that running "fedpkg request-repo ... --no-initial-commit" would potentially also not create the branches. When I created it initially, there were no branches at all.

I had to run "git push -u origin rawhide" to push the Rawhide, commit, and it worked. And running "git push -u origin f39" also worked. But "git push -u origin f38" didn't.

(also, sorry about the mess; our team is trying to figure out a good way to create Rust compat packages, and this process that involves "fedpkg request-repo .. --no-initial-commit" probably isn't the most optimal way.)

You should use fedpkg for most of the work. See the packaging guidelines

fedpkg reports this:

$ fedpkg push
fatal: The current branch f38 has no upstream branch.
To push the current branch and set the remote as upstream, use
    git push --set-upstream origin f38

...and I ran "git push -u origin f38", and it failed.

We already have builds for Rawhide and F39 for this package, and they are tested as working. Guidelines exist for normal situations, and this is not a normal situation. We have to find a way forward.

If you're going to sit here and point to policy, please escalate to someone who can help. Otherwise, I'm leaving this until next week, so Mulhern can find someone who can help us.

You need to request f38/f37 branches, just like you did for f39...

"When the repo is created, it only contains the rawhide branch. If you want to bring the package to other Fedora releases, request branches with fedpkg request-branch --repo PACKAGE-NAME BRANCH."

That should work and automation should just add them.

ie,

fedpkg request-branch --repo rust-libcryptsetup-rs0.8 f38
fedpkg request-branch --repo rust-libcryptsetup-rs0.8 f37

The exception is only needed to create the initial repo, from there it's all like normal packages.

ok; trying the f38 request-branch command now.

Hi @bgurney,

You/maintainer didn't request branch f38 only f39 and rawhide.

https://pagure.io/releng/fedora-scm-requests/issues?status=Closed&search_pattern=rust-libcryptsetup-rs0.8&close_status=

You should get familiar with the process before saying to anybody they just sit here...

Metadata Update from @humaton:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

Looks good; I ran "git fetch origin" and saw this:

 * [new branch]      f38        -> origin/f38

I'm going to run a scratch build again on the compat package and the new one, just to make sure I won't FTBFS, and then I'll continue with the builds.

Thanks for the help!

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

Metadata Update from @bgurney:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

Sorry this has been all a complex hassle. ;(

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.