Use a different package for dependency test

[psss]

The dummy-test-package-crested package is no more maintained, let's use a different one.

Related pull request:

• Use a different package for upgrade dependency test tmt#4725

[psklenar]

Hi,
I noticed the reboot logic could be improved to follow the official Fedora guidelines. I've implemented a fix based on the Fedora Quick Docs in my fork.
If you’re using DNF 5 (starting from Fedora 41+)

Feel free to cherry-pick this commit into your PR:
psklenar/upgrade@3a26809"

anyway, upgrade started, but machine was not upgraded. It was still f43 after the upgrade to f44.
No idea whats happening during the reboot as its not visible from logs :(

testing-farm-internal request --test-type fmf --git-url https://gitlab.cee.redhat.com/psklenar/tft_mine.git --git-ref main --plan "/upgrade/superplan" --compose Fedora-43 --arch x86_64
https://artifacts.osci.redhat.com/testing-farm/108a22f3-9962-4337-bf70-0092e49d2d00/

[LecrisUT]

LGTM. @psss can you confirm again the merge order of these? This one should be merged first and then teemtee/tmt#4725 should go in?

---

anyway, upgrade started, but machine was not upgraded. It was still f43 after the upgrade to f44. No idea whats happening during the reboot as its not visible from logs :(

It should be independent to this change though right? For now want to focus on getting teemtee/tmt#4725 in

[psss]

@psss can you confirm again the merge order of these? This one should be merged first and then teemtee/tmt#4725 should go in?

Yes, whenever 4725 is at the top of the merge queue, this one should be merged, 4725 test jobs restarted to make sure everything works fine with the new required package and merge.

[psss]

Feel free to cherry-pick this commit into your PR: psklenar/upgrade@3a26809"

@psklenar, thanks for the hint. Actually, we've discussed using dnf5 offline reboot here:

• Run upgrade via dnf5 offline reboot #15

There @mmacura311 suggested this is low-level functionality not expected to be used by users:

Hi @psss
according the documentation
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
the user should run dnf system-upgrade download ... and afterwards dnf system-upgrade reboot so TBH I do not see a need to run the dnf5 offline which looks like lower-level functionality to perform offlne transactions.

Now I see that dnf5 offline reboot is also mentioned in the upgrade docs. So not completely sure.

anyway, upgrade started, but machine was not upgraded. It was still f43 after the upgrade to f44. No idea whats happening during the reboot as its not visible from logs :(

Hmmm, does it seem to be limited to f43-to-f44 scenario? I just checked a recent upgrade job which exercises f42-to-f43 and there everything seems to be working just fine.

[LecrisUT]

Well, will merge and go ahead with teemtee/tmt#4725. We can figure out the rest with the subsequent PRs that are coming