From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2012-March/004252.html | 81 +++ zarb-ml/mageia-sysadm/2012-March/004253.html | 81 +++ zarb-ml/mageia-sysadm/2012-March/004254.html | 88 ++++ zarb-ml/mageia-sysadm/2012-March/004255.html | 94 ++++ zarb-ml/mageia-sysadm/2012-March/004256.html | 75 +++ zarb-ml/mageia-sysadm/2012-March/004257.html | 67 +++ zarb-ml/mageia-sysadm/2012-March/004258.html | 73 +++ zarb-ml/mageia-sysadm/2012-March/004259.html | 71 +++ zarb-ml/mageia-sysadm/2012-March/004260.html | 76 +++ zarb-ml/mageia-sysadm/2012-March/004261.html | 78 +++ zarb-ml/mageia-sysadm/2012-March/004262.html | 87 ++++ zarb-ml/mageia-sysadm/2012-March/004263.html | 71 +++ zarb-ml/mageia-sysadm/2012-March/004264.html | 75 +++ zarb-ml/mageia-sysadm/2012-March/004265.html | 94 ++++ zarb-ml/mageia-sysadm/2012-March/004266.html | 65 +++ zarb-ml/mageia-sysadm/2012-March/004267.html | 82 +++ zarb-ml/mageia-sysadm/2012-March/004268.html | 96 ++++ zarb-ml/mageia-sysadm/2012-March/004269.html | 67 +++ zarb-ml/mageia-sysadm/2012-March/004270.html | 83 +++ zarb-ml/mageia-sysadm/2012-March/004271.html | 83 +++ zarb-ml/mageia-sysadm/2012-March/004272.html | 80 +++ zarb-ml/mageia-sysadm/2012-March/004273.html | 60 +++ zarb-ml/mageia-sysadm/2012-March/004274.html | 70 +++ zarb-ml/mageia-sysadm/2012-March/004275.html | 89 ++++ zarb-ml/mageia-sysadm/2012-March/004276.html | 69 +++ zarb-ml/mageia-sysadm/2012-March/004277.html | 66 +++ zarb-ml/mageia-sysadm/2012-March/004278.html | 74 +++ zarb-ml/mageia-sysadm/2012-March/004279.html | 80 +++ zarb-ml/mageia-sysadm/2012-March/004280.html | 90 ++++ zarb-ml/mageia-sysadm/2012-March/004281.html | 88 ++++ zarb-ml/mageia-sysadm/2012-March/004282.html | 93 ++++ zarb-ml/mageia-sysadm/2012-March/004283.html | 100 ++++ zarb-ml/mageia-sysadm/2012-March/004284.html | 103 ++++ zarb-ml/mageia-sysadm/2012-March/004285.html | 88 ++++ zarb-ml/mageia-sysadm/2012-March/004286.html | 73 +++ zarb-ml/mageia-sysadm/2012-March/004287.html | 79 +++ zarb-ml/mageia-sysadm/2012-March/004288.html | 175 +++++++ zarb-ml/mageia-sysadm/2012-March/004289.html | 120 +++++ zarb-ml/mageia-sysadm/2012-March/004290.html | 82 +++ zarb-ml/mageia-sysadm/2012-March/004291.html | 141 +++++ zarb-ml/mageia-sysadm/2012-March/004292.html | 154 ++++++ zarb-ml/mageia-sysadm/2012-March/004293.html | 102 ++++ zarb-ml/mageia-sysadm/2012-March/004294.html | 134 +++++ zarb-ml/mageia-sysadm/2012-March/004295.html | 76 +++ zarb-ml/mageia-sysadm/2012-March/004296.html | 170 ++++++ zarb-ml/mageia-sysadm/2012-March/004297.html | 86 ++++ zarb-ml/mageia-sysadm/2012-March/004298.html | 66 +++ zarb-ml/mageia-sysadm/2012-March/004299.html | 80 +++ zarb-ml/mageia-sysadm/2012-March/004300.html | 88 ++++ zarb-ml/mageia-sysadm/2012-March/004301.html | 114 ++++ zarb-ml/mageia-sysadm/2012-March/004302.html | 109 ++++ zarb-ml/mageia-sysadm/2012-March/004303.html | 106 ++++ zarb-ml/mageia-sysadm/2012-March/004304.html | 90 ++++ zarb-ml/mageia-sysadm/2012-March/004305.html | 308 +++++++++++ zarb-ml/mageia-sysadm/2012-March/004306.html | 91 ++++ zarb-ml/mageia-sysadm/2012-March/004307.html | 104 ++++ zarb-ml/mageia-sysadm/2012-March/004308.html | 87 ++++ zarb-ml/mageia-sysadm/2012-March/004309.html | 143 ++++++ zarb-ml/mageia-sysadm/2012-March/004310.html | 97 ++++ zarb-ml/mageia-sysadm/2012-March/004311.html | 102 ++++ zarb-ml/mageia-sysadm/2012-March/004312.html | 259 ++++++++++ zarb-ml/mageia-sysadm/2012-March/004313.html | 96 ++++ zarb-ml/mageia-sysadm/2012-March/004314.html | 167 ++++++ zarb-ml/mageia-sysadm/2012-March/004315.html | 90 ++++ zarb-ml/mageia-sysadm/2012-March/004316.html | 100 ++++ zarb-ml/mageia-sysadm/2012-March/004317.html | 82 +++ zarb-ml/mageia-sysadm/2012-March/004318.html | 71 +++ zarb-ml/mageia-sysadm/2012-March/004319.html | 83 +++ zarb-ml/mageia-sysadm/2012-March/004320.html | 77 +++ zarb-ml/mageia-sysadm/2012-March/004321.html | 77 +++ zarb-ml/mageia-sysadm/2012-March/004322.html | 82 +++ zarb-ml/mageia-sysadm/2012-March/004323.html | 75 +++ zarb-ml/mageia-sysadm/2012-March/004324.html | 80 +++ zarb-ml/mageia-sysadm/2012-March/004325.html | 76 +++ zarb-ml/mageia-sysadm/2012-March/004326.html | 75 +++ zarb-ml/mageia-sysadm/2012-March/004327.html | 64 +++ zarb-ml/mageia-sysadm/2012-March/004328.html | 81 +++ zarb-ml/mageia-sysadm/2012-March/004329.html | 99 ++++ zarb-ml/mageia-sysadm/2012-March/004330.html | 92 ++++ zarb-ml/mageia-sysadm/2012-March/004331.html | 86 ++++ zarb-ml/mageia-sysadm/2012-March/004332.html | 299 +++++++++++ zarb-ml/mageia-sysadm/2012-March/004333.html | 202 ++++++++ zarb-ml/mageia-sysadm/2012-March/004334.html | 58 +++ zarb-ml/mageia-sysadm/2012-March/004335.html | 58 +++ zarb-ml/mageia-sysadm/2012-March/004336.html | 76 +++ zarb-ml/mageia-sysadm/2012-March/004337.html | 103 ++++ zarb-ml/mageia-sysadm/2012-March/004338.html | 70 +++ zarb-ml/mageia-sysadm/2012-March/004339.html | 83 +++ zarb-ml/mageia-sysadm/2012-March/004340.html | 77 +++ zarb-ml/mageia-sysadm/2012-March/004341.html | 69 +++ zarb-ml/mageia-sysadm/2012-March/004342.html | 78 +++ zarb-ml/mageia-sysadm/2012-March/004343.html | 73 +++ zarb-ml/mageia-sysadm/2012-March/004344.html | 77 +++ zarb-ml/mageia-sysadm/2012-March/004345.html | 74 +++ zarb-ml/mageia-sysadm/2012-March/004346.html | 57 ++ zarb-ml/mageia-sysadm/2012-March/004347.html | 59 +++ zarb-ml/mageia-sysadm/2012-March/004348.html | 152 ++++++ zarb-ml/mageia-sysadm/2012-March/004349.html | 101 ++++ zarb-ml/mageia-sysadm/2012-March/004350.html | 72 +++ zarb-ml/mageia-sysadm/2012-March/004351.html | 121 +++++ zarb-ml/mageia-sysadm/2012-March/004352.html | 122 +++++ zarb-ml/mageia-sysadm/2012-March/author.html | 552 ++++++++++++++++++++ zarb-ml/mageia-sysadm/2012-March/date.html | 552 ++++++++++++++++++++ zarb-ml/mageia-sysadm/2012-March/index.html | 1 + zarb-ml/mageia-sysadm/2012-March/subject.html | 552 ++++++++++++++++++++ zarb-ml/mageia-sysadm/2012-March/thread.html | 713 ++++++++++++++++++++++++++ 106 files changed, 12077 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2012-March/004252.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004253.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004254.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004255.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004256.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004257.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004258.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004259.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004260.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004261.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004262.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004263.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004264.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004265.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004266.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004267.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004268.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004269.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004270.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004271.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004272.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004273.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004274.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004275.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004276.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004277.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004278.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004279.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004280.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004281.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004282.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004283.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004284.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004285.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004286.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004287.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004288.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004289.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004290.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004291.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004292.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004293.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004294.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004295.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004296.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004297.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004298.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004299.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004300.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004301.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004302.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004303.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004304.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004305.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004306.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004307.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004308.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004309.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004310.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004311.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004312.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004313.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004314.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004315.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004316.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004317.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004318.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004319.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004320.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004321.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004322.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004323.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004324.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004325.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004326.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004327.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004328.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004329.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004330.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004331.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004332.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004333.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004334.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004335.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004336.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004337.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004338.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004339.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004340.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004341.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004342.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004343.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004344.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004345.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004346.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004347.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004348.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004349.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004350.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004351.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/004352.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/author.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/date.html create mode 120000 zarb-ml/mageia-sysadm/2012-March/index.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/subject.html create mode 100644 zarb-ml/mageia-sysadm/2012-March/thread.html (limited to 'zarb-ml/mageia-sysadm/2012-March') diff --git a/zarb-ml/mageia-sysadm/2012-March/004252.html b/zarb-ml/mageia-sysadm/2012-March/004252.html new file mode 100644 index 000000000..2de5eca7d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004252.html @@ -0,0 +1,81 @@ + + + + [Mageia-sysadm] ITC société de TRADUCTION! + + + + + + + + + +

[Mageia-sysadm] ITC société de TRADUCTION!

+ Marie Françoise Greck – ITC France + mf.greck at itcfrance.com +
+ Tue Mar 6 13:14:43 CET 2012 +

+
+ +
English ( "http://www.itcglobaltranslations.com/email/itcfrance/english/index.html" ) - Español ( "http://www.itcglobaltranslations.com/email/itcfrance/spanish/index.html" )- Deutsch ( "http://www.itcglobaltranslations.com/email/itcfrance/german/index.html" )
+
+Bonjour,
+
+J’ai obtenu les informations concernant votre entreprise sur Internet et je prends donc la liberté de vous contacter.
+
+Notre société de traduction, ITC Traduction ( "http://www.itcfrance.com/" ), serait intéressée par une collaboration avec votre entreprise pour vos projets de traduction.  Accepteriez-vous, à cet égard, de transférer cet email à la personne responsable de la traduction de vos documents ainsi qu’à votre département marketing ? 
+
+ITC est une société de traduction qui propose des services de traduction très technique dans plus de 25 langues. Forts d’une expérience de 10 ans de collaboration avec des entreprises internationales et avec des bureaux en Europe et aux Etats-Unis, nous nous sommes forgé une solide réputation et nous disposons d’un portefeuille clients incluant des organisations réputées telles que Cap Gemini, Johnson Controls, Emerson Process, John Deere, Haulotte, Sciemetric, Toyota, Pfizer, Covidien, Publicis, L’Oréal, Nestlé, Sanofi, l’Organisation Mondiale de la Santé (OMS), Averion, Alstom, l’Association Word Trade Center, et les Nations Unies, pour n’en citer que quelques-unes.
+Traductions de documents techniques : guides d’utilisateur, notices d’emballage, documentation technique, interfaces graphiques (GUI), systèmes d’aide, guides de résolution de problèmes, instructions de travail, documents portant sur les caractéristiques produit etc.
+Traductions de documents médicaux/pharmaceutiques : protocoles, comptes-rendus médicaux, brochures pour investigateur, suivis d’essai clinique, formulaires de rapport de cas (CRF), documents et attestations de conformité et d’innocuité des tests, documents relatifs aux essais cliniques, dispositions réglementaires, documents relatifs à l’enregistrement d’un médicament, autorisations de mise sur le marché, formulaires de consentement éclairé, questionnaires patients, rapports toxicologiques, rapports de sûreté et rapports d’études cliniques, mode d’emploi et encarts publicitaires, etc. Traductions de documents marketing : brochures, questionnaires/études, notices d’utilisation, emballages/étiquettes, sites Internet, communiqués de presse, livres blancs, etc.
+Traductions de documents juridiques : brevets, procédures légales, contrats, traités, lois et dispositifs réglementaires, rapports d’experts, engagements de confidentialité, etc.
+N’hésitez pas à me contacter pour tout renseignement complémentaire. 
+
+Je vous prie d’agréer, Madame, Monsieur, mes sincères salutations.
+
+Marie-Françoise Greck
+( "mailto:mf.greck at itcfrance.com?" )
+
+Pour vous désinscrire ( "mailto:jm.conseil at itcglobaltranslations.com?subject=d%E9sinscrire" ). Pour demander un devis ( "mailto:mf.greck at itcfrance.com?subject=demander%20un%20devis" ).
+Si on vous a transféré cet e-mail et que vous souhaitez vous inscrire pour recevoir notre newsletter ( "mailto:mf.greck at itcfrance.com?subject=inscrire" ).
+( "mailto:mgreck at itcfrance.com?subject=subscribe" )
+
+© 2011 International Traduction Conseil ( "http://www.itcfrance.com/" ) - 4 allée de la combe - 69380 Lissieu France - Tél. +33 4 78 33 02 55 - Fax +33 4 72 54 93 89
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120306/b684ccdd/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004253.html b/zarb-ml/mageia-sysadm/2012-March/004253.html new file mode 100644 index 000000000..1062b899a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004253.html @@ -0,0 +1,81 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ nicolas vigier + boklm at mars-attacks.org +
+ Wed Mar 7 18:38:57 CET 2012 +

+
+ +
Hello,
+
+I order to discuss next things to do in sysadmin, I propose that we do
+an IRC meeting on #mageia-sysadmin.
+
+We can do it on thursday next week, the 15th at 8pm UTC, during 1h30.
+Unless someone cannot be there and we can try to find an other date or
+hour.
+
+What do you think ?
+
+List of topics can be :
+
+ * rabbit end of sponsoring
+ * sucuk server and VMs
+ * backups
+ * arm build system
+ * backports setup
+ * other build system improvements
+ * council representative elections
+ * other topics ?
+
+Meeting is for sysadmin team members, but is also open to anyone
+interested.
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004254.html b/zarb-ml/mageia-sysadm/2012-March/004254.html new file mode 100644 index 000000000..4b302460d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004254.html @@ -0,0 +1,88 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Mar 7 18:46:03 CET 2012 +

+
+ +
On Wed, Mar 7, 2012 at 17:38, nicolas vigier <boklm at mars-attacks.org> wrote:
+> Hello,
+>
+> I order to discuss next things to do in sysadmin
+I won't obey ! :)
+
+> I propose that we do an IRC meeting on #mageia-sysadmin.
+>
+> We can do it on thursday next week, the 15th at 8pm UTC, during 1h30.
+> Unless someone cannot be there and we can try to find an other date or
+> hour.
+
+Should be fine for me
+
+> What do you think ?
+>
+> List of topics can be :
+>
+>  * rabbit end of sponsoring
+>  * sucuk server and VMs
+>  * backups
+>  * arm build system
+>  * backports setup
+>  * other build system improvements
+>  * council representative elections
+>  * other topics ?
+
+management of infra_1 ?
+we need to ensure packages there get updated when we get security fixes
+
+> Meeting is for sysadmin team members, but is also open to anyone
+> interested.
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004255.html b/zarb-ml/mageia-sysadm/2012-March/004255.html new file mode 100644 index 000000000..8866cc10e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004255.html @@ -0,0 +1,94 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ nicolas vigier + boklm at mars-attacks.org +
+ Wed Mar 7 20:30:03 CET 2012 +

+
+ +
On Wed, 07 Mar 2012, Pascal Terjan wrote:
+
+> On Wed, Mar 7, 2012 at 17:38, nicolas vigier <boklm at mars-attacks.org> wrote:
+> > Hello,
+> >
+> > I order to discuss next things to do in sysadmin
+> I won't obey ! :)
+
+Oops, I wanted to say "In order to discuss" of course :)
+
+> 
+> > I propose that we do an IRC meeting on #mageia-sysadmin.
+> >
+> > We can do it on thursday next week, the 15th at 8pm UTC, during 1h30.
+> > Unless someone cannot be there and we can try to find an other date or
+> > hour.
+> 
+> Should be fine for me
+> 
+> > What do you think ?
+> >
+> > List of topics can be :
+> >
+> >  * rabbit end of sponsoring
+> >  * sucuk server and VMs
+> >  * backups
+> >  * arm build system
+> >  * backports setup
+> >  * other build system improvements
+> >  * council representative elections
+> >  * other topics ?
+> 
+> management of infra_1 ?
+> we need to ensure packages there get updated when we get security fixes
+
+Ok.
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004256.html b/zarb-ml/mageia-sysadm/2012-March/004256.html new file mode 100644 index 000000000..51dc59b06 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004256.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] Remove/disable mirrors + + + + + + + + + +

[Mageia-sysadm] Remove/disable mirrors

+ Manuel Hiebel + manuel at hiebel.eu +
+ Thu Mar 8 04:43:09 CET 2012 +

+
+ +
Hi,
+
+Can somebody remove http://mirrors.mageia.org/mirrors/ftp.itb.ac.id as
+mirror ? It was not updated since September, and seems it's also a dead
+one for other projects.
+
+You can also disabling http://mirrors.mageia.org/mirrors/ftp.twaren.net
+not updated since January. (I have send a mail)
+
+Thanks.
+
+
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004257.html b/zarb-ml/mageia-sysadm/2012-March/004257.html new file mode 100644 index 000000000..2bf79d02e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004257.html @@ -0,0 +1,67 @@ + + + + [Mageia-sysadm] no more mails from bugzilla? + + + + + + + + + +

[Mageia-sysadm] no more mails from bugzilla?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Mar 8 09:10:01 CET 2012 +

+
+ +
Hi
+It looks like bugzilla no more send mails when new comments are added
+to bugs where I'm in the cc list since a couple days...
+See you
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004258.html b/zarb-ml/mageia-sysadm/2012-March/004258.html new file mode 100644 index 000000000..9c052c204 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004258.html @@ -0,0 +1,73 @@ + + + + [Mageia-sysadm] no more mails from bugzilla? + + + + + + + + + +

[Mageia-sysadm] no more mails from bugzilla?

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 8 11:44:02 CET 2012 +

+
+ +
On Thu, 08 Mar 2012, Thierry Vignaud wrote:
+
+> Hi
+> It looks like bugzilla no more send mails when new comments are added
+> to bugs where I'm in the cc list since a couple days...
+> See you
+
+I didn't notice any problem. Do you have an exemple of bug where you
+didn't receive email ?
+
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004259.html b/zarb-ml/mageia-sysadm/2012-March/004259.html new file mode 100644 index 000000000..1f234cc81 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004259.html @@ -0,0 +1,71 @@ + + + + [Mageia-sysadm] Remove/disable mirrors + + + + + + + + + +

[Mageia-sysadm] Remove/disable mirrors

+ Manuel Hiebel + manuel at hiebel.eu +
+ Thu Mar 8 12:12:50 CET 2012 +

+
+ +
Le jeudi 08 mars 2012 à 04:43 +0100, Manuel Hiebel a écrit :
+> Hi,
+> You can also disabling http://mirrors.mageia.org/mirrors/ftp.twaren.net
+> not updated since January. (I have send a mail)
+"Hello,
+
+We are running out of hard disk space and preparing for migrating to a
+larger storage zone.
+The sync will be restored once the migration is done."
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004260.html b/zarb-ml/mageia-sysadm/2012-March/004260.html new file mode 100644 index 000000000..2ff7debae --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004260.html @@ -0,0 +1,76 @@ + + + + [Mageia-sysadm] no more mails from bugzilla? + + + + + + + + + +

[Mageia-sysadm] no more mails from bugzilla?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Mar 8 12:59:28 CET 2012 +

+
+ +
On 8 March 2012 11:44, nicolas vigier <boklm at mars-attacks.org> wrote:
+>> It looks like bugzilla no more send mails when new comments are added
+>> to bugs where I'm in the cc list since a couple days...
+>> See you
+>
+> I didn't notice any problem. Do you have an exemple of bug where you
+> didn't receive email ?
+
+https://bugs.mageia.org/show_bug.cgi?id=4724
+https://bugs.mageia.org/show_bug.cgi?id=4432
+https://bugs.mageia.org/show_bug.cgi?id=4197
+https://bugs.mageia.org/show_bug.cgi?id=4769
+
+Thus I've opened https://bugs.mageia.org/show_bug.cgi?id=4850
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004261.html b/zarb-ml/mageia-sysadm/2012-March/004261.html new file mode 100644 index 000000000..73ee7082b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004261.html @@ -0,0 +1,78 @@ + + + + [Mageia-sysadm] no more mails from bugzilla? + + + + + + + + + +

[Mageia-sysadm] no more mails from bugzilla?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Mar 8 14:17:43 CET 2012 +

+
+ +
On 8 March 2012 12:59, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>> It looks like bugzilla no more send mails when new comments are added
+>>> to bugs where I'm in the cc list since a couple days...
+>>> See you
+>>
+>> I didn't notice any problem. Do you have an exemple of bug where you
+>> didn't receive email ?
+>
+> https://bugs.mageia.org/show_bug.cgi?id=4724
+> https://bugs.mageia.org/show_bug.cgi?id=4432
+> https://bugs.mageia.org/show_bug.cgi?id=4197
+> https://bugs.mageia.org/show_bug.cgi?id=4769
+>
+> Thus I've opened https://bugs.mageia.org/show_bug.cgi?id=4850
+
+Anybody else not receiving bugzilla mails anymore?
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004262.html b/zarb-ml/mageia-sysadm/2012-March/004262.html new file mode 100644 index 000000000..0d93d03f9 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004262.html @@ -0,0 +1,87 @@ + + + + [Mageia-sysadm] no more mails from bugzilla? + + + + + + + + + +

[Mageia-sysadm] no more mails from bugzilla?

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 8 14:21:00 CET 2012 +

+
+ +
On Thu, 08 Mar 2012, Thierry Vignaud wrote:
+
+> On 8 March 2012 12:59, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+> >>> It looks like bugzilla no more send mails when new comments are added
+> >>> to bugs where I'm in the cc list since a couple days...
+> >>> See you
+> >>
+> >> I didn't notice any problem. Do you have an exemple of bug where you
+> >> didn't receive email ?
+> >
+> > https://bugs.mageia.org/show_bug.cgi?id=4724
+> > https://bugs.mageia.org/show_bug.cgi?id=4432
+> > https://bugs.mageia.org/show_bug.cgi?id=4197
+> > https://bugs.mageia.org/show_bug.cgi?id=4769
+> >
+> > Thus I've opened https://bugs.mageia.org/show_bug.cgi?id=4850
+> 
+> Anybody else not receiving bugzilla mails anymore?
+
+Did you check the spam folder ? According to mail server logs, the email
+was accepted by google server :
+https://bugs.mageia.org/show_bug.cgi?id=4850#c2
+
+Do you still receive the emails from ml.mageia.org mailing lists ?
+
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004263.html b/zarb-ml/mageia-sysadm/2012-March/004263.html new file mode 100644 index 000000000..2d2814062 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004263.html @@ -0,0 +1,71 @@ + + + + [Mageia-sysadm] no more mails from bugzilla? + + + + + + + + + +

[Mageia-sysadm] no more mails from bugzilla?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Mar 8 14:52:27 CET 2012 +

+
+ +
On 8 March 2012 14:21, nicolas vigier <boklm at mars-attacks.org> wrote:
+>> Anybody else not receiving bugzilla mails anymore?
+>
+> Did you check the spam folder ? According to mail server logs, the email
+> was accepted by google server :
+> https://bugs.mageia.org/show_bug.cgi?id=4850#c2
+
+Indeed sg triggered gmail spam :-(
+Sorry for the noise.
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004264.html b/zarb-ml/mageia-sysadm/2012-March/004264.html new file mode 100644 index 000000000..5c6d5dbca --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004264.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] Problems with the build server chroot (xboard building) + + + + + + + + + +

[Mageia-sysadm] Problems with the build server chroot (xboard building)

+ Kamil Rytarowski + n54 at gmx.com +
+ Sun Mar 11 01:08:07 CET 2012 +

+
+ +
Hello!
+
+I have got encountered problems building xboard (both core and tainted 
+version).
+
+There were many chroot failures and the package was bouncing to install 
+dependencies and then 'partial' period took way too long time.
+
+xboard core/release
+http://pkgsubmit.mageia.org/uploads/done/cauldron/core/release/20120310111314.kamil.valstar.1068/
+
+xboard tainted/release
+http://pkgsubmit.mageia.org/uploads/done/cauldron/tainted/release/20120310234717.kamil.valstar.19095/
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004265.html b/zarb-ml/mageia-sysadm/2012-March/004265.html new file mode 100644 index 000000000..a3db8e8fa --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004265.html @@ -0,0 +1,94 @@ + + + + [Mageia-sysadm] Problems with the build server chroot (xboard building) + + + + + + + + + +

[Mageia-sysadm] Problems with the build server chroot (xboard building)

+ Pascal Terjan + pterjan at gmail.com +
+ Sun Mar 11 01:33:36 CET 2012 +

+
+ +
On Sun, Mar 11, 2012 at 00:08, Kamil Rytarowski <n54 at gmx.com> wrote:
+> Hello!
+>
+> I have got encountered problems building xboard (both core and tainted
+> version).
+>
+> There were many chroot failures and the package was bouncing to install
+> dependencies and then 'partial' period took way too long time.
+>
+> xboard core/release
+> http://pkgsubmit.mageia.org/uploads/done/cauldron/core/release/20120310111314.kamil.valstar.1068/
+>
+> xboard tainted/release
+> http://pkgsubmit.mageia.org/uploads/done/cauldron/tainted/release/20120310234717.kamil.valstar.19095/
+
+It seems the command exited with error 1 even if urpmi suceeded
+installing all packages:
+
+    84/84: texinfo               #############################################
+removing installed rpms (texlive-texmf-20110705-6.mga2.noarch.rpm
+texinfo-4.13a-3.mga2.i586.rpm perl-TimeDate-1.200.0-1.mga1.noarch.rpm
+perl-Tk-804.30.0-1.mga2.i586.rpm) from /var/cache/urpmi/rpms
+I: [iurt_root_command] ERROR: chroot
+ __
+E: [iurt2] [iurt2] ERROR: call_ret=1 kill= err=256 (cannot be installed)
+F: [iurt2] [iurt2] See
+http://pkgsubmit.mageia.org/queue/build//cauldron/i586//log/@222381:xboard-4.5.3-4.mga2.src.rpm/
+
+Command failed: /usr/bin/sudo /usr/sbin/iurt_root_command --chroot
+/home/iurt/chroot_tmp/iurt/chroot_cauldron.i586.0.20120310130401 urpmi
+-v --no-verify-rpm --nolock --auto --no-suggests --ignoresize
+/home/iurt/rpm/SRPMS//@222381:xboard-4.5.3-4.mga2.src.rpm
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004266.html b/zarb-ml/mageia-sysadm/2012-March/004266.html new file mode 100644 index 000000000..3f7e8c9bf --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004266.html @@ -0,0 +1,65 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Mar 13 13:09:18 CET 2012 +

+
+ +
On Wed, 07 Mar 2012, nicolas vigier wrote:
+
+> 
+> We can do it on thursday next week, the 15th at 8pm UTC, during 1h30.
+> Unless someone cannot be there and we can try to find an other date or
+> hour.
+
+So everybody agree for thursday ?
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004267.html b/zarb-ml/mageia-sysadm/2012-March/004267.html new file mode 100644 index 000000000..d3d81c261 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004267.html @@ -0,0 +1,82 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Tue Mar 13 14:14:43 CET 2012 +

+
+ +
* nicolas vigier (boklm at mars-attacks.org) wrote:
+> On Wed, 07 Mar 2012, nicolas vigier wrote:
+> 
+> > 
+> > We can do it on thursday next week, the 15th at 8pm UTC, during 1h30.
+> > Unless someone cannot be there and we can try to find an other date or
+> > hour.
+> 
+> So everybody agree for thursday ?
+
+No problem for me.
+
+> 
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20120313/112e6134/attachment.asc>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004268.html b/zarb-ml/mageia-sysadm/2012-March/004268.html new file mode 100644 index 000000000..f45336043 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004268.html @@ -0,0 +1,96 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ Samuel Verschelde + stormi at laposte.net +
+ Thu Mar 15 09:43:27 CET 2012 +

+
+ +
Hi,
+
+If time permits I'd like also to discuss Mageia App Db setup in order to 
+prepare its installation once version 0.3 (which is late, but partly because 
+we made it work with postgresl!) is out.
+
+Otherwise this is a topic I can discuss outside meeting.
+
+Samuel
+
+Le mercredi 7 mars 2012 18:38:57, nicolas vigier a écrit :
+> Hello,
+> 
+> I order to discuss next things to do in sysadmin, I propose that we do
+> an IRC meeting on #mageia-sysadmin.
+> 
+> We can do it on thursday next week, the 15th at 8pm UTC, during 1h30.
+> Unless someone cannot be there and we can try to find an other date or
+> hour.
+> 
+> What do you think ?
+> 
+> List of topics can be :
+> 
+>  * rabbit end of sponsoring
+>  * sucuk server and VMs
+>  * backups
+>  * arm build system
+>  * backports setup
+>  * other build system improvements
+>  * council representative elections
+>  * other topics ?
+> 
+> Meeting is for sysadmin team members, but is also open to anyone
+> interested.
+> 
+> _______________________________________________
+> Mageia-sysadm mailing list
+> Mageia-sysadm at mageia.org
+> https://www.mageia.org/mailman/listinfo/mageia-sysadm
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004269.html b/zarb-ml/mageia-sysadm/2012-March/004269.html new file mode 100644 index 000000000..fbd3f9e2a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004269.html @@ -0,0 +1,67 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 15 11:51:28 CET 2012 +

+
+ +
On Thu, 15 Mar 2012, Samuel Verschelde wrote:
+
+> Hi,
+> 
+> If time permits I'd like also to discuss Mageia App Db setup in order to 
+> prepare its installation once version 0.3 (which is late, but partly because 
+> we made it work with postgresl!) is out.
+
+Ok, it's added to the list of topics for the meeting.
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004270.html b/zarb-ml/mageia-sysadm/2012-March/004270.html new file mode 100644 index 000000000..721f60e46 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004270.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] mageia.org subdomain for Mageia manuals, + ftp server + + + + + + + + + +

[Mageia-sysadm] mageia.org subdomain for Mageia manuals, + ftp server

+ Marja van Waes + marja11 at xs4all.nl +
+ Thu Mar 15 11:56:36 CET 2012 +

+
+ +
Hi everyone,
+
+When documentation team starts anew with the installer guide in Calenco, 
+it would be nice to have a sub domain like guide.mageia.org/..... or 
+doc.mageia.org/...   to show the installer manual we make.
+
+To get an impression of what is meant look at the current guide: 
+http://waesvanm.home.xs4all.nl/webhelp/content/
+
+It gets updated automatically when anything is changed in our Calenco 
+workspace. An ftp server (ftp.mageia.org ?) and inlog credentials are 
+needed for this feature to work.
+
+We don't yet want any official links to it, that can be done when the 
+work is finished. For now it is only to see what we are doing, so we can 
+work faster, and to point others to who are willing to help :)
+
+Would it be possible to arrange this?
+
+Of course, in the end we hope to put a Full Mageia Manual there ;)
+
+Regards,
+Marja
+
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004271.html b/zarb-ml/mageia-sysadm/2012-March/004271.html new file mode 100644 index 000000000..cb6d1fc06 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004271.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] [sysadmin-reports] Hobbit [827256] valstar.mageia.org:rsync warning (YELLOW) + + + + + + + + + +

[Mageia-sysadm] [sysadmin-reports] Hobbit [827256] valstar.mageia.org:rsync warning (YELLOW)

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 15 12:59:45 CET 2012 +

+
+ +
On Thu, 15 Mar 2012, root at mageia.org wrote:
+
+> yellow  Thu Mar 15 12:31:40 2012 rsync NOT ok 
+> 
+> Service rsync on valstar.mageia.org is not OK : Unexpected service response
+
+I restarted xinetd to fix this error. It also happenned yesterday.
+
+When connecting to rsync, connection was immediately closed :
+$ telnet valstar.mageia.org rsync
+Trying 212.85.158.147...
+Connected to valstar.mageia.org.
+Escape character is '^]'.
+Connection closed by foreign host.
+
+
+In syslog, we had errors like this :
+Mar 15 12:46:42 valstar xinetd[22848]: socket bind: Invalid argument (errno = 22)
+Mar 15 12:46:42 valstar xinetd[22848]: Failed to contact identity server at ::ffff:
+212.85.158.146: system error
+
+
+Maybe this problem ?
+https://bugzilla.redhat.com/show_bug.cgi?id=448069
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004272.html b/zarb-ml/mageia-sysadm/2012-March/004272.html new file mode 100644 index 000000000..c1e33463c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004272.html @@ -0,0 +1,80 @@ + + + + [Mageia-sysadm] Meeting tonight + + + + + + + + + +

[Mageia-sysadm] Meeting tonight

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 15 19:47:22 CET 2012 +

+
+ +
Hello,
+
+This is a reminder about IRC meeting tonight at 8pm UTC (9pm in Paris)
+in #mageia-sysadm channel on freenode.
+
+There is 10 topics planned, and 1h30, so that's only 8 or 9 minutes per
+topic (discussions can be continued on mailing list if needed, or other
+meeting organized later).
+
+List of topics with approximate time (some can be longer and other
+shorter) :
+ * 20:10 rabbit end of sponsoring
+ * 20:18 sucuk server and VMs
+ * 20:26 backups
+ * 20:34 arm build system
+ * 20:42 backports setup
+ * 20:50 management of infra_1
+ * 20:58 other build system improvements
+ * 21:06 council representative elections
+ * 21:14 mailing lists migration
+ * 21:22 madb installation
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004273.html b/zarb-ml/mageia-sysadm/2012-March/004273.html new file mode 100644 index 000000000..45d80b963 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004273.html @@ -0,0 +1,60 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 15 23:12:48 CET 2012 +

+
+ +
+Logs of the meeting :
+http://meetbot.mageia.org/mageia-sysadm/2012/mageia-sysadm.2012-03-15-20.06.html
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004274.html b/zarb-ml/mageia-sysadm/2012-March/004274.html new file mode 100644 index 000000000..3957517a6 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004274.html @@ -0,0 +1,70 @@ + + + + [Mageia-sysadm] Sysadmin IRC meeting + + + + + + + + + +

[Mageia-sysadm] Sysadmin IRC meeting

+ Samuel Verschelde + stormi at laposte.net +
+ Fri Mar 16 08:51:35 CET 2012 +

+
+ +
Le jeudi 15 mars 2012 11:51:28, nicolas vigier a écrit :
+> On Thu, 15 Mar 2012, Samuel Verschelde wrote:
+> > Hi,
+> > 
+> > If time permits I'd like also to discuss Mageia App Db setup in order to
+> > prepare its installation once version 0.3 (which is late, but partly
+> > because we made it work with postgresl!) is out.
+> 
+> Ok, it's added to the list of topics for the meeting.
+> 
+
+Oops, I forgot about the meeting after having asked to add topic, big shame on 
+me! Sorry for that.
+
+Samuel
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004275.html b/zarb-ml/mageia-sysadm/2012-March/004275.html new file mode 100644 index 000000000..5c5501933 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004275.html @@ -0,0 +1,89 @@ + + + + [Mageia-sysadm] Meeting tonight + + + + + + + + + +

[Mageia-sysadm] Meeting tonight

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Fri Mar 16 15:09:48 CET 2012 +

+
+ +
Sorry I couldn't attend the meeting, I am on leave, at my mother-in-law's house, and there were problems with her ADSL account (which I have just fixed, about 12 hours before I leave to drive home). I will be back home on Sunday night (at work from Monday).
+
+I have work-in-progress to update Xymon to 4.3.x, but the actions needed for upgrade are non-trivial (as the 2nd phase of renaming from Hobbit to Xymon was done between 4.2.x and 4.3.x), and I would like to try and get them seamless (both for Mandriva->Mageia for Mageia servers, and for use in a number of environments at work).
+
+Since I now also have ADSL at home (finally, after 6 years working for the Telco), I should be able to finish this in the next week or two (and attend more meetings).
+
+Regards,
+Buchan
+
+----- Original Message -----
+> Hello,
+> 
+> This is a reminder about IRC meeting tonight at 8pm UTC (9pm in Paris)
+> in #mageia-sysadm channel on freenode.
+> 
+> There is 10 topics planned, and 1h30, so that's only 8 or 9 minutes
+> per
+> topic (discussions can be continued on mailing list if needed, or
+> other
+> meeting organized later).
+> 
+> List of topics with approximate time (some can be longer and other
+> shorter) :
+> * 20:10 rabbit end of sponsoring
+> * 20:18 sucuk server and VMs
+> * 20:26 backups
+> * 20:34 arm build system
+> * 20:42 backports setup
+> * 20:50 management of infra_1
+> * 20:58 other build system improvements
+> * 21:06 council representative elections
+> * 21:14 mailing lists migration
+> * 21:22 madb installation
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004276.html b/zarb-ml/mageia-sysadm/2012-March/004276.html new file mode 100644 index 000000000..787fba0f3 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004276.html @@ -0,0 +1,69 @@ + + + + [Mageia-sysadm] Sysadmin team council representative and deputy election + + + + + + + + + +

[Mageia-sysadm] Sysadmin team council representative and deputy election

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Mar 20 00:15:20 CET 2012 +

+
+ +
Hello,
+
+As mentioned in last IRC meeting, we need to elect sysadmin team
+representative, and deputy, for council. Anybody from sysadmin team can
+be candidate. If you are candidate, you need to answer to this email to
+say you are candidate, before next monday when the vote will be started.
+
+Planning for election :
+ - 20/03 to 26/03 at 19:00 UTC: candidates send an email to say that they are
+   candidate
+ - 26/03 at 20:00 to 29/03 at 20:00 UTC: vote is done using epoll
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004277.html b/zarb-ml/mageia-sysadm/2012-March/004277.html new file mode 100644 index 000000000..d319e93ae --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004277.html @@ -0,0 +1,66 @@ + + + + [Mageia-sysadm] twiska.zarb.org mirror + + + + + + + + + +

[Mageia-sysadm] twiska.zarb.org mirror

+ David W. Hodgins + davidwhodgins at gmail.com +
+ Wed Mar 21 07:35:59 CET 2012 +

+
+ +
For at least the last 12 hours, with mgaapplet, I've been getting ...
+Installation failed, some files are missing:
+     http://twiska.zarb.org/mageia/distrib/1/i586/media/core/updates_testing/nautilus-dropbox-0.7.1-1.22.mga1.i586.rpm
+
+Is this a problem with this mirror, or is there a problem
+getting the i586 packages out?
+
+Regards, Dave Hodgins
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004278.html b/zarb-ml/mageia-sysadm/2012-March/004278.html new file mode 100644 index 000000000..024ea2402 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004278.html @@ -0,0 +1,74 @@ + + + + [Mageia-sysadm] twiska.zarb.org mirror + + + + + + + + + +

[Mageia-sysadm] twiska.zarb.org mirror

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Mar 21 10:30:00 CET 2012 +

+
+ +
On Wed, Mar 21, 2012 at 06:35, David W. Hodgins <davidwhodgins at gmail.com>wrote:
+
+> For at least the last 12 hours, with mgaapplet, I've been getting ...
+> Installation failed, some files are missing:
+>    http://twiska.zarb.org/mageia/**distrib/1/i586/media/core/**
+> updates_testing/nautilus-**dropbox-0.7.1-1.22.mga1.i586.**rpm<http://twiska.zarb.org/mageia/distrib/1/i586/media/core/updates_testing/nautilus-dropbox-0.7.1-1.22.mga1.i586.rpm>
+>
+> Is this a problem with this mirror, or is there a problem
+> getting the i586 packages out?
+>
+
+I saw someone requesting to remove a nautilus-dropbox from updates_testing,
+maybe the person who did it did not update the hdlists
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120321/51e43b14/attachment.html>
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004279.html b/zarb-ml/mageia-sysadm/2012-March/004279.html new file mode 100644 index 000000000..461838a7a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004279.html @@ -0,0 +1,80 @@ + + + + [Mageia-sysadm] twiska.zarb.org mirror + + + + + + + + + +

[Mageia-sysadm] twiska.zarb.org mirror

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Wed Mar 21 10:39:27 CET 2012 +

+
+ +
2012/3/21 Pascal Terjan <pterjan at gmail.com>:
+>
+> On Wed, Mar 21, 2012 at 06:35, David W. Hodgins <davidwhodgins at gmail.com>
+> wrote:
+>>
+>> For at least the last 12 hours, with mgaapplet, I've been getting ...
+>> Installation failed, some files are missing:
+>>
+>>  http://twiska.zarb.org/mageia/distrib/1/i586/media/core/updates_testing/nautilus-dropbox-0.7.1-1.22.mga1.i586.rpm
+>>
+>> Is this a problem with this mirror, or is there a problem
+>> getting the i586 packages out?
+>
+>
+> I saw someone requesting to remove a nautilus-dropbox from updates_testing,
+> maybe the person who did it did not update the hdlists
+
+Just checked with ftp://ftp.mandrivauser.de which syncs with
+distrib-coffee - the package is not there.
+
+-- 
+wobo
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004280.html b/zarb-ml/mageia-sysadm/2012-March/004280.html new file mode 100644 index 000000000..3d0410927 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004280.html @@ -0,0 +1,90 @@ + + + + [Mageia-sysadm] twiska.zarb.org mirror + + + + + + + + + +

[Mageia-sysadm] twiska.zarb.org mirror

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Mar 21 10:49:01 CET 2012 +

+
+ +
On Wed, Mar 21, 2012 at 09:39, Wolfgang Bornath <molch.b at googlemail.com>wrote:
+
+> 2012/3/21 Pascal Terjan <pterjan at gmail.com>:
+> >
+> > On Wed, Mar 21, 2012 at 06:35, David W. Hodgins <davidwhodgins at gmail.com
+> >
+> > wrote:
+> >>
+> >> For at least the last 12 hours, with mgaapplet, I've been getting ...
+> >> Installation failed, some files are missing:
+> >>
+> >>
+> http://twiska.zarb.org/mageia/distrib/1/i586/media/core/updates_testing/nautilus-dropbox-0.7.1-1.22.mga1.i586.rpm
+> >>
+> >> Is this a problem with this mirror, or is there a problem
+> >> getting the i586 packages out?
+> >
+> >
+> > I saw someone requesting to remove a nautilus-dropbox from
+> updates_testing,
+> > maybe the person who did it did not update the hdlists
+>
+> Just checked with ftp://ftp.mandrivauser.de which syncs with
+> distrib-coffee - the package is not there.
+
+
+Which makes sense if it was removed as requested, I hope the person who did
+it will see this thread :)
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120321/59502f30/attachment.html>
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004281.html b/zarb-ml/mageia-sysadm/2012-March/004281.html new file mode 100644 index 000000000..f16b169e1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004281.html @@ -0,0 +1,88 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Romain d'Alverny + rdalverny at gmail.com +
+ Wed Mar 21 14:57:13 CET 2012 +

+
+ +
Hi there (xpost sysadmins and forums-discuss lists),
+
+following the steps in
+https://ml.mageia.org/l/arc/council/2012-03/msg00115.html I'm going to
+update the forums groups for sysadmin members. The culprit is that
+it's not in sync with LDAP so far, so it's to be manually updated.
+
+Targetted situation:
+ - forum _technical_ management people => sysadmin (includes updating
+the code base, reviewing and applying patches)
+ - forum administration (roles, configuration, all that can be done
+through the Web interface, interfacing with sysadmin) => someone still
+to step up
+ - we don't touch to user-defined groups by default (although I'm not
+sure Packagers/Sysadmins ones are really needed/used - they are not in
+sync either - but this should be dealt with future forum)
+ - we use the Administrators group to manage who gets to fully manage
+the forums (there's an extra higher level for that, but not accessible
+to anyone at this time). Sysadmin members are members of this group.
+I'm reviewing the steps to do that (I will most likely kill the
+Sysadmins group and copy the forums users from the LDAP sysadmin group
+into this Administrators group).
+ - this is for forums.mageia.org/en/ ; forums.mageia.org/de/ should be
+managed in the same way, but we need someone to relay the discussion
+in German.
+
+Comments?
+
+r.
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004282.html b/zarb-ml/mageia-sysadm/2012-March/004282.html new file mode 100644 index 000000000..9fe064028 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004282.html @@ -0,0 +1,93 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Oliver Burger + oliver.bgr at googlemail.com +
+ Wed Mar 21 15:10:40 CET 2012 +

+
+ +
Am 21.03.2012 14:57, schrieb Romain d'Alverny:
+> Hi there (xpost sysadmins and forums-discuss lists),
+>
+> following the steps in
+> https://ml.mageia.org/l/arc/council/2012-03/msg00115.html I'm going to
+> update the forums groups for sysadmin members. The culprit is that
+> it's not in sync with LDAP so far, so it's to be manually updated.
+>
+> Targetted situation:
+>   - forum _technical_ management people =>  sysadmin (includes updating
+> the code base, reviewing and applying patches)
+>   - forum administration (roles, configuration, all that can be done
+> through the Web interface, interfacing with sysadmin) =>  someone still
+> to step up
+>   - we don't touch to user-defined groups by default (although I'm not
+> sure Packagers/Sysadmins ones are really needed/used - they are not in
+> sync either - but this should be dealt with future forum)
+>   - we use the Administrators group to manage who gets to fully manage
+> the forums (there's an extra higher level for that, but not accessible
+> to anyone at this time). Sysadmin members are members of this group.
+> I'm reviewing the steps to do that (I will most likely kill the
+> Sysadmins group and copy the forums users from the LDAP sysadmin group
+> into this Administrators group).
+>   - this is for forums.mageia.org/en/ ; forums.mageia.org/de/ should be
+> managed in the same way, but we need someone to relay the discussion
+> in German.
+Currently I am the admin of the de forums, and I am reading here.
+We do need only three groups in de forums:
+"admin, global moderator, registered user"
+I needed the admin rights exactly once, to ban a spammer. But it should 
+be possible to do that without filing a bug report assigned to the 
+sysadmins.
+
+Oliver
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004283.html b/zarb-ml/mageia-sysadm/2012-March/004283.html new file mode 100644 index 000000000..b782e6f9e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004283.html @@ -0,0 +1,100 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Wed Mar 21 15:20:46 CET 2012 +

+
+ +
2012/3/21 Oliver Burger <oliver.bgr at googlemail.com>:
+> Am 21.03.2012 14:57, schrieb Romain d'Alverny:
+>
+>> Hi there (xpost sysadmins and forums-discuss lists),
+>>
+>> following the steps in
+>> https://ml.mageia.org/l/arc/council/2012-03/msg00115.html I'm going to
+>> update the forums groups for sysadmin members. The culprit is that
+>> it's not in sync with LDAP so far, so it's to be manually updated.
+>>
+>> Targetted situation:
+>>  - forum _technical_ management people =>  sysadmin (includes updating
+>> the code base, reviewing and applying patches)
+>>  - forum administration (roles, configuration, all that can be done
+>> through the Web interface, interfacing with sysadmin) =>  someone still
+>> to step up
+>>  - we don't touch to user-defined groups by default (although I'm not
+>> sure Packagers/Sysadmins ones are really needed/used - they are not in
+>> sync either - but this should be dealt with future forum)
+>>  - we use the Administrators group to manage who gets to fully manage
+>> the forums (there's an extra higher level for that, but not accessible
+>> to anyone at this time). Sysadmin members are members of this group.
+>> I'm reviewing the steps to do that (I will most likely kill the
+>> Sysadmins group and copy the forums users from the LDAP sysadmin group
+>> into this Administrators group).
+>>  - this is for forums.mageia.org/en/ ; forums.mageia.org/de/ should be
+>> managed in the same way, but we need someone to relay the discussion
+>> in German.
+>
+> Currently I am the admin of the de forums, and I am reading here.
+> We do need only three groups in de forums:
+> "admin, global moderator, registered user"
+> I needed the admin rights exactly once, to ban a spammer. But it should be
+> possible to do that without filing a bug report assigned to the sysadmins.
+
+As you are already admin you have full access to all levels. Except if
+maât changed the default permissions. I did not see any such missing
+rights nor any "extra level".
+
+-- 
+wobo
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004284.html b/zarb-ml/mageia-sysadm/2012-March/004284.html new file mode 100644 index 000000000..d501d1a14 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004284.html @@ -0,0 +1,103 @@ + + + + [Mageia-sysadm] [forums-discuss] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] updating sysadmin privileges in forum config

+ isadora + isis2000 at gmail.com +
+ Wed Mar 21 17:07:06 CET 2012 +

+
+ +
Merci, d'accord.
+
+*~isadora*
+
+2012/3/21 Romain d'Alverny <rdalverny at gmail.com>
+
+> Hi there (xpost sysadmins and forums-discuss lists),
+>
+> following the steps in
+> https://ml.mageia.org/l/arc/council/2012-03/msg00115.html I'm going to
+> update the forums groups for sysadmin members. The culprit is that
+> it's not in sync with LDAP so far, so it's to be manually updated.
+>
+> Targetted situation:
+>  - forum _technical_ management people => sysadmin (includes updating
+> the code base, reviewing and applying patches)
+>  - forum administration (roles, configuration, all that can be done
+> through the Web interface, interfacing with sysadmin) => someone still
+> to step up
+>  - we don't touch to user-defined groups by default (although I'm not
+> sure Packagers/Sysadmins ones are really needed/used - they are not in
+> sync either - but this should be dealt with future forum)
+>  - we use the Administrators group to manage who gets to fully manage
+> the forums (there's an extra higher level for that, but not accessible
+> to anyone at this time). Sysadmin members are members of this group.
+> I'm reviewing the steps to do that (I will most likely kill the
+> Sysadmins group and copy the forums users from the LDAP sysadmin group
+> into this Administrators group).
+>  - this is for forums.mageia.org/en/ ; forums.mageia.org/de/ should be
+> managed in the same way, but we need someone to relay the discussion
+> in German.
+>
+> Comments?
+>
+> r.
+>
+
+
+
+-- 
+*We are shaped by our thoughts, we become what we think.*
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120321/1fe3aaa0/attachment.html>
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004285.html b/zarb-ml/mageia-sysadm/2012-March/004285.html new file mode 100644 index 000000000..a11749253 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004285.html @@ -0,0 +1,88 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Romain d'Alverny + rdalverny at gmail.com +
+ Wed Mar 21 17:18:43 CET 2012 +

+
+ +
On Wed, Mar 21, 2012 at 14:57, Romain d'Alverny <rdalverny at gmail.com> wrote:
+> [...]
+
+Steps taken so far (removing one level of indirection):
+ * Sysadmins group:
+   - removed;
+ * Administrators group:
+   - added sysadmin members who have not bee inactive for too long; I
+still didn't look up full sysadmins list for that, but this can now be
+managed by them directly;
+   - added boklm as leader;
+   - removed ash who has not been active in the forum and the project
+for several months;
+   - don't know what to do with forumadmin user (neither what it's for);
+ * Moderators group:
+   - demoted ash from leadership for the same reason.
+
+(as a reminder, this is not going to change at all how forum
+moderators already operate).
+
+So now:
+ - sysadmin members can organize to manage, update and answer forum
+admin & moderators, from code to deployment to online config;
+ - it's up to a volunteer to get the forum admin role and coordinate
+with moderators and sysadmins; s/he will have to be promoted in
+Administrators and Moderators groups;
+ - all groups, you decide then how you operate for the best.
+
+r.
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004286.html b/zarb-ml/mageia-sysadm/2012-March/004286.html new file mode 100644 index 000000000..7eeb5f842 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004286.html @@ -0,0 +1,73 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Wed Mar 21 17:32:03 CET 2012 +

+
+ +
2012/3/21 Romain d'Alverny <rdalverny at gmail.com>:
+> On Wed, Mar 21, 2012 at 14:57, Romain d'Alverny <rdalverny at gmail.com> wrote:
+>   - don't know what to do with forumadmin user (neither what it's for);
+
+forumadmin is implemented by the forum software if the person who
+installs the software for the first time does not care to set
+"forumadmin = maât". You can safely let this entry stay where it is,
+or remove it.
+Important is: one of the admins should also be marked as "founder" (I
+do not mean the "founder" group as created by maât, but "the user who
+has funded the forum").
+
+-- 
+wobo
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004287.html b/zarb-ml/mageia-sysadm/2012-March/004287.html new file mode 100644 index 000000000..4e10cfdff --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004287.html @@ -0,0 +1,79 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Wed Mar 21 17:34:21 CET 2012 +

+
+ +
2012/3/21 Wolfgang Bornath <molch.b at googlemail.com>:
+> 2012/3/21 Romain d'Alverny <rdalverny at gmail.com>:
+>>   - don't know what to do with forumadmin user (neither what it's for);
+>
+> forumadmin is implemented by the forum software if the person who
+> installs the software for the first time does not care to set
+> "forumadmin = maât". You can safely let this entry stay where it is,
+> or remove it.
+> Important is: one of the admins should also be marked as "founder" (I
+> do not mean the "founder" group as created by maât, but "the user who
+> has funded the forum").
+
+Sorry, last sentence should read:
+"but the "user who has founded the forum"
+
+:)
+
+-- 
+wobo
+
+ + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004288.html b/zarb-ml/mageia-sysadm/2012-March/004288.html new file mode 100644 index 000000000..e56963f0a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004288.html @@ -0,0 +1,175 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Maât + maat-ml at vilarem.net +
+ Wed Mar 21 20:09:35 CET 2012 +

+
+ +
On 21/03/2012 14:57, Romain d'Alverny wrote:
+> Hi there (xpost sysadmins and forums-discuss lists),
+>
+> following the steps in
+> https://ml.mageia.org/l/arc/council/2012-03/msg00115.html I'm going to
+> update the forums groups for sysadmin members. The culprit is that
+> it's not in sync with LDAP so far, so it's to be manually updated.
+It's already been done for all sysadmins who asked for it or simply 
+needed that at least once.
+
+And they not only were put as administrator but also as forum-founders.
+
+That's why you're able to do this privileges update... i did set you 
+forum-founder and that's in the straight line of what's already been 
+done from the beginning.
+
+For LDAP technical sync i already explained that we could use Talend 
+Jobs to get privileges and roles from LDAP and push them to the forum 
+without needing a heavy code change. Once per day or once per hour or 
+triggered on LDAP change...
+
+> Targetted situation:
+>   - forum _technical_ management people =>  sysadmin (includes updating
+> the code base, reviewing and applying patches)
+>   - forum administration (roles, configuration, all that can be done
+> through the Web interface, interfacing with sysadmin) =>  someone still
+> to step up
+
+I already explained that separating these roles would bring no good... a 
+pure "interface forum admin" is an emasculated admin... nearly useless. 
+Without the ability of administrating the database at a low level adding 
+indexes for tuning, optimizing cache and that sort of things, getting 
+data from apache logs and various things to lock spammers without 
+loading the system, without all these tasks a forum admin is, in facts, 
+not a forum admin but just a figurine... beautiful in a glass case if in 
+line with adornment ^^
+
+But useless... or nearly. Well not totally... can still promote 
+moderators or do moderations tasks as a "supermoderator" if in need of 
+flattering image... once a while add a forum or tweak a few things 
+(missing privileges, tweak thresholds or various subtle parameters).
+
+But such a half-admin used this way gives 5% of what he could bring to 
+the community through the forums.
+
+>   - we don't touch to user-defined groups by default (although I'm not
+> sure Packagers/Sysadmins ones are really needed/used - they are not in
+> sync either - but this should be dealt with future forum)
+They could be of great use... i wont explain again why and how.
+
+>   - we use the Administrators group to manage who gets to fully manage
+> the forums (there's an extra higher level for that, but not accessible
+> to anyone at this time). Sysadmin members are members of this group.
+> I'm reviewing the steps to do that (I will most likely kill the
+> Sysadmins group and copy the forums users from the LDAP sysadmin group
+> into this Administrators group).
+Well really that will not change the face of the world. The 2 groups 
+were separated because some sysadmins seemed so unwilling to deal with 
+forums that having the 2 could allow to have some shown as sysadmin to 
+anwser sysadmin things without having forum-admin privileges.
+
+But if nobody cares you can simplify. Nothing will change in the world 
+but you'll have removed a group in the footer of the forum.
+
+>   - this is for forums.mageia.org/en/ ; forums.mageia.org/de/ should be
+> managed in the same way, but we need someone to relay the discussion
+> in German.
+>
+> Comments?
+>
+> r.
+>
+Oliver already answered about that.
+
+Just one comment : You could ask me for that change (You could try just 
+for the fun of it on irc: maat on freenode)... it would be done in 
+seconds without side effect. You could even ask for LDAP sync or perhaps 
+one or two more things who knows ?
+
+m.
+
+-- 
+Life is magic... at least it would be if...
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004289.html b/zarb-ml/mageia-sysadm/2012-March/004289.html new file mode 100644 index 000000000..64669499a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004289.html @@ -0,0 +1,120 @@ + + + + [Mageia-sysadm] updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] updating sysadmin privileges in forum config

+ Maât + maat-ml at vilarem.net +
+ Wed Mar 21 20:39:01 CET 2012 +

+
+ +
On 21/03/2012 17:18, Romain d'Alverny wrote:
+> On Wed, Mar 21, 2012 at 14:57, Romain d'Alverny<rdalverny at gmail.com>  wrote:
+>> [...]
+> Steps taken so far (removing one level of indirection):
+>   * Sysadmins group:
+>     - removed;
+>   * Administrators group:
+>     - added sysadmin members who have not bee inactive for too long; I
+> still didn't look up full sysadmins list for that, but this can now be
+> managed by them directly;
+>     - added boklm as leader;
+>     - removed ash who has not been active in the forum and the project
+> for several months;
+>     - don't know what to do with forumadmin user (neither what it's for);
+It's the first user created at install: it was used to create the other 
+admins with forum-founder bit set up (included yours)
+
+This account should not be used except for crash recovery or things like 
+that (login impossible until ldap connexion is disengaged or an matching 
+user is created in LDAP directory)
+
+>   * Moderators group:
+>     - demoted ash from leadership for the same reason.
+>
+> (as a reminder, this is not going to change at all how forum
+> moderators already operate).
+>
+> So now:
+>   - sysadmin members can organize to manage, update and answer forum
+> admin&  moderators, from code to deployment to online config;
+>   - it's up to a volunteer to get the forum admin role and coordinate
+> with moderators and sysadmins; s/he will have to be promoted in
+> Administrators and Moderators groups;
+>   - all groups, you decide then how you operate for the best.
+>
+> r.
+
+There are 2 things that were not adressed :
+
+  * Separation of forum administration on several "roles" which... oh
+    well forget about it... saying it once more will only demoralize
+    me... so let's do as if i did say nothing :-/
+  * Lack of PHP/PHPBB coding skills... Once that solved i'd fear to see
+    mongers and python experts reviewing PHPBB hacks... by the way
+    testing them in a testbed without a copy of the real database...
+    pushing them blindly with git and asking if a sysadmin could find 2
+    minutes to push them on the actives forums... waiting for the
+    mail/whatever notification to click on the interfaces (of each... a
+    chance we have only 2 of them) and run the update process (praying
+    god that everything will go as expected because the rollback given
+    this way of doing things is just something that you don't want to
+    get into)
+
+That's what i already pointed... half an admin... bound and 
+distrusted... as useful as the ties allow to be (iow not very much).
+
+(sigh)
+
+-- 
+Life is magic... or at least it would be if...
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004290.html b/zarb-ml/mageia-sysadm/2012-March/004290.html new file mode 100644 index 000000000..ec1fc03b9 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004290.html @@ -0,0 +1,82 @@ + + + + [Mageia-sysadm] twiska.zarb.org mirror + + + + + + + + + +

[Mageia-sysadm] twiska.zarb.org mirror

+ David W. Hodgins + davidwhodgins at gmail.com +
+ Wed Mar 21 21:47:37 CET 2012 +

+
+ +
On Wed, 21 Mar 2012 05:30:00 -0400, Pascal Terjan <pterjan at gmail.com> wrote:
+
+> On Wed, Mar 21, 2012 at 06:35, David W. Hodgins <davidwhodgins at gmail.com>wrote:
+>
+>> For at least the last 12 hours, with mgaapplet, I've been getting ...
+>> Installation failed, some files are missing:
+>>    http://twiska.zarb.org/mageia/**distrib/1/i586/media/core/**
+>> updates_testing/nautilus-**dropbox-0.7.1-1.22.mga1.i586.**rpm<http://twiska.zarb.org/mageia/distrib/1/i586/media/core/updates_testing/nautilus-dropbox-0.7.1-1.22.mga1.i586.rpm>
+>>
+>> Is this a problem with this mirror, or is there a problem
+>> getting the i586 packages out?
+>>
+>
+> I saw someone requesting to remove a nautilus-dropbox from updates_testing,
+> maybe the person who did it did not update the hdlists
+
+Strange.  It's currently undergoing qa testing for
+https://bugs.mageia.org/show_bug.cgi?id=3641
+
+Seems to have been sorted out about two hours ago, though.
+Mar 21 15:02:01 hodgins perl: [RPM] nautilus-dropbox-0.7.1-1.2.mga1.nonfree.i586 installed
+
+Looks like the .22 change to .2, was needed to fix it.
+
+Thanks, Dave Hodgins
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004291.html b/zarb-ml/mageia-sysadm/2012-March/004291.html new file mode 100644 index 000000000..73b118b3d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004291.html @@ -0,0 +1,141 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Florian Hubold + doktor5000 at arcor.de +
+ Wed Mar 21 22:17:24 CET 2012 +

+
+ +
Am 21.03.2012 20:39, schrieb Maât:
+> On 21/03/2012 17:18, Romain d'Alverny wrote:
+>> On Wed, Mar 21, 2012 at 14:57, Romain d'Alverny<rdalverny at gmail.com>  wrote:
+>>> [...]
+>> Steps taken so far (removing one level of indirection):
+>>   * Sysadmins group:
+>>     - removed;
+>>   * Administrators group:
+>>     - added sysadmin members who have not bee inactive for too long; I
+>> still didn't look up full sysadmins list for that, but this can now be
+>> managed by them directly;
+>>     - added boklm as leader;
+>>     - removed ash who has not been active in the forum and the project
+>> for several months;
+>>     - don't know what to do with forumadmin user (neither what it's for);
+> It's the first user created at install: it was used to create the other
+> admins with forum-founder bit set up (included yours)
+>
+> This account should not be used except for crash recovery or things like that
+> (login impossible until ldap connexion is disengaged or an matching user is
+> created in LDAP directory)
+>
+>>   * Moderators group:
+>>     - demoted ash from leadership for the same reason.
+>>
+>> (as a reminder, this is not going to change at all how forum
+>> moderators already operate).
+>>
+>> So now:
+>>   - sysadmin members can organize to manage, update and answer forum
+>> admin&  moderators, from code to deployment to online config;
+>>   - it's up to a volunteer to get the forum admin role and coordinate
+>> with moderators and sysadmins; s/he will have to be promoted in
+>> Administrators and Moderators groups;
+>>   - all groups, you decide then how you operate for the best.
+>>
+>> r.
+>
+> There are 2 things that were not adressed :
+>
+>  * Separation of forum administration on several "roles" which... oh
+>    well forget about it... saying it once more will only demoralize
+>    me... so let's do as if i did say nothing :-/
+>  * Lack of PHP/PHPBB coding skills... Once that solved i'd fear to see
+>    mongers and python experts reviewing PHPBB hacks... by the way
+>    testing them in a testbed without a copy of the real database...
+>    pushing them blindly with git and asking if a sysadmin could find 2
+>    minutes to push them on the actives forums... waiting for the
+>    mail/whatever notification to click on the interfaces (of each... a
+>    chance we have only 2 of them) and run the update process (praying
+>    god that everything will go as expected because the rollback given
+>    this way of doing things is just something that you don't want to
+>    get into)
+>
+> That's what i already pointed... half an admin... bound and distrusted... as
+> useful as the ties allow to be (iow not very much).
+
+Sorry, just can't resist. You wrote in the other mail:
+
+> I already explained that separating these roles would bring no good... a pure
+> "interface forum admin" is an emasculated admin... nearly useless. Without
+> the ability of administrating the database at a low level adding indexes for
+> tuning, optimizing cache and that sort of things, getting data from apache
+> logs and various things to lock spammers without loading the system, without
+> all these tasks a forum admin is, in facts, not a forum admin but just a
+> figurine... beautiful in a glass case if in line with adornment ^^ 
+On the other hand, what's an admin who does nothing except
+being absent, not even doing forum software security updates?
+These arguments from you are just laughable to me, sorry, but i,
+for one, rather like to be true than to bite my lips.
+
+For a real world example, we have a few of such pure "emasculated"
+interface forum admins as moderators at mandrivauser.de, and it's
+perfectly enough to care for the day-to-day forum business.
+But you seem to know much better, that's maybe also the reason
+why the int. Mageia forum is currently doing so well overall.
+
+But i'll refrain to go on about this, to keep my blood pressure at sane levels.
+
+>
+> (sigh)
+>
+Exactly.
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004292.html b/zarb-ml/mageia-sysadm/2012-March/004292.html new file mode 100644 index 000000000..1e14d3778 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004292.html @@ -0,0 +1,154 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Wed Mar 21 23:34:24 CET 2012 +

+
+ +
2012/3/21 Florian Hubold <doktor5000 at arcor.de>:
+> Am 21.03.2012 20:39, schrieb Maât:
+>> On 21/03/2012 17:18, Romain d'Alverny wrote:
+>>> On Wed, Mar 21, 2012 at 14:57, Romain d'Alverny<rdalverny at gmail.com>  wrote:
+>>>> [...]
+>>> Steps taken so far (removing one level of indirection):
+>>>   * Sysadmins group:
+>>>     - removed;
+>>>   * Administrators group:
+>>>     - added sysadmin members who have not bee inactive for too long; I
+>>> still didn't look up full sysadmins list for that, but this can now be
+>>> managed by them directly;
+>>>     - added boklm as leader;
+>>>     - removed ash who has not been active in the forum and the project
+>>> for several months;
+>>>     - don't know what to do with forumadmin user (neither what it's for);
+>> It's the first user created at install: it was used to create the other
+>> admins with forum-founder bit set up (included yours)
+>>
+>> This account should not be used except for crash recovery or things like that
+>> (login impossible until ldap connexion is disengaged or an matching user is
+>> created in LDAP directory)
+>>
+>>>   * Moderators group:
+>>>     - demoted ash from leadership for the same reason.
+>>>
+>>> (as a reminder, this is not going to change at all how forum
+>>> moderators already operate).
+>>>
+>>> So now:
+>>>   - sysadmin members can organize to manage, update and answer forum
+>>> admin&  moderators, from code to deployment to online config;
+>>>   - it's up to a volunteer to get the forum admin role and coordinate
+>>> with moderators and sysadmins; s/he will have to be promoted in
+>>> Administrators and Moderators groups;
+>>>   - all groups, you decide then how you operate for the best.
+>>>
+>>> r.
+>>
+>> There are 2 things that were not adressed :
+>>
+>>  * Separation of forum administration on several "roles" which... oh
+>>    well forget about it... saying it once more will only demoralize
+>>    me... so let's do as if i did say nothing :-/
+>>  * Lack of PHP/PHPBB coding skills... Once that solved i'd fear to see
+>>    mongers and python experts reviewing PHPBB hacks... by the way
+>>    testing them in a testbed without a copy of the real database...
+>>    pushing them blindly with git and asking if a sysadmin could find 2
+>>    minutes to push them on the actives forums... waiting for the
+>>    mail/whatever notification to click on the interfaces (of each... a
+>>    chance we have only 2 of them) and run the update process (praying
+>>    god that everything will go as expected because the rollback given
+>>    this way of doing things is just something that you don't want to
+>>    get into)
+>>
+>> That's what i already pointed... half an admin... bound and distrusted... as
+>> useful as the ties allow to be (iow not very much).
+>
+> Sorry, just can't resist. You wrote in the other mail:
+>
+>> I already explained that separating these roles would bring no good... a pure
+>> "interface forum admin" is an emasculated admin... nearly useless. Without
+>> the ability of administrating the database at a low level adding indexes for
+>> tuning, optimizing cache and that sort of things, getting data from apache
+>> logs and various things to lock spammers without loading the system, without
+>> all these tasks a forum admin is, in facts, not a forum admin but just a
+>> figurine... beautiful in a glass case if in line with adornment ^^
+> On the other hand, what's an admin who does nothing except
+> being absent, not even doing forum software security updates?
+> These arguments from you are just laughable to me, sorry, but i,
+> for one, rather like to be true than to bite my lips.
+>
+> For a real world example, we have a few of such pure "emasculated"
+> interface forum admins as moderators at mandrivauser.de, and it's
+> perfectly enough to care for the day-to-day forum business.
+> But you seem to know much better, that's maybe also the reason
+> why the int. Mageia forum is currently doing so well overall.
+>
+> But i'll refrain to go on about this, to keep my blood pressure at sane levels.
+>
+>>
+>> (sigh)
+>>
+> Exactly.
+
+Not much to add to this.
+maât, you haven't understood it many months ago, I'm not surprised
+that you don't understand it now. Setting up a forum can be done by
+somebody like you or any other guy with the necessary technical
+knowledge. Being a real admin in a forum involves more than that
+technical knowledge.
+
+But i'll refrain to go on about this, to save me from dieing of boredom.
+
+-- 
+wobo
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004293.html b/zarb-ml/mageia-sysadm/2012-March/004293.html new file mode 100644 index 000000000..cfbd63cb5 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004293.html @@ -0,0 +1,102 @@ + + + + [Mageia-sysadm] Access to ARM boards + + + + + + + + + +

[Mageia-sysadm] Access to ARM boards

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 22 00:24:00 CET 2012 +

+
+ +
Hello,
+
+The 2 Mageia ARM boards are currently connected to the network behind
+valstar, so access from outside is not possible directly.
+
+To give access to the boards to rtp, I forwarded ports 2221 and 2222
+from valstar to arm1 and arm2 sshd.
+
+To do this, the two following commands are run in screen "armbs" on
+valstar :
+ socat TCP-LISTEN:2221,fork,reuseaddr,su=nobody TCP4:arm1:22
+ socat TCP-LISTEN:2222,fork,reuseaddr,su=nobody TCP4:arm2:22
+
+(so we will need to restart this after a reboot, or find a better
+solution to do it)
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004294.html b/zarb-ml/mageia-sysadm/2012-March/004294.html new file mode 100644 index 000000000..bd96d0b9f --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004294.html @@ -0,0 +1,134 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Thu Mar 22 07:21:53 CET 2012 +

+
+ +
On 21/03/12 23:34, Wolfgang Bornath wrote:
+> 2012/3/21 Florian Hubold<doktor5000 at arcor.de>:
+>> Am 21.03.2012 20:39, schrieb Maât:
+>>> On 21/03/2012 17:18, Romain d'Alverny wrote:
+>>>> On Wed, Mar 21, 2012 at 14:57, Romain d'Alverny<rdalverny at gmail.com>    wrote:
+>>>>> [...]
+>>>> Steps taken so far (removing one level of indirection):
+>>>>    * Sysadmins group:
+>>>>      - removed;
+>>>>    * Administrators group:
+>>>>      - added sysadmin members who have not bee inactive for too long; I
+>>>> still didn't look up full sysadmins list for that, but this can now be
+>>>> managed by them directly;
+>>>>      - added boklm as leader;
+>>>>      - removed ash who has not been active in the forum and the project
+>>>> for several months;
+>>>>      - don't know what to do with forumadmin user (neither what it's for);
+>>> It's the first user created at install: it was used to create the other
+>>> admins with forum-founder bit set up (included yours)
+>>>
+>>> This account should not be used except for crash recovery or things like that
+>>> (login impossible until ldap connexion is disengaged or an matching user is
+>>> created in LDAP directory)
+>>>
+>>>>    * Moderators group:
+>>>>      - demoted ash from leadership for the same reason.
+>>>>
+>>>> (as a reminder, this is not going to change at all how forum
+>>>> moderators already operate).
+>>>>
+>>>> So now:
+>>>>    - sysadmin members can organize to manage, update and answer forum
+>>>> admin&    moderators, from code to deployment to online config;
+>>>>    - it's up to a volunteer to get the forum admin role and coordinate
+>>>> with moderators and sysadmins; s/he will have to be promoted in
+>>>> Administrators and Moderators groups;
+>>>>    - all groups, you decide then how you operate for the best.
+>>>>
+>>>> r.
+>>> There are 2 things that were not adressed :
+>>>
+>>>   * Separation of forum administration on several "roles" which... oh
+>>>     well forget about it... saying it once more will only demoralize
+>>>     me... so let's do as if i did say nothing :-/
+>>>   * Lack of PHP/PHPBB coding skills... Once that solved i'd fear to see
+>>>     mongers and python experts reviewing PHPBB hacks... by the way
+>>>     testing them in a testbed without a copy of the real database...
+>>>     pushing them blindly with git and asking if a sysadmin could find 2
+>>>     minutes to push them on the actives forums... waiting for the
+>>>     mail/whatever notification to click on the interfaces (of each... a
+>>>     chance we have only 2 of them) and run the update process (praying
+>>>     god that everything will go as expected because the rollback given
+>>>     this way of doing things is just something that you don't want to
+>>>     get into)
+>>>
+>>> That's what i already pointed... half an admin... bound and distrusted... as
+>>> useful as the ties allow to be (iow not very much).
+>> Sorry, just can't resist. You wrote in the other mail:
+>>
+>>> I already explained that separating these roles would bring no good... a pure
+>>> "interface forum admin" is an emasculated admin... nearly useless. Without
+>>> the ability of administrating the database at a low level adding indexes for
+>>> tuning, optimizing cache and that sort of things, getting data from apache
+>>> logs and various things to lock spammers without loading the system, without
+>>> all these tasks a forum admin is, in facts, not a forum admin but just a
+>>> figurine... beautiful in a glass case if in line with adornment ^^
+>> On the other hand, what's an admin who does nothing except
+>> being absent, not even doing forum software security updates?
+
+TBH, Florian, I would have left completely if I had been him, but he is 
+still around.
+
+Can you please give a link to the updates you just mentioned?
+
+
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004295.html b/zarb-ml/mageia-sysadm/2012-March/004295.html new file mode 100644 index 000000000..165686564 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004295.html @@ -0,0 +1,76 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Thu Mar 22 08:05:48 CET 2012 +

+
+ +
On 22/03/12 07:21, Marja van Waes wrote:
+> On 21/03/12 23:34, Wolfgang Bornath wrote:
+>> 2012/3/21 Florian Hubold<doktor5000 at arcor.de>:
+>>> On the other hand, what's an admin who does nothing except
+>>> being absent, not even doing forum software security updates?
+>
+> TBH, Florian, I would have left completely if I had been him, but he 
+> is still around.
+>
+> Can you please give a link to the updates you just mentioned?
+>
+>
+>
+@ Maât
+
+If you already know which security updates Florian is talking about, 
+would you be willing and have time to do them?
+
+ + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004296.html b/zarb-ml/mageia-sysadm/2012-March/004296.html new file mode 100644 index 000000000..f9c77ca54 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004296.html @@ -0,0 +1,170 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Thu Mar 22 08:18:05 CET 2012 +

+
+ +
2012/3/22 Marja van Waes <marja11 at xs4all.nl>:
+> On 21/03/12 23:34, Wolfgang Bornath wrote:
+>>
+>> 2012/3/21 Florian Hubold<doktor5000 at arcor.de>:
+>>>
+>>> Am 21.03.2012 20:39, schrieb Maât:
+>>>>
+>>>> On 21/03/2012 17:18, Romain d'Alverny wrote:
+>>>>>
+>>>>> On Wed, Mar 21, 2012 at 14:57, Romain d'Alverny<rdalverny at gmail.com>
+>>>>>  wrote:
+>>>>>>
+>>>>>> [...]
+>>>>>
+>>>>> Steps taken so far (removing one level of indirection):
+>>>>>   * Sysadmins group:
+>>>>>     - removed;
+>>>>>   * Administrators group:
+>>>>>     - added sysadmin members who have not bee inactive for too long; I
+>>>>> still didn't look up full sysadmins list for that, but this can now be
+>>>>> managed by them directly;
+>>>>>     - added boklm as leader;
+>>>>>     - removed ash who has not been active in the forum and the project
+>>>>> for several months;
+>>>>>     - don't know what to do with forumadmin user (neither what it's
+>>>>> for);
+>>>>
+>>>> It's the first user created at install: it was used to create the other
+>>>> admins with forum-founder bit set up (included yours)
+>>>>
+>>>> This account should not be used except for crash recovery or things like
+>>>> that
+>>>> (login impossible until ldap connexion is disengaged or an matching user
+>>>> is
+>>>> created in LDAP directory)
+>>>>
+>>>>>   * Moderators group:
+>>>>>     - demoted ash from leadership for the same reason.
+>>>>>
+>>>>> (as a reminder, this is not going to change at all how forum
+>>>>> moderators already operate).
+>>>>>
+>>>>> So now:
+>>>>>   - sysadmin members can organize to manage, update and answer forum
+>>>>> admin&    moderators, from code to deployment to online config;
+>>>>>   - it's up to a volunteer to get the forum admin role and coordinate
+>>>>> with moderators and sysadmins; s/he will have to be promoted in
+>>>>> Administrators and Moderators groups;
+>>>>>   - all groups, you decide then how you operate for the best.
+>>>>>
+>>>>> r.
+>>>>
+>>>> There are 2 things that were not adressed :
+>>>>
+>>>>  * Separation of forum administration on several "roles" which... oh
+>>>>    well forget about it... saying it once more will only demoralize
+>>>>    me... so let's do as if i did say nothing :-/
+>>>>  * Lack of PHP/PHPBB coding skills... Once that solved i'd fear to see
+>>>>    mongers and python experts reviewing PHPBB hacks... by the way
+>>>>    testing them in a testbed without a copy of the real database...
+>>>>    pushing them blindly with git and asking if a sysadmin could find 2
+>>>>    minutes to push them on the actives forums... waiting for the
+>>>>    mail/whatever notification to click on the interfaces (of each... a
+>>>>    chance we have only 2 of them) and run the update process (praying
+>>>>    god that everything will go as expected because the rollback given
+>>>>    this way of doing things is just something that you don't want to
+>>>>    get into)
+>>>>
+>>>> That's what i already pointed... half an admin... bound and
+>>>> distrusted... as
+>>>> useful as the ties allow to be (iow not very much).
+>>>
+>>> Sorry, just can't resist. You wrote in the other mail:
+>>>
+>>>> I already explained that separating these roles would bring no good... a
+>>>> pure
+>>>> "interface forum admin" is an emasculated admin... nearly useless.
+>>>> Without
+>>>> the ability of administrating the database at a low level adding indexes
+>>>> for
+>>>> tuning, optimizing cache and that sort of things, getting data from
+>>>> apache
+>>>> logs and various things to lock spammers without loading the system,
+>>>> without
+>>>> all these tasks a forum admin is, in facts, not a forum admin but just a
+>>>> figurine... beautiful in a glass case if in line with adornment ^^
+>>>
+>>> On the other hand, what's an admin who does nothing except
+>>> being absent, not even doing forum software security updates?
+>
+>
+> TBH, Florian, I would have left completely if I had been him, but he is
+> still around.
+>
+> Can you please give a link to the updates you just mentioned?
+
+He is talking about the update of the forum software phpBB3. The
+version used at Mageia is outdated since summer 2011. New versions of
+phpBB3 almost always are caused by security issues. This has been
+mentioned several times in the forum threads. The point is that the
+implementation of the forum software at Mageia (involving puppet,
+etc.) was done this way to "ease forum software maintenance" (quoting
+maât). :)
+
+And yes, TBH as well, Marja, after the forums were installed last year
+it would not have made much difference if maât had left completely a
+year ago.
+
+-- 
+wobo
+
+ + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004297.html b/zarb-ml/mageia-sysadm/2012-March/004297.html new file mode 100644 index 000000000..cadb57335 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004297.html @@ -0,0 +1,86 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Thu Mar 22 08:20:07 CET 2012 +

+
+ +
2012/3/22 Marja van Waes <marja11 at xs4all.nl>:
+> On 22/03/12 07:21, Marja van Waes wrote:
+>>
+>> On 21/03/12 23:34, Wolfgang Bornath wrote:
+>>>
+>>> 2012/3/21 Florian Hubold<doktor5000 at arcor.de>:
+>>>>
+>>>> On the other hand, what's an admin who does nothing except
+>>>>
+>>>> being absent, not even doing forum software security updates?
+>>
+>>
+>> TBH, Florian, I would have left completely if I had been him, but he is
+>> still around.
+>>
+>> Can you please give a link to the updates you just mentioned?
+>>
+>>
+>>
+> @ Maât
+>
+> If you already know which security updates Florian is talking about, would
+> you be willing and have time to do them?
+
+He knows for a long time, he has been asked about this months ago.
+
+-- 
+wobo
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004298.html b/zarb-ml/mageia-sysadm/2012-March/004298.html new file mode 100644 index 000000000..dc93b6c0e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004298.html @@ -0,0 +1,66 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ nicolas vigier + boklm at mars-attacks.org +
+ Thu Mar 22 08:37:52 CET 2012 +

+
+ +
On Thu, 22 Mar 2012, Marja van Waes wrote:
+
+>
+> If you already know which security updates Florian is talking about, would 
+> you be willing and have time to do them?
+
+forums setup will be managed by sysadmin team now, so we will look at
+this soon. First testing the update on a VM then do it on the server.
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004299.html b/zarb-ml/mageia-sysadm/2012-March/004299.html new file mode 100644 index 000000000..99ecb91db --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004299.html @@ -0,0 +1,80 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Thu Mar 22 10:27:42 CET 2012 +

+
+ +
On 22/03/12 08:18, Wolfgang Bornath wrote:
+> 2012/3/22 Marja van Waes<marja11 at xs4all.nl>:
+>>
+>>
+>> TBH, Florian, I would have left completely if I had been him, but he is
+>> still around.
+>>
+>
+> And yes, TBH as well, Marja, after the forums were installed last year
+> it would not have made much difference if maât had left completely a
+> year ago.
+>
+So it was wrong of me to say that, because apparently it helps polarisation.
+
+:(
+
+I feel rotten, I very much like you all, including Maât.
+
+
+
+
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004300.html b/zarb-ml/mageia-sysadm/2012-March/004300.html new file mode 100644 index 000000000..064f1a823 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004300.html @@ -0,0 +1,88 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Thu Mar 22 10:44:46 CET 2012 +

+
+ +
2012/3/22 Marja van Waes <marja11 at xs4all.nl>:
+> On 22/03/12 08:18, Wolfgang Bornath wrote:
+>>
+>> 2012/3/22 Marja van Waes<marja11 at xs4all.nl>:
+>>>
+>>>
+>>>
+>>> TBH, Florian, I would have left completely if I had been him, but he is
+>>> still around.
+>>>
+>>
+>> And yes, TBH as well, Marja, after the forums were installed last year
+>> it would not have made much difference if maât had left completely a
+>> year ago.
+>>
+> So it was wrong of me to say that, because apparently it helps polarisation.
+>
+> :(
+>
+> I feel rotten, I very much like you all, including Maât.
+
+Don't feel bad - after all this is not a matter of "liking" a person
+or not. There are people who I do not like but I'd never write
+something bad about them as long as they are doing their "job". OTOH I
+would suggest to somebody to quit if he does not do his job, whether I
+like him or not. This is what it's about, nothing else. It's not a
+personal or even emotional matter.
+
+-- 
+wobo
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004301.html b/zarb-ml/mageia-sysadm/2012-March/004301.html new file mode 100644 index 000000000..caa01aad6 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004301.html @@ -0,0 +1,114 @@ + + + + [Mageia-sysadm] Access to ARM boards + + + + + + + + + +

[Mageia-sysadm] Access to ARM boards

+ Arnaud Patard (Rtp) + arnaud.patard at rtp-net.org +
+ Thu Mar 22 15:27:55 CET 2012 +

+
+ +
nicolas vigier <boklm at mars-attacks.org> writes:
+
+> Hello,
+Hi,
+
+>
+> The 2 Mageia ARM boards are currently connected to the network behind
+> valstar, so access from outside is not possible directly.
+>
+> To give access to the boards to rtp, I forwarded ports 2221 and 2222
+> from valstar to arm1 and arm2 sshd.
+
+Thanks, I've managed to connect to them but it looks like there's no
+connectivity. It's a little bit annoying as this means:
+
+- wrong date. QSB boards don't have any battery for rtc so they're
+currently in 1970 :)
+- no way to rsync somewhere my repo. imho, mageia systems should be the
+primary mirror for arm stuff.
+
+>
+> To do this, the two following commands are run in screen "armbs" on
+> valstar :
+>  socat TCP-LISTEN:2221,fork,reuseaddr,su=nobody TCP4:arm1:22
+>  socat TCP-LISTEN:2222,fork,reuseaddr,su=nobody TCP4:arm2:22
+>
+> (so we will need to restart this after a reboot, or find a better
+> solution to do it)
+
+maybe ipv6 ?
+
+Thanks,
+Arnaud
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004302.html b/zarb-ml/mageia-sysadm/2012-March/004302.html new file mode 100644 index 000000000..b8e354723 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004302.html @@ -0,0 +1,109 @@ + + + + [Mageia-sysadm] About the old HDDs we changed in February + + + + + + + + + +

[Mageia-sysadm] About the old HDDs we changed in February

+ Damien Lallement + mageia at damsweb.net +
+ Thu Mar 22 17:44:10 CET 2012 +

+
+ +
Hi Team!
+
+FYI, I tested the three HDD we removed with rtp, misc, boklm and I when 
+we went to Marseille in February. The test was to send HDD to Western 
+Digital for an exchange (5y waranty).
+I used:
+- smartctl --test=long /dev/sdX
+- UBCD and Western Digital tool for extended Smart test and low format
+
+In fact... The three HDD are safe! None is having issue as smartmontools 
+was reporting it on ecosse or valstar...
+My idea is that the Mandriva kernel was having an issue reporting smart 
+info or the controler of the servers was having problems.
+But if it was the second option, why don't we have smart error anymore 
+now with Mageia 1 and new HDDs?
+
+So, the old HDD are now part of Mageia.Org spare hardware.
+- WD1002FAEX
+- WD1002FAEX
+- WD2001FASS
+
+I will launch a full smart test tomorrow on all the HDDs of our BS.
+I will keep you in touch if something is going wrong.
+
+Dams
+-- 
+Damien Lallement
+twitter: damsweb - IRC: damsweb/coincoin
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004303.html b/zarb-ml/mageia-sysadm/2012-March/004303.html new file mode 100644 index 000000000..1fac41eb2 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004303.html @@ -0,0 +1,106 @@ + + + + [Mageia-sysadm] Access to ARM boards + + + + + + + + + +

[Mageia-sysadm] Access to ARM boards

+ Michael Scherer + misc at zarb.org +
+ Thu Mar 22 18:55:08 CET 2012 +

+
+ +
Le jeudi 22 mars 2012 à 00:24 +0100, nicolas vigier a écrit :
+> Hello,
+> 
+> The 2 Mageia ARM boards are currently connected to the network behind
+> valstar, so access from outside is not possible directly.
+> 
+> To give access to the boards to rtp, I forwarded ports 2221 and 2222
+> from valstar to arm1 and arm2 sshd.
+>
+> To do this, the two following commands are run in screen "armbs" on
+> valstar :
+>  socat TCP-LISTEN:2221,fork,reuseaddr,su=nobody TCP4:arm1:22
+>  socat TCP-LISTEN:2222,fork,reuseaddr,su=nobody TCP4:arm2:22
+> 
+> (so we will need to restart this after a reboot, or find a better
+> solution to do it)
+
+I am still amazed to see that no one ever know xinetd can do that since
+years 
+http://adamantsys.com/node/116
+
+and people always take the more complex way of either using socat,
+netcat, iptables, or complex tunnel system.
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004304.html b/zarb-ml/mageia-sysadm/2012-March/004304.html new file mode 100644 index 000000000..aef70d72e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004304.html @@ -0,0 +1,90 @@ + + + + [Mageia-sysadm] Access to ARM boards + + + + + + + + + +

[Mageia-sysadm] Access to ARM boards

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Mar 22 19:59:08 CET 2012 +

+
+ +
On Thu, Mar 22, 2012 at 14:27, Arnaud Patard <arnaud.patard at rtp-net.org>wrote:
+
+>
+> - no way to rsync somewhere my repo. imho, mageia systems should be the
+> primary mirror for arm stuff.
+
+
+I think valstar should be the reference.
+Maybe we can add a module on rsync server with you IP is allowed to write to
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120322/fcf6a706/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004305.html b/zarb-ml/mageia-sysadm/2012-March/004305.html new file mode 100644 index 000000000..0dfa23df3 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004305.html @@ -0,0 +1,308 @@ + + + + [Mageia-sysadm] [sysadmin-commits] [2674] clean postfix module, rework the layout and split it in several file + + + + + + + + + +

[Mageia-sysadm] [sysadmin-commits] [2674] clean postfix module, rework the layout and split it in several file

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Mar 22 20:26:11 CET 2012 +

+
+ +
We seem to reject all mails to MLs on alamut:
+
+Mar 22 20:18:08 alamut postfix/smtpd[1384]: NOQUEUE: reject: RCPT from
+valstar.mageia.org[212.85.158.147]: 450 4.1.1 <
+packages-commits at ml.mageia.org>: Recipient address rejected: User unknown
+in local recipient table; from=<schedbot at valstar.mageia.org> to=<
+packages-commits at ml.mageia.org> proto=ESMTP helo=<valstar.mageia.org>
+
+Mar 22 20:18:08 alamut postfix/smtpd[1385]: NOQUEUE: reject: RCPT from
+valstar.mageia.org[212.85.158.147]: 450 4.1.1 <changelog at ml.mageia.org>:
+Recipient address rejected: User unknown in local recipient table; from=<
+schedbot at valstar.mageia.org> to=<changelog at ml.mageia.org> proto=ESMTP helo=<
+valstar.mageia.org>
+
+Reported by AL13N as bugzilla fails to send email and gives an error
+
+On Thu, Mar 22, 2012 at 15:18, <root at mageia.org> wrote:
+
+> **
+>  Revision 2674 Author misc Date 2012-03-22 16:18:24 +0100 (Thu, 22 Mar
+> 2012) Log Message
+>
+> clean postfix module, rework the layout and split it in several file
+>
+> Modified Paths
+>
+>    - puppet/manifests/nodes/alamut.pp<#1363afcdfc8acd3f_puppetmanifestsnodesalamutpp>
+>    - puppet/manifests/nodes/krampouezh.pp<#1363afcdfc8acd3f_puppetmanifestsnodeskrampouezhpp>
+>    - puppet/modules/postfix/manifests/init.pp<#1363afcdfc8acd3f_puppetmodulespostfixmanifestsinitpp>
+>
+> Added Paths
+>
+>    - puppet/modules/postfix/manifests/server/
+>    - puppet/modules/postfix/manifests/server/primary.pp<#1363afcdfc8acd3f_puppetmodulespostfixmanifestsserverprimarypp>
+>    - puppet/modules/postfix/manifests/server/secondary.pp<#1363afcdfc8acd3f_puppetmodulespostfixmanifestsserversecondarypp>
+>    - puppet/modules/postfix/manifests/server.pp<#1363afcdfc8acd3f_puppetmodulespostfixmanifestsserverpp>
+>    - puppet/modules/postfix/manifests/simple_relay.pp<#1363afcdfc8acd3f_puppetmodulespostfixmanifestssimple_relaypp>
+>
+>  Modified: puppet/manifests/nodes/alamut.pp
+> ===================================================================
+> --- puppet/manifests/nodes/alamut.pp	2012-03-22 15:18:21 UTC (rev 2673)
+> +++ puppet/manifests/nodes/alamut.pp	2012-03-22 15:18:24 UTC (rev 2674)
+> @@ -20,7 +20,7 @@
+>      include transifex
+>      include bugzilla
+>      include sympa::server
+> -    include postfix::primary_smtp
+> +    include postfix::server::primary
+>
+>      # temporary, just the time the vm is running there
+>      host { 'friteuse':
+> Modified: puppet/manifests/nodes/krampouezh.pp
+> ===================================================================
+> --- puppet/manifests/nodes/krampouezh.pp	2012-03-22 15:18:21 UTC (rev 2673)
+> +++ puppet/manifests/nodes/krampouezh.pp	2012-03-22 15:18:24 UTC (rev 2674)
+> @@ -5,7 +5,7 @@
+>  #
+>      #include common::default_mageia_server
+>      include common::default_mageia_server_no_smtp
+> -    include postfix::secondary_smtp
+> +    include postfix::server::secondary
+>      include blog::base
+>      include blog::db_backup
+>      include mysql::server
+> Modified: puppet/modules/postfix/manifests/init.pp
+> ===================================================================
+> --- puppet/modules/postfix/manifests/init.pp	2012-03-22 15:18:21 UTC (rev 2673)
+> +++ puppet/modules/postfix/manifests/init.pp	2012-03-22 15:18:24 UTC (rev 2674)
+> @@ -1,71 +1,13 @@
+>  class postfix {
+> -    class base {
+> -        package { [postfix,nail]: }
+> +    package { ['postfix', 'nail']: }
+>
+> -        service { postfix:
+> -            subscribe => Package['postfix'],
+> -        }
+> -
+> -        file { '/etc/postfix/main.cf':
+> -            require => Package["postfix"],
+> -            content => "",
+> -            notify => Service['postfix'],
+> -        }
+> +    service { 'postfix':
+> +        subscribe => Package['postfix'],
+>      }
+>
+> -
+> -    class simple_relay inherits base {
+> -        File['/etc/postfix/main.cf'] {
+> -            content => template("postfix/simple_relay_main.cf"),
+> -        }
+> +    file { '/etc/postfix/main.cf':
+> +        require => Package['postfix'],
+> +        content => '',
+> +        notify  => Service['postfix'],
+>      }
+> -
+> -    class smtp_server inherits base {
+> -        include postgrey
+> -        include amavis
+> -        include spamassassin
+> -
+> -        File['/etc/postfix/main.cf'] {
+> -            content => template("postfix/main.cf"),
+> -        }
+> -
+> -        file { '/etc/postfix/transport_regexp':
+> -            content => template("postfix/transport_regexp"),
+> -        }
+> -
+> -    }
+> -
+> -    class primary_smtp inherits smtp_server {
+> -
+> -        package { "postfix-ldap": }
+> -
+> -        # council is here until we fully decide who has aliases in com team,
+> -        # see https://bugs.mageia.org/show_bug.cgi?id=1345
+> -        # alumini is a special group for tracking previous members of
+> -        # the project, so they keep their aliases for a time
+> -        $aliases_group = ['mga-founders','mga-packagers',
+> -                          'mga-sysadmin','mga-council',
+> -                          'mga-alumni','mga-i18n-committers',
+> -                         ]
+> -        $ldap_password = extlookup("postfix_ldap",'x')
+> -        $ldap_servers = get_ldap_servers()
+> -
+> -        file {
+> -            '/etc/postfix/master.cf': content => template("postfix/primary_master.cf");
+> -            '/etc/postfix/ldap_aliases.conf': content => template("postfix/ldap_aliases.conf");
+> -            # TODO merge the file with the previous one, for common part (ldap, etc)
+> -            '/etc/postfix/group_aliases.conf': content => template("postfix/group_aliases.conf");
+> -            # TODO make it conditional to the presence of sympa
+> -            '/etc/postfix/sympa_aliases': content => template("postfix/sympa_aliases");
+> -            '/etc/postfix/virtual_aliases': content => template("postfix/virtual_aliases");
+> -        }
+> -
+> -        exec { "postmap /etc/postfix/virtual_aliases":
+> -            refreshonly => true,
+> -            subscribe => File['/etc/postfix/virtual_aliases'],
+> -        }
+> -    }
+> -
+> -    class secondary_smtp inherits smtp_server {
+> -    }
+>  }
+> Added: puppet/modules/postfix/manifests/server/primary.pp
+> ===================================================================
+> --- puppet/modules/postfix/manifests/server/primary.pp	                        (rev 0)
+> +++ puppet/modules/postfix/manifests/server/primary.pp	2012-03-22 15:18:24 UTC (rev 2674)
+> @@ -0,0 +1,37 @@
+> +class postfix::server::primary inherits postfix::server {
+> +
+> +    package { 'postfix-ldap': }
+> +
+> +    # council is here until we fully decide who has aliases in com team,
+> +    # see https://bugs.mageia.org/show_bug.cgi?id=1345
+> +    # alumini is a special group for tracking previous members of
+> +    # the project, so they keep their aliases for a time
+> +    $aliases_group = ['mga-founders',
+> +                      'mga-packagers',
+> +                      'mga-sysadmin',
+> +                      'mga-council',
+> +                      'mga-alumni',
+> +                      'mga-i18n-committers']
+> +    $ldap_password = extlookup('postfix_ldap','x')
+> +    $ldap_servers = get_ldap_servers()
+> +
+> +    file {
+> +        '/etc/postfix/master.cf':
+> +            content => template('postfix/primary_master.cf');
+> +        '/etc/postfix/ldap_aliases.conf':
+> +            content => template('postfix/ldap_aliases.conf');
+> +        # TODO merge the file with the previous one, for common part (ldap, etc)
+> +        '/etc/postfix/group_aliases.conf':
+> +            content => template('postfix/group_aliases.conf');
+> +        # TODO make it conditional to the presence of sympa
+> +        '/etc/postfix/sympa_aliases':
+> +            content => template('postfix/sympa_aliases');
+> +        '/etc/postfix/virtual_aliases':
+> +            content => template('postfix/virtual_aliases');
+> +    }
+> +
+> +    exec { 'postmap /etc/postfix/virtual_aliases':
+> +        refreshonly => true,
+> +        subscribe   => File['/etc/postfix/virtual_aliases'],
+> +    }
+> +}
+> Added: puppet/modules/postfix/manifests/server/secondary.pp
+> ===================================================================
+> --- puppet/modules/postfix/manifests/server/secondary.pp	                        (rev 0)
+> +++ puppet/modules/postfix/manifests/server/secondary.pp	2012-03-22 15:18:24 UTC (rev 2674)
+> @@ -0,0 +1 @@
+> +class postfix::server::secondary inherits postfix::server { }
+> Added: puppet/modules/postfix/manifests/server.pp
+> ===================================================================
+> --- puppet/modules/postfix/manifests/server.pp	                        (rev 0)
+> +++ puppet/modules/postfix/manifests/server.pp	2012-03-22 15:18:24 UTC (rev 2674)
+> @@ -0,0 +1,13 @@
+> +class postfix::server inherits postfix {
+> +    include postgrey
+> +    include amavis
+> +    include spamassassin
+> +
+> +    File['/etc/postfix/main.cf'] {
+> +        content => template('postfix/main.cf'),
+> +    }
+> +
+> +    file { '/etc/postfix/transport_regexp':
+> +        content => template('postfix/transport_regexp'),
+> +    }
+> +}
+> Added: puppet/modules/postfix/manifests/simple_relay.pp
+> ===================================================================
+> --- puppet/modules/postfix/manifests/simple_relay.pp	                        (rev 0)
+> +++ puppet/modules/postfix/manifests/simple_relay.pp	2012-03-22 15:18:24 UTC (rev 2674)
+> @@ -0,0 +1,5 @@
+> +class postfix::simple_relay inherits postfix {
+> +    File['/etc/postfix/main.cf'] {
+> +        content => template('postfix/simple_relay_main.cf'),
+> +    }
+> +}
+>
+>
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120322/9945203b/attachment-0001.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004306.html b/zarb-ml/mageia-sysadm/2012-March/004306.html new file mode 100644 index 000000000..a2fe504c9 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004306.html @@ -0,0 +1,91 @@ + + + + [Mageia-sysadm] [sysadmin-commits] [2674] clean postfix module, rework the layout and split it in several file + + + + + + + + + +

[Mageia-sysadm] [sysadmin-commits] [2674] clean postfix module, rework the layout and split it in several file

+ Michael Scherer + misc at zarb.org +
+ Thu Mar 22 22:36:19 CET 2012 +

+
+ +
Le jeudi 22 mars 2012 à 19:26 +0000, Pascal Terjan a écrit :
+> We seem to reject all mails to MLs on alamut:
+> 
+
+gosh, forgot this hack with the tags in the template. 
+sorry.
+
+
+-- 
+Michael Scherer
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004307.html b/zarb-ml/mageia-sysadm/2012-March/004307.html new file mode 100644 index 000000000..899606e47 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004307.html @@ -0,0 +1,104 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Michael Scherer + misc at zarb.org +
+ Sat Mar 24 11:43:53 CET 2012 +

+
+ +
Le jeudi 22 mars 2012 à 08:18 +0100, Wolfgang Bornath a écrit :
+
+> He is talking about the update of the forum software phpBB3. The
+> version used at Mageia is outdated since summer 2011. New versions of
+> phpBB3 almost always are caused by security issues. This has been
+> mentioned several times in the forum threads. The point is that the
+> implementation of the forum software at Mageia (involving puppet,
+> etc.) was done this way to "ease forum software maintenance" (quoting
+> maât). :)
+
+Strictly speaking, what would have really helped the maintenance would
+have been to use :
+- a forum properly packaged, not one requiring specific deployment
+process like the current setup we have. Packages solved part of the
+problem since 15 years, maybe it would be a good moment to start using
+them. 
+- a forum that do not requires to patch it for adding features
+- a forum that do not requires update on a regular basis.
+
+But since people could neither wait nor volunteered to do the work
+properly ( ie, real packages, or selecting a cleaner forum ), the
+current setup is the best we could have achieved in the given time frame
+( and with the constraint of "we will need to open lots of new forums",
+and now, there is ... 2 ). 
+
+We are open to discuss patches or even constructive comments to the
+puppet setup, but it seems that no one sent anything at all. I have
+justified everything we did, and the reason for not having a free for
+all system due to privacy and security requirements that I explained
+enough to not repeat myself. 
+
+I either didn't see any pull request of patch to upgrade the forum in
+git, nor any request to have write access to the aforementioned git by
+anyone. While I can imagine that puppet, despite being dead easy and
+very well documented, is too complex for a hobbyist sysadmin, I do not
+think that git is a so obscure and unknown technology that no one ever
+tried to do anything with it.
+
+Also, it seemed obvious to me that security issues should be treated
+like the rest of the issues, on bugzilla and not on forums. I still see
+no bug opened for that on the bug tracker.
+
+-- 
+Michael Scherer
+
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004308.html b/zarb-ml/mageia-sysadm/2012-March/004308.html new file mode 100644 index 000000000..5c6df9ef1 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004308.html @@ -0,0 +1,87 @@ + + + + [Mageia-sysadm] Forums, wiki and bugzilla down? + + + + + + + + + +

[Mageia-sysadm] Forums, wiki and bugzilla down?

+ Oliver Burger + oliver.bgr at googlemail.com +
+ Sat Mar 24 12:22:32 CET 2012 +

+
+ +
Hi there,
+
+I can't reach the forums, the wiki or the bugzilla.
+Alamut does answer to pings, so I think it's just the httpd being down?
+
+Could anyone have a look, thanks
+
+Oliver
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004309.html b/zarb-ml/mageia-sysadm/2012-March/004309.html new file mode 100644 index 000000000..8c33df5ea --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004309.html @@ -0,0 +1,143 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Sat Mar 24 12:48:26 CET 2012 +

+
+ +
2012/3/24 Michael Scherer <misc at zarb.org>:
+> Le jeudi 22 mars 2012 à 08:18 +0100, Wolfgang Bornath a écrit :
+>
+>> He is talking about the update of the forum software phpBB3. The
+>> version used at Mageia is outdated since summer 2011. New versions of
+>> phpBB3 almost always are caused by security issues. This has been
+>> mentioned several times in the forum threads. The point is that the
+>> implementation of the forum software at Mageia (involving puppet,
+>> etc.) was done this way to "ease forum software maintenance" (quoting
+>> maât). :)
+>
+> Strictly speaking, what would have really helped the maintenance would
+> have been to use :
+> - a forum properly packaged, not one requiring specific deployment
+> process like the current setup we have. Packages solved part of the
+> problem since 15 years, maybe it would be a good moment to start using
+> them.
+> - a forum that do not requires to patch it for adding features
+> - a forum that do not requires update on a regular basis.
+
+ - I know not much about packaging (just the essentials). But I doubt
+there would be benefits by having a package for the forum software.
+Quite to the contrary, a simple change of a character in one of the
+php files would cause the need of an update of the whole package,
+while as is you just need to exchange this one php file. If there
+would be a benefit I guess there would have been phpBB packages for
+years, phpBB being the most popular forum software, not only in the
+Linux world. Ok, a weak point, I admit.
+
+ - How would you implement requested features which are not available
+in the forum software other than by "MODs" (which is the same as a
+patch?
+
+ - every php based forum software I know (I think I know almost all of
+them at least from testing) gets regular updates from upstream. Most
+of the changes between versions are not added functionalities or nicer
+looks (where implementing an update could be a matter of discussions)
+but needed bug fixes and even more needed security fixes. That's why
+updates are unavoidable and should be done in due time. If you know a
+forum software with equal functionality and which does not require
+such updates, great, let's have it!
+
+> We are open to discuss patches or even constructive comments to the
+> puppet setup, but it seems that no one sent anything at all. I have
+> justified everything we did, and the reason for not having a free for
+> all system due to privacy and security requirements that I explained
+> enough to not repeat myself.
+
+Exactly these (privacy & security) are the reasons for forum software
+updates. To me the current implementation was explained as a way to
+ease maintenance. That's why I (and others) asked in the forum why
+needed updates were not installed. I asked this in the forum because
+for a forum user the forum admin is the right person to contact, not
+any other group or person, not any other platform.
+
+> I either didn't see any pull request of patch to upgrade the forum in
+> git, nor any request to have write access to the aforementioned git by
+> anyone. While I can imagine that puppet, despite being dead easy and
+> very well documented, is too complex for a hobbyist sysadmin, I do not
+> think that git is a so obscure and unknown technology that no one ever
+> tried to do anything with it.
+
+Maintaining the forum (implementing modifications, updates or starting
+these by creating a bug report or whatever needed) is the most
+prominent task of the forum admin, there's not much else for him to
+do. It is not the user's job to care for such things. Maât himself
+even explained the workflow once in the forum, so he knew exactly what
+to do. So, if you blame somebody about missing requests or whatever,
+pls knock on the right door.
+
+> Also, it seemed obvious to me that security issues should be treated
+> like the rest of the issues, on bugzilla and not on forums. I still see
+> no bug opened for that on the bug tracker.
+
+You're right, it's no topic for forum discussions. If updates are
+available upstream, the admin should open a bugreport, adding an
+"important" tag to ensure that it is done in due time. This was never
+done.
+
+Summary: this discussion only started because somebody did not do his
+job (whatever reason). Hopefully exchanging people on the relevant
+position will improve the situation.
+
+-- 
+wobo
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004310.html b/zarb-ml/mageia-sysadm/2012-March/004310.html new file mode 100644 index 000000000..ca871a783 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004310.html @@ -0,0 +1,97 @@ + + + + [Mageia-sysadm] Forums, wiki and bugzilla down? + + + + + + + + + +

[Mageia-sysadm] Forums, wiki and bugzilla down?

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Sat Mar 24 13:02:36 CET 2012 +

+
+ +
2012/3/24 Oliver Burger <oliver.bgr at googlemail.com>:
+> Hi there,
+>
+> I can't reach the forums, the wiki or the bugzilla.
+
+Experienced the same while non-Mageia sites are answering ok. Failure
+was existant for 12 minutes.
+
+> Alamut does answer to pings, so I think it's just the httpd being down?
+
+I did a traceroute to alamut, looks normal.
+
+The phenomenon is over, pages answer normally.
+
+In the forum other users reported such occasional incidents with
+Mageia pages recently.
+
+-- 
+wobo
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004311.html b/zarb-ml/mageia-sysadm/2012-March/004311.html new file mode 100644 index 000000000..91c90c1a0 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004311.html @@ -0,0 +1,102 @@ + + + + [Mageia-sysadm] Forums, wiki and bugzilla down? + + + + + + + + + +

[Mageia-sysadm] Forums, wiki and bugzilla down?

+ Michael Scherer + misc at zarb.org +
+ Sat Mar 24 13:37:23 CET 2012 +

+
+ +
Le samedi 24 mars 2012 à 12:22 +0100, Oliver Burger a écrit :
+> Hi there,
+> 
+> I can't reach the forums, the wiki or the bugzilla.
+> Alamut does answer to pings, so I think it's just the httpd being down?
+> 
+> Could anyone have a look, thanks
+
+This was the result of applying php updates, and it seems that apache
+was not able to restart itself after it, and died silently. Usually,
+that's the sign of some long running process blocking one single apache
+process, thus blocking everything.
+
+I guess revamping the whole system, either on rpm level ( ie, having non
+breaking upgrade ), or on the organisation level ( like having specific
+upgrade time and stick to it ) would prevent such problems in the
+future, but I do not have hope for neither being adopted soon.
+
+
+Puppet restarted it automatically so that's why the problem fixed
+itself.
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004312.html b/zarb-ml/mageia-sysadm/2012-March/004312.html new file mode 100644 index 000000000..1ce2e225a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004312.html @@ -0,0 +1,259 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Michael Scherer + misc at zarb.org +
+ Sat Mar 24 14:45:34 CET 2012 +

+
+ +
Le samedi 24 mars 2012 à 12:48 +0100, Wolfgang Bornath a écrit :
+> 2012/3/24 Michael Scherer <misc at zarb.org>:
+> > Le jeudi 22 mars 2012 à 08:18 +0100, Wolfgang Bornath a écrit :
+> >
+> >> He is talking about the update of the forum software phpBB3. The
+> >> version used at Mageia is outdated since summer 2011. New versions of
+> >> phpBB3 almost always are caused by security issues. This has been
+> >> mentioned several times in the forum threads. The point is that the
+> >> implementation of the forum software at Mageia (involving puppet,
+> >> etc.) was done this way to "ease forum software maintenance" (quoting
+> >> maât). :)
+> >
+> > Strictly speaking, what would have really helped the maintenance would
+> > have been to use :
+> > - a forum properly packaged, not one requiring specific deployment
+> > process like the current setup we have. Packages solved part of the
+> > problem since 15 years, maybe it would be a good moment to start using
+> > them.
+> > - a forum that do not requires to patch it for adding features
+> > - a forum that do not requires update on a regular basis.
+> 
+>  - I know not much about packaging (just the essentials). 
+
+I know packaging, and more than "the essentials", I also know system
+administration, and also more the essential, partly because that's my
+job.
+
+> But I doubt
+> there would be benefits by having a package for the forum software.
+> Quite to the contrary, a simple change of a character in one of the
+> php files would cause the need of an update of the whole package,
+> while as is you just need to exchange this one php file. If there
+> would be a benefit I guess there would have been phpBB packages for
+> years, phpBB being the most popular forum software, not only in the
+> Linux world. Ok, a weak point, I admit.
+
+The point is indeed weak.
+
+For the start, having a package would ease the testing, since right now,
+people just have no clue on how to replicate our setup. There is the
+puppet manifests, but I take for granted that the intersection of those
+that know how to use them and those interested into testing phpbb is
+near 0.
+
+Second part of having a package is that it would benefit to others if in
+the distribution. It would also ease the management of version by the QA
+( cause if stuff is really important, you want to have it checked before
+it goes live ).
+
+Another idea is to detect when there is change in the php files, by
+using the rpm -V feature. That's quite handy when there is a problem
+( again speaking of experience ).
+
+And having a rpm in the distribution also mean that we can benefit from
+the whole framework on making sure this is up to date, making sure that
+basic quality is respected, etc. Something that is far from being the
+case with a random zip taken from the web, especially from php software.
+And I do not even talk of more complex security system like tomoyo or
+selinux.
+
+It also mean that the packager is following the update policy, which is
+here to prevent unwanted breakage by minimizing changes.
+
+A package also mean we know what we can remove from the server, or what
+we need. If we say "phpbb need php-zip", we know that the 2nd need to
+have a packager, or we are in trouble. 
+
+If we wanted to use slackware-style package on our servers, we would
+have done so.
+
+
+Oh, and there is package for phpbb in debian. So the lack of package in
+mageia just show that no one is interested into it, and show there isn't
+much correlation about what users would want and what people are
+interested to do.
+
+
+>  - How would you implement requested features which are not available
+> in the forum software other than by "MODs" (which is the same as a
+> patch?
+
+Usually, with well designed software, that work with plugins. Of course,
+with some stuff, that goes by "let's duplicate the source code and deal
+with merging source code update". There is ton of example of why this is
+wrong ( search "technical debt" on a search engine for lots of articles
+on the topic ), hence the need to use a software properly designed, and
+to stay in a well designed process.
+
+For example, bugzilla has a rather clean API in the version 4.0.
+Firefox, evolution, kde, all can be extended because they were designed
+this way.
+
+In fact, every single software that we can consider extendable in the
+world has some form of plugin system, . Except for some web application,
+because people are too impatient or too enthusiast to do stuff more
+slowly and properly, because it take time to design a proper API.
+
+And that's not because others application are harder to edit. There is
+lots of python, ruby and perl application out there that are no more
+harder to edit in place than php. And yet, coders usually add extensions
+system rather than telling "just edit the file and that's it". 
+
+We did take the "let's patch bugzilla to death" during the mandrake era.
+This ended with a outdated bugzilla. 
+
+And frankly, the whole idea of mod is a sign that phpbb is not suitable
+out of the box, as I said in the past. So while maybe the others are not
+either, that's still a signal that something is wrong.
+
+>  - every php based forum software I know (I think I know almost all of
+> them at least from testing) gets regular updates from upstream. Most
+> of the changes between versions are not added functionalities or nicer
+> looks (where implementing an update could be a matter of discussions)
+> but needed bug fixes and even more needed security fixes. That's why
+> updates are unavoidable and should be done in due time. If you know a
+> forum software with equal functionality and which does not require
+> such updates, great, let's have it!
+
+I never said that update should not be done in due time. But the fact
+that you need to patch the software is a clear blocker for doing
+upgrade. There is unit test in place in phpbb to ease everything, but I
+doubt that coders who know how to write tests would be ok with the whole
+"patching the code" style of extensions.
+
+And that's also a point for having a package in the distribution, where
+we have a proper process for upgrade. There is nothing more special
+about the forum software than for the rest of the system that would
+warrant being treated differently.
+
+> > We are open to discuss patches or even constructive comments to the
+> > puppet setup, but it seems that no one sent anything at all. I have
+> > justified everything we did, and the reason for not having a free for
+> > all system due to privacy and security requirements that I explained
+> > enough to not repeat myself.
+> 
+> Exactly these (privacy & security) are the reasons for forum software
+> updates. To me the current implementation was explained as a way to
+> ease maintenance. 
+
+Easing doesn't mean "give a magical wand to do upgrade". If no one do
+it, it just doesn't happen. 
+
+> That's why I (and others) asked in the forum why
+> needed updates were not installed. I asked this in the forum because
+> for a forum user the forum admin is the right person to contact, not
+> any other group or person, not any other platform.
+
+There is what people may think regarding who to contact, and the
+reality. If the 2 doesn't match, that's usually the reality that win.
+
+> > I either didn't see any pull request of patch to upgrade the forum in
+> > git, nor any request to have write access to the aforementioned git by
+> > anyone. While I can imagine that puppet, despite being dead easy and
+> > very well documented, is too complex for a hobbyist sysadmin, I do not
+> > think that git is a so obscure and unknown technology that no one ever
+> > tried to do anything with it.
+> 
+> Maintaining the forum (implementing modifications, updates or starting
+> these by creating a bug report or whatever needed) is the most
+> prominent task of the forum admin, there's not much else for him to
+> do. It is not the user's job to care for such things. Maât himself
+> even explained the workflow once in the forum, so he knew exactly what
+> to do. So, if you blame somebody about missing requests or whatever,
+> pls knock on the right door.
+
+>From my point of view, everybody can open a bug report or send patches.
+No one did, and you can say as much as you want "this is not my fault",
+that will not change anything nor retroactively make bug reports appear.
+
+I would add that if people have a pretension to become admin or
+anything, they should at least attempt to act as such. Ie, sending
+patchs, etc.
+
+The last "git push" is not harder than "git send-email".
+
+> > Also, it seemed obvious to me that security issues should be treated
+> > like the rest of the issues, on bugzilla and not on forums. I still see
+> > no bug opened for that on the bug tracker.
+> 
+> You're right, it's no topic for forum discussions. If updates are
+> available upstream, the admin should open a bugreport, adding an
+> "important" tag to ensure that it is done in due time. This was never
+> done.
+> 
+> Summary: this discussion only started because somebody did not do his
+> job (whatever reason). Hopefully exchanging people on the relevant
+> position will improve the situation.
+
+No, the discussion started because no one did the job. We are not
+Mandriva, there is not "someone is in charge so I do nothing" bullshit
+state of mind with the company and the rest of the world separation. The
+system is open enough that someone skilled enough and motivated enough
+can do most of the job, except the last step. 
+
+If people were really concerned on contributing instead of speaking how
+they would want to do something or how others didn't do what they
+wanted, they would have done something.
+
+-- 
+Michael Scherer
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004313.html b/zarb-ml/mageia-sysadm/2012-March/004313.html new file mode 100644 index 000000000..b9f40f1ce --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004313.html @@ -0,0 +1,96 @@ + + + + [Mageia-sysadm] Forums, wiki and bugzilla down? + + + + + + + + + +

[Mageia-sysadm] Forums, wiki and bugzilla down?

+ Damien Lallement + mageia at damsweb.net +
+ Sat Mar 24 12:53:53 CET 2012 +

+
+ +
Le 24/03/2012 12:22, Oliver Burger a écrit :
+> Hi there,
+>
+> I can't reach the forums, the wiki or the bugzilla.
+> Alamut does answer to pings, so I think it's just the httpd being down?
+>
+> Could anyone have a look, thanks
+>
+> Oliver
+
+Hi,
+
+Seems someone restarted apache but it was not enough:
+"no listening sockets available, shutting down"
+So, I killed apache process then restarted httpd service.
+It's now working.
+
+Dams
+-- 
+Damien Lallement
+twitter: damsweb - IRC: damsweb/coincoin
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004314.html b/zarb-ml/mageia-sysadm/2012-March/004314.html new file mode 100644 index 000000000..bec8ab402 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004314.html @@ -0,0 +1,167 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Sun Mar 25 08:24:31 CEST 2012 +

+
+ +
2012/3/24 Michael Scherer <misc at zarb.org>:
+> Le samedi 24 mars 2012 à 12:48 +0100, Wolfgang Bornath a écrit :
+>
+>> But I doubt
+>> there would be benefits by having a package for the forum software.
+>> Quite to the contrary, a simple change of a character in one of the
+>> php files would cause the need of an update of the whole package,
+>> while as is you just need to exchange this one php file. If there
+>> would be a benefit I guess there would have been phpBB packages for
+>> years, phpBB being the most popular forum software, not only in the
+>> Linux world. Ok, a weak point, I admit.
+>
+> The point is indeed weak.
+>
+> For the start, having a package would ease the testing, since right now,
+> people just have no clue on how to replicate our setup. There is the
+> puppet manifests, but I take for granted that the intersection of those
+> that know how to use them and those interested into testing phpbb is
+> near 0.
+
+Right. Why? Because even those who have experience in phpBB forum
+maintenance and php are not familiar of the setup used at Mageia.
+
+> Second part of having a package is that it would benefit to others if in
+> the distribution. It would also ease the management of version by the QA
+> ( cause if stuff is really important, you want to have it checked before
+> it goes live ).
+>
+> Another idea is to detect when there is change in the php files, by
+> using the rpm -V feature. That's quite handy when there is a problem
+> ( again speaking of experience ).
+>
+> And having a rpm in the distribution also mean that we can benefit from
+> the whole framework on making sure this is up to date, making sure that
+> basic quality is respected, etc. Something that is far from being the
+> case with a random zip taken from the web, especially from php software.
+> And I do not even talk of more complex security system like tomoyo or
+> selinux.
+
+Well, the phpBB community is very large, involving people on all
+levels of knowledge related to web applications and system
+administration. Regarding the software being released from them as not
+up to date and far from basic quality seems to me a bit ...
+"exaggerating".
+
+>>  - How would you implement requested features which are not available
+>> in the forum software other than by "MODs" (which is the same as a
+>> patch?
+>
+> Usually, with well designed software, that work with plugins. Of course,
+> with some stuff, that goes by "let's duplicate the source code and deal
+> with merging source code update". There is ton of example of why this is
+> wrong ( search "technical debt" on a search engine for lots of articles
+> on the topic ), hence the need to use a software properly designed, and
+> to stay in a well designed process.
+
+Ok, so your point is that phpBB is not the software you want to use.
+This is a point I understand and would accept, you explained the
+points very well. But I don't know if there is a software with same
+functionality which would qualify and if there is it would mean a lot
+of work to switch.
+
+> And frankly, the whole idea of mod is a sign that phpbb is not suitable
+> out of the box, as I said in the past. So while maybe the others are not
+> either, that's still a signal that something is wrong.
+
+Ok, what can be done about that?
+
+> From my point of view, everybody can open a bug report or send patches.
+> No one did, and you can say as much as you want "this is not my fault",
+> that will not change anything nor retroactively make bug reports appear.
+>
+> I would add that if people have a pretension to become admin or
+> anything, they should at least attempt to act as such. Ie, sending
+> patchs, etc.
+
+I haven't met anybody in the international forum with a pretention to
+become admin in the way you see it.
+
+> No, the discussion started because no one did the job. We are not
+> Mandriva, there is not "someone is in charge so I do nothing" bullshit
+> state of mind with the company and the rest of the world separation. The
+> system is open enough that someone skilled enough and motivated enough
+> can do most of the job, except the last step.
+>
+> If people were really concerned on contributing instead of speaking how
+> they would want to do something or how others didn't do what they
+> wanted, they would have done something.
+
+Yes, all correct in general and it would surely have happened like
+this in the Mageia forum as well. But:
+If there is an admin in place (even somebody who claims that there are
+enough admins), if this admin keeps responding to questions in the
+forum about a missing update and other requests by explaining how it
+will be done and what is needed and that it will be done as soon as
+possible - why should anyone of the users should write a bug report?
+
+Of course I can only speak for myself. There was a time when I was
+concerned on contributing, especially in the forum area. But after
+some discussions I got the impression that maât did not need
+contributions. I do not insist on contributing if it seems to be not
+wanted by the person who was the responsible person for this area. If
+you regard this to be caused by my ego, no problem.
+
+Overall I agree to most of your points after your explanations, thx
+for taking the time.
+
+-- 
+wobo
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004315.html b/zarb-ml/mageia-sysadm/2012-March/004315.html new file mode 100644 index 000000000..b3850c91b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004315.html @@ -0,0 +1,90 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Maarten Vanraes + alien at rmail.be +
+ Sun Mar 25 16:50:39 CEST 2012 +

+
+ +
Op zondag 25 maart 2012 08:24:31 schreef Wolfgang Bornath:
+> 2012/3/24 Michael Scherer <misc at zarb.org>:
+[...]
+
+I do agree with misc that software used by mageia shouldn't be different from 
+what we package.
+
+I also agree that having nice plugins is alot better than patching code, this 
+makes for a nice and stable and tested upgrade path.
+
+i'm not against phpBB or php in general, i kinda like php, it has it's good 
+points.
+
+but nothing prevents people to implement a proper and documented API, in any 
+reasonable language.
+
+take for example squirrelmail. it has alot of plugins and they don't require 
+patching (except, some do, and that goes to show that the API could have been 
+better)
+
+another example is drupal, etc...
+
+
+of course, i can understand it if no sysadmin wants to keep a patched software 
+up2date where mageia doesn't have a package...
+
+if there had been a package, a packager could have been doing upgrades instead 
+of only a sysadmin. and a sysadmin would've happily done the upgrade of a 
+well-tested application.
+
+
+
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004316.html b/zarb-ml/mageia-sysadm/2012-March/004316.html new file mode 100644 index 000000000..1902b50fb --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004316.html @@ -0,0 +1,100 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Sun Mar 25 17:49:27 CEST 2012 +

+
+ +
2012/3/25 Maarten Vanraes <alien at rmail.be>:
+> Op zondag 25 maart 2012 08:24:31 schreef Wolfgang Bornath:
+>> 2012/3/24 Michael Scherer <misc at zarb.org>:
+> [...]
+>
+> I do agree with misc that software used by mageia shouldn't be different from
+> what we package.
+>
+> I also agree that having nice plugins is alot better than patching code, this
+> makes for a nice and stable and tested upgrade path.
+>
+> i'm not against phpBB or php in general, i kinda like php, it has it's good
+> points.
+>
+> but nothing prevents people to implement a proper and documented API, in any
+> reasonable language.
+>
+> take for example squirrelmail. it has alot of plugins and they don't require
+> patching (except, some do, and that goes to show that the API could have been
+> better)
+>
+> another example is drupal, etc...
+>
+>
+> of course, i can understand it if no sysadmin wants to keep a patched software
+> up2date where mageia doesn't have a package...
+>
+> if there had been a package, a packager could have been doing upgrades instead
+> of only a sysadmin. and a sysadmin would've happily done the upgrade of a
+> well-tested application.
+
+But there were no Mageia packages available nor were they installed. I
+don't know why this was not discussed before forums were implemented
+(or was it?) but that's not the issue now. As I understand the current
+situation there are only 2 options:
+ - pack a package, remove the installed system and install the package
+(including language packages) and transfer the databases or
+ - go on with the current system and find a better workflow to react
+to upstream updates and customizing requests.
+
+-- 
+wobo
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004317.html b/zarb-ml/mageia-sysadm/2012-March/004317.html new file mode 100644 index 000000000..5dad7025c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004317.html @@ -0,0 +1,82 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Maarten Vanraes + alien at rmail.be +
+ Sun Mar 25 20:28:03 CEST 2012 +

+
+ +
Op zondag 25 maart 2012 17:49:27 schreef Wolfgang Bornath:
+[...]
+> But there were no Mageia packages available nor were they installed. I
+> don't know why this was not discussed before forums were implemented
+> (or was it?) but that's not the issue now. As I understand the current
+> situation there are only 2 options:
+>  - pack a package, remove the installed system and install the package
+> (including language packages) and transfer the databases or
+>  - go on with the current system and find a better workflow to react
+> to upstream updates and customizing requests.
+
+I think it's been discussed to death really, but i can be wrong.
+
+well maybe that's true, but is this something to be focussed on at this very 
+moment? imho it can likely wait until after mga2 (unless pending security 
+updates)
+
+otoh: any packager can make a phpbb package (or other forum software) and it 
+can even be pushed onto mga2 until release freeze.
+
+is there even a request for it on bugzilla?
+
+even if we take the second option, still, some packager will have to make a 
+package for it.
+
+ + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004318.html b/zarb-ml/mageia-sysadm/2012-March/004318.html new file mode 100644 index 000000000..725665139 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004318.html @@ -0,0 +1,71 @@ + + + + [Mageia-sysadm] Sysadmin team council representative and deputy election + + + + + + + + + +

[Mageia-sysadm] Sysadmin team council representative and deputy election

+ nicolas vigier + boklm at mars-attacks.org +
+ Sun Mar 25 21:42:56 CEST 2012 +

+
+ +
On Tue, 20 Mar 2012, nicolas vigier wrote:
+
+> Hello,
+> 
+> As mentioned in last IRC meeting, we need to elect sysadmin team
+> representative, and deputy, for council. Anybody from sysadmin team can
+> be candidate. If you are candidate, you need to answer to this email to
+> say you are candidate, before next monday when the vote will be started.
+> 
+> Planning for election :
+>  - 20/03 to 26/03 at 19:00 UTC: candidates send an email to say that they are
+>    candidate
+
+So I'm sending this email to say I will be candidate for this.
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004319.html b/zarb-ml/mageia-sysadm/2012-March/004319.html new file mode 100644 index 000000000..9e4e8642b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004319.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Mar 26 08:58:24 CEST 2012 +

+
+ +
2012/3/25 Maarten Vanraes <alien at rmail.be>:
+> Op zondag 25 maart 2012 17:49:27 schreef Wolfgang Bornath:
+> [...]
+>> But there were no Mageia packages available nor were they installed. I
+>> don't know why this was not discussed before forums were implemented
+>> (or was it?) but that's not the issue now. As I understand the current
+>> situation there are only 2 options:
+>>  - pack a package, remove the installed system and install the package
+>> (including language packages) and transfer the databases or
+>>  - go on with the current system and find a better workflow to react
+>> to upstream updates and customizing requests.
+>
+> I think it's been discussed to death really, but i can be wrong.
+>
+> well maybe that's true, but is this something to be focussed on at this very
+> moment? imho it can likely wait until after mga2 (unless pending security
+> updates)
+
+We were not talking about a simple software package for the
+distribution (although this is certainly an option). We were talking
+about the Mageia forums and what to do with the needed update to the
+forum software, and, yes, the 2 official updates of phpBB3 which we
+missed include several security fixes.
+
+-- 
+wobo
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004320.html b/zarb-ml/mageia-sysadm/2012-March/004320.html new file mode 100644 index 000000000..bdd1279a0 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004320.html @@ -0,0 +1,77 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Mon Mar 26 15:43:16 CEST 2012 +

+
+ +
On 26/03/12 08:58, Wolfgang Bornath wrote:
+>
+> We were not talking about a simple software package for the
+> distribution (although this is certainly an option). We were talking
+> about the Mageia forums and what to do with the needed update to the
+> forum software, and, yes, the 2 official updates of phpBB3 which we
+> missed include several security fixes.
+>
+Please be as kind as to open bug reports for them, including the links 
+to the security issues that are solved by those updates.
+
+We've had a lot of security bug reports so far, see 
+https://bugs.mageia.org/buglist.cgi?quicksearch=ALL+CVE because many of 
+our packagers missed the news about security fixes or were too busy to 
+take proper action. Luckily some people took the trouble to open reports 
+for them, that really helps to get the fixes done by either the 
+maintainers of the packages involved or by others who are willing to help.
+
+Thanks in advance,
+Marja
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004321.html b/zarb-ml/mageia-sysadm/2012-March/004321.html new file mode 100644 index 000000000..8a225b23a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004321.html @@ -0,0 +1,77 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Mar 26 16:13:03 CEST 2012 +

+
+ +
2012/3/26 Marja van Waes <marja11 at xs4all.nl>:
+> On 26/03/12 08:58, Wolfgang Bornath wrote:
+>>
+>>
+>> We were not talking about a simple software package for the
+>> distribution (although this is certainly an option). We were talking
+>> about the Mageia forums and what to do with the needed update to the
+>> forum software, and, yes, the 2 official updates of phpBB3 which we
+>> missed include several security fixes.
+>>
+> Please be as kind as to open bug reports for them, including the links to
+> the security issues that are solved by those updates.
+
+Information about security fixes are available in the changelogs of
+the phpBB3 versions. But if in future we do not use "a zip from some
+website" we have to search where the phpBB team lists the issues
+(solved and not solved).
+
+-- 
+wobo
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004322.html b/zarb-ml/mageia-sysadm/2012-March/004322.html new file mode 100644 index 000000000..952b10449 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004322.html @@ -0,0 +1,82 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Mon Mar 26 16:14:18 CEST 2012 +

+
+ +
On 26/03/12 15:43, Marja van Waes wrote:
+> On 26/03/12 08:58, Wolfgang Bornath wrote:
+>>
+>> We were not talking about a simple software package for the
+>> distribution (although this is certainly an option). We were talking
+>> about the Mageia forums and what to do with the needed update to the
+>> forum software, and, yes, the 2 official updates of phpBB3 which we
+>> missed include several security fixes.
+>>
+> Please be as kind as to open bug reports for them, including the links 
+> to the security issues that are solved by those updates.
+>
+> We've had a lot of security bug reports so far, see 
+> https://bugs.mageia.org/buglist.cgi?quicksearch=ALL+CVE because many 
+> of our packagers missed the news about security fixes or were too busy 
+> to take proper action. Luckily some people took the trouble to open 
+> reports for them, that really helps to get the fixes done by either 
+> the maintainers of the packages involved or by others who are willing 
+> to help.
+
+Sorry, I'm not referring to all of those bugs, but to, for instance, all 
+those reported by David Walser.
+
+Regards,
+Marja
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004323.html b/zarb-ml/mageia-sysadm/2012-March/004323.html new file mode 100644 index 000000000..8abab516a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004323.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Mar 26 16:24:25 CEST 2012 +

+
+ +
2012/3/26 Marja van Waes <marja11 at xs4all.nl>:
+> On 26/03/12 15:43, Marja van Waes wrote:
+>>
+>> We've had a lot of security bug reports so far, see
+>> https://bugs.mageia.org/buglist.cgi?quicksearch=ALL+CVE because many of our
+>> packagers missed the news about security fixes or were too busy to take
+>> proper action. Luckily some people took the trouble to open reports for
+>> them, that really helps to get the fixes done by either the maintainers of
+>> the packages involved or by others who are willing to help.
+>
+> Sorry, I'm not referring to all of those bugs, but to, for instance, all
+> those reported by David Walser.
+
+Sorry, can't find any related entry in your list when searching for
+phpBB or forum.
+
+-- 
+wobo
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004324.html b/zarb-ml/mageia-sysadm/2012-March/004324.html new file mode 100644 index 000000000..e2dd7406a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004324.html @@ -0,0 +1,80 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Mon Mar 26 16:44:22 CEST 2012 +

+
+ +
On 26/03/12 16:24, Wolfgang Bornath wrote:
+> 2012/3/26 Marja van Waes<marja11 at xs4all.nl>:
+>> On 26/03/12 15:43, Marja van Waes wrote:
+>>> We've had a lot of security bug reports so far, see
+>>> https://bugs.mageia.org/buglist.cgi?quicksearch=ALL+CVE because many of our
+>>> packagers missed the news about security fixes or were too busy to take
+>>> proper action. Luckily some people took the trouble to open reports for
+>>> them, that really helps to get the fixes done by either the maintainers of
+>>> the packages involved or by others who are willing to help.
+>> Sorry, I'm not referring to all of those bugs, but to, for instance, all
+>> those reported by David Walser.
+> Sorry, can't find any related entry in your list when searching for
+> phpBB or forum.
+>
+No, that is why I asked you to report in Bugzilla, like e.g. David 
+Walser did for other security issues that affected Mageia and were missed :)
+
+Sorry, but I miss the knowledge you have. You have knowledge about 
+missed phpBB security issues that affect our forum, please report them 
+and link to the relevant phpBB bug fixes or attach the relevant changelogs.
+
+Thanks, Wolfgang :)
+Marja
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004325.html b/zarb-ml/mageia-sysadm/2012-March/004325.html new file mode 100644 index 000000000..86497c935 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004325.html @@ -0,0 +1,76 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Mar 26 16:55:13 CEST 2012 +

+
+ +
2012/3/26 Marja van Waes <marja11 at xs4all.nl>:
+>>
+> No, that is why I asked you to report in Bugzilla, like e.g. David Walser
+> did for other security issues that affected Mageia and were missed :)
+>
+> Sorry, but I miss the knowledge you have. You have knowledge about missed
+> phpBB security issues that affect our forum, please report them and link to
+> the relevant phpBB bug fixes or attach the relevant changelogs.
+
+Will check this but I think it will not do any good because I fear the
+same discussion (updating phpBB3 version using the official phpBB from
+the website opposed to using own packages) will start on Bugzilla
+again. As long as this is not finished/decided it makes not much sense
+reporting.
+
+Anyhow I will see what I can do.
+
+-- 
+wobo
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004326.html b/zarb-ml/mageia-sysadm/2012-March/004326.html new file mode 100644 index 000000000..f10a48231 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004326.html @@ -0,0 +1,75 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Mar 26 17:56:49 CEST 2012 +

+
+ +
2012/3/26 Wolfgang Bornath <molch.b at googlemail.com>:
+> 2012/3/26 Marja van Waes <marja11 at xs4all.nl>:
+>> Sorry, but I miss the knowledge you have. You have knowledge about missed
+>> phpBB security issues that affect our forum, please report them and link to
+>> the relevant phpBB bug fixes or attach the relevant changelogs.
+>
+> Anyhow I will see what I can do.
+
+Just to give you an idea: there are around 150 bug fixes between the
+version used by Mageia and the latest stable version, not counting
+feature enhancements, new features, tasks nor subtasks::
+http://www.phpbb.com/support/documents.php?mode=changelog&version=3
+
+I'm searching for a list of security related fixes but I think bug
+fixes are already a good motivation to upgrade.
+
+-- 
+wobo
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004327.html b/zarb-ml/mageia-sysadm/2012-March/004327.html new file mode 100644 index 000000000..12087e88a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004327.html @@ -0,0 +1,64 @@ + + + + [Mageia-sysadm] Sysadmin team council representative and deputy election + + + + + + + + + +

[Mageia-sysadm] Sysadmin team council representative and deputy election

+ nicolas vigier + boklm at mars-attacks.org +
+ Mon Mar 26 18:32:44 CEST 2012 +

+
+ +
On Tue, 20 Mar 2012, nicolas vigier wrote:
+
+> 
+> Planning for election :
+>  - 20/03 to 26/03 at 19:00 UTC: candidates send an email to say that they are
+>    candidate
+
+Today is last day to send an email if you are candidate.
+
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004328.html b/zarb-ml/mageia-sysadm/2012-March/004328.html new file mode 100644 index 000000000..21f40a544 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004328.html @@ -0,0 +1,81 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Mar 26 18:47:03 CEST 2012 +

+
+ +
2012/3/26 Wolfgang Bornath <molch.b at googlemail.com>:
+> 2012/3/26 Wolfgang Bornath <molch.b at googlemail.com>:
+>> 2012/3/26 Marja van Waes <marja11 at xs4all.nl>:
+>>> Sorry, but I miss the knowledge you have. You have knowledge about missed
+>>> phpBB security issues that affect our forum, please report them and link to
+>>> the relevant phpBB bug fixes or attach the relevant changelogs.
+>>
+>> Anyhow I will see what I can do.
+>
+> Just to give you an idea: there are around 150 bug fixes between the
+> version used by Mageia and the latest stable version, not counting
+> feature enhancements, new features, tasks nor subtasks::
+> http://www.phpbb.com/support/documents.php?mode=changelog&version=3
+>
+> I'm searching for a list of security related fixes but I think bug
+> fixes are already a good motivation to upgrade.
+
+Ok, I checked. Last security related fix was before 3.0.8 - seeing the
+sheer number of bug fixes and the general recommendation of the phpbb
+team to update because of security built an "update-friendly" habit
+here. But all the more than 150 bug fixes are just that: bug fixes.
+So, to say it in a provoking way: no need for updates = case closed.
+
+-- 
+wobo
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004329.html b/zarb-ml/mageia-sysadm/2012-March/004329.html new file mode 100644 index 000000000..94174262f --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004329.html @@ -0,0 +1,99 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Mon Mar 26 19:03:06 CEST 2012 +

+
+ +
On 26/03/12 18:47, Wolfgang Bornath wrote:
+> 2012/3/26 Wolfgang Bornath<molch.b at googlemail.com>:
+>> 2012/3/26 Wolfgang Bornath<molch.b at googlemail.com>:
+>>> 2012/3/26 Marja van Waes<marja11 at xs4all.nl>:
+>>>> Sorry, but I miss the knowledge you have. You have knowledge about missed
+>>>> phpBB security issues that affect our forum, please report them and link to
+>>>> the relevant phpBB bug fixes or attach the relevant changelogs.
+>>> Anyhow I will see what I can do.
+>> Just to give you an idea: there are around 150 bug fixes between the
+>> version used by Mageia and the latest stable version, not counting
+>> feature enhancements, new features, tasks nor subtasks::
+>> http://www.phpbb.com/support/documents.php?mode=changelog&version=3
+>>
+>> I'm searching for a list of security related fixes but I think bug
+>> fixes are already a good motivation to upgrade.
+> Ok, I checked. Last security related fix was before 3.0.8 - seeing the
+> sheer number of bug fixes and the general recommendation of the phpbb
+> team to update because of security built an "update-friendly" habit
+> here. But all the more than 150 bug fixes are just that: bug fixes.
+> So, to say it in a provoking way: no need for updates = case closed.
+>
+Wel, it helps if people file a bug report when they suffer from those 
+"normal" bugs. We don't vote for bugs in our bugzilla, but the more 
+users report a bug, the more chance it gets fixed.
+
+But even then nothing is guaranteed, because the people who fix bugs , 
+push upgrades, etc. here are human beings, with limited time, 
+capabilities, and so on, even security fixes sometimes don't get done 
+fast, in spite of everyone doing his best.
+
+We have a bug report (#40) about an upgrade that would fix several bugs, 
+including several security fixes, some of the last were already 
+mentioned in the report in august last year by the upstream maintainer.
+
+Having the report there helps as a reminder and I'm sure upgrading will 
+be done, but the report also shows that it is good to have limited 
+expectations about how fast we are.
+
+Thanks a lot, wobo, for telling that there are no security issues in our 
+forum :)
+
+Cheers,
+Marja
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004330.html b/zarb-ml/mageia-sysadm/2012-March/004330.html new file mode 100644 index 000000000..c7e1c4fb9 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004330.html @@ -0,0 +1,92 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Mar 26 19:21:26 CEST 2012 +

+
+ +
2012/3/26 Marja van Waes <marja11 at xs4all.nl>:
+>>
+> Wel, it helps if people file a bug report when they suffer from those
+> "normal" bugs. We don't vote for bugs in our bugzilla, but the more users
+> report a bug, the more chance it gets fixed.
+>
+> But even then nothing is guaranteed, because the people who fix bugs , push
+> upgrades, etc. here are human beings, with limited time, capabilities, and
+> so on, even security fixes sometimes don't get done fast, in spite of
+> everyone doing his best.
+>
+> We have a bug report (#40) about an upgrade that would fix several bugs,
+> including several security fixes, some of the last were already mentioned in
+> the report in august last year by the upstream maintainer.
+>
+> Having the report there helps as a reminder and I'm sure upgrading will be
+> done, but the report also shows that it is good to have limited expectations
+> about how fast we are.
+
+As explained several times, you can't mix bug fixing for mageia
+packages with bug fixing of phpBB. First we do not have a phpBB3
+package. Second:  updating the couple of hundred files with all
+100+something bugs would be some work. Third: if we would have a
+package, still it needs to be unpacked and all the bug fixes must be
+checked and integrated into the single files and then packed. This way
+or that, all this only in case we still trust the "zip from some
+website" (as Michael put it). If we don't we would have to find our
+bug fixes on our own, in other words: that one or two php-savvy people
+(if we find so many for the forum software) would have to do what a
+large team at phpBB does. Or look how Debian does it (do they trust
+phpbb?).
+
+But this is something else and there are people who know much better than I.
+
+-- 
+wobo
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004331.html b/zarb-ml/mageia-sysadm/2012-March/004331.html new file mode 100644 index 000000000..38d458cb5 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004331.html @@ -0,0 +1,86 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Marja van Waes + marja11 at xs4all.nl +
+ Mon Mar 26 20:59:47 CEST 2012 +

+
+ +
On 26/03/12 19:21, Wolfgang Bornath wrote:
+> 2012/3/26 Marja van Waes<marja11 at xs4all.nl>:
+>> Wel, it helps if people file a bug report when they suffer from those
+>> "normal" bugs. We don't vote for bugs in our bugzilla, but the more users
+>> report a bug, the more chance it gets fixed.
+>>
+>> But even then nothing is guaranteed, because the people who fix bugs , push
+>> upgrades, etc. here are human beings, with limited time, capabilities, and
+>> so on, even security fixes sometimes don't get done fast, in spite of
+>> everyone doing his best.
+>>
+>> We have a bug report (#40) about an upgrade that would fix several bugs,
+>> including several security fixes, some of the last were already mentioned in
+>> the report in august last year by the upstream maintainer.
+>>
+>> Having the report there helps as a reminder and I'm sure upgrading will be
+>> done, but the report also shows that it is good to have limited expectations
+>> about how fast we are.
+> As explained several times, you can't mix bug fixing for mageia
+> packages with bug fixing of phpBB. First we do not have a phpBB3
+> package. Second:  updating the couple of hundred files with all
+> 100+something bugs would be some work. Third: if we would have a
+> package, still it needs to be unpacked and all the bug fixes must be
+> checked and integrated into the single files and then packed. This way
+> or that, all this only in case we still trust the "zip from some
+> website" (as Michael put it).
+Thanks wobo, sometimes I miss mails or they don't sink in when I read 
+them, so thanks for taking the time to explain it again :)
+
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004332.html b/zarb-ml/mageia-sysadm/2012-March/004332.html new file mode 100644 index 000000000..20c90fc74 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004332.html @@ -0,0 +1,299 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Michael Scherer + misc at zarb.org +
+ Mon Mar 26 22:49:32 CEST 2012 +

+
+ +
Le dimanche 25 mars 2012 à 08:24 +0200, Wolfgang Bornath a écrit :
+> 2012/3/24 Michael Scherer <misc at zarb.org>:
+> > Le samedi 24 mars 2012 à 12:48 +0100, Wolfgang Bornath a écrit :
+> >
+> >> But I doubt
+> >> there would be benefits by having a package for the forum software.
+> >> Quite to the contrary, a simple change of a character in one of the
+> >> php files would cause the need of an update of the whole package,
+> >> while as is you just need to exchange this one php file. If there
+> >> would be a benefit I guess there would have been phpBB packages for
+> >> years, phpBB being the most popular forum software, not only in the
+> >> Linux world. Ok, a weak point, I admit.
+> >
+> > The point is indeed weak.
+> >
+> > For the start, having a package would ease the testing, since right now,
+> > people just have no clue on how to replicate our setup. There is the
+> > puppet manifests, but I take for granted that the intersection of those
+> > that know how to use them and those interested into testing phpbb is
+> > near 0.
+> 
+> Right. Why? Because even those who have experience in phpBB forum
+> maintenance and php are not familiar of the setup used at Mageia.
+
+Writing script to ease the setup of the copy of the system have been on
+my todo list since a long time. I started to write documents on the
+wiki, I did some conference to have some buzz, I did refactor the whole
+repository to make it easier to read and to understand.
+
+The setup used at mageia is nothing special or magic, there is :
+- 1 postgresql database
+- 1 git checkout 
+- 1 apache config file that basically block some directory for security
+reasons
+
+I have yet to see a request for more information, that I would have
+provided. But maybe people think we are too busy or too important to be
+disturbed, or that they would not be able to change anything ( despites
+me saying several time "send patch" ). There isn't much secret in the
+setup, this is published since the beginning.
+
+For example :
+http://svnweb.mageia.org/adm/puppet/modules/phpbb/templates/config.php?revision=1625&view=markup
+that's config.php. Anyone knowing php ( or asp, or jsp ) would
+intuitively understand the format ( ie, database is a variable given
+somewhere else )
+
+The git checkout url is in another file, to get it :
+
+git clone git://git.mageia.org/forum/ foo
+
+and we just remove "phpBB/install" after checkout.
+
+I agree this is not obvious, but I think we have a fairly standard
+setup, and since no one ever ask a question, we can hardly see what is
+difficult to understand.
+
+> > Second part of having a package is that it would benefit to others if in
+> > the distribution. It would also ease the management of version by the QA
+> > ( cause if stuff is really important, you want to have it checked before
+> > it goes live ).
+> >
+> > Another idea is to detect when there is change in the php files, by
+> > using the rpm -V feature. That's quite handy when there is a problem
+> > ( again speaking of experience ).
+> >
+> > And having a rpm in the distribution also mean that we can benefit from
+> > the whole framework on making sure this is up to date, making sure that
+> > basic quality is respected, etc. Something that is far from being the
+> > case with a random zip taken from the web, especially from php software.
+> > And I do not even talk of more complex security system like tomoyo or
+> > selinux.
+> 
+> Well, the phpBB community is very large, involving people on all
+> levels of knowledge related to web applications and system
+> administration. Regarding the software being released from them as not
+> up to date and far from basic quality seems to me a bit ...
+> "exaggerating".
+
+When I mean "being up to date", i mean using the same tool we use for
+others packages to know there is a update, etc.
+IE, having the package up to date. The same goes for "quality". Web
+developpers tend to focus on the use case of "I have a shared space and
+I cannot change nything to it", which is not our case. We can change
+apache config, we can put some stuff outside of the web root, etc.
+
+Software distribution is something that we already do, so solving the
+same problem in a different way a second time is IMHO not a good idea.
+
+> >>  - How would you implement requested features which are not available
+> >> in the forum software other than by "MODs" (which is the same as a
+> >> patch?
+> >
+> > Usually, with well designed software, that work with plugins. Of course,
+> > with some stuff, that goes by "let's duplicate the source code and deal
+> > with merging source code update". There is ton of example of why this is
+> > wrong ( search "technical debt" on a search engine for lots of articles
+> > on the topic ), hence the need to use a software properly designed, and
+> > to stay in a well designed process.
+> 
+> Ok, so your point is that phpBB is not the software you want to use.
+> This is a point I understand and would accept, you explained the
+> points very well. But I don't know if there is a software with same
+> functionality which would qualify and if there is it would mean a lot
+> of work to switch.
+
+That's not phpbb per se than the idea of how we should modify it.
+
+Basically, in a world where we have near infinite ressources, we would
+be able to take phpbb, and do any customisation. The same could be done
+for all softwares. 
+
+For exemple, that's what Google or Yahoo do ( more the first than the
+2nd ). Google do have a custom http server, likely a custom kernel,
+custom jvm, custom software and framework, even custom languages, custom
+hardware, custom routers. They also have around 24 000 people working
+for them, and a pile of money. 
+
+But we are on the other side of the spectrum and we may not have the
+sustainable ressources for custom stuff ( and I should really make the
+word sustainable bold ). We did took this road for some of our component
+( identity, for exemple ) and we do not have the man power to make
+software evolve.
+
+In the long run, the best would be to have such ressources, of course.
+
+But that's a difficult problem to solve, and in the mean term, we should
+have a solution, and I think therefor sticking to stock software is the
+best compromise. I am aware that some mod would make stuff better ( for
+example, to have a decent url, helping for visibility, etc ) and i am
+sure that they are all enhancing the forum ( I mean, no one will do a
+mod to make it worst ), but they are not free in term of ressources to
+integrate.
+
+So that's a tradeoff. It is better, but then you have to do some work
+for each upgrade, etc. 
+
+
+> > And frankly, the whole idea of mod is a sign that phpbb is not suitable
+> > out of the box, as I said in the past. So while maybe the others are not
+> > either, that's still a signal that something is wrong.
+> 
+> Ok, what can be done about that?
+
+Now we decided to use phpbb, I guess we will stick to it. A migration
+would take too much time, and despites having a setup that can be
+improved ( to my eyes ), it seems to do the job.
+
+But I think that we should keep in mind to prefer a software that do
+what we want directly than one we can fix later ( or at least, depend
+how we can fix ). That sound simple once said, but unfortunately, that's
+hard to resist to the call of code for coders, so I will not blame
+anyone on that.
+
+> > From my point of view, everybody can open a bug report or send patches.
+> > No one did, and you can say as much as you want "this is not my fault",
+> > that will not change anything nor retroactively make bug reports appear.
+> >
+> > I would add that if people have a pretension to become admin or
+> > anything, they should at least attempt to act as such. Ie, sending
+> > patchs, etc.
+> 
+> I haven't met anybody in the international forum with a pretention to
+> become admin in the way you see it.
+
+I didn't read the forum, so maybe I misunderstood ( likely, in fact ),
+so sorry if I was too harsh.
+
+But the point is still valid,  if people wish to help or think they can
+do a better job than us ( and I think we are not perfect, I do not deny
+), we can arrange something. 
+
+> > No, the discussion started because no one did the job. We are not
+> > Mandriva, there is not "someone is in charge so I do nothing" bullshit
+> > state of mind with the company and the rest of the world separation. The
+> > system is open enough that someone skilled enough and motivated enough
+> > can do most of the job, except the last step.
+> >
+> > If people were really concerned on contributing instead of speaking how
+> > they would want to do something or how others didn't do what they
+> > wanted, they would have done something.
+> 
+> Yes, all correct in general and it would surely have happened like
+> this in the Mageia forum as well. But:
+> If there is an admin in place (even somebody who claims that there are
+> enough admins), if this admin keeps responding to questions in the
+> forum about a missing update and other requests by explaining how it
+> will be done and what is needed and that it will be done as soon as
+> possible - why should anyone of the users should write a bug report?
+
+Part of the problem is first what do people mean by "admin".
+
+To me, this mean "system admin", and even if I tried to use sysadmin for
+that meaning, I am sure that I have slipped more than once.
+And while it may not have been obvious, I only speak of the sysadmin
+side of the thing. 
+
+To me, it seems obvious we need to have 1 and 1 single way to report
+issue. Bugzilla is not perfect, but if we use 1 single system instead of
+more, this permit to have 1 system to maintain, to not need to ask to
+user to decide where to report problem, and people will have 1 system to
+learn. ( and that's ITIL compliant, but that's a private joke with
+myself ).
+
+Now, I understand and should keep in mind that by admin, people also see
+forum admin, and I will likely not comment on this part. Not that I do
+not have a perfect(tm) solution for the problem :)
+
+So maybe the first step would be to document exactly what is the current
+state of affairs, who do what, who is in what group so we can at least
+make sure we use the same word, see the same things. I have part of this
+information in mind, but thanks to my training when I worked for CIA,
+people cannot read it.
+
+>From what I remember :
+
+- there is mga-sysadmin group, 10 person, who ( for the forum ) :
+ - access the server, databases and can commit to puppet or modify
+directly the db, and grant access to git
+
+they also have lots of access, and the long term goal is to delegate as
+much as possible. As i say, my goal is to be able to replace myself by a
+script. So this is not practical to give access to this group without
+any check of skills or anything. 
+
+- there is the mga-forum_developer group, of 3 person ( now 2 ), who :
+ - have write access to the code of phpbb hosted in our git ( see url
+before )
+ - should have enough access to upgrade the forum ( but do not know )
+
+the deployment is planned to be automatised, but that's not done ( my
+point was that sysadmin will do it by hand until sufficiently annoyed,
+and until the know how to automate it, until then we have to do the
+upgrade by hand to see what need to be coded, or wait for a patch for
+that ). I cannot speak for the others, but I do not plan to blindly code
+without doing a few test runs so without request to upgrade forum.
+
+on the side of forum management, well, I do not know. That's the part
+where someone step in and complete my mail.
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004333.html b/zarb-ml/mageia-sysadm/2012-March/004333.html new file mode 100644 index 000000000..45b4cae52 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004333.html @@ -0,0 +1,202 @@ + + + + [Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config + + + + + + + + + +

[Mageia-sysadm] [forums-discuss] Re: updating sysadmin privileges in forum config

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Tue Mar 27 10:16:00 CEST 2012 +

+
+ +
First let me express my appreciation for putting so much time into
+explanations of points I now understand more clearly than before.
+
+2012/3/26 Michael Scherer <misc at zarb.org>:
+>
+> For example :
+> http://svnweb.mageia.org/adm/puppet/modules/phpbb/templates/config.php?revision=1625&view=markup
+> that's config.php. Anyone knowing php ( or asp, or jsp ) would
+> intuitively understand the format ( ie, database is a variable given
+> somewhere else )
+>
+> The git checkout url is in another file, to get it :
+>
+> git clone git://git.mageia.org/forum/ foo
+>
+> and we just remove "phpBB/install" after checkout.
+
+Yes, that is a must after installation, forum software checks for that.
+
+> When I mean "being up to date", i mean using the same tool we use for
+> others packages to know there is a update, etc.
+> IE, having the package up to date. The same goes for "quality". Web
+> developpers tend to focus on the use case of "I have a shared space and
+> I cannot change nything to it", which is not our case. We can change
+> apache config, we can put some stuff outside of the web root, etc.
+
+When we (mandrivauser.de) set up phpBB (and later phpBB3) we used
+Mandriva as server os and there was not much to change in apache
+(forum related), I remember we had to change one setting in php.ini,
+that was all. In fact we had (still have now on Debian) a similar
+setup, except that we installed phpBB directly without git.
+
+> But that's a difficult problem to solve, and in the mean term, we should
+> have a solution, and I think therefor sticking to stock software is the
+> best compromise. I am aware that some mod would make stuff better ( for
+> example, to have a decent url, helping for visibility, etc ) and i am
+> sure that they are all enhancing the forum ( I mean, no one will do a
+> mod to make it worst ), but they are not free in term of ressources to
+> integrate.
+>
+> So that's a tradeoff. It is better, but then you have to do some work
+> for each upgrade, etc.
+
+Yes. But as I see in the forum, requests for changes are almost all in
+the /styles section, that are not MODs, just changing of lines in the
+templates. So no security related software involved. Examples: moving
+or adding a line with a link, etc. or another icon set. Of course this
+has to be documented because it has to be changed at each update.
+
+> Now we decided to use phpbb, I guess we will stick to it. A migration
+> would take too much time, and despites having a setup that can be
+> improved ( to my eyes ), it seems to do the job.
+
+Yes.
+
+> But the point is still valid,  if people wish to help or think they can
+> do a better job than us ( and I think we are not perfect, I do not deny
+> ), we can arrange something.
+
+No, through all these discussions (here and in the forum
+(unfortunately I have the time to read both)) I never had the
+impression that somebody wrote he could do better than your team.
+
+> Part of the problem is first what do people mean by "admin".
+
+Yes. I explained that several times but I realize that this was
+probably only in forum discussions.
+
+> To me, this mean "system admin", and even if I tried to use sysadmin for
+> that meaning, I am sure that I have slipped more than once.
+> And while it may not have been obvious, I only speak of the sysadmin
+> side of the thing.
+
+Yes. OTOH I (and others) never meant "sysadmin" with "admin". A
+sysadmin is an admin for a special purpose, that's why he has those 3
+extra letters (sys) in the name. A forum-admin also has a special
+purpose, that's why he has "forum-" in his name. So "admin" is a
+rather generic term which can mean anything. To know what kind of
+admin is meant you need to add the prefix or extra letters.
+
+> From what I remember :
+>
+> - there is mga-sysadmin group, 10 person, who ( for the forum ) :
+>  - access the server, databases and can commit to puppet or modify
+> directly the db, and grant access to git
+>
+> - there is the mga-forum_developer group, of 3 person ( now 2 ), who :
+>  - have write access to the code of phpbb hosted in our git ( see url
+> before )
+>  - should have enough access to upgrade the forum ( but do not know )
+
+> the deployment is planned to be automatised, but that's not done ( my
+> point was that sysadmin will do it by hand until sufficiently annoyed,
+> and until the know how to automate it, until then we have to do the
+> upgrade by hand to see what need to be coded, or wait for a patch for
+> that ). I cannot speak for the others, but I do not plan to blindly code
+> without doing a few test runs so without request to upgrade forum.
+
+Just to give you an idea how much has changed so far I posted an url
+of the changelogs (more than 150 bug fixes) a little earlier in this
+thread. The update can be done automatically, but only in a custom
+setup with a custom forum. If you have only changed templates you can
+do it as well automatically but you have to repeat the template
+changes ion the new version. If you have implemented MODs or otherwise
+changed the code you have to do the updates manually which normally
+takes me (roughly) 2 work days, but I am a slow worker :).
+You get a set of "changed files" and normally you just copy them over
+the old files. If you changed something in those files (and had it
+documented!) then you have to do the same change in the new file. And
+you can not update from n to n+2, you have to go from n to n+1 to n+2.
+
+Then you start testing, no matter which setup you have. When I do
+changes or an update I do it locally first for testing, later on the
+server. This is about code changes or updates, it's not so hard.
+
+But what about changes in the template? Most requests of forum users
+involve only templates (like moving or adding a forum line with a
+link). These changes can be done (and have already been done in the
+Mageia forums) by the forum admin in the ACP without involving git or
+sysadmins or mga-forum_developers. Hopefully those are documented.
+
+> on the side of forum management, well, I do not know. That's the part
+> where someone step in and complete my mail.
+
+Well, in a forum we only need 2 kinds of "admins":
+ - the forum admin who is visible in the forum, participates in
+discussions, a contact for users in case of requests or complaints, a
+contact in case of issues between users (if the Global Moderators are
+not able to solve it). Here in fact it is the human social and
+communicative side which is more important than technical knowledge.
+He is the "team leader" of the moderators, doing organisational things
+in the forum (like changing settings in the ACP). That is the
+important position which was not filled most of the time up to now.
+ - the technical forum admin. Somebody with phpbb knowledge who can
+work with mga-forum_developer_group and/or sysadmin team to do code
+changes and updates. He is in close contact with "forum admin" who
+forwards requests of forum users or issues of technical nature
+occuring in the daily life of the forum to him. He is the "bridge" to
+sysadmin group. Of course this can be somebody of the sysadmin group
+or forum_devels as well. He must not be present or communicative in
+the forum.
+
+OTOH these 2 positions can be filled by one person as well but both
+are equally important.
+
+-- 
+wobo
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004334.html b/zarb-ml/mageia-sysadm/2012-March/004334.html new file mode 100644 index 000000000..50c26e468 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004334.html @@ -0,0 +1,58 @@ + + + + [Mageia-sysadm] bonjour^ + + + + + + + + + +

[Mageia-sysadm] bonjour^

+ yxt + yxt at peko.com.cn +
+ Thu Mar 29 00:26:13 CEST 2012 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120329/96a9eeef/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004335.html b/zarb-ml/mageia-sysadm/2012-March/004335.html new file mode 100644 index 000000000..041d78785 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004335.html @@ -0,0 +1,58 @@ + + + + [Mageia-sysadm] hi( + + + + + + + + + +

[Mageia-sysadm] hi(

+ b.pellegatta + b.pellegatta at tin.it +
+ Thu Mar 29 20:41:07 CEST 2012 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120330/4abff836/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004336.html b/zarb-ml/mageia-sysadm/2012-March/004336.html new file mode 100644 index 000000000..05bb75229 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004336.html @@ -0,0 +1,76 @@ + + + + [Mageia-sysadm] Bugzilla security fixes + + + + + + + + + +

[Mageia-sysadm] Bugzilla security fixes

+ Marja van Waes + marja11 at xs4all.nl +
+ Fri Mar 30 09:14:53 CEST 2012 +

+
+ +
Hi all,
+
+CC'ing this mailing list in bug 40 wasn't successful.
+
+Some time ago DMorgan inquired here how to proceed with upgrading our 
+Bugzilla. Since then not much happened.
+https://www.mageia.org/pipermail/mageia-sysadm/2012-February/004182.html
+
+He didn't say the upgrade would solve some security issues. I don't know 
+if he wasn't aware because we forgot to set the "Security" keyword 
+(sorry for that :-[ ), or if the security issues Frédéric Buclin from 
+upstream referred to in  https://bugs.mageia.org/show_bug.cgi?id=40#c15 
+and in https://bugs.mageia.org/show_bug.cgi?id=40#c22 can't harm Mageia.
+
+For me upgrading would solve the problem mentioned here 
+https://bugs.mageia.org/show_bug.cgi?id=40#c17
+
+Regards,
+Marja
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004337.html b/zarb-ml/mageia-sysadm/2012-March/004337.html new file mode 100644 index 000000000..e82ede4ef --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004337.html @@ -0,0 +1,103 @@ + + + + [Mageia-sysadm] perl modules shipped by mageia - the web site! + + + + + + + + + +

[Mageia-sysadm] perl modules shipped by mageia - the web site!

+ Jerome Quelin + jquelin at gmail.com +
+ Fri Mar 30 17:08:35 CEST 2012 +

+
+ +
hi,
+
+so now that pkgcpan.mageia.org is up & running and serving the database
+(thanks again!), i finally took some time to kickstart an idea i was
+toying with: tracking the number of modules shipped by mageia over time.
+
+i also created a very rough webpage for that, which i'd like to expand
+in the future to a more consistent website.
+
+cf attached tarball for the website.
+(note: i'm not a web designer, any help & comments are welcome)
+
+now, i'd like this website to be placed on mageia infrastructure.
+benefits: stats will be updated on a regular basis, and this will allow
+people to quickly see the trend, showing that mageia is perl-developer
+friendly.
+
+to generate the site, it's a matter of running once a day:
+
+    $ magpie webstatic -d /path/to/website
+
+it doesn't take long (less than 5 seconds), and updates the statistics
+besides generating the website.
+
+note that /path/to/website will be wiped, so no other data than the
+website needs to be put in this location. it also means that process
+needs to have write access to the parent dir of /path/to/website
+
+at this point in time, you are now eager to implement that. :) however,
+there are 2 problems:
+
+- "magpie webstatic" is implemented in latest release of magpie, which
+  just hit cpan. the package is updated in svn & ready to be submitted,
+  but it's release freeze. granted, magpie is a leaf package which is
+  only used by mageia perl packagers.
+  ==> do you think i can ask for a freeze push?
+
+- mageia infrastructure is running mga1. so even if magpie is pushed
+  according to previous point, the infra won't have it in their repos.
+  and it also needs perl-ORDB-CPAN-Mageia & perl-RRDTool-OO which are
+  also not available in mga1.
+  ==> if magpie gets pushed, can it be installed on the infra? (by
+      picking & installing the right rpms)
+
+thanks,
+jérôme 
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004338.html b/zarb-ml/mageia-sysadm/2012-March/004338.html new file mode 100644 index 000000000..2ee244768 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004338.html @@ -0,0 +1,70 @@ + + + + [Mageia-sysadm] perl modules shipped by mageia - the web site! + + + + + + + + + +

[Mageia-sysadm] perl modules shipped by mageia - the web site!

+ Jerome Quelin + jquelin at gmail.com +
+ Fri Mar 30 17:09:29 CEST 2012 +

+
+ +
On 12/03/30 17:08 +0200, Jerome Quelin wrote:
+> cf attached tarball for the website.
+> (note: i'm not a web designer, any help & comments are welcome)
+
+and i forgot to attach the tarball...
+sorry, jérôme 
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: mgaperl.tgz
+Type: application/octet-stream
+Size: 8783 bytes
+Desc: not available
+URL: </pipermail/mageia-sysadm/attachments/20120330/07aae665/attachment.obj>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004339.html b/zarb-ml/mageia-sysadm/2012-March/004339.html new file mode 100644 index 000000000..ebc615e3a --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004339.html @@ -0,0 +1,83 @@ + + + + [Mageia-sysadm] perl modules shipped by mageia - the web site! + + + + + + + + + +

[Mageia-sysadm] perl modules shipped by mageia - the web site!

+ nicolas vigier + boklm at mars-attacks.org +
+ Fri Mar 30 17:32:37 CEST 2012 +

+
+ +
On Fri, 30 Mar 2012, Jerome Quelin wrote:
+
+> 
+> at this point in time, you are now eager to implement that. :) however,
+> there are 2 problems:
+> 
+> - "magpie webstatic" is implemented in latest release of magpie, which
+>   just hit cpan. the package is updated in svn & ready to be submitted,
+>   but it's release freeze. granted, magpie is a leaf package which is
+>   only used by mageia perl packagers.
+>   ==> do you think i can ask for a freeze push?
+
+If you expect no regression in this new version, I think a freeze push
+is possible.
+
+> 
+> - mageia infrastructure is running mga1. so even if magpie is pushed
+>   according to previous point, the infra won't have it in their repos.
+>   and it also needs perl-ORDB-CPAN-Mageia & perl-RRDTool-OO which are
+>   also not available in mga1.
+>   ==> if magpie gets pushed, can it be installed on the infra? (by
+>       picking & installing the right rpms)
+
+We have a repository "infra_1" used on mageia servers, where we can push
+those packages.
+
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004340.html b/zarb-ml/mageia-sysadm/2012-March/004340.html new file mode 100644 index 000000000..f8947a39b --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004340.html @@ -0,0 +1,77 @@ + + + + [Mageia-sysadm] perl modules shipped by mageia - the web site! + + + + + + + + + +

[Mageia-sysadm] perl modules shipped by mageia - the web site!

+ Jerome Quelin + jquelin at gmail.com +
+ Fri Mar 30 17:51:55 CEST 2012 +

+
+ +
On 12/03/30 17:32 +0200, nicolas vigier wrote:
+> On Fri, 30 Mar 2012, Jerome Quelin wrote:
+> If you expect no regression in this new version, I think a freeze push
+> is possible.
+
+given that it is a whole new sub-command, existing code was not even
+touched.
+
+> > - mageia infrastructure is running mga1. so even if magpie is pushed
+> >   according to previous point, the infra won't have it in their repos.
+> >   and it also needs perl-ORDB-CPAN-Mageia & perl-RRDTool-OO which are
+> >   also not available in mga1.
+> >   ==> if magpie gets pushed, can it be installed on the infra? (by
+> >       picking & installing the right rpms)
+> 
+> We have a repository "infra_1" used on mageia servers, where we can push
+> those packages.
+
+ok, then i'll request a freeze push. thanks!
+jérôme 
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004341.html b/zarb-ml/mageia-sysadm/2012-March/004341.html new file mode 100644 index 000000000..b367971f7 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004341.html @@ -0,0 +1,69 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Mar 30 18:10:58 CEST 2012 +

+
+ +
Hi
+is the svn server down?
+
+It looks like it's not possible to commit anymore:
+Network connection closed unexpectedly: Unable to connect to a
+repository at URL 'svn+ssh://svn.mageia.org/svn/soft/rpmdrake/trunk':
+To better debug SSH connection problems, remove the -q option from
+'ssh' in the [tunnels] section of your Subversion configuration file.
+at /usr/lib64/git-core/git-svn line 920
+
+
+See you
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004342.html b/zarb-ml/mageia-sysadm/2012-March/004342.html new file mode 100644 index 000000000..5d4e4f4e5 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004342.html @@ -0,0 +1,78 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Mar 30 18:32:32 CEST 2012 +

+
+ +
On Fri, Mar 30, 2012 at 17:10, Thierry Vignaud <thierry.vignaud at gmail.com>wrote:
+
+> Hi
+> is the svn server down?
+>
+
+It seems to be up...
+
+
+> It looks like it's not possible to commit anymore:
+> Network connection closed unexpectedly: Unable to connect to a
+> repository at URL 'svn+ssh://svn.mageia.org/svn/soft/rpmdrake/trunk':
+> To better debug SSH connection problems, remove the -q option from
+> 'ssh' in the [tunnels] section of your Subversion configuration file.
+> at /usr/lib64/git-core/git-svn line 920
+>
+
+... but not reachable, as for the other servers in Marseille
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120330/5c126c80/attachment-0001.html>
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004343.html b/zarb-ml/mageia-sysadm/2012-March/004343.html new file mode 100644 index 000000000..1adea3602 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004343.html @@ -0,0 +1,73 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Fri Mar 30 18:36:38 CEST 2012 +

+
+ +
2012/3/30 Thierry Vignaud <thierry.vignaud at gmail.com>:
+> Hi
+> is the svn server down?
+>
+> It looks like it's not possible to commit anymore:
+> Network connection closed unexpectedly: Unable to connect to a
+> repository at URL 'svn+ssh://svn.mageia.org/svn/soft/rpmdrake/trunk':
+> To better debug SSH connection problems, remove the -q option from
+> 'ssh' in the [tunnels] section of your Subversion configuration file.
+> at /usr/lib64/git-core/git-svn line 920
+
+I've been m getting timeouts with forums, bugzilla, wiki for 10-15
+minutes now. Main website works. Mail server works obviously
+
+-- 
+wobo
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004344.html b/zarb-ml/mageia-sysadm/2012-March/004344.html new file mode 100644 index 000000000..93a7b1247 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004344.html @@ -0,0 +1,77 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ D.Morgan + dmorganec at gmail.com +
+ Fri Mar 30 21:48:26 CEST 2012 +

+
+ +
On Fri, Mar 30, 2012 at 6:36 PM, Wolfgang Bornath
+<molch.b at googlemail.com> wrote:
+> 2012/3/30 Thierry Vignaud <thierry.vignaud at gmail.com>:
+>> Hi
+>> is the svn server down?
+>>
+>> It looks like it's not possible to commit anymore:
+>> Network connection closed unexpectedly: Unable to connect to a
+>> repository at URL 'svn+ssh://svn.mageia.org/svn/soft/rpmdrake/trunk':
+>> To better debug SSH connection problems, remove the -q option from
+>> 'ssh' in the [tunnels] section of your Subversion configuration file.
+>> at /usr/lib64/git-core/git-svn line 920
+>
+> I've been m getting timeouts with forums, bugzilla, wiki for 10-15
+> minutes now. Main website works. Mail server works obviously
+>
+> --
+> wobo
+
+main website works because it is not hosted on the same place
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004345.html b/zarb-ml/mageia-sysadm/2012-March/004345.html new file mode 100644 index 000000000..dc0014128 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004345.html @@ -0,0 +1,74 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ D.Morgan + dmorganec at gmail.com +
+ Fri Mar 30 21:48:52 CEST 2012 +

+
+ +
On Fri, Mar 30, 2012 at 6:10 PM, Thierry Vignaud
+<thierry.vignaud at gmail.com> wrote:
+> Hi
+> is the svn server down?
+>
+> It looks like it's not possible to commit anymore:
+> Network connection closed unexpectedly: Unable to connect to a
+> repository at URL 'svn+ssh://svn.mageia.org/svn/soft/rpmdrake/trunk':
+> To better debug SSH connection problems, remove the -q option from
+> 'ssh' in the [tunnels] section of your Subversion configuration file.
+> at /usr/lib64/git-core/git-svn line 920
+>
+>
+> See you
+
+
+yes seems we have a pb on our server hosting for now.
+
+ + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004346.html b/zarb-ml/mageia-sysadm/2012-March/004346.html new file mode 100644 index 000000000..632815bf7 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004346.html @@ -0,0 +1,57 @@ + + + + [Mageia-sysadm] bon cadeau_ + + + + + + + + + +

[Mageia-sysadm] bon cadeau_

+ compras + compras at italicasaude.com.br +
+ Fri Mar 30 10:49:00 CEST 2012 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-sysadm/attachments/20120330/3574f27c/attachment-0001.html>
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004347.html b/zarb-ml/mageia-sysadm/2012-March/004347.html new file mode 100644 index 000000000..8b5297c4e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004347.html @@ -0,0 +1,59 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ nicolas vigier + boklm at mars-attacks.org +
+ Fri Mar 30 22:21:07 CEST 2012 +

+
+ +
There is a problem with the switch where our servers are connected.
+We may need to replace it.
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004348.html b/zarb-ml/mageia-sysadm/2012-March/004348.html new file mode 100644 index 000000000..a8433d516 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004348.html @@ -0,0 +1,152 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ Michael Scherer + misc at zarb.org +
+ Sat Mar 31 02:22:49 CEST 2012 +

+
+ +
Le vendredi 30 mars 2012 à 22:21 +0200, nicolas vigier a écrit :
+> There is a problem with the switch where our servers are connected.
+> We may need to replace it.
+
+mtr ryu and mtr alamut show the problem is just at the entry of the ielo
+network :
+
+on ryu, there is 6 hops after 
+xe2-2-0.ter2.eqx2.par.as8218.eu
+
+ge1-5.br1.rdb.par.ielo.net
+ge-1-6-neo-cr2.eqx-prs.fr.rt.ielo.net
+2ge-e1-17-e1-18-cr5.le9-lyon.fr.rt.ielo.net
+2ge-e1-17-e1-18-cr4.le9-mrs.fr.rt.ielo.net
+ge-2-1-ve25-cr3.ldr-mrs.fr.rt.ielo.net
+
+I am not a expert into deciphering network admin language, but I suppose
+that :
+- since that's all ielo.net, that's also the same type of convention
+used for all equipements.
+
+ge usually mean "gigabit ethernet", 2ge maybe is when there is 2 cards,
+or something like that.
+
+ldr-mrs mean "liandier marseile" ( ie, the location of our hoster,
+liandier street, in Marseille ), so that's a network device in the
+server room.
+
+The 2 others one are gigabit switch , 1 in Marseille, the other one in
+Lyon. le9 is the french for "the 9", the old name of a ISP now merged
+with SFR ( another french isp/telephony provider ). If we see the list
+of PoP of ielo ( a pop being a equipment where someone can connect ) :
+http://www.ielo.net/solutions/infrastructures/points-de-presence/ 
+
+We see that indeed, they are in Lyon and Marseille in "le neuf"
+datacenter ( ie, le 9 ).
+
+There, they are connected to lyonIX, as seen here 
+http://www.lyonix.net/fr/a-propos-de-lyonix/participants-lyonix
+( a IX being a place where ISP interconnect their network, seek
+"internet exchange" on wikipedia )
+
+
+- ge-1-6-neo-cr2.eqx-prs.fr.rt.ielo.net
+
+and then, they go to the equinix datacenter in Paris ( eqx-prs ), and
+they are connected to as8218.eu, that is neotelecom ( hence "neo" ). 
+
+See for the detail of the as 
+http://www.peeringdb.com/view.php?asn=8218
+
+( a AS being a autonomous system, think of it as a network under the
+control of one single administrative entity, the internet being a
+network of network, ie interconnection of AS ).
+
+
+for the mageia.org servers, there is nothing. 
+
+At first sight, I would say that having our switch ( ie, the small
+consumer grade equipment we use to interconnect to the main
+cisco/hp/whatever switch of Lost oasis ) would not cause such issues
+( ie, I would expect to drop paquet at the last step ). However, since
+all others servers on the same Lost Oasis switch seems to work, that's
+also weird.
+
+For the record, I see that 212.85.158.145 ( alamut default gateway,
+whose reverse is gateway-mageia.ielo.net ) is not answering to ping and
+on the other hand, the default gateway for zarb.org ( 212.85.158.1 )
+answer to ping. 
+
+And I am pretty sure that this gateway is after our switch from a
+network point of view, and so that this should answer fine if our switch
+is unplugged.  
+
+So I suppose that this device ( 158.45 ) do send network
+topology/routing with OSPF or RIP etc, and for some reason, it no longer
+announce the route for our network.
+
+It could be caused by our switch being broken, but that would be rather
+strange, as I do not know any network equipment that would act like this
+( doesn't mean that it doesn't exist, but usually, network is not that
+smart ).
+
+
+So what did IELO said exactly ?
+
+( cause "our switch" can mean the switch we use, or the switch they use
+for us, as I doubt they remember do know exactly how everything is done
+for all the client they have  )
+
+And more important, what can we do to diagnose the issue, does it have
+to wait on Monday ? 
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004349.html b/zarb-ml/mageia-sysadm/2012-March/004349.html new file mode 100644 index 000000000..4fb97d29e --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004349.html @@ -0,0 +1,101 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ nicolas vigier + boklm at mars-attacks.org +
+ Sat Mar 31 12:51:51 CEST 2012 +

+
+ +
On Sat, 31 Mar 2012, Michael Scherer wrote:
+
+> 
+> For the record, I see that 212.85.158.145 ( alamut default gateway,
+> whose reverse is gateway-mageia.ielo.net ) is not answering to ping and
+> on the other hand, the default gateway for zarb.org ( 212.85.158.1 )
+> answer to ping. 
+> 
+> And I am pretty sure that this gateway is after our switch from a
+> network point of view, and so that this should answer fine if our switch
+> is unplugged.  
+> 
+> So I suppose that this device ( 158.45 ) do send network
+> topology/routing with OSPF or RIP etc, and for some reason, it no longer
+> announce the route for our network.
+> 
+> It could be caused by our switch being broken, but that would be rather
+> strange, as I do not know any network equipment that would act like this
+> ( doesn't mean that it doesn't exist, but usually, network is not that
+> smart ).
+
+According to gradator, this is normal if the switch is down. When the
+port is down, OSPF automatically clear the route.
+
+> 
+> So what did IELO said exactly ?
+
+The port where our switch is connected is down.
+
+> 
+> ( cause "our switch" can mean the switch we use, or the switch they use
+> for us, as I doubt they remember do know exactly how everything is done
+> for all the client they have  )
+> 
+> And more important, what can we do to diagnose the issue, does it have
+> to wait on Monday ? 
+
+I think we cannot do a lot, until someone from LO is in the datacenter
+and can check the switch, to see if we need to replace it.
+
+But even if the swich is not the problem, it would be a good idea to
+replace it for a bigger one, to allow us to connect the arm boards on
+it (instead of connecting them behind valstar). We also need to replace
+one of the disk on the arm boards which seems to be not working.
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004350.html b/zarb-ml/mageia-sysadm/2012-March/004350.html new file mode 100644 index 000000000..ce4e068ae --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004350.html @@ -0,0 +1,72 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ nicolas vigier + boklm at mars-attacks.org +
+ Sat Mar 31 13:46:29 CEST 2012 +

+
+ +
On Sat, 31 Mar 2012, nicolas vigier wrote:
+
+> 
+> But even if the swich is not the problem, it would be a good idea to
+> replace it for a bigger one, to allow us to connect the arm boards on
+> it (instead of connecting them behind valstar). We also need to replace
+> one of the disk on the arm boards which seems to be not working.
+
+So what we can do :
+ - we wait until someone can check the switch, probably on monday
+   morning
+ - on monday afternoon we buy a new switch in paris, like this one :
+   http://www.grosbill.com/4-d_link_dgs_1024d_-58561-reseaux-reseau_filaire
+ - on tuesday someone go to marseille and replace the switch and also
+   the disk on the arm board. Train with carte 12-30 costs 99,90 euros.
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004351.html b/zarb-ml/mageia-sysadm/2012-March/004351.html new file mode 100644 index 000000000..af38535ad --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004351.html @@ -0,0 +1,121 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ Michael Scherer + misc at zarb.org +
+ Sat Mar 31 15:12:18 CEST 2012 +

+
+ +
Le samedi 31 mars 2012 à 12:51 +0200, nicolas vigier a écrit :
+> On Sat, 31 Mar 2012, Michael Scherer wrote:
+> 
+> > 
+> > For the record, I see that 212.85.158.145 ( alamut default gateway,
+> > whose reverse is gateway-mageia.ielo.net ) is not answering to ping and
+> > on the other hand, the default gateway for zarb.org ( 212.85.158.1 )
+> > answer to ping. 
+> > 
+> > And I am pretty sure that this gateway is after our switch from a
+> > network point of view, and so that this should answer fine if our switch
+> > is unplugged.  
+> > 
+> > So I suppose that this device ( 158.45 ) do send network
+> > topology/routing with OSPF or RIP etc, and for some reason, it no longer
+> > announce the route for our network.
+> > 
+> > It could be caused by our switch being broken, but that would be rather
+> > strange, as I do not know any network equipment that would act like this
+> > ( doesn't mean that it doesn't exist, but usually, network is not that
+> > smart ).
+> 
+> According to gradator, this is normal if the switch is down. When the
+> port is down, OSPF automatically clear the route.
+
+But what about the default gateway ? IIRC, that's not our switch ( as
+this is just a layer 2 switch ), so did it disappear on purpose once the
+network disappeared too ? 
+
+
+> > 
+> > So what did IELO said exactly ?
+> 
+> The port where our switch is connected is down.
+
+> But even if the swich is not the problem, it would be a good idea to
+> replace it for a bigger one, to allow us to connect the arm boards on
+> it (instead of connecting them behind valstar). We also need to replace
+> one of the disk on the arm boards which seems to be not working.
+
+Connecting them behind valstar was also to protect them until we
+properly secured them, since the password is still weak and easy to
+attack from bruteforce. And AFAIK, we didn't plan to give direct access
+to people, so that was useless and I think moving to a bastion model for
+ssh access would be a improvement in term of security for others
+builders too ( jonund, ecosse, and maybe fiona, depending how the backup
+are done ).
+
+Also, just replacing the switch is not a improvement, since we will have
+the same issue if this switch break ( unlikely, but so was the current
+breakage, or the various hardware issues we faced each time we got there
+) so what about trying to have a more redundant setup ?
+
+Most, if not all, of our servers have 2 ethernet interface, so we could
+try to see if bonding could help ( in case of ethernet card failure ) or
+see if we can find a setup with 2 switchs ( one that doesn't cost too
+much, cause of course, cisco can solve the issue for us, we just cannot
+afford it ). 
+
+Can we afford one or two switchs that support it ? ( I lost the name of
+the current flavor du jour in term of bonding ) 
+
+-- 
+Michael Scherer
+
+
+ + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/004352.html b/zarb-ml/mageia-sysadm/2012-March/004352.html new file mode 100644 index 000000000..0f47bced2 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/004352.html @@ -0,0 +1,122 @@ + + + + [Mageia-sysadm] is the svn server down? + + + + + + + + + +

[Mageia-sysadm] is the svn server down?

+ Maarten Vanraes + alien at rmail.be +
+ Sat Mar 31 18:16:22 CEST 2012 +

+
+ +
Op zaterdag 31 maart 2012 15:12:18 schreef Michael Scherer:
+> Le samedi 31 mars 2012 à 12:51 +0200, nicolas vigier a écrit :
+> > On Sat, 31 Mar 2012, Michael Scherer wrote:
+> > > For the record, I see that 212.85.158.145 ( alamut default gateway,
+> > > whose reverse is gateway-mageia.ielo.net ) is not answering to ping and
+> > > on the other hand, the default gateway for zarb.org ( 212.85.158.1 )
+> > > answer to ping.
+> > > 
+> > > And I am pretty sure that this gateway is after our switch from a
+> > > network point of view, and so that this should answer fine if our
+> > > switch is unplugged.
+> > > 
+> > > So I suppose that this device ( 158.45 ) do send network
+> > > topology/routing with OSPF or RIP etc, and for some reason, it no
+> > > longer announce the route for our network.
+> > > 
+> > > It could be caused by our switch being broken, but that would be rather
+> > > strange, as I do not know any network equipment that would act like
+> > > this ( doesn't mean that it doesn't exist, but usually, network is not
+> > > that smart ).
+> > 
+> > According to gradator, this is normal if the switch is down. When the
+> > port is down, OSPF automatically clear the route.
+> 
+> But what about the default gateway ? IIRC, that's not our switch ( as
+> this is just a layer 2 switch ), so did it disappear on purpose once the
+> network disappeared too ?
+> 
+> > > So what did IELO said exactly ?
+> > 
+> > The port where our switch is connected is down.
+> > 
+> > But even if the swich is not the problem, it would be a good idea to
+> > replace it for a bigger one, to allow us to connect the arm boards on
+> > it (instead of connecting them behind valstar). We also need to replace
+> > one of the disk on the arm boards which seems to be not working.
+> 
+> Connecting them behind valstar was also to protect them until we
+> properly secured them, since the password is still weak and easy to
+> attack from bruteforce. And AFAIK, we didn't plan to give direct access
+> to people, so that was useless and I think moving to a bastion model for
+> ssh access would be a improvement in term of security for others
+> builders too ( jonund, ecosse, and maybe fiona, depending how the backup
+> are done ).
+> 
+> Also, just replacing the switch is not a improvement, since we will have
+> the same issue if this switch break ( unlikely, but so was the current
+> breakage, or the various hardware issues we faced each time we got there
+> ) so what about trying to have a more redundant setup ?
+> 
+> Most, if not all, of our servers have 2 ethernet interface, so we could
+> try to see if bonding could help ( in case of ethernet card failure ) or
+> see if we can find a setup with 2 switchs ( one that doesn't cost too
+> much, cause of course, cisco can solve the issue for us, we just cannot
+> afford it ).
+> 
+> Can we afford one or two switchs that support it ? ( I lost the name of
+> the current flavor du jour in term of bonding )
+
+i think you're looking for distributed trunking? ie: having 2 cables in two 
+separate switches, so if a switch fails, it stays working...
+
+but those switches are quite expensive, iinm at least 2kEUR/switch
+
+non-distributed trunking is alot cheaper, but that just means half the servers 
+are down.
+
+or we could just not bond and have 2 different networks over such servers. that 
+also works for redundancy, but on l3 instead of l2 and alot cheaper...
+
+ + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ diff --git a/zarb-ml/mageia-sysadm/2012-March/author.html b/zarb-ml/mageia-sysadm/2012-March/author.html new file mode 100644 index 000000000..b1f4157f2 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/author.html @@ -0,0 +1,552 @@ + + + + The Mageia-sysadm March 2012 Archive by author + + + + + +

March 2012 Archives by author

+ +

Starting: Tue Mar 6 13:14:43 CET 2012
+ Ending: Sat Mar 31 18:16:22 CEST 2012
+ Messages: 101

+

+

+ Last message date: + Sat Mar 31 18:16:22 CEST 2012
+ Archived on: Sat Mar 31 18:17:31 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-sysadm/2012-March/date.html b/zarb-ml/mageia-sysadm/2012-March/date.html new file mode 100644 index 000000000..4e08abc1d --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/date.html @@ -0,0 +1,552 @@ + + + + The Mageia-sysadm March 2012 Archive by date + + + + + +

March 2012 Archives by date

+ +

Starting: Tue Mar 6 13:14:43 CET 2012
+ Ending: Sat Mar 31 18:16:22 CEST 2012
+ Messages: 101

+

+

+ Last message date: + Sat Mar 31 18:16:22 CEST 2012
+ Archived on: Sat Mar 31 18:17:31 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-sysadm/2012-March/index.html b/zarb-ml/mageia-sysadm/2012-March/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/index.html @@ -0,0 +1 @@ +thread.html \ No newline at end of file diff --git a/zarb-ml/mageia-sysadm/2012-March/subject.html b/zarb-ml/mageia-sysadm/2012-March/subject.html new file mode 100644 index 000000000..e4275ff3c --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/subject.html @@ -0,0 +1,552 @@ + + + + The Mageia-sysadm March 2012 Archive by subject + + + + + +

March 2012 Archives by subject

+ +

Starting: Tue Mar 6 13:14:43 CET 2012
+ Ending: Sat Mar 31 18:16:22 CEST 2012
+ Messages: 101

+

+

+ Last message date: + Sat Mar 31 18:16:22 CEST 2012
+ Archived on: Sat Mar 31 18:17:31 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-sysadm/2012-March/thread.html b/zarb-ml/mageia-sysadm/2012-March/thread.html new file mode 100644 index 000000000..370679f71 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2012-March/thread.html @@ -0,0 +1,713 @@ + + + + The Mageia-sysadm March 2012 Archive by thread + + + + + +

March 2012 Archives by thread

+ +

Starting: Tue Mar 6 13:14:43 CET 2012
+ Ending: Sat Mar 31 18:16:22 CEST 2012
+ Messages: 101

+

+

+ Last message date: + Sat Mar 31 18:16:22 CEST 2012
+ Archived on: Sat Mar 31 18:17:31 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + -- cgit v1.2.1