Disable centos production repo, keep only development enabled.

[rvykydal]

The issue this patch is trying to resolve is older version of package in developemnt CentOS repository than in the production CentOS repository. For example for gtk package:

Error:
 Problem 1: package gtk3-devel-docs-3.24.43-2.el10.x86_64 from
crb-development requires gtk3 = 3.24.43-2.el10, but none of the providers can be installed
  - cannot install both gtk3-3.24.43-3.el10.x86_64 from appstream and gtk3-3.24.43-2.el10.x86_64 from appstream-development
  - cannot install both gtk3-3.24.43-3.el10.x86_64 from appstream and gtk3-3.24.43-2.el10.x86_64 from appstream
  - package gtk3-devel-3.24.43-3.el10.x86_64 from appstream requires gtk3(x86-64) = 3.24.43-3.el10, but none of the providers can be installed
  - cannot install the best candidate for the job
  - conflicting requests

If it the solution is acceptable, I'll update also anaconda-ci Dockerfile in the same manner?

[jkonecny12]

I think the proper solution should be to disable the production CentOS Stream repositories and using only the development one. Is there something blocking to do this?

[rvykydal]

I think the proper solution should be to disable the production CentOS Stream repositories and using only the development one. Is there something blocking to do this?

Agreed, I'll try to.

[rvykydal]

/kickstar-test --testtype smoke

[rvykydal]

/kickstart-test --testtype smoke

[rvykydal]

I think the proper solution should be to disable the production CentOS Stream repositories and using only the development one. Is there something blocking to do this?

Agreed, I'll try to.

@jkonecny12 I updated the PR to disable the production repo.
As you can see in the rpm tests possible downside compared to --nobest and both repos may be that as in this case it can happen that the development repo has significantly older content then the production one.

[rvykydal]

(Need to fix a typo in the commit message.)

[jkonecny12]

Something feels fishy here. As I understand it the package lifecycle goes:
development -> nightly -> production

so there shouldn't be a way of getting older packages from development or am I incorrect? I think that this situation happened because someone is trying to downgrade the package but I may be incorrect.