Dear Gustaf and all,
I'm no longer using OpenACS at work, but I still maintain both openacs and dotlrn debian packages in my spare time, and your post hurted my feelings :)
Not responsible for the aolserver packages though, but i guess their maintainer reads this forum.
With that said, let see all the issues in detail:
- PG 9.1: The openacs package (5.7.0) is currently using "standard_conforming_strings = off" as a compatibility option in the openacs database to avoid the errors. It seemed to work fine, and I asked if there was any other change to do in the OCT list. I was told that using a more recent version of nspostgres would make the "standard_conforming_strings = off" unnecesary. IIRC, the nspostgres maintainer was asked about updating it (i think it was Stefan who asked him to), but, as it was never updated, i kept that option hoping it would be enough.
- Changes in head to support newer aolserver: I could include a patch in the package that modifies the openacs tarball and fix this but, at this point, i think the best solution is to package a new version of openacs (5.8) with proper pg9.x and aolserver compatibility.
Is there any estimation of when 5.8 will be *officially* out, with its static tarball in the download page? If the release is no near though, i'll go with the patch, but i think this is a way better solution.
However, we'll have to deal with the nspostgres issues. I'll try to contact its maintainer to see if he's willing to update it.
P.S: not the place to say it, but dotlrn packages has those and worse problems too. 2.5.0 is extremely old and, if no release is made soon, i fear for its continuity in the debian archive.
Kind regards,
Héctor Romojaro