Your message dated Tue, 15 Aug 2006 09:17:33 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#383136: fixed in remctl 2.0-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: libremctl-dev
Severity: serious
Version: 2.0-1

Hi

Your package is not installable as it depends on libkrb53-dev which is
not available in unstable. You might want to update the dependency to
libkrb5-dev instead...

Cheers

Luk

-- 
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint:   D5AF 25FB 316B 53BB 08E7   F999 E544 DE07 9B7C 328D

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: remctl
Source-Version: 2.0-2

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

libremctl-dev_2.0-2_i386.deb
  to pool/main/r/remctl/libremctl-dev_2.0-2_i386.deb
libremctl1_2.0-2_i386.deb
  to pool/main/r/remctl/libremctl1_2.0-2_i386.deb
remctl-client_2.0-2_i386.deb
  to pool/main/r/remctl/remctl-client_2.0-2_i386.deb
remctl-server_2.0-2_i386.deb
  to pool/main/r/remctl/remctl-server_2.0-2_i386.deb
remctl_2.0-2.diff.gz
  to pool/main/r/remctl/remctl_2.0-2.diff.gz
remctl_2.0-2.dsc
  to pool/main/r/remctl/remctl_2.0-2.dsc
remctl_2.0-2_all.deb
  to pool/main/r/remctl/remctl_2.0-2_all.deb



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Russ Allbery <[EMAIL PROTECTED]> (supplier of updated remctl 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 [EMAIL PROTECTED])


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

Format: 1.7
Date: Tue, 15 Aug 2006 09:04:44 -0700
Source: remctl
Binary: remctl-server libremctl1 remctl-client libremctl-dev remctl
Architecture: source i386 all
Version: 2.0-2
Distribution: unstable
Urgency: low
Maintainer: Russ Allbery <[EMAIL PROTECTED]>
Changed-By: Russ Allbery <[EMAIL PROTECTED]>
Description: 
 libremctl-dev - Development files for Kerberos-authenticated command execution
 libremctl1 - Library for Kerberos-authenticated command execution
 remctl     - Kerberos-authenticated command execution (transitional package)
 remctl-client - Client for Kerberos-authenticated command execution
 remctl-server - Server for Kerberos-authenticated command execution
Closes: 383136
Changes: 
 remctl (2.0-2) unstable; urgency=low
 .
   * The development package for MIT Kerberos is libkrb5-dev, not
     libkrb53-dev.  Thanks, Luk Claes.  (Closes: #383136)
Files: 
 dcb7c0cfef59e93b5f08fe77d69b5b12 617 net optional remctl_2.0-2.dsc
 6b0b8adc98b26276e49b8a1b207040c6 5753 net optional remctl_2.0-2.diff.gz
 d1c9f13c56ac1e8fb25e540a68510ab6 19528 libs optional libremctl1_2.0-2_i386.deb
 9548db0350cb8f5abe6b39aec9f8cc6f 22520 libdevel extra 
libremctl-dev_2.0-2_i386.deb
 43f2b4c14394309a1755d2197245d698 47480 net optional 
remctl-client_2.0-2_i386.deb
 8a43df3d9c88dfa04540139c05be0839 54554 net optional 
remctl-server_2.0-2_i386.deb
 336c3b662fe93274295c6d6d703efd2d 3670 net extra remctl_2.0-2_all.deb

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

iD8DBQFE4fHA+YXjQAr8dHYRAq0EAJ9WH11yWvSZYh21mkh51p+HVihgwgCgmbAY
ccDxfn/iF7qoyGWvMyyn6R0=
=7D0J
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to