Re: Bug#731211: aster: new upstream release, work in progress

2014-03-26 Thread Andrea Palazzi
Il Mercoledì 26 Marzo 2014 10:07, Denis Laxalde ha scritto: Hi, >Andrea Palazzi a écrit : >> So, the package is good, the only thing that should be changed, if we >> want to upload the package as soon as possible, is that with this >> packaging, code-aster-mpi-engine should depend on code-ast

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-26 Thread Denis Laxalde
Hi, Andrea Palazzi a écrit : So, the package is good, the only thing that should be changed, if we want to upload the package as soon as possible, is that with this packaging, code-aster-mpi-engine should depend on code-aster and not vice-versa. I don't understand why we'd want this. With the c

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-26 Thread Andrea Palazzi
Hi, sorry for the late asnwer, I've been busy in these days. So, the package is good, the only thing that should be changed, if we want to upload the package as soon as possible, is that with this packaging, code-aster-mpi-engine should depend on code-aster and not vice-versa.   On the other ha

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-21 Thread Denis Laxalde
Hi, Some other changes and Lintian warnings fixes: - install the elements catalog in /usr/lib/aster as it is architecture dependent. - install the Python library in code-aster binary as it is not tied to the underlying engine. Regards. -- Denis Laxalde Logilab http://www.logilab.fr

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-19 Thread Denis Laxalde
Andrea Palazzi a écrit : I propose to disable it for the moment and focus on getting a working and lintian-clean package; then we can think about what to do with metis and also work to build multiple versions. That seems reasonable. Added two commits for this. Of course, some tests will not pa

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-18 Thread Andrea Palazzi
Hi, I did some testing, and I can't build the packages in any way with libmetis or libparmetis, but if I remove it from the build-deps I can make the packages. I propose to disable it for the moment and focus on getting a working and lintian-clean package; then we can think about what to do wi

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-18 Thread trophime
On Tue, 2014-03-18 at 08:38 +0100, Denis Laxalde wrote: > Hi, > > Andrea Palazzi a écrit : > > - I'd really prefer to remove the libmetis dependency and keep it in > > main and not in contrib; after all libmetis is not absolutely required ( > > the patch no_metis_default.diff was there to change t

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-18 Thread Denis Laxalde
Hi, Andrea Palazzi a écrit : - I'd really prefer to remove the libmetis dependency and keep it in main and not in contrib; after all libmetis is not absolutely required ( the patch no_metis_default.diff was there to change the default renumerator from metis to md ) , and I think that packages in

Re: Bug#731211: aster: new upstream release, work in progress

2014-03-15 Thread Andrea Palazzi
Hi, first of all, thank you for your effort :) I'm writing in the mailing list because the discussion is generic and not regarding the specific issue. I've looked quickly at your packaging; in the next days I'll review it with more attention, anyway here there's some early observations: - I'd