Bug 2422396 - grammalecte-2.3.0 is available
Summary: grammalecte-2.3.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: grammalecte
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohamed El Morabity
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-15 20:34 UTC by Upstream Release Monitoring
Modified: 2026-01-12 01:08 UTC (History)
1 user (show)

Fixed In Version: grammalecte-2.3.0-1.fc43 grammalecte-2.3.0-1.fc42
Clone Of:
Environment:
Last Closed: 2026-01-12 00:55:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 2.3.0 (#2422396) (1.17 KB, patch)
2025-12-15 20:35 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2025-12-15 20:34:37 UTC
Releases retrieved: 2.3.0
Upstream release that is considered latest: 2.3.0
Current version/release in rawhide: 2.2-5.fc44
URL: https://grammalecte.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://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/130209/


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

Comment 1 Upstream Release Monitoring 2025-12-15 20:35:02 UTC
Created attachment 2118845 [details]
Update to 2.3.0 (#2422396)

Comment 2 Upstream Release Monitoring 2025-12-15 20:42:40 UTC
the-new-hotness/release-monitoring.org's scratch build of grammalecte-2.3.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=140059403

Comment 3 Fedora Update System 2026-01-03 00:12:25 UTC
FEDORA-2026-08de050b15 (grammalecte-2.3.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-08de050b15

Comment 4 Fedora Update System 2026-01-03 00:12:25 UTC
FEDORA-2026-c5e5883691 (grammalecte-2.3.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c5e5883691

Comment 5 Fedora Update System 2026-01-04 01:19:24 UTC
FEDORA-2026-08de050b15 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-08de050b15`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-08de050b15

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

Comment 6 Fedora Update System 2026-01-04 01:54:43 UTC
FEDORA-2026-c5e5883691 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-2026-c5e5883691`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c5e5883691

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

Comment 7 Fedora Update System 2026-01-12 00:55:45 UTC
FEDORA-2026-08de050b15 (grammalecte-2.3.0-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-01-12 01:08:39 UTC
FEDORA-2026-c5e5883691 (grammalecte-2.3.0-1.fc42) 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.