Bug 1917180 - uronode-2.13 is available
Summary: uronode-2.13 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: uronode
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: 2021-01-17 22:13 UTC by Upstream Release Monitoring
Modified: 2021-01-27 02:38 UTC (History)
1 user (show)

Fixed In Version: uronode-2.13-1.fc34 uronode-2.13-1.fc33 uronode-2.13-1.fc32
Clone Of:
Environment:
Last Closed: 2021-01-18 10:08:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 2.13 (#1917180) (1.03 KB, patch)
2021-01-17 22:13 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2021-01-17 22:13:08 UTC
Latest upstream release: 2.13
Current version/release in rawhide: 2.12-2.fc33
URL: http://uronode.sourceforge.net

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/10462/

Comment 1 Upstream Release Monitoring 2021-01-17 22:13:25 UTC
Created attachment 1748316 [details]
[patch] Update to 2.13 (#1917180)

Comment 2 Upstream Release Monitoring 2021-01-17 22:18:17 UTC
the-new-hotness/release-monitoring.org's scratch build of uronode-2.13-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=59918260

Comment 3 Fedora Update System 2021-01-18 10:08:51 UTC
FEDORA-2021-d61ccf42b3 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2021-01-18 10:18:19 UTC
FEDORA-2021-df58c5a7c4 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-df58c5a7c4

Comment 5 Fedora Update System 2021-01-18 10:18:46 UTC
FEDORA-2021-a419725f2b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a419725f2b

Comment 6 Fedora Update System 2021-01-19 01:37:41 UTC
FEDORA-2021-a419725f2b has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a419725f2b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a419725f2b

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

Comment 7 Fedora Update System 2021-01-19 01:51:42 UTC
FEDORA-2021-df58c5a7c4 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-df58c5a7c4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-df58c5a7c4

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

Comment 8 Fedora Update System 2021-01-27 01:17:52 UTC
FEDORA-2021-df58c5a7c4 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2021-01-27 02:38:22 UTC
FEDORA-2021-a419725f2b has been pushed to the Fedora 32 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.