I just submitted 6.1.9-2.3.mga2 in updates_testing, fixing the issue.

After configuring sympa with /usr/sbin/sympa_wizard.pl

I was trying to figure out why http://127.0.0.1/sympa was working ok
with the prior version, and then took a closer look at the file.

The change only affects http://127.0.0.1/static-sympa, however even
with this update, that still returns Access forbidden!.

# ll /var/lib/sympa/static_content
total 12
drwxr-xr-x 2 sympa sympa 4096 Sep  1 13:51 css/
drwxr-xr-x 2 sympa sympa 4096 Sep  1 13:56 icons/
-rw-r----- 1 sympa sympa    0 Sep  1 13:51 index.html
drwxrwxr-x 2 sympa sympa 4096 Sep  1 13:51 pictures/

What is supposed to create the index.html file?

From what I can see, it doesn't look like http://127.0.0.1/static-sympa is
intended to be used in a browser, so this update is probably not needed.

CC: (none) => davidwhodgins

I'm adding the feedback whiteboard entry, but it's actually Claire
that the question is for.

While the entry in /etc/httpd/conf/webapps.d/sympa.con for
the static-sympa sympa was obviously incorrect, is that
actually used anywhere?  What wasn't working?

Whiteboard: (none) => feedback

From what I remember Dave it was sympa-www, the web interface.

See https://bugs.mageia.org/show_bug.cgi?id=5939#c31

It seems it affected mga1 and 2 although I think this update is just for mga2 so we should probably create another bug for mga1.

Whiteboard: feedback => (none)

(In reply to comment #4)
> From what I remember Dave it was sympa-www, the web interface.
> 
> See https://bugs.mageia.org/show_bug.cgi?id=5939#c31
> 
> It seems it affected mga1 and 2 although I think this update is just for mga2
> so we should probably create another bug for mga1.

As per https://bugs.mageia.org/show_bug.cgi?id=5939#c22, bug 6714 was
opened for the problem with modules not loading, which affected Mageia 2
only.

The problem with the fcgi files downloading instead of running was caused
missing changes in /etc/httpd/modules.d/92_mod_fastcgi.conf from the
apache-mod_fastcgi package.  Several other apache modules required the
same change, in order to work in a systemd environment.

That was fixed in Mageia 2 Core Updates Testing on 2012-07-07, with that
fix pushed to Core Updates 2012-07-21.

Comparing sympa running with the Core Updates version versus the Core Updates
testing version, the difference is whether or not things like the sympa logo
get loaded.  Didn't notice the missing logo before, as I'd never seen it. :-)

Testing complete on Mageia 2 i586 and x86-64.

Advisory:  This bugfix update for sympa-www corrects a path error in the
httpd configuration file, that prevented static content such as the sympa
logo from being displayed.

This does affect Mageia 1 as well.

Guillaume, would you like to correct the Mageia 1 version as part of this
update, or would you prefer that we validate this update, and open a new
one for Mageia 1?

Whiteboard: (none) => MGA2-32-OK MGA2-64-OK feedback

Adding Guillaume to the cc list.  Please take a look at comment 5.

CC: (none) => guillomovitch

Bug 7456 created for Mageia 1

Validating this one.

Advisory:  This bugfix update for sympa-www corrects a path error in the
httpd configuration file, that prevented static content such as the sympa
logo from being displayed.

SRPM: sympa-6.1.9-2.3.mga2


Could sysadmin please push from core/updates_testing to core/updates

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Whiteboard: MGA2-32-OK MGA2-64-OK feedback => MGA2-32-OK MGA2-64-OK

Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0190

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED