Re: Inactive packagers to be removed after the F37 release

[Mark Reynolds]

On 11/28/22 1:20 PM, Mattia Verga via devel wrote:

Il 28/11/22 18:36, Nick Bebout ha scritto:

I've removed a lot of ACLs.  See attached log file.



Thanks Nick.

From your output I made a list of the orphaned packages which I think 
it's a bit more readable:


- container/cassandra
- container/php
- modules/389-ds


389-ds would be mine now.

Thanks,
Mark


- modules/timescaledb
- rpms/5minute
- rpms/CBFlib
- rpms/CFR
- rpms/CheMPS2
- rpms/NetworkManager-l2tp
- rpms/PolicyKit-olpc
- rpms/RdRand
- rpms/SFML
- rpms/ServiceReport
- rpms/abiword
- rpms/aboot
- rpms/abrt-java-connector
- rpms/activemq-cpp
- rpms/adwaita-qt
- rpms/aiksaurus
- rpms/airspyhf-1.6.8-1
- rpms/albatross
- rpms/alef-fonts
- rpms/alleyoop
- rpms/alure
- rpms/amor
- rpms/anki
- rpms/anyremote
- rpms/asio
- rpms/asn1c
- rpms/atf
- rpms/autotest-framework
- rpms/axis
- rpms/backup-manager
- rpms/baobab
- rpms/bbkeys
- rpms/bc
- rpms/bdsync
- rpms/bharati-m17n
- rpms/bibtex2html
- rpms/biosdevname
- rpms/blackbox
- rpms/bluebird
- rpms/bonnie++
- rpms/brainfuck
- rpms/brotli
- rpms/buildbot
- rpms/cairo-clock
- rpms/cave9
- rpms/cciss_vol_status
- rpms/celestia
- rpms/chisholm-to-be-continued-fonts
- rpms/clc
- rpms/clipper
- rpms/cmockery2
- rpms/code-editor
- rpms/compton
- rpms/converseen
- rpms/crash
- rpms/csslint
- rpms/ctan-cm-lgc-fonts
- rpms/ctan-kerkis-fonts
- rpms/cups-bjnp
- rpms/curlpp
- rpms/davix
- rpms/debconf
- rpms/debhelper
- rpms/deepin-account-faces
- rpms/deepin-api
- rpms/deepin-calculator
- rpms/deepin-control-center
- rpms/deepin-daemon
- rpms/deepin-desktop-base
- rpms/deepin-desktop-schemas
- rpms/deepin-dock
- rpms/deepin-draw
- rpms/deepin-editor
- rpms/deepin-file-manager
- rpms/deepin-gettext-tools
- rpms/deepin-gir-generator
- rpms/deepin-gtk-theme
- rpms/deepin-icon-theme
- rpms/deepin-image-viewer
- rpms/deepin-launcher
- rpms/deepin-menu
- rpms/deepin-network-utils
- rpms/deepin-picker
- rpms/deepin-polkit-agent
- rpms/deepin-qml-widgets
- rpms/deepin-qt-dbus-factory
- rpms/deepin-qt5integration
- rpms/deepin-screenshot
- rpms/deepin-session-ui
- rpms/deepin-shortcut-viewer
- rpms/deepin-sound-theme
- rpms/deepin-system-monitor
- rpms/deepin-terminal
- rpms/deepin-topbar
- rpms/deepin-wallpapers
- rpms/dmz-cursor-themes
- rpms/docker-compose
- rpms/drupal7-addressfield
- rpms/drupal7-admin_menu
- rpms/drupal7-admin_theme
- rpms/drupal7-block_class
- rpms/dtkcore
- rpms/dtkwidget
- rpms/dtkwm
- rpms/dynafed
- rpms/ebook-tools
- rpms/enchant
- rpms/erlang-epgsql
- rpms/eureka
- rpms/evas-generic-loaders
- rpms/fastback
- rpms/fcitx
- rpms/fcitx-chewing
- rpms/fcitx-cloudpinyin
- rpms/fcitx-configtool
- rpms/fcitx-fbterm
- rpms/fcitx-hangul
- rpms/fcitx-libpinyin
- rpms/fcitx-m17n
- rpms/fcitx-sunpinyin
- rpms/fcitx-table-extra
- rpms/fcitx-table-other
- rpms/fcitx-ui-light
- rpms/fcitx-unikey
- rpms/fedora-dockerfiles
- rpms/fence-agents
- rpms/flumotion
- rpms/fpc
- rpms/fros
- rpms/fusioninventory-agent
- rpms/fwsnort
- rpms/ganyremote
- rpms/gbrainy
- rpms/gdeploy
- rpms/genius
- rpms/geoclue2
- rpms/geocode-glib
- rpms/gfal2
- rpms/gfal2-python
- rpms/gfalFS
- rpms/gl-117
- rpms/glusterfs-selinux
- rpms/gnome-abrt
- rpms/gnome-activity-journal
- rpms/gnome-font-viewer
- rpms/gnome-initial-setup
- rpms/gnome-nds-thumbnailer
- rpms/gnome-passwordsafe
- rpms/gnome-photos
- rpms/gnome-search-tool
- rpms/gnome-settings-daemon
- rpms/gnome-shell-theme-selene
- rpms/golang-deepin-go-lib
- rpms/golang-github-alecthomas-assert
- rpms/golang-github-alecthomas-colour
- rpms/golang-github-alecthomas-repr
- rpms/golang-github-alecthomas-template
- rpms/golang-github-alecthomas-units
- rpms/golang-github-auth0-go-jwt-middleware
- rpms/golang-github-axgle-mahonia
- rpms/golang-github-cheekybits-is
- rpms/golang-github-codegangsta-negroni
- rpms/golang-github-cryptix-wav
- rpms/golang-github-disintegration-imaging
- rpms/golang-github-fogleman-gg
- rpms/golang-github-gocomply-scap
- rpms/golang-github-justinas-alice
- rpms/golang-github-linuxdeepin-dbus-factory
- rpms/golang-github-linuxdeepin-go-x11-client
- rpms/golang-github-lpabon-godbc
- rpms/golang-github-mitchellh-cli
- rpms/golang-github-msteinert-pam
- rpms/golang-github-nfnt-resize
- rpms/golang-github-pkg-browser
- rpms/golang-github-spaolacci-murmur3
- rpms/golie
- rpms/gperf
- rpms/grads
- rpms/gsm-ussd
- rpms/gtk-sharp3
- rpms/hatools
- rpms/heisenbug-kde-theme
- rpms/highcontrast-qt
- rpms/holland
- rpms/hunspell-kn
- rpms/ibus-table-others
- rpms/imwheel
- rpms/indefero
- rpms/intel-cmt-cat
- rpms/intel-ipsec-mb
- rpms/iperf3
- rpms/jama
- rpms/jargs
- rpms/java-mersenne-twister
- rpms/jcodings
- rpms/jdns
- rpms/jffi
- rpms/jgrapht
- rpms/jnr-constants
- rpms/jnr-ffi
- rpms/jnr-netdb
- rpms/jnr-posix
- rpms/jnr-x86asm
- rpms/js-web-socket-js
- rpms/kanyremote
- rpms/kcm-fcitx
- rpms/kcron
- rpms/kde-connect
- rpms/keylime
- rpms/kfaenza-icon-theme
- rpms/kfilefactory
- rpms/kompose
- rpms/kpcli
- rpms/krename
- rpms/krusader
- rpms/ksystemlog
- 

Re: Regular crash of the internal DirectoryServer389 replication

[Mark Reynolds]

On 11/18/22 8:05 AM, Dip Barua wrote:

Hello all,

I hope you are doing well.
I would like to have your help because I have a Replication crash problem on 
389DS.


Is the server crashing, or is replication not working?  There's a big 
difference between the two.


If it's crashing please obtain a stack trace from the core file:

https://www.port389.org/docs/389ds/FAQ/faq.html#sts=Debugging%C2%A0Crashes

If it's just replication not working then we need a lot more 
information.  Access logs, error logs with replication logging enabled, 
and the replication agreements.


Look through your access log and track down what client is opening 
conn=36614.  is this a replica or some other client?


Mark


Here is the below some Frequent Error :


[25/Oct/2022:02:03:15.698645866 +0200] - ERR - slapi_ldap_bind - Could not send bind 
request for id [cn=Directory Manager] authentication mechanism [SIMPLE]: error -1 (Can't 
contact LDAP server), system error -5987 (Invalid function argument.), network error 107 
(Transport endpoint is not connected, host "wam2p.lefoyer.lu:389")

[25/Oct/2022:02:06:27.558971677 +0200] - INFO - NSMMReplicationPlugin - 
bind_and_check_pwp - agmt="cn=lpfroot12" (wam2p:389): Replication bind with 
SIMPLE auth resumed

[25/Oct/2022:07:25:15.490236609 +0200] - ERR - log_ber_too_big_error - 
conn=36614 fd=78 Incoming BER Element may be misformed. This may indicate an 
attempt to use TLS on a plaintext port, IE ldaps://localhost:389. Check your 
client's LDAP_URI settings.

[25/Oct/2022:12:10:07.709047940 +0200] - ERR - NSMMReplicationPlugin - 
repl5_inc_waitfor_async_results  - Timed out waiting for responses: 330754 
330879

Thanks in advance for your help.

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


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

[389-devel] Re: ATTENTION - mass unsubscribe to happen this evening

[Mark Reynolds]

For those of you who wish to stay on this list you will need to 
subscribe yourselves again.  Please wait 24 hours before resubscribing:


https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org/

Thanks


On 8/19/21 2:16 PM, Mark Reynolds wrote:


Hello everyone,

A few months ago there was a SPAM attack on our list and 1800 people 
were incorrectly subscribed to this list.  I think there were only 300 
people on it prior to this happening.  While actions have been taken 
to prevent this from happening again, it doesn't help our current 
situation.  Next week I will be unsubscribing /everyone/.


Those who are interested in remaining on this list will need to 
subscribe again after this mass unsubscribe event.  I will send one 
more email announcement prior to unsubscribing everyone.


Sorry for those who never wanted to be on this list, and sorry to 
those who want to remain on it.


--
Directory Server Development Team


--
Directory Server Development Team

___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] ATTENTION - going to do a mass unsubscribe of this mailing list

[Mark Reynolds]

Hello everyone,

A few months ago there was a SPAM attack on our list and 1800 people 
were incorrectly subscribed to this list.  I think there were only 300 
people on it prior to this happening.  While actions have been taken to 
prevent this from happening again, it doesn't help our current 
situation.  Next week I will be unsubscribing /everyone/.


Those who are interested in remaining on this list will need to 
subscribe again after this mass unsubscribe event.  I will send one more 
email announcement prior to unsubscribing everyone.


Sorry for those who never wanted to be on this list, and sorry to those 
who want to remain on it.


--
Directory Server Development Team

___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4873 - Move EntryUUID Plugin to subpackage

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4873

--
Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Re: stable/dev branches

[Mark Reynolds]

On 8/11/21 9:23 AM, Stanislav Levin wrote:


11.11.2020 22:03, Mark Reynolds пишет:

On 11/3/20 8:50 AM, Stanislav Levin wrote:

03.11.2020 15:58, Mark Reynolds пишет:

On 11/3/20 4:41 AM, Stanislav Levin wrote:

Hello.

Currently, I package 1.4.1 branch as the former-stable for ALTLinux.
But it is not updated since July, too stable?


1.4.x branches in upstream:

    upstream/389-ds-base-1.4.1

This is no longer being maintained

    upstream/389-ds-base-1.4.2

This branch is about to stop being maintained

    upstream/389-ds-base-1.4.3

This would be the "most" stable branch at this time.

    upstream/389-ds-base-1.4.4
    upstream/master

1.4.4 and master (2.0.0) are not "stable" and include more cutting edge
changes and features.

HTH,

Mark

It would be much appreciated such future changes will be announced at
time. I think the other distro-packagers need this information too.

We follow the Fedora release schedule:

https://fedoraproject.org/wiki/Releases?rd=Releases/

So...

F34(rawhide) --> 389-ds-base-2.0.0

F33 --> 389-ds-base-1.4.4

F32 --> 389-ds-base-1.4.3

F31 --> 389-ds-base-1.4.2

Now F31 is probably going to be EOLed sooner than later, so we will stop
maintaining 1.4.2 at that time.


I will add something to the landing page of our wiki about this topic.



Hi! Any news on this?
Could you please point me to which branch is current stable or LTS?


389-ds-base-1.4.3 and 1.4.4 are the most stable, 389-ds-base-2.0 and 
master branch are still under heavy development.


HTH,

Mark



Thanks.


___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


--
Directory Server Development Team

___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Branched master to 389-ds-base-2.0

[Mark Reynolds]

Master branch will now represent the 389-ds-base-2.1.x work.  The 
branched name (389-ds-base-2.0) is shorter than usual, but this is 
because we shortened our versioning string once we started the 2.x 
series.  Please remember to do a "git pull" on your repo to pull in the 
new branch.


Thanks...

--
Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4856 -CLI - Errors from certutil are not propagated

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4856

--
Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4855 - UI - Migrate Replication & Schema tabs to Patternfly 4

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4855

--
Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4834 - Unindexed searches in retro changelog

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4834

--
Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4832 - UI - migrate PF3 Forms for the Server and Database Tabs

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4832

--
Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Reminder: please review: PR 4807 - Repl Plugin name upgrade did not update global dependency plugin list

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4807

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4807 - Repl Plugin name upgrade did not update global dependency plugin list

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4807

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4806 - Fix MEP test case

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4806

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4805 - Fix double free in dbscan

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4805

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4808 - regression: replication name change upgrade code causes crash when dynamic plugins is enabled

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4804

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4795 - Crash when the Referential Integrity log is manually edited

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4795

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4786 - RFE - Allow setting TOD for db compaction and add task

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4784

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4777 - CI - Add tests for DNA interval assignment

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4777

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4774 - UI - migrate plugin tables to PF4 (completes table migration)

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4774

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4749 - Improve SASL logging

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4749

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: UI - make sure dsconf always uses the LDAPI path and not the server ID

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4743

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4739 - UI - Migrate Server, Security, and Schema tables to PF4

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4739

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Reminder: please review: PR 4720 - remove problematic language from source code and config

[Mark Reynolds]

On 4/8/21 3:15 PM, Mark Reynolds wrote:

https://github.com/389ds/389-ds-base/pull/4720


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: Issue 4169 - UI - Migrate Replication tables to PF4

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4722

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4720 - remove problematic language from source code and config

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4720

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4718 - UI - Migrate database tables to Patternfly 4

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4718

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4707 - fix shebang mangling warnings

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4707

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4705 - UI - migrate tables to PF4 (part 1 - monitor tables)

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4705

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Re: Please have look at One-Time Password password policy

[Mark Reynolds]

On 3/24/21 8:32 PM, William Brown wrote:

I think maybe it could be easy to visualise it.


We have time going from past to future like:


past -> future


So we want a window of:

* When can the OTP start to be used?
* When is the OTP no longer able to be used?

So my thinking is:

past -> future
^  ^ ^
|  | |
otp created| |
otp valid from   |
  otp expire at


So I would say otp valid from and the otp expire should be *absolute* date 
times in UTC.


Hi William

Good idea of that graphic. I am sorry to be so slow to understand but still 
things are not clear.
There are the attributes of the password policy and the operational attribute 
of the user account.

I think you meant and I agree with you that operational attributes (in the user 
account) should be absolute date.
What is not clear to me is how to compute those operational attributes from the 
password policy.
I see three options:
• password policy contains absolute time (e.g. passwordOTPValidFromUTC) 
=> account.validFrom = policyValidFromUTC
• password policy contains a delay after OTP create/reset (e.g. 
passwordOTPValidFromDelay) => account.validFrom = Now + policyValidFromDelay
• password policy contains both and if both are set we should give the 
priority to one or the other
If a password policy is a stable entry, then they should not contain absolute 
time. If we imagine password policy created on purpose to do a bunch of 
registration, then that is okay if they contain absolute time.

Do you think we should support password policy with absolute time ?


No we should not store actual times in the config.  These time values need to 
live in the entry itself, just like passwordExpirationtime.  Perhaps this is a 
good candidate to handle through the CLI (maybe even a new task that uses a 
filter, base, etc)?

I'm a bit confused about this answer but:


Theirry thought you wanted to set:


    dn: cn=config
    passwordOTPStartTime: 2021034578489754Z


But I was saying it should be in the entry, not cn=config, like how we 
use passwordExpirationtime:



    uid=mark,dc=example,dc=com
    passwordOTPStartTime: 2021034578489754Z


Mark



I think there are no "operational" attributes here. These should all be 
absolute dates, set on the entry. No calculation or whatever needed.

There is no policy at all. Basicly you just have a mechanic that sets on the 
account that this password is only valid in these time windows, and can only be 
used a maximum number of times.




Mark


—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Re: Please have look at One-Time Password password policy

[Mark Reynolds]

On 3/24/21 6:14 AM, thierry bordaz wrote:



On 3/24/21 12:16 AM, William Brown wrote:

On 24 Mar 2021, at 02:12, thierry bordaz  wrote:

Hi William

Thanks for you review. Some answers are inlined in the mail below.

On 3/23/21 12:33 AM, William Brown wrote:

Hey there,

I think that you also need:


pwdOTPValidFromTime

This way an admin can pre-configure all the OTP's and they only "become valid 
from" that time frame. IE think university enrollment. You can configure all the 
OTP's a month before, and they become valid at a specific datetime.

That is a very nice idea. Note to be OTP the 'userpassword' of the account must 
be reset by an admin and the account inheriting password policy with OTP 
settings.
Assuming 'pwdOTPValidFromTime' is the account operational attribute holding a 
precise time. How should it be computed ? Directly from a precise time set in 
the password policy or computed from a ' 'passwordOTPValidationDelay' (number 
of seconds after OTP reset time) or something else ?

I think maybe it could be easy to visualise it.


We have time going from past to future like:


past -> future


So we want a window of:

* When can the OTP start to be used?
* When is the OTP no longer able to be used?

So my thinking is:

past -> future
^  ^ ^
|  | |
otp created| |
otp valid from   |
  otp expire at


So I would say otp valid from and the otp expire should be *absolute* date 
times in UTC.

Hi William

Good idea of that graphic. I am sorry to be so slow to understand but 
still things are not clear.
There are the attributes of the password policy and the operational 
attribute of the user account.


I think you meant and I agree with you that operational attributes (in 
the user account) should be absolute date.
What is not clear to me is how to compute those operational attributes 
from the password policy.

I see three options:

 1. password policy contains absolute time (e.g.
passwordOTPValidFromUTC) => account.validFrom = policyValidFromUTC
 2. password policy contains a delay after OTP create/reset (e.g.
passwordOTPValidFromDelay) => account.validFrom = Now +
policyValidFromDelay
 3. password policy contains both and if both are set we should give
the priority to one or the other

If a password policy is a stable entry, then they should not contain 
absolute time. If we imagine password policy created on purpose to do 
a bunch of registration, then that is okay if they contain absolute time.


Do you think we should support password policy with absolute time ?

No we should not store actual times in the config.  These time values 
need to live in the entry itself, just like passwordExpirationtime.  
Perhaps this is a good candidate to handle through the CLI (maybe even a 
new task that uses a filter, base, etc)?


Mark



thanks

thierry


And then within that otp valid from - expire at time window, we have the "max 
use" field of how many times it can be used.

Does that help?



I think you should make it consistent with passwordOTPExpDelay to pwdOTPExpDelay. Better, OTP means "one 
time password" so why is it "password one time password". Just make the attributes 
"OTPExpDelay" or whatever. Alternately make it pwdOT (password one time).

ATM password policy ('passwordPolicy') only contains 'password*' attributes 
this is why I would prefer to keep 'passwordOTP*' (e.g. passwordOTPMaxUse, 
passwordOTPExpirationDelay, passwordOTPValidFromTime').
I agree that 'passwordOTP' looks weird ("password one time password") but the 
first 'password' is the way the password policy attribute are prefixed.

Ahh I think I missed that this is using the userPassword and combined with 
passwordPolicy. That makes sense now.

Still better to keep it consistent - all pwd or all password. I think you 
mix/match these 


Then the account operational attributes updated via  password policy. There is 
a mix.
6 out of 10 start with 'password' (like 'passwordExpirationTime')
2 out of 10 start with 'pwd' (like 'pwdReset')
The two remaining are 'retryCountResetTime' and 'accountUnlockTime'.
I choose the 'pwdOTP' prefix because the feature is somehow related to 
'pwdReset' and also I preferred a different prefix than the password policy.

I think passwordOTPExpDelay can be remove if you have ValidFromTime instead.

Why ? Registration should be done after Now+ValidFromTime and before 
Now+passwordOTPExpDelay.
So the two are useful.

I'd see above :)


The OC should be named onetimepasswordPolicy instead.

Do you suggest we have two password policies OC: passwordPolicy and 
OnTimePasswordPolicy.
OTP relying on 'passwordMustChange' then OnTimePasswordPolicy should allow 
'passwordMustChange'

Ignore this comment - I think I missed about the 

[389-devel] please review: PR 4675 - UI - Add PF4 charts for server stats

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4675

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4668 - lib389 - Default path initialization should use dse.ldif if the server is down

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4668

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4664 - CLI - unable to add objectclass/attribute without x-origin

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4664

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4657 - remove problematic language from UI/CLI/CI

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4657

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4655 - UI - migrate modals to PF4

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4655

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Were you unexpectedly subscribed to this list?

[Mark Reynolds]

We've had a very large inflow of subscriptions requests recently, and 
there are concerns something malicious might be going on.  If you are 
getting these emails, but you have not subscribed to this 389-devel 
mailing list please respond to me: mreyno...@redhat.com and I will get 
you removed asap.


Sincerely,

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] Re: failed to build rpms

[Mark Reynolds]

You have to skip the npm audit check "SKIP_AUDIT_CI=1" for now, and the 
rust stuff is a pain and it is hardcoded to be enabled. You always have 
to update and download the latest Rust dependencies:


SKIP_AUDIT_CI=1 make -f rpm.mk update-cargo-dependencies 
download-cargo-dependencies rpms


HTH,

Mark

On 2/23/21 1:40 PM, Ludwig Krispenz wrote:

Hi,

since a long time I was trying to build rpms and failed, here are the 
issues I run into:


1] problem with npm/audit

I followed the suggestions here: 
https://www.port389.org/docs/389ds/contributing.html (pushd/npm 
fix/popd), but this didn't help, only commenting out audit-ci in 
src/cockpit/389-console/node_modules.mk got me over this


2] rust

2.1]

rpm build failed with:

error: failed to get `concread` as a dependency of package `librslapd 
v0.1.0 
(/home/elkris/DEV/gh/two/389-ds-base/rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/src/librslapd)`


Caused by:
  failed to load source for dependency `concread`

Caused by:
  Unable to update registry 
`https://github.com/rust-lang/crates.io-index`


Caused by:
  failed to update replaced source registry 
`https://github.com/rust-lang/crates.io-index`


Caused by:
  failed to read root of directory source: 
/home/elkris/DEV/gh/two/389-ds-base/rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/vendor


Caused by:
  No such file or directory (os error 2)
make[1]: *** [Makefile:12715: 
.../rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/rs/rslapd/release/librslapd.a] 
Error 101



,

It was right that there wasno rs/rslapd/release/librslapd.a file, not 
even the directory rs existed. After configuring --enable-rust the 
directory was created and populated.


Q1: why does it try to pack rust stuff if it is not enabled ?

2.2] Now the directory was there, but I still did get the same error. 
A closer look showed that it was looking for 
.../rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/rs/rslapd/release/librslapd.a 
,but what existed was 
.../rpmbuild/BUILD/389-ds-base-2.0.3.20210223gitbda2c53d0/rs/rslapd/debug/librslapd.a. 
Note "debug" -- "release". configure was run with --enable-debug


Q2: Is there somewhere a hardcoded/default assumpion of "release" ? in 
the cargo spec?


Thanks for any suggestions


Regards,

Ludwig
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4650 - CLI/UI revise DNA plugin management

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4650

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4636 - UI - Migrate Toast Notifications to PF4 Alerts

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4636

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4635 - UI - Migrate CustomCollapse to PF4 ExpandableSection

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4635

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4631 - UI - port monitor charts to PF4 react

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4631

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4617 - Add log message when psearch triggers "max threads per conn" condition

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4617

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4604 - UI - Start migrating PF3 to PF4

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4604

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4566 - Update the doxy file, and fix compiler warnings (x86_64, arm, and s390x)

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4566

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Revised: PR 4543 - Search results are different between RHDS10 and RHDS11

[Mark Reynolds]

Changes made.  I removed a code block from aci__matching function that 
now allows all of this to work correctly.   I do not know if this fix is 
"safe" as I could not really tell what the original code, that I 
removed, was really trying to do (complicated code with no comments).  
But removing it did not cause any regressions in our CI tests, and we 
got the expected behavior everyone was asking for.  Please review...


On 1/13/21 2:05 PM, Mark Reynolds wrote:

https://github.com/389ds/389-ds-base/pull/4543


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4549 - dsconf add validation checks for root DN access control settings

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4549

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4543 - Search results are different between RHDS10 and RHDS11

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4543

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4538 - lib389 healthecheck API throw exception if a backend is not replicated

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4538

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4532 - CI tests - fix test failures

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4532

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: Issue 4414 - crash in disk monitoring from division by zero

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4519

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4508 - Improve csngen testing task

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4508

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4501 - add cockpit options to dsctl

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4501

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4485 - heap-use-after-free in disk monitoring

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4485

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4484 - Remove DES to AES conversion code

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4484

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4482 - Unable to build with Rust-enabled in a closed environment

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4482

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4477 - RFE - LDAPI authentication DN rewritter

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4477

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4453 - Add options to dsctl to create, delete, and display the .dsrc file

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4453

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4450 - Use MONOTONIC clock for all timing events and timed condition vars

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4450

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4433 - After a failed online import the next imports are very slow

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4433

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Re: stable/dev branches

[Mark Reynolds]

On 11/3/20 8:50 AM, Stanislav Levin wrote:


03.11.2020 15:58, Mark Reynolds пишет:

On 11/3/20 4:41 AM, Stanislav Levin wrote:

Hello.

Currently, I package 1.4.1 branch as the former-stable for ALTLinux.
But it is not updated since July, too stable?


1.4.x branches in upstream:

   upstream/389-ds-base-1.4.1

This is no longer being maintained

   upstream/389-ds-base-1.4.2

This branch is about to stop being maintained

   upstream/389-ds-base-1.4.3

This would be the "most" stable branch at this time.

   upstream/389-ds-base-1.4.4
   upstream/master

1.4.4 and master (2.0.0) are not "stable" and include more cutting edge
changes and features.

HTH,

Mark

It would be much appreciated such future changes will be announced at
time. I think the other distro-packagers need this information too.


We follow the Fedora release schedule:

https://fedoraproject.org/wiki/Releases?rd=Releases/

So...

F34(rawhide) --> 389-ds-base-2.0.0

F33 --> 389-ds-base-1.4.4

F32 --> 389-ds-base-1.4.3

F31 --> 389-ds-base-1.4.2

Now F31 is probably going to be EOLed sooner than later, so we will stop 
maintaining 1.4.2 at that time.



I will add something to the landing page of our wiki about this topic.

Regards,
Mark




Thank you very much!


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4431 - Do not normalize escaped spaces in a DN

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4431

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4430 - Fix NULL dereference in cache_revert()

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4430

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Re: stable/dev branches

[Mark Reynolds]

On 11/3/20 4:41 AM, Stanislav Levin wrote:

Hello.

Currently, I package 1.4.1 branch as the former-stable for ALTLinux.
But it is not updated since July, too stable?


1.4.x branches in upstream:

   upstream/389-ds-base-1.4.1

This is no longer being maintained

   upstream/389-ds-base-1.4.2

This branch is about to stop being maintained

   upstream/389-ds-base-1.4.3

This would be the "most" stable branch at this time.

   upstream/389-ds-base-1.4.4
   upstream/master


1.4.4 and master (2.0.0) are not "stable" and include more cutting edge 
changes and features.


HTH,

Mark




Any plans on supporting these?
Which one is stable now?

Thanks.

___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org


--

389 Directory Server Development Team

___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4417 - CL trimming triggering high CPU

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4417

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4416 - lib389 - unable to query schema if there are extra parenthesis

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4416

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: Issue 4262 - remove remaining "perl_enabled" code

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4405

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4402 - more cleanup for Perl/Legacy tool removal

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4402

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4388 - remove Perl legacy tools

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4388

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Re: Mapping tree rework

[Mark Reynolds]

Hi,

So some of the arguments here is that we are introducing risk for 
something that is not really a big problem.  Or, simply not worth 
investing in. From a Red Hat perspective "we" would _never_ fix this, 
it's just not a problem that comes up enough to justify the work and 
time.  But...  The initial work has been done by the upstream community 
(William).  So from a RH perspective we are getting this work for free.  
Personally I don't see this code change as "very" risky, but this is a 
very sensitive area of the code.  That being said, I am not opposed to 
adding it, but...  I think we need much more testing around it to build 
confidence in the patch.  I would want tests that deal with suffixes of 
varying size, names, nested levels/complexity:


    o=my_server.com

    dc=example,dc=com

    dc=abcdef,dc=abc  (same length as suffix above - since the patch 
uses sizing as a way of sorting)


    dc=test,dc=this,dc=patch


I want tests that are adding and removing subsuffixes, and 
sub-subsuffixes, and making sure ldap ops work, and replication, etc.  I 
want tests that use many different suffixes at the same time and many 
subsuffixes - some customers have 50 subsuffixes. Our current CI test 
suite does not have these kinds of tests, and we need them.


As of today I'm not comfortable with the current CI tests to ack this 
patch, but if we can ramp it up and cover more scenarios it would be a 
step in the right direction.  This is all just my humble opinion, we are 
all still just talking :-)


Mark




On 10/19/20 6:47 AM, Pierre Rogier wrote:

Hi William,

Things are not black and white:
   there is a huge difference between a fix with limited impact (like 
adding some check in configuration tools or in the server) and 
redesigning something that is used in many different contexts for 
every request handled by the server ...


In the first case we could easily mitigate the risk by testing and be 
fairly confident, in the second case the tests are too complex to 
achieve the same confidence and we should take this kind of risk only 
if there were a serious benefit to balance it, but in this case, there 
are other solutions with less risks.


I can understand it could seem too conservervative and frustrating but 
that is the price when working on mature projects. If you do not do 
that, the product becomes unstable, and users quickly abandon it.


Regards,
   Pierre


On Mon, Oct 19, 2020 at 1:27 AM William Brown > wrote:




> On 16 Oct 2020, at 17:48, Pierre Rogier mailto:prog...@redhat.com>> wrote:
>
> Hi William,
> I agree with your architecture points and that is why I said my
proposal is a less appealing trade off.
>
> My real concern is your last point:
>  we just do not know and IMHO we are unable to predict what (or
if) config will cause problems, and I am afraid we will only
discover it when people start to complain.
> So I still think that the benefit/risk ratio is bad)
>

I think this wasn't my point. The thing is *any* change will have
that "unknown" risk. Our job is to qualify and identify as many of
those risks as we can, to remove them as unknowns. Think about the
work recently to merge the changelog to the main db, or BDB to
LMDB work, even changing from perl to python for installation.
These are all significantly larger changes, which would be "much
riskier" but all of them have been managed effectively by the team
communicating, coordinating, analysing, designing and testing changes.

So I really don't accept this "unknown" risk argument. I have laid
out a design that explores the configuration, how it works today
and how the values are currently trusted, and a process to manage
and understand this change in a way to minimise the risk. There
are associated tests, and it passes with address sanitiser, and
other test cases for mapping trees, replication and others.

If we just say "unknown risk" at every change we make we'd never
progress. We may as well packup and go home, the project is completed.

So I still stand by my design and the PR I have submitted in this
case, and if there are concerns about esoteric configurations,
then we should identify and understand them too beyond the testing
I have already provided.

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org

To unsubscribe send an email to
389-devel-le...@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:

[389-devel] please review: PR 4378 - suffix management in backends is incorrect

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4378

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Reminder: please review: PR 4331 - import ldif2cl task should not close all changelogs

[Mark Reynolds]

Requested changes made...

On 9/24/20 9:55 PM, Mark Reynolds wrote:

Friendly reminder :-)  I will be out on PTO next week though...

On 9/18/20 4:39 PM, Mark Reynolds wrote:

https://github.com/389ds/389-ds-base/pull/4331


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Reminder about git commit headers

[Mark Reynolds]

Hello,

Seems like everyone is doing something different with the commit 
headers, and I've been wanting to address it. I'd prefer we use "Issue 
" and stop using "Ticket ". Most developers are using "Issue 
###", but some are still using "Ticket", so I always have to tweak this 
when doing upstream builds and writing the release notes.


https://www.port389.org/docs/389ds/contributing.html#getting-the-patch-ready

We silently switched to using "Issue " when we went to Pagure, but 
it was never officially stated.  Moving forward I'd really appreciate it 
if everyone used "Issue  - " as the first line in your 
commits.  Note the hyphen before the issue description.  Also please 
don't use colons, just use "Issue  - My description of this patch".  
It just makes doing upstream releases and wiki updates easier.


Thanks,

Mark

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Reminder: please review: PR 4331 - import ldif2cl task should not close all changelogs

[Mark Reynolds]

Friendly reminder :-)  I will be out on PTO next week though...

On 9/18/20 4:39 PM, Mark Reynolds wrote:

https://github.com/389ds/389-ds-base/pull/4331


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4336 - Add server version information to UI

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4336

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 4331 - import ldif2cl task should not close all changelogs

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4331

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] We've moved to github, make sure you are watching...

[Mark Reynolds]

https://github.com/389ds/389-ds-base/

All developers, and any other interested individuals, should make sure 
to "watch" this repo.  We moved off of Pagure and onto github, but the 
Pagure subscribers were not migrated.  So if you want to keep an eye on 
what's happening make sure to watch this project!


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51258 - remove hardcoded repl changelog filename string

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51258

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51254 - dscreate should use LDAPI to bootstrap the config

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51254

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51252 - RFE - add bootstrap credentials to replication agreements

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51252

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51234 - ds-replcheck crashes in offline mode

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51234

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51221 - Fix regression from last cleanup patch regarding ldbm_back_entry_release()

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51221

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51218 - remove more unused code

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51218

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51217 - remove unused or unnecessary database plugin functions

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51217

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51216 - Fix issues with setting SSL min and max versions (default vs supported versions)

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51216

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51202 - Completely move backend monitors to BDB backend code

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51202

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51199 - Stop importing cockpit's base1/patternfly.css

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51199

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51194 - add more logconv enhancements for the access log time keywords (wtime, optime, etime)

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51194

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51183 - add new access log keywords for wtime and optime

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51183

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please revie: PR 51173 - Log warning if nsslapd-threadnumber is too low or too high

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51173

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51170 - UI - attr uniqueness - selecting empty subtree crashes cockpit

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51170

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51167 - Log internal unindexed searches (notes=A) in errors log

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51167

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] Re: Roadmap for rust as a requirement in the project

[Mark Reynolds]

On 6/11/20 8:15 PM, William Brown wrote:

Hi all,

Background: https://pagure.io/389-ds-base/issue/51140


Ludwig and Mark both raised some good points here. First is that features today 
(EntryUUID, LDAPSsoToken) are both locked behind another language. Rightly so, 
they shouldn't be hidden here forever. As well, Mark wants to ask what it would 
take to enable by default.

** Why did I use the fedse.c to load a plugin entry?

Because we don't (fully) support startup migrations yet. Mark has privately 
reminded me that he has reviewed 
https://pagure.io/389-ds-base/pull-request/49579 and that I should revive it. 
This v4 plugin adds a stateful assertion of entries allowing better migrations 
beyond what fedse.c's bootstrap can achieve. IE we can create an entry if it 
does not exist, and modify it partially if an admin has changed it (ie we can 
tweak defaults but without affecing say pluginEnabled). There was an issue 
viktor raised about pbkdf2 where it could not be disabled, and this would 
resolve it. Most likely, I will break the on startup migrations out from the v4 
plugin patch set, and make it it's own change, and move some of the content 
from fedse.c and friends into this.

** TODO list to get rust enabled by default.

I think there is still a bit of work to do to enable by default, but I think we 
are pretty close. Roughly ordered, this is the list of things that has to 
happen to let us enable rust by default.

- everyone -> test that you can build and run tests with --enable-rust 
--disable-asan in your development environment so that we can work out and issues 
that may exist for us as developers.
I meant to try this again to confirm, but it worked for me a few weeks 
ago on Fedora.  The build took a lot longer :-( but it worked ;-)

- william -> fix the intentional name leak in the rust slapi plugin interface 
to use lazy_static. Today this triggers LSAN which breaks basic test suites.
- william -> clean up libsds linking and some of the related elements
- william -> revive and make on upgrade configs better (see above), potentially 
break it out from the v4 plugin patch.
- william + mark -> check that our respective major distros/releases can build 
with --enable-rust in release rpms
As long as "make -f rpm.mk dist-bz2" does all the cargo building it 
should work fine on Fedora and RHEL.

- william + viktor -> check that we can pass with --enable-rust and 
--enable-asan, especially in CI
- anyone interested -> update wiki contributing guide to include rust as a 
requirement
- (optional) anyone interested (but not william) -> add a section to the wiki 
on using rust in development
- team -> agree we are happy, and make configure.ac have --enable-rust by 
default
- team -> after a few weeks / months, remove the ifdefs, duplicate C versions 
of Rust features, and enable/disable features from configure.ac


Does this seem reasonable to everyone? I really want to make sure we do this 
right as a team, and we are all happy with it (I don't want a repeat of 
nunc-stans ;) ). If we agree on this, I will open some tickets up, add the 
relevant blocks/ordering and assign out the work.


Thanks for getting this discussion started!   I think we already have 
most of this in place to use rust by default today, but we need to do 
some more testing, etc.


Thanks,

Mark



Thank you all!

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org


--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51151 - Set the default minimum worker threads

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51151

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51150 - healthcheck tests for "notes=A" and "notes=F" in the access log

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51150

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: Issue 51144 - dsctl breaks if an instance name contains "slapd-" in the middle of the name

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51145

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51139 - dsctl & dsidm were not returning errors is JSON when JSON CLI arg was requested

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51139

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51133 - Winsync setting winSyncWindowsFilter not working as expected

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51133

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51127 - UI - improve instance creation form validation

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51127

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org

[389-devel] please review: PR 51114 - CLI/UI - Allow using uid for the replication manager entry

[Mark Reynolds]

https://pagure.io/389-ds-base/pull-request/51114

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@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-devel@lists.fedoraproject.org