Your message dated Sat, 29 Dec 2012 11:17:29 +0000
with message-id <[email protected]>
and subject line Bug#696130: fixed in ferm 2.1-5
has caused the Debian Bug report #696130,
regarding 2.1-4 upgrade error "Died at /usr/sbin/ferm line 1719"
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.)


-- 
696130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696130
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ferm
Version: 2.1-4
Severity: important


Upgrade to 2.1-4 dies with an error about stopping ferm. The firewall is left running, but the ferm scripts are already in place and future manual or automatic operations fail with the message "Died at /usr/sbin/ferm line 1719".

By commenting out that line in /usr/sbin/ferm I can get a slightly more useful, but still incorrect error message about mis-matched "}". The actual problem turned out to be the config block was starting with "domain (ip ip6) table filter {...}" to specify rules shared by both IPv4 and IPv6 firewalls.

This "domain (ip ip6)" syntax appears not to be a problem when used in the main ferm.conf file, and is valid. But the new version errors out with the above problems when it is used in a sub-include file.

Workaround was to cut-n-paste a blocks of config file into "domain ip ..." and "domain ip6 ..." blocks. Or to move the domain stanza outside the include file. Both of which can be problematic when the config files are under different administrative jurisdictions or automatically generated.
--- End Message ---
--- Begin Message ---
Source: ferm
Source-Version: 2.1-5

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

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.
Alexander Wirt <[email protected]> (supplier of updated ferm 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.8
Date: Sat, 29 Dec 2012 11:30:56 +0100
Source: ferm
Binary: ferm
Architecture: source all
Version: 2.1-5
Distribution: unstable
Urgency: low
Maintainer: Alexander Wirt <[email protected]>
Changed-By: Alexander Wirt <[email protected]>
Description: 
 ferm       - maintain and setup complicated firewall rules
Closes: 696130
Changes: 
 ferm (2.1-5) unstable; urgency=low
 .
   * [f4e216a] Backport a fix from 2.1.2 which fixes a regression from the
               domain (ip ip6) fix introduced in 2.1.1 (backported to 2.1-4)
               (Closes: #696130)
Checksums-Sha1: 
 347d659afc3f605dfa50ad73338ef3e3de271ce2 1025 ferm_2.1-5.dsc
 fde96827e4882b8656794ac4b817039dcea7d08a 15771 ferm_2.1-5.diff.gz
 93a3ab9a72915ce62e2923d5bb6d1a8a52899672 111432 ferm_2.1-5_all.deb
Checksums-Sha256: 
 2d1ffaa5f3c0727c7781284e5430cb6f9a961affc7f698f9464ec11483b0cc3a 1025 
ferm_2.1-5.dsc
 1272ae2dffe0562d88b0183cb477e236f2a44e57f258a7ee897a424a205f74e1 15771 
ferm_2.1-5.diff.gz
 d59577e79db24470efef3ff8159f02594581d6fa4f03812fc3ce4cf2d9bd0c93 111432 
ferm_2.1-5_all.deb
Files: 
 ccdbcf24b7d96e77663f4825380b5cf4 1025 net optional ferm_2.1-5.dsc
 5afce671be9850008782ecfe82fb283b 15771 net optional ferm_2.1-5.diff.gz
 e5ca21091a20a6963c7dc3979b3ffe23 111432 net optional ferm_2.1-5_all.deb

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

iEYEARECAAYFAlDezocACgkQ01u8mbx9AgphaACeMqsIOFSWUF+2bxgFTK+Go0jN
748AoJkTK3M66G+l3eskztG7vDUDiMML
=LcAs
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to