Your message dated Thu, 22 Nov 2018 11:00:14 +0100
with message-id <5b2e1751-46cd-f193-d4c3-241a157e1...@debian.org>
and subject line Bug fixed
has caused the Debian Bug report #914074,
regarding ln: failed to create symbolic link '/sbin/iptables': File exists
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 ow...@bugs.debian.org
immediately.)
--
914074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iptables
Version: 1.8.2-1
Severity: serious
Justification: not installable
Setting up iptables (1.8.2-1) ...
ln: failed to create symbolic link '/sbin/iptables': File exists
dpkg: error processing package iptables (--configure):
installed iptables package post-installation script subprocess returned error
exit status 1
-- System Information:
Debian Release: buster/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
Versions of packages iptables depends on:
ii libc6 2.27-8
ii libip4tc0 1.8.2-1
ii libip6tc0 1.8.2-1
ii libiptc0 1.8.2-1
ii libmnl0 1.0.4-2
ii libnetfilter-conntrack3 1.0.7-1
ii libnfnetlink0 1.0.1-3+b1
ii libnftnl7 1.1.1-1
ii libxtables12 1.8.2-1
iptables recommends no packages.
Versions of packages iptables suggests:
ii kmod 25-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: unmerge -1
Control: fixed -1 1.8.2-2
This bug is different from #914129, unmerging now.
Also, this bug is fixed by iptables 1.8.2-2, so closing it now as well.
--- End Message ---
