Graham Dumpleton wrote .. > Jim Gallacher wrote .. > > WRT to 3.2.9, I've been bogged down with other stuff and will likely > be > > fairly busy this week as well. How be we aim for a release somewhere > > around April 22? I'd like to sort out why the apache 2.2 auth test fails > > on some platforms before the release. It's a defect in the test I'm > > sure, but I don't think we should make a release when failing tests. > > In terms of the list we drew up, what still needs to be done? Has > anything new come up since that we should also consider? > > I can help progress things a bit, although stuff like these logging > additions would prefer someone else to do purely so they get reviewed by > someone else in the process to ensure I didn't stuff up. > > BTW, you don't happen to have a reference to the Apache 2.2 auth test > failures to save me tracking it down in the archive do you. :-)
All I can find from previous 3.3 snapshot testing on Apache 2.2 auth problems was: http://www.mail-archive.com/python-dev@httpd.apache.org/msg01703.html Specifically: [Wed Mar 22 07:16:03 2006] [warn] mod_python (pid=5140,interpreter='test_req_auth_type'): Module directory listed in "sys.path". This may cause problems. Please check code. Code file being imported is "C:\\projets\\mod_python\\test\\htdocs\\tests.py". [Wed Mar 22 07:16:03 2006] [notice] mod_python (pid=5140,interpreter='test_req_auth_type'): Importing module 'C:\\projets\\mod_python\\test\\htdocs\\tests.py' [Wed Mar 22 07:16:03 2006] [crit] [client 127.0.0.1] configuration error: couldn't check access. No groups file?: /tests.py [Wed Mar 22 07:16:03 2006] [error] [client 127.0.0.1] No Authn provider configured Nicolas, what is the latest on this, I couldn't see any followup to say it had been resolved as a configuration issue or otherwise. The "No Authn provider configured" error almost suggests Apache can't load up separate Apache 2.2 auth provider modules and that it is getting itself in a know over that. Graham
