http://bugzilla.novell.com/show_bug.cgi?id=525048 Summary: SuSEfirewall2 upgrade hosed by firewall config Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1.1 Firefox/3.0.11 Upgrading SuSEfirewall2 recently hosed by firewall config. I'm pretty sure it's fillup, actually, but altering my firewall config (and breaking it in the process) did not make me happy. Basically, on 100% of the boxes I've upgraded, I've got various configs which stretch across more than one line. Like this: SOME_FIREWALL_DIRECTIVE="blah blah blah more blah blah blah more blah blah blah" As part of the upgrade, this got turned into: SOME_FIREWALL_DIRECTIVE="blah blah blah ## Type: string more blah blah blah more blah blah blah" which of course doesn't work. Why did this happen? Previously I've also tried things like this: SOME_FIREWALL_DIRECTIVE="blah blah blah" SOME_FIREWALL_DIRECTIVE="$SOME_FIREWALL_DIRECTIVE more blah blah blah" SOME_FIREWALL_DIRECTIVE="$SOME_FIREWALL_DIRECTIVE more blah blah blah" but that, too, sometimes falls apart with upgrades. Since these files are sh-compatible, why aren't the upgrade scripts and processes (fillup) shell compatible in their parsing, or am I pointing the blame incorrectly. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.