#12311 fedpkg request-branch --all-releases Attempts to Create F42 & Releng Bot Fails
Closed: Fixed 8 days ago by jnsamyak. Opened a month ago by jsteffan.

  • Describe the issue

Following the packaging guidelines for importing a package, fedpkg request-branch --all-releases creates f39->f42 and the f42 tag fails to work correctly. This seems appropriate that it fails as f42 should be rawhide. However, someone that knows should review:

https://pagure.io/releng/fedora-scm-requests/issue/66666
https://pagure.io/fedpkg/issue/566

  • When do you need this? (YYYY/MM/DD)

At leisure.

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

N/A

  • If we cannot complete your request, what is the impact?

Extra SCM requests are opened and fail. This does not impact maintainers from being able to manage/import new packages.


Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, low-trouble, ops

a month ago

I agree with your point, but this seems like a fedpkg (upstream) issue to me! Thanks for opening the ticket here, I'll check what more can be done from the fedpg end :D

This seems to have happened with rust-eif_build too: https://src.fedoraproject.org/rpms/rust-eif_build

It's owned by releng-bot instead of me, and I can't request branches.

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

a month ago

Metadata Update from @jnsamyak:
- Issue untagged with: low-gain, low-trouble
- Issue tagged with: medium-gain, medium-trouble

a month ago

Worked on a pr: https://pagure.io/fedpkg/pull-request/573 to dynamically handle rawhide release branches and excluding it from being considered as an active release!

Closing this, since this is an upstream request, and I already have put a PR to fix this, and we can track this at: https://pagure.io/fedpkg/issue/566

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

8 days ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog