Learn more about these different git repos.
Other Git URLs
Package dist-git contains only dead.package file, but the PDC request
dead.package
Not sure what happened here, but this doesn't seem correct.
When do you need this? (YYYY/MM/DD) This is not urgent
When is this no longer needed or useful? (YYYY/MM/DD) When the PDC is no longer a thing
If we cannot complete your request, what is the impact? Not a big impact, just failed scratch build for the package based on the monitoring setting. Maybe it would be good to also disable monitoring, when the package is retired or orphaned.
Hi, I have removed the log paste so we don't have to scroll through it on every comment.
The package in question has updated SLAs.
AS it goes for the future, can you point me to a doc/api how to disable monitoring for a particular package?
@humaton IIRC, the-new-hotness will automatically disable monitoring when a package gets retired, @zlopez can you confirm?
Metadata Update from @mohanboddu: - Issue tagged with: low-gain, low-trouble, ops
@mohanboddu This is not correct, when the package is retired the-new-hotness will just skip the package and will not check the the monitoring status. It just reads the information from src.fedoraproject.org, doesn't change anything.
@humaton The monitoring setting is changed directly on the dist_git. It is the monitoring status option at the left bottom menu on every package. I think there is even an API that could be used to change the monitoring setting.
monitoring status
Hmm, that is funny because there is no word about monitoring in the API docs but I can see something here however when I try that endpoint on random projects I get 404.
The API docs running at /api/0/ is created from the main/regular API, the endpoints added by 3rd party plugins aren't gathered there :(
The fedscm_admin uses the web endpoint to set the monitoring setting.
We have 2 options here:
1, implement API call in rpkg underlining the library that is used by fedpkg
2, Implement it in toddlers, on commit messages containing dead.package file
Metadata Update from @humaton: - Issue untagged with: low-gain, low-trouble, ops - Issue tagged with: dev, medium-gain, medium-trouble
We have 2 options here: 1, implement API call in rpkg underlining the library that is used by fedpkg 2, Implement it in toddlers, on commit messages containing dead.package file
gives us more control should we ever want to migrate to another way of handling this.
will also require some API token to authenticate the user, which people may or may not have/want to deal with.
How can I reproduce this?
For curl "https://pdc.stg.fedoraproject.org/rest_api/v1/component-branches/?global_component=rubygem-ruby_parser&type=rpm&active=true" I get this result: {"count":0,"next":null,"previous":null,"results":[]}
curl "https://pdc.stg.fedoraproject.org/rest_api/v1/component-branches/?global_component=rubygem-ruby_parser&type=rpm&active=true"
{"count":0,"next":null,"previous":null,"results":[]}
For curl "https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=rubygem-ruby_parser&type=rpm&active=true" I get {"count":0,"next":null,"previous":null,"results":[]}.
curl "https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=rubygem-ruby_parser&type=rpm&active=true"
I don't see any active.
Pull request to disable monitoring when a package is retiring : https://pagure.io/rpkg/pull-request/646
Thanks @lenkaseg !
That PR is still marked WIP... let us know when it's ready. I guess it needs a matching fedpkg PR too?
@kevin yes, I have the change in fedpkg ready. Before I open a PR I'm trying to figure out how to test it on staging. When it's ready for review I'll remove the [WIP]
The fedpkg pull request: https://pagure.io/fedpkg/pull-request/497
fedpkg
It is tested on staging, it seems to work.
Login to comment on this ticket.