Thanks for filing up the issue. Do you intend to spin up an fedora image or recommend one on which you want us to install the COPR software version? Also, is the new version going to also be used for testing upgrades...?

@kparal @adamwill , do you know how we can trick the system into thinking there is an upgrade especially if the build is Rawhide only?

Hi Sumantro,

I didn’t originally plan to create a custom Fedora image for testing, but if you think it would make things easier for users, we can certainly prepare one. Otherwise, since this change is intended for Fedora 42 (current Rawhide), testing it in that environment would likely be best.

As for testing upgrades, I assume you mean system upgrades. That would be useful, though I’m not sure how to approach it without a newer version beyond Rawhide to upgrade to...

Thanks for filing up the issue. Do you intend to spin up an fedora image or recommend one on which you want us to install the COPR software version? Also, is the new version going to also be used for testing upgrades...?

@kparal @adamwill , do you know how we can trick the system into thinking there is an upgrade especially if the build is Rawhide only?

To make sure there will always be an upgrade ready, we are doing the following in openQA:

1. Disable the updates repositories to prevent the system from knowing about updates.
2. Remove the acpica-tools package.
3. Download and install a fake repository curl -o /etc/yum.repos.d/openqa-testrepo-1.repo https://fedorapeople.org/groups/qa/openqa-repos/openqa-testrepo-1.repo. This repository contains an old version of acpica-tools.
4. Install the acpica-tools from that fake repository while disabling all other repositories to make sure the system does not know about any other packages and will install this particular version of the package, dnf -y --disablerepo=* --enablerepo=openqa-testrepo-1 install acpica-tools.
5. Now the system has an old version of acpica-tools so the newer version will be always available from the standard repositories, so you can use dnf update and there will be at least the newer version of acpica-tools ready for updates.
   4.

Hi Sumantro,

I didn’t originally plan to create a custom Fedora image for testing, but if you think it would make things easier for users, we can certainly prepare one. Otherwise, since this change is intended for Fedora 42 (current Rawhide), testing it in that environment would likely be best.

As for testing upgrades, I assume you mean system upgrades. That would be useful, though I’m not sure how to approach it without a newer version beyond Rawhide to upgrade to...

Nah lets sure Rawhide in this case. I will come up with test case by tomorrow and we should be able to sync up fix this! Thanks

@lruzicka a thousand hearts for the steps :D

wiki : http://fedoraproject.org/wiki/Test_Day:2025-02-10_GNOME_Software_with_dnf5
results : https://testdays.fedoraproject.org/events/208

cal : https://calendar.fedoraproject.org/QA/2025/2/10/#m10984
FedMag coming out soon!