Bug 1896920 - oath-toolkit-2.6.4 is available
Summary: oath-toolkit-2.6.4 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: oath-toolkit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-11 20:50 UTC by Upstream Release Monitoring
Modified: 2020-11-24 02:49 UTC (History)
2 users (show)

Fixed In Version: oath-toolkit-2.6.4-1.fc34 oath-toolkit-2.6.4-1.eln105 oath-toolkit-2.6.4-1.fc32 oath-toolkit-2.6.4-1.fc33
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-12 12:39:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 2.6.4 (#1896920) (987 bytes, patch)
2020-11-11 20:50 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2020-11-11 20:50:15 UTC
Latest upstream release: 2.6.4
Current version/release in rawhide: 2.6.3-1.fc34
URL: https://www.nongnu.org/oath-toolkit/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/2515/

Comment 1 Upstream Release Monitoring 2020-11-11 20:50:19 UTC
Created attachment 1728505 [details]
[patch] Update to 2.6.4 (#1896920)

Comment 2 Fedora Update System 2020-11-12 12:39:17 UTC
FEDORA-2020-81307987ca has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2020-11-12 12:57:20 UTC
FEDORA-2020-68d3b624a9 has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2020-11-12 13:07:41 UTC
FEDORA-2020-d03cb96179 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d03cb96179

Comment 5 Fedora Update System 2020-11-12 13:08:28 UTC
FEDORA-2020-314ba4522b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-314ba4522b

Comment 6 Fedora Update System 2020-11-13 01:47:44 UTC
FEDORA-2020-314ba4522b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-314ba4522b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-314ba4522b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-11-13 02:16:10 UTC
FEDORA-2020-d03cb96179 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d03cb96179`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d03cb96179

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2020-11-21 01:45:12 UTC
FEDORA-2020-314ba4522b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2020-11-24 02:49:45 UTC
FEDORA-2020-d03cb96179 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.