Thursday, March 26, 2026

[389-users] Re: [Extern] Re: Nested groups

Am 23.03.26 um 15:46 schrieb Viktor Ashirov:
> Hi,
>
> On Mon, Mar 23, 2026 at 2:31 PM Kippels, Julian via 389-users <389-
> users@lists.fedoraproject.org <mailto:389-
> users@lists.fedoraproject.org>> wrote:
>
> Hi,
>
> I would like to have a group be a member of another group. How would I
> go about that?
>
> If you have enabled the memberOf plugin, it should work.
>
>
> Example:
>
> User1, User2 and User3 are members of GroupA.
>
> dn: cn=GroupA,ou=groups,dc=example,dc=com objectClass: top objectClass:
> groupOfNames objectClass: nsMemberOf cn: GroupA member:
> uid=User1,ou=people,dc=example,dc=com member:
> uid=User2,ou=people,dc=example,dc=com member:
> uid=User3,ou=people,dc=example,dc=com
>
> GroupA is a member of GroupB.
> User4 is a member of GroupB.
>
>
> dn: cn=GroupB,ou=groups,dc=example,dc=com objectClass: top objectClass:
> groupOfNames objectClass: nsMemberOf cn: GroupB member:
> cn=GroupA,ou=groups,dc=example,dc=com
> member: uid=User4,ou=people,dc=example,dc=com
>
>
> Searching for all members of GroupB returns Users1 to 4.
>
>
> # ldapsearch -xLLL '(memberOf=cn=GroupB,ou=groups,dc=example,dc=com)' dn
> dn: uid=User1,ou=people,dc=example,dc=com dn:
> uid=User2,ou=people,dc=example,dc=com dn:
> uid=User3,ou=people,dc=example,dc=com dn:
> uid=User4,ou=people,dc=example,dc=com
> dn: cn=GroupA,ou=groups,dc=example,dc=com
>
>
> Thanks
> Julian
> --
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> <mailto:389-users@lists.fedoraproject.org>
> To unsubscribe send an email to 389-users-
> leave@lists.fedoraproject.org <mailto:389-users-
> leave@lists.fedoraproject.org>
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/
> project/code-of-conduct/ <https://docs.fedoraproject.org/en-US/
> project/code-of-conduct/>
> List Guidelines: https://fedoraproject.org/wiki/
> Mailing_list_guidelines <https://fedoraproject.org/wiki/
> Mailing_list_guidelines>
> List Archives: https://lists.fedoraproject.org/archives/list/389-
> users@lists.fedoraproject.org <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 <https://forge.fedoraproject.org/infra/
> tickets/issues/new>
>
>
>
> --
> Viktor

Hi,

Thank you Viktor. Is it possible to mix groupOfNames and
groupOfUniqueNames with this approach?

Julian

Tuesday, March 24, 2026

[Test-Announce] Fedora 44 Branched 20260324.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event
for Fedora 44 Branched 20260324.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:
lorax - 20260314.n.0: lorax-44.4-2.fc44.src, 20260324.n.0: lorax-44.6-1.fc44.src

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

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

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260324.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260324.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260324.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260324.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260324.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_44_Branched_20260324.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

Monday, March 23, 2026

[389-users] Re: Nested groups

Hi,

On Mon, Mar 23, 2026 at 2:31 PM Kippels, Julian via 389-users <389-users@lists.fedoraproject.org> wrote:
Hi,

I would like to have a group be a member of another group. How would I
go about that?
If you have enabled the memberOf plugin, it should work. 

Example:

User1, User2 and User3 are members of GroupA.
dn: cn=GroupA,ou=groups,dc=example,dc=com objectClass: top objectClass: groupOfNames objectClass: nsMemberOf cn: GroupA member: uid=User1,ou=people,dc=example,dc=com member: uid=User2,ou=people,dc=example,dc=com member: uid=User3,ou=people,dc=example,dc=com
GroupA is a member of GroupB.
User4 is a member of GroupB.

dn: cn=GroupB,ou=groups,dc=example,dc=com objectClass: top objectClass: groupOfNames objectClass: nsMemberOf cn: GroupB member: cn=GroupA,ou=groups,dc=example,dc=com 
member: uid=User4,ou=people,dc=example,dc=com 
 

Searching for all members of GroupB returns Users1 to 4.

# ldapsearch -xLLL '(memberOf=cn=GroupB,ou=groups,dc=example,dc=com)' dn dn: uid=User1,ou=people,dc=example,dc=com dn: uid=User2,ou=people,dc=example,dc=com dn: uid=User3,ou=people,dc=example,dc=com dn: uid=User4,ou=people,dc=example,dc=com  
dn: cn=GroupA,ou=groups,dc=example,dc=com 

Thanks
Julian
--
_______________________________________________
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


--
Viktor

[389-users] Nested groups

Hi,

I would like to have a group be a member of another group. How would I
go about that?

Example:

User1, User2 and User3 are members of GroupA.
GroupA is a member of GroupB.
User4 is a member of GroupB.

Searching for all members of GroupB returns Users1 to 4.

Thanks
Julian

[Test-Announce] 2026-03-23 Fedora 44 Blocker Review Meeting

# F44 Blocker Review meeting
# Date: 2026-03-23
# 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 44 blocker review meeting!

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+43+Blocker+review+meeting&iso=20260316T15&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 F44 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

[Test-Announce] Test Days: CoreOS

Greetings testers!

Please join us for upcoming Test Days [1] 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 the CoreOS Edition in Fedora 44.

Test period: 2026-03-23 to 2026-03-27
Test instructions: https://fedoraproject.org/wiki/Test_Day:2026-03-23_CoreOS

Thank you for your contributions!

Kamil Paral
Fedora QA


Sunday, March 22, 2026

Localization workshop @ Prague in June

Dear translators,

I'll do one talk and organize one workshop in Prague in June, related to language community health in Linux ecosystem, and how to improve the situation.
Could you please route the following message to your language communities across the world?

The workshop would greatly benefit to have people with a diversity of experiences/projects/languages.

I created this ticket to track invites: https://forge.fedoraproject.org/localization/tickets/issues/57
I'll send it to some mailing lists, but if you do, could you please share the link with me or in the ticket?
You are welcome to add me in CC of your emails (jibecfed@fedoraproject.org)

Thanks a lot for your help,

---
The Fedora Project community officially invites you and leaders from your localization communities to join us in Prague this June 14th–16th, 2026, for a cross-community workshop on the State of Open Source Localization.

Our l10n community has been processing localization statistics for the entire Linux operating system ecosystem over the last 20 years. The preliminary data reveals some serious challenges regarding the health and velocity of our language communities.

While Flock to Fedora is traditionally our distribution's annual contributor conference, these translation challenges cannot be solved in a silo. We need the shared experience, knowledge, and perspectives of allies from Mozilla, Weblate, LibreOffice, Wikimedia, Localization Lab, and others to truly analyze this data.

Flock 2026 content dedicated on this subject (schedule TBD):
  • An introductory talk presenting the 20-year statistical analysis and its limitations.
  • An extended, collaborative workshop focused on interpreting the data and brainstorming ecosystem-wide improvements.
Your free registration includes conference attendance, meals, evening social events, and access to our negotiated hotel block rates. Please note that we are unable to offer travel sponsorship at this time. You will need to secure your own travel and lodging.

We have 20 years of data to review, and we would love for you to come to Prague and share your experience with us. If you have any questions, you can reach Jean-Baptiste on the Fedora Matrix server in the #l10n:fedoraproject.org channel.

We look forward to hearing from you!

Jean-Baptiste