Package: heimdal-clients
Version: 0.6.3-8
Severity: minor

rsh.1.gz should use the alternatives mechanism, just like the ftp and
telnet manpages. Otherwise, update-alternatives removes it, which
causes, among other things, reportbug to complain about package integrity
problems.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages heimdal-clients depends on:
ii  krb5-config           1.6                Configuration files for Kerberos V
ii  libasn1-6-heimdal     0.6.3-8            Libraries for Heimdal Kerberos
ii  libc6                 2.3.2.ds1-20       GNU C Library: Shared libraries an
ii  libdb4.2              4.2.52-18          Berkeley v4.2 Database Libraries [
ii  libedit2              2.9.cvs.20040827-1 BSD editline and history libraries
ii  libgssapi1-heimdal    0.6.3-8            Libraries for Heimdal Kerberos
ii  libhdb7-heimdal       0.6.3-8            Libraries for Heimdal Kerberos
ii  libhesiod0            3.0.2-15.1         Libraries for hesiod, a service na
ii  libkadm5clnt4-heimdal 0.6.3-8            Libraries for Heimdal Kerberos
ii  libkadm5srv7-heimdal  0.6.3-8            Libraries for Heimdal Kerberos
ii  libkafs0-heimdal      0.6.3-8            Libraries for Heimdal Kerberos
ii  libkrb-1-kerberos4kth 1.2.2-11.1         Kerberos Libraries for Kerberos4 F
ii  libkrb5-17-heimdal    0.6.3-8            Libraries for Heimdal Kerberos
ii  libncurses5           5.4-4              Shared libraries for terminal hand
ii  libotp0-kerberos4kth  1.2.2-11.1         Otp Libraries for Kerberos4 From K
ii  libroken16-kerberos4k 1.2.2-11.1         Roken Libraries for Kerberos4 From
ii  libsl0-kerberos4kth   1.2.2-11.1         Sl Libraries for Kerberos4 From KT
ii  libssl0.9.7           0.9.7e-3           SSL shared libraries

-- no debconf information


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

Reply via email to