FS#17724 - [iptables] 1.4.6 - /etc/conf.d/iptables should be added to backup=() directive

Attached to Project: Arch Linux
Opened by Alexander Drozdov (adrozdov) - Wednesday, 06 January 2010, 14:35 GMT
Last edited by Ronald van Haren (pressh) - Wednesday, 17 February 2010, 09:45 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Low
Priority Normal
Reported Version 2009.08
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

After upgrade iptables up to 1.4.6 my network stop to work, some research give me, that directive IPTABLES_FORWARD in /etc/conf.d/iptables sets to zero, but I set it to 1.

I think, that this is good idea to move this file to backup=() directive in PKGBUILD to prevent automatic changes.
This task depends upon

Closed by  Ronald van Haren (pressh)
Wednesday, 17 February 2010, 09:45 GMT
Reason for closing:  Works for me
Comment by Ronald van Haren (pressh) - Wednesday, 06 January 2010, 18:04 GMT
Did I make a typo adding it to the backup line? I'm sure I've added it there.
Comment by Valentin Saikov (xlin) - Thursday, 07 January 2010, 19:56 GMT
Yes. Please correct a mistake. The network has stopped and many times have been spent while has found in what business.
Comment by Ronald van Haren (pressh) - Thursday, 07 January 2010, 20:20 GMT
I looked it over, seems to work fine here (i.e. pacsave is created when removing iptables). What is happening here is the default pacman behavior as far as I can see.

from the pacman manpage:

original=X, current=X, new=Y
The current file is the same as the original but the new one differs. Since the user did
not ever modify the file, and the new one may contain improvements or bugfixes, install
the new file.

Loading...