Bug 1892705 - yoshimi-1.7.4 is available
Summary: yoshimi-1.7.4 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: yoshimi
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Huffman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-29 13:45 UTC by Upstream Release Monitoring
Modified: 2021-01-15 01:26 UTC (History)
1 user (show)

Fixed In Version: yoshimi-1.7.4-1.fc33
Clone Of:
Environment:
Last Closed: 2021-01-15 01:26:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 1.7.4 (#1892705) (957 bytes, patch)
2021-01-05 19:18 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2020-10-29 13:45:07 UTC
Latest upstream release: 1.7.3
Current version/release in rawhide: 1.7.2-1.fc34
URL: http://sourceforge.net/projects/yoshimi

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

Comment 1 Upstream Release Monitoring 2020-10-29 13:45:10 UTC
The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you.  Please use URLs in your Source declarations if possible.

- yoshimi.desktop

Comment 2 Upstream Release Monitoring 2021-01-05 19:18:06 UTC
Latest upstream release: 1.7.4
Current version/release in rawhide: 1.7.3-1.fc34
URL: http://sourceforge.net/projects/yoshimi

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

Comment 3 Upstream Release Monitoring 2021-01-05 19:18:25 UTC
Created attachment 1744693 [details]
[patch] Update to 1.7.4 (#1892705)

Comment 4 Upstream Release Monitoring 2021-01-05 20:14:10 UTC
the-new-hotness/release-monitoring.org's scratch build of yoshimi-1.7.4-1.fc32.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=58996994

Comment 5 Fedora Update System 2021-01-06 21:54:48 UTC
FEDORA-2021-17b9ea721f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-17b9ea721f

Comment 6 Fedora Update System 2021-01-07 01:20:53 UTC
FEDORA-2021-17b9ea721f 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-17b9ea721f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-17b9ea721f

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

Comment 7 Fedora Update System 2021-01-15 01:26:37 UTC
FEDORA-2021-17b9ea721f 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.