Bug#457075: Status of Salomé packaging
On Thu, Aug 21, 2008 at 2:02 PM, Adam C Powell IV <[EMAIL PROTECTED]> wrote: > On Thu, 2008-08-21 at 13:19 +0200, Jordi Mallach wrote: >> Hi Adam & rest of list, >> >> I've been checking the archives for progress on Salomé's ITP, which >> seemed quite promising back in March. However, after the success with >> the OpenCASCADE effort, I see no more references to Salomé. >> >> Is the ITP stalled for some licensing reason, or do the compile problems >> still apply and have not been resolved yet? > > I have resolved the compile problems, but at runtime, none of the > modules load. (As noted in this bug, you can get the latest at > http://lyre.mit.edu/~powell/salome/ .) I've solved this problem before, > and could solve it again. > > But upstream practices are really frustrating me. They released a new > binary 3.2.9 Salomé-MECA back in -- forgot, March? -- but with no source > code. So any new effort I make is already obsolete. Furthermore, they > have never released the source of the MECA extensions, even though this > is supposed to be an open source project. > > To add insult to injury, they have *never* replied to ANY of my emails > or website inquiries. (I even took the time to write to specific > developers in French, but with no reply.) I have put a *TON* of effort > into this, on the order of 100 hours, as you can see from the nearly 50 > patches, and really feel blown off and disrespected by upstream. > > At some point I'll give up on upstream and go ahead and fix the 3.2.6 > package, essentially maintaining a Debian fork until upstream releases > more source. But this is a very low priority for the above reasons. > > While ranting about upstream, I should thank Sylvestre Ledru for > participating in the discussion with upstream, including using some of > his contacts to try to move this along. I hear there will be a meeting > in September to try to resolve some of these issues, and will return to > packaging work if something comes out of this process. This is really frustrating. Sorry to hear that! That's why I prefer small tools, or tools that are simple in nature, so that in the worse case one can maintain it alone if upstream decides to close the source. Ondrej
Bug#462631: status update
On Tue, Feb 19, 2008 at 1:10 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > On Feb 19, 2008 11:59 AM, Francesco Poli <[EMAIL PROTECTED]> wrote: > > On Sun, 17 Feb 2008 15:32:21 +0100 Ondrej Certik wrote: > > > > > Hi Francesco, > > > > Hi! :) > > > > > > > > On Thu, Feb 07, 2008 at 12:23:00AM +0100, Francesco Poli wrote: > > [...] > > > > I wonder if you managed to link Paraview against (and make it work > > > > properly with) libraries already packaged and included in Debian. > > > > > > Not yet. Currently we are still trying to make it compile on i386 and > > > amd64 together with MPI and python. We just succeeded in the compilation > > > itself, so at least the package builds now. > > > > I see. > > > > > > > > Unfortunately, the python scripting still isn't working at runtime. When > > > this is fixed, only then we'll try to build shared libraries and reuse > > > as much as possible from Debian to reduce the sice of the paraview > > > binary package (currently 100MB). > > > > Really huge! I hope you soon manage to successfully package it without > > the "extraneous" libraries! > > Christphe managed to cut the size down to 33MB. Everything seems to work now > just fine, the only exception is python support. Follow our malinglist > for the latest updates. All major things are fixed now: * python scripting works * MPI works * binary package size is 35MB * tested on i386 and amd64 what remains: * manpages * lintian warnings fixes The updodate wokring packages compiled for i386 and amd64 can always be found here: http://debian.certik.cz/ Feel free to test them and report all bugs to our mailinglist. Also any help with fixing the remaining things is appreciated. Ondrej Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462631: current status
On Feb 19, 2008 11:59 AM, Francesco Poli <[EMAIL PROTECTED]> wrote: > On Sun, 17 Feb 2008 15:32:21 +0100 Ondrej Certik wrote: > > > Hi Francesco, > > Hi! :) > > > > > On Thu, Feb 07, 2008 at 12:23:00AM +0100, Francesco Poli wrote: > [...] > > > I wonder if you managed to link Paraview against (and make it work > > > properly with) libraries already packaged and included in Debian. > > > > Not yet. Currently we are still trying to make it compile on i386 and > > amd64 together with MPI and python. We just succeeded in the compilation > > itself, so at least the package builds now. > > I see. > > > > > Unfortunately, the python scripting still isn't working at runtime. When > > this is fixed, only then we'll try to build shared libraries and reuse > > as much as possible from Debian to reduce the sice of the paraview > > binary package (currently 100MB). > > Really huge! I hope you soon manage to successfully package it without > the "extraneous" libraries! Christphe managed to cut the size down to 33MB. Everything seems to work now just fine, the only exception is python support. Follow our malinglist for the latest updates. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462631: current status
Hi Francesco, On Thu, Feb 07, 2008 at 12:23:00AM +0100, Francesco Poli wrote: > Hi! > > Thanks for your ITP bug regarding Paraview! > I hope the packaging is going on well. You can see for yourself. Our svn is here: XS-Vcs-Svn: svn://svn.debian.org/svn/pkg-scicomp/paraview/ XS-Vcs-Browser: http://svn.debian.org/wsvn/pkg-scicomp/paraview/ We welcome any help with the packaging. > I wonder if you managed to link Paraview against (and make it work > properly with) libraries already packaged and included in Debian. Not yet. Currently we are still trying to make it compile on i386 and amd64 together with MPI and python. We just succeeded in the compilation itself, so at least the package builds now. Unfortunately, the python scripting still isn't working at runtime. When this is fixed, only then we'll try to build shared libraries and reuse as much as possible from Debian to reduce the sice of the paraview binary package (currently 100MB). > > Last time I checked, it seemed Paraview could not be linked with > already installed libraries (without applying heavy modifications). > I think that, from a maintainability/code-duplication point of view, > shipping a special copy of VTK and TclTk just for Paraview would > not be acceptable. Unfortunately though, last time I checked, Paraview > shipped with special versions of those libraries that had to be > recompiled: > http://public.kitware.com/pipermail/paraview/2006-October/003881.html > > I hope the situation has improved in the meanwhile: for instance, > Paraview was going to switch from TclTk to Qt and it seems this > transition has already been completed... Is it now possible to easily > link Paraview against an already installed copy of VTK? I don't know, we didn't try it yet. > Or did you modify CMakeLists.txt in order to let Paraview compile and > link against debianized VTK? Not yet. First we need to make it work with all the features. If you would like to help us, it'd be awesome. Feel free to join the http://wiki.debian.org/Teams/DebianScientificComputingTeam where the package is maintained. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459729: ITP: pyglet -- a cross-platform windowing and multimedia library for Python
> > I am not seeing any files, and "git log" fails, so does gitk. Could > > you please send me the debian dir, maybe it will be easier. > This repos does not utilize a 'master' branch. In your clone do: > > git branch -a > > After a > > git checkout -b master origin/release > > also gitk and git log will work. Excellent, this works nice. Thanks! Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459729: ITP: pyglet -- a cross-platform windowing and multimedia library for Python
On Feb 11, 2008 11:40 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > > On Feb 11, 2008 10:45 AM, Michael Hanke <[EMAIL PROTECTED]> wrote: > > > > > > On Mon, Feb 11, 2008 at 09:43:41AM +0100, Ondrej Certik wrote: > > > On Feb 11, 2008 7:04 AM, Michael Hanke <[EMAIL PROTECTED]> wrote: > > > > Hi Ondrej, > > > > > > > > On Mon, Feb 11, 2008 at 12:33:28AM +0100, Ondrej Certik wrote: > > > > > > At the moment pyglet is included in the python-sympy package. As it > > > > > > can > > > > > > be viewed as a pygame replacement sympy maintainers agree that it > > > > > > should > > > > > > be packaged separately. > > > > > > > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459716 > > > > > > > > > > > > The final package will be maintained by the pkg-exppsy project on > > > > > > alioth. > > > > > > > > > > Could you please maintain pyglet in the Debian Python Modules Team > > > > > (DPMT)? > > > > > > > > > > http://wiki.debian.org/Teams/PythonModulesTeam > > > > > > > > > > This is so that it's easy for the DPMT members to manage and make > > > > > changes to all python modules. For example when a python policy > > > > > changes, > > > > > or we switch from python2.4 to python2.5 etc. > > > > Sure I would, but read on. > > > > > > > > > Upstream has released a new version that works with sympy. Any > > > > > progress in packaging it? > > > > I have a package for 1.0. But I failed to convince upstream the put the > > > > documentation sources into the source tarball. He seems to be pretty > > > > much set with respect to what people need and what not. Therefore the > > > > sources have to be repackages (removed docs) or a new source > > > > distribution has to be compiled from the upstream source SVN. > > > > > > I see. No problem, let's repackage upstream by deleting the doc > > > directory I do that > > > by adding a target get-orig-sources in the debian/rules, which does that > > > for me. > > Right. It is just not nice that the package won't ship docs. But well, > > that's life. > > Well, I prefer to browse the docs on the web anyway, or read the > sources directly. > > > > > > > At the moment I am (re)evaluating whether I want to do that or go with > > > > pygame. > > > > > > In sympy, we use svn, but for Debian I recommend to package the latest > > > released > > > version (with deleting the doc dir), so that all is clear which version > > > we have. > > > > > > > > > > > If you or the DPMT want to take over, please feel free to do so: > > > > > > > > http://git.debian.org/?p=pkg-exppsy/pyglet.git;a=summary > > > > > > OK, I'll take over it. The only problem is that DPMT uses svn for all > > > it's packages. > > > So I just start initialize it with your latest git version, is that ok? > > Sure, please go on. > > > > Could you please drop me a note when you checked it into SVN. I will > > remove the git repository when it is done. > > I am sorry for a stupid question - am I doing something wrong, or is > the git repository corrupted? > > [EMAIL PROTECTED]:/tmp/p$ git clone > git://git.debian.org/git/pkg-exppsy/pyglet.git > Initialized empty Git repository in /tmp/p/pyglet/.git/ > remote: Generating pack... > remote: Done counting 1440 objects. > remote: Deltifying 1440 objects... > remote: 100% (1440/1440) done > remote: Total 1440 (delta 945), reused 1315 (delta 828) > Receiving objects: 100% (1440/1440), 4.10 MiB | 391 KiB/s, done. > Resolving deltas: 100% (945/945), done. > [EMAIL PROTECTED]:/tmp/p$ cd pyglet/ > [EMAIL PROTECTED]:/tmp/p/pyglet$ ls > [EMAIL PROTECTED]:/tmp/p/pyglet$ la > .git > [EMAIL PROTECTED]:/tmp/p/pyglet$ git branch > [EMAIL PROTECTED]:/tmp/p/pyglet$ git log > fatal: bad default revision 'HEAD' > [EMAIL PROTECTED]:/tmp/p/pyglet$ > > > I am not seeing any files, and "git log" fails, so does gitk. Could > you please send me the debian dir, maybe it will be easier. I managed to get the sources on this link: http://git.debian.org/?p=pkg-exppsy/pyglet.git;a=snapshot;h=95e0159c01e501b7c6e3f5c841018fb354901ca5 So you can now delete the git repo. But still I am curious why it didn't work the way I described. The svn repo is here: http://svn.debian.org/wsvn/python-modules/packages/pyglet/trunk/?op=log Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459729: ITP: pyglet -- a cross-platform windowing and multimedia library for Python
On Feb 11, 2008 10:45 AM, Michael Hanke <[EMAIL PROTECTED]> wrote: > > > On Mon, Feb 11, 2008 at 09:43:41AM +0100, Ondrej Certik wrote: > > On Feb 11, 2008 7:04 AM, Michael Hanke <[EMAIL PROTECTED]> wrote: > > > Hi Ondrej, > > > > > > On Mon, Feb 11, 2008 at 12:33:28AM +0100, Ondrej Certik wrote: > > > > > At the moment pyglet is included in the python-sympy package. As it > > > > > can > > > > > be viewed as a pygame replacement sympy maintainers agree that it > > > > > should > > > > > be packaged separately. > > > > > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459716 > > > > > > > > > > The final package will be maintained by the pkg-exppsy project on > > > > > alioth. > > > > > > > > Could you please maintain pyglet in the Debian Python Modules Team > > > > (DPMT)? > > > > > > > > http://wiki.debian.org/Teams/PythonModulesTeam > > > > > > > > This is so that it's easy for the DPMT members to manage and make > > > > changes to all python modules. For example when a python policy > > > > changes, > > > > or we switch from python2.4 to python2.5 etc. > > > Sure I would, but read on. > > > > > > > Upstream has released a new version that works with sympy. Any > > > > progress in packaging it? > > > I have a package for 1.0. But I failed to convince upstream the put the > > > documentation sources into the source tarball. He seems to be pretty > > > much set with respect to what people need and what not. Therefore the > > > sources have to be repackages (removed docs) or a new source > > > distribution has to be compiled from the upstream source SVN. > > > > I see. No problem, let's repackage upstream by deleting the doc > > directory I do that > > by adding a target get-orig-sources in the debian/rules, which does that > > for me. > Right. It is just not nice that the package won't ship docs. But well, > that's life. Well, I prefer to browse the docs on the web anyway, or read the sources directly. > > > > At the moment I am (re)evaluating whether I want to do that or go with > > > pygame. > > > > In sympy, we use svn, but for Debian I recommend to package the latest > > released > > version (with deleting the doc dir), so that all is clear which version we > > have. > > > > > > > > If you or the DPMT want to take over, please feel free to do so: > > > > > > http://git.debian.org/?p=pkg-exppsy/pyglet.git;a=summary > > > > OK, I'll take over it. The only problem is that DPMT uses svn for all > > it's packages. > > So I just start initialize it with your latest git version, is that ok? > Sure, please go on. > > Could you please drop me a note when you checked it into SVN. I will > remove the git repository when it is done. I am sorry for a stupid question - am I doing something wrong, or is the git repository corrupted? [EMAIL PROTECTED]:/tmp/p$ git clone git://git.debian.org/git/pkg-exppsy/pyglet.git Initialized empty Git repository in /tmp/p/pyglet/.git/ remote: Generating pack... remote: Done counting 1440 objects. remote: Deltifying 1440 objects... remote: 100% (1440/1440) done remote: Total 1440 (delta 945), reused 1315 (delta 828) Receiving objects: 100% (1440/1440), 4.10 MiB | 391 KiB/s, done. Resolving deltas: 100% (945/945), done. [EMAIL PROTECTED]:/tmp/p$ cd pyglet/ [EMAIL PROTECTED]:/tmp/p/pyglet$ ls [EMAIL PROTECTED]:/tmp/p/pyglet$ la .git [EMAIL PROTECTED]:/tmp/p/pyglet$ git branch [EMAIL PROTECTED]:/tmp/p/pyglet$ git log fatal: bad default revision 'HEAD' [EMAIL PROTECTED]:/tmp/p/pyglet$ I am not seeing any files, and "git log" fails, so does gitk. Could you please send me the debian dir, maybe it will be easier. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459729: ITP: pyglet -- a cross-platform windowing and multimedia library for Python
On Feb 11, 2008 7:04 AM, Michael Hanke <[EMAIL PROTECTED]> wrote: > Hi Ondrej, > > On Mon, Feb 11, 2008 at 12:33:28AM +0100, Ondrej Certik wrote: > > > At the moment pyglet is included in the python-sympy package. As it can > > > be viewed as a pygame replacement sympy maintainers agree that it should > > > be packaged separately. > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459716 > > > > > > The final package will be maintained by the pkg-exppsy project on > > > alioth. > > > > Could you please maintain pyglet in the Debian Python Modules Team (DPMT)? > > > > http://wiki.debian.org/Teams/PythonModulesTeam > > > > This is so that it's easy for the DPMT members to manage and make > > changes to all python modules. For example when a python policy > > changes, > > or we switch from python2.4 to python2.5 etc. > Sure I would, but read on. > > > Upstream has released a new version that works with sympy. Any > > progress in packaging it? > I have a package for 1.0. But I failed to convince upstream the put the > documentation sources into the source tarball. He seems to be pretty > much set with respect to what people need and what not. Therefore the > sources have to be repackages (removed docs) or a new source > distribution has to be compiled from the upstream source SVN. I see. No problem, let's repackage upstream by deleting the doc directory I do that by adding a target get-orig-sources in the debian/rules, which does that for me. > At the moment I am (re)evaluating whether I want to do that or go with > pygame. In sympy, we use svn, but for Debian I recommend to package the latest released version (with deleting the doc dir), so that all is clear which version we have. > > If you or the DPMT want to take over, please feel free to do so: > > http://git.debian.org/?p=pkg-exppsy/pyglet.git;a=summary OK, I'll take over it. The only problem is that DPMT uses svn for all it's packages. So I just start initialize it with your latest git version, is that ok? Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459729: ITP: pyglet -- a cross-platform windowing and multimedia library for Python
> At the moment pyglet is included in the python-sympy package. As it can > be viewed as a pygame replacement sympy maintainers agree that it should > be packaged separately. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459716 > > The final package will be maintained by the pkg-exppsy project on > alioth. Could you please maintain pyglet in the Debian Python Modules Team (DPMT)? http://wiki.debian.org/Teams/PythonModulesTeam This is so that it's easy for the DPMT members to manage and make changes to all python modules. For example when a python policy changes, or we switch from python2.4 to python2.5 etc. Upstream has released a new version that works with sympy. Any progress in packaging it? Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462631: [Pkg-scicomp-devel] current state
On Feb 3, 2008 10:42 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > Hi Christophe, > > > > | what is the state of this? I also would like to use this package in > > > | Debian very much. I tried to compile from source, but I am getting an > > > | error, that paraview only compiles with QT 4.2, but in Debian there is > > > | QT 4.3.3. Did you succeed compiling it? > > > You have to go for the CVS version. The version I retrieved a few days ago > > > from CVS works well with the Qt version in Debian. > > > I have the configuration relatively complete included MPI support (which I > > > need, and paraview is not distributed which mpi support on paraview.org) > > > Now I need to create the package. > > > I need the package soon, at least in some state, so I already created > almost a working solution in our svn. Feel free to base your work on > that, or create a new directory for the cvs version. Also this link > come very handy: > > http://cvs.fedora.redhat.com/viewcvs/rpms/paraview/devel/ > > It contains all the patches that fedora guys had to apply to make it > work. So I am going to apply them to the released version of paraview, > it should do the job mostly. ok, I applied the fedora patches and the paraview package in our svn just built on both i386 and amd64 for me. Without MPI. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462631: [Pkg-scicomp-devel] current state
Hi Christophe, > > | what is the state of this? I also would like to use this package in > > | Debian very much. I tried to compile from source, but I am getting an > > | error, that paraview only compiles with QT 4.2, but in Debian there is > > | QT 4.3.3. Did you succeed compiling it? > > You have to go for the CVS version. The version I retrieved a few days ago > > from CVS works well with the Qt version in Debian. > > I have the configuration relatively complete included MPI support (which I > > need, and paraview is not distributed which mpi support on paraview.org) > > Now I need to create the package. I need the package soon, at least in some state, so I already created almost a working solution in our svn. Feel free to base your work on that, or create a new directory for the cvs version. Also this link come very handy: http://cvs.fedora.redhat.com/viewcvs/rpms/paraview/devel/ It contains all the patches that fedora guys had to apply to make it work. So I am going to apply them to the released version of paraview, it should do the job mostly. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462631: current state
Hi Christophe, what is the state of this? I also would like to use this package in Debian very much. I tried to compile from source, but I am getting an error, that paraview only compiles with QT 4.2, but in Debian there is QT 4.3.3. Did you succeed compiling it? Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455292: work in progress
This is a huge task. But a work on this has started already, please follow all development here: http://wiki.sagemath.org/DebianSAGE Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451039: ITP: cython -- C-Extensions for Python
>Package name: cython > Version: 0.9.6.8.ds > Upstream Author: Stefan Behnel, Robert Bradshaw, and William Stein > URL: http://www.cython.org/ > License: Python Software Foundation License > Description: C-Extensions for Python > Cython is a language that makes writing C extensions for the Python > language as > easy as Python itself. > . > Cython is based on the well-known Pyrex, but supports more cutting edge > functionality and optimizations. > . > Development of Cython is mainly motivated by the needs of SAGE. A preliminary package of cython could be downloaded from: http://debian.certik.cz/ It works, but still needs some QA work, before it could be uploaded to sid. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451039: ITP: cython -- C-Extensions for Python
Package: wnpp Severity: wishlist X-Debbugs-CC: [EMAIL PROTECTED] --- Please fill out the fields below. --- Package name: cython Version: 0.9.6.8.ds Upstream Author: Stefan Behnel, Robert Bradshaw, and William Stein URL: http://www.cython.org/ License: Python Software Foundation License Description: C-Extensions for Python Cython is a language that makes writing C extensions for the Python language as easy as Python itself. . Cython is based on the well-known Pyrex, but supports more cutting edge functionality and optimizations. . Development of Cython is mainly motivated by the needs of SAGE. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441302: ITP: getxpath -- extract a value from a XML file using a XPATH expression
> same here, do we really need a package for a wrapper around xsltproc, > where the GPL header is larger than the script itself? Why not to put that script inside the xsltproc package instead of creating a new one? Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#435394: ITP: blzpack -- library for solving large sparse eigenproblems
Package: wnpp Owner: Ondrej Certik <[EMAIL PROTECTED]> Severity: wishlist * Package name: blzpack Version : 0.0.20020101 Upstream Author : Osni Marques <[EMAIL PROTECTED]> * URL : http://crd.lbl.gov/~osni/#Software * License : BSD Programming Lang: Fortran 77 Description : library for solving large sparse eigenproblems BLZPACK (for Block LancZos PACKage, release 04/00) is a standard Fortran 77 implementation of the block Lanczos algorithm intended for the solution of the standard eigenvalue problem Ax=µx or the generalized eigenvalue problem Ax=µBx, where A and B are real, sparse symmetric matrices, µ an eigenvalue and x an eigenvector. . The development of this eigensolver was motivated by the need to solve large, sparse, generalized problems from free vibration analyses in structural engineering. Several upgrades were performed afterwards aiming at the solution of eigenvalues problems from a wider range of applications. . Documentation: user's guide, technical report and comprehensive bibliography. . Install this package if you need to compile or link against BLZPACK. . Homepage: http://crd.lbl.gov/~osni/#Software -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.20-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
Bug#434912: ITP: abinit -- A package for electronic structure calculations
Package: wnpp Severity: wishlist X-Debbugs-CC: [EMAIL PROTECTED] --- Please fill out the fields below. --- Package name: abinit Version: 5.3.4 Upstream Author: Prof. Xavier Gonze URL: http://www.abinit.org/ License: GPL Description: ABINIT is a package whose main program allows one to find the total energy, charge density and electronic structure of systems made of electrons and nuclei (molecules and periodic solids) within Density Functional Theory (DFT), using pseudopotentials and a planewave basis. . ABINIT also includes options to optimize the geometry according to the DFT forces and stresses, or to perform molecular dynamics simulations using these forces, or to generate dynamical matrices, Born effective charges, and dielectric tensors. Excited states can be computed within the Time-Dependent Density Functional Theory (for molecules), or within Many-Body Perturbation Theory (the GW approximation). In addition to the main ABINIT code, different utility programs are provided. . Homepage: http://www.abinit.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428265: ITP: openmx -- Package for nano-scale material simulations
Package: wnpp Owner: Ondrej Certik <[EMAIL PROTECTED]> Severity: wishlist * Package name: openmx Version : 3.2 Upstream Author : Taisuke Ozaki * URL : http://www.openmx-square.org/ * License : GPL Programming Lang: C Description : Package for nano-scale material simulations OpenMX (Open source package for Material eXplorer) is a program package for nano-scale material simulations based on density functional theories (DFT), norm-conserving pseudopotentials and pseudo-atomic localized basis functions. Since the code is designed for the realization of large-scale ab initio calculations on parallel computers, it is anticipated that OpenMX can be a useful and powerful tool for nano-scale material sciences in a wide variety of systems such as biomaterials, carbon nanotubes, magnetic materials, and nanoscale conductors. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#427094: ITP: tetgen -- TetGen - A Quality Tetrahedral Mesh Generator
Package: wnpp Owner: Ondrej Certik <[EMAIL PROTECTED]> Severity: wishlist * Package name: tetgen Version : 1.4.1 Upstream Author : Hang Si <[EMAIL PROTECTED]> * URL : http://tetgen.berlios.de/ * License : MIT with a non-free clausule Programming Lang: C++ Description : TetGen - A Quality Tetrahedral Mesh Generator TetGen generates the Delaunay tetrahedralization, Voronoi diagram, and convex hull for three-dimensional point sets, generates the constrained Delaunay tetrahedralizations and quality tetrahedral meshes for three-dimensional domains with piecewise linear boundary. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426734: ITP: libmesh -- libMesh - A C++ Finite Element Library
Package: wnpp Severity: wishlist Owner: Ondrej Certik <[EMAIL PROTECTED]> * Package name: libmesh Version : 0.6.0~rc2 Upstream Author : Benjamin S. Kirk <[EMAIL PROTECTED]> * URL : http://libmesh.sourceforge.net * License : LGPL Programming Lang: C++ Description : libMesh - A C++ Finite Element Library The libMesh library is a C++ framework for the numerical simulation of partial differential equations on serial and parallel platforms. Development began in March 2002 with the intent of providing a friendly interface to a number of high-quality software packages that are publicly available. Currently the library supports 1D, 2D, and 3D steady and transient finite element and finite volume simulations. PETSc is currently used for the solution of linear systems on both serial and parallel platforms. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#421677: ITP: python-petsc4py -- Python bindings for PETSc libraries
Package: wnpp Severity: wishlist Owner: Ondrej Certik <[EMAIL PROTECTED]> * Package name: python-petsc4py Version : 0.7.3 Upstream Author : Lisandro Dalcin <[EMAIL PROTECTED]> * URL : http://code.google.com/p/petsc4py/ * License : BSD Programming Lang: C, Python Description : Python bindings for PETSc libraries PETSc is a suite of data structures and routines for the scalable (parallel) solution of scientific applications modeled by partial differential equations. It employs the MPI standard for all message-passing communication. petsc4py are Python bindings for the PETSc libraries. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418410: ITP: python-sympy -- Computer Algebra System (CAS) in Python
Package: wnpp Severity: wishlist Owner: Ondrej Certik <[EMAIL PROTECTED]> * Package name: python-sympy Version : 0.3 Upstream Author : Ondrej Certik <[EMAIL PROTECTED]> * URL : http://code.google.com/p/sympy * License : GPL Programming Lang: Python Description : Computer Algebra System (CAS) in Python SymPy is a symbolic manipulation package, written in pure Python. Its aim is to become a full featured CAS in Python, while keeping the code as simple as possible in order to be comprehensible and easily extensible. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=czech (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
