Bug#731211: aster: new upstream release, work in progress
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 hand, I think that the packaging scheme should stay as it was previously: the code-aster package was originally meant to be a meta-package, just to allow to easlily install the whole thing with apt-get install code-aster; I think we should still follow this concept. So, move all arch-independent files (mostly python) in another package, like code-aster-common; move the elements file and other arch-dependant files common to the serial and parallel version to another package code-aster-elements, and leave the code-aster package as a metapackage. Suggestions on better package scheme ( and naming ) naming are welcome :) Other issues/enhancements/wishes: - the code-aster package creates both /usr/lib/aster an /usr/lib/codeaster; the latter seems to be used just for a symlink from ../../share/aster . It's just a leftover of the old packaging, or CA looks for files in this path? Note however that code-aster-run puts some files under /usr/lib/codeaster, so we shoult ideally take also care of code-aster-run and code-aster-gui packages. - In the process, I'd like also to switch from svn to git. - as_run doesn't work out of the box: it relies on having informations about available versions in the file /etc/codeaster/aster ; the script update-codeaster-engines takes care of this, it should be run on postinst/postrm scripts of the code-aster-*-engine packages. - provide also the serial version - a simple script to run the test cases would be nice... the .comm file that was used for this purpose has been removed from upstream, or it's just me that can't find it? - we should fix libmetis in one way or another, either by adapting the sources to libmetis 5.1.0 (the metis documentation says something about this process) or by changing the default renumerator from METIS to something other, like MD, so that it can be compatible with comm files that doesn't specify the renumerator to be used. - 11.5 is already out - and I'd like to provide also testing/unstable versions So, considering that the actual packages are empty, I propose to fix the dependency and upload the packages, then start working on enhancong the package. Bye Andrea Il Venerdì 21 Marzo 2014 10:09, Denis Laxalde denis.laxa...@logilab.fr ha scritto: 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 -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532bfd49.8040...@logilab.fr -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#731211: aster: new upstream release, work in progress
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 current binary layout, code-aster (the Python library and elements catalog) cannot be used without an engine (the aster binary), whereas the engine could (in theory) be used without the code-aster Python library or elements catalog (although it wouldn't be more useful than a python interpreter). On the other hand, I think that the packaging scheme should stay as it was previously: the code-aster package was originally meant to be a meta-package, just to allow to easlily install the whole thing with apt-get install code-aster; I think we should still follow this concept. Even if it's not a meta package anymore, the code-aster binary package still provides this feature. So, move all arch-independent files (mostly python) in another package, like code-aster-common; move the elements file and other arch-dependant files common to the serial and parallel version to another package code-aster-elements, and leave the code-aster package as a metapackage. Suggestions on better package scheme ( and naming ) naming are welcome :) I think this is over-design. Let's keep it simple, unless there's a real need to have something more complicated. Other issues/enhancements/wishes: - the code-aster package creates both /usr/lib/aster an /usr/lib/codeaster; the latter seems to be used just for a symlink from ../../share/aster . It's just a leftover of the old packaging, or CA looks for files in this path? Note however that code-aster-run puts some files under /usr/lib/codeaster, so we shoult ideally take also care of code-aster-run and code-aster-gui packages. This symlink is precisely here so that as_run (from code-aster-run package) can still be used when aster is installed in /usr/lib/aster (not /usr/lib/codeaster). Ultimately, astk's packaging should be updated in order not to need this, but I currently I no time to do this. - In the process, I'd like also to switch from svn to git. Not sure I get your point. It's already done. - as_run doesn't work out of the box: it relies on having informations about available versions in the file /etc/codeaster/aster ; the script update-codeaster-engines takes care of this, it should be run on postinst/postrm scripts of the code-aster-*-engine packages. What does not work? AFAICT, it works: I can run 'as_run xxx.export' or some tests like 'as_run --test mtlp100a'. - provide also the serial version - a simple script to run the test cases would be nice... the .comm file that was used for this purpose has been removed from upstream, or it's just me that can't find it? - we should fix libmetis in one way or another, either by adapting the sources to libmetis 5.1.0 (the metis documentation says something about this process) or by changing the default renumerator from METIS to something other, like MD, so that it can be compatible with comm files that doesn't specify the renumerator to be used. The tree latter points would be nice, indeed. - 11.5 is already out And I updated the packaging for this version already. - and I'd like to provide also testing/unstable versions Again, let's keep it simple first. Regards, Denis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: Trilinos packages
i suspect that the clean way would be (binary) packages for each library the trilinos source package contains. I fully agree. Trilinos is structurally similar to Boost which does provide a sophisticated install structure. Unfortunately, the Trilinos build system is flawed in certain places that make it difficult to take an automated approach to that. One example is that the interdependencies of the subpackages aren't presented in a machine-readable form. Although, I'm submitting patches to Trilinos to address these issues, I would suggest to first go with a monolithic package and split it up at a later point. In the course of packaging Trilinos for Debian, I have identified quite a number of bugs in Trilinos for which I maintain a little zoo of patches, https://github.com/nschloe/trilinos-ubuntu/tree/master/patches. Some of those have already made it upstream, and we'll have to see if we can get in more of those before the next release freeze. I'll keep you all posted. Cheers, Nico On Tue, Mar 18, 2014 at 12:56 PM, Felix Salfelder fe...@salfelder.org wrote: On Tue, Mar 18, 2014 at 12:15:49PM +0100, Nico Schlömer wrote: A quick poll on the Trilinos package naming: Right now, we have libtrilinos, which triggers a package-name-doesnt-match-sonames warning since none of the Trilinos libraries is called libtrilinos.* (rather libepetra.*, libbelos.*, ...). This is similar to the libboost package which doesn't contain a library by the name libboost.* either. i suspect that the clean way would be (binary) packages for each library the trilinos source package contains. and maybe have a trilinos-dev metapackage that depends on all the lib*-dev packages. this will add up to some copy and paste work, and end up with a lot of packages... i don't know if it's worth the effort. fwiw, theres another source package that creates a heap of libraries. it is the old trilinos package [1]. here, all sonames are prefixed by libtrilinos_. looks like an alternative... On the other hand, a software very similar to Trilinos, PETSc, goes by the Debian name petsc. i cannot find a (binary) package called petsc. but there is (e.g.) libpetsc3.4.2, and it contains libpetsc.so.4.3.2. unkike trilinos, the petsc source package creates just one shared library. and afaics its soname matches the package name. hth felix [1] https://packages.debian.org/squeeze/amd64/libtrilinos/filelist -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Le devis énergétique de votre maison effectué sans frais par nos experts
Vous recevez cet email car vous êtes inscrit à la base M.E.S. Si le message ci-dessous ne s'affiche pas correctement, vous pouvez consulter la version en ligne. [http://s1.emailing-factory.fr/static/n/njBMlmvOEsSIxlEDGMBTWvkn/c/xlsd66a225fca6e484ca46dca58db] [http://s1.emailing-factory.fr/stats/tracker/t/tsxpleQb0gIj1RHGGsPc1wjD/c/xlsd66a225fca6e484ca46dca58db] [http://s1.emailing-factory.fr/stats/tracker/t/tsxpleQb0gIj1RHGGsPc1wjD/c/xlsd66a225fca6e484ca46dca58db] [http://s1.emailing-factory.fr/stats/tracker/t/tsxpleQb0gIj1RHGGsPc1wjD/c/xlsd66a225fca6e484ca46dca58db] Une estimation claire du rendement de votre toit en fonction de : Votre zone géographique L'orientation et la pente de votre toit La surface et la puissance de vos panneaux En application de la loi «Informatique et Liberté», vous disposez d'un droit d'accès, de rectification et d'opposition sur les données vous concernant. Si vous souhaitez accéder à vos données personnelles, les rectifier ou ne plus recevoir de propositions commerciales par l'intermédiaire de M.E.S [http://s1.emailing-factory.fr/stats/tracker/t/t7pmdPhSLCsWKJFUnfyiKDSE/c/xlsd66a225fca6e484ca46dca58db] , il vous suffit de le signaler à M.E.S., 116 Rue de Charenton 75012 PARIS ou sur cette page [http://s1.emailing-factory.fr/fr/campaign/unsubscribe/ct/xlsd66a225fca6e484ca46dca58db/n/njBMlmvOEsSIxlEDGMBTWvkn] . [http://s1.emailing-factory.fr/fr/campaign/unsubscribe/ct/xlsd66a225fca6e484ca46dca58db/n/njBMlmvOEsSIxlEDGMBTWvkn]-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of glpk_4.53-2_amd64.changes
glpk_4.53-2_amd64.changes uploaded successfully to localhost along with the files: glpk_4.53-2.dsc glpk_4.53-2.debian.tar.xz glpk-doc_4.53-2_all.deb libglpk36_4.53-2_amd64.deb libglpk36-dbg_4.53-2_amd64.deb libglpk-dev_4.53-2_amd64.deb glpk-utils_4.53-2_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#741303: libfeel++1: libfeelpp.so.1.0.0 links with both GPL-licensed and GPL-incompatible libraries
Dear Francesco Poli
What is the state of this bug ? any progress with respect to scotch
licensing ?
this is a really painful situation !
are petsc and all libraries (based on umfpack) related to this bug issues
marked for removal from testing ?
have you marked also octave with an RC bug ? it uses suitesparse/umfpack
and scotch [1]
Basically all libraries/programs using suitesparse/umfpack should have this
bug, no ?
I think Libreoffice/Openoffice are using suitesparse(and scotch) and glpk
so it should also have the RC bug.
I guess that the technical solution would be to get rid of umfpack but then
that would disrupt a lot of software !
1. http://packages.qa.debian.org/o/octave.html
Best regards
C.
On Tue, Mar 11, 2014 at 12:05 AM, Francesco Poli (wintermute)
invernom...@paranoici.org wrote:
Package: libfeel++1
Version: 1:0.95.0-final-2
Severity: serious
Justification: Policy 2.3
User: debian-science-maintainers@lists.alioth.debian.org
Usertags: scotch-license-issues
Hello,
the library /usr/lib/libfeelpp.so.1.0.0 links with:
= libumfpack.so.5.6.2, which is under the GNU GPL v2 or later
= libcholmod.so.2.1.2, which has parts under the GNU GPL v2 or later
= libptscotch-5.1.so and libptscotcherr-5.1.so, which are released
under the GPL-incompatible terms of the CeCILL-C v1.0 license
= libpetsc.so.3.4.2 and libslepc.so.3.4.2, which, though not being
under strong copyleft or under copyleft at all, link, in their
turn, with the above three libraries...
= libglpk.so.36, which is under the GNU GPL v3 or later
= libgmsh.so.2, which is under the GNU GPL v2 or later (with some
exceptions, but not regarding SCOTCH or CeCILL-C)
This seems to mean that package libfeel++1 includes a file which
links with both GPL-licensed and GPL-incompatible libraries.
Please refer to the similar bug #740463 for some further details about
the SCOTCH licensing issues.
I have also noticed that package feel++-apps includes several files
which link with the above mentioned combination of libraries.
I think the possible solutions to the issue for feel++ are, in
descending order of desirability:
(A) SCOTCH copyright holders should be contacted and persuaded to
re-license (or dual-license) it under GPLv2-or-later-compatible terms
(B) SCOTCH should be substituted with a GPLv2-or-later-compatible
replacement, if any is available (METIS seems to be at least
GPLv3-or-later-compatible, see https://bugs.debian.org/740463#15 )
(C) GPL-licensed library (such as UMFPACK and CHOLMOD, GLPK, Gmsh)
copyright holders should be asked to relax the copyleft (for instance
by switching to the LGPL v2.1) or add license exceptions that give
permission to link their works with code released under CeCILL-C v1.0
As said in other bug reports, the best solution is (A):
I am thus renewing my call for help to push in the direction of
{re|dual}-licensing SCOTCH under the GNU LGPL v2.1:
please see https://bugs.debian.org/740463#5 for the full story.
Thanks for your time!
To unsubscribe from this group and stop receiving emails from it, send an
email to feelpp-devel+unsubscr...@feelpp.org.
--
Professor in Scientific Computing
IRMA, CeMoSiS, AMIES
IRMA: http://www-irma.u-strasbg.fr/~prudhomm
CeMoSis: http://www.cemosis.fr
AMIES: http://www.agence-maths-entreprises.fr/
Téléphone : 03 68 85 0089 - Bureau : P-210
Mobile: 06 87 64 60 51
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Processing of aster_11.5.0+dfsg2-1_amd64.changes
aster_11.5.0+dfsg2-1_amd64.changes uploaded successfully to localhost along with the files: aster_11.5.0+dfsg2-1.dsc aster_11.5.0+dfsg2.orig.tar.gz aster_11.5.0+dfsg2-1.debian.tar.xz code-aster_11.5.0+dfsg2-1_amd64.deb code-aster-mpi-engine_11.5.0+dfsg2-1_amd64.deb code-aster-test_11.5.0+dfsg2-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Alioth /git/debian-science/packages directory
Hi, I'm thinking to package another piece of software under about robotics. When I have login to alioth and chdir to /git/debian-science/packages I have realised that: $ ls -1 | grep .git | wc -l 425 so, we have 425 folders containing 425 git repos. I thought that the packages from robotics blend could go to a folder (for instance robotics). So, my question is what do you think if we are moving the git repo to a folder with the name of the blend, or something that classify it? It's just an idea... also for the robotics packages. It implies to create another version of the package with the vcs field updated. Regards, Leopold -- -- Linux User 152692 Catalonia signature.asc Description: This is a digitally signed message part. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
aster_11.5.0+dfsg2-1_amd64.changes ACCEPTED into unstable
Mapping sid to unstable.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 26 Mar 2014 16:03:58 +0100
Source: aster
Binary: code-aster code-aster-mpi-engine code-aster-test
Architecture: source amd64 all
Version: 11.5.0+dfsg2-1
Distribution: sid
Urgency: low
Maintainer: Debian Science Team
debian-science-maintainers@lists.alioth.debian.org
Changed-By: Denis Laxalde denis.laxa...@logilab.fr
Description:
code-aster - Code_Aster finite element program - metapackage
code-aster-mpi-engine - Code_Aster finite element program - parallel binary
code-aster-test - Code_Aster finite element program - test files and examples
Closes: 670842 703415 707940 713083 731211 740091
Changes:
aster (11.5.0+dfsg2-1) unstable; urgency=low
.
* New upstream release (Closes: #731211):
- drop all previous patches that don't apply anymore;
- add new ones to fix the build system configuration;
- (most) test cases run fine (Closes: #670842);
.
* debian/control:
- set myself as uploader;
- adjust build dependencies:
+ code-aster-{run,gui} not needed,
+ use petsc-dev instead of libpetsc3.2-dev (Closes: #740091)
.
* debian/rules:
- rewrite from scratch in order to account for the change of build system,
upstream (waf is used now);
- use dh_python2 instead of python-support;
- only build the MPI version;
.
* Adjust .install files (Closes: #713083)
* Drop .postrm/.postinst files (Closes: #703415, #707940)
.
* Unpack Waf binary, hence the +dfsg.
Checksums-Sha1:
4d892337a27f7a29d9312fa1a253cb3c235d9563 2505 aster_11.5.0+dfsg2-1.dsc
615b80d3c6956093eb44c3f931110e2336e66210 76593241
aster_11.5.0+dfsg2.orig.tar.gz
02bd9440c90c94dfb7420a5327927a2fffa80e6b 9600
aster_11.5.0+dfsg2-1.debian.tar.xz
0b695eee838682a2ecb3adc77107bc4a2d25aa5d 1638620
code-aster_11.5.0+dfsg2-1_amd64.deb
52fad6a8fa2437eee500bb83ced8676880f771b0 6713688
code-aster-mpi-engine_11.5.0+dfsg2-1_amd64.deb
5e805b374b74cb5efe17f419478fb61979373f4d 26805108
code-aster-test_11.5.0+dfsg2-1_all.deb
Checksums-Sha256:
8978c91e5a7780791944c15b352603c6bf60a731255c972f16b39aec4b04e650 2505
aster_11.5.0+dfsg2-1.dsc
d8b2e69a889b2bc3364c7eb65cc5d7a752f221125e5ea0b4c9fb06083adfe969 76593241
aster_11.5.0+dfsg2.orig.tar.gz
d6d15bd047d6b2328c528c475d9aec2c454fc86b4e4784f82ee1ca984a4e9ffe 9600
aster_11.5.0+dfsg2-1.debian.tar.xz
7d2952d91269261673dece991c94d981cf09b6d3b085d10d14fd8eed08cb0e00 1638620
code-aster_11.5.0+dfsg2-1_amd64.deb
c048704e2cbf3d6a2395968444b97056b74c93f9a21e8b03ab810eab36779112 6713688
code-aster-mpi-engine_11.5.0+dfsg2-1_amd64.deb
0520e2abcb15537c891b3ac356d73014544d03a50410a9772732713bc382241e 26805108
code-aster-test_11.5.0+dfsg2-1_all.deb
Files:
414ff591b435248cf5c4a3eaac814137 2505 science extra aster_11.5.0+dfsg2-1.dsc
70f1e29276dd9889482bd4f33ca777be 76593241 science extra
aster_11.5.0+dfsg2.orig.tar.gz
85ab2bf0c05ea7fe39c3312c562a1a7b 9600 science extra
aster_11.5.0+dfsg2-1.debian.tar.xz
e20fc79e09dba6c216fbbfa8fe808dc1 1638620 science extra
code-aster_11.5.0+dfsg2-1_amd64.deb
d3bf944ff71922fd1479b965dc2c0799 6713688 science extra
code-aster-mpi-engine_11.5.0+dfsg2-1_amd64.deb
57b8ff59efb0dff12d4bd6357347489e 26805108 science extra
code-aster-test_11.5.0+dfsg2-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJTMvH8AAoJEDEBgAUJBeQMlEwP+gMrp8ES+rt5s7ipmytJ1y05
cDtguxVZV6w3/gNzXFZ3GzmEdiAYtvhGk77jFZTOxgcvDVqnFtTx2aoicgwHy6vv
C1P76fR/pFG0rzlr8FQ2+q/jEFKwTzEmkmELHmL+j0LyF01Do+HqvX0rzk/eq5Pu
7Cs2kEhLJLVPCPgrbeoBiGCDuV4vAwcTCmEPo3J/gFSM/OpJqPTc9iZtDKAP2Z/S
tHAeQjLx4KRForD+fam45TkQqQrgY47l2b2pAZ6NalKNnWIkCdJYMfuG3mX2Q1Uu
SlZbuyugNti5LSZwSoXZpRqM7ZR6FTFuPiQi2q5AsIAM4QgqsWVOQkfB2cgNOqUI
zhixN20j2cTLVKb7VduH2s3VT49IX+rpfPBqoFFtecTZtcSJwBq0TBWRBuaabbvb
Od5YlulRo5JUKjZ+GwieVs7nl8C9uu8iKbUu+r9e8ph8Jjid3HuIIwYfIXka2i2u
ENtEAcdOBTDZ1zVJK9TJVqOI8WYFd+3fKlm4+y02xqBJIU6DGxUhc5kIRZUmjLVq
BjdR0kKMcDfmJt/ucgc1TXfEL7HEZ2m02ZQgvKs/+h3+L4Tvk627JUHClXrEXWkc
xkaAE4VYQRTwJSvzfpL58Uj1a7fDJyAvqitOjiKQDIwNNonQOZg9mB/hj+obXLCF
Lz4B05oiyLleLF3DVfjk
=wlFA
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#670842: marked as done (code-aster-mpi-engine: can't run cases list)
Your message dated Wed, 26 Mar 2014 15:49:03 +
with message-id e1wsq4d-wm...@franck.debian.org
and subject line Bug#670842: fixed in aster 11.5.0+dfsg2-1
has caused the Debian Bug report #670842,
regarding code-aster-mpi-engine: can't run cases list
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
670842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670842
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: code-aster-mpi-engine
Version: 10.6.0-1-4
Severity: normal
Dear Maintainer,
when I tried to run a test list (as those provided by code-aster-test)
it claims about incorrect parameters.
I checked flash files (feti001a) and I could see the problem was in
tpmax and memjeveux, that were missing.
It is because in export file created automatically when a list is
provided, it doesn't write input files.
In fact if I add tpmax and memjeveux parameters in list export file, it
stops beacause of NO_COMM_FILE.
Again, I checked flash file, and no .comm, nor .para, nor .mail file
were written.
If I run the single test with an export file created by hand everything
is ok.
Best regards,
Corrado
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=UTF-8) (ignored: LC_ALL set
to it_IT.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages code-aster-mpi-engine depends on:
ii libblacs-mpi11.1-31
ii libblas3gf [libblas.so.3gf] 1.2.20110419-2
ii libc62.13-30
ii libgfortran3 4.7.0-3
ii libhdf5-openmpi-71.8.8-9
ii liblapack3gf [liblapack.so.3gf] 3.3.1-1
ii libmed1 3.0.3-3
ii libmumps-ptscotch-4.10.0 4.10.0.dfsg-3
ii libopenmpi1.31.4.3-2.1
ii libptscotch-5.1 5.1.12b.dfsg-1
ii libpython2.6 2.6.7-4
ii libpython2.7 2.7.2-8
ii libscalapack-mpi11.8.0-9
ii libscotch-5.15.1.12b.dfsg-1
ii libstdc++6 4.7.0-3
ii omniidl 4.1.6-2
ii zlib1g 1:1.2.6.dfsg-2
code-aster-mpi-engine recommends no packages.
Versions of packages code-aster-mpi-engine suggests:
ii eficas 6.4.0-1-1
ii gmsh 2.5.1~beta2~svn11845~dfsg-2
ii grace 1:5.1.22-12+b1
ii metis-edf 4.1-2-2
-- no debconf information
---End Message---
---BeginMessage---
Source: aster
Source-Version: 11.5.0+dfsg2-1
We believe that the bug you reported is fixed in the latest version of
aster, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 670...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Denis Laxalde denis.laxa...@logilab.fr (supplier of updated aster package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 26 Mar 2014 16:03:58 +0100
Source: aster
Binary: code-aster code-aster-mpi-engine code-aster-test
Architecture: source amd64 all
Version: 11.5.0+dfsg2-1
Distribution: sid
Urgency: low
Maintainer: Debian Science Team
debian-science-maintainers@lists.alioth.debian.org
Changed-By: Denis Laxalde denis.laxa...@logilab.fr
Description:
code-aster - Code_Aster finite element program - metapackage
code-aster-mpi-engine - Code_Aster finite element program - parallel binary
code-aster-test - Code_Aster finite element program - test files and examples
Closes: 670842 703415 707940 713083 731211 740091
Changes:
aster (11.5.0+dfsg2-1) unstable; urgency=low
.
* New upstream release (Closes: #731211):
- drop all previous patches that don't apply anymore;
- add new ones to fix the build system configuration;
- (most) test cases run fine (Closes: #670842);
.
* debian/control:
- set myself as uploader;
- adjust build dependencies:
+ code-aster-{run,gui} not needed,
+ use petsc-dev instead of libpetsc3.2-dev (Closes: #740091)
.
* debian/rules:
- rewrite from scratch in order to
Bug#731211: marked as done (aster: new upstream release, work in progress)
Your message dated Wed, 26 Mar 2014 15:49:03 +
with message-id e1wsq4d-wg...@franck.debian.org
and subject line Bug#731211: fixed in aster 11.5.0+dfsg2-1
has caused the Debian Bug report #731211,
regarding aster: new upstream release, work in progress
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
731211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Source: aster
Severity: wishlist
Hi,
There's a new stable release of Aster available: 11.4.
I am currently working on adapting the current packaging for this
release. The build system changed (waf inside now), so this requires a
bit of work.
Regards,
Denis
--
Denis Laxalde
Logilab http://www.logilab.fr
-- System Information:
Debian Release: 7.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: aster
Source-Version: 11.5.0+dfsg2-1
We believe that the bug you reported is fixed in the latest version of
aster, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 731...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Denis Laxalde denis.laxa...@logilab.fr (supplier of updated aster package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 26 Mar 2014 16:03:58 +0100
Source: aster
Binary: code-aster code-aster-mpi-engine code-aster-test
Architecture: source amd64 all
Version: 11.5.0+dfsg2-1
Distribution: sid
Urgency: low
Maintainer: Debian Science Team
debian-science-maintainers@lists.alioth.debian.org
Changed-By: Denis Laxalde denis.laxa...@logilab.fr
Description:
code-aster - Code_Aster finite element program - metapackage
code-aster-mpi-engine - Code_Aster finite element program - parallel binary
code-aster-test - Code_Aster finite element program - test files and examples
Closes: 670842 703415 707940 713083 731211 740091
Changes:
aster (11.5.0+dfsg2-1) unstable; urgency=low
.
* New upstream release (Closes: #731211):
- drop all previous patches that don't apply anymore;
- add new ones to fix the build system configuration;
- (most) test cases run fine (Closes: #670842);
.
* debian/control:
- set myself as uploader;
- adjust build dependencies:
+ code-aster-{run,gui} not needed,
+ use petsc-dev instead of libpetsc3.2-dev (Closes: #740091)
.
* debian/rules:
- rewrite from scratch in order to account for the change of build system,
upstream (waf is used now);
- use dh_python2 instead of python-support;
- only build the MPI version;
.
* Adjust .install files (Closes: #713083)
* Drop .postrm/.postinst files (Closes: #703415, #707940)
.
* Unpack Waf binary, hence the +dfsg.
Checksums-Sha1:
4d892337a27f7a29d9312fa1a253cb3c235d9563 2505 aster_11.5.0+dfsg2-1.dsc
615b80d3c6956093eb44c3f931110e2336e66210 76593241
aster_11.5.0+dfsg2.orig.tar.gz
02bd9440c90c94dfb7420a5327927a2fffa80e6b 9600
aster_11.5.0+dfsg2-1.debian.tar.xz
0b695eee838682a2ecb3adc77107bc4a2d25aa5d 1638620
code-aster_11.5.0+dfsg2-1_amd64.deb
52fad6a8fa2437eee500bb83ced8676880f771b0 6713688
code-aster-mpi-engine_11.5.0+dfsg2-1_amd64.deb
5e805b374b74cb5efe17f419478fb61979373f4d 26805108
code-aster-test_11.5.0+dfsg2-1_all.deb
Checksums-Sha256:
8978c91e5a7780791944c15b352603c6bf60a731255c972f16b39aec4b04e650 2505
aster_11.5.0+dfsg2-1.dsc
d8b2e69a889b2bc3364c7eb65cc5d7a752f221125e5ea0b4c9fb06083adfe969 76593241
aster_11.5.0+dfsg2.orig.tar.gz
d6d15bd047d6b2328c528c475d9aec2c454fc86b4e4784f82ee1ca984a4e9ffe 9600
aster_11.5.0+dfsg2-1.debian.tar.xz
7d2952d91269261673dece991c94d981cf09b6d3b085d10d14fd8eed08cb0e00 1638620
code-aster_11.5.0+dfsg2-1_amd64.deb
c048704e2cbf3d6a2395968444b97056b74c93f9a21e8b03ab810eab36779112 6713688
code-aster-mpi-engine_11.5.0+dfsg2-1_amd64.deb
Bug#707940: marked as done (code-aster-engine: fails to install, purge, and install again: ln: failed to create symbolic link '/usr/lib/codeaster/STABLE/config.txt': No such file or directory)
Your message dated Wed, 26 Mar 2014 15:49:03 +
with message-id e1wsq4d-ww...@franck.debian.org
and subject line Bug#707940: fixed in aster 11.5.0+dfsg2-1
has caused the Debian Bug report #707940,
regarding code-aster-engine: fails to install, purge, and install again: ln:
failed to create symbolic link '/usr/lib/codeaster/STABLE/config.txt': No such
file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
707940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: code-aster-engine
Version: 11.3.0-2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install,
remove+purge, and install again.
Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.
This is often a problem with the home directory of a system user:
the user is not deleted during purge (which is fine), but the home
directory is removed. Since the user already exists on the next
installation, adduser won't recreate the home.
From the attached log (scroll to the bottom...):
Selecting previously unselected package code-aster-engine.
(Reading database ... 7875 files and directories currently installed.)
Unpacking code-aster-engine (from
.../code-aster-engine_11.3.0-2-2+b1_amd64.deb) ...
Setting up code-aster-engine (11.3.0-2-2+b1) ...
+ CODEASTER_VERSION=STA11.3
+ pyversions -d
+ perl -pi -e s|python||g
+ dc_pyvers=2.7
+ ln -sf /usr/lib/codeaster/STABLE/config-py2.7.txt
/usr/lib/codeaster/STABLE/config.txt
ln: failed to create symbolic link '/usr/lib/codeaster/STABLE/config.txt': No
such file or directory
dpkg: error processing code-aster-engine (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
code-aster-engine
cheers,
Andreas
code-aster-engine_11.3.0-2-2+b1.log.gz
Description: GNU Zip compressed data
---End Message---
---BeginMessage---
Source: aster
Source-Version: 11.5.0+dfsg2-1
We believe that the bug you reported is fixed in the latest version of
aster, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 707...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Denis Laxalde denis.laxa...@logilab.fr (supplier of updated aster package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 26 Mar 2014 16:03:58 +0100
Source: aster
Binary: code-aster code-aster-mpi-engine code-aster-test
Architecture: source amd64 all
Version: 11.5.0+dfsg2-1
Distribution: sid
Urgency: low
Maintainer: Debian Science Team
debian-science-maintainers@lists.alioth.debian.org
Changed-By: Denis Laxalde denis.laxa...@logilab.fr
Description:
code-aster - Code_Aster finite element program - metapackage
code-aster-mpi-engine - Code_Aster finite element program - parallel binary
code-aster-test - Code_Aster finite element program - test files and examples
Closes: 670842 703415 707940 713083 731211 740091
Changes:
aster (11.5.0+dfsg2-1) unstable; urgency=low
.
* New upstream release (Closes: #731211):
- drop all previous patches that don't apply anymore;
- add new ones to fix the build system configuration;
- (most) test cases run fine (Closes: #670842);
.
* debian/control:
- set myself as uploader;
- adjust build dependencies:
+ code-aster-{run,gui} not needed,
+ use petsc-dev instead of libpetsc3.2-dev (Closes: #740091)
.
* debian/rules:
- rewrite from scratch in order to account for the change of build system,
upstream (waf is used now);
- use dh_python2 instead of python-support;
- only build the MPI version;
.
* Adjust .install files (Closes: #713083)
* Drop .postrm/.postinst files (Closes: #703415, #707940)
.
* Unpack Waf binary, hence the +dfsg.
Checksums-Sha1:
4d892337a27f7a29d9312fa1a253cb3c235d9563 2505 aster_11.5.0+dfsg2-1.dsc
615b80d3c6956093eb44c3f931110e2336e66210 76593241
aster_11.5.0+dfsg2.orig.tar.gz
glpk_4.53-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Mar 2014 14:27:17 +0100 Source: glpk Binary: libglpk36 libglpk36-dbg libglpk-dev glpk-doc glpk-utils Architecture: source all amd64 Version: 4.53-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team debian-science-maintainers@lists.alioth.debian.org Changed-By: Sébastien Villemot sebast...@debian.org Description: glpk-doc - linear programming kit - documentation files glpk-utils - linear programming kit - utility files libglpk-dev - linear programming kit - development files libglpk36 - linear programming kit with integer (MIP) support libglpk36-dbg - linear programming kit - debugging symbols Closes: 740067 Changes: glpk (4.53-2) unstable; urgency=medium . [ Maximiliano Curia ] * New patch: obtain-iodbc-cflags.patch (Closes: #740067) Checksums-Sha1: 4874e99eeaadd508f81cdcb64729221450602ce9 2255 glpk_4.53-2.dsc 4e5db4a76e5057c129591c21770bc11d3afdaece 13980 glpk_4.53-2.debian.tar.xz 6d45f1996951c21f176118c289509e34d47c387e 1027838 glpk-doc_4.53-2_all.deb 8a4927230cc6662859578483b336a8741d96fd87 410196 libglpk36_4.53-2_amd64.deb 1d8a26f99bc43b56716dc6bd0db37cf795c58287 829090 libglpk36-dbg_4.53-2_amd64.deb 893d57700dc14c9f4582e5953775bf4aef43b39a 456426 libglpk-dev_4.53-2_amd64.deb af3112a6ff6ed471c33ac5f73a0ec9d05c050353 153758 glpk-utils_4.53-2_amd64.deb Checksums-Sha256: 72ed5aa06cd1cb270474c8b126ab828b5dae4c42ccb03b06b8da20e4e1c80eca 2255 glpk_4.53-2.dsc 30ec47be38dcded07e0cfda09d107df14a54cf318fdcfcd48e836696d04973d2 13980 glpk_4.53-2.debian.tar.xz 6927cc173d7c15358144728b6c8c13cd3151d3208e6f2578890a0f08957a49a4 1027838 glpk-doc_4.53-2_all.deb 6d14e213916b9e0970f2701ae9985cd4f2b29e7d2fbf8071f2eed0d6d7c90d7c 410196 libglpk36_4.53-2_amd64.deb cb90c43293bfbe1e389319297a74700dba9b260504bace9906c9290073234515 829090 libglpk36-dbg_4.53-2_amd64.deb 784f734bf40383edbd9fe6a9c045b004cda7539aa8530054615a6a603abcbe0a 456426 libglpk-dev_4.53-2_amd64.deb 5230fdb6536b1d1f7ce01f0d90ec821e4783ea1f68c49932c195e096ba44c1b7 153758 glpk-utils_4.53-2_amd64.deb Files: 570f6b4f65ffe4cdf71b971b8a54b5d9 2255 math optional glpk_4.53-2.dsc 53341699ef2d6891ae2ebff01b7739cc 13980 math optional glpk_4.53-2.debian.tar.xz dd39001e83aacd2004208172d0123c2a 1027838 doc optional glpk-doc_4.53-2_all.deb 1ef328db4580054607f86fbde9fea202 410196 math optional libglpk36_4.53-2_amd64.deb 6867aadb442e24855199aff63686c213 829090 debug extra libglpk36-dbg_4.53-2_amd64.deb 6cdfaa19564b38589d64729d6f29a3e8 456426 libdevel optional libglpk-dev_4.53-2_amd64.deb 105be9399dffa67b2648fa1c066efa73 153758 math optional glpk-utils_4.53-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTMuavAAoJECzs6TUOzr5KGnUP+wWJbDAzENNaEUcFA2NxnCRp 7toqPHj5AUP3y1125tuFnPqv5DtWnBD+MPhxRH/48HtPP67t4N52t91zb31cYdwL iH2gkbCNadWSbkqMwuzlJUmF3qt6CXa5SMJmjEQj65AUAl8dVYWokHyZhsZVjNPR nq3AAee1F/V5vhfRWgXk3gsVbVK60XGnf+vnu/K1EOBT5f8hc1JDvLjAMRBj+jTH pFtltn0YE0eg7oL803JKaQE7q/1YcwwwXcvReiewxPZs/O7doYnODH3accIZdg2/ NbIER0Xx6XV+67G8VLeGCKauxfGG4d+MkExubIoX8YBNakTDFO8Ek5XTgB2pFJ2v JSAai9cdqwUDqL7tZXVAQx70Ufn1vcliAA5YpXYRBHzkb7aqo6MAiT6A6irK32db /uLVH5z0kEJJ6rsqln0njwoPWz2MAGK+vY6fYOufSIVdmLY7wseem85pH9F9JlO+ zRNi0QsrrH+VxADfq7INYJwL5ZC6/1JfE4bgAhpH3SpVOvwfIAQenX6wswESwKsP OP8W7NoWBbiTxlBfJFVQ5waxNUKtVmUzON6S4lPt8TrR5eLvmpNwIzNH1nY0qFiH UX/lyuylYSSnH7errFGYB9/uzGdZKuhSY84K//GqDD3uOpB/hT/OI+fo4FJFWoGY wm46xzWRRtKQCMVp/kkh =qbdU -END PGP SIGNATURE- Thank you for your contribution to Debian. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#740067: marked as done (src:glpk: Changes in build dependency libiodbc2)
Your message dated Wed, 26 Mar 2014 15:53:26 + with message-id e1wsq8t-0001tw...@franck.debian.org and subject line Bug#740067: fixed in glpk 4.53-2 has caused the Debian Bug report #740067, regarding src:glpk: Changes in build dependency libiodbc2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 740067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: glpk Version: 4.53-1 Severity: important Tags: patch Hi, I'm about to upload a new version of libiodbc2 to unstable that includes some changes that require patching glpk, I'm attaching the proposed patch. Please let me know if there is any issue related to libiodbc2 I might have overlooked. Thanks, Index: glpk-4.53/configure.ac === --- glpk-4.53.orig/configure.ac 2014-02-25 11:32:09.878480621 +0100 +++ glpk-4.53/configure.ac 2014-02-25 11:32:47.316935539 +0100 @@ -117,6 +117,7 @@ AC_MSG_ERROR([--enable-odbc requires --enable-dl]) fi AC_MSG_RESULT([yes]) + CPPFLAGS=$(iodbc-config --cflags) $CPPFLAGS AC_DEFINE_UNQUOTED([ODBC_DLNAME], [$LIBIODBC], [N/A]) elif test $enable_odbc = unix; then if test $enable_dl = no; then ---End Message--- ---BeginMessage--- Source: glpk Source-Version: 4.53-2 We believe that the bug you reported is fixed in the latest version of glpk, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 740...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot sebast...@debian.org (supplier of updated glpk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Mar 2014 14:27:17 +0100 Source: glpk Binary: libglpk36 libglpk36-dbg libglpk-dev glpk-doc glpk-utils Architecture: source all amd64 Version: 4.53-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Team debian-science-maintainers@lists.alioth.debian.org Changed-By: Sébastien Villemot sebast...@debian.org Description: glpk-doc - linear programming kit - documentation files glpk-utils - linear programming kit - utility files libglpk-dev - linear programming kit - development files libglpk36 - linear programming kit with integer (MIP) support libglpk36-dbg - linear programming kit - debugging symbols Closes: 740067 Changes: glpk (4.53-2) unstable; urgency=medium . [ Maximiliano Curia ] * New patch: obtain-iodbc-cflags.patch (Closes: #740067) Checksums-Sha1: 4874e99eeaadd508f81cdcb64729221450602ce9 2255 glpk_4.53-2.dsc 4e5db4a76e5057c129591c21770bc11d3afdaece 13980 glpk_4.53-2.debian.tar.xz 6d45f1996951c21f176118c289509e34d47c387e 1027838 glpk-doc_4.53-2_all.deb 8a4927230cc6662859578483b336a8741d96fd87 410196 libglpk36_4.53-2_amd64.deb 1d8a26f99bc43b56716dc6bd0db37cf795c58287 829090 libglpk36-dbg_4.53-2_amd64.deb 893d57700dc14c9f4582e5953775bf4aef43b39a 456426 libglpk-dev_4.53-2_amd64.deb af3112a6ff6ed471c33ac5f73a0ec9d05c050353 153758 glpk-utils_4.53-2_amd64.deb Checksums-Sha256: 72ed5aa06cd1cb270474c8b126ab828b5dae4c42ccb03b06b8da20e4e1c80eca 2255 glpk_4.53-2.dsc 30ec47be38dcded07e0cfda09d107df14a54cf318fdcfcd48e836696d04973d2 13980 glpk_4.53-2.debian.tar.xz 6927cc173d7c15358144728b6c8c13cd3151d3208e6f2578890a0f08957a49a4 1027838 glpk-doc_4.53-2_all.deb 6d14e213916b9e0970f2701ae9985cd4f2b29e7d2fbf8071f2eed0d6d7c90d7c 410196 libglpk36_4.53-2_amd64.deb cb90c43293bfbe1e389319297a74700dba9b260504bace9906c9290073234515 829090 libglpk36-dbg_4.53-2_amd64.deb 784f734bf40383edbd9fe6a9c045b004cda7539aa8530054615a6a603abcbe0a 456426 libglpk-dev_4.53-2_amd64.deb 5230fdb6536b1d1f7ce01f0d90ec821e4783ea1f68c49932c195e096ba44c1b7 153758 glpk-utils_4.53-2_amd64.deb Files: 570f6b4f65ffe4cdf71b971b8a54b5d9 2255 math optional glpk_4.53-2.dsc 53341699ef2d6891ae2ebff01b7739cc 13980 math optional glpk_4.53-2.debian.tar.xz dd39001e83aacd2004208172d0123c2a 1027838 doc optional glpk-doc_4.53-2_all.deb 1ef328db4580054607f86fbde9fea202 410196 math optional libglpk36_4.53-2_amd64.deb 6867aadb442e24855199aff63686c213 829090 debug extra libglpk36-dbg_4.53-2_amd64.deb
Re: Trilinos packages
On Wed, Mar 26, 2014 at 10:22:23AM +0100, Nico Schlömer wrote: I would suggest to first go with a monolithic package and split it up at a later point. yes. the old trilinos debian source package had a libname.patch and a soname.patch, these fix the names for a monolithic package. i suggest to import these (or just rebase your work on top of that). also, theres a note on renaming in README.Debian. and a changelog that would be nice to have. README.Debian [..] Debian Trilinos libraries renaming == Following a discussion with ftpmaster, the Trilinos libraries have been renamed to be less generic. They all use the same prefix now : libtrilinos_ . That should also help tremendously with - avoiding conflicts with other libraries/packages - identifying available trilinos libraries [..] In the course of packaging Trilinos for Debian, I have identified quite a number of bugs in Trilinos for which I maintain a little zoo of patches, https://github.com/nschloe/trilinos-ubuntu/tree/master/patches. Some of those have already made it upstream, and we'll have to see if we can get in more of those before the next release freeze. ideally those patches should be included in your package at alioth (whether or not they have been accepted upstream). is there a specific reason to maintain a second and different repository for ubuntu? regards felix -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
liggghts 3.0.0+repack-1 MIGRATED to testing
FYI: The status of the liggghts source package in Debian's testing distribution has changed. Previous version: 2.3.8-1 Current version: 3.0.0+repack-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#731211: aster: new upstream release, work in progress
Il Mercoledì 26 Marzo 2014 10:07, Denis Laxalde de...@laxalde.org 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-aster and not vice-versa. I don't understand why we'd want this. With the current binary layout, code-aster (the Python library and elements catalog) cannot be used without an engine (the aster binary), whereas the engine could (in theory) be used without the code-aster Python library or elements catalog (although it wouldn't be more useful than a python interpreter). From the Debian policy: The Depends field should be used if the depended-on package is required for the depending package to provide a significant amount of functionality. So I would say that code-aster-engine depends on code-aster. On the other hand also code-aster depends on engine, which makes it a circular dependency. They are not forbidden and we can live with it, however I would like to avoid it if possible. Note also that as_run (code-aster-run) depends on code-aster because of config.txt so we would have another circular dependency... the more I think about it the more I feel like we have to find a good solution for this. Note however that code-aster-run puts some files under /usr/lib/codeaster, so we shoult ideally take also care of code-aster-run and code-aster-gui packages. This symlink is precisely here so that as_run (from code-aster-run package) can still be used when aster is installed in /usr/lib/aster (not /usr/lib/codeaster). Ultimately, astk's packaging should be updated in order not to need this, but I currently I no time to do this. Ok, let's just keep it as it is then. - In the process, I'd like also to switch from svn to git. Not sure I get your point. It's already done. I was talking about the astk packages, but if you don't have the time to maintain them then let's stay on svn. - as_run doesn't work out of the box: it relies on having informations about available versions in the file /etc/codeaster/aster ; the script update-codeaster-engines takes care of this, it should be run on postinst/postrm scripts of the code-aster-*-engine packages. What does not work? AFAICT, it works: I can run 'as_run xxx.export' or some tests like 'as_run --test mtlp100a'. You're right: it works because the template /etc/codeaster/aster file points to STABLE when installed. However a sysadmin is not supposed to edit the file every time an engine package is installed or removed: as I said previously, this is more a status file than a config file, so the issue is still valid: we need a way to update the /etc/codeaster/aster file when an engine package is installed, be it the old postinst scripts or some other mechanism. - provide also the serial version - a simple script to run the test cases would be nice... the .comm file that was used for this purpose has been removed from upstream, or it's just me that can't find it? In the previous packaging there were an as_test script, maybe I can work on it... - 11.5 is already out And I updated the packaging for this version already. Great :D - and I'd like to provide also testing/unstable versions Again, let's keep it simple first. Sure, it was just a wish :) Bye Andrea -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Re: Alioth /git/debian-science/packages directory
2014-03-26 16:41 GMT+01:00 Leopold Palomo-Avellaneda l...@alaxarxa.net: I thought that the packages from robotics blend could go to a folder (for instance robotics). So, my question is what do you think if we are moving the git repo to a folder with the name of the blend, or something that classify it? I do not think, that it is necessary and can improve anything. IMHO. Cheers Anton -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
[sponsor needed] Updates to urdfdom and urdfdom-headers
Hi all: I would need a sponsor to upload the updates to our packages: urdfdom and urdfdom-headers. Both jump to version 0.3.0, and the updates are already in their respective debian repositories: http://anonscm.debian.org/gitweb/?p=debian-science/packages/urdfdom.git http://anonscm.debian.org/gitweb/?p=debian-science/packages/urdfdom-headers.git Thanks. -- Jose Luis Rivero jriv...@osrfoundation.org -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#741303: libfeel++1: libfeelpp.so.1.0.0 links with both GPL-licensed and GPL-incompatible libraries
On Wed, 26 Mar 2014 15:52:34 +0100 Christophe Prud'homme wrote: Dear Francesco Poli Hello Christophe, thanks for commenting my bug report. What is the state of this bug ? any progress with respect to scotch licensing ? I am not aware of any progress: I am the bug report submitter and, as I said in the original bug report, I need help from other people who volunteer to get in touch with the upstream developer of SCOTCH and persuade him to re-license SCOTCH under the LGPL. I have already tried to do so in the past, but I failed to convince him that there is an issue. Please (re-)read https://bugs.debian.org/740463#5 for the full story. Are you willing to help? If so, please contact the main author of SCOTCH and explain the licensing headaches he is causing to several other projects. If you manage to persuade him (to get the necessary paperwork) to re-license SCOTCH under the LGPL v2.1 or, at least, to dual-license it under the GNU LGPL v2.1 or the CeCILL-C v1.0 (at the recipient's choice), all the GPL-incompatibility issues will instantly vanish! this is a really painful situation ! Indeed. are petsc and all libraries (based on umfpack) related to this bug issues marked for removal from testing ? By looking at http://udd.debian.org/cgi-bin/autoremovals.cgi it seems to me that feel++ and getdp are marked for auto-removal from Debian testing, while other packages affected by SCOTCH licensing issues are not (yet?) on the list. I am not sure why (maybe because they are not leaf packages?). The complete list of SCOTCH licensing bug reports is https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;tag=scotch-license-issues;users=debian-science-maintainers@lists.alioth.debian.org have you marked also octave with an RC bug ? it uses suitesparse/umfpack and scotch [1] Could you please elaborate? I cannot spot the dependency of octave on scotch... Basically all libraries/programs using suitesparse/umfpack should have this bug, no ? Only when they contain a file which (directly or indirectly) links with both SCOTCH and some GPL-licensed library (such as UMFPACK)... I think Libreoffice/Openoffice are using suitesparse(and scotch) and glpk so it should also have the RC bug. libreoffice? glpk? Could you please help me to find the dependency on scotch? I fail to see it... I guess that the technical solution would be to get rid of umfpack but then that would disrupt a lot of software ! I think I clearly illustrated the solutions that I consider as acceptable: see my original bug report(s). Solution (A) is the most desirable, that's why I called for help to push in that direction... I hope this clarifies. -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpwO9vjHrans.pgp Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#742752: linking patches for the scilab build system
Package: scilab Version: 5.5.0~beta-1~git~20140324-1354-1 Severity: important Tags: patch Hi, here are a few patches for the scilab build system, where from my point of view, upstream doesn't understand autotools. - the scilab-bin and scilab-cli-bin binaries reference symbols in the .o files, which are not explicitly linked. Recent binutils default to --no-copy-dt-needed-entries, so I'm not sure why the build doesn't fail. fix-binary-linking.diff tries to fix that, suggestions which library to fix in which case by Sylvestre Ledru. - fix-lib-linking.diff fixes the understanding of LDFLAGS and LIBADD. I think these are all cases, but maybe I do miss some. - add-lib-dependencies.diff fixes some underlinking. this is seen in load errors when trying to build the docs. There is a patch commented out for modules/graphic_export which seems to be needed, but apparently the build system has some dependency cycles, so this won't work. - disable-no-as-needed.diff makes no difference for Debian builds. However, with or without it, it still fails on Ubuntu 14.04. I think I did fix the worst misconceptions, but the upstream build system still looks like some kind of mess. I won't have time to further dive into that. The patches still allow the build on Debian unstable, but still ftbfs on Ubuntu trusty. The only difference for Ubuntu should be the --as-needed default and the hardening defaults, but despite adding the extra flags to disable these defaults, the build still fails. The Debian portion of the patch calls autoreconf. Looks like you should disable the modelica bits on architectures which have ocaml but don't have ocamlopt. patches at: http://launchpadlibrarian.net/170791978/scilab_5.5.0%7Ebeta-1%2Bgit%7E20140324-1354-1ubuntu1_5.5.0%7Ebeta-1%2Bgit%7E20140324-1354-1ubuntu2.diff.gz -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
A votre aimable attention
Bonsoir, Excusez-moi, du fait que mon mail puisse vous choquer. Cela fait quelques jours, que j'ai envoyé ce mail à une association qui s'occupe des enfants démunis. Depuis lors, je n'ai toujours pas eu de réponse de cette association qui se prétend être pour les enfants démunis et pourtant ce n'était pas vraiment le cas. Mais, j'ai pu obtenir votre profil grâce à un logiciel appelé contact Express v2013 France. Un moteur de recherche de profil privilégié sur internet et si vous recevez ma lettre ce jour, je vous prie de me répondre. Je vous fais savoir avec confiance que je dispose de 180.000 Euros dans une banque dans le pays ou j'étais en fonction en qualité d'ingénieure énergéticien. Mon souhait est d'en faire un don car je n'ai pas d’héritiers, ni parents à qui léguer mon argent, vue que mes jours sont en danger à cause de mon état de santé critique. Je dois subir une intervention chirurgicale les jours à venir dans un hôpital spécialisé. Je ne sais pas ce que l'être suprême me réserve, les résultats de certaines de mes analyses médicales font état de ce que mes jours sur terre sont comptés. Mon désire est que vous prenez contact au plutôt avec mon avocat pour qu'il vous aide à rentré en possession de ces fonds, car il est déjà informé de mes intentions envers vous. Maître Francis DAKO email: etude_mefrancisd...@yahoo.fr Très sincèrement. Jeanne MORAU -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
συναγερμού ενημέρωση
γραμματοκιβώτιό σας έχει υπερβεί, το όριο αποθήκευσης είναι 1 GB, η οποία ορίζεται από το διαχειριστή, είναι τρέχει σε 99,8 gigabytes, δεν μπορείτε να στείλετε ή να λάβετε νέα μηνύματα, μέχρι να ξανά-validate γραμματοκιβώτιό σας. να ανανεώσει το γραμματοκιβώτιο, κάντε κλικ στο παρακάτω σύνδεσμο: http://webphysicsuocgr.yolasite.com/ Σας ευχαριστώ! διαχειριστής του συστήματος webmail -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
