Bug#457075: Salomé packaging
Hi Adam,
>
> Until salome is uploaded into Debian, it will not be possible to use the
> bug tracking system for individual issues. At this point, the only
> "bug" in Debian is that salome isn't there -- #457075. :-)
Ok, so from now I organise tickets on
http://www.python-science.org/project/salome-packaging
and I keep you in touch with my progress.
>
...
>
> > I would like to add such
> > documentation do the salome.git repo, inside the debian directory. I
> > have added the following ticket:
> > http://www.python-science.org/ticket/1403
> > that will certainly move.
>
> Good point. I haven't used the Debian Science Wiki, perhaps that's a
> good place to put such documentation at this point.
Perfect, I will add a page on the wiki as soon as my documentation is
ready. I will restart from a clean sid install today. I plan to document
every module so it will help me to supply the 'debian/rules' patch
of ticket http://www.python-science.org/ticket/1405.
>
> > > You can get and build my latest salome package by the same "git clone"
> > > command but substitute salome for med-fichier. It still needs a lot of
> > > tweaking before it is ready to upload into Debian unstable. And first
> > > the patched HDF5 package needs to go in, along with the new med-fichier.
> > I have succeeded to build salome at revision
> > 181964c525693f410d01646a616e5d94f05c7c9d but I got only KERNEL and GUI
> > running out of the box at the end. I plan to investigate on the GEOM
> > runtime problem first, is it allright for you?
>
> Yes. But please try re-cloning it, I have made a lot of progress, and
> some things might work now that didn't before. I think your tickets
> 1398, 1400 and 1402 are fixed now.
Congratulations, your Release 5.1.3-4 worked fine and closed those three
tickets concerning MED build and install as well as GEOM install. So
now the MED and GEOM modules are present when starting Salome.
>
> My suspicion is that the geom issue might due to incorrect directory
> usage for the OpenCascade data files. I've just added tests for their
> location in check_cas.m4, and will change
> KERNEL/bin/appliskel/env.d/envProducts.sh to use the new CAS_LIBDIR and
> CAS_DATADIR variables accordingly (will need to move it to
> envProducts.sh.in and have configure generate the .sh file).
Unfortunately, I still get the same crash for GEOM with the SIGFPE
Arithmetic exception, forcing me to kill Salome. I plan to investigate
this problem as soon as the documentation is ready.
Thank you very much for your explanations on git-buildpackage and
the Debian build process, they clarified many points. My main problem
in Salome packaging is that the building process is resource intensive
and thus takes lot of time. I sometimes also run out of disk space but
that is really part of the fun.
Best regards,
André
Reply to: