Issues with Repo Generation and/or metadata?

[sfalken]

I've been working on wlmaker in https://copr.fedorainfracloud.org/coprs/sfaulken/mir/package/wlmaker/

And seeing some weird behavior, where the repository that gets generated, was shipping out of date builds.

I was refactoring some of the Recommends in my build iterations, and the original package had a Recommends on Chromium, but even after removing that Recommend: the rpm I was downloading was trying to bring in chromium as a dependency.

I changed to manual Release: in my spec file, just to verify, and after getting a successful build of the -2 of the package, and clicking the "Regenerate Repositories" button in COPR, I still had to run dnf install --refresh wlmaker three times before dnf could see that there was a -2 release available, that reflected the proper package dependencies.

[FrostyX]

Hello @sfalken,
thank you for the report.

I would expect you to have to run the dnf install --refresh but not exactly three times like you are saying.

For future reference when somebody tries to reproduce:

• The project does not use "Create repositories manually" option
• The project is not in Pulp