tags 292761 pending
thanks

Thank you for the report.

I don't believe this problem is present in 1.2.5.3-2 which was uploaded
on December 22 (but is still in the NEW queue).  Can you please check
that version of the packages?  You can find them in:
http://lyre.mit.edu/~powell/mpich/

-Adam

On Sat, 2005-01-29 at 15:23 +0000, Jochen Voss wrote:
> Package: mpich
> Version: 1.2.5.3-1.2
> Severity: normal
> File: /usr/bin/mpereconfig.mpich
> 
> Hello,
> 
> the mpich package contains a broken symlink:
> 
>     [EMAIL PROTECTED] [~] ls -l /usr/bin/mpereconfig.mpich
>     lrwxr-xr-x  1 root root 28 Jan 29 15:18 /usr/bin/mpereconfig.mpich -> 
> ../lib/mpich/bin/mpereconfig
>     [EMAIL PROTECTED] [~] ls -l /usr/lib/mpich/bin/mpe*
>     ls: /usr/lib/mpich/bin/mpe*: No such file or directory
> 
> I do not know what this program is supposed to do, but maybe
> it is just a typo:
> 
>     [EMAIL PROTECTED] [~] ls -l /usr/lib/mpich/bin/*reconfig
>     -rwxr-xr-x  1 root root 1864 Jan  5 11:29 /usr/lib/mpich/bin/mpireconfig*
> 
> mpireconfig instead of mpereconfig would exist.
> 
> I hope this helps,
> Jochen
> 
> -- System Information:
> Debian Release: 3.1
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Kernel: Linux 2.6.10
> Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
> 
> Versions of packages mpich depends on:
> ii  libc6                2.3.2.ds1-20        GNU C Library: Shared libraries 
> an
> ii  libmpich1.0          1.2.5.3-1.2         mpich runtime shared library
> ii  mpich-common         1.2.5.3-1.2         Manpages and other common files 
> fo
> ii  ssh [rsh-client]     1:3.8.1p1-8.sarge.4 Secure rlogin/rsh/rcp 
> replacement 
> 
> -- no debconf information
> 

-Adam
-- 
GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Welcome to the best software in the world today cafe!
http://www.take6.com/albums/greatesthits.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to