Bug 2344734 - givaro-4.2.1 is available
Summary: givaro-4.2.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: givaro
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Beasley
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-10 19:46 UTC by Upstream Release Monitoring
Modified: 2025-03-15 00:27 UTC (History)
4 users (show)

Fixed In Version: givaro-4.2.1-1.el9 givaro-4.2.1-1.el10_1 givaro-4.2.1-1.el10_0 givaro-4.2.1-1.fc42
Clone Of:
Environment:
Last Closed: 2025-03-02 00:41:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2025-02-10 19:46:35 UTC
Releases retrieved: 4.2.1
Upstream release that is considered latest: 4.2.1
Current version/release in rawhide: 4.2.0-17.fc42
URL: https://casys.gricad-pages.univ-grenoble-alpes.fr/givaro/

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


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

Comment 1 Ben Beasley 2025-02-11 03:11:04 UTC
Waiting for upstream to consider https://github.com/linbox-team/givaro/issues/235.

Comment 2 Fedora Update System 2025-02-21 11:53:07 UTC
FEDORA-2025-4e0c65ee4e (fflas-ffpack-2.5.0-14.fc43, givaro-4.2.1-1.fc43, and 3 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4e0c65ee4e

Comment 3 Fedora Update System 2025-02-21 11:53:30 UTC
FEDORA-2025-adb5d17204 (fflas-ffpack-2.5.0-14.fc42, givaro-4.2.1-1.fc42, and 3 more) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-adb5d17204

Comment 4 Fedora Update System 2025-02-21 12:05:54 UTC
FEDORA-2025-4e0c65ee4e (fflas-ffpack-2.5.0-14.fc43, givaro-4.2.1-1.fc43, and 3 more) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2025-02-21 16:40:45 UTC
FEDORA-EPEL-2025-d7791563a8 (fflas-ffpack-2.5.0-15.el10_1 and givaro-4.2.1-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d7791563a8

Comment 6 Fedora Update System 2025-02-21 16:41:04 UTC
FEDORA-EPEL-2025-47d039c142 (fflas-ffpack-2.5.0-12.el9 and givaro-4.2.1-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-47d039c142

Comment 7 Fedora Update System 2025-02-21 17:48:53 UTC
FEDORA-EPEL-2025-7da06ac9c1 (fflas-ffpack-2.5.0-15.el10_0 and givaro-4.2.1-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7da06ac9c1

Comment 8 Fedora Update System 2025-02-22 00:54:43 UTC
FEDORA-EPEL-2025-47d039c142 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-47d039c142

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

Comment 9 Fedora Update System 2025-02-22 02:38:39 UTC
FEDORA-EPEL-2025-d7791563a8 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d7791563a8

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

Comment 10 Fedora Update System 2025-02-22 03:07:50 UTC
FEDORA-EPEL-2025-7da06ac9c1 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7da06ac9c1

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

Comment 11 Fedora Update System 2025-02-22 03:17:25 UTC
FEDORA-2025-adb5d17204 has been pushed to the Fedora 42 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-adb5d17204`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-adb5d17204

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

Comment 12 Fedora Update System 2025-03-02 00:41:53 UTC
FEDORA-EPEL-2025-47d039c142 (fflas-ffpack-2.5.0-12.el9 and givaro-4.2.1-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2025-03-02 01:51:20 UTC
FEDORA-EPEL-2025-d7791563a8 (fflas-ffpack-2.5.0-15.el10_1 and givaro-4.2.1-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-03-02 02:07:35 UTC
FEDORA-EPEL-2025-7da06ac9c1 (fflas-ffpack-2.5.0-15.el10_0 and givaro-4.2.1-1.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-03-15 00:27:43 UTC
FEDORA-2025-adb5d17204 (fflas-ffpack-2.5.0-14.fc42, givaro-4.2.1-1.fc42, and 3 more) has been pushed to the Fedora 42 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.