[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#457075: Salomé packaging



Hi Adam,

> > > > 
> > > > On Tue, 2010-02-23 at 10:05 +0100, Andre Espaze wrote:
> > > > > > 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.
> > > > 
> > > > Great, thanks.  I'm making pretty quick progress (well, as much as can
> > > > be done in one or two builds per day), I think the first upload should
> > > > come fairly soon, within a week or so.
> > > Ok, today I have worked on your revision:
> > > 
> > >     c56f196854092f0dc0d222de71de1a4532f214ec
> > >     Release 5.1.3-4 "Look ma, it builds!"
> > > 
> > > of the master branch or do you have another branch that I could follow?
> > 
> > That's the current public branch now.  I'm working now on my own branch,
> > which doesn't build because of a problem with $(wildcard...) in the
> > rules file which I mentioned on debian-science.  I'm testing a possible
> > solution based on Aaron Ucko's reply, and will push everything to alioth
> > if/when it works.
> 
> Everything works now, so I just pushed a bunch of changes to alioth,
> including the LIGHT and PYLIGHT CORBA-free GUI modules.
Thank you very much for the push, I have succeeded a complete build
at revision:

    5f1c9676ce493cb5f31f01c8a12c4f697308e2fe
    Updated time stamp.
    Fri Feb 26

However I had to set up a virtual machine with 20Go of disk and 1024Mo 
of RAM on a server. I had finally to move away from the chrooted
environment on my local machine. For the installation part, it seems
that there is a cyclic dependency between salome and salome-common.
Obviously salome-common should not depend on salome.

> 
> I'm adding MULTIPR now, which should be the last module (XDATA and YACS
> gave me some trouble, the others have non-free dependencies).  Then I'm
> going to do a .desktop file so it can run from the Applications or KDE
> menu, and when that's done it should be set to upload!
> 
> Oh, except for the HDF5 and MED issue.  Well, when bug 510057 closes,
> then it will be ready to upload.
For that point and also the packaging steps, I have started a draft
of documentation on the mercurial repo:
    http://hg.python-science.org/salome-packaging/
in the file:
    debian-packaging.rst
It is supposed to end up on the debian wiki. In case you have time
to read it, would you have comments? I really feel beginner for the 
Debian packaging process.
Else I have also uploaded the documentation for the modules MED, SMESH
and VISU.

However, I got a runtime error with my version, the study server is 
not found even if I only work with the KERNEL and GUI modules. I am
going to run a new build at revision:

    1a1c81a479c5c021ff685046623831ffc3621ccf
    Wed Mar 3 17:36:30

I saw that you already fixed the 'killSalome' command problem pointing
on python2.4.

Kind regards,

André



Reply to: