RedHat 8.0 RPMS -- what they foretell

[Joe Little]

Yeah.. I know there is a lot to do. I was just relating what I saw in one of my primary tasks (maintain a university's Linux distro). I sincerely hope to dig into builds against 2.1.x and libldap_r. I also noted the issue with OpenLDAP and the problem report, and will await whatever they respond to. I just don't have much code to test OpenLDAP 2.1 or any version against. I need to get sufficient code that will provide bug reports.

As to the mem leaks, I'm at a loss as to how to tackle that one on Python.

On Friday, July 5, 2002, at 10:15 AM, Michael Ströder wrote:

> Joe Little wrote:
>> I'll downloaded the isos for limbo, the first RedHat 8.0 beta release.
>> Its a true .0 release, in that a lot of major changes are in the works. Primarily, they have migrated their whole installation system from python 1.5.x to 2.2.x. Along with this, they have adopted OpenLDAP 2.1.2, and their compat libs are only for OpenLDAP 1.2.13. This means that at least for this vendor, a CVS release of python-ldap will be the bare minimum requirement. My guess is that 8.0 may be an August release, or perhaps later. Regardless, the list will get more questions about OpenLDAP 2.1.x in the future.
>
> Now how about testing the current CVS instead of counting version numbers? Did you read about my problems with OpenLDAP 2.1.x libs? I filed two bug reports to OpenLDAP's ITS related to problems I found when working on python-ldap during the last days.
>
> So far I had no feedback from list members when requesting tests during the last days! :-(
>
> Red Hat is famous for packaging premature software into RPMs such causing a 1st-level support nightmare on mailing lists which they simply don't have to pay (e.g. the gcc catastrophy).
>
> Sorry, Red Hat nor any other Linux distributors' packaging decisions will influence my schedule.
>
> Joe, if you want to push things forward then there are several things to dig into:
>
> 1. Solve problems with NON-ASCII chars in DN when using OpenLDAP 2.1.x libs.
>
> 2. Find huge memory leaks reported to the list.
>
> 3. Dig into thread-safety issues with libldap_r. Despite your personal conversation with Luke I have some doubts that this is really solved.
>
> 4. Test build process with several flavors of OpenLDAP (./configure --help to give you an idea).
>
> 5. Clean up the nightmare of DEFINE's used.
>
> 6. At least test the CVS version!
>
> Not to speak of adding new features...
>
> Ciao, Michael.