Re: Salomé packaging
Hi, On Thu, Feb 11, 2010 at 05:32:35PM +0100, Andre Espaze wrote: How to you plan to collaborate on the package building? I would suggest to use the project http://www.python-science.org/project/salome-packaging because I can be efficiently organized on such a platform. Would you like to add a git or mercurial repository on which we will share the package source code? If it is to be hosted on python-science.org, please make it a hg repo and it will be easier for us on the admin side since hg.python-science.org is already operationnal. -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Salomé packaging
Le jeudi 11 février 2010 à 18:54 +0100, Nicolas Chauvat a écrit : Hi, On Thu, Feb 11, 2010 at 05:32:35PM +0100, Andre Espaze wrote: How to you plan to collaborate on the package building? I would suggest to use the project http://www.python-science.org/project/salome-packaging because I can be efficiently organized on such a platform. Would you like to add a git or mercurial repository on which we will share the package source code? If it is to be hosted on python-science.org, please make it a hg repo and it will be easier for us on the admin side since hg.python-science.org is already operationnal. Well, Debian (Science) has hosting capabilities and Debian tools prefers Git or SVN. I also think it would be easier to stick with Debian hosting since we already have accounts, procedures and so on... Sylvestre -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Salomé packaging
Sorry, forgot to mention a couple of things yesterday. First, the package doesn't build in current unstable, because HDF5 transitioned and MED didn't transition with it. I may be able to help with MED to resolve this, but not until next week. (It builds fine in my unstable chroot updated a few days ago, but that machine doesn't have enough disk space to build the whole thing.) On Mon, 2010-01-25 at 11:45 -0500, Adam C Powell IV wrote: Now for one problem. The VISU module doesn't completely compile, because of a symbol/prototype incompatibility within its CONVERTER library. I don't know quite enough C++ to fix this, can someone help? Second, the log with this build failure is in http://lyre.mit.edu/~powell/salome/salome_5.1.3-3_amd64.build - search for *** . The relevant files are VISU_SRC_5.1.3/src/CONVERTOR/VISU_MergeFilterUtilities.cxx and .hxx. I don't understand why TGetFieldData in the prototype with the vtkDataSet* argument works for both TGetPointData and TGetCellData but the one with the VISU::TFieldList* argument doesn't... -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Re: Salomé packaging
Hello again, I now have 10 modules enabled, and have made all but one of the patches upstream-friendly, though I've only uploaded the -3 source package to http://lyre.mit.edu/~powell/salome/ at the moment. Nicolas, can you do me a favor and try to push some of the patches upstream? You can find them in the salome_5.1.3-3.debian.tar.gz file, in the debian/patches directory; I can send them to you individually if you prefer. The patches fall into in several categories, and are separated out by module: * *-safe-include: Eliminate extern C blocks where they are unnecessary -- and even harmful, as they break building with OpenMPI. See the patch head for details. * *-cleanup: Fixes for compiler bugs which break the build with recent compilers. * *-hdf5-needs-mpi: The HDF5 header and library files need MPI in order to work, so this includes the MPI -I and -L flags in with those of HDF5, and puts MPI checks before HDF5 ones. * *-mpich-mpi: Replace MPICH checks with MPI checks, as I've made it compatible with OpenMPI. * *-use-gui-check: Use check_GUI.m4 in the GUI module directory, instead of the rewritten version of that file in several other module directories. * *-build-in-tree: Debian requires that the whole package build first, then install. These patches make this possible. These patches will not only make it easier to maintain the package, but will assist anyone building Salomé on Debian/Ubuntu in the future. And all of them should preserve the ability to build as before, let me know if that is not the case. Other specific patches: * kernel-remove-mpi-undefs: Not sure why these undefs are there, they break OpenMPI compatibility. * kernel-occ-includes: Search for OpenCASCADE header files both in the default location when building OCC from source and also in the Debian/Ubuntu package location. * hxx2solame-destdir: Use DESTDIR for install. * med-scotch: Search for Scotch files both in the default location when building Scotch from source and also in the Debian/Ubuntu package location. * med-missing-libs: Add the MED libraries to the mprint_version link command. * visu-flags-typo: Fix incorrect automake flags variable. * kernel-mpi-libs: This is the one which should *not* go upstream, as it tests for the Debian-specific MPI alternative symlink lib names. Now for one problem. The VISU module doesn't completely compile, because of a symbol/prototype incompatibility within its CONVERTER library. I don't know quite enough C++ to fix this, can someone help? Before upload, I think this needs a few more modules, a full copyright audit, and at least a working GUI shell. I've only done the audit for the first two modules (KERNEL and HXX2SALOME), and haven't tried running the shell yet... Cheers, Adam On Sun, 2010-01-10 at 17:53 -0500, Adam C Powell IV wrote: On Sun, 2010-01-10 at 23:28 +0100, Nicolas Chauvat wrote: Hi, As part of the OpenHPC project[1], Logilab commited itself to package Salomé for Debian. We had seen the great work you have done and are glad that you are resuming it. Wow, thank you for this terrific news! Have you started to forward-port the old patches to a new package, or are you using a different approach? A correction: most of my work on this was two years ago, not three. André Espaze has been developing a connector between Salomé and Code_Aster for the past few months. He is about to continue his work with the packaging of Salomé. He will have the help of Pierre-Yves David. We also have a Debian developer on the team, Alexandre Fayolle, but he will not have a lot of time for this particular project in the upcoming months. Okay. Let me know how I can best fit in with your plans for this project. I am cc'ing every person involved to make sure everyone can get in touch easily. Is debian-science the best place to discuss this topic or should we take the discussion off-list? I think this list is pretty good as long as we are talking about generalities, as I think some of the people on the list will have good suggestions. When we start to get into the details of patches and the package, maybe it will make sense to go off-list. Hopefully, the fact that we have been working with upstream for years will help us get this work done more easily. This is terrific. My patches are Debian-specific, and need some work to make them fit the needs of both upstream and Debian. This gives me hope that doing that work will help to actually get the patches into the upstream source! This is the best news I've heard in a long time. Thanks again, I look forward to working with you. Regards, Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools
Salomé packaging
Greetings, For those interested, I'm re-doing the Salomé .deb I started three years ago. Salomé is a finite element pre-post processing framework, with a lot of other things in there as well. Though some things have improved between version 3.2.6 and 5.1.3, many have not, so although this likely won't take 100+ hours like the last one did, it's taking more effort than I can give to it. I've got five modules configuring, compiling and installing, but will not be able to work on it for the next couple of weeks. rantAmong other things, it needs major updates for modern compilers, for OpenMPI, and for new versions of other packages. It amazes me that upstream can get it to build at all, but then, they seem to only build to certain particular narrow (and old) platforms/targets, and don't accept outside patches (never looked at the 50+ I generated last time), so it is not surprising that this is the result./rant Because I can't do the whole package, I'm putting up the progress I've made thus far at http://lyre.mit.edu/~powell/salome/ for others to work on. The -2 .dsc and .debian.tar.gz files are there, the rest will follow later today. I'm reluctant to put it in git until an audit turns up the non-free and other troublesome files, to avoid having to change the upstream branch and dfsg tarball too many times. (I've only audited the first two modules thus far, which seem dfsg-clean.) Speaking of which, random -legal question: one directory has a .sxw, a .pdf and a .ps. The .pdf and ps files are clearly generated from the sxw. Does a .dfsg tarball have to remove the .pdf and .ps files, and somehow re-generate them from the .sxw, or can it just leave them in? Is there a way to script OO.o to generate a .pdf from a .sxw? Note: the files whose debian/patches/series entries are commented are old patches from 3.2.6 which I haven't backported. They're there to provide some guidance into how to fix problems related to those I fixed back then. The uncommented patches are new, and many of them are ready to go to upstream. A few others need only to be made more general before going upstream, e.g. test for files in dependency packages both where upstream installs them and where Debian installs them, etc. To summarize, I need help with the following: * Copyright audit of the tree * Getting the other modules to configure, compile and install * Making patches upstream-compatible, and sending them to upstream Hopefully in a month or two we'll have both a good Salomé package in Debian, and a more enlightened upstream! -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Re: Salomé packaging
Hi, On Sun, Jan 10, 2010 at 02:29:03PM -0500, Adam C Powell IV wrote: For those interested, I'm re-doing the Salomé .deb I started three years ... Because I can't do the whole package, I'm putting up the progress I've ... To summarize, I need help with the following: * ... * Getting the other modules to configure, compile and install * Making patches upstream-compatible, and sending them to upstream As part of the OpenHPC project[1], Logilab commited itself to package Salomé for Debian. We had seen the great work you have done and are glad that you are resuming it. André Espaze has been developing a connector between Salomé and Code_Aster for the past few months. He is about to continue his work with the packaging of Salomé. He will have the help of Pierre-Yves David. We also have a Debian developer on the team, Alexandre Fayolle, but he will not have a lot of time for this particular project in the upcoming months. I am cc'ing every person involved to make sure everyone can get in touch easily. Is debian-science the best place to discuss this topic or should we take the discussion off-list? Hopefully, the fact that we have been working with upstream for years will help us get this work done more easily. 1: see 2nd project in the list at http://www.teratec.eu/gb/doc/Projets_rd.html Best regards, -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Salomé packaging
On Sun, 2010-01-10 at 23:28 +0100, Nicolas Chauvat wrote: Hi, On Sun, Jan 10, 2010 at 02:29:03PM -0500, Adam C Powell IV wrote: For those interested, I'm re-doing the Salomé .deb I started three years ... Because I can't do the whole package, I'm putting up the progress I've ... To summarize, I need help with the following: * ... * Getting the other modules to configure, compile and install * Making patches upstream-compatible, and sending them to upstream As part of the OpenHPC project[1], Logilab commited itself to package Salomé for Debian. We had seen the great work you have done and are glad that you are resuming it. Wow, thank you for this terrific news! Have you started to forward-port the old patches to a new package, or are you using a different approach? A correction: most of my work on this was two years ago, not three. André Espaze has been developing a connector between Salomé and Code_Aster for the past few months. He is about to continue his work with the packaging of Salomé. He will have the help of Pierre-Yves David. We also have a Debian developer on the team, Alexandre Fayolle, but he will not have a lot of time for this particular project in the upcoming months. Okay. Let me know how I can best fit in with your plans for this project. I am cc'ing every person involved to make sure everyone can get in touch easily. Is debian-science the best place to discuss this topic or should we take the discussion off-list? I think this list is pretty good as long as we are talking about generalities, as I think some of the people on the list will have good suggestions. When we start to get into the details of patches and the package, maybe it will make sense to go off-list. Hopefully, the fact that we have been working with upstream for years will help us get this work done more easily. This is terrific. My patches are Debian-specific, and need some work to make them fit the needs of both upstream and Debian. This gives me hope that doing that work will help to actually get the patches into the upstream source! This is the best news I've heard in a long time. Thanks again, I look forward to working with you. Regards, Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Re: Salomé packaging
Hello, Le dimanche 10 janvier 2010 à 23:28 +0100, Nicolas Chauvat a écrit : Hi, On Sun, Jan 10, 2010 at 02:29:03PM -0500, Adam C Powell IV wrote: For those interested, I'm re-doing the Salomé .deb I started three years ... Because I can't do the whole package, I'm putting up the progress I've ... To summarize, I need help with the following: * ... * Getting the other modules to configure, compile and install * Making patches upstream-compatible, and sending them to upstream As part of the OpenHPC project[1], Logilab commited itself to package Salomé for Debian. We had seen the great work you have done and are glad that you are resuming it. Indeed. Thanks for getting back on this Adam. You can count on me if you need some help. Since we are talking about EDF software, Code Saturne is now available in Debian ;) André Espaze has been developing a connector between Salomé and Code_Aster for the past few months. He is about to continue his work with the packaging of Salomé. He will have the help of Pierre-Yves David. We also have a Debian developer on the team, Alexandre Fayolle, but he will not have a lot of time for this particular project in the upcoming months. I am cc'ing every person involved to make sure everyone can get in touch easily. Is debian-science the best place to discuss this topic or should we take the discussion off-list? I am happy to see that on Debian-Science for now ... but we could switch on Debian Science Maintainers if the conversation starts to be too technical. Hopefully, the fact that we have been working with upstream for years will help us get this work done more easily. I hope so too. It is the main problem of Salome packaging: the lack of interest of upstream for our work. Sylvestre -- Nicolas Chauvat logilab.fr - services en informatique scientifique et gestion de connaissances -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#457075: Status of Salomé packaging
On Thu, 2008-08-21 at 22:28 +0200, Christophe Prud'homme wrote: To follow Ondrej comment, I have been in contact with some people close to the Salome project. With almost the same ones we are going to have a similar project to build a recently funded open platform (OPUS) for uncertainty quantification in simulations possibly based on openturns (in the NEW queue). I will be extra careful that Salome's mess doesn't happen again. I also try at each meeting to bring forth Debian's (Adam's and others) huge efforts to bring Salome to its users. Thank you very much Christophe. It would be terrific to have a cooperative partner in the Salomé upstream developers. I think they share our goal of broadening the use of this amazing project by making it much easier to install and use in Debian and derivative distros, and I look forward to being a part of a future vibrant Salomé user/developer community. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ signature.asc Description: This is a digitally signed message part
Re: Bug#457075: Status of Salomé packaging
To follow Ondrej comment, I have been in contact with some people close to the Salome project. With almost the same ones we are going to have a similar project to build a recently funded open platform (OPUS) for uncertainty quantification in simulations possibly based on openturns (in the NEW queue). I will be extra careful that Salome's mess doesn't happen again. I also try at each meeting to bring forth Debian's (Adam's and others) huge efforts to bring Salome to its users. Best regards C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
