Friday, December 20, 2024

[Bug 2324962] Missing Georgian translation for bash

https://bugzilla.redhat.com/show_bug.cgi?id=2324962

Petr Pisar <ppisar@redhat.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Doc Type|--- |If docs needed, set a value
CC| |ppisar@redhat.com
Status|NEW |CLOSED
Last Closed| |2024-12-20 10:22:10



--- Comment #3 from Petr Pisar <ppisar@redhat.com> ---
Latest upstream stable release is 5.2.37
<https://mirror.easyname.at/gnu/bash/>. You need to wait until upstream
releases 5.3 version.


--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2324962

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202324962%23c3

--
_______________________________________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-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/trans@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Monday, December 16, 2024

Sunday, December 15, 2024

Re: Xfce 4.20 for F42/Rawhide?

Thanks a lot for the efforts!

Johannes
--
_______________________________________________
xfce mailing list -- xfce@lists.fedoraproject.org
To unsubscribe send an email to xfce-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/xfce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Re: Xfce 4.20 for F42/Rawhide?

On 11/14/24 20:25, Mukundan Ragavan wrote:
> Thanks for the feedback Neal and Kevin.
>
> I have added the links and sent it to the wrangler.
>
> Mukundan.


FESCO has approved the change and Xfce 4.20 is also released upstream.

I will start building Xfce 4.20 packages in a side tag this coming week
and merge when ready.

Mukundan.

--
_______________________________________________
xfce mailing list -- xfce@lists.fedoraproject.org
To unsubscribe send an email to xfce-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/xfce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce]Fedora 42 Rawhide 20241215.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event
for Fedora 42 Rawhide 20241215.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 - 20241205.n.1: kiwi-10.2.3-1.fc42.src, 20241215.n.0: kiwi-10.2.4-1.fc42.src
python-blivet - 20241205.n.1: python-blivet-3.11.0-5.fc42.src, 20241215.n.0: python-blivet-3.11.0-6.fc42.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/42

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_42_Rawhide_20241215.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_42_Rawhide_20241215.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_42_Rawhide_20241215.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_42_Rawhide_20241215.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_42_Rawhide_20241215.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_42_Rawhide_20241215.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_42_Rawhide_20241215.n.0_Security_Lab

Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/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://pagure.io/fedora-infrastructure/new_issue

Saturday, December 14, 2024

[Test-Announce]2024-12-16 @ 16:00 UTC - Fedora Quality Meeting

# Fedora Quality Assurance Meeting
# Date: 2024-12-16
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location:
https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org

Greetings testers! As proposed last week, let's do the final meeting of
the year on Monday.

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=20241216T16&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 42 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://pagure.io/fedora-infrastructure/new_issue

Wednesday, December 11, 2024

[389-users] Re: Help with 389 Directory Server Replication

I used the iperf program to check for any issues in data traffic between the nodes, but no abnormalities were detected.

I also adjusted the Linux limits parameters according to the tuning and performance recommendations from the 389 documentation.

Additionally, I upgraded the 389 Directory Server from version 2.4.5 to 2.5.2.

However, despite these changes, the same errors persist when starting the replication process.


On Mon, Dec 9, 2024 at 3:47 PM Pierre Rogier <progier@redhat.com> wrote:
so node2 returns a LDAP_BUSY error which is relatively rare (and usually happens just after logging the 
"Retry count exceeded"  error ...) because txn get aborted too often because of db locks conflicts
You can try to tweak the nsslapd-db-deadlock-policy but it is a bit puzzling:
    During a bulk import (i.e importing entries from another supplier), only the import is active on the backend, so     
   there should not be db lock  conflict during an import 
And I do not understand why deleting and recreating the agreements could solve such issues. 
Especially since agreement toward and from the target replica are disabled while the replication is in progress.
 The fact that they exist or not, should not change anything ...
 Unless there is a bug somewhere an a db lock is leaking. But that does not ring any bells in mind mind ...


On Mon, Dec 9, 2024 at 6:37 PM Luiz Quirino via 389-users <389-users@lists.fedoraproject.org> wrote:
Hi, Pierre,

I appreciate your assertive approach to addressing this issue.

I reviewed the logs on node01, which was sending data for replication, and noticed that at the exact moment the error was recorded on node02, node01 logged an LDAP error 51 ("Server is busy").

Given that node01 and node02 are virtual machines on the same network segment, I do not believe this issue is related to the network interface.

This leads me to focus on the minimum resource requirements or internal parameters of the 389 Directory Server as potential causes.

Currently, both nodes are configured with 4 vCPUs and 4 GB of RAM each.

I suspect that some internal parameter in the 389 DS configuration might be contributing to this issue.

Looking forward to your insights.
--
_______________________________________________
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://pagure.io/fedora-infrastructure/new_issue


--
--

389 Directory Server Development Team