severity 815485 serious
thanks

Quoting Guillaume Brochu (guillaume.bro...@gmail.com):
> Package: geneweb
> Version: 6.08dfsg-5
> Severity: important
> 
> --- Please enter the report below this line. ---
> 
> Debian 6.x should not be compiled with OCAML >=4.02 (the current OCAML
> version in Stretch and Sid), as it causes problem like this:
> - https://groups.yahoo.com/neo/groups/geneweb/conversations/messages/6557
> - https://groups.yahoo.com/neo/groups/geneweb/conversations/messages/6560
> - http://i63.tinypic.com/2aifuyu.jpg
> Example : " Married%t to [: 26 July 1813, St. Mary, Kingsclere, ] Deborah
> Foster ca 1795-ca 1857 ( "
> 
> Even if release 6.08dfsg-5 seems to have solved the problem compilation with
> OCAML <=4.01 (for gwc2), the binaries distributed in Stretch and Sid are
> currently unusable.
> 
> To my best knowledge, the only upstream geneweb version that can be compiled
> with OCAML>=4.02 is this "fork" of the development code for Geneweb 7.00 :
> https://github.com/geneweb/geneweb
> 
> The geneweb version in Jessie is OK, since it is built using OCAML 4.01.0

Doh. This, and the other issue you reported leads me to think that I
should hand up the maintenance of the geneweb package to somebody
else.

I no longer use geneweb myself, except by having a running instance on
my home server so that my genealogical research stays available to
others even though I stopped it about 15 years ago.

Moreover, I don't follow upstream development closely enough, mostly
starting when I noticed that upstream was going in weird directions
(from my POV), making geneweb 7.x versions nearly impossible to
package for distros (again, from my own POV....that was maybe just
lazyness to understand the changes).

As a consequence, I'm seriously thinking about orphaning geneweb or,
better, hand the maintenance out to someone else.

So, well, if anyone reading this is interested, please get in touch
with me.

Raising the severity of this bug report, by the way: if geneweb is
unusable, it should not enter testing...and if it stays as is, it
should be removed from testing (incredibly sad after 17 years
maitneannce of the package, but c'est la vie).


Attachment: signature.asc
Description: PGP signature

Reply via email to