Learn more about these different git repos.
Other Git URLs
In the "Create New Update page", I can search out my build dropwatch-1.5.3-6.el9. After fill the description, set type to newpackage, set bug field to false. disable require testcases.
At latest, submit the request. the webpage shows error "HTTPForbidden : Access was denied to this resource."
I also tried with fedpkg update and bodhi-cli, both are not working.
fedpkg update
When do you need this? (YYYY/MM/DD) ASAP
When is this no longer needed or useful? (YYYY/MM/DD) when dropwatch be able to added to elep9
If we cannot complete your request, what is the impact? dropwatch was removed from RHEL9. If user wants to use it, they have to install it via epel9. Without this, they have to build it themselves. <img alt="1.png" src="/releng/issue/raw/files/d5acfdd60aaac6053a37497ab841990e748f3a1d28616fe4899787bd970ca151-1.png" />
Metadata Update from @mohanboddu: - Issue tagged with: high-trouble, medium-gain, ops
Metadata Update from @mohanboddu: - Issue untagged with: high-trouble - Issue tagged with: medium-trouble
Can you remove .fedora/openidbaseclient-sessions.cache and try again with bodhi client and/or get a new kerberos ticket and try with fedpkg client and/or logout and login again on bodhi web then try to create the update?
.fedora/openidbaseclient-sessions.cache
Logout and login again on bodhi web do not work.
re-do fedpkg update also does not work..
$ rm -f ~/.fedora/openidbaseclient-sessions.cache $ kinit liuhangbin@FEDORAPROJECT.ORG Password for liuhangbin@FEDORAPROJECT.ORG: $ fedpkg update Password: Could not execute update: Could not generate update request: A copy of the filled in template is saved as bodhi.template.last
Hmm, you FAS seems to be missing any groups https://fasjson.fedoraproject.org/v1/users/liuhangbin/groups/
@humaton Then what I should do about this issue? Thanks
@mohanboddu Hi, is there anything I can do about this issue?
hello?
Ah, I find this doc How_to_Get_Sponsored_into_the_Packager_Group . I will follow the steps and try join the packager group first.
packager
I am very puzzled how this could occur.
Are you using https or ssh to push your commits?
Can you try pushing a simple empty file commit or the like and tell us exactly what the output from it is and what time you did it so we can check logs?
Do you mean why I could not request budhi update (the reason should be that I didn't join the packager group ) or why I can push commit without packager group?
I use https and fedpkg push to push my commit.
fedpkg push
I just did a rebase on epel9 branch and pushed it.
Here is the log
$ fedpkg push Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: 2022-02-20 05:31:21,709 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2022-02-20 05:31:21,709 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2022-02-20 05:31:21,718 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTest Helper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pag ure': 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: 2022-02-20 05:31:21,718 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTest Helper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pag ure': 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: 2022-02-20 05:31:21,783 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2022-02-20 05:31:21,783 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2022-02-20 05:31:21,801 [DEBUG] pagure.utils: User is a committer remote: 2022-02-20 05:31:21,801 [DEBUG] pagure.utils: User is a committer remote: 2022-02-20 05:31:23,271 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2022-02-20 05:31:23,271 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2022-02-20 05:31:23,280 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTest Helper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pag ure': 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: 2022-02-20 05:31:23,280 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTest Helper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pag ure': 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: 2022-02-20 05:31:23,345 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2022-02-20 05:31:23,345 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2022-02-20 05:31:23,362 [DEBUG] pagure.utils: User is a committer remote: 2022-02-20 05:31:23,362 [DEBUG] pagure.utils: User is a committer remote: Emitting a message to the fedora-messaging message bus. remote: * Publishing information for 2 commits remote: 2022-02-20 05:31:24,782 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2022-02-20 05:31:24,782 [INFO] pagure.lib.git_auth: Looking for backend: distgit remote: 2022-02-20 05:31:24,790 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTest Helper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pag ure': 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: 2022-02-20 05:31:24,790 [DEBUG] pagure.lib.git_auth: Found the following installed helpers {'test_auth': EntryPoint.parse('test_auth = pagure.lib.git_auth:GitAuthTest Helper'), 'gitolite2': EntryPoint.parse('gitolite2 = pagure.lib.git_auth:Gitolite2Auth'), 'gitolite3': EntryPoint.parse('gitolite3 = pagure.lib.git_auth:Gitolite3Auth'), 'pag ure': 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: 2022-02-20 05:31:24,856 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2022-02-20 05:31:24,856 [DEBUG] pagure.lib.git_auth: Returning helper <class 'dist_git_auth.DistGitAuth'> from backend key 'distgit' remote: 2022-02-20 05:31:25,042 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive remote: 2022-02-20 05:31:25,042 [INFO] pagure.lib.notify: Sending blinker signal to: pagure - topic: git.receive remote: 2022-02-20 05:31:25,266 [INFO] fedora_messaging.message: Registering the 'pagure.Test.notification' key as the '<class 'pagure_messages.misc_schema.TestNotificationV1 '>' class in the Message class registry remote: 2022-02-20 05:31:25,268 [INFO] fedora_messaging.message: Registering the 'pagure.commit.flag.added' key as the '<class 'pagure_messages.misc_schema.CommitFlagAddedV1' >' class in the Message class registry remote: 2022-02-20 05:31:25,269 [INFO] fedora_messaging.message: Registering the 'pagure.commit.flag.updated' key as the '<class 'pagure_messages.misc_schema.CommitFlagUpdate dV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,271 [INFO] fedora_messaging.message: Registering the 'pagure.git.branch.creation' key as the '<class 'pagure_messages.git_schema.GitBranchCreation V1'>' class in the Message class registry remote: 2022-02-20 05:31:25,272 [INFO] fedora_messaging.message: Registering the 'pagure.git.branch.deletion' key as the '<class 'pagure_messages.git_schema.GitBranchDeletion V1'>' class in the Message class registry remote: 2022-02-20 05:31:25,274 [INFO] fedora_messaging.message: Registering the 'pagure.git.receive' key as the '<class 'pagure_messages.git_schema.GitReceiveV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,275 [INFO] fedora_messaging.message: Registering the 'pagure.git.tag.creation' key as the '<class 'pagure_messages.git_schema.GitTagCreationV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,277 [INFO] fedora_messaging.message: Registering the 'pagure.git.tag.deletion' key as the '<class 'pagure_messages.git_schema.GitTagDeletionV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,278 [INFO] fedora_messaging.message: Registering the 'pagure.group.edit' key as the '<class 'pagure_messages.misc_schema.GroupEditV1'>' class in t he Message class registry remote: 2022-02-20 05:31:25,280 [INFO] fedora_messaging.message: Registering the 'pagure.issue.assigned.added' key as the '<class 'pagure_messages.issue_schema.IssueAssignedA ddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,281 [INFO] fedora_messaging.message: Registering the 'pagure.issue.assigned.reset' key as the '<class 'pagure_messages.issue_schema.IssueAssignedR esetV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,283 [INFO] fedora_messaging.message: Registering the 'pagure.issue.comment.added' key as the '<class 'pagure_messages.issue_schema.IssueCommentAdd edV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,284 [INFO] fedora_messaging.message: Registering the 'pagure.issue.dependency.added' key as the '<class 'pagure_messages.issue_schema.IssueDepende ncyAddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,286 [INFO] fedora_messaging.message: Registering the 'pagure.issue.dependency.removed' key as the '<class 'pagure_messages.issue_schema.IssueDepen dencyRemovedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,287 [INFO] fedora_messaging.message: Registering the 'pagure.issue.drop' key as the '<class 'pagure_messages.issue_schema.IssueDropV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,289 [INFO] fedora_messaging.message: Registering the 'pagure.issue.edit' key as the '<class 'pagure_messages.issue_schema.IssueEditV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,291 [INFO] fedora_messaging.message: Registering the 'pagure.issue.new' key as the '<class 'pagure_messages.issue_schema.IssueNewV1'>' class in th e Message class registry remote: 2022-02-20 05:31:25,292 [INFO] fedora_messaging.message: Registering the 'pagure.issue.tag.added' key as the '<class 'pagure_messages.issue_schema.IssueTagAddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,294 [INFO] fedora_messaging.message: Registering the 'pagure.issue.tag.removed' key as the '<class 'pagure_messages.issue_schema.IssueTagRemovedV1 '>' class in the Message class registry remote: 2022-02-20 05:31:25,295 [INFO] fedora_messaging.message: Registering the 'pagure.project.deleted' key as the '<class 'pagure_messages.project_schema.ProjectDeletedV1' >' class in the Message class registry remote: 2022-02-20 05:31:25,297 [INFO] fedora_messaging.message: Registering the 'pagure.project.edit' key as the '<class 'pagure_messages.project_schema.ProjectEditV1'>' cla ss in the Message class registry remote: 2022-02-20 05:31:25,299 [INFO] fedora_messaging.message: Registering the 'pagure.project.forked' key as the '<class 'pagure_messages.project_schema.ProjectForkedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,300 [INFO] fedora_messaging.message: Registering the 'pagure.project.group.access.updated' key as the '<class 'pagure_messages.project_schema.Proj ectGroupAccessUpdatedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,302 [INFO] fedora_messaging.message: Registering the 'pagure.project.group.added' key as the '<class 'pagure_messages.project_schema.ProjectGroupA ddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,303 [INFO] fedora_messaging.message: Registering the 'pagure.project.group.removed' key as the '<class 'pagure_messages.project_schema.ProjectGrou pRemovedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,305 [INFO] fedora_messaging.message: Registering the 'pagure.project.new' key as the '<class 'pagure_messages.project_schema.ProjectNewV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,306 [INFO] fedora_messaging.message: Registering the 'pagure.project.tag.edited' key as the '<class 'pagure_messages.project_schema.ProjectTagEdit edV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,308 [INFO] fedora_messaging.message: Registering the 'pagure.project.tag.removed' key as the '<class 'pagure_messages.project_schema.ProjectTagRem ovedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,309 [INFO] fedora_messaging.message: Registering the 'pagure.project.user.access.updated' key as the '<class 'pagure_messages.project_schema.Proje ctUserAccessUpdatedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,311 [INFO] fedora_messaging.message: Registering the 'pagure.project.user.added' key as the '<class 'pagure_messages.project_schema.ProjectUserAdd edV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,312 [INFO] fedora_messaging.message: Registering the 'pagure.project.user.removed' key as the '<class 'pagure_messages.project_schema.ProjectUserR emovedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,314 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.assigned.added' key as the '<class 'pagure_messages.pull_requests_schema .PullRequestAssignedAddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,315 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.assigned.reset' key as the '<class 'pagure_messages.pull_requests_schema .PullRequestAssignedResetV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,317 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.closed' key as the '<class 'pagure_messages.pull_requests_schema.PullReq uestClosedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,319 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.comment.added' key as the '<class 'pagure_messages.pull_requests_schema. PullRequestCommentAddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,320 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.comment.edited' key as the '<class 'pagure_messages.pull_requests_schema .PullRequestCommentEditedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,322 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.flag.added' key as the '<class 'pagure_messages.pull_requests_schema.Pul lRequestFlagAddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,323 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.flag.updated' key as the '<class 'pagure_messages.pull_requests_schema.P ullRequestFlagUpdatedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,325 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.initial_comment.edited' key as the '<class 'pagure_messages.pull_request s_schema.PullRequestInitialCommentEditedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,326 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.new' key as the '<class 'pagure_messages.pull_requests_schema.PullReques tNewV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,328 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.rebased' key as the '<class 'pagure_messages.pull_requests_schema.PullRe questRebasedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,330 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.reopened' key as the '<class 'pagure_messages.pull_requests_schema.PullR equestReopenedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,331 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.tag.added' key as the '<class 'pagure_messages.pull_requests_schema.Pull RequestTagAddedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,333 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.tag.removed' key as the '<class 'pagure_messages.pull_requests_schema.Pu llRequestTagRemovedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,334 [INFO] fedora_messaging.message: Registering the 'pagure.pull-request.updated' key as the '<class 'pagure_messages.pull_requests_schema.PullRe questUpdatedV1'>' class in the Message class registry remote: 2022-02-20 05:31:25,336 [INFO] fedora_messaging.message: Registering the 'base.message' key as the '<class 'fedora_messaging.message.Message'>' class in the Message c lass registry remote: 2022-02-20 05:31:25,343 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive remote: 2022-02-20 05:31:25,343 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive remote: 2022-02-20 05:31:25,347 [INFO] twisted: Log opened. remote: 2022-02-20 05:31:25,347 [INFO] fedora_messaging.config: Loading configuration from /etc/fedora-messaging/config.toml remote: 2022-02-20 05:31:25,354 [INFO] fedora_messaging.twisted.service: Authenticating with server using x509 (certfile: /etc/pki/rabbitmq/pagurecert/src.fp.o.crt, keyfile: /etc/pki/rabbitmq/pagurecert/src.fp.o.key) remote: 2022-02-20 05:31:25,365 [INFO] twisted: Starting factory FedoraMessagingFactoryV2(parameters=<URLParameters host=rabbitmq.fedoraproject.org port=5671 virtual_host=/pu bsub ssl=True>, confirms=True) remote: Sending to redis to log activity and send commit notification emails remote: * Publishing information for 2 commits remote: - to fedora-message remote: remote: Create a pull-request for epel9 remote: https://src.fedoraproject.org/rpms/dropwatch/diff/rawhide..epel9 remote: remote: 2022-02-20 05:31:25,447 [INFO] fedora_messaging.twisted.protocol: Waiting for 0 consumer(s) to finish processing before halting remote: 2022-02-20 05:31:25,448 [INFO] fedora_messaging.twisted.protocol: Finished canceling 0 consumers remote: 2022-02-20 05:31:25,448 [INFO] pika.channel: Closing channel (200): 'Normal shutdown' on <Channel number=1 OPEN conn=<pika.adapters.twisted_connection._TwistedConnect ionAdapter object at 0x7f3a84587668>> remote: 2022-02-20 05:31:25,448 [INFO] pika.channel: Closing channel (200): 'Normal shutdown' on <Channel number=2 OPEN conn=<pika.adapters.twisted_connection._TwistedConnect ionAdapter object at 0x7f3a84587668>> remote: 2022-02-20 05:31:25,448 [INFO] pika.connection: Closing connection (200): 'Normal shutdown' remote: 2022-02-20 05:31:25,448 [INFO] pika.connection: Connection.close is waiting for 2 channels to close: <pika.adapters.twisted_connection._TwistedConnectionAdapter objec t at 0x7f3a84587668> remote: 2022-02-20 05:31:25,449 [INFO] pika.channel: Received <Channel.CloseOk> on <Channel number=2 CLOSING conn=<pika.adapters.twisted_connection._TwistedConnectionAdapter object at 0x7f3a84587668>> remote: 2022-02-20 05:31:25,450 [INFO] pika.channel: Received <Channel.CloseOk> on <Channel number=1 CLOSING conn=<pika.adapters.twisted_connection._TwistedConnectionAdapter object at 0x7f3a84587668>> remote: 2022-02-20 05:31:25,452 [INFO] pika.connection: AMQP stack terminated, failed to connect, or aborted: error-arg=None; pending-error=ConnectionDone() remote: 2022-02-20 05:31:25,452 [INFO] pika.connection: Stack terminated due to ConnectionDone() remote: 2022-02-20 05:31:25,453 [INFO] fedora_messaging.twisted.protocol: Disconnect requested, but AMQP connection already gone remote: 2022-02-20 05:31:25,453 [INFO] twisted: Stopping factory FedoraMessagingFactoryV2(parameters=<URLParameters host=rabbitmq.fedoraproject.org port=5671 virtual_host=/pu bsub ssl=True>, confirms=True) remote: 2022-02-20 05:31:25,454 [INFO] twisted: Main loop terminated. To https://src.fedoraproject.org/rpms/dropwatch.git a7edd2c..dfb9c27 epel9 -> epel9 $ date -u Sun Feb 20 05:32:33 AM UTC 2022
Hum.
@pingou could I get you to look at this?
I see this in the logs:
Feb 20 05:31:24 pkgs01.iad2.fedoraproject.org celery[1074]: 2022-02-20 05:31:24,992 [INFO] pagure.lib.tasks_services: Looking for project: rpms/dropwatch of None Feb 20 05:31:24 pkgs01.iad2.fedoraproject.org celery[1074]: 2022-02-20 05:31:24,992 [INFO] pagure.lib.tasks_services: Looking for project: rpms/dropwatch of None Feb 20 05:31:25 pkgs01.iad2.fedoraproject.org celery[1074]: 2022-02-20 05:31:25,007 [INFO] pagure.lib.tasks_services: Found project: rpms/dropwatch Feb 20 05:31:25 pkgs01.iad2.fedoraproject.org celery[1074]: 2022-02-20 05:31:25,007 [INFO] pagure.lib.tasks_services: Processing 2 commits in /srv/git/repositories/rpms/dropwatch.git
Might it be allowing the commit because they are owner, even though they are not in the packager group?
Hello, @mrunge has helped add me to the packager group in sponsors ticket 523. And I have permission to submit updates in bodhi now. Although it said "Update for dropwatch-1.5.3-6.el9 already exists". Then I searched and found @humaton has helped submit the update 2 weeks ago.
Thanks to everyone for the help. Please feel free to close this ticket now.
I'd like to keep this open until we figure out how this was possible...
I'd like to keep this open until we figure out how this was possible... OK for me
OK for me
@kevin I think what happened is @humaton might have assigned the dropwatch package to @liuhangbin without checking whether he is a packager or not when he requested for unretirement for the package. That gave him the permissions to push it to dist-git repo, but when he tried to submit the update bodhi checked for the packager permission and wasn't able to create the update until he was sponsored.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.