Bug 2188544
| Summary: | No release monitoring and no recent releases available - blocks upgrade to Fedora 38 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kees de Jong <keesdejong+dev> |
| Component: | yubioath-desktop | Assignee: | Gerald Cox <gbcox> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | gbcox, orion, sethdjennings |
| Target Milestone: | --- | Keywords: | Desktop, UpgradeBlocker |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://github.com/Yubico/yubioath-flutter/releases | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-04-21 09:31:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kees de Jong
2023-04-21 06:01:05 UTC
yubioath is no longer available in the fedora repository. Please review bug: 2136583 for more information and the included link to the discussion for mitigation. *** This bug has been marked as a duplicate of bug 2136583 *** Here is the direct link to the discussion that gives a good history and provides the recommended mitigation, so you don't have to slog through the bugzilla ticket: https://discussion.fedoraproject.org/t/f38-yubioath-desktop-will-no-longer-be-available-in-fedora-repository/45921 Isn't there a general cleanup package that obsoletes packages that have dropped from the distro? yubioath-desktop probably should be added to that. If you want to try it, there is https://copr.fedorainfracloud.org/coprs/orion/yubico-authenticator/ which is simply a repackaging of the binary tarball but does give you desktop integration. Yes I followed the package retirement process. In this instance I decided to allow people to decide which mitigation path to take rather than forcing them to a specific path. I found at least for my workflow that ykocli works better than the new flutter based solution. |