Bug 2459757 - ytree-2.12 is available
Summary: ytree-2.12 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ytree
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Filipe Rosset
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-20 14:48 UTC by Upstream Release Monitoring
Modified: 2026-05-05 00:54 UTC (History)
2 users (show)

Fixed In Version: ytree-2.12-1.fc45 ytree-2.12-1.fc43 ytree-2.12-1.fc42 ytree-2.12-1.el10_2 ytree-2.12-1.el10_3 ytree-2.12-1.el10_1 ytree-2.12-1.fc44
Clone Of:
Environment:
Last Closed: 2026-04-24 21:29:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2026-04-20 14:48:05 UTC
Releases retrieved: 2.11
Upstream release that is considered latest: 2.11
Current version/release in rawhide: 2.10-2.fc44
URL: http://www.han.de/~werner/ytree.html

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


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

Comment 1 Upstream Release Monitoring 2026-04-21 09:24:34 UTC
Releases retrieved: 2.12
Upstream release that is considered latest: 2.12
Current version/release in rawhide: 2.10-2.fc44
URL: http://www.han.de/~werner/ytree.html

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


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

Comment 2 Fedora Update System 2026-04-24 20:27:06 UTC
FEDORA-2026-62a21b9ddf (ytree-2.12-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-62a21b9ddf

Comment 3 Fedora Update System 2026-04-24 20:55:26 UTC
FEDORA-2026-bf34666f32 (ytree-2.12-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-bf34666f32

Comment 4 Fedora Update System 2026-04-24 20:55:27 UTC
FEDORA-2026-3120d84ce4 (ytree-2.12-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-3120d84ce4

Comment 5 Fedora Update System 2026-04-24 20:55:27 UTC
FEDORA-EPEL-2026-321deef34d (ytree-2.12-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-321deef34d

Comment 6 Fedora Update System 2026-04-24 20:55:28 UTC
FEDORA-EPEL-2026-52b462f918 (ytree-2.12-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-52b462f918

Comment 7 Fedora Update System 2026-04-24 21:29:57 UTC
FEDORA-2026-62a21b9ddf (ytree-2.12-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-04-25 02:01:08 UTC
FEDORA-EPEL-2026-52b462f918 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-52b462f918

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

Comment 9 Fedora Update System 2026-04-25 02:05:25 UTC
FEDORA-EPEL-2026-321deef34d has been pushed to the Fedora EPEL 10.3 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-321deef34d

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

Comment 10 Fedora Update System 2026-04-25 02:20:29 UTC
FEDORA-EPEL-2026-6fe3f95559 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-2026-6fe3f95559

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

Comment 11 Fedora Update System 2026-04-25 02:30:11 UTC
FEDORA-2026-3120d84ce4 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-3120d84ce4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-3120d84ce4

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

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

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

Comment 13 Fedora Update System 2026-04-27 20:58:30 UTC
FEDORA-2026-d5ce94430d has been pushed to the Fedora 44 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-d5ce94430d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d5ce94430d

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

Comment 14 Fedora Update System 2026-05-03 01:18:26 UTC
FEDORA-2026-3120d84ce4 (ytree-2.12-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 15 Fedora Update System 2026-05-03 01:21:47 UTC
FEDORA-2026-bf34666f32 (ytree-2.12-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2026-05-03 02:24:32 UTC
FEDORA-EPEL-2026-52b462f918 (ytree-2.12-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2026-05-03 02:26:57 UTC
FEDORA-EPEL-2026-321deef34d (ytree-2.12-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2026-05-03 02:38:13 UTC
FEDORA-EPEL-2026-6fe3f95559 (ytree-2.12-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 19 Fedora Update System 2026-05-05 00:54:45 UTC
FEDORA-2026-d5ce94430d (ytree-2.12-1.fc44) has been pushed to the Fedora 44 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.