I retired pdfmod but an automatic step couldn’t be executed because I didn’t updated my token:
remote: Emitting a message to the fedora-messaging message bus. remote: * Publishing information for 1 commits remote: Sending to redis to log activity and send commit notification emails remote: * Publishing information for 1 commits remote: - to fedora-message remote: 2024-05-27 19:06:38,457 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive To ssh://pkgs.fedoraproject.org/rpms/pdfmod.git 6438599..b6cb722 rawhide -> rawhide Could not execute retire: The following error occurred while disabling monitoring: Invalid or expired token. Please visit https://src.fedoraproject.org/settings#nav-api-tab to get or renew your API token. For invalid or expired tokens please set a new token in your user configuration with: fedpkg set-distgit-token <token>
Is there any task I should perform to finish the procedure? I have my new token but don't see how to fix this by myself.
Thanks.
Looking at the logs, try doing fedpkg set-distgit-token <token> with the new token?
fedpkg set-distgit-token <token>
Ok so I checked the dist-git assuming, you wanted it to retire it from the rawhide branch only, it is rightly retired there[1], blocked from koji as well, and EOL is set properly at PDC[2]. I don't think there is anything there to do!
pdfmod f39-Beta olea pdfmod f41 olea [BLOCKED] pdfmod f40-Beta olea
[1] https://src.fedoraproject.org/rpms/pdfmod/branches?branchname=rawhide [2] https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?branch=rawhide&global_component=pdfmod
Metadata Update from @jnsamyak: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)
Thanks!
FYI, this issue is discussed here: https://pagure.io/fedpkg/issue/505
basically, it's trying to disable monitoring, but there's a number of reasons that wouldn't work. :(
we should fix this...