Please also see bug 6772 In /etc/httpd/conf/webapps.d/sympa.conf the settings point to a non existent directory structure at /var/sympa instead of /var/lib/sympa which causes sympa-www to fail. This was corrected for Mageia 2 but affects Mageia 1 also.
I just submitted a 6.1.4-2.3mga1 release into testing_updates. Make make clear in the advisory it is just a change in a default configuration file, meaning it has no interest for anyone with already a working configuration in place.
Status: NEW => RESOLVEDResolution: (none) => FIXED
It needs to go through QA then, following the updates policy. It would just sit in updates_testing otherwise. https://wiki.mageia.org/en/Updates_policy#Maintainer_.28or_any_interested_packager.29 There is an example there for the type of advisory to give. If it's ready for this could you please follow proper policy. Assign to QA, leave advisory, add yourself to CC.. Thankyou
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Ping for packager response.
You already issued an advisory for bug #6772. Just mention the problem occurs in the default configuration, and that will be OK. For the rest, you don't need my help.
CC: (none) => guillomovitchAssignee: guillomovitch => qa-bugs
Testing complete on Mageia 1 i586 & x86-64. Could someone from the sysadmin team push the srpm sympa-6.1.4-2.3.mga1.src.rpm from Mageia 1 Core Updates Testing to Core Updates. 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. https://bugs.mageia.org/show_bug.cgi?id=7456
Keywords: (none) => validated_updateCC: (none) => davidwhodgins, sysadmin-bugsWhiteboard: (none) => MGA1-32-OK MGA1-64-OK
Update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0204
Status: REOPENED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED