Bug 9694 - 3_b4: User's shorewall rules removed during drakxtools updates
Summary: 3_b4: User's shorewall rules removed during drakxtools updates
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-11 05:08 CEST by Bit Twister
Modified: 2017-01-24 08:59 CET (History)
3 users (show)

See Also:
Source RPM: drakx-net
CVE:
Status comment:

Attachments
rules before update (2.23 KB, text/plain)
2013-04-11 05:10 CEST, Bit Twister 		Details
rules after update (1.28 KB, text/plain)
2013-04-11 05:11 CEST, Bit Twister 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2013-04-11 05:08:33 CEST 
Description of problem:
Lines containing variables are removed from /etc/shorewall/* files during drakxtools updates.

Version-Release number of selected component (if applicable):


How reproducible: Always.


Steps to Reproduce:
1. Create lines in /etc/shorewall/rules with variables.
2. urpmi --auto --auto-update
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Bit Twister 2013-04-11 05:10:41 CEST 
Created attachment 3732 [details]
rules before update
Comment 2 Bit Twister 2013-04-11 05:11:26 CEST 
Created attachment 3733 [details]
rules after update
Manuel Hiebel 2013-04-11 10:55:09 CEST

CC: (none) => mageia
Assignee: bugsquad => thierry.vignaud
Summary: 3_b4: User's shorewall rules removed during updates => 3_b4: User's shorewall rules removed during drakxtools updates

Marcin Ch 2013-04-14 19:10:32 CEST

CC: (none) => chmielu1_a

Bit Twister 2014-01-18 16:37:45 CET

CC: (none) => junknospam

Comment 3 Thierry Vignaud 2015-05-19 14:24:19 CEST 
Wrong package

Source RPM: drakxtools => drakx-net

Comment 4 Bit Twister 2017-01-24 08:59:39 CET 
I have not seen the problem in release 6 cauldron.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.