Your message dated Sat, 18 Nov 2006 19:51:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Closing bug #397153
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: shorewall
Version: 3.2.4-1
Severity: serious
"shorewall start" simply displays:
ERROR: Startup is disabled
Reading the source, I can see a reference to a new STARTUP_ENABLED
option in shorewall.conf. This is not documented in
releasenotes.txt.gz.
This variable would appear to make startup=1 in /etc/default/shorewall
superfluous.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages shorewall depends on:
ii debconf [debconf-2.0] 1.5.6 Debian configuration management sy
ii iproute 20060323-1 Professional tools to control the
ii iptables 1.3.5.0debian1-1 Linux kernel 2.4+ iptables adminis
Versions of packages shorewall recommends:
ii wget 1.10.2-2 retrieves files from the web
-- debconf information:
shorewall/upgrade_20_22:
shorewall/upgrade_14_20:
shorewall/upgrade_to_14:
shorewall/warnrfc1918:
shorewall/warn_about_klogd_floods:
shorewall/dont_restart:
* shorewall/major_release: true
--- End Message ---
--- Begin Message ---
The bug reported is not really present in the package.
-- lm
--- End Message ---
