Debian Bug report logs - #420638
ITP: mpich2 -- an implementation of the Message-Passing Interface (MPI)

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Muammar Wadih El Khatib Rodriguez" <muammarelkhatib@gmail.com>

To: submit@bugs.debian.org

Subject: ITP: an implementation of the Message-Passing Interface (MPI)

Date: Mon, 23 Apr 2007 13:47:52 -0400

Package: wnpp
Severity: wishlist
Owner: Muammar El Khatib <muammarelkhatib@gmail.com>

* Package name      : mpich2
Version                 : 1.0.5p4
Upstream Author   : Argonne National Laboratory Group
* URL                     : http://www-unix.mcs.anl.gov/mpi/mpich2/index.htm
* License                : Copyright Notice + 2002 University of Chicago [1]
Description           : an implementation of the Message-Passing
Interface (MPI)

Citing the homepage:

<snip>

The goals of MPICH2 are to provide an MPI implementation for important
platforms, including clusters, SMPs, and massively parallel
processors. It also provides a vehicle for MPI implementation research
and for developing new and better parallel programming environments.

</snip>


For more information see the oficial web site.

[1] http://www-unix.mcs.anl.gov/mpi/mpich2/license.htm
-- 
Muammar El Khatib.
Linux user: 403107.
Key fingerprint = 90B8 BFC4 4A75 B881 39A3  1440 30EB 403B 1270 29F1
http://muammarelkhatib.net | http://www.teorex.org
 ,''`.
: :' :
`. `'
  `-

Message #12 received at 420638-done@bugs.debian.org (full text, mbox, reply):

From: David Moreno Garza <damog@merkel.debian.org>

To: 420638-done@bugs.debian.org

Subject: WNPP bug closing

Date: Thu, 24 Apr 2008 11:59:41 -0600

Hello,

This is an automatic mail sent to close the ITP you have reported or 
are involved with.

Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

 reopen 420638
 stop

Further comments on the work done in the bug sent to
420638@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>.
 

Message #19 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Pavan Balaji <balaji@mcs.anl.gov>

Cc: pkg-scicomp-devel@lists.alioth.debian.org, 420638@bugs.debian.org, muammarelkhatib@gmail.com

Subject: Re: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Tue, 16 Jun 2009 07:41:13 +0200

On 15/06/09 at 16:32 -0500, Pavan Balaji wrote:
> Hello,
>
> I'm one of the developers of MPICH at Argonne National Laboratory. As  
> some of you might be aware, our current focus is mainly on the second  
> generation of MPICH, i.e., MPICH2. I noticed that currently Debian only  
> contains MPICH-1. So, we'd like to work closely with you guys to get  
> MPICH2 packaged into Debian as well. Would someone be able to help us  
> with this? I have contacted the package maintainer for MPICH-1, as well,  
> to find out what we need to do for this.

Hi Pavan,

I'm willing to help with that. How would you like to proceed? Do you
want to maintain the package yourself, and only need a sponsor or backup
maintainer, or do you want me to maintain the package and refer to you
for issues?

Also, there was an ITP (Intent to Package) bug opened about mpich2
(http://bugs.debian.org/420638) a long time ago. I'm Ccing the bug and
the submitter, since he might want to step in, and technically has
priority over packaging mpich2.
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #24 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Pavan Balaji <balaji@mcs.anl.gov>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Cc: pkg-scicomp-devel@lists.alioth.debian.org, 420638@bugs.debian.org, muammarelkhatib@gmail.com, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Tue, 16 Jun 2009 08:46:13 -0500

These emails seem to have been broken across two email chains; merging 
them here.

Lucas: thanks for offering to help. I don't have a preference with who 
packages MPICH2. Either you or Muammar, or if needed I can package it 
(though I might need some help if I'm doing it). Also, if either one of 
you wants to do it, I can help with source code issues and even absorb 
patches upstream for the upcoming 1.1.1 release, so the build goes 
through cleanly.

Muammar: since you have the priority on this, can you let us know how 
you want to proceed?

Thanks,

 -- Pavan

On 06/16/2009 12:41 AM, Lucas Nussbaum wrote:
> On 15/06/09 at 16:32 -0500, Pavan Balaji wrote:
>> Hello,
>>
>> I'm one of the developers of MPICH at Argonne National Laboratory. As  
>> some of you might be aware, our current focus is mainly on the second  
>> generation of MPICH, i.e., MPICH2. I noticed that currently Debian only  
>> contains MPICH-1. So, we'd like to work closely with you guys to get  
>> MPICH2 packaged into Debian as well. Would someone be able to help us  
>> with this? I have contacted the package maintainer for MPICH-1, as well,  
>> to find out what we need to do for this.
> 
> Hi Pavan,
> 
> I'm willing to help with that. How would you like to proceed? Do you
> want to maintain the package yourself, and only need a sponsor or backup
> maintainer, or do you want me to maintain the package and refer to you
> for issues?
> 
> Also, there was an ITP (Intent to Package) bug opened about mpich2
> (http://bugs.debian.org/420638) a long time ago. I'm Ccing the bug and
> the submitter, since he might want to step in, and technically has
> priority over packaging mpich2.

-- 
Pavan Balaji
http://www.mcs.anl.gov/~balaji

Message #29 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Muammar El Khatib <muammarelkhatib@gmail.com>

To: Pavan Balaji <balaji@mcs.anl.gov>

Cc: Lucas Nussbaum <lucas@lucas-nussbaum.net>, pkg-scicomp-devel@lists.alioth.debian.org, 420638@bugs.debian.org, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Wed, 17 Jun 2009 13:08:43 +1930

Hi,

On Wed, Jun 17, 2009 at 9:16 AM, Pavan Balaji<balaji@mcs.anl.gov> wrote:
>
> These emails seem to have been broken across two email chains; merging them
> here.
>
> Lucas: thanks for offering to help. I don't have a preference with who
> packages MPICH2. Either you or Muammar, or if needed I can package it
> (though I might need some help if I'm doing it). Also, if either one of you
> wants to do it, I can help with source code issues and even absorb patches
> upstream for the upcoming 1.1.1 release, so the build goes through cleanly.
>
> Muammar: since you have the priority on this, can you let us know how you
> want to proceed?
>

I have been working on it for some time. I started packaging it from
the work who other did (requesting his permission of using it
previously).

The package compiles, but it has a _bunch_ of lintian warnings. Look at them:

muammar@obey:~/src/main/libs/mpich2$ lintian -i mpich2_1.0.7-1_amd64.changes
W: mpich2 source: debian-watch-file-missing-version
N:
N:    The debian/watch file in this package doesn't start a version= line. The
N:    first non-comment line of debian/watch should be a version= declaration.
N:    This may mean that this is an old version one watch file that should be
N:    updated to the current version.
N:
N:    Refer to the uscan(1) manual page for details.
N:
N:    Severity: normal, Certainty: certain
N:
W: mpich2 source: debhelper-but-no-misc-depends mpich2
N:
N:    The source package uses debhelper but it does not use ${misc:Depends} in
N:    the given binary package's debian/control entry. This is required so the
N:    dependencies are set correctly in case the result of a call to any of
N:    the dh_ commands cause the package to depend on another package.
N:
N:    Refer to the debhelper(7) manual page for details.
N:
N:    Severity: normal, Certainty: certain
N:
W: mpich2 source: debhelper-but-no-misc-depends libmpich2-1.0-dev
W: mpich2 source: debhelper-but-no-misc-depends libmpich2-1.0
W: mpich2 source: debhelper-but-no-misc-depends mpich2-mpd
W: mpich2 source: debhelper-but-no-misc-depends mpich2-doc
W: mpich2 source: debhelper-but-no-misc-depends mpich2-mpe
E: mpich2 source: build-depends-on-obsolete-package build-depends: x-dev
N:
N:    The package build-depends on a package that has been superseded. If the
N:    superseded package is part of an ORed group, it should not be the first
N:    package in the group.
N:
N:    Severity: important, Certainty: possible
N:
E: mpich2 source: ancient-autotools-helper-file
src/mpi/romio/confdb/config.sub 2003-07-17
N:
N:    The referenced file has a time stamp older than year 2004 and the
N:    package does not build-depend on autotools-dev or automake and therefore
N:    apparently does not update it. This usually means that the source
N:    package will not build correctly on all currently released
N:    architectures.
N:
N:    Read /usr/share/doc/autotools-dev/README.Debian.gz (from the
N:    autotools-dev package) for information on how to fix this problem. cdbs
N:    will automatically update these files if autotools-dev is installed
N:    during build, but the build dependency on autotools-dev is still
N:    necessary.
N:
N:    Severity: important, Certainty: possible
N:
E: mpich2 source: ancient-autotools-helper-file
src/mpi/romio/confdb/config.guess 2003-07-02
W: mpich2 source: outdated-autotools-helper-file confdb/config.sub 2005-02-10
N:
N:    The referenced file has a time stamp older than June of 2006 and the
N:    package does not build-depend on autotools-dev or automake and therefore
N:    apparently does not update it. This usually means that the source
N:    package will not build correctly on AVR32, for which a Debian port is
N:    currently in progress, and may not support other newer architectures.
N:
N:    Read /usr/share/doc/autotools-dev/README.Debian.gz (from the
N:    autotools-dev package) for information on how to fix this problem. cdbs
N:    will automatically update these files if autotools-dev is installed
N:    during build, but the build dependency on autotools-dev is still
N:    necessary.
N:
N:    Severity: normal, Certainty: possible
N:
W: mpich2 source: outdated-autotools-helper-file confdb/config.guess 2005-03-24
W: libmpich2-1.0: non-dev-pkg-with-shlib-symlink
usr/lib/libfmpich.so.1.1 usr/lib/libfmpich.so
N:
N:    Although this package is not a "-dev" package, it installs a
N:    "libsomething.so" symbolic link referencing the corresponding shared
N:    library. When the link doesn't include the version number, it is used by
N:    the linker when other programs are built against this shared library.
N:
N:    Shared libraries are supposed to place such symbolic links in their
N:    respective "-dev" packages, so it is a bug to include it with the main
N:    library package.
N:
N:    However, if this is a small package which includes the runtime and the
N:    development libraries, this is not a bug. In the latter case, please
N:    override this warning.
N:
N:    Refer to Debian Policy Manual section 8.4 (Development files) for
N:    details.
N:
N:    Severity: normal, Certainty: possible
N:
W: libmpich2-1.0: non-dev-pkg-with-shlib-symlink
usr/lib/libmpich.so.1.1 usr/lib/libmpich.so
W: libmpich2-1.0: copyright-without-copyright-notice
N:
N:    The copyright file for this package does not appear to contain a
N:    copyright notice. You should copy the copyright notice from the upstream
N:    source (or add one of your own for a native package). A copyright notice
N:    must consist of Copyright, Copr., or the Unicode symbol of C in a circle
N:    followed by the years and the copyright holder. A copyright notice is
N:    not required for a work to be copyrighted, but Debian requires the
N:    copyright file include the authors and years of copyright, and including
N:    a valid copyright notice is the best way to do that.
N:
N:    If the package is in the public domain rather than copyrighted, be sure
N:    to mention "public domain" in the copyright file. Please be aware that
N:    this is very rare and not the same as a DFSG-free license. True public
N:    domain software is generally limited to such special cases as a work
N:    product of a United States government agency.
N:
N:    Refer to http://ftp-master.debian.org/REJECT-FAQ.html for details.
N:
N:    Severity: normal, Certainty: certain
N:
W: libmpich2-1.0: package-name-doesnt-match-sonames libfmpich1.1 libmpich1.1
N:
N:    The package name of a library package should usually reflect the soname
N:    of the included library. The package name can determined from the
N:    library file name with the following code snippet:
N:
N:     $ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n
-e's/^[[:space:]]*SONAME[[:space:]]*//p' | sed
-e's/\([0-9]\)\.so\./\1-/; s/\.so\.//'
N:
N:    Refer to Debian Library Packaging Guide chapter 5 (shared library
N:    packages) for details.
N:
N:    Severity: normal, Certainty: possible
N:
E: mpich2: non-standard-toplevel-dir examples/
N:
N:    The Filesystem Hierarchy Standard forbids the installation of new files
N:    or directories in the root directory.
N:
N:    Refer to Filesystem Hierarchy Standard (The Root Filesystem) for
N:    details.
N:
N:    Severity: important, Certainty: certain
N:
W: mpich2: file-in-unusual-dir examples/cpi
N:
N:    This file or symbolic link is in a directory where files are not
N:    normally installed by Debian packages.
N:
N:    Severity: normal, Certainty: certain
N:
W: mpich2: script-not-executable ./etc/mpich2/mpicc.conf
N:
N:    This file starts with the #! sequence that marks interpreted scripts,
N:    but it is not executable.
N:
N:    Severity: normal, Certainty: certain
N:
W: mpich2: script-not-executable ./etc/mpich2/mpicxx.conf
W: mpich2: script-not-executable ./etc/mpich2/mpif77.conf
W: mpich2: copyright-without-copyright-notice
W: mpich2: binary-or-shlib-defines-rpath ./examples/cpi
/home/muammar/src/main/libs/mpich2/mpich2-1.0.7/lib
N:
N:    The binary or shared library sets RPATH. This overrides the normal
N:    library search path, possibly interfering with local policy and causing
N:    problems for multilib, among other issues.
N:
N:    The only time a binary or shared library in a Debian package should set
N:    RPATH is if it is linked to private shared libraries in the same
N:    package. In that case, place those private shared libraries in
N:    /usr/lib/<package>. Libraries used by binaries in other packages should
N:    be placed in /lib or /usr/lib as appropriate, with a proper SONAME, in
N:    which case RPATH is unnecessary.
N:
N:    To fix this problem, look for link lines like:
N:        gcc test.o -o test -Wl,--rpath,/usr/local/lib
N:    or
N:        gcc test.o -o test -R/usr/local/lib
N:    and remove the -Wl,--rpath or -R argument. You can also use the chrpath
N:    utility to remove the RPATH.
N:
N:    Refer to http://wiki.debian.org/RpathIssue for details.
N:
N:    Severity: normal, Certainty: certain
N:
E: mpich2-mpe: non-standard-toplevel-dir src/
W: mpich2-mpe: file-in-unusual-dir src/mpe2/bin/clog2_print
W: mpich2-mpe: file-in-unusual-dir src/mpe2/include/mpe.h
W: mpich2-mpe: file-in-unusual-dir src/mpe2/include/mpe_graphics.h
W: mpich2-mpe: file-in-unusual-dir src/mpe2/include/mpe_graphicsf.h
W: mpich2-mpe: file-in-unusual-dir src/mpe2/include/mpe_log.h
W: mpich2-mpe: file-in-unusual-dir src/mpe2/include/mpe_logf.h
W: mpich2-mpe: file-in-unusual-dir src/mpe2/include/mpe_misc.h
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libampe.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/liblmpe.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libmpe.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libmpe_collchk.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libmpe_f2cmpi.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libmpe_nompi.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libmpe_nompi_null.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libmpe_null.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/libtmpe.a
W: mpich2-mpe: file-in-unusual-dir src/mpe2/lib/mpe_prof.o
W: mpich2-mpe: script-not-executable ./etc/mpich2/mpich2/mpicc.conf
W: mpich2-mpe: script-not-executable ./etc/mpich2/mpich2/mpicxx.conf
W: mpich2-mpe: script-not-executable ./etc/mpich2/mpich2/mpif77.conf
W: mpich2-mpe: script-not-executable ./etc/mpich2/mpich2/mpif90.conf
W: mpich2-mpe: copyright-without-copyright-notice
W: libmpich2-1.0-dev: copyright-without-copyright-notice
W: libmpich2-1.0-dev: wrong-section-according-to-package-name
libmpich2-1.0-dev => libdevel
N:
N:    This package has a name suggesting that it belongs to a section other
N:    than the one it is currently categorized in.
N:
N:    Severity: normal, Certainty: certain
N:
W: mpich2-doc: copyright-without-copyright-notice
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpd.py.1
N:
N:    Manual pages have to be installed compressed (using "gzip -9").
N:
N:    Refer to Debian Policy Manual section 12.1 (Manual pages) for details.
N:
N:    Severity: important, Certainty: certain
N:
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdallexit.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdboot.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdcheck.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdchkpyver.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdcleanup.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdexit.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdgdbdrv.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdhelp.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdkilljob.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdlib.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdlistjobs.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdman.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdringtest.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdsigjob.py.1
E: mpich2-mpd: manpage-not-compressed usr/share/man/man1/mpdtrace.py.1
W: mpich2-mpd: binary-without-manpage usr/bin/mpd
N:
N:    Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should
N:    have a manual page
N:
N:    Note that though the man program has the capability to check for several
N:    program names in the NAMES section, each of these programs should have
N:    its own manual page (a symbolic link to the appropriate manual page is
N:    sufficient) because other manual page viewers such as xman or tkman
N:    don't support this.
N:
N:    If the name of the man page differs from the binary by case, man may be
N:    able to find it anyway; however, it is still best practice to make the
N:    case of the man page match the case of the binary.
N:
N:    If the man pages are provided by another package on which this package
N:    depends, lintian may not be able to determine that man pages are
N:    available. In this case, after confirming that all binaries do have man
N:    pages after this package and its dependencies are installed, please add
N:    a lintian override.
N:
N:    Refer to Debian Policy Manual section 12.1 (Manual pages) for details.
N:
N:    Severity: normal, Certainty: possible
N:
W: mpich2-mpd: binary-without-manpage usr/bin/mpdallexit
W: mpich2-mpd: binary-without-manpage usr/bin/mpdboot
W: mpich2-mpd: binary-without-manpage usr/bin/mpdcheck
W: mpich2-mpd: binary-without-manpage usr/bin/mpdcleanup
W: mpich2-mpd: binary-without-manpage usr/bin/mpdexit
W: mpich2-mpd: binary-without-manpage usr/bin/mpdhelp
W: mpich2-mpd: binary-without-manpage usr/bin/mpdkilljob
W: mpich2-mpd: binary-without-manpage usr/bin/mpdlistjobs
W: mpich2-mpd: binary-without-manpage usr/bin/mpdringtest
W: mpich2-mpd: binary-without-manpage usr/bin/mpdroot
W: mpich2-mpd: binary-without-manpage usr/bin/mpdsigjob
W: mpich2-mpd: binary-without-manpage usr/bin/mpdtrace
W: mpich2-mpd: script-with-language-extension usr/bin/mpd.py
N:
N:    When scripts are installed into a directory in the system PATH, the
N:    script name should not include an extension such as .sh or .pl that
N:    denotes the scripting language currently used to implement it. The
N:    implementation language may change; if it does, leaving the name the
N:    same would be confusing and changing it would be disruptive.
N:
N:    Refer to Debian Policy Manual section 10.4 (Scripts) for details.
N:
N:    Severity: normal, Certainty: certain
N:
W: mpich2-mpd: script-with-language-extension usr/bin/mpdallexit.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdboot.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdcheck.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdchkpyver.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdcleanup.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdexit.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdgdbdrv.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdhelp.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdkilljob.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdlib.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdlistjobs.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdman.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdringtest.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdsigjob.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpdtrace.py
W: mpich2-mpd: script-with-language-extension usr/bin/mpiexec.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpd.py
N:
N:    Packages with Python scripts must depend on the package python. Those
N:    that have scripts executed with a versioned python package need a
N:    dependency on the equivalent version of python.
N:
N:    For example, if a script in the package uses #!/usr/bin/python, the
N:    package needs a dependency on "python". If a script uses
N:    #!/usr/bin/python2.5, the package need a dependency on "python2.5".
N:
N:    In some cases a weaker relationship, such as Suggests or Recommends,
N:    will be more appropriate.
N:
N:    Severity: important, Certainty: certain
N:
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdallexit.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdboot.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdcheck.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdchkpyver.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdcleanup.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdexit.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdgdbdrv.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdhelp.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdkilljob.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdlib.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdlistjobs.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdman.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdringtest.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdsigjob.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpdtrace.py
E: mpich2-mpd: python-script-but-no-python-dep ./usr/bin/mpiexec.py
W: mpich2-mpd: copyright-without-copyright-notice

OTOH, I think the debian/copyright file should be rechecked again. I
don't have any problem in giving the work I've done, let others
maintain MPICH2,  or co-maintain the package with debian-science. The
important thing is that there is people who is interested in maintain
it :). I'll upload what I have done in mentors.d.n so that you can
check it when you desire.

Regards,
-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 127029F1
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Message #34 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Muammar El Khatib <muammarelkhatib@gmail.com>

Cc: Pavan Balaji <balaji@mcs.anl.gov>, pkg-scicomp-devel@lists.alioth.debian.org, 420638@bugs.debian.org, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Wed, 17 Jun 2009 14:15:59 +0200

On 17/06/09 at 13:08 +1930, Muammar El Khatib wrote:
> OTOH, I think the debian/copyright file should be rechecked again. I
> don't have any problem in giving the work I've done, let others
> maintain MPICH2,  or co-maintain the package with debian-science. The
> important thing is that there is people who is interested in maintain
> it :). I'll upload what I have done in mentors.d.n so that you can
> check it when you desire.

OK, please upload to mentors. We could probably team-maintain it inside
debian-science or pkg-scicomp.
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #39 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Pavan Balaji <balaji@mcs.anl.gov>

To: Muammar El Khatib <muammarelkhatib@gmail.com>

Cc: Lucas Nussbaum <lucas@lucas-nussbaum.net>, pkg-scicomp-devel@lists.alioth.debian.org, 420638@bugs.debian.org, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Wed, 17 Jun 2009 08:35:02 -0500

Muammar, Lucas, and others,

>> Muammar: since you have the priority on this, can you let us know how you
>> want to proceed?
>>
> 
> I have been working on it for some time. I started packaging it from
> the work who other did (requesting his permission of using it
> previously).
> 
> The package compiles, but it has a _bunch_ of lintian warnings. Look 
> at them:

Thanks. Some of these warnings (e.g., confdb warnings about ancient 
files) should be fixed for 1.1, which went out a few weeks ago.

> E: mpich2 source: ancient-autotools-helper-file 
> src/mpi/romio/confdb/config.sub 2003-07-17

I'm not familiar with many of the below warnings, but some of these seem 
like they don't follow the debian naming convention:

> W: libmpich2-1.0: non-dev-pkg-with-shlib-symlink 
> usr/lib/libmpich.so.1.1 usr/lib/libmpich.so

Can you or someone else make a pass on the mpich2_1.0.7-1_amd64.changes 
changes file (is there an architecture independent one?) and see if some 
of these issues can be fixed? Btw, are these files put up online 
somewhere, so I can locally try them out as well?

I noticed that lintian also requires every installed binary to have a 
man page. I'll take care of that.

Thanks,

 -- Pavan

-- 
Pavan Balaji
http://www.mcs.anl.gov/~balaji

Message #44 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Muammar El Khatib <muammarelkhatib@gmail.com>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 420638@bugs.debian.org

Cc: Pavan Balaji <balaji@mcs.anl.gov>, pkg-scicomp-devel@lists.alioth.debian.org, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: Bug#420638: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Wed, 17 Jun 2009 22:00:40 -0400

On Thu, Jun 18, 2009 at 7:45 AM, Lucas Nussbaum<lucas@lucas-nussbaum.net> wrote:
> On 17/06/09 at 13:08 +1930, Muammar El Khatib wrote:
>> OTOH, I think the debian/copyright file should be rechecked again. I
>> don't have any problem in giving the work I've done, let others
>> maintain MPICH2,  or co-maintain the package with debian-science. The
>> important thing is that there is people who is interested in maintain
>> it :). I'll upload what I have done in mentors.d.n so that you can
>> check it when you desire.
>
> OK, please upload to mentors. We could probably team-maintain it inside
> debian-science or pkg-scicomp.

Fine, I have uploaded it. You can find it at:

http://mentors.debian.net/debian/pool/main/m/mpich2/mpich2_1.0.7-1.dsc

It would be nice If we team-maintain it, so that I can start learning
how to work on that way :)

Regards,
-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 127029F1
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Message #49 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Muammar El Khatib <muammarelkhatib@gmail.com>

Cc: 420638@bugs.debian.org, Pavan Balaji <balaji@mcs.anl.gov>, pkg-scicomp-devel@lists.alioth.debian.org, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: Bug#420638: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Thu, 18 Jun 2009 16:33:17 +0200

On 17/06/09 at 22:00 -0400, Muammar El Khatib wrote:
> On Thu, Jun 18, 2009 at 7:45 AM, Lucas Nussbaum<lucas@lucas-nussbaum.net> wrote:
> > On 17/06/09 at 13:08 +1930, Muammar El Khatib wrote:
> >> OTOH, I think the debian/copyright file should be rechecked again. I
> >> don't have any problem in giving the work I've done, let others
> >> maintain MPICH2,  or co-maintain the package with debian-science. The
> >> important thing is that there is people who is interested in maintain
> >> it :). I'll upload what I have done in mentors.d.n so that you can
> >> check it when you desire.
> >
> > OK, please upload to mentors. We could probably team-maintain it inside
> > debian-science or pkg-scicomp.
> 
> Fine, I have uploaded it. You can find it at:
> 
> http://mentors.debian.net/debian/pool/main/m/mpich2/mpich2_1.0.7-1.dsc
> 
> It would be nice If we team-maintain it, so that I can start learning
> how to work on that way :)

Would you have time to port it to mpich2 1.1, or should I take a look?
Basically, if you can do the packaging work, and I only do the
review/sponsoring, that would be perfect.

Do you want me to import your package into SVN? Do you have a preference
between debian-science and pkg-scicomp?
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #54 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Muammar El Khatib <muammarelkhatib@gmail.com>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Cc: 420638@bugs.debian.org, Pavan Balaji <balaji@mcs.anl.gov>, pkg-scicomp-devel@lists.alioth.debian.org, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: Bug#420638: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Fri, 19 Jun 2009 19:55:25 +1930

On Fri, Jun 19, 2009 at 10:03 AM, Lucas
Nussbaum<lucas@lucas-nussbaum.net> wrote:
> On 17/06/09 at 22:00 -0400, Muammar El Khatib wrote:
>> On Thu, Jun 18, 2009 at 7:45 AM, Lucas Nussbaum<lucas@lucas-nussbaum.net> wrote:
>> > On 17/06/09 at 13:08 +1930, Muammar El Khatib wrote:
>> >> OTOH, I think the debian/copyright file should be rechecked again. I
>> >> don't have any problem in giving the work I've done, let others
>> >> maintain MPICH2,  or co-maintain the package with debian-science. The
>> >> important thing is that there is people who is interested in maintain
>> >> it :). I'll upload what I have done in mentors.d.n so that you can
>> >> check it when you desire.
>> >
>> > OK, please upload to mentors. We could probably team-maintain it inside
>> > debian-science or pkg-scicomp.
>>
>> Fine, I have uploaded it. You can find it at:
>>
>> http://mentors.debian.net/debian/pool/main/m/mpich2/mpich2_1.0.7-1.dsc
>>
>> It would be nice If we team-maintain it, so that I can start learning
>> how to work on that way :)
>
> Would you have time to port it to mpich2 1.1, or should I take a look?
> Basically, if you can do the packaging work, and I only do the
> review/sponsoring, that would be perfect.
>

Yes, I would, but When I port it, If you desire, you can take a look, too.

> Do you want me to import your package into SVN? Do you have a preference
> between debian-science and pkg-scicomp?

Well, if you consider a good choice to import it into SVN, I am OK
with it. I don't have any preference so far, do you? Anyways, I have
read wiki pages of debian-science and pkg-scicomp, and the package
fits on both.

I am working on porting this now. When I have it ready, I'll send a mail.

Regards,
-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 127029F1
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Message #59 received at 420638@bugs.debian.org (full text, mbox, reply):

From: Muammar El Khatib <muammarelkhatib@gmail.com>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>

Cc: 420638@bugs.debian.org, Pavan Balaji <balaji@mcs.anl.gov>, pkg-scicomp-devel@lists.alioth.debian.org, hazelsct@debian.org, debian-science@lists.debian.org, camm@enhanced.com

Subject: Re: Bug#420638: [Pkg-scicomp-devel] MPICH2 in Debian

Date: Mon, 22 Jun 2009 11:53:38 -0400

Hi Lucas,

On Fri, Jun 19, 2009 at 7:55 PM, Muammar El
Khatib<muammarelkhatib@gmail.com> wrote:
>>
>> Would you have time to port it to mpich2 1.1, or should I take a look?
>> Basically, if you can do the packaging work, and I only do the
>> review/sponsoring, that would be perfect.
>>
>
> Yes, I would, but When I port it, If you desire, you can take a look, too.
>
>> Do you want me to import your package into SVN? Do you have a preference
>> between debian-science and pkg-scicomp?
>
> Well, if you consider a good choice to import it into SVN, I am OK
> with it. I don't have any preference so far, do you? Anyways, I have
> read wiki pages of debian-science and pkg-scicomp, and the package
> fits on both.
>
> I am working on porting this now. When I have it ready, I'll send a mail.
>

I have it almost ready. Please, check it.  If you see that something
is missing or have to be improved just let me know. The package can be
downloaded at: http://mentors.debian.net/debian/pool/main/m/mpich2/mpich2_1.1-1.dsc


Regards,
-- 
Muammar El Khatib.
Linux user: 403107.
GPG Key = 127029F1
http://muammar.me | http://proyectociencia.org
  ,''`.
 : :' :
 `. `'
   `-

Message #66 received at 420638-close@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: 420638-close@bugs.debian.org

Subject: Bug#420638: fixed in mpich2 1.2-1

Date: Sun, 18 Oct 2009 18:32:03 +0000

Source: mpich2
Source-Version: 1.2-1

We believe that the bug you reported is fixed in the latest version of
mpich2, which is due to be installed in the Debian FTP archive:

libmpich2-1.2_1.2-1_amd64.deb
  to pool/main/m/mpich2/libmpich2-1.2_1.2-1_amd64.deb
libmpich2-dev_1.2-1_amd64.deb
  to pool/main/m/mpich2/libmpich2-dev_1.2-1_amd64.deb
mpich2-doc_1.2-1_all.deb
  to pool/main/m/mpich2/mpich2-doc_1.2-1_all.deb
mpich2_1.2-1.diff.gz
  to pool/main/m/mpich2/mpich2_1.2-1.diff.gz
mpich2_1.2-1.dsc
  to pool/main/m/mpich2/mpich2_1.2-1.dsc
mpich2_1.2-1_amd64.deb
  to pool/main/m/mpich2/mpich2_1.2-1_amd64.deb
mpich2_1.2.orig.tar.gz
  to pool/main/m/mpich2/mpich2_1.2.orig.tar.gz



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 420638@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lucas Nussbaum <lucas@lucas-nussbaum.net> (supplier of updated mpich2 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 07 Oct 2009 23:11:42 +0200
Source: mpich2
Binary: mpich2 mpich2-doc libmpich2-1.2 libmpich2-dev
Architecture: source all amd64
Version: 1.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers <debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Lucas Nussbaum <lucas@lucas-nussbaum.net>
Description: 
 libmpich2-1.2 - Shared libraries for MPICH2
 libmpich2-dev - Development files for MPICH2
 mpich2     - Implementation of the MPI Message Passing Interface standard
 mpich2-doc - Documentation for MPICH2
Closes: 420638
Changes: 
 mpich2 (1.2-1) experimental; urgency=low
 .
   * Initial packaging. Closes: #420638
Checksums-Sha1: 
 386553a800a0b7b8a438032cc7a76155c305d063 1361 mpich2_1.2-1.dsc
 48502bf0acd6f877503b7f7756d51b63989e4fdd 17245392 mpich2_1.2.orig.tar.gz
 963c37b7354166b857a772aedb96a1e03dbdb489 15731 mpich2_1.2-1.diff.gz
 82b06f9f54f84571cb282118f2e38c3ae794ca17 1077298 mpich2-doc_1.2-1_all.deb
 c8df64c566c424807bacccde1dfba14cccdb3bdc 237368 mpich2_1.2-1_amd64.deb
 701705194df09dc5e289e61fa0e40b567b768799 794552 libmpich2-1.2_1.2-1_amd64.deb
 58e7cc3f944eae06fc7f45037b697abb46f73736 1031332 libmpich2-dev_1.2-1_amd64.deb
Checksums-Sha256: 
 8171785e8fbfb0641cb5cf28d56e7b252a0c1bc2ac3813e79e1b332da7cb49ad 1361 mpich2_1.2-1.dsc
 b9d6d830864a940eead0e48965e5258f07190446eb511c14f5d567b2acfcdf44 17245392 mpich2_1.2.orig.tar.gz
 9f3c6cf5673ca49124c0dc79dd37793ece7a0e096796c76f79358152f72325d2 15731 mpich2_1.2-1.diff.gz
 8eccc7e513e03c31617533436dab3c4f0ba0ecbc2a7c9a56a30bcf6a58870836 1077298 mpich2-doc_1.2-1_all.deb
 7d2b613b9da729fd1c5c34737376848eac1f9b60313f74e948fef7d43628c6e8 237368 mpich2_1.2-1_amd64.deb
 654539ce53aeff02ed161ce90813e4fd64b50a778846fd078ef69cb32e82503a 794552 libmpich2-1.2_1.2-1_amd64.deb
 8a7b1b8e159c1d956d0bb439c02ff39b62eb8bff2b73c083a163b541bb237b04 1031332 libmpich2-dev_1.2-1_amd64.deb
Files: 
 682b13929d7c207c18ba70ffe0daf438 1361 devel extra mpich2_1.2-1.dsc
 925c8792c8aacbfca1aceae94852d591 17245392 devel extra mpich2_1.2.orig.tar.gz
 a0e72fe3c5b6c9a6f7d45333ecae8793 15731 devel extra mpich2_1.2-1.diff.gz
 9545061519e1ce34b994445e9ac6f985 1077298 doc extra mpich2-doc_1.2-1_all.deb
 5039f887b574353cd90a21de21da056a 237368 devel extra mpich2_1.2-1_amd64.deb
 ec42c7352880c9bfa1fe5069da317de3 794552 libs extra libmpich2-1.2_1.2-1_amd64.deb
 a57392b042474e8d35699df00e44e644 1031332 libdevel extra libmpich2-dev_1.2-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFK2i8E2hliNwI7P08RAmxfAJ4vlZ0OHOsjorFChSJfGxxaKQCPlwCgy83W
GBIaxluTAZnmnbbxCXR0q+U=
=5mtt
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.