Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

According to the mirror I checked there is too a Cauldron.

A name change of a nominally changed release doesn't magically make a bug go away. And, one must do an installation to confirm the problem. I'm not going to do another installation simply to confirm a many years old bug when the bug owner hasn't done anything with it in the mere two weeks since it was filed.

Keywords: NEEDINFO => (none)
Version: Cauldron => 2

no worry, the ping was to a lot a bugs, but some exclude was missing (like exclude the recent bugs near to the release freeze)

1. Changing version to cauldron since we can't fix installer for released versions (that's what alphas and betas are for)
2. Is this bug still valid with latest installer? (Mageia 4 alpha 1 as of today)

Version: 2 => Cauldron

This is what's installed after unchecking the iptables and shorewall boxes doing HTTP install of x86_64 Cauldron from mirrors.us.kernel.org using 22 Aug. installation kernel and initrd from alt0, with all non-default installation source checkboxes checked:
iptables-1.4.20-1.mga4
lib64iptables10-1.4.20-1.mga4
lib64x264_133-0.133-0.20130823.stable.1.mga4.tainted
shorewall-4.5.10.1-5.mga4
shorewall-core-4.5.10.1-5.mga4
shorewall-ipv6-4.5.10.1-5.mga4

Subsequently running:
urpme iptables lib64iptables10 lib64x264_133
does not list shorewall-core among packages to be removed, and does list
lib64-alsa-plugins, and
lib64-avcodec55
among packages to be removed.

What do lib64-alsa-plugins and lib64-avcodec55 have to do with iptables or shorewall? Maybe this is why $SUMMARY?

Keywords: NEEDINFO => (none)

Ok, then this would be more a packaging issue than an installer issue. Let's see if alsa-plugins' maintainer has any insight to give us :)

Keywords: (none) => Triaged
Assignee: bugsquad => mageia
Source RPM: (none) => alsa-plugins

On rereading my comment 5, lib64x264_133 shouldn't have been listed, and therefore I shouldn't have tried urpme on it, which is what wanted to uninstall the two audio libs. The only relationship between iptables* and the 3 audio libs is the string "table" in the x264 A/V package's name.

ok, back to installer then :)

Assignee: mageia => bugsquad
Source RPM: alsa-plugins => (none)

Triage did not correct assignee. Now it is kinda old.

Needs retesting and proper assignment per current installer (5beta1 these days).

Keywords: Triaged => NEEDINFO

This ie due to the call to network::drakfirewall::set_ports(() from install::steps::configure_firewall(), itself being called from configureNetwork():
http://gitweb.mageia.org/software/drakx/tree/perl-install/install/steps.pm#n641

We automatically configure a firewall since this commit:
http://gitweb.mageia.org/software/drakx/commit/?id=9f332be09e
"configure a firewall by default in secure level >= 3"

The bug being one cannot alter the security level before summary since quite some time.
On the other hand we do want to setup a firewall by default for our users.
I suggest adding a "nofirewall" option to drakx.

WDYT?

Keywords: NEEDINFO => (none)
Priority: Normal => Low
CC: (none) => mageia, thierry.vignaud
Summary: deselection of iptables/shorewall never persists => configureNetwork install iptables/shorewall despite having been previously deselected
Severity: normal => minor

(In reply to Thierry Vignaud from comment #10)

<snip>
> I suggest adding a "nofirewall" option to drakx.
> 
> WDYT?

@ Felix

can you please reply?

It sounds fine to me, but I won't ever use the option, and you own this bug report ;-)

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Why doesn't the NEEDINFO keyword somehow specify who it is that info is expected from, like in other bug trackers that use the term?

As I use a dedicated firewall, I don't litter workstation or test installations with software that lengthens update processes, complicates testing, and consumes filesystem space needlessly whereever I have the choice. Normally I install minimal, then add what I need with urpmi. I'd much rather add than need to subtract. IMO, firewall ought not be part of a minimal install, so a startup option shouldn't be needed, but if an option is the only way to not have what isn't wanted or needed it will be better than nothing.

(In reply to Felix Miata from comment #12)
> Why doesn't the NEEDINFO keyword somehow specify who it is that info is
> expected from, like in other bug trackers that use the term?

I wasn't aware other bug trackers did that, but just asked about it in #mageia-bugsquad on freenode... you might want to join that channel if you're curious whether anyone replies

Keywords: NEEDINFO => (none)