We don't remove stable updates.

You will need to push a older version to get with a Epoch: added to make it downgrade from the old one. ;(

Sadly, you will also then need to add the Epoch to f38,rawhide, and moving forward too tho, so they get upgraded.

You can ask the devel list for more info...

Thanks for the quick response Kevin. Since that is the case, I'm just going leave it as it is. I don't really believe it's going to affect much people, and those it does affect can easily work around it manually.

Yeah, thats definitely an option, depending on how bad things are.

Possibly you could also look at making a common bugs for it? but I guess wait and see how much user feedback there is...

and those it does affect can easily work around it manually

Can you please provide some instructions how to work around?

Thanks for the quick response Kevin. Since that is the case, I'm just going leave it as it is.

Why? I think bumping epoch is a quick & easy fix. Are there any pitfalls?

and those it does affect can easily work around it manually

Can you please provide some instructions how to work around?

Sure. As it stands right now F37 will support yubikey-manager v5+ and also yubikey-manager-qt (the GUI interface). The only issue will be with yubioath-authenticator which provides totp codes. If you are using yubioath-authenticator, DNF will prevent you from upgrading to the current release of yubikey-manager (V5+). To stop the DNF dependency errors, all you need to do is to add the line: excludepkgs=yubikey-manager to the /etc/yum.repos.d/fedora-updates.repo file. If you decide you want to use the current yubikey-manager v5+; then you can follow the instructions here: https://discussion.fedoraproject.org/t/f38-yubioath-desktop-will-no-longer-be-available-in-fedora-repository/45921

If you have any further questions, issues, concerns, please respond to the bugzilla ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2189807

Thanks!

@solopasha Adding an epoch adds additional complexity and according to the packaging guidelines should only be used as a last resort. The impact of this now is very limited, and the workarounds (described in my comment above) are easy to implement.