Bug 2273856 - buku-4.9 is available
Summary: buku-4.9 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: buku
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert-André Mauchin 🐧
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-04-07 13:29 UTC by Upstream Release Monitoring
Modified: 2025-02-03 01:32 UTC (History)
1 user (show)

Fixed In Version: buku-4.9-1.fc41 buku-4.9-1.fc40
Clone Of:
Environment:
Last Closed: 2025-02-03 01:18:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 4.9 (#2273856) (549 bytes, patch)
2024-04-07 13:29 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2024-04-07 13:29:03 UTC
Releases retrieved: 4.9
Upstream release that is considered latest: 4.9
Current version/release in rawhide: 4.8-4.fc40
URL: https://github.com/jarun/Buku

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://docs.fedoraproject.org/en-US/package-maintainers/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/18297/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/buku

Comment 1 Upstream Release Monitoring 2024-04-07 13:29:08 UTC
Created attachment 2025666 [details]
Update to 4.9 (#2273856)

Comment 2 Upstream Release Monitoring 2024-04-07 13:33:34 UTC
the-new-hotness/release-monitoring.org's scratch build of buku-4.9-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=116030586

Comment 3 Fedora Update System 2025-01-25 18:00:07 UTC
FEDORA-2025-e035838041 (buku-4.9-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-e035838041

Comment 4 Fedora Update System 2025-01-25 19:33:33 UTC
FEDORA-2025-df3432c3ee (buku-4.9-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-df3432c3ee

Comment 5 Fedora Update System 2025-01-26 02:26:03 UTC
FEDORA-2025-e035838041 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-e035838041`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-e035838041

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

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

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

Comment 7 Fedora Update System 2025-02-03 01:18:04 UTC
FEDORA-2025-e035838041 (buku-4.9-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-02-03 01:32:40 UTC
FEDORA-2025-df3432c3ee (buku-4.9-1.fc40) has been pushed to the Fedora 40 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.