Bug 25360 - syntax error in /usr/libexec/iptables.init
Summary: syntax error in /usr/libexec/iptables.init
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
: 25366 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-08-26 13:30 CEST by eric gerbier
Modified: 2019-09-06 23:10 CEST (History)
3 users (show)

See Also:
Source RPM: iptables-1.8.2-5.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description eric gerbier 2019-08-26 13:30:33 CEST 
Description of problem:
In syslog file, I have an error :
/usr/libexec/iptables.init: ligne 35: rep : commande introuvable

and the line looks strange. If I compare with a mageia 6 ,  the unknown "rep" command is "fgrep".

If I replace "rep" by "fgrep", I do not have any more error

Version-Release number of selected component (if applicable):
iptables-1.8.2-5.mga7

How reproducible:
every time

Steps to Reproduce:
1.
2.
3.
Comment 1 eric gerbier 2019-08-26 13:46:40 CEST 
and If compare with the script for ipv6 ( /usr/libexec/ip6tables.init )
the "rep" is replaced by "grep"
Comment 2 Thomas Backlund 2019-08-26 17:54:27 CEST 
Thanks for the report, I've pushed  iptables-1.8.2-5.1.mga7 to testing with this fixed

CC: (none) => tmb
Assignee: bugsquad => tmb

Comment 3 Thomas Backlund 2019-08-26 19:47:35 CEST 

And the rpm list for QA:



SRPMS:
iptables-1.8.2-5.1.mga7.src.rpm

i586:
iptables-1.8.2-5.1.mga7.i586.rpm
iptables-nft-1.8.2-5.1.mga7.i586.rpm
libip4tc0-1.8.2-5.1.mga7.i586.rpm
libip4tc-devel-1.8.2-5.1.mga7.i586.rpm
libip6tc0-1.8.2-5.1.mga7.i586.rpm
libip6tc-devel-1.8.2-5.1.mga7.i586.rpm
libipq0-1.8.2-5.1.mga7.i586.rpm
libipq-devel-1.8.2-5.1.mga7.i586.rpm
libiptables12-1.8.2-5.1.mga7.i586.rpm
libiptables-devel-1.8.2-5.1.mga7.i586.rpm
libiptc0-1.8.2-5.1.mga7.i586.rpm
libiptc-devel-1.8.2-5.1.mga7.i586.rpm

x86_64:
iptables-1.8.2-5.1.mga7.x86_64.rpm
iptables-nft-1.8.2-5.1.mga7.x86_64.rpm
lib64ip4tc0-1.8.2-5.1.mga7.x86_64.rpm
lib64ip4tc-devel-1.8.2-5.1.mga7.x86_64.rpm
lib64ip6tc0-1.8.2-5.1.mga7.x86_64.rpm
lib64ip6tc-devel-1.8.2-5.1.mga7.x86_64.rpm
lib64ipq0-1.8.2-5.1.mga7.x86_64.rpm
lib64ipq-devel-1.8.2-5.1.mga7.x86_64.rpm
lib64iptables12-1.8.2-5.1.mga7.x86_64.rpm
lib64iptables-devel-1.8.2-5.1.mga7.x86_64.rpm
lib64iptc0-1.8.2-5.1.mga7.x86_64.rpm
lib64iptc-devel-1.8.2-5.1.mga7.x86_64.rpm

Assignee: tmb => qa-bugs

Comment 4 Thomas Backlund 2019-08-28 13:02:24 CEST 
*** Bug 25366 has been marked as a duplicate of this bug. ***

CC: (none) => mageia

Comment 5 Thomas Backlund 2019-08-31 16:20:15 CEST 
@eric gerbier: have you tested this update ?
Comment 6 eric gerbier 2019-09-03 13:38:44 CEST 
I have tested the update (on another laptop), and all seems ok for me
Thomas Backlund 2019-09-06 20:45:53 CEST

Keywords: (none) => advisory, validated_update
Whiteboard: (none) => MGA7-64-OK
CC: (none) => sysadmin-bugs

Comment 7 Mageia Robot 2019-09-06 23:10:51 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2019-0117.html

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