Bug 1780007 - twolame-0.4.0 is available
Summary: twolame-0.4.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: twolame
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simone Caronni
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1767974 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-05 08:50 UTC by Upstream Release Monitoring
Modified: 2022-09-05 09:13 UTC (History)
3 users (show)

Fixed In Version: twolame-0.4.0-1.fc36 twolame-0.4.0-1.fc35
Clone Of:
Environment:
Last Closed: 2022-08-24 20:31:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 0.4.0 (#1780007) (1.06 KB, patch)
2019-12-05 08:51 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2019-12-05 08:50:56 UTC
Latest upstream release: 0.4.0
Current version/release in rawhide: 0.3.13-14.fc31
URL: http://www.twolame.org/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/12524/

Comment 1 Upstream Release Monitoring 2019-12-05 08:51:02 UTC
Created attachment 1642300 [details]
[patch] Update to 0.4.0 (#1780007)

Comment 2 Upstream Release Monitoring 2019-12-05 08:55:13 UTC
the-new-hotness/release-monitoring.org's scratch build of twolame-0.4.0-1.fc29.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=39437927

Comment 3 barsnick 2020-01-14 13:24:27 UTC
*** Bug 1767974 has been marked as a duplicate of this bug. ***

Comment 4 barsnick 2020-01-14 13:28:15 UTC
Please note my remarks in bug 1641446 (marked as duplicate of this one) that the lib's ABI has changed without an SONAME version bump.

Comment 5 Fedora Update System 2022-08-20 07:38:56 UTC
FEDORA-2022-564484bcd4 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-564484bcd4

Comment 6 Fedora Update System 2022-08-20 07:38:57 UTC
FEDORA-2022-5d03fe24dc has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5d03fe24dc

Comment 7 Fedora Update System 2022-08-22 02:28:25 UTC
FEDORA-2022-5d03fe24dc has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-5d03fe24dc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5d03fe24dc

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

Comment 8 Fedora Update System 2022-08-22 02:41:07 UTC
FEDORA-2022-564484bcd4 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-564484bcd4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-564484bcd4

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

Comment 9 Fedora Update System 2022-08-24 20:31:03 UTC
FEDORA-2022-5d03fe24dc has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-09-05 09:13:12 UTC
FEDORA-2022-564484bcd4 has been pushed to the Fedora 35 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.