Learn more about these different git repos.
Other Git URLs
I cannot push to or merge PRs to the "jmc" and "jmc7" branches of rpms/jmc [0].
In addition to the main branch, the jmc repo also has "jmc" and "jmc7" branches that correspond with the "jmc:latest" and "jmc:7" module streams from modules/jmc [1]. Without access to these rpm branches I am unable to update the module.
This is an issue at the moment because of a potential broken installation of the jmc module streams. I've been trying to merge PRs [2][3], and pushing to the rpm branches directly, but I end up with the following error:
remote: 2021-01-13 21:36:34,992 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2021-01-13 21:36:34,992 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2021-01-13 21:36:34,999 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTestHelper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pagure': EntryPoint.parse('pagure = pagure.lib.git_auth:PagureGitAuth'), 'pagure_authorized_keys': EntryPoint.parse('pagure_authorized_keys = pagure.lib.git_auth:PagureGitAuth'), 'distgit': EntryPoint.parse('distgit = dist_git_auth:DistGitAuth') remote: 2021-01-13 21:36:34,999 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTestHelper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pagure': EntryPoint.parse('pagure = pagure.lib.git_auth:PagureGitAuth'), 'pagure_authorized_keys': EntryPoint.parse('pagure_authorized_keys = pagure.lib.git_auth:PagureGitAuth'), 'distgit': EntryPoint.parse('distgit = dist_git_auth:DistGitAuth') remote: 2021-01-13 21:36:35,063 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2021-01-13 21:36:35,063 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2021-01-13 21:36:35,082 [DEBUG] pagure.utils: User is a committer remote: 2021-01-13 21:36:35,082 [DEBUG] pagure.utils: User is a committer remote: 2021-01-13 21:36:35,128 [INFO] pagure_auth: Branch refs/heads/jmc is unsupported remote: Branch refs/heads/jmc is unsupported remote: Denied push for ref 'refs/heads/jmc' for user 'almac' remote: All changes have been rejected
I thought my issue was related to another on this issue tracker, but user pingou informed me that my difficulties may be a result of the branches either being EOL, or that they don't exist in PDC anymore [4].
If anyone could help me out or point me in the right direction it would be greatly appreciated!
[0] https://src.fedoraproject.org/rpms/jmc [1] https://src.fedoraproject.org/modules/jmc [2] https://src.fedoraproject.org/rpms/jmc/pull-request/24 [3] https://src.fedoraproject.org/rpms/jmc/pull-request/25 [4] https://pagure.io/releng/issue/9834#comment-709863
As soon as possible
I guess it wouldn't be needed when the module is unsupported after f32, however it is important to fix this issue ASAP as the installation issue is already tracked in rhbz.
Module jmc is not guaranteed to work on f32 due to a dependency issue on installation. I need to patch the jmc branches and rebuild the modules for updates.
@almac It is because when the branches were requested, they requested for a EOL date to 2020-12-01. I can extend it if you could let us know what date should we extend it to?
https://pagure.io/releng/fedora-scm-requests/issue/9277 https://pagure.io/releng/fedora-scm-requests/issue/11990
@mohanboddu Thank you for the quick reply! Is it possible to have a non-expiry on the branch? Or is it required to specify an end date?
Is it possible to have a non-expiry on the branch? Or is it required to specify an end date?
It needs to have a specific date :)
Is it possible to have a non-expiry on the branch? Or is it required to specify an end date? It needs to have a specific date :)
Aha, fair enough! Really we'd be hoping for as long as possible.. whatever that date can be set to.
Or if there's a maximum year, the same december 1st of that year works 20XX-12-01.
Otherwise something like 2030-12-01 should be okay.
Edit: er, the more I think about it, maybe another 2 years is okay and we can re-visit then.
2022-12-01
Hi @almac EOL for branches jmc and jmc7 is set to 2022-12-01. If there are any issues with this package/module please reopen this issue.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@humaton thank you for setting the new EOL for the rpms/jmc branches! I tested it out by merging one my PRs this morning, and it is working.
Having said that, I'm seeing a similar problem with modules/jmc, and wonder if it's the same EOL problem.
I tried pushing to modules/jmc/latest and am seeing:
remote: Branch refs/heads/latest is unsupported remote: Denied push for ref 'refs/heads/latest' for user 'almac' remote: All changes have been rejected To ssh://pkgs.fedoraproject.org/modules/jmc ! [remote rejected] latest -> latest (pre-receive hook declined) error: failed to push some refs to 'ssh://almac@pkgs.fedoraproject.org/modules/jmc'
The relevant branches for modules/jmc are "latest" and "7".
Metadata Update from @almac: - Issue status updated to: Open (was: Closed)
Metadata Update from @mohanboddu: - Issue tagged with: low-gain, low-trouble, ops
@almac That was correct and fixed module eol dates as well for 7 and latest branches.
7
latest
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.