Bug#676620: RFS: FreeFOAM
Package: sponsorship-requests Severity: normal I am looking for a sponsor of the FreeFOAM software for Computational FLuid Dynamics (CFD) which uses the Control / Finite Volume Method. * Package name: freefoam Version : 0.1.0-1 Upstream Author : Michael Wild * URL : http://freefoam.sourceforge.net/ * License : GPL-3+ Section : science It builds the follwing binary packages: freefoam-dev-doc - software for Computational Fluid Dynamics - developers documentation freefoam - programs for Computational Fluid Dynamics (CFD) libfreefoam - libraries for Computational Fluid Dynamics (CFD) libfreefoam-dev - libraries for Computational Fluid Dynamics (CFD) - development files freefoam-user-doc - software for Computational Fluid Dynamics - user documentation The packages can be found at: http://mentors.debian.net/package/freefoam The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/f/freefoam/freefoam_0.1.0 +dfsg-1.dsc Also, there is a git repo at debian/science: http://git.debian.org/?p=debian-science/packages/freefoam.git Changes since the last upload: - Removed non-free files (+dfsg) - Repaired debian/watch The package also builds correctly under pbuilder. Gerber van der Graaf -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1339149036.2209.49.ca...@delft.vdg.net
RFS frefoam
I modified the FreeFOAM source code by removing the non-free files. Also debian/watch has been modified and now seems to work fine. The packages can be found at: http://mentors.debian.net/package/freefoam The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/f/freefoam/freefoam_0.1.0 +dfsg-1.dsc Also, the git repo at debian/science has been updated: http://git.debian.org/?p=debian-science/packages/freefoam.git Gerber van der Graaf -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1339014211.5054.9.camel@solo
+dfsg
For the (lib)freefoam* packages I am building I came across some non-free files in the source. I got some remarks that the non-free files will have to be removed and the source will have to be re-packed in a new +dfsg tar file (instead of providing patches in debian/). As I will have to remove an entire directory, containing a module, its parent directory contains a CMakeLists.txt file containing 'add_subdirectory(subdir_containing_non_free_files)' My question is: do I have to provide a patch in debian/patches which contains the change in the CMakeLists.txt file or should the file be modified before repacking? Thanks, Gerber -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1338884843.24716.10.ca...@hamburg.upc.es
adding a new file using (d)quilt
Hi, for packaging freefoam-user-doc I intend to include the static file UsersGuide.pdf.gz as asymptote is currently broken. (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668286) Also, generating the manual pages for the freefoam package does not work for the moment as a2x from asccidoc does currently not work properly. The idea is to include these files statically (for the moment until mentioned packages have been repaired) using (d)quilt. But my workflow does not seems to work: dquilt new 'patch' dquilt add file dquilt refresh The patch only contains: Binary files /dev/null and b/doc/UserGuide/UserGuide.pdf.gz differ Resulting that it removes properly the file(s) when invoking 'dquilt pop', but is unable to recover them using 'dquilt push'. I also tried to 'touch file' in order to create an empty file first before adding to the patch, but this does not make any difference. In addition, this would probably cause a different checksum in upstream source compared with _orig.tar.bz2. What is the proper way to handle this? Thanks, Gerber -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1334227824.7358.35.ca...@delft.vdg.net
Re: RFS: freefoam
To Fernando Lemos: Its the --pedantic key that made the difference. Thanks for the hint. To Sylvestre Ledru: thanks for your remarks. I will have a look at them. I understand that all individual files (an amount of 12310, if counted correctly) will have to be reviewed manually. Is there some tool for checking files on licence automatically? Gerber On Fri, 2012-03-23 at 00:42 +0100, Sylvestre Ledru wrote: > Le vendredi 23 mars 2012 à 00:01 +0100, Sylvestre Ledru a écrit : > > Le jeudi 22 mars 2012 à 23:51 +0100, Gerber van der Graaf a écrit : > > > Dear mentors and members of the debian-science group, > [...] > > > > http://freefoam.sourceforge.net > > > The package can be found at: > > > http://mentors.debian.net/package/freefoam > > > and its .dsc is found at: > > > http://mentors.debian.net/debian/pool/contrib/f/freefoam/freefoam_0.1.0-1.dsc > > Could you consider moving this package in Debian Science ? > > See: > > http://debian-science.alioth.debian.org/debian-science-policy.html > > > > You would have to use the svn or the git repository provided by Debian > > Science. > Few things: > * Please improve the description... > * Please explicit in the description that freefoam is a fork of openfoam > (idem in the copyright file) > * Drop the useless comments in debian/rules > * Is it wanted contrib/ ? If yes, please describe the reason in > Debian.README > * What is the point of the content of README ? > * please follow the debian science policy regarding uploaders, > maintainer, vcs-*, etc > * the file copyright is not up to date at all, > cf ./src/OpenFOAM/db/IOstreams/gzstream/gzstream.h lgpl > ./src/OpenFOAM/primitives/random/BSD_random.c bsd > and some other gpl v3 > * please document the lintian overrides. > > Thanks > S > > -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1332538593.3184.4.camel@solo
Re: RFS: freefoam
Ah, I forgot to tell I also have created a git repo at debian/science: http://git.debian.org/?p=debian-science/packages/freefoam.git Gerber van der Graaf On Thu, 2012-03-22 at 23:51 +0100, Gerber van der Graaf wrote: > Dear mentors and members of the debian-science group, > I am looking for a sponsor for the FreeFOAM software of which the > following binary packages are build: > freefoam - programs for Computational Fluid Dynamics (CFD) > freefoam-dev-doc - software for Computational Fluid Dynamics -developers > documentation > freefoam-user-doc - software for Computational Fluid Dynamics - user > documentation > libfreefoam - libraries for Computational Fluid Dynamics (CFD) > libfreefoam-dev - libraries for Computational Fluid Dynamics (CFD) - > development files > > During the building on my box, the packages appeared to be lintian error > free. Though, some warning / error messages showed up on the mentors > site where the packages can be found, which I have commented. The > packages build correctly in a pbuilder environment and can be found at: > he URL of the home site is at: > http://freefoam.sourceforge.net > The package can be found at: > http://mentors.debian.net/package/freefoam > and its .dsc is found at: > http://mentors.debian.net/debian/pool/contrib/f/freefoam/freefoam_0.1.0-1.dsc > > Gerber van der Graaf -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1332457857.4471.24.camel@solo
packaging using cmake using external modules
Hi, I am working on the DEB packaging of FreeFOAM (http://freefoam.wiki.sourceforge.net/) that uses the CMake building system. In order to build some tools for making the output readable in Paraview, it uses find_package () which searches for a complete building tree of Paraview which also includes ParaViewConfig.cmake. Paraview is available in Debian, but does not provide ParaViewConfig.cmake. Manually building of the Paraview modules in FreeFOAM by pointing to the build tree of Paraview works fine. But in order to get DEB packages of FreeFOAM, the building will also have to be done automatically, under pbuilder for example. How to deal with this? I already have reported a bug against paraview to include ParaViewConfig.cmake, but wonder if that will do the trick. Thanks in forward, Gerber -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: simultaneous installation lib and lib-mpi
A start has been made already some time ago with this. See Debian bug #521221 libhdf5-openmpi-1.6.6-0: simultaneous installation of -serial and -mpi packages Gerber On Thu, 2009-04-30 at 10:11 +0200, Francesco P. Lovergine wrote: > On Sun, Apr 26, 2009 at 08:19:20PM +0200, Magnus Holmgren wrote: > > On torsdagen den 26 februari 2009, Gerber van der Graaf wrote: > > > I came across this problem when packaging my own libgpiv3 / libgpiv-mpi3 > > > (recently accepted and uploaded). These libraries are used by the other > > > packages gpivtools / gpivtools-mpi from a single upstream source (not > > > yet available on Deb). When testing the packaging of gpivtools(-mpi) > > > with pbuilder it only can be done if libgpiv3 and libgpiv-mpi3 are to be > > > installed simultaneously. Otherwise the building of one of the packages > > > gpivtools / gpivtools-mpi is impossible. > > > > > > While working on the packaging of gpivtools(-mpi) I am getting across a > > > similar problem with other libraries that are available in seriel and > > > -mpi (libhdf5-serial-dev libhdf5-openmpi-dev to be more specific). Only > > > one of these can be installed at once. As I also work with Paraview, > > > which depends on libhdf5-openmpi, packaging and the use of gpivtools > > > (that depends on libhdf5-dev) is impossible. (It is preferred to have > > > the dependancy on libhdf5-dev, even in gpivtools-mpi as the .h5 files > > > are quite small and don't need to be stored/retrieved in parallel way.) > > > > > > My question is why isn't it possible to package such libraries in a way > > > they can be installed simultaneously? Am I doing something wrong here? > > > If not, a suggestion might be to provide this possibility by filing a > > > 'feature request' bug against all -mpi libraries. If this really is a > > > weak point in packaging such libs, shouldn't it become a formal > > > packaging policy? > > > > There are more examples, such as cyrus-sasl2, which contains two Kerberos > > GSSAPI modules, one using MIT Kerberos 5 and one using Heimdal. But because > > those libraries can't be installed simultaneously, there is a separate > > source > > package, cyrus-sasl2-heimdal, with a copy of the upstream tarball, which > > only > > builds the Heimdal module packages. Currently I don't think there is any > > other solution to this problem, and solving it "for real" would require > > rather serious changes to how packages are built, but it might still be > > meaningful to bring it up on -devel, which I've done now. > > > > The best reasonable solution is convincing upstream to build rather different > lib names and sonames for each case. That would imply that all people > depending on the mpi lib flavor should change their library names. Providing > the same kind of implementation in our distribution is a viable possibility, > but diverged by upstream: that should be done in the library package, while > the serial and mpi -dev packages still should retain the same names (and > conflict each other). This is what I will implement for the HDF5 case. > > -- > Francesco P. Lovergine > > signature.asc Description: This is a digitally signed message part
simultaneous installation lib and lib-mpi
Maybe I am not on the correct lists here, but I have a question / remark concerning packaging and the use of a library that is provided in different tastes, like a seriel and Message Passing Interface (MPI) one. I came across this problem when packaging my own libgpiv3 / libgpiv-mpi3 (recently accepted and uploaded). These libraries are used by the other packages gpivtools / gpivtools-mpi from a single upstream source (not yet available on Deb). When testing the packaging of gpivtools(-mpi) with pbuilder it only can be done if libgpiv3 and libgpiv-mpi3 are to be installed simultaneously. Otherwise the building of one of the packages gpivtools / gpivtools-mpi is impossible. While working on the packaging of gpivtools(-mpi) I am getting across a similar problem with other libraries that are available in seriel and -mpi (libhdf5-serial-dev libhdf5-openmpi-dev to be more specific). Only one of these can be installed at once. As I also work with Paraview, which depends on libhdf5-openmpi, packaging and the use of gpivtools (that depends on libhdf5-dev) is impossible. (It is preferred to have the dependancy on libhdf5-dev, even in gpivtools-mpi as the .h5 files are quite small and don't need to be stored/retrieved in parallel way.) My question is why isn't it possible to package such libraries in a way they can be installed simultaneously? Am I doing something wrong here? If not, a suggestion might be to provide this possibility by filing a 'feature request' bug against all -mpi libraries. If this really is a weak point in packaging such libs, shouldn't it become a formal packaging policy? Just my thought, -- Gerber van der Graaf http://gpiv.sourceforge.net GnuPG key fingerprint: BF0A BBFE 5623 9761 C9E1 7C82 8B08 F586 D39A 2B64 signature.asc Description: This is a digitally signed message part
RFS: pygpiv
Sorry, I meshed the "RFS: pygpiv" mail up a bit. The complete info is as follows: I am looking for a sponsor for my package "pygpiv". * Package name: pygpiv Version : 1.0.0-1 Upstream Author : Gerber van der Graaf <[EMAIL PROTECTED]> * URL : http://libgpiv.sourceforge.net/pygpiv.html * License : GNU Section : python It builds these binary packages: python-gpiv - wrapper of libgpiv The package appears to be lintian clean and also went through pbuilder without problems. The upload would fix these bugs: 507894 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pygpiv - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pygpiv/pygpiv_1.0.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards Gerber van der Graaf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: pygpiv
Dear mentors, I am looking for a sponsor for my package "pygpiv". * Package name: pygpiv Version : 1.0.0-1 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : python It builds these binary packages: python-gpiv - wrapper of libgpiv The package appears to be lintian clean and also went through pbuilder without problems. The upload would fix these bugs: 507894 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pygpiv - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pygpiv/pygpiv_1.0.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards Gerber van der Graaf signature.asc Description: This is a digitally signed message part
Re: bits/news from the users of Debian?
Hi, Why using Debian and not another distro? Its a voluntary project without comercial interests. I like this philosophy and it seems to function quite well regarding its quality and as Debian is the mother of many other distros. I would like to see some more software concerning the topics I am working on. My main activitities are on heat transfer and fluid mechanics problems. Mostly to laboratory experimental techniques, but also on Computational Fluid Dynamics (CFD, i.e. computer simulations of heat and fluid flows). I already have made some contributions to Open Source Software and Debian as I am upstream developer of Gpiv c.s., of which I also have submitted the debian packages (Unfortunately, no sponsor found for new upstream release). Since recently I am also working with the OpenFoam software, a CFD package. I think it would be a good idea to have this software in Debian as well. Compiling and installing of this package is very complex and therefore a large amount of mails at the forums of this software is dedicated to the installation. The building system seems to be quite old and may need an upgrade, like with cmake, before it might be possible to debianize the software. Also the package includes other, third party software that is already in Debian (like openmpi) or somebody is working on it (paraview). These should be removed from the upstream source. Because of time restrictions I'd prefer to work on my own (upstream and debian packages) Gpiv c.s and to start with the debianizing OpenFoam than going through a NM process. Hopefully there will be DD's who are willing to upload these packages, because it is very frustrating to do a big efford which finally turns out is not appreciated. Thanks, Gerber -- developer of Gpiv: software for Particle Image Velocimetry URL: http:/gpiv.sourceforge.net GnuPG fingerprint: BF0A BBFE 5623 9761 C9E1 7C82 8B08 F586 D39A 2B64 signature.asc Description: This is a digitally signed message part
Re: RFS: libgpiv, gpiv and gpivtools
Thanks, I will have a look there, as well. Gerber On Thu, 2008-04-10 at 11:50 +0800, Paul Wise wrote: > On Wed, Apr 9, 2008 at 11:24 PM, Gerber van der Graaf > <[EMAIL PROTECTED]> wrote: > > > I am looking for a sponsor of the following packages. Older packages of > > this software are already in Debian. It concerns here new upstream > > releases: > > You might want to ask people on the science list, join the pkg-science > team and maintain the package collaboratively there. > > http://lists.debian.org/debian-science/ > http://alioth.debian.org/projects/pkg-science > > -- > bye, > pabs > > http://wiki.debian.org/PaulWise > > signature.asc Description: This is a digitally signed message part
RFS: libgpiv, gpiv and gpivtools
Dear mentors, I am looking for a sponsor of the following packages. Older packages of this software are already in Debian. It concerns here new upstream releases: Package: libgpiv-0.5.2 URL: http://libgpiv.sourceforge.net It builds the binary packages: libgpiv3, libgpiv3-dev: Description: Library for Particle Image Velocimetry (PIV) and libgpiv3-doc: Description: Documentation for libgpiv3 The package can be found on mentors.debian.net: http://mentors.debian.net/debian/pool/main/l/libgpiv The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/l/libgpiv/libgpiv_0.5.2-1.dsc Package: gpiv-0.5.2 URL: http://gpiv.sourceforge.net It builds the binary package: gpiv Description: Graphic User Interface program for Particle Image Velocimetry The package can be found on mentors.debian.net: http://mentors.debian.net/debian/pool/main/g/gpiv The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/g/gpiv/gpiv_0.5.2-1.dsc Package: gpivtools-0.5.2 URL: http://gpivtools.sourceforge.net It builds the binary package: gpivtools Description: Command line programs for Particle Image Velocimetry The package can be found on mentors.debian.net: http://mentors.debian.net/debian/pool/main/g/gpivtools The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/g/gpivtools/gpivtools_0.5.2-1.dsc The packages are lintian clean and are properly build and installed under a clean system, using pbuilder. I would be glad if someone could upload these packages for me. Kind regards, Gerber van der Graaf -- developer of Gpiv: software for Particle Image Velocimetry URL: http:/gpiv.sourceforge.net signature.asc Description: This is a digitally signed message part
Re: change bug# for ITP bug of WNPP package
Thanks for the reply. I'll just sit and wait until I will notice its accepted or rejetced. Gerber On Thu, 2006-04-27 at 10:45 -0400, Justin Pryzby wrote: > On Thu, Apr 27, 2006 at 03:19:29PM +0200, Gerber van der Graaf wrote: > > About one week ago my mentor uploaded my package libgpiv. As I don't > > find it yet on the debian repository, I have been looking if the ITP bug > > has been closed. This seems not to be the case, yet. > Do you know http://ftp-master.debian.org/new.html, where I see that it > is waiting? > > > The ITP bug reports version 0.3.2, but the upstream version (that has > > been packaged by me) has been increased to version 0.3.3. (I am the > > upstream developer as well. I have increased the version in upstream in > > order to implement all the changes in source that were needed, so > > the .diff only includes debian/ and .orig.tar.gz is equal to upstream > > tar.gz). > Changes which are not Debian specific, if I understand correctly? Yes, it concerns only bug repair-patches for the upstream source. These have been included in the new 0.3.3 upstream release before I packaged the software for debian. > > > My question is if this is this an error that will have to be repaired in > > order to get the debian package uploaded by ftp-master in the repository > > and close this bug? If so, can I change the bug report to version 0.3.3 > > or will I have to send a new bugreport, resulting into a new bug number > > and, therefore, have to change debian/changelog and re-upload the > > debianized package? > Don't worry about the version in the ITP bug, probably nobody will > ever look at it ever :) > > When you next upload the package, you'll have to have a different > .diff.gz, with less stuff in it, because that stuff has already been > patched (AIUI). > > Justin > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
change bug# for ITP bug of WNPP package
About one week ago my mentor uploaded my package libgpiv. As I don't find it yet on the debian repository, I have been looking if the ITP bug has been closed. This seems not to be the case, yet. The ITP bug reports version 0.3.2, but the upstream version (that has been packaged by me) has been increased to version 0.3.3. (I am the upstream developer as well. I have increased the version in upstream in order to implement all the changes in source that were needed, so the .diff only includes debian/ and .orig.tar.gz is equal to upstream tar.gz). My question is if this is this an error that will have to be repaired in order to get the debian package uploaded by ftp-master in the repository and close this bug? If so, can I change the bug report to version 0.3.3 or will I have to send a new bugreport, resulting into a new bug number and, therefore, have to change debian/changelog and re-upload the debianized package? Thanks in advance, Gerber -- URL http://gpiv.sourceforge.net Main Gpiv developer: software for Particle Image Velocimetry pnupg key id: ID D39A2B64 signature.asc Description: This is a digitally signed message part
Re: RFS: tnef -- Tool to unpack MIME application/ms-tnef attachments
I recently had a similar problem with my package libgpiv2; the differences between upstram .tar.gz and .orig.tar.gz., I think , is due to the differences in the root direcory names. Programs/scripts like dh_make create a new directory 'name.orig' if you start to debianize an upstream package from scratch. During building the package the name.orig is packed into name.orig.tar.gz. The md5check sum's of the CONTENTS of upstream and progname-version.orig were identic, but the md5check sum's of tar.gz and orig.tar.gz FILES were different. The only remedy against this is to rename the name.tar.gz (from upstream) to name.orig.tar.gz before you start building the package. Maybe there should be filed a bug against dh_make for this? Gerber -- Main developer of G[ov c.s.; software for Particle Image Velocimetry http://gpiv.sourceforge.net public key: D39A2B64 signature.asc Description: This is a digitally signed message part
Re: /etc/conf not installed
Excellent: --purge solved the problem. Thanks a lot. Gerber -- URL http://gpiv.sourceforge.net Main Gpiv developer: software for Particle Image Velocimetry pnupg key id: ID D39A2B64 signature.asc Description: This is a digitally signed message part
/etc/conf not installed
I am trying to repair the libgpiv package I've build. The libgpiv_0.3.2-1_i386.deb contains a configuration file /etc/gpiv.conf, as reported by dpkg -c. Extracting the .deb to tmpdir/ (with dpkg -x) gives tmpdir/etc/gpiv.conf, as expected. However, dpkg --install .deb or installing with: "apt-get install libgpiv" (after uploading in a local repository) does not install this file. On the other side, /usr/lib/libgpiv.so is perfectly installed. The gpiv.conf file is pointed by debian/libgpiv.files. I also tried to include it in debian/conffiles, in order to warn in case of an upgrade. Can somebody give me a hint where I have to look at or to search for in order to repair this bug? Thanks, Gerber -- URL http://gpiv.sourceforge.net Main Gpiv developer: software for Particle Image Velocimetry pnupg key id: ID D39A2B64 signature.asc Description: This is a digitally signed message part
Re: RFS: libgpiv
On Mon, 2006-03-13 at 21:53 +0100, Christoph Haas wrote: > Hi, Gerber... > > On Monday 13 March 2006 21:10, Gerber van der Graaf wrote: > > I just uploaded a repaired package to the debian-mentors repository > > after I got some comments from the previous one. The packages are linda > > and lintian error free. Lintian issued two warning messages: > > "source: package-uses-deprecated-debhelper-compat-version 3" > > "package-name-doesnt-match-sonames libgpiv2". I don't know what these > > warnings mean and if they're important. > > Kind of. "debhelper" delivers dh_install and other dh_* tools that you use > in your debian/rules file. Most packages still depend on version 4 of > debhelper. A while ago debhelper 5 has been released. You are using the > version 3 which is deprecated. Bump up the version to 5 and test if your > build still works. Hint: DH_COMPAT in debian/rules. > > "zless /usr/share/doc/debhelper/changelog.gz" gives you detailed > information on the changes to "debhelper". Or "man 7 debhelper". OK, I will update this > > > As the previous package was not uploaded to the formal Debian repository > > by a DD, I did not increase the package number. So, its still an initial > > release which also closes the ITP BUG I reported against this package. > > Is this correct behaviour? > > It's okay. But your debian/changelog file appears to have a superfluous > linebreak and a missing blank line. Try "cat" on it to see what I mean. > > > I perfectly understand that there is very little chance that there is a > > DD who might be interested in this software. > > Not necessarily. I sometimes sponsor software that I don't use myself. For > me it's more important that I can verify that your package works (e.g. I'm > not a "cdbs" guru and prefer "debhelper"-based packages like yours). > Libraries are a bit more complicated unless I have an application that > uses it which I can click and torture and test. I will upload soon new packages Gpivtools; > 40 command line programs and scripts and Gpiv; a Gtk/Gnome GUI program. These programs use libgpiv. Both new packages have been tested as well with pbuilder on Sid. To test the software you will need specific data. For this (PIV) technology it concerns a pair of two images. How to provide them? I might upload one image pair to the upstream URL (i.e. sourforge) or include them in the package. To me, the last option seems a bit a waist of bandwidth as every download from Debian then will downlaod this example image pair, whether needed by the user or not. > > > Even though, I kindly ask whether a DD will sponsor the package. > > Sure. But please tell us more about the package. See other RFS reports as a > template. I didn't notice your previous posts here about libgpiv so at > least I have missed it. > > > Though I am the developer of the software as well, > > the packaging has been kept separated from the upstream source packages > > available at http://gpiv.sourceforge.net > > Very good. Shipping a debian/ directory with your distribution leads to > more problems most of the time. The only location where you need it is for > the debian package. And users can get that from the Debian repositories. > So no need to include it. > > > Description: Library for Particle Image Velocimetry (PIV) > > This library contains functions for evaluating images from a fluid > > flow by means of Particle Image Velocimetry (PIV), resulting into a > > velocity field on a rectangular grid. It includes the core functions > > for image acquiring, processing, interrogation, PIV data validation, > > post-processing, input/output and memory allocation. > > > > Thanks a lot in forward, > > Further notes: > - Why debian/Makefile? Where do you use it? It is an acccidently left-over; previously the debian directory was included in the upstream sources. From this mailing list I learnd its better not to do so. I will clean it up. > - Since you are the upstream author: why is gpiv.1 in debian and not > generally installed by your software? It's probably not Debian-specific. > - Your debian/watch seems to be b0rked. Running "uscan" I get warnings > and errors. > - My "pbuilder" fails to build the package: > > checking for GPIV_UI_LIBS... > configure: error: The pkg-config script could not be found or is too old. > Make sure it > is in your PATH or set the PKG_CONFIG environment variable to the full > path to pkg-config. As this is a package that was not tested with pbuilder. The new one will be uploaded very soon; it has already been tested. I will acknowledge by a sending separate RFS for the new Gpiv and Gpivtools packages. > > Anyway, thanks for your contribution. > > Kindly > Christoph > -- > ~ > ~ > ".signature" [Modified] 1 line --100%--1,48 All > signature.asc Description: This is a digitally signed message part
RFS: libgpiv
Hi, I just uploaded a repaired package to the debian-mentors repository after I got some comments from the previous one. The packages are linda and lintian error free. Lintian issued two warning messages: "source: package-uses-deprecated-debhelper-compat-version 3" "package-name-doesnt-match-sonames libgpiv2". I don't know what these warnings mean and if they're important. The package has been builded on Sid and dependancies have been checked with pbuilder. As the previous package was not uploaded to the formal Debian repository by a DD, I did not increase the package number. So, its still an initial release which also closes the ITP BUG I reported against this package. Is this correct behaviour? I perfectly understand that there is very little chance that there is a DD who might be interested in this software. Even though, I kindly ask whether a DD will sponsor the package. The software is unique in its kind and will definitely help its users to install it on the wide range of architecture Debian is supporting. So, please, give me some help, feedback and an upload. Though I am the developer of the software as well, the packaging has been kept separated from the upstream source packages available at http://gpiv.sourceforge.net Description: Library for Particle Image Velocimetry (PIV) This library contains functions for evaluating images from a fluid flow by means of Particle Image Velocimetry (PIV), resulting into a velocity field on a rectangular grid. It includes the core functions for image acquiring, processing, interrogation, PIV data validation, post-processing, input/output and memory allocation. Thanks a lot in forward, -- Gerber van der Graaf Main developer of Gpiv: Open Source Software for Particle Image Velocimetry http://gpiv.sourceforge.net pnupg key id: ID D39A2B64 signature.asc Description: This is a digitally signed message part
RFS libgpiv , gpivtools and gpiv
Hi, I am looking for a sponsor for the packages libgpiv, gpiv and gpivtools I recently uploaded to the debian-mentors repository. The packages are linda and lintian error free. Please, can some DD have a look at it? As the packages are mainly interesting for scientific and engineering purposes, the audience is quite limited. But nevertheless I think it might help users a lot if this software would be included in Debian. Building from source seems to be complicated for many users as the packages depend on quite a few libraries. Though I am the developer of the software as well, the packaging has been kept separated from the upstream source packages available at http://gpiv.sourceforge.net The description for the libgpiv package is: Description: Library for Particle Image Velocimetry (PIV) This library contains functions for evaluating images from a fluid flow by means of Particle Image Velocimetry (PIV), resulting into a velocity field of the fluid flow. It includes the core functions for interrogation, data validation, post-processing, input/output and memory allocation. for the gpivtools package: Description: Command line programs for Particle Image Velocimetry A collection of programs for recording and interrogating images that are generated during a Particle Image Velocimetry (PIV) experiment. This is a technique to obtain the velocity field of a fluid flow quantitatively and is performed by tracking tracer particles that have been seeded to a fluid. The technique is also applied for observing deformations at surfaces of (solid) bodies. The package contains: . an image recording program that uses an IEEE1394 (Firewire) IIDC-compliant camera and a program for triggering the camera with a light source (mostly a double cavity Nd-YAG laser). Trigger pulses are sent over the parallel port of the computer using RealTimeLinux and RTAI. . an image processing program for typical filtering and manipulation routines that may be convenient for PIV. . an image interrogation program resulting into estimators of particle image displacements. . validation programs to test on outliers, peak-locking effect and velocity gradients. . post-processing programs for data manipulation (flipping, rotation etc), spatial and time scaling, calculation of spatial averages and derivatived quantities from the PIV data, like vorticity and strain. . miscelaneous programs and scripts to perform image format conversion, batch-processing, pipeline processing (image evaluation, validation and post-processing at once), calculation of time averages from a series of PIV data sets, data-visualization and data-manipulation. and for the gpiv package: Description: Graphic Interface program for Particle Image Velocimetry Gpiv is a graphic program using the the GTK/GNOME libraries for Particle Image Velocimetry (PIV). The program gives a quick overview of the parameter settings of the processes and allows to change them easely, running the processes, individually or in a chain, visualizes and displays the results. The processes that may be invoked by Gpiv are: . Image recording and triggering of a camera with light sources. . Image evaluation or interrogation, resulting into estimators of particle image displacements. . Data validation to test on outliers, peak-locking effect and velocity gradients over the interrogation area's. . Data post-processing: data manipulation,spatial and time scaling to obtain a velocity field from the PIV data, calculation of spatial averages, vorticity and strain. I am looking forward that these packages will be included in the Debian distribution. So please, let somebody sponsor me. Thanks, Gerber van der Graaf Main developer of Gpiv: Open Source Software for Particle Image Velocimetry http://gpiv.sourceforge.net pnupg key id: ID D39A2B64 signature.asc Description: This is a digitally signed message part
main, contrib, non-free
I recently uploaded some packages (Libgpiv_0.3.1, Gpivtools_0.3.1 and Gpiv_0.2.1) to mentors.debian.net with dupload. It seemed that everything went fine. But to me surprise they have been put in the contrib repository, instead of main. How is the choice of repository controlled, automatically or by human intervention? As far as I do know, and which is also the intention, this software and all libraries it depends on is free and resident in the main repository. So it should be put in main, not? Will it affect the RFC process? If, so, may these packages be moved or re-uploaded to main? Thanks, Gerber signature.asc Description: This is a digitally signed message part
debian-mentors@lists.debian.org
I am searching for a sponsor for the Libgpiv, Gpivtools and Gpiv packages I have developed and would like to see included in Debian. The home pages of the software can be found at: http://gpiv.sourceforge.net. The packages can be obtained from http://mentors.debian.net/ The software provides the analyzing of images for Particle Image Velocimetry (PIV). Software for this (research and production) technology is not included in any Linux distro, yet. The features, quality and performances of Gpiv s.s. are very competitive compared to other existing, Open Source, free-ware and commercial software for PIV. The popularity of this technique is still increasing but, for starters, the initial costs are high because of hard and software to be needed. Experienced users are often searching for alternatives of their commercial program after some time as it becomes obsolete for the analysing of the images. Thanks, Gerber van der Graaf -- http://gpiv.sourceforge.net pnupg key id: ID D39A2B64 public key at: http://pgpkeys.mit.edu signature.asc Description: This is a digitally signed message part
RFS Gpiv c.s.
ty and strain. The (debianized) source packages can be obtained from at respectively: https://sourceforge.net/project/showfiles.php?group_id=85208&package_id=88102&release_id=309946 https://sourceforge.net/project/showfiles.php?group_id=85224&package_id=88126&release_id=309959 https://sourceforge.net/project/showfiles.php?group_id=85227&package_id=88129&release_id=309962 4) Additional help is needed for a fourth package GPIVTRIG that concerns a kernel module using RTAI. This can be found at: https://sourceforge.net/project/showfiles.php?group_id=85208&package_id=88102&release_id=309946 The main web page of this project is found at: http://gpiv.sourceforge.net Eventually, I can send compiled packages, including .changes and .dsc directly by email. (.diff and -orig.tar.gz do not exist as the upstream source packages have been developed by me.) Motivation to include it in Debian -- Regarding the number of participants (23) of the PIV-challenge project (http://www.pivchallenge.org/), known free-ware and Open Source projects (about 5 to 6), there are about 30 PIV software programs around for this technique. A few manufactures who are selling (closed-source) software at high rates (order of magnitude EU 10.000,-) only work on the other (MS-WIN) operating systems. A few (three to four) Open Source projects for this technique exist as well. Most of these (except one or two) are using commercial software like Matlab. None of these Open source projects are included in any Linux distribution. The Gpiv c.s is the only Open Source project that also includes the recording of images and the controlling of camera and light source (mostly this are Nd-Yag lasers). As far as I know, only commercial software provide this service, apart from Gpiv c.s. I would like to see this software included in the Debian distribution for several reasons: - PIV now exists for about 20 years. Its popularity is very large and is still increasing. Estimated from the number of conference visitors for this and related techniques, there are about 2000 research groups working with it. So, there is a potential market for Gpiv c.s. - PIV is expensive because of the needed hard and software. This project might be a help for aspirant users to reduce initial costs. - PIV technology is still improving and new technologies are published almost monthly. For experimentalists already using PIV during a some time (4 to 5 years) their commercial software is mostly only used for retrieving the data. The technique to interrogate the images becomes obsolete and need to be upgraded or searched for alternatives. Also here, Gpiv c.s. might pop in for these users. - Debian is running on many different hardware architectures, which not only provides a large freedom of choice for (aspirant) Gpiv c.s. users, but also would be advantageous for these packages as the analyzing processes are high-performance demanding, that even may need a (Beowulf) cluster of computers. - Including Gpiv c.s. will be good advertising for Debian in the world of technical and scientific research, (not only for fluid mechanics but also for material sciences PIV is applied), and probably also in areas of chemical (and mechanical) construction and processing industry. Actually, some advertising for the Debian project has already been done in this context by expressing my hope that the Gpiv c.s. will once be included in the Debian distro during my talk "Presentation of an open source software for PIV" at the Seventh SIG32 & Pivnet workshop: Lisbon July 9-10 2004 (http://www.univ-lille1.fr/pivnet/sig32/lisbon2004/announcement_Lisbon04.html). So, don't let me down, please - I prefer Debian because of its open source and open-minded mentality and philosophy in order to provide a high-quality, non-commercial driven distribution. - Due to my experiences with Debian and the packaging system, I discovered that Debian has a lot to offer. To my opinion, it is easy to maintain and technically the best under the Linux distributions. This is my way to give something back. Sincerely, Gerber van der Graaf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
