Describe the issue I'm trying to reproduce issue https://pagure.io/fedora-infrastructure/issue/8150 in staging, but I'm now getting that package is retired, so the bugzilla issue creation is just skipped. Could you unretire golang-github-MakeNowJust-heredoc on staging? It will help me to check if my fix is really working.
When do you need this? (YYYY/MM/DD) ASAP
When is this no longer needed or useful? (YYYY/MM/DD) When bugzilla is no longer a thing
If we cannot complete your request, what is the impact? I can't test if the issue with the-new-hotness is fixed and it could happen again in the future
@zlopez As far as I can see, the package is not blocked in staging koji and there is no dead.package in the staging dist-git, but its eol'd in pdc which I just fixed, which means you should be able to push commits to staging dist-git.
dead.package
Is that all you wanted or you want to be added as a maintainer in stg dist-git as well, since I can see you are not a provenpackager, which means you cannot push changes to dist-git to all packages including golang-github-MakeNowJust-heredoc?
@mohanboddu Thanks, now the check in the-new-hotness is going through. However I'm hitting another issue in mdapi. It's not returning 200, so the-new-hotness just thinks that this package is not in koji., which is probably true, because otherwise I should get json response.
mdapi
Could you add it to mdapi?
I didn't get this, mdapi is not part of fedora and is always built in -infra tags which are available in stg as well.
-infra
https://koji.stg.fedoraproject.org/koji/packageinfo?packageID=23512
The-new-hotness is calling https://apps.stg.fedoraproject.org/mdapi/koji/srcpkg/golang-github-MakeNowJust-heredoc and expects to get json response, but instead it gets 400: Bad request.
https://apps.stg.fedoraproject.org/mdapi/koji/srcpkg/golang-github-MakeNowJust-heredoc
400: Bad request
I'm not sure if you could do anything about it.
With help from @cverna and @pingou I was able to reproduce the issue today. @mohanboddu thanks for help.
Metadata Update from @zlopez: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)