[Date Prev][Date Next]
Re: (ITS#8404) Fix for an assertion failure when olcDbRewrite is modified on a meta or asyncmeta database
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#8404) Fix for an assertion failure when olcDbRewrite is modified on a meta or asyncmeta database
- From: email@example.com
- Date: Tue, 12 Sep 2017 14:25:27 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
A new patch for this issue is uploaded at ftp://ftp.openldap.org/incoming/nadezhda-ivanova-170912.patch
Since asyncmeta no longer uses the rewrite engine, that part of the fix has become irrelevant and is therefore not included.
----- Original Message -----
Sent: Thursday, April 14, 2016 4:28:20 PM
Subject: Re: (ITS#8404) Fix for an assertion failure when olcDbRewrite is modified on a meta or asyncmeta database
*** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
Thanks for your report to the OpenLDAP Issue Tracking System. Your
report has been assigned the tracking number ITS#8404.
One of our support engineers will look at your report in due course.
Note that this may take some time because our support engineers
are volunteers. They only work on OpenLDAP when they have spare
If you need to provide additional information in regards to your
issue report, you may do so by replying to this message. Note that
any mail sent to firstname.lastname@example.org with (ITS#8404)
in the subject will automatically be attached to the issue report.
You may follow the progress of this report by loading the following
URL in a web browser:
Please remember to retain your issue tracking number (ITS#8404)
on any further messages you send to us regarding this report. If
you don't then you'll just waste our time and yours because we
won't be able to properly track the report.
Please note that the Issue Tracking System is not intended to
be used to seek help in the proper use of OpenLDAP Software.
Such requests will be closed.
OpenLDAP Software is user supported.
Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.