Your message dated Sat, 06 Jan 2007 22:02:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#388037: fixed in stun 0.96.dfsg-4
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: stun
Version: 0.96.dfsg-1
Severity: normal

Hello

We're only using the stun client binary on one system to use it for
monitoring purposes. When installing it we ran into two problems:

a) The package seems uninstallable without modifications:
        Setting up stun (0.96.dfsg-1) ...
        No primary IP given. Exiting.
        invoke-rc.d: initscript stun, action "start" failed.
        dpkg: error processing stun (--configure):
        subprocess post-installation script returned error exit status 1
   I would consider this a bug, every package should be installable
   without error messages. Could be solved by the solution proposed for
   b), too.

b) As we only need the client-binary and splitting client and server
   would probably be overkill something like the following would be
   good in /etc/defaults/stun
        # Change this from /bin/true to /usr/sbin/stun enables the Server
        DAEMON=/bin/true

bye,

-christian-

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.17.6-fc4-westend2
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to de_DE)

Versions of packages stun depends on:
ii  libc6                 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii  libstdc++2.10-glibc2. 1:2.95.4-22        The GNU stdc++ library

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: stun
Source-Version: 0.96.dfsg-4

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

stun_0.96.dfsg-4.diff.gz
  to pool/main/s/stun/stun_0.96.dfsg-4.diff.gz
stun_0.96.dfsg-4.dsc
  to pool/main/s/stun/stun_0.96.dfsg-4.dsc
stun_0.96.dfsg-4_i386.deb
  to pool/main/s/stun/stun_0.96.dfsg-4_i386.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.
Kilian Krause <[EMAIL PROTECTED]> (supplier of updated stun 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: Sat,  6 Jan 2007 22:53:52 +0100
Source: stun
Binary: stun
Architecture: source i386
Version: 0.96.dfsg-4
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team <[EMAIL PROTECTED]>
Changed-By: Kilian Krause <[EMAIL PROTECTED]>
Description: 
 stun       - Server daemon and test client for STUN
Closes: 388037
Changes: 
 stun (0.96.dfsg-4) unstable; urgency=low
 .
   * Fix startup again. (Closes: #388037)
Files: 
 e58855228b3e99a1c450a8e62e48ea33 763 net optional stun_0.96.dfsg-4.dsc
 2a50bd5db76dff2769de467dae972448 4869 net optional stun_0.96.dfsg-4.diff.gz
 55eccb6b38dee65af730ff2ecad4ec1d 38396 net optional stun_0.96.dfsg-4_i386.deb

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

iD8DBQFFoBtOvdkzt4X+wX8RAgP3AJ9shpl2/2xwWeXTystAcejyodcbiACfYBpv
zkvNRzEYiEX9b8ajZwxfzx0=
=CiBv
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to