Your message dated Tue, 31 Jan 2023 17:18:37 +0100 with message-id <87o7qeekyq.fsf@lusus> and subject line Re: shorewall: overwrite /etc/default/shorewall on update has caused the Debian Bug report #930431, regarding shorewall: overwrite /etc/default/shorewall on update 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 930431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930431 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: shorewall Version: 5.0.15.6-1 Severity: normal Dear Maintainer, * What led up to the situation? Update of the shorewall using apt upgrade * What exactly did you do (or not do) that was effective (or ineffective)? # apt update # apt upgrade * What was the outcome of this action? /etc/default/shorewall was overwritten and startup=1 was replaced with the startup=0 * What outcome did you expect instead? /etc/default/shorewall should not be overwritten! -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages shorewall depends on: ii bc 1.06.95-9+b3 ii debconf [debconf-2.0] 1.5.61 ii iproute2 4.9.0-1+deb9u1 ii iptables 1.6.0+snapshot20161117-6 ii lsb-base 9.20161125 ii perl 5.24.1-3+deb9u5 ii shorewall-core 5.0.15.6-1 Versions of packages shorewall recommends: pn libnetfilter-cthelper0 <none> Versions of packages shorewall suggests: pn make <none> pn shorewall-doc <none> -- Configuration Files: /etc/default/shorewall changed: startup=1 OPTIONS="" STARTOPTIONS="" RELOADOPTIONS="" RESTARTOPTIONS="" INITLOG=/dev/null SAFESTOP=0 /etc/shorewall/shorewall.conf changed: STARTUP_ENABLED=Yes VERBOSITY=1 PAGER= FIREWALL= BLACKLIST_LOG_LEVEL= INVALID_LOG_LEVEL= LOG_BACKEND= LOG_MARTIANS=Yes LOG_VERBOSITY=2 LOGALLNEW= LOGFILE=/var/log/messages LOGFORMAT="Shorewall:%s:%s:" LOGTAGONLY=No LOGLIMIT= MACLIST_LOG_LEVEL=info RELATED_LOG_LEVEL= RPFILTER_LOG_LEVEL=info SFILTER_LOG_LEVEL=info SMURF_LOG_LEVEL=info STARTUP_LOG=/var/log/shorewall-init.log TCP_FLAGS_LOG_LEVEL=info UNTRACKED_LOG_LEVEL= ARPTABLES= CONFIG_PATH="${CONFDIR}/shorewall:${SHAREDIR}/shorewall" GEOIPDIR=/usr/share/xt_geoip/LE IPTABLES= IP= IPSET= LOCKFILE= MODULESDIR= NFACCT= PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin" PERL=/usr/bin/perl RESTOREFILE=restore SHOREWALL_SHELL=/bin/sh SUBSYSLOCK="" TC= ACCEPT_DEFAULT=none DROP_DEFAULT=Drop NFQUEUE_DEFAULT=none QUEUE_DEFAULT=none REJECT_DEFAULT=Reject RCP_COMMAND='scp ${files} ${root}@${system}:${destination}' RSH_COMMAND='ssh ${root}@${system} ${command}' ACCOUNTING=Yes ACCOUNTING_TABLE=filter ADD_IP_ALIASES=No ADD_SNAT_ALIASES=No ADMINISABSENTMINDED=Yes AUTOCOMMENT=Yes AUTOHELPERS=Yes AUTOMAKE=No BASIC_FILTERS=No BLACKLIST="NEW,INVALID,UNTRACKED" CHAIN_SCRIPTS=Yes CLAMPMSS=No CLEAR_TC=Yes COMPLETE=No DEFER_DNS_RESOLUTION=Yes DELETE_THEN_ADD=Yes DETECT_DNAT_IPADDRS=No DISABLE_IPV6=No DOCKER=No DONT_LOAD= DYNAMIC_BLACKLIST=Yes EXPAND_POLICIES=Yes EXPORTMODULES=Yes FASTACCEPT=No FORWARD_CLEAR_MARK= HELPERS= IGNOREUNKNOWNVARIABLES=No IMPLICIT_CONTINUE=No INLINE_MATCHES=No IPSET_WARNINGS=Yes IP_FORWARDING=On KEEP_RT_TABLES=No LOAD_HELPERS_ONLY=Yes MACLIST_TABLE=filter MACLIST_TTL= MANGLE_ENABLED=Yes MAPOLDACTIONS=No MARK_IN_FORWARD_CHAIN=No MINIUPNPD=No MODULE_SUFFIX=ko MULTICAST=No MUTEX_TIMEOUT=60 NULL_ROUTE_RFC1918=No OPTIMIZE=0 OPTIMIZE_ACCOUNTING=No REJECT_ACTION= REQUIRE_INTERFACE=No RESTART=restart RESTORE_DEFAULT_ROUTE=Yes RESTORE_ROUTEMARKS=Yes RETAIN_ALIASES=No ROUTE_FILTER=Yes SAVE_ARPTABLES=No SAVE_IPSETS=No TC_ENABLED=Internal TC_EXPERT=No TC_PRIOMAP="2 3 3 3 2 3 1 1 2 2 2 2 2 2 2 2" TRACK_PROVIDERS=No TRACK_RULES=No USE_DEFAULT_RT=Yes USE_PHYSICAL_NAMES=No USE_RT_NAMES=No VERBOSE_MESSAGES=Yes WARNOLDCAPVERSION=Yes WORKAROUNDS=No ZERO_MARKS=No ZONE2ZONE=- BLACKLIST_DISPOSITION=DROP INVALID_DISPOSITION=CONTINUE MACLIST_DISPOSITION=REJECT RELATED_DISPOSITION=ACCEPT RPFILTER_DISPOSITION=DROP SMURF_DISPOSITION=DROP SFILTER_DISPOSITION=DROP TCP_FLAGS_DISPOSITION=DROP UNTRACKED_DISPOSITION=CONTINUE TC_BITS= PROVIDER_BITS= PROVIDER_OFFSET= MASK_BITS= ZONE_BITS=0 -- debconf information: shorewall/major_release: shorewall/dont_restart: shorewall/invalid_config:
--- End Message ---
--- Begin Message ---Hi, On Wed, Jun 12, 2019 at 04:23:13PM +0200, Sergey Spiridonov wrote: > # apt update > # apt upgrade > > /etc/default/shorewall was overwritten and startup=1 was replaced with > the startup=0 /etc/default/shorewall is marked as a conffile by the package, so it can't have been overwritten in this way without confirmation. Or maybe you have a misconfigured conffile management tool, like ucf? Either way, I don't think there's anything wrong with the package and there's nothing more to do here. If you can reproduce such an issue with the current version of shorewall, please reopen. Thanks, -- Romain Francoise <[email protected]> https://people.debian.org/~rfrancoise/
--- End Message ---
