Bugzilla Bug 182244

In the course of debugging a segmentation fault when accessing any URI
handled by trac when running trac 0.10.4 w/mod_python on apache-2.2.4
w/sqlite 3.3.17 (all ~x86 keyworded) and pysqlite 2.3.1 (x86 keyworded), I
tracked the root cause to the issue described over at
http://www.initd.org/tracker/pysqlite/wiki/2.3.3_Changelog :

- gcc on Linux sucks. It exports all symbols by default in shared
  libraries, so if symbols are not unique it can lead to problems with
  symbol lookup.  pysqlite used to crash under Apache when mod_cache
  was enabled because both modules had the symbol cache_init. I fixed
  this by applying the prefix pysqlite_ almost everywhere. Sigh.

I confirmed that the following worked:

 * using pysqlite-2.3.3 and leaving the default set of modules on in httpd.conf
 * using pysqlite-2.3.1 and commenting out mod_cache.so, mod_disk_cache.so,
mod_file_cache.so and mod_mem_cache.so

At least two of the residents in #gentoo-apache said they run trac w/mod_python
3.3.1 on apache 2.2.4 and one of them, Hollow, kindly provided the
troubleshooting assistance which led me to the above.

To me, the most obvious solution seems to be to stabilize pysqlite 2.3.3 so
that when apache 2.2.4 hits stable and users try out trac + mod_python, they
won't get bitten by this particular issue if they leave the default modules
enabled in httpd.conf to start with.

I hope you agree :)

Reproducible: Always

Steps to Reproduce:
(Will update if necessary)

Actual Results:  
N/A

Expected Results:  
N/A

Thanks to Hollow, kerframil and nerdboy for constructive feedback.

That sounds like a good idea :)

CCing some arch teams: please test and mark stable.

ppc stable

amd64 done, thanks to Nico on IRC

Sparc is stable.

ppc64 stable

omg, all the three arches i'm on are the last!11!!

alpha/ia64/x86 stable, closing.