On Mon, Aug 16, 2004 at 09:41:07AM +0200, Christian Perrier wrote: > > If the problem is not fixed before the 28th of August freeze date at the > > latest, i will ask for the removal of geneweb from testing so that the ocaml > > 3.08 transition can happen. > > > > > Unfortunately, I just discovered this RC bug before going away for > > > holidays and couldn't even get time for reporting it myself. > > > > Not cool, when will you be back ? > > > > > I have asked for help about it on the debian-ocaml-maint ML as this is > > > a consequence of the recent switch to Ocaml 3.08. I also may need input > > > from Geneweb upstream author. I still need checking if I got some > > > answers while being away. > > > > If all else fail, i can prepare uploads of ocaml-3.07 packages, but i would > > much prefer not to have to do this. What are the dependencies and build > > dependencies of geneweb ? > > > Geneweb does not depend on any ocaml stuff. It only Build-Depends on > it: > > Build-Depends: debhelper (>= 4.1.16), ocaml-best-compilers, ocaml (>= > 3.04), doc-base, dh-buildinfo, iso-codes, po-debconf
Which means it depends on ocaml-base-nox on non-native arches. > Currently, I have two solutions left: > > 1) use a copy of Daniel CVS (he fixed geneweb so that it compiles with > 3.07 and 3.08) Go for it. > 2) backport code changes needed for correct build to stable geneweb > 4.09 > > I tested 1) and it works. I have a CVS snapshot from 20040815 which > builds properly So, case solved, upload this one. > About 2), this needs help from Daniel and he probably prefers > releasing the 4.10 version of Geneweb from his CVS. > > I still have to read possible answers from Daniel but I think that 1) > is the most probable way for solving this. Indeed. I did the same for advi. > Unless I get clues for backporting compiling fixes in the next couple > of days, I will build a package from the CVS snapshot I have. Daniel, > do you confirm that it is ready for release? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
