Announcing 389 Directory Server 1.2.5 Release Candidate 3

[Rich Megginson]

The 389 team is pleased to announce the availability of Release
Candidate 3 of version 1.2.5.

NOTE: Packages for Enterprise Linux are available from EPEL. We will no 
longer have a separate yum repo for these packagse.

We need your help!  Please help us test this software.  It is a Release
Candidate, so it is fairly stable at this point.  We have worked hard to
make sure upgrades from previous releases are as smooth as possible, and
we would really appreciate feedback about upgrades.  The Fedora system
strongly encourages packages to be in Testing until verified and pushed
to Stable.  If we don't get any feedback while the packages are in
Testing, the packages will remain in limbo, or get pushed to Stable.

The more testing we get, the faster we can release these packages to Stable.

The packages that need testing are:
* 389-ds-base-1.2.5.rc3
* 389-admin-1.1.10.a2

* Release Notes - http://port389.org/wiki/Release_Notes
* Install_Guide - http://port389.org/wiki/Install_Guide
* Download - http://port389.org/wiki/Download

=== New features ===
None - this release is primarily to fix some bugs found in 1.2.5.rc2,

=== Bugs Fixed ===
This release contains a couple of bug fixes.  The complete list of bugs
fixed is found at the link below.  Note that bugs marked as MODIFIED
have been fixed but are still in testing.
* Tracking bug for 1.2.5 release - 
https://bugzilla.redhat.com/showdependencytree.cgi?id=533025&hide_res...
* https://bugzilla.redhat.com/show_bug.cgi?id=548537 548537 Fix memory 
leaks in DNA plugin
* https://bugzilla.redhat.com/show_bug.cgi?id=518084 518084 Fix out of 
order retro changelog entries
* https://bugzilla.redhat.com/show_bug.cgi?id=497556 497556 LDAPI 
connections cause TCP performance degradation

[389-announce] Announcing 389 Directory Server 1.2.5 Release Candidate 3

[Ivanov Andrey (M.)]

Hi,

2009/12/18 Rich Megginson <rmeggins(a)redhat.com&gt;:
>  The 389 team is pleased to announce the availability of Release
>  Candidate 3 of version 1.2.5.
>
>  NOTE: Packages for Enterprise Linux are available from EPEL. We will no
>  longer have a separate yum repo for these packagse.
>
>  The packages that need testing are:
>  * 389-ds-base-1.2.5.rc3
>  * 389-admin-1.1.10.a2 
I still can't find the rpms for "ds rc3" and "admin a2" in EPEL
testing repos  (http://download.fedora.redhat.com/pub/epel/testing/5/x86_64/).
Maybe it will appear tomorrow?

[389-announce] Announcing 389 Directory Server 1.2.5 Release Candidate 3

[Ivanov Andrey (M.)]

2009/12/18 Rich Megginson <rmeggins(a)redhat.com&gt;:
>  The 389 team is pleased to announce the availability of Release
>  Candidate 3 of version 1.2.5.
>
>  NOTE: Packages for Enterprise Linux are available from EPEL. We will no
>  longer have a separate yum repo for these packagse.
>
>  We need your help!  Please help us test this software.  It is a Release
>  Candidate, so it is fairly stable at this point.  We have worked hard to 

It seems that the dn with double quotes is not validated by syntax
validation plug-ins. However this type of DNs is generated by the
default installation from rpms ("Express install" with
setup-ds-admin.pl).

The error log if i launch the syntax validation task on "o=NetscapeRoot" :

/usr/lib64/dirsrv/slapd-ldap-model/syntax-validate.pl -v -D
"cn=Directory Manager" -w '<password>' -b
"o=NetscapeRoot"


[25/Dec/2009:20:07:23 +0100] syntax-plugin - Syntax validate task
starting (base: "o=NetscapeRoot", filter: "(objectclass=*)") ...
[25/Dec/2009:20:07:23 +0100] syntax-plugin - Entry "ou="uid=admin,
ou=Administrators, ou=TopologyManagement,
o=NetscapeRoot",ou=UserPreferences, ou=polytechnique.fr,
o=NetscapeRoot" violates syntax.
entrydn: value #0 invalid per syntax
[25/Dec/2009:20:07:23 +0100] syntax-plugin - Entry
"ou="cn=slapd-ldap-model, cn=389 Directory Server, cn=Server Group,
cn=ldap-model.polytechnique.fr, ou=polytechnique.fr,
o=NetscapeRoot",ou=UserPreferences, ou=polytechnique.fr,
o=NetscapeRoot" violates syntax.
entrydn: value #0 invalid per syntax
[25/Dec/2009:20:07:23 +0100] syntax-plugin - Entry
"ou="cn=admin-serv-ldap-model, cn=389 Administration Server, cn=Server
Group, cn=ldap-model.polytechnique.fr, ou=polytechnique.fr,
o=NetscapeRoot",ou=UserPreferences, ou=polytechnique.fr,
o=NetscapeRoot" violates syntax.
entrydn: value #0 invalid per syntax
[25/Dec/2009:20:07:23 +0100] syntax-plugin - Syntax validate task
complete.  Found 3 invalid entries.


[root@ldap-model ~]# rpm -qa |grep 389
389-adminutil-1.1.8-4.el5
389-ds-base-1.2.5-0.4.rc3.el5
389-admin-1.1.10-0.2.a2.el5

[389-announce] Announcing 389 Directory Server 1.2.5 Release Candidate 3

[Ivanov Andrey (M.)]

The syntax problem applies also to replication agreement entries, just
create one or two replicas and agreements :

/usr/lib64/dirsrv/slapd-ldap-model/syntax-validate.pl -v -D
"cn=Directory Manager" -w '<password>' -b "cn=config"

[29/Dec/2009:12:43:39 +0100] syntax-plugin - Entry "cn=Replication
from a to b,cn=replica,cn="dc=example,dc=com",cn=mapping
tree,cn=config" violates syntax.
nsds5replicaChangesSentSinceStartup: value #0 invalid per syntax
nsds5replicaLastInitStart: value #0 invalid per syntax
nsds5replicaLastInitEnd: value #0 invalid per syntax

nsds5replicaChangesSentSinceStartup has the integer syntax and
contains actually smth like
nsds5replicaChangesSentSinceStartup: 1:9/0

nsds5replicaLastInitStart and nsds5replicaLastInitEnd have
GeneralizedTime syntax and are initiamised to "0". They stay "0" if
there is no complete initilialisation performed from this server and
with this agreement. So it may well always stay 0 in multimaster
configs.


2009/12/25 Andrey Ivanov <andrey.ivanov(a)polytechnique.fr&gt;:
>  2009/12/18 Rich Megginson <rmeggins(a)redhat.com&gt;:
> > The 389 team is pleased to announce the availability of Release
> > Candidate 3 of version 1.2.5.
> >
> > NOTE: Packages for Enterprise Linux are available from EPEL. We will no
> > longer have a separate yum repo for these packagse.
> >
> > We need your help!  Please help us test this software.  It is a Release
> > Candidate, so it is fairly stable at this point.  We have worked hard to
>
>
>  It seems that the dn with double quotes is not validated by syntax
>  validation plug-ins. However this type of DNs is generated by the
>  default installation from rpms ("Express install" with
>  setup-ds-admin.pl).
>
>  The error log if i launch the syntax validation task on "o=NetscapeRoot" :
>
>  /usr/lib64/dirsrv/slapd-ldap-model/syntax-validate.pl -v -D
>  "cn=Directory Manager" -w '<password>' -b
> "o=NetscapeRoot"
>
>
>  [25/Dec/2009:20:07:23 +0100] syntax-plugin - Syntax validate task
>  starting (base: "o=NetscapeRoot", filter: "(objectclass=*)") ...
>  [25/Dec/2009:20:07:23 +0100] syntax-plugin - Entry "ou="uid=admin,
>  ou=Administrators, ou=TopologyManagement,
>  o=NetscapeRoot",ou=UserPreferences, ou=polytechnique.fr,
>  o=NetscapeRoot" violates syntax.
>  entrydn: value #0 invalid per syntax
>  [25/Dec/2009:20:07:23 +0100] syntax-plugin - Entry
>  "ou="cn=slapd-ldap-model, cn=389 Directory Server, cn=Server Group,
>  cn=ldap-model.polytechnique.fr, ou=polytechnique.fr,
>  o=NetscapeRoot",ou=UserPreferences, ou=polytechnique.fr,
>  o=NetscapeRoot" violates syntax.
>  entrydn: value #0 invalid per syntax
>  [25/Dec/2009:20:07:23 +0100] syntax-plugin - Entry
>  "ou="cn=admin-serv-ldap-model, cn=389 Administration Server, cn=Server
>  Group, cn=ldap-model.polytechnique.fr, ou=polytechnique.fr,
>  o=NetscapeRoot",ou=UserPreferences, ou=polytechnique.fr,
>  o=NetscapeRoot" violates syntax.
>  entrydn: value #0 invalid per syntax
>  [25/Dec/2009:20:07:23 +0100] syntax-plugin - Syntax validate task
>  complete.  Found 3 invalid entries.
>
>
>  [root@ldap-model ~]# rpm -qa |grep 389
>  389-adminutil-1.1.8-4.el5
>  389-ds-base-1.2.5-0.4.rc3.el5
>  389-admin-1.1.10-0.2.a2.el5
>

[389-announce] Announcing 389 Directory Server 1.2.5 Release Candidate 3

[Ivanov Andrey (M.)]

> > 2009/12/18 Rich Megginson <rmeggins(a)redhat.com&gt;:
> >> The 389 team is pleased to announce the availability of Release
> >> Candidate 3 of version 1.2.5.
> >>
> >> NOTE: Packages for Enterprise Linux are available from EPEL. We will no
> >> longer have a separate yum repo for these packagse.
> >>
> >> We need your help!  Please help us test this software.  It is a Release
> >> Candidate, so it is fairly stable at this point.  We have worked hard to 
Another small bug is logging during ldapi connection - i've made a
bugzilla entry for this one :
https://bugzilla.redhat.com/show_bug.cgi?id=551198