Fix system updates for Nobara

[thecatcore]

Standards checklist:

• The PR title is descriptive.
• I have read CONTRIBUTING.md
• The code compiles (cargo build)
• The code passes rustfmt (cargo fmt)
• The code passes clippy (cargo clippy)
• The code passes tests (cargo test)
• Optional: I have tested the code myself

For new steps

• Optional: Topgrade skips this step where needed
• Optional: The --dry-run option works with this step
• Optional: The --yes option works with this step if it is supported by
  the underlying command

If you developed a feature or a bug fix for someone else and you do not have the
means to test it, please tag this person here.

Description

Nobara has some repositories that aren't updated by the default dnf distro-sync --refresh.
I've implemented the workaround indicated at Nobara Project.

[SteveLauC]

Hi, thanks for this patch!

What will happen if you simply run nobara-sync in your terminal? Will it only launch the Update System app, and thus you still need to click the update button yourself?

[SteveLauC]

Thanks for the PR!

Generally, I think we should follow the document, and use the suggested commands to do the update:

$ sudo dnf update rpmfusion-nonfree-release rpmfusion-free-release fedora-repos nobara-repos --refresh 
$ sudo dnf distro-sync --refresh 
$ sudo dnf update --refresh

though a -y option is needed is assume_yes is set to true.

[thecatcore]

Hi, thanks for this patch!

What will happen if you simply run nobara-sync in your terminal? Will it only launch the Update System app, and thus you still need to click the update button yourself?

Yes that is exactly what is happening, it opens the graphical app.

[thecatcore]

Thanks for the PR!

Generally, I think we should follow the document, and use the suggested commands to do the update:

$ sudo dnf update rpmfusion-nonfree-release rpmfusion-free-release fedora-repos nobara-repos --refresh 
$ sudo dnf distro-sync --refresh 
$ sudo dnf update --refresh

though a -y option is needed is assume_yes is set to true.

I agree with you, but using --refresh 3 times and update 2 times seems redundant, I've tested my implementation and it seems to be enough on my end so far.

[SteveLauC]

Thanks!