Fedora Info

[Test-Announce] Test Days: GRUB EFI for confidential computing

2026-10-19T00:35:11.016-07:00

-- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] 2026-10-19 @ 16:00 UTC - Fedora 45 Blocker Review Meeting

2026-10-18T20:57:57.138-07:00

# F45 Blocker Review meeting # Date: 2026-10-19 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 4 proposed blockers and 2 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20261019T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[fedora-arm] 2026-10-19 @ 16:00 UTC - Fedora 45 Blocker Review Meeting

2026-10-18T20:57:39.774-07:00

# F45 Blocker Review meeting # Date: 2026-10-19 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 4 proposed blockers and 2 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20261019T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Candidate RC-1.1 Available Now!

2026-10-17T11:42:28.939-07:00

According to [the schedule][1], Fedora 45 Candidate RC-1.1 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_RC_1.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_RC_1.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_RC_1.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_RC_1.1_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_RC_1.1_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_RC_1.1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_RC_1.1_Security_Lab All RC priority test cases for each of these [test pages][2] must pass in order to meet the [RC Release Criteria][3]. Help is available on [the Fedora Quality chat channel][4], [the Fedora Quality tag on Discourse][5], or on [the test list][6]. Current Blocker and Freeze Exception bugs: https://qa.fedoraproject.org/blockerbugs/current [1]: https://fedorapeople.org/groups/schedule/f-45/f-45-quality-tasks.html [2]: https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3]: https://fedoraproject.org/wiki/Fedora_45_RC_Release_Criteria [4]: https://matrix.to/#/#quality:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org [5]: https://discussion.fedoraproject.org/tags/c/project/7/quality-team [6]: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Branched 20261017.n.0 nightly compose nominated for testing

2026-10-17T02:39:51.973-07:00

Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20261017.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20261009.n.0: anaconda-45.27-2.fc45.src, 20261017.n.0: anaconda-45.29-1.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261017.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261017.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261017.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261017.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261017.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261017.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261017.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] F45 Final NO-GO

2026-10-15T10:51:23.214-07:00

Because no suitable release candidate (rc) was available, we do not have an F45 Final RC. As a result, F45 Final is NO-GO by default. The next Fedora Linux 45 Final Go/No-Go meeting[1] will be held at 1700 UTC on Thursday, 22 October 2026 in #fedora-meeting on Matrix. We will aim for the "current target date #1" milestone of Tuesday, 27 October 2026. The release schedule[2] will be updated accordingly soon. [1] https://calendar.fedoraproject.org/meeting/11450/ [2] https://fedorapeople.org/groups/schedule/f-45/f-45-key-tasks.html -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[fedora-arm] 2026-10-12 @ 16:00 UTC - Fedora 45 Blocker Review Meeting

2026-10-11T16:08:54.597-07:00

# F45 Blocker Review meeting # Date: 2026-10-12 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 4 proposed blockers and 7 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20261012T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora-IoT 45 RC 20261009.0 nightly compose nominated for testing

2026-10-09T04:30:34.710-07:00

Announcing the creation of a new nightly release validation test event for Fedora-IoT 45 RC 20261009.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45iot You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_45_RC_20261009.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_45_RC_20261009.0_General Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Branched 20261009.n.0 nightly compose nominated for testing

2026-10-09T02:33:37.471-07:00

Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20261009.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: kiwi - 20261003.n.0: kiwi-11.0.2-1.fc45.src, 20261009.n.0: kiwi-11.1.1-2.fc45.src lorax - 20261003.n.0: lorax-45.3-1.fc45.src, 20261009.n.0: lorax-45.4-1.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261009.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261009.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261009.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261009.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261009.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261009.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261009.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Test Days: Podman Conmon-v3

2026-10-09T00:13:12.730-07:00

Greetings testers! Please join us for upcoming Test Days and help us improve Fedora's quality and stability. Your participation helps us find and fix bugs before the next release, ensuring a smoother experience for all users. This time we'll focus on testing Podman Conmon-v3. You'll install Fedora from the provided test image and report your test results along with your hardware configuration. Test period: 2026-10-12 to 2026-10-18 Test instructions: https://fedoraproject.org/wiki/Test_Day:2026-10-12_Podman_Conmon-v3 Fedora Magazine: https://fedoramagazine.org/podman-test-week-help-test-the-rust-based-conmon-v3/ Thank you for your contributions! Petr Sklenar Fedora Quality -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[389-users] Re: Questions re: Replication Change Log Management

2026-10-07T09:48:22.845-07:00

On 10/7/26 10:23 AM, Paul Whitney wrote:

Good morning,

I confirmed the old RUVs are now removed from the HUB.

The replication-changelog.db file on the SUPPLIER is now down to a manageable size of 474M. The HUB however is still at 18G in size. I am focusing on one site, There are 8 others that are a part of this topology,

All of the HUBS are in the same state. Will these file eventually reduce in size? Can we expedite it?

Well with BDB you need to wait for database compaction to actually reduce the size of the file. By default it runs every 30 days, but you can adjust this schedule or trigger it via a task:

https://www.port389.org/docs/389ds/design/compact-schedule-design.html

# dsconf slapd-hub backend compact-db --only-changelog

It's possible you might run in a db lock issue so check the error log. IF you do run into then you can bump the db locks, restart the server, and try again:

# dsconf slapd-hub backend config set --locks 1000000 ; dsctl slapd-hub restart ; dsconf slapd-hub backend compact-db --only-changelog

If replication checks come back all green, can we just spike the file and let it recreate on restart?

If you remove the file then that replica (hub) needs to be reinitialized, but its agreements should be ok. So you would only need to reinit that single hub.

Mark

The SUPPLIERS are mixed. Some are still stuck at the larger size changelog and others like above are at ~474M.

Paul M. Whitney E-mail: paul.whitney@mac.com Sent from my browser.
On Oct 6, 2026, at 1:08 PM, Mark Reynolds <mareynol@redhat.com> wrote:
On 10/6/26 12:32 PM, Paul Whitney wrote:

Hi Mark,

I ended up running it on the Supplier using the replica-ids on the hub, that got the list cleaned up. I did run it before I saw this email and did use the --force-cleaning option. Hopefully that doesnt break anything since IDs were not on the supplier, just the hub.

Ok glad it got things cleaned up. Using the force option really means that if it hits a problem it just skips over that replica. Meaning it might NOT clean the rid and proceed to the others. So by "not" using the force option the task will not complete until all replicas are fully cleaned - just an FYI. So lets see how changelog trimming is affected...
Thank you!

Paul M. Whitney E-mail: paul.whitney@mac.com Cell: 410.493.9448 Sent from my browser.
On Oct 6, 2026, at 12:09 PM, Mark Reynolds <mareynol@redhat.com> wrote:
Run it again on a supplier and do not use the force option

On 10/6/26 10:31 AM, Paul Whitney wrote:
Hi Mark,

So I ran the command this morning on the HUB. The error i am getting is:

Failed to clean rid (55224) task cannot be run on a consumer.

Cannot modify task entry, no such object.

Basically, if the supplier isnt providing the change, it wont clear on the hub. Or at least that is how i am understanding it.

Paul M. Whitney E-mail: paul.whitney@mac.com Cell: 410.493.9448 Sent from my browser.
On Oct 5, 2026, at 3:02 PM, Mark Reynolds <mareynol@redhat.com> wrote:
Hi Paul,

Did you run the cleanallruv task on the groupRoot suffix? You need to run it individually on all the replicated suffixes(and sub-suffixes).

Otherwise, the cleanallruv task should have cleaned the hub, but perhaps the force option allowed it to be skipped for some reason. Instead try the command without the force option:

# dsconf slapd-hub repl-tasks cleanallruv --suffix dc=group,dc=root --replica-id <the ID>

Also check the error log on the hub and see if it complained about anything related to the cleanallruv task (grep -i cleanallruv /var/log/dirsrv/slapd_INSTANCE/errors)

Thanks,
Mark

On 10/5/26 2:48 PM, Paul Whitney wrote:
Hi Mark,

This definitely helped. Discovered that there were obsolete RUVs in both my userRoot and groupRoot databases.

I cleaned up the suppliers and they now look clean. However, I am still seeing the old RUVs in the groupRoot database on the hub. Is there a way to clean those out without having to do a reinit?

Paul M. Whitney E-mail: paul.whitney@mac.com Sent from my browser.
On Oct 1, 2026, at 4:02 PM, Mark Reynolds <mareynol@redhat.com> wrote:
Hi Paul,

Another reason the the change log might not be trimmed is if there is a replication agreement that has not sent some of those changes yet. I think it can also happen if there is an obsolete replica in the RUV.

Check the ruv with this command (adjust the suffix of course):

# dsconf slapd-localhost replication get-ruv --suffix dc=example,dc=com

If you see a replica RUV element that is out of place you can remove it using the cleanallruv task

# dsconf slapd-localhost repl-tasks cleanallruv --suffix dc=example,dc=com --replica-id <the ID> --force-cleaning

You can also enable replication error logging and check for trimming events. Trimming is probably still happening, but perhaps it's not a lot of entries:

# dsconf slapd-localhost logging error set level replication

And when you're done you can do:

# dsconf slapd-localhost logging error set level default

HTH,

Mark

On 10/1/26 2:50 PM, Paul Whitney via 389-users wrote:

Good afternoon,

We are running 389-DS version 2.8.0-10. We have a multi-supplier replication agreement in place and each supplier to hub and then to consumers. We have a changelog retention policy of 7 days (the default). Lately we are noticing very large replication-changelog.db files to the tune of about 17-22 GB. The 7-day retention policy doesnt seem to be truncating the size of these files as relication chages are aged off. I have tried setting the max size of the db to 10 GB, but that did not make a difference and then changed the trim-interval setting to every 5 minutes. Still no change in the db file size. Is there a better way to manage this cleanly?

Thank you,

Paul M. Whitney E-mail: paul.whitney@mac.com Sent from my browser.
-- 
Identity Management Development Team
-- 
Identity Management Development Team
-- 
Identity Management Development Team
-- 
Identity Management Development Team

-- 
Identity Management Development Team

-- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 is in final freeze

2026-10-07T01:46:25.408-07:00

Hi all, Today, 2026-10-06, is an important day on the Fedora Linux 45 schedule [1], with significant cut-offs. Today we have the Final Freeze [2], which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted, and packages can move to the 'updates' repository. Pending updates will be pushed before final release as zero-day updates. Regards, Samyak Jain Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-45/f-45-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/f45/final/buglist -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

Intelligent Personal Assistants: How They Work, Help, and Shape Daily Life

2026-10-05T00:38:01.466-07:00

What Is an Intelligent Personal Assistant? An intelligent personal assistant is software that understands spoken or written requests and helps people complete tasks. Common examples include Siri, Google Assistant, Alexa, and AI chat assistants. Users may ask an assistant to set reminders, answer questions, play music, draft messages, or control connected devices. These systems combine technologies such as speech recognition, natural-language processing, machine learning, and information retrieval. Speech recognition converts spoken words into text, while language-processing tools interpret the request and identify its purpose. The assistant then generates a response or performs an action, sometimes using connected apps or online services. Some assistants operate through phones and computers; others are built into speakers, vehicles, and home appliances. Their capabilities vary, and they may require an internet connection. Although they can make everyday interactions faster and more convenient, they do not understand the world exactly as people do. Their responses depend on available data, software design, and the clarity of the request. -- _______________________________________________ wiki mailing list -- wiki@lists.fedoraproject.org To unsubscribe send an email to wiki-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/wiki@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[fedora-arm] 2026-10-05 @ 16:00 UTC - Fedora 45 Blocker Review Meeting

2026-10-04T10:29:33.328-07:00

# F45 Blocker Review meeting # Date: 2026-10-05 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 2 proposed blockers and 2 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20261005T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Branched 20261003.n.0 nightly compose nominated for testing

2026-10-03T02:30:28.911-07:00

Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20261003.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20260927.n.0: anaconda-45.27-1.fc45.src, 20261003.n.0: anaconda-45.27-2.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261003.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261003.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261003.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261003.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261003.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261003.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20261003.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[389-users] Re: Questions re: Replication Change Log Management

2026-10-01T13:02:25.816-07:00

Hi Paul,

Another reason the the change log might not be trimmed is if there is a replication agreement that has not sent some of those changes yet. I think it can also happen if there is an obsolete replica in the RUV.

Check the ruv with this command (adjust the suffix of course):

# dsconf slapd-localhost replication get-ruv --suffix dc=example,dc=com

If you see a replica RUV element that is out of place you can remove it using the cleanallruv task

# dsconf slapd-localhost repl-tasks cleanallruv --suffix dc=example,dc=com --replica-id <the ID> --force-cleaning

You can also enable replication error logging and check for trimming events. Trimming is probably still happening, but perhaps it's not a lot of entries:

# dsconf slapd-localhost logging error set level replication

And when you're done you can do:

# dsconf slapd-localhost logging error set level default

HTH,

Mark

On 10/1/26 2:50 PM, Paul Whitney via 389-users wrote:

Good afternoon,

We are running 389-DS version 2.8.0-10. We have a multi-supplier replication agreement in place and each supplier to hub and then to consumers. We have a changelog retention policy of 7 days (the default). Lately we are noticing very large replication-changelog.db files to the tune of about 17-22 GB. The 7-day retention policy doesnt seem to be truncating the size of these files as relication chages are aged off. I have tried setting the max size of the db to 10 GB, but that did not make a difference and then changed the trim-interval setting to every 5 minutes. Still no change in the db file size. Is there a better way to manage this cleanly?

Thank you,

Paul M. Whitney E-mail: paul.whitney@mac.com Sent from my browser.

-- 
Identity Management Development Team

[389-users] Questions re: Replication Change Log Management

2026-10-01T11:51:04.483-07:00

Good afternoon, We are running 389-DS version 2.8.0-10. We have a multi-supplier replication agreement in place and each supplier to hub and then to consumers. We have a changelog retention policy of 7 days (the default). Lately we are noticing very large replication-changelog.db files to the tune of about 17-22 GB. The 7-day retention policy doesnt seem to be truncating the size of these files as relication chages are aged off. I have tried setting the max size of the db to 10 GB, but that did not make a difference and then changed the trim-interval setting to every 5 minutes. Still no change in the db file size. Is there a better way to manage this cleanly? Thank you, Paul M. Whitney E-mail: paul.whitney@mac.com Sent from my browser.

[Test-Announce] Test Days: Anaconda installer new features in Fedora 45

2026-09-28T09:15:56.660-07:00

Thank you for your contributions!

Kamil Paral (he/him/his)

Fedora Quality

[Test-Announce] 2026-09-28 @ 15:00 UTC - Fedora Quality Meeting

2026-09-27T18:43:03.363-07:00

# Fedora Quality Assurance Meeting # Date: 2026-09-28 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting&iso=20260928T15&p1=1440&ah=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 45 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[fedora-arm] 2026-09-28 @ 16:00 UTC - Fedora 45 Blocker Review Meeting

2026-09-27T18:42:44.019-07:00

# F45 Blocker Review meeting # Date: 2026-09-28 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for a Fedora 45 blocker (and FE) review meeting! We have 4 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+45+Blocker+review+meeting&iso=20260928T16&p1=1440&ah=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F45 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net -- _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Branched 20260927.n.0 nightly compose nominated for testing

2026-09-27T01:46:23.731-07:00

Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20260927.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: python-blivet - 20260924.n.0: python-blivet-3.14.2-1.fc45.src, 20260927.n.0: python-blivet-3.14.2-2.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260927.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 RISC-V (non-official) Beta images are available!

2026-09-25T08:16:53.635-07:00

(Also on Discourse: https://discussion.fedoraproject.org/t/fedora-45-risc-v-non-official-beta-images-are-available/) Hi, folks! The Fedora 45 RISC-V (non-official, community-contributed) *Beta* images are available for testing. You can find the Server, Cloud, and Container artifacts here: https://dl.fedoraproject.org/pub/alt/risc-v/releases/test/45_Beta/ Notes on server images ---------------------- There are two kinds of server images available: • Fedora-Server-Host-Generic: This image uses the standard 7.2 kernel (7.2.7-300.0.riscv64.fc45). This kernel is very close to upstream, and will work on VisionFive 2, Orange Pi RV, Milk-V Mars, and probably other boards. • Fedora-Server-Host-Omni: This image uses the Fedora "Omni" kernel, (7.2.7-300.0.riscv64.omni.fc45). The "Omni" aims to work on a wider range of RISC-V boards. Some patches in this kernel are still under review upstream. For details on the list of boards the Omni kernel should work on, refer to the overview[1] of Omni kernel. Please take these images for a spin[2] and let us know if you hit any issues. Most of the active discussion is on the Fedora RISC-V Matrix channel[2]. Regards, Fedora RISC-V Community (but any errors are mine) [1] https://copr.fedorainfracloud.org/coprs/g/forge-riscv-members/riscv64_omni_kernel/ [2] https://fedoraproject.org/wiki/Architectures/RISC-V/QEMU [3] https://chat.fedoraproject.org/#/room/#riscv:fedoraproject.org PS: Usually we send these out just to Fedora Discourse, trying to include the lists as well from this release :-) -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora-IoT 45 RC 20260924.0 nightly compose nominated for testing

2026-09-24T04:29:13.680-07:00

Announcing the creation of a new nightly release validation test event for Fedora-IoT 45 RC 20260924.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45iot You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_45_RC_20260924.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_45_RC_20260924.0_General Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Branched 20260924.n.0 nightly compose nominated for testing

2026-09-24T02:42:09.344-07:00

Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20260924.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: anaconda - 20260921.n.0: anaconda-45.22-1.fc45.src, 20260924.n.0: anaconda-45.27-1.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260924.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260924.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260924.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260924.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260924.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260924.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260924.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[Test-Announce] Fedora 45 Branched 20260921.n.0 nightly compose nominated for testing

2026-09-21T02:04:02.037-07:00

Announcing the creation of a new nightly release validation test event for Fedora 45 Branched 20260921.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: kiwi - 20260918.n.0: kiwi-10.3.11-1.fc45.src, 20260921.n.0: kiwi-11.0.2-1.fc45.src parted - 20260918.n.0: parted-3.7-4.fc45.src, 20260921.n.0: parted-3.7.13-1.fc45.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260921.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260921.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260921.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260921.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260921.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260921.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_45_Branched_20260921.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new