#10724 Package rubygem-ruby_parser is retired in dist git, but PDC still see it as active
Opened 4 months ago by zlopez. Modified 3 months ago

  • Describe the issue
    Today I found an issue on the-new-hotness and when doing the investigation I found out that the package is actually retired, but it seems to be still active in PDC.

Package dist-git contains only dead.package file, but the PDC request

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

4 months ago

@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.

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.

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

3 months ago

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

  1. gives us more control should we ever want to migrate to another way of
    handling this.

  2. will also require some API token to authenticate the user, which people may
    or may not have/want to deal with.

Login to comment on this ticket.

Metadata
Boards 1
Dev Status: Backlog