https://wiki.mageia.org/mw-en/api.php?action=feedcontributions&user=Dtux&feedformat=atomMageia wiki - User contributions [en]2024-03-29T08:33:25ZUser contributionsMediaWiki 1.31.16https://wiki.mageia.org/mw-en/index.php?title=Events_Box&diff=59650Events Box2023-10-20T16:13:35Z<p>Dtux: /* Next, planned locations */</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Marcom]]<br />
[[Category:Atelier]]<br />
[[Category:Events]]<br />
<br />
We need a first, small, limited events box to help keep together tools for each event.<br />
<br />
See the [[Events HowTo]] as well.<br />
<br />
== How does the box look like? ==<br />
TODO, picture<br />
<br />
== What's in the box? ==<br />
Box contents can be donated, directly, or through http://www.mageia.org/donate/.<br />
<br />
* contents checklist including inventory (for CDs/stickers/goodies) and state of tablecloths (washed/not washed).<br />
* cash box<br />
* a pen and a notebook<br />
<br />
Showcase:<br />
* big posters with Mageia logo - we have some<br />
* kakemono - we have one (and can get extra banners if wanted); posters fit in kakemono case<br />
<br />
Distribute:<br />
* CD, DVD - we have some discs left for Mageia 1, we need a solution for Mageia 2<br />
<br />
Goodies:<br />
* tshirts - we have some left from FOSDEM 2011 - we need an inventory and new series<br />
* stationery (stickers, contact list, flyers, contact cards/business cards, blank pre-printed CDs (to burn on the stand), CD sleeves) - we have some left - we need new ones - for booth and to distribute to attendees when one speaks at a conference<br />
<br />
== Where is the box? ==<br />
<br />
=== Current location of the box ===<br />
<br />
=== Current goodies around Europe ===<br />
<br />
{| style="color:black; cellpadding="5%" cellpadding="5%" cellspacing="0" border="1"<br />
|Country <br />
|city <br />
|Tshirts <br />
|stickers <br />
|flyers <br />
|USB Keys <br />
|pens <br />
|Tablecloth <br />
|kakemono <br />
|others <br />
|-<br />
|France <br />
|Lyon <br />
|16 x S 25 x M <br />
23 x L <br />
XL x 1 <br />
XXL x 3 <br />
ladies - S x 5 - M x 13 - L x 5 - 3 x XL <br />
|<br />
|<br />
| <br />
|66 Pens <br />
|1 tablecloth <br />
|1 kakemono <br />
|}<br />
<br />
=== Next, planned locations ===<br />
* Campus du Libre - 21 october 2023 - Lyon France<br />
* Capitole du Libre - 18-19 november 2023 - Toulouse France - https://capitoledulibre.org<br />
<br />
=== Base locations ===<br />
Ideally, two locations, in France or in its direct periphery. Events that we will attend with this box are among: FOSDEM, LinuxTag, Solutions Linux, RMLL, OWF, JDLL, ORR, what others in Europe?<br />
<br />
=== Transportation costs ===<br />
Use these max limits to estimate roughly the cost:<br />
* weight: 10 kg<br />
* dimensions: 55 x 35 x 25 cm<br />
* declared value: 3000 €<br />
<br />
* cities: Paris, Marseille, Bordeaux, Nantes, Berlin, Bruxelles, London, Barcelona, Madrid, Rome, Lisbon<br />
Indicative average max prices (UPS - https://wwwapps.ups.com/ctc/request):<br />
* Paris -> {Brussel,Berlin}, ~300 €<br />
* Nantes -> Paris, ~100 € (about the same intra France?)<br />
<br />
* 10kg 120 x 60 x 60 cm 6,90€ (intra Germany), 22,00€ Germany->France (http://www.dhl.de/en.html)<br />
<br />
The actual cost may be less (the box may be lighter, smaller) or more (change in transportation fees).<br />
<br />
=== Asking for the box ===<br />
Wanted home candidates (multiple is better):<br />
* Nantes, FR: rda<br />
* Paris, FR: baud (Versailles, for SL, RMLL, PremierSamedi])<br />
* Berlin, DE: ?<br />
* Brussel, BE: ?<br />
* Lyon<br />
* other?<br />
<br />
== Grow the box! ==<br />
<br />
Here are other stuff good to have in the box.<br />
<br />
The whole package (box + contents) must not exceed 10 kg and must keep 55 x 35 x 25 cm (easier for someone to travel with it).<br />
<br />
* BOX itself (wish, no model/size decided) a box to fit all this, that can be handled by a single person, that has wheels and handles. Suggest medium (20kg, international roll-on size or a little larger) suitcase with at least one zipper poclet on the outside (for padlock &c during shipping).<br />
<br />
* (wish) event schedule and [[Events HowTo|howto]] (in this very wiki at least; a print copy is good too)<br />
* (wish) two large pieces of cloth: one white, one black. (see tablecloths in showcase. Black may be redundant...)<br />
* (wish) cables? RJ45, video, USB, multi powerplugs, type <br />
* (wish) small medikit, scissors, thread<br />
* (wish) velcro dots (both hook and fuzz), with adhesive back, two types (standard and strong)<br />
* (wish) good-quality packaging tape in tape-gun<br />
* (wish) good brass padlock to lock suitcase when travelling with someone<br />
* (wish) cycle lock (click-together type with coated cable or chain) to lock Events Box to racks on trains - prevent theft of Box<br />
<br />
Showcase stuff:<br />
* (must have) - 2 tablecloths for exhibition tables, white with mageia logo placed to be at front of table, sized for 2 180cm long x 90cm wide x 80cm high tables (so, (2*180)+(2*80) long and 90+(2*80) wide.) Mageia logo can be on vinyl like banner and poster, and be fixed with double-sided tape or velcro, or can be printed onto the cloth.<br />
* (wish) perspex or portable/foldable metal display stands for leaflets/brochures/cds. Metal will stand on floor beside tables, perspex on table (so metal might work better).<br />
* (wish, no model decided, price tag max 300 €) dedicated projector<br />
* (wish, no model decided, price tag max 200 € each) 2 dedicated laptops or small boxes (cubox, other?): one for projection, the other one for direct manipulation<br />
** one potential candidate, white ASRock Ion330 + keyboard + mouse and cables (second hand, ~150 € worth, rda)<br />
* for projection:<br />
** (wish) simple slides calling for contributors, with specific & easy tasks,<br />
** (wish) project presentation, demonstrating the product,<br />
** (wish) give immediate contact hooks (Web, IRC, Twitter, other events)<br />
** (wish) display a small twitter wall of the current event<br />
<br />
Distribute:<br />
* (wish) a system to dump a Mageia system image to USB key or portable HD<br />
* (wish) mageia-logo USB sticks<br />
* (idea) one of the computer is used either as a Wi-Fi access point (advertised as "Get Mageia") or as a station in the local network, and advertises shared directories (FTP, Samba) containing Mageia ISOs<br />
<br />
<br />
* interactive, live access to forums, IRC channels and other info source about the project<br />
** Maybe a projector connected to a laptop? Maybe more than one? Forums, wiki, an event-central IRC channel? I think a projector displaying a live feed of #mageia-social would be a good place to start. --[[User:Max|max]] 19:56, 16 July 2012 (UTC)<br />
* computers/projectors showcasing the OS: laptops, tablets, projectors<br />
<br />
<br />
== Other projects events boxes ==<br />
* http://live.gnome.org/GnomeEventsBox<br />
* other ?<br />
<br />
== Other ideas of goodies ==<br />
* USB key <br />
** 4 GB should be enough, ~5 € and could be proposed at 10 € with Mageia logo<br />
** http://www.memoriasusb.com<br />
* USB card<br />
** was here at Fosdem 2013, not seen since :/ 2 GB card with Mageia logo<br />
* stickers<br />
** see https://wiki.mageia.org/en/Commercial_vendors#Goodies_vendors<br />
<br />
== Documents to promote Mageia ==<br />
<br />
<br />
* stickers (meta-key, powered by, GNU/Linux Mageia logo) : http://download.tuxfamily.org/cauldron/mageia/logo/<br />
* prez : http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7A.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/FOSDEM%202014%20Flyer.odt french and english versions<br />
* http://www.mageia.org/about/media/ mainly logo & CD/DVD covers, available in SVG<br />
* FOSDEM 2015 flyer: [[File:Mageia_flyer_2015_EN.odt]]<br />
* http://stormi.lautre.net/fichiers/jdll/2015/ french and english version showed at JDLL 2015</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Events_Box&diff=59649Events Box2023-10-20T16:11:13Z<p>Dtux: </p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Marcom]]<br />
[[Category:Atelier]]<br />
[[Category:Events]]<br />
<br />
We need a first, small, limited events box to help keep together tools for each event.<br />
<br />
See the [[Events HowTo]] as well.<br />
<br />
== How does the box look like? ==<br />
TODO, picture<br />
<br />
== What's in the box? ==<br />
Box contents can be donated, directly, or through http://www.mageia.org/donate/.<br />
<br />
* contents checklist including inventory (for CDs/stickers/goodies) and state of tablecloths (washed/not washed).<br />
* cash box<br />
* a pen and a notebook<br />
<br />
Showcase:<br />
* big posters with Mageia logo - we have some<br />
* kakemono - we have one (and can get extra banners if wanted); posters fit in kakemono case<br />
<br />
Distribute:<br />
* CD, DVD - we have some discs left for Mageia 1, we need a solution for Mageia 2<br />
<br />
Goodies:<br />
* tshirts - we have some left from FOSDEM 2011 - we need an inventory and new series<br />
* stationery (stickers, contact list, flyers, contact cards/business cards, blank pre-printed CDs (to burn on the stand), CD sleeves) - we have some left - we need new ones - for booth and to distribute to attendees when one speaks at a conference<br />
<br />
== Where is the box? ==<br />
<br />
=== Current location of the box ===<br />
<br />
=== Current goodies around Europe ===<br />
<br />
{| style="color:black; cellpadding="5%" cellpadding="5%" cellspacing="0" border="1"<br />
|Country <br />
|city <br />
|Tshirts <br />
|stickers <br />
|flyers <br />
|USB Keys <br />
|pens <br />
|Tablecloth <br />
|kakemono <br />
|others <br />
|-<br />
|France <br />
|Lyon <br />
|16 x S 25 x M <br />
23 x L <br />
XL x 1 <br />
XXL x 3 <br />
ladies - S x 5 - M x 13 - L x 5 - 3 x XL <br />
|<br />
|<br />
| <br />
|66 Pens <br />
|1 tablecloth <br />
|1 kakemono <br />
|}<br />
<br />
=== Next, planned locations ===<br />
* Campus du Libre - 6 november 2021 - Lyon France<br />
* Opensource Experience - 9-10 november 2021 - Paris France - https://www.opensource-experience.com<br />
<br />
=== Base locations ===<br />
Ideally, two locations, in France or in its direct periphery. Events that we will attend with this box are among: FOSDEM, LinuxTag, Solutions Linux, RMLL, OWF, JDLL, ORR, what others in Europe?<br />
<br />
=== Transportation costs ===<br />
Use these max limits to estimate roughly the cost:<br />
* weight: 10 kg<br />
* dimensions: 55 x 35 x 25 cm<br />
* declared value: 3000 €<br />
<br />
* cities: Paris, Marseille, Bordeaux, Nantes, Berlin, Bruxelles, London, Barcelona, Madrid, Rome, Lisbon<br />
Indicative average max prices (UPS - https://wwwapps.ups.com/ctc/request):<br />
* Paris -> {Brussel,Berlin}, ~300 €<br />
* Nantes -> Paris, ~100 € (about the same intra France?)<br />
<br />
* 10kg 120 x 60 x 60 cm 6,90€ (intra Germany), 22,00€ Germany->France (http://www.dhl.de/en.html)<br />
<br />
The actual cost may be less (the box may be lighter, smaller) or more (change in transportation fees).<br />
<br />
=== Asking for the box ===<br />
Wanted home candidates (multiple is better):<br />
* Nantes, FR: rda<br />
* Paris, FR: baud (Versailles, for SL, RMLL, PremierSamedi])<br />
* Berlin, DE: ?<br />
* Brussel, BE: ?<br />
* Lyon<br />
* other?<br />
<br />
== Grow the box! ==<br />
<br />
Here are other stuff good to have in the box.<br />
<br />
The whole package (box + contents) must not exceed 10 kg and must keep 55 x 35 x 25 cm (easier for someone to travel with it).<br />
<br />
* BOX itself (wish, no model/size decided) a box to fit all this, that can be handled by a single person, that has wheels and handles. Suggest medium (20kg, international roll-on size or a little larger) suitcase with at least one zipper poclet on the outside (for padlock &c during shipping).<br />
<br />
* (wish) event schedule and [[Events HowTo|howto]] (in this very wiki at least; a print copy is good too)<br />
* (wish) two large pieces of cloth: one white, one black. (see tablecloths in showcase. Black may be redundant...)<br />
* (wish) cables? RJ45, video, USB, multi powerplugs, type <br />
* (wish) small medikit, scissors, thread<br />
* (wish) velcro dots (both hook and fuzz), with adhesive back, two types (standard and strong)<br />
* (wish) good-quality packaging tape in tape-gun<br />
* (wish) good brass padlock to lock suitcase when travelling with someone<br />
* (wish) cycle lock (click-together type with coated cable or chain) to lock Events Box to racks on trains - prevent theft of Box<br />
<br />
Showcase stuff:<br />
* (must have) - 2 tablecloths for exhibition tables, white with mageia logo placed to be at front of table, sized for 2 180cm long x 90cm wide x 80cm high tables (so, (2*180)+(2*80) long and 90+(2*80) wide.) Mageia logo can be on vinyl like banner and poster, and be fixed with double-sided tape or velcro, or can be printed onto the cloth.<br />
* (wish) perspex or portable/foldable metal display stands for leaflets/brochures/cds. Metal will stand on floor beside tables, perspex on table (so metal might work better).<br />
* (wish, no model decided, price tag max 300 €) dedicated projector<br />
* (wish, no model decided, price tag max 200 € each) 2 dedicated laptops or small boxes (cubox, other?): one for projection, the other one for direct manipulation<br />
** one potential candidate, white ASRock Ion330 + keyboard + mouse and cables (second hand, ~150 € worth, rda)<br />
* for projection:<br />
** (wish) simple slides calling for contributors, with specific & easy tasks,<br />
** (wish) project presentation, demonstrating the product,<br />
** (wish) give immediate contact hooks (Web, IRC, Twitter, other events)<br />
** (wish) display a small twitter wall of the current event<br />
<br />
Distribute:<br />
* (wish) a system to dump a Mageia system image to USB key or portable HD<br />
* (wish) mageia-logo USB sticks<br />
* (idea) one of the computer is used either as a Wi-Fi access point (advertised as "Get Mageia") or as a station in the local network, and advertises shared directories (FTP, Samba) containing Mageia ISOs<br />
<br />
<br />
* interactive, live access to forums, IRC channels and other info source about the project<br />
** Maybe a projector connected to a laptop? Maybe more than one? Forums, wiki, an event-central IRC channel? I think a projector displaying a live feed of #mageia-social would be a good place to start. --[[User:Max|max]] 19:56, 16 July 2012 (UTC)<br />
* computers/projectors showcasing the OS: laptops, tablets, projectors<br />
<br />
<br />
== Other projects events boxes ==<br />
* http://live.gnome.org/GnomeEventsBox<br />
* other ?<br />
<br />
== Other ideas of goodies ==<br />
* USB key <br />
** 4 GB should be enough, ~5 € and could be proposed at 10 € with Mageia logo<br />
** http://www.memoriasusb.com<br />
* USB card<br />
** was here at Fosdem 2013, not seen since :/ 2 GB card with Mageia logo<br />
* stickers<br />
** see https://wiki.mageia.org/en/Commercial_vendors#Goodies_vendors<br />
<br />
== Documents to promote Mageia ==<br />
<br />
<br />
* stickers (meta-key, powered by, GNU/Linux Mageia logo) : http://download.tuxfamily.org/cauldron/mageia/logo/<br />
* prez : http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7A.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/FOSDEM%202014%20Flyer.odt french and english versions<br />
* http://www.mageia.org/about/media/ mainly logo & CD/DVD covers, available in SVG<br />
* FOSDEM 2015 flyer: [[File:Mageia_flyer_2015_EN.odt]]<br />
* http://stormi.lautre.net/fichiers/jdll/2015/ french and english version showed at JDLL 2015</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Mageia_8_Errata-fr&diff=55685Mageia 8 Errata-fr2022-11-09T15:59:36Z<p>Dtux: syntax error</p>
<hr />
<div>[[Category:Erratas]]<br />
[[Category:Mageia 8]]<br />
<br />
{{Bandeau multi-langues-fr|[[Mageia_8_Errata-de|Deutsch]] ; [[Mageia_8_Errata|English]] ; [[Erratas de Mageia 8|Español]] ; [[Mageia_8_Errata-fr|Français]] ; [[Mageia_8_Erratas do Mageia|Português (Portugal)]] ;}}<br />
<br />
== Notes ==<br />
<br />
Cette page est un complément des [[Mageia 8 Notes de version-fr|Notes de version]].<br />
<br />
<!--'''Cette page reflète actuellement la sortie de RC.''' Elle sera révisée pour toute nouvelle RC, et pour les ISO définitives.--><br />
'''Les rubriques ci-dessous précédées de « CORRIGÉ », ont une mise à jour disponible.'''<br />
Donc si vous rencontrez un problème marqué comme résolu, essayez de faire une mise à jour complète. Certains problèmes peuvent nécessiter une déconnexion/login ou un redémarrage. D’autres sont des problèmes d’installation ou de mise à niveau. Notez que la publication d’une mise à jour peut demander 24H pour être disponible sur [http://mirrors.mageia.org/status votre mirroir].<br />
<br />
Seuls les problèmes importants concernant les paquets contenus dans les ISO sont énumérés ici. Nous avons beaucoup de logiciels supplémentaires dans les dépôts.<br />
<br />
Un problème non répertorié que vous voyez peut-être résolu si vous faites une mise à jour complète.<br />
<br />
Voir également les sections des Notes de versions [[Mageia_8_Notes_de_version-fr#Problèmes connus|Problèmes connus]] et [[Mageia_8_Notes_de_version-fr#Signaler un bogue|Rapport de bogue]].<br />
<br />
Attention, nous ajouterons les problèmes provenant de l’outil de suivi des bogues, à savoir<!--[https://bugs.mageia.org/buglist.cgi?keywords=8rc1 rc1], [https://bugs.mageia.org/buglist.cgi?keywords=8rc2 rc2]-->, [https://bugs.mageia.org/buglist.cgi?keywords=FOR_ERRATA8 Pour ERRATA 8], [https://bugs.mageia.org/buglist.cgi?keywords=FOR_RELEASENOTES8 Pour les notes de versions 8] au fur et à mesure qu’ils seront signalés.<br />
<br />
== Démarrage ==<br />
<br />
Pensez à consulter le paragraphe sur les cartes [[#Graphiques|Graphiques]]<br />
<br />
{{Bug|27117}} - Si rootfs est en btrfs, et que {{folder|/boot}} est sur rootfs, GRUB se plaint de ../../grub-core/commands/loadenv.c:216:sparse file not allowed. Ceci est seulement un problème cosmétique. '''Correction manuelle''' dans [https://bugs.mageia.org/show_bug.cgi?id=27117#c3 Commentaire 3].<br />
<br />
== Images autonomes ==<br />
<br />
{{bug|28768}} Le manuel d’utilisation de ''draklive'' inclut dans les images a une page manquante sur l’entrée « Mises à jour ». La [https://doc.mageia.org/draklive/8/fr/content/index.html version en ligne] est complète.<br />
<br />
== Images d’installation ==<br />
<br />
=== Plantage à la fin de l’installation ===<br />
<br />
{{bug|27838}} Certains ordinateurs ont des firmwares bogués, ce qui fait que les écritures sur la NVRAM EFI échouent à la fin de l’installation de Mageia.<br />
<br />
Solution de contournement : Lors de la configuration du chargeur de démarrage à la fin de l’installation : Selectionner rEFInd à la place de GRUB, cocher « Install in /EFI/BOOT », décocher l’option de stockage dans la NVRAM ''(Nouveau pour Mageia 8)''<br />
<br />
=== Installateur réseau ===<br />
<br />
* Sur certaines machines UEFI, l’ISO d’Installation Réseau démarre avec un '''message d’erreur Grub''' : <br />
''error: ../../grub-core/video/readers/png.c:595 invalid filter value'' et affiche le menu Grub2 en mode texte au lieu du mode graphique. Le fonctionnement n’est pas affecté ; il s’agit simplement d’une bizarrerie esthétique. {{bug|28225}}<br />
<br />
==== USB memory formatted with Ventoy ====<br />
<br />
[https://www.ventoy.net/en/index.html {{prog|Ventoy}}] est un outil open source pour créer un lecteur USB amorçable pour les fichiers ISO/WIM/IMG/VHD(x)/EFI.<br />
Avec Ventoy, vous n’avez pas besoin de formater le disque encore et encore, il suffit de copier les fichiers ISO/WIM/IMG/VHD(x)/EFI sur le lecteur USB et de les démarrer directement.<br />
<br />
Après avoir lancé une image réseau, si la source de l’installation de Mageia (qui peut être un DVD d’installation classique ou une copie locale de l’arborescence de fichiers de Mageia) se trouve dans la partition étiquetée « Ventoy » (c’est-à-dire là où les images ISO doivent être stockées), vous devrez peut-être débrancher et rebrancher le périphérique USB pour avoir accès à la partition. [https://bugs.mageia.org/show_bug.cgi?id=28371#c23 Commentaire#23 dans mga#28371]<br />
<br />
Une autre solution consiste à réserver un espace au moment de formater la clé USB avec Ventoy, à formater cette partition avec l’un des systèmes de fichiers acceptés par l’installateur et à stocker la source de l’installation de Mageia dans cette partition. ([https://bugs.mageia.org/show_bug.cgi?id=28371#c33 Commentaire 33 dans mga#28371]).<br />
<br />
{{Note|Bien sûr, si vous avez l’une des images d’installation du DVD « Classique », vous pouvez la sélectionner directement dans le menu de démarrage de la Ventoy.}}<br />
<br />
=== L’image d’installation 32 bits doit être sur DVD pour fonctionner comme dépôt. ===<br />
<br />
Après l’installation du système, les ISOs de l’installation classique peuvent être utilisés comme dépôt, pour installer des logiciels sans utiliser de connexion Internet.<br />
<br />
L’ISO 64 bits fonctionne comme dépôt à la fois sur DVD et sur clé USB. Les ISO 32 bits fonctionnent uniquement comme dépôt à partir d’un DVD.<br />
<br />
== Graphiques ==<br />
<br />
=== AMD/ATI ===<br />
<br />
''Les problèmes décrits sont plus manifestes sur les médias autonomes ou sur les systèmes installés avec l’ISO classique sans que les dépôts de mise à jour soient activés. Certaines mises à jour ont amélioré la situation, certains dépôts de mise à jour sont en cours de réalisation dans le noyau, et le plus important est de voir l’explication et la solution de contournement ci-dessous.''<br />
<br />
* Problème de démarrage avec certains GPU Radeon HD. ''Exemple : {{bug|28154}}''<br />
<br />
* Problème de reprise, malgré un démarrage correct. ''Exemple : {{bug|28863}}''<br />
<br />
* Legacy VGA ne fonctionne pas encore ''(problèmes en amont)'', Ainsi, par exemple, si vous avez un '''double écran avec un écran VGA''', l’écran VGA ne fonctionne pas. ''Exemple : {{bug|28817}}''<br />
<br />
''Explication :'' Pour les cartes graphiques AMD basées sur les familles Southern Islands (Tahiti, Pitcairn, Oland, Verde, Hainan) et Sea Islands (Kaveri, Bonaire, Hawaii, Kabini, Mullins), nous utilisons désormais par défaut le nouveau pilote amdgpu au lieu de l’ancien pilote radeon, moins développé. Nous apprécierons les retours en cas d’échec sur votre matériel, voir les différents bogues {{bug|}} ci-dessus.<br />
<br />
'''Solution de contournement''' pour les deux cas ci-dessus : ''utilisez l’ancien pilote radeon'' (comme Mageia 7 par défaut) en ajoutant ce qui suit sur [[Comment_ajouter_des_options_au_noyau-fr#Avec_le_chargeur_de_boot_Grub_2_2|la ligne de commande du noyau]] :<br />
<br />
Pour les cartes Southern Island : {{cmd|<nowiki>radeon.si_support=1 amdgpu.si_support=0</nowiki>}}.<br />
<br />
Pour les cartes Sea Islands : {{cmd|<nowiki>radeon.cik_support=1 amdgpu.cik_support=0</nowiki>}}.<br />
<br />
Premièrement utiliser {{cmd|drakx11}} ({{prog|Centre de contrôle Mageia}} Section {{menu|Matériels > Configurer le serveur d’affichage}} onglet {{menu|Carte graphique}}) pour définir le pilote sur ''« ATI radeon HD 4870 and earlier »'' (au moins pour les cartes discrètes).<br />
<br />
En cas d’échec du démarrage en mode graphique, utilisez la fonction {{keypress|Ctrl}}+{{keypress|Alt}}+{{keypress|F2}} (ou redémarrer en mode maintenance) pour ouvrir un terminal et exécuter {{cmd|drakx11}} pour sélectionner un autre pilote, pour redémarrer (taper {{cmd|reboot}}.<br />
<br />
=== Nvidia ===<br />
<br />
Nvidia a négligé de régler les problèmes de sécurité de son pilote de la série 340, nous avons donc dû le retirer des dépôts officiels. Voir les [[Mageia 8 Notes de version-fr#Pilote propriétaire NVIDIA|Notes de version]].<br />
<br />
=== Intel ===<br />
<br />
{{Bug|30189|}} '''Il est également possible d’avoir plus d’un écran sur les derniers chipsets Intel X5XX.''' Intel a publié un nouveau matériel, mais les problèmes n’ont pas encore été corrigés au niveau de leur pilote. La solution de contournement est implémentée dans les noyaux Mageia 5.15.32 et plus dans les mises à jour normales, et 5.16.14 et plus dans les backports. Si vous êtes concerné, démarrez avec seulement un écran connecté et mettez à jour votre système.<br />
<br />
=== LibreOffice, fenêtres minuscules ===<br />
<br />
{{Bug|30152}}. L’étendue de ce problème n’est pas connue, mais il semble qu’il soit lié aux ordinateurs de bureau utilisant Qt, et utilisant le port VGA pour le moniteur. Les fenêtres LibreOffice peuvent se lancer de façon minuscule. Voir le bogue ''[https://bugs.mageia.org/show_bug.cgi?id=30152#c17 Commentaire 17]''. '' Solution : '' glisser le bord de la fenêtre et la redimensionner en taille réelle, au moins deux fois pour chaque application affectée par LibreOffice, une depuis le menu de lancement et une en ouvrant un fichier associé depuis le gestionnaire de fichiers.<br />
<br />
=== Recording your desktop ===<br />
<br />
{{bug|29405}}. Résultats étranges lors de l''''enregistrement du bureau'''. L’étendue de ce problème n’est pas encore identifiée. Le '''contournement''' du bogue [https://bugs.mageia.org/show_bug.cgi?id=30152#c7 30152 c7] résout le problème.<br />
<br />
== Environnements de bureaux ==<br />
<br />
{{Bug|23929}} – Le répertoire « Desktop » sous $HOME n’a pas été traduit lors de l’installation de '''Plasma ou MATE uniquement'''.<br />
<br />
{{Bug|25877}} - '''Netapplet/Mgaapplet/nm_applet''' avec '''Cinammon''' ou '''Xfce''': Lorsque l'applet se trouve dans la barre des taches, sa fenêtre pop-up apparaît uniquement sous la forme d'une barre noire au bas de l'écran. '''Une solution de contournement [https://bugs.mageia.org/show_bug.cgi?id=25877#c1 est proposée ici.]'''<br />
<br />
{{Bug|27601}} – La session graphique peut rester sur un écran noir, avec le surseur de la souris qui reste mobile. Ceci est dû un changement de nom de l’ordinateur pendant le lancement de SDDM, ce qui le fait échouer, en général réalisé par ''avahi'' lorsque le nom d’hôte est ''localhost''. Un remède est de définir un nom d'hôte autre que celui par défaut, par exemple avec la commande ''hostnamectl set-hostname mon-super-ordi.local''.<br />
<br />
CORRIGÉ {{Bug|28378}} – '''SDDM greeter''' ne se souvient pas de la session précédemment exécutée. – '''correction manuelle''': Dans {{file|/etc/sddm.conf}} dans la ligne {{cmd|<nowiki>RememberLastSession=false</nowiki>}} changez ''false'' en ''true''. Ceci est corrigé par une mise à jour. Cette mise à jour définit également le paramètre {{cmd|<nowiki>RememberLastUser=false</nowiki>}}, vous pouvez le définir à la valeur ''true'' si vous souhaitez que le dernier utilisateur soit présélectionné lors de la connexion.<br />
<br />
=== Plasma ===<br />
<br />
La session '''Wayland''' avec les pilotes propriétaires nvidia-current est disponible en s’assurant que « nokmsboot » est supprimé et que « nouveau.modeset=0 » est passé à la ligne de commande du noyau. {{bug|27296}} – La session Plasma Wayland est cassée, et {{bug|28365}} – Le centre de contrôle ne démarre pas avec Plasma Wayland. '''Correction temporaire''' : en tant qu’utilisateur normal, premier problème {{cmd|xhost +si:localuser:root}}<br />
<br />
Les effets de bureau '''Compiz''' ne sont plus compatibles avec Plasma. Si vous l’utilisez avec Plasma sur Mageia 7, désactivez-le dans {{prog|Centre de contrôle Mageia}} {{menu|Matériel -> Configurez les effets bureau 3D}} – '''avant''' de mettre à niveau, et si vous n’avez pas besoin de Compiz pour un autre environnement de bureau, désinstallez-le. Après l’installation ou la mise à niveau de Mageia, vous trouverez les effets de bureau dans {{menu|Configuration du système}} (icône de la barre des tâches) -> {{menu|Espace de travail}} -> {{menu|Comportement de l’espace de travail}} -> {{menu|Effets de bureau}}.<br />
<br />
L’extension clic droit {{prog|kde-rootactions-servicemenu}} de '''Dolphin''' est supprimée, car elle est délaissée en amont et présente des problèmes.<br />
<br />
{{bug|27147}} – Connexions successives multi-utilisateurs, plasmashell ne se connecte plus à n’importe quel utilisateur après s’être éteint.<br />
<br />
{{bug|27183}} – Les réglages par défaut de l’intégration de spectacle de Mageia manquent dans configuration du système de plasma – ''Dans certains cas, après la mise à niveau.'' CORRECTION : Lancer Spectacle, sélectionner le bouton {{menu|Configurer -> Raccourcis -> Lancer Spectacle}}. Changer le paramètre de « Personnalisé » vers « Par défaut » (Imprimer), et confirmer la demande de réassignation dans la fenêtre qui s’affiche.<br />
<br />
'''CORRIGÉ''' grâce aux mises à jour de Mageia 8 : startplasma-x11 génère des '''processus zombies''' - {{bug|27362}}. (plusieurs paquets), {{bug|28824}} (qtbase), {{bug|28859}} (systemd)<br />
<br />
{{bug|28095}} – Le changement d’avatar ne fonctionne pas avec l’installation classique de Mageia 8 mais fonctionne avec l’installation autonome. '''Correction manuelle [https://bugs.mageia.org/show_bug.cgi?id=28095#c5 ici].'''<br />
<br />
{{bug|28287}} – Le nouvel espace de travail plasma ne permet pas de '''déverrouiller les widgets lors de la mise à jour''' depuis l’ancienne version.<br />
Les widgets du bureau et des panneaux de Plasma 5 ne peuvent pas être verrouillés ou déverrouillés à partir de la version 5.18 de Plasma. Cela signifie que tout widget verrouillé avant la mise à niveau ne peut être déverrouillé après. '''Par conséquent, avant de mettre à niveau''', assurez-vous de déverrouiller tous ces widgets.<br />
Si par la suite vous trouvez des widgets verrouillés, cela les déverrouillera :<br />
{{cmd|$ qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"}}<br />
<br />
{{bug|28299}} – Les applications GTK se plaignent (dans le journal) de l’absence de window_decorations.css. – [https://bugs.mageia.org/show_bug.cgi?id=28299#c1 Solution ici]<br />
<br />
{{bug|28342}} – Pas d’ombres pour les menus GTK avec les applications GTK sous l’environnement Plasma. Lorsque le thème « Breeze » est défini dans Configuration du système => Apparence des applications => Style d’application => Configurer le style des applications GNOME/GTK, il n’y a pas d’ombre dans les menus GTK et le clic droit GTK. Contournement : Réglez le sur « Adwaita » (qui est par défaut).<br />
<br />
{{bug|28623}} - Alt+F2 n’ouvre pas la boîte de dialogue pour l’exécution d’une commande. – Correction manuelle : dans la Configuration du système : Raccourcis -> Raccourcis globaux -> Exécuter la commande, cocher « Alt+F2 ». Répondre « Oui » lors de la demande de confirmation. Appliquez, fermez et essayez si ça fonctionne. Recommencez si besoin. Si ça ne fonctionne toujours pas, voir le rapport de bogue. ''*) KRunner peut être traduit par quelque chose correspondant à « Run program ».''<br />
<br />
{{bug|28827}} - '''KDE Connect''' ne peut pas parccourrir les périphériques. ''Explication :'' Si Mageia a été installé à l'aide de l'ISO d'installation classique sans que les dépôts en ligne soient activés, le paquetage suggéré {{pkg|sshfs-fuse}} ne sera pas installé. '''Correction manuelle :''' Installez {{pkg|sshfs-fuse}}.<br />
<br />
=== GNOME ===<br />
<br />
'''Wayland :''' Par défaut, GNOME utilise le serveur d’affichage Wayland. Wayland n’est pas encore complètement mature, et peut ne pas fonctionner correctement sur certains matériels. Normalement, GNOME reviendra automatiquement à l’utilisation du serveur d’affichage X.org si Wayland ne démarre pas, mais dans certains cas, cela ne marche pas. Si le bureau GNOME ne se lance pas après avoir complété la sélection initiale de la langue et de la locale, ou si vous rencontrez des problèmes d’affichage, vous pouvez essayer de forcer GNOME à utiliser le serveur d’affichage X.org en ajoutant {{cmd|nowayland}} aux options de démarrage dans le menu de démarrage initial (Appuyez sur la touche {{keypress|e}} pour modifier les options de démarrage).<br />
<br />
'''Network :''' Par défaut, le service NetworkManager est activé à la place des anciens services de gestion de réseau. Vous pouvez utiliser le menu déroulant accessible depuis le coin supérieur droit du bureau GNOME pour effectuer toute configuration réseau nécessaire. Pour les connexions filaires, le réseau est généralement configuré automatiquement et vous n’avez rien à faire. Pour les réseaux sans fil, vous devrez généralement sélectionner un point d’accès et, s’il est protégé par un mot de passe, entrer ce dernier. La configuration du réseau via le MCC/drakconnect devrait également fonctionner dans la plupart des cas.<br />
<br />
<!--=== Cinnamon ===<br />
<br />
CORRIGÉ {{bug|28129}} (Sur architecture 32 bits) – '''Nemo''' est suspendu au départ du lanceur ou du terminal.--><br />
=== Xfce ===<br />
<br />
{{bug|24134}} – Après la connexion, l’écran peut afficher des bandes noires et blanches ou des effets particuliers pendant quelques secondes.<br />
<br />
{{bug|27795}} – Avec Xfce, net_applet ne réagit pas correctement aux changements d’état de la connexion.<br />
<br />
=== LXQt ===<br />
<br />
{{bug|28360}} Le compositeur pour la transparence, généralement utilisé avec Openbox, était {{pkg|compton}}. Celui-ci est déprécié et remplacé par {{pkg|'''picom'''}}. '''Si vous passez de Mageia 7''', le fichier de configuration {{file|~/.config/compton.conf}} peut avoir des paramètres incompatibles qui doivent être modifiés – Ou simplement supprimer ce fichier. Malheureusement, nous n’avons pas encore d’outil de configuration Picom.<br />
<br />
Picom recherche la configuration dans l’ordre suivant : {{file|~/.config/picom.conf}}, {{file|~/.config/compton.conf}}, {{file|/etc/xdg/picom.conf}}. Cela signifie qu’un picom.conf personnalisé peut résider dans {{folder|~/.config/}} pour une configuration personnelle ou dans {{folder|/etc/xdg/}} pour une configuration à l’échelle du système. Donc, pour une personnalisation par utilisateur, il faut faire une copie du fichier {{file|/etc/xdg/picom.conf}} vers {{folder|~/.config/}} et l’éditer.<br />
<br />
Si vous souhaitez plutôt utiliser la configuration de compton-conf similaire à celle de Mageia 7, installez le rpm de compton-conf puis copiez {{file|/usr/share/compton-conf/compton.conf.example}} et éditez-le comme ci-dessous.<br />
<br />
Comment modifier les paramètres de Compton pour les rendre compatibles avec Picom : Renomer {{file|~/.config/compton.conf}} vers {{file|picom.conf}}, et y désactive les lignes commençant par : {{cmd|no_dnd_shadow, no_dock_shadow, clear shadow, menu_opacity, alpha_step, paint-on-overlay}} en les préparant avec un #. Faites lire la ligne commençant par vsync {{cmd|<nowiki>vsync = false;</nowiki>}}, et remplacer toute la ligne commençant par glx-swap-method avec {{cmd|<nowiki>use-damage = true;</nowiki>}}.<br />
<br />
Pour démarrer Picom: {{menu|Mageia -> Accessoires -> picom}}. Pour que Picom démarre automatiquement à l’ouverture de session : {{menu|LXQt centre de configuration -> Paramètres LXQt -> Paramètres de Session -> Autostart -> Ajouter}} Nom : Picom, Commande : picom.<br />
Un peu d’aide, si nécessaire : 1) Lancer {{cmd|picom}} depuis un terminal et voir la sortie, sortir avec {{keypress|Ctrl}}+{{keypress|C}}. 2) {{file|/etc/xdg/picom.conf}} ont des commentaires.<br />
<br />
---<br />
<br />
'''CORRIGÉ''' pour les nouveaux utilisateurs : {{Bug|28407}} '''Le terminal par défaut dans pcmanfm''' doit être qterminal, et non xterm. '''Correction manuelle''' pour les utilisateurs existants dans les mises à jour ou installations déjà effectuées : Utilisez les préférences de l'interface graphiqe utilisateur de pcmanfm-qt. ''(Notre politique générale est de ne pas forcer les préférences des utilisateurs)''.<br />
<br />
== Logiciels ==<br />
<br />
=== Firefox ESR ===<br />
<br />
'''CORRIGÉ''' par une mise à jour {{Bug|29064}} – Un problème d’empaquetage provoquait diverses anomalies avec quelques sites, en résolvant par exemple {{Bug|27374}}, {{Bug|28359}}.<br />
<br />
Notez que quelques sites choisissent encore de ne pas accepter Firefox ESR (même la version en amont) et exigent une version non-ESR. Vous pouvez informer les sites problématiques que [https://support.mozilla.org/en-US/kb/switch-to-firefox-extended-support-release-esr Firefox ESR n’est pas livré avec les dernières fonctionnalités, mais qu’il dispose des derniers correctifs de sécurité et de stabilité].<br />
<br />
Comme solution de rechange, vous pouvez essayer d’utiliser un commutateur d’agent utilisateur pour usurper un Firefox non-ESR. Vous pouvez également installer la version non-ESR de Firefox, par exemple en utilisant [[Flatpak-fr|Flatpak]] ou d'autres [[Les_méthodes_pour_installer_des_programmes-fr#|méthodes pour installer des programmes]].<br />
<br />
=== Flatpak ===<br />
<br />
Plasma Discover et Gnome-software préfèrent [[Flatpak-fr|Flatpack]] comme le décrit le bogue {{bug|27620#c5}} aux paquets RPM de Mageia.<br />
<br />
=== Problèmes liés aux Backports ===<br />
<br />
{{Bug|29830}} - drakrpm sélectionne automatiquement les dépendances d’un dépôt désactivé. Cela peut installer des versions incompatibles.<br />
<br />
Lorsque vous avez configuré le dépôt de backports (ce qui est normal), les outils graphiques de Mageia choisissent les dépendances à partir de celui-ci, même si, normalement, il n’est pas activé. Un exemple typique est que PHP8.1 est installé comme dépendance pour quelque chose qui nécessite PHP, mais certaines de ces applications ont besoin de PHP8.0.x, qui doit être installé à partir du dépôt de mises à jour « core ». '''Résolution :'''utiliser la ligne de commande urpmi, ou ''' ''Enlever'' ''' les dépôts backports: utiliser la ligne de commande {{cmd|urpmi.removemedia -y Backports}} ou les outils graphiques : Lancer {{cmd|drakrpm-edit-media}} qui se trouve dans le {{prog|Centre de contrôle Mageia}} section {{menu|Gestion des logiciels -> Configurer les sources pour installer et mettre à jour des logiciels}}, sélectionner tous miroirs backport et cliquer sur le bouton « Enlever ».<br />
'''CORRECTION :''' Si vous avez déjà récupéré les versions trop récentes, vous pouvez rétrograder en désactivant (ou en supprimant) les dépôts de backports, et en effectuant la commande {{cmd|urpmi --downgrade des paquets concernés}}. Pour vérifier, vous pouvez utiliser {{cmd|urpmq --not-available}} pour lister les paquets et les versions qui ne sont pas dans les dépôts activés. ''(Il est possible que tous n’aient pas besoin d’être déclassés pour résoudre votre problème et que certains aient été installés à partir d’autres dépôts actuellement non configurés ou activés, ou d’autres moyens.)''<br />
<br />
{{Bug|30084}} – mgaapplet ne liste pas toutes les mises à jour disponibles dans Core Updates si Core Backports est activé<br />
<br />
=== Mageia Welcome ===<br />
<br />
{{bug|28328}} – Steam ne peut pas être installé en un clic avec le bouton proposé avec Mageia Welcome si les dépôts 32 bits ne sont pas être activés, comme c’est le cas par défaut. [[Mageia_8_Notes_de_version-fr#Dépôts 32 bits sur des systèmes 64 bits|Les dépôts 32 bits doivent être activés]] pour compléter l’installation.<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28806}} – L’onglet MCC de MageiaWelcome s’affiche de façon incorrecte pour les langues chinoises et japonaises.<br />
<br />
=== Connexion USB des téléphones ===<br />
<br />
'''Android, MTP:''' {{bug|28216}}. Le paquet {{pkg|libusb}} a été mis à jour pour inclure des corrections qui améliorent la connectivité des téléphones Android par USB. Vous connaissez la large variété d’appareils Android – s’il reste des problèmes essayez une autre méthode de connexion, par exemple par Wifi en utilisant {{pkg|kdeconnect-kde}} (fonctionne aussi en dehors de Plasma, et fournit bien plus que le transfert de fichiers) ou la synchronisation de fichiers sans serveur avec {{prog|Syncthing}} ou un service cloud. Plus d’informations sur notre page [[File_transfer_with_Android_devices|Transfert de fichiers avec les périphériques Android (en)]].<br />
<br />
'''iPhone :''' {{bug|28669}} Les paquets {{pkg|ifuse}} et {{pkg|usbmuxd}} ne sont pas installés par défaut. '''Correction manuelle :''' les installer.<br />
<br />
=== Logiciels divers ===<br />
<br />
{{Bug|9683}} - Les langpacks '''LibreOffice''' ne sont pas installés pour le chinois et le portugais-brésil. '''Correction manuelle :''' les installer.<br />
<br />
{{Bug|28963}} - Le paquetage '''LibreOffice''' {{pkg|libreoffice-'''emailmerge'''}} et le task package {{pkg|libreoffice}} ne sont pas installés lors de l'installation à partir des images ISO classiques. '''CORRECTION :''' installer {{pkg|libreoffice}}.<br />
<br />
{{Bug|22425}} - '''Draksnapshot''' ne se lance pas.<br />
<br />
{{Bug|27340}} – l’interface graphique de '''FreeCAD''' ne s’affiche pas. '''Correction manuelle :''' effacer {{file|~/.mozila/plugins/mozplugger0.so}} résiduel après une mise à niveau de 7 à 8.<br />
<br />
{{Bug|28097}} - Erreur de segmentation '''xviewer''', également absent du menu des applications.<br />
<br />
CORRIGÉ lors par mise à jour : {{bug|28363}} – VLC plante à l’ouverture d’un fichier MKV lorsque le codec vidéo est AV1.<br />
<br />
{{Bug|28683}} - '''OGMRip''' ne se lance pas. Le problème est de plus observé dans d'autres distributions, et les solutions en amont semblent périmées.<br />
<br />
{{Bug|28814}}, {{Bug|28840}}, {{Bug|30462}} '''Wine''' manque quelques dépendances, surtout pour les bibliothèques 32 bits. (Aussi pour '''PlayOnLinux'''.) '''Correction manuelle''' et aussi d'autres conseils [[Les_méthodes_pour_installer_des_programmes-fr#Exécution de programmes MS Windows|'''ici''']]. Voir par ailleurs {{Bug|16273}}.<br />
<br />
{{Bug|30937}} - '''Thunderbird''' conserve des fichiers temporaires s'il est configuré pour ouvrir un PDF dans un programme externe. [https://bugzilla.mozilla.org/show_bug.cgi?id=1793932 En amont]. La solution manuelle consiste à modifier le paramètre, voir les bogues associés.<br />
<br />
=== Logiciels externes ===<br />
<br />
''Aucun logiciel n’est fourni par Mageia, seuls les logiciels externes importants doivent être répertoriés ici.''<br />
<br />
{{Bug|30103}} – Problèmes vidéo avec '''Remote Desktop Tools''' ''(VNC, TeamViewer, AnyDesk, etc.)'' '''Solution de contournement :''' Tout d’abord, au moins TeamViewer et Anydesk sont incompatibles avec Wayland, par conséquent, utilisez Xorg. Les problèmes peuvent souvent être atténués en sélectionnant une résolution inférieure sur l’ordinateur hôte ou bien en désactivant les effets du bureau (dans Plasma, par exemple, appuyez sur Maj-Alt-F12), mais mieux encore : dans le fichier {{file|/etc/X11/xorg.conf}}, dans la section « Device », ajouter l’Option « LinearFramebuffer ».<br />
<br />
== Sécurité ==<br />
<br />
=== Amorçage d’un système avec des partitions chiffrées ===<br />
<br />
{{Bug|19800}} - [http://hmarco.org/bugs/CVE-2016-4484/CVE-2016-4484_cryptsetup_initrd_shell.html CVE-2016-4484] les tentatives avortées d'entrée d'un mot de passe pour les partitions LUKS aboutissent à une console.<br />
<br />
Les personnes voulant sécuriser leur système doivent :<br />
* ajouter un mot de passe du BIOS<br />
* ajouter un mot de passe à GRUB<br />
* ajouter “rd.shell=0” aux options d'amorçage du noyau<br />
<br />
=== Changement des valeurs par défaut des politiques de chiffrement du système ===<br />
<br />
Au cours du développement de Mageia 8, les valeurs par défaut en amont des politiques cryptographiques du système (qui sont fournies avec le paquet {{pkg|crypto-policies}}) ont changé.<br />
Auparavant, la valeur par défaut était LEGACY, qui autorisait les protocoles TLS 1.0 et 1.1. Les algorithmes DSA, 3DES et RC4 étaient autorisés, tandis que les clés RSA et les paramètres Diffie-Hellman sont acceptés s'ils font au moins 1023 bits.<br />
Le nouveau paramètre DEFAULT autorise les protocoles TLS 1.2 et 1.3, ainsi que les protocoles IKEv2 et SSH2. Les clés RSA et les paramètres Diffie-Hellman sont acceptés s'ils font au moins 2048 bits.<br />
<br />
Le paramètre actuel peut être vu dans {{file|/etc/crypto-policies/config}}.<br />
<br />
Il est déconseillé de remettre les politiques de cryptage par défaut du système à LEGACY. Veuillez plutôt signaler les bogues des applications qui ne fonctionnent pas en raison de ces nouvelles valeurs par défaut.<br />
<br />
Pour plus de détails, je vous invite à consulter [https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening Red Hat Enterprise Linux 8 Security hardening - Using system-wide cryptographic policies]<br />
<br />
== Divers ==<br />
<br />
=== Hibernation ===<br />
<br />
{{bug|28528}} - '''Reprendre''' à partir de l'hibernation au lieu de repartir à zéro. [https://github.com/dracutdevs/dracut/issues/924 Bogue en amont]. '''Correction manuelle''' : 1) Vérifier qu'il n’y a aucune ligne contenant "add_dracutmodules" dans la sortie {{cmd|cat /etc/dracut.conf.d/51-mageia-resume.conf}} . 2) Ajoutez la ligne manquante en exécutant {{cmd|<nowiki>echo 'add_dracutmodules+=" resume "' >> /etc/dracut.conf.d/51-mageia-resume.conf</nowiki>}} en tant que root et générez ensuite un nouvel initrd :<br />
{{cmd|dracut -fv}}.<br />
À la sortie de l'hibernation, cela doit fonctionner. Si ce n'est pas le cas, il reste un autre problème, consulter le forum.<br />
<br />
=== Réseau ===<br />
<br />
==== Téléchargement des logiciels RPMs ====<br />
<br />
Pour quelques personnes, la méthode de téléchargement par défaut échoue par intermittence. '''Une autre méthode consiste à''' démarrer {{cmd|drakrpm-edit-media}} qui est un des modules du {{prog|Centre de contrôle de Mageia}} qui se trouve dans {{menu|Gestion des logiciels -> Configurer les sources pour installer et mettre à jour des logiciels}}. Dans le menu {{menu|Options -> Options générales}} mettre « Programme de téléchargement à utiliser » sur « wget ». {{bug|24362}}<br />
<br />
Si vous l’avez déjà fait, les téléchargements qui ont échoué peuvent donner lieu à des messages tels que<br />
<br />
There was a problem during the installation:<br />
package firefox-0:91.3.0-1.mga8.x86_64 does not verify: Payload SHA256 ALT digest: BAD (Expected<br />
6ba98a0b474689bd5bbf15f361faf4116279e7c52d921ef5283db0e6f08d11c3 != 49b9a8f7b34a063e966a0133f5f84701d61ffd41ee3c595df575696a43c221bc)<br />
<br />
Si cela se produit, faites {{cmd|urpmi --clean}} et réessayez (en utilisant wget).<br />
<br />
Si cela ne résout pas le problème, il se peut que le paquet de votre miroir soit cassé, supprimez donc votre jeu de miroirs et ajoutez un nouveau jeu, nettoyez à nouveau et réessayez :<br />
<br />
Pour supprimer tous les dépôts, utilisez la ligne de commande {{cmd|urpmi.removemedia -a}} ou les outils graphiques : Démarrez {{cmd|drakrpm-edit-media}} qui est {{prog|Centre de Contrôle de Mageia}} section {{menu|Gestion des logiciels -> Configurer les sources pour installer et mettre à jour des logiciels}}, {{keypress|Ctrl}}+{{keypress|A}}+{{keypress|clic}} pour sélectionner tous les médias, et cliquez sur le bouton « Enlever ».<br />
<br />
Pour ajouter tous les dépôts Mageia d’un miroir en particulier, utilisez soit la ligne de commande - ''exemple pour un miroir en France de Mageia 8 en version 64 bits'' : {{cmd|urpmi.addmedia --distrib mirrorlist 'ftp://ftp.free.fr/mirrors/mageia.org/distrib/8/x86_64'}}, ou avec les outils graphiques : dans {{menu|Configurer les sources pour installer et mettre à jour des logiciels -> Fichier -> Ajouter un miroir de media spécifique}},<br />
<br />
=== Impression ===<br />
<br />
==== Impression dans les applications webkit gtk ====<br />
<br />
{{bug|28758}} - Un bogue en amont dans le bac à sable peut empêcher l'impression à partir d'applications webkit gtk telles que Evolution. '''Solution de contournement''', liens vers les sources et plus d'informations voir le premier post du bogue.<br />
<br />
==== Imprimante en double – ce n’est pas un bogue ====<br />
<br />
Vous pouvez voir votre imprimante affichée deux fois. En effet, toutes les imprimantes disponibles sont affichées sur le serveur CUPS local (localhost) et sur tous les serveurs CUPS connectés. Ainsi, si vous partagez une imprimante sur le réseau, ce qui est le cas par défaut, elle sera affichée en double sur l’ordinateur partagé. Ce comportement n’est pas propre à Mageia.<br />
<br />
Solution de contournement : Dites à CUPS de ne pas partager le travail de la file d’attente des imprimantes sur le réseau local si vous n’avez pas besoin de l’utiliser depuis un autre ordinateur. Allez dans {{prog|Centre de contrôle Mageia}} Section {{menu|Matériel > Configurer l’impression}} menu {{menu|Serveur -> Paramètres}}.<br />
<br />
=== Shell / Consoles ===<br />
<br />
==== « mode de collage entre crochets » affectant le copier-coller ====<br />
<br />
Par défaut, readline 8.1 a activé le mode de collage « entre crochets », qui est également actif, notamment dans le shell bash. Cela signifie que si quelque chose est collé dans votre terminal, le texte collé sera entouré de caractères d’échappement invisibles \e[200~ et \e[201~</br><br />
L’effet manifeste est que les couleurs d’arrière-plan et de premier plan sont remplacées par le texte collé, et qu’il faut également appuyer sur une touche ou cliquer avec la souris pour pouvoir exécuter le texte collé.</br><br />
Pour plus d’informations à ce sujet, voir [https://cirw.in/blog/bracketed-paste bracketed paste mode].</br><br />
</br><br />
Ceci peut être désactivé pour bash en ajoutant la ligne {{cmd|<nowiki>bind 'set enable-bracketed-paste off'</nowiki>}} au fichier {{file|~/.bashrc}}. les modifications sur le fichier {{file|~/.bashrc}} prendront effet au prochain lancement du shell bash.<br />
</br></br><br />
Il devrait également être possible de désactiver cette fonction en ajoutant le paramètre {{cmd|<nowiki>set enable-bracketed-paste off</nowiki>}} au fichier {{file|~/.inputrc}}, mais cela ne semble pas avoir d’effet.<br />
<br />
== Difficultés sur la mise à niveau ==<br />
<br />
Assurez-vous de suivre l’une des procédures indiquées dans [[Mageia_8_Notes_de_version-fr#Mise à niveau depuis Mageia 7|les notes de mise de version]]. Évitez les interférences de l’économiseur d’écran ! {{bug|25251}}<br />
<br />
=== Si la mise à niveau échoue ===<br />
<br />
Si vous ne pouvez pas démarrer votre machine dans un état fonctionnel, démarrez sur l’ISO classique et effectuez une mise à niveau. Gardez à l’esprit '''qu’il ne faut pas formater''' les partitions. C’est important : vous devez '''activer tous les dépôts de mise à jour''' qui ont été actifs lors d’une mise à jour ou d’une version précédente. Notez également que l’installation classique n’utilise pas de pilotes nonfree, vous pouvez avoir besoin d’une connexion filaire pour avoir un accès à internet. Si cela vous est impossible, essayez l’image d’installation réseau avec le micro-code non libre. Il y a davantage de pilote pour le wifi. Pour plus d’information consulter [[Mageia 8 Notes de version-fr#Supports d’installation disponibles|Supports d’installation disponibles]].<br />
<br />
Si toutes les tentatives de mise à jour échouent, la solution de repli consiste à effectuer une nouvelle installation, en conservant éventuellement le dossier {{folder|/home}}, dans ce cas (NE PAS LE FORMATER).<br />
<br />
=== Aucune mise à niveau proposée par l’applette ===<br />
<br />
''' '' Nouveau : activée au 4 avril 2021 '' '''<br />
<br />
L’applette dans la boîte à miniatures qui vous informe des mises à jour doit aussi vous prévenir de la disponibilité d’une mise à niveau vers la nouvelle version.<br />
<br />
Comme toujours, nous retardons l'activation de ce message afin de résoudre les problèmes rencontrés par les premiers outils d'installation et de mise à niveau. Soyez patient ou mettez à jour selon les [[Mageia_8_Notes_de_version-fr#Mise à niveau depuis Mageia 7|méthodes décrites dans les notes de mise à jour]].<br />
<br />
=== Mise à niveau à l’aide de DNF ===<br />
<br />
'''Une version supplémentaire du noyau a été installée.''' – DNF utilise une méthode différente de celle de l’outil d’installation Mageia pour sélectionner la version du noyau. Cela peut avoir pour conséquence qu’un système qui utilisait un kernel desktop, après la mise à niveau ait à la fois des kernels desktop et server installés, et le kernel server est utilisé. Pour corriger cela, sélectionner au démarrage le kernel desktop, puis désinstaller le kernel server {{bug|28272}}.<br />
<br />
=== Abandon de PHP7 ===<br />
<br />
Mageia 8 est dépourvu de PHP7. Cela peut poser une difficulté si vous avez un logiciel qui est incompatible avec PHP8.<br />
<br />
Exemple<br />
<br />
* [[Mageia_8_Notes_de_version-fr#Nextcloud|'''Nextcloud''' sera disponible dans le backport]].<br />
* '''CORRIGÉ''' avec la mise à jour de Mageia 8 : {{bug|28533}} Le client de messagerie Roundcube est maintenant compatible avec PHP8.<br />
'''Solution de contournement''' : Vous pouvez compiler PHP7 vous-même, en consultant [https://forums.mageia.org/en/viewtopic.php?f=7&t=14038#p82334 notre forum].<br />
<br />
=== Paquetages retirés de la distribution ===<br />
<br />
Consulter [[Mageia 8 Notes de version-fr#Paquetages retirés de la distribution|à la fin des notes de version]].<br />
<br />
==== VirtualBox ====<br />
<br />
[[Mageia_8_Release_Notes#VirtualBox|Il n’y a plus d’hôte]] VirtualBox 32 bits.<br />
<br />
=== Paquets Inutilisés ===<br />
<br />
Après la mise à niveau, vous pouvez constater que beaucoup de paquets installés sont inutilisés. ''(Signalés comme orphelins, ou vous êtes incapables de savoir directement ce pour quoi ils sont installés.)''<br />
<br />
Soyez prudent – '''ils peuvent en fait être nécessaires :'''<br />
<br />
Il se peut que la personne ait un logiciel tiers qui nécessite les modules de ces paquets lib ou d’anciens paquets qui ne sont pas des paquets lib. Le logiciel tiers peut être compilé à partir des sources ou des fichiers binaires copiés manuellement – non installés par rpm, donc le gestionnaire de paquets ne le sait pas. De plus, si vous alternez entre l’utilisation de DNF et d’urpmi, le [[Utilisation_de_DNF-fr#Vigilance_sur_la_gestion_relative_aux_orphelins|traitement des orphelins ne fonctionne pas]] pour l’un ou l’autre.<br />
<br />
Tant que les anciens paquets n’interfèrent pas avec les nouveaux, nous avons choisi de laisser les personnes choisir les anciens paquets dont elles n’ont pas besoin et de les désinstaller manuellement si elles le souhaitent. (Si vous le faites, veuillez conserver une trace de ce que vous désinstallez).<br />
<br />
Vous verrez également que le dispositif de mise à jour n’a pas seulement laissé les anciens paquets en place, mais a également installé les versions Mageia correspondantes – voyez cela comme un service.<br />
<br />
''Même lors d’une nouvelle installation, il y aura plusieurs versions ou alternatives de certains paquets installés comme étant suggérés par différents paquets. Ces paquets ne sont pas obligatoires, mais seulement suggérés ou recommandés, et sont donc orphelins dès leur installation.''<br />
<br />
Pour plus d’informations voir [[Supprimer des paquets-fr|Supprimer des paquets]].<br />
<br />
=== Difficultés diverses sur la mise à niveau ===<br />
<br />
{{bug|29182}} '''La mise à jour depuis Wayland au moyen de l'applet mgaonline''' / mgaapplet-upgrade-helper ne fonctionne pas. '''Une des solutions''' est de se Déconnecter et se connectez en utilisant Xorg. Ou utilisez une autre méthode de [[Mageia_8_Notes_de_version-fr#Mise à niveau depuis Mageia 7|mise à niveau]].<br />
<br />
'''Optimus / Mageia Prime''' peut nécessiter l’exécution de mageia-prime-uninstall suivi de mageia-prime-install. Voir [https://bugs.mageia.org/show_bug.cgi?id=24967#c45 ce commentaire sur le bogue] et notre page wiki [[Mageia-prime pour Optimus-fr|Mageia Prime]].<br />
<br />
{{bug|27880}} – '''Serveur x2 Go'''. Pour l’instant, '''Correction manuelle''' dans {{bug|27880#c9}}<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28007}} – llvm-11.0 Les paquets mga8 entrent en conflit avec les paquets mga7 llvm-devel lors de la mise à jour de MGA7 en MGA8<br />
<br />
{{bug|28018}} – ''Google Earth Pro'' – Voir notre page wiki [[Google_Earth|Google Earth]] pour savoir comment l’installer pour Mageia 8 (et Cauldron).<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28352}} – '''KiCAD''' ne parvient pas à activer l’accélération Matérielle. ''Et si vous avez besoin de la branche 6.x, essayez [[flatpak-fr|Flatpak]].''<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{Bug|28419}} – Imprimante virtuelle '''Boomaga''' : La version mga7 reste installée après la mise à niveau – avec le nouveau paquet mga8. '''Correction manuelle''' : Désinstallez le paquet mga7. S’il refuse de se désinstaller : en tant que root {{cmd|rpm -e --noscripts boomaga-3.0.0-1.mga7}} – ou laissez-le – il fonctionne de toute façon avec les deux installés… '' ''Si'' vous constatez que l’imprimante Boomaga a '''disparu''' de vos choix d’imprimantes, configurez-la de nouveau dans '' {{prog|Centre de contrôle Mageia}} {{menu|Matériel -> Configurer l’impression…}}. Sachez que si vous laissez installer le paquet Boomaga dans les deux versions mga7 et mga8, vous aurez le même problème avec les futures mises à jour de Boomaga et les mises à niveau de Mageia.<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28479}} – conflits entre le paquet '''batik''' et la mise à niveau de Mageia 7 à 8<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28481}} – npm a une version plus élevée sur Mageia 7 que sur Mageia 8, ce qui entraîne des problèmes de mise à niveau.<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28485}} – mythtv: la mise à niveau de MGA7-> MGA8 échoue sur des conflits de fichiers.<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28503}} – '''php-json''' provient de Mageia 7 et casse PHP dans Mageia 8 – php-json est maintenant inclus, il n’y a plus d’extension. CORRECTION : Supprimez le php-json persistant. La mise à jour arrive pour faire cela automatiquement.<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28522}} - Les conflits de fichiers avec '''opencv-devel''' provoquent des erreurs en cascade lors de la mise à niveau de Mageia 7 vers Mageia 8<br />
<br />
{{bug|28550}} – Si l’UID est 500, la variable $PATH ne contient pas {{folder|/usr/games}}, par conséquent ''les jeux sont impossibles à lancer. ''Cela affecte les versions 6 ou précédentes de Mageia initialement installées et mises à jour depuis, ou un système configuré manuellement avec un '''UID < 1000'''. Il est difficile d’y remédier de manière sûre dans tous les cas. Consultez le bogue pour connaître la '''solution''' et demandez sur notre forum si vous avez besoin d’aide.<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28636}} – '''python3-gdal'''3.1.3-7.mga8 entre en conflit avec un fichier du paquet lib(64)gdal-devel-2.4.3-1.1.mga7<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia 8 {{bug|28679}} – La mise à niveau de Mageia 7 vers Mageia 8 (DNF/CLI) échoue sur le paquet '''CairoSVG''' de Mageia 8 qui entre en conflit avec le paquet cairosvg de Mageia 7.<br />
<br />
{{bug|28724}} – '''Mise à niveau de mgaapplet :''' : demande où télécharger d’abord tous les paquets, mais ne respecte ni '''l’emplacement du téléchargement''' ni « la priorité ». <br />
<br />
CORRIGÉ avec la mise à jour de Mageia 8 {{bug|28743}} – L’aide de '''LibreOffice''' ne fonctionne pas.<br />
<br />
{{bug|28914}} – Il manque certains '''plugins Gimp''', qui étaient présents dans Mageia 7.<br />
<br />
==== Samba ====<br />
<br />
'''CORRIGÉ''' avec la mise à jour de Mageia '''7''' {{bug|28042}} – Lors de la mise à niveau vers MGA8 : ERROR : 'script' failed for '''samba-client'''-4.10.18-1.1mga7.x86_64. Dans la plupart des cas, vous pouvez '''négliger''' ce message d’erreur.</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=QA_ISO_testers&diff=55391QA ISO testers2022-09-28T19:54:06Z<p>Dtux: Jean-philippe Squelbut est décédé.</p>
<hr />
<div>[[Category:QA]]<br />
<br />
<br />
'''Please only add your details below if you intend to [[Pre-release_ISO_testing|test development snapshots, stabilisation shaphots, RC pre-release ISOs]] as part of the QA team or as active BugSquad member. You need to also subscribe to the [https://ml.mageia.org/l/info/qa-discuss qa-discuss mailing list] if you haven't done so already. It's a good idea to post a message to qa-discuss when you add your name to this list, so the change is noticed.'''<br />
<br />
=Read this before you add yourself to the list=<br />
<br />
<br />
This page is here to help us to keep in touch with you. Sorry for the list of rules but we do have to restrict access to the server.<br />
<br />
<br />
This is a necessary step as pre-release ISOs are not held on a public server, so somebody will need this information to contact you directly with further instructions and download details. Notification of pre-release ISO availability and discussion takes place on qa-discuss.<br />
<br />
<br />
The server is a development server with limited bandwidth, so please do not share the details you will be given with anybody else. Please ensure that you do not inadvertently use them in any public emails, such as those to the mailing list or on any open IRC channel or forum. <br />
<br />
<br />
It is also a good idea, but not mandatory, to leave information about the hardware you use in the [[QA_iso_hardware_list|QA hardware list]]. Please keep this information up-to-date if you choose to do so.<br />
<br />
= The list =<br />
<br />
IRC/Forums nick - Name - email address<br />
<br />
'''Please do not wipe the ones in the first three lists, unless they resigned:'''<br/><br/><br />
<br />
=='''QA-team, Bugsquad and Packaging-team leaders/council representatives:'''==<br />
* MrsB - Claire Robinson - eeeemail at gmail dot com<br />
* davidwhodgins - Dave Hodgins - davidwhodgins at gmail dot com<br />
* lewyssmith - Lewis - lewyssmith at laposte dot net<br />
* wilcal - Bill Kenney - wilcal dot int at gmail dot com<br />
* stormi - Samuel Verschelde - stormi at laposte dot net<br />
* marja - Marja van Waes - marja11 at xs4all dot nl<br />
* akien - Rémi Verschelde - rverschelde@gmail.com<br />
* MageiaTJ - Thomas J Andrews - andrewsfarm at gmail dot com<br/><br/><br />
<br />
=='''Desktop environment maintainers:'''==<br />
* KDE - neoclust - Nicolas Lécureuil - neoclust at mageia dot org<br />
* KDE - daviddavid - David Geiger - geiger.david68210 at gmail dot com<br />
* Gnome - ovitters - Olav Vitters - olav at vitters dot nl<br />
* XFCE - wally_ - Jani Välimaa - wally at mageia dot org <br />
* Cinnamon - jquant - Joseph Wang - joequant at gmail dot com<br />
<!-- * Mate - tarakbumba - Atilla ÖNTAŞ - tarakbumba at gmail dot com - TO BE REPLACED. Removed from cc list --><br />
* LXDE - ns80 - Nicolas Salguero - nicolas dot salguero at laposte dot net<br/><br/><br />
<br />
=='''Important iso bug squashers:'''==<br />
* coling - Colin Guthrie - mageia at colin dot guthr dot ie<br />
* tv - Thierry Vignaud - thierry dot vignaud at gmail dot com <br />
* martinw - Martin Whitaker - mageia at martin-whitaker dot me dot uk <br />
* barjac - Barry Jackson zen25000 (at) zen (dot) co (dot) uk<br />
<br/><br/><br />
<br />
=='''All other active iso-testers:'''==<br />
Adding a separate list for BugSquad iso-testers, because BugSquad needs its members so very badly that avoiding the slightest impression that they're a member of QA team seems needed.<br><br />
--[[User:Marja|marja]] 06:30, 9 February 2016 (UTC)<br />
<br />
==='''For BugSquad:'''===<br />
*Chromo - Nic Baxter - nic at nicbaxter dot com dot au<br />
*auroud_85 - Aurélien Oudelet - ouaurelien at gmail dot com<br />
<br />
==='''For Qa team:'''===<br />
Additional testers, please add your id to the end of this list in the format IRC nick, Name, email address. For example<br />
* davidwhodgins - Dave Hodgins -davidwhodgins at gmail dot com<br />
<br />
* benmc - Ben McMonagle - westel at xtra dot co dot nz<br />
<br />
* bri_an - Brian Rockwell - brtians1 at gmail dot com<br />
<br />
* eslrahc - Charles A Edwards - cae at eslrahc dot com - Mail delivery failed NXDOMAIN<br />
<br />
* linuxero - Muhammad Tailounie - mageia at mtailounie dot net<br />
<br />
* stroibe974 - Sébastien Morin - sebsweb at gmail dot com<br />
<br />
* daviddavid - David Geiger - geiger.david68210 at gmail dot com<br />
<br />
* krisNL - Chris - shybluenight at gmail dot com<br />
<br />
*hviaene - Herman Viaene - herman dot viaene at edpnet dot be<br />
<br />
* lebarhon - André Desmottes - lebarhon at free dot fr<br />
<br />
* tarazed - Len Lawrence - tarazed25 at gmail dot com<br />
<br />
* rindolf - Shlomi Fish - shlomif at shlomifish dot org<br />
<br />
* justchris57 - Chris Ammerlaan - justchris57 at gmail dot com<br />
<br />
* schultz - Donald Stewart - watersnowrock at gmail dot com<br />
<br />
* dtux - Daniel Tartavel - contact at librepc dot com<br />
<br />
* neoser10 - Mauricio Andres Bustamante Viveros - neoser10 at hotmail dot com<br />
<br />
* mab33 - Maurice Batey - maurice at bcs dot org dot uk<br />
<br />
* wikigazer - Paul Blackburn - paul dot blackburn at gmail dot com<br />
<br />
* leuhmanu - Manuel Hiebel - leuhmanu at mageia dot org<br />
<br />
* bittwister - Bit Twister - bittwister2 at gmail dot com<br />
<br />
* Bequimao - Ulrich Beckmann - bequimao dot de at googlemail dot com<br />
<br />
* wintpe - Peter Winterflood - peter dot winterflood at ossi dot co dot uk<br />
<br />
* ZekeMX - Ezequiel Partida - ezequiel dot partida at gmail dot com<br />
<br />
* jagodyn - Jacob Godyn - jagodyn at laposte dot net<br />
<br />
* Aussie_matt - Xboxboy - xboxboy dot mageia at gmail dot com<br />
<br />
* tonyb - Tony Blackwell - tablackwell at bigpond dot com<br />
<br />
* ghibo - Giuseppe Ghibò - ghibo at mageia dot org<br />
<br />
* joselp - Jose Manuel López - joselp at disroot dot org<br />
<br />
* pclx - PC LX - mageia at pmc dot com dot pt<br />
<br />
* Morgano - Morgan Leijström - fri at tribun dot eu<br />
<br />
* kensor - Kenneth Marcy - kmmos1 at frontier dot com<br />
<br />
* jybz - Jean-Baptiste - j.biernacki+mga at free dot fr</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Commercial_vendors&diff=52592Commercial vendors2021-10-25T14:17:27Z<p>Dtux: deleted Librepc because it is closed</p>
<hr />
<div>{{multi language banner|[[Commercial_vendors|English]] ; [[Commercial_vendors_pl|Polski]] ; [[Área_Comercial_pt-PT|Português (Portugal)]]}}<br />
<br />
<br />
For-profit organizations are part of the Mageia ecosystem. The following companies provide commercial services with or around Mageia software, tools or project.<br />
<br />
Note that Mageia.Org does not represent, validate, or endorse these organizations - this space is provided mainly as a reference - and may be redesigned or reindexed later at the [[Org_Board|Board]]'s discretion.<br />
<br />
== Consulting, training, development services ==<br />
<br />
=== France ===<br />
<br />
* '''hupstream''' - http://hupstream.com - We help businesses and people make the most out of Open Source: kernel expertise, packaging, build system, all base system components. We help our client to industrialise their use of Open Source. We are also part of some Open Source projects like Mageia, kernel, debian, ... We provide support on many distributions including Mageia.<br />
<br />
* '''Open Source Software Assurance''' - https://www.linagora.com/ - From Open Source Leader company ! Our mission : bug hunting, support, assistance and Open Source lifecycle management from Open Source experts !<br />
<br />
* '''SIVEO''' - http://www.siveo.net/ - SIVEO is an infrastructure automation software company; it is a young company creates innovative in November 2008. First French company labelled in the INTEL CLOUD Builder initiative for its eVA solution, SIVEO works with publishers, SSII, public and private accounts. [https://blog.mageia.org/en/2015/11/17/siveo-joins-mageia/ SIVEO joins Mageia <!--is first official sponsor of the Mageia project (To be discussed, this is ambiguous - Stormi). (Commenting that part out for now, to avoid that companies feel offended who have donated in whichever way to Mageia and were earlier in time to do that marja, 2016-04-21)-->] [https://twitter.com/eVPlanet Follow us on twitter.]<br />
<br />
=== USA ===<br />
<br />
* '''Remy Services, LLC''' - https://community.spiceworks.com/service-providers/975-remy-services-llc - We offer remote and onsite computer maintenance and repair to help you with all your computer needs. Everything from virus or malware removal, data recovery, network installations, hardware installation, laptop repairs and general cleanup. Our recent work: Mageia Package QA Testing.<br />
<br />
<!--- * '''Name''' - url or contact - City, Country<br />
presentation in 3/4 sentences: services provided, context, locales/countries managed --><br />
<br />
== Hosting ==<br />
* '''GigaTux''' - http://www.gigatux.com/distro/mageia_vps Gigatux supports the latest Mageia stable version on demand<br />
<br />
<!--- * '''Name''' - url, city --><br />
<br />
== Hardware vendors ==<br />
=== United Kingdom ===<br />
* '''Ministry of Freedom''' - https://minifree.org/ (website in English) - Essex - Selling laptop, desktop and server computers with Mageia preinstalled, along with a free/opensource BIOS called [https://libreboot.org/ Libreboot]<br />
<br />
=== Belgium ===<br />
* '''PC-Fixer.be''' - http://www.pc-fixer.be/ (website in French) - Brussels - Selling laptop and desktop computers with Mageia preinstalled<br />
<br />
=== Germany ===<br />
* '''ixsoft''' - https://www.ixsoft.de/ (website in german) - Schorfheide / Altenhof - Selling laptop and desktop computers with (selectable) Mageia preinstalled<br />
<br />
<!--- * '''Name''' - url, city - type of hardware --><br />
<br />
== Software vendors ==<br />
Other than what is already provided in the distribution.<br />
<br />
=== UK ===<br />
* '''BuyLinuxCDs''' - http://www.buylinuxcds.co.uk/buy-linux-cds-in-the-uk.html - DVD<br />
<br />
=== Germany ===<br />
* '''ixsoft''' - http://ixsoft.de/cgi-bin/web_store.cgi?ref=Catalogs/de/mageia-catalog.html DVD<br />
<br />
<!--- * '''Name''' - url - software products --><br />
<br />
<!--- * '''Name''' - url - goodies --><br />
<br />
== Notes ==<br />
<br />
* '''Be aware that this list may be out of date,''' in which case the representative of the mentioned company should advise or update the page with a clear and self-explanatory comment. Contact our Board or Council if you do not represent the involved company (see below).<br />
* If your company provides services or products with or around Mageia software, for individuals or professionals, feel free to add yourself in this list, in the right country, in alphabetical order.<br />
* If you think a company should not be listed here or think its description is no longer correct, but you are '''not its representative''', do '''not remove or change '''its entry, but please contact our Board and Council, see [[Contacts]], and explain your reasons.<br />
<br />
[[Category:Users]][[Category:commercial]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Events_Box&diff=52447Events Box2021-09-17T15:30:57Z<p>Dtux: </p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Marcom]]<br />
[[Category:Atelier]]<br />
[[Category:Events]]<br />
<br />
We need a first, small, limited events box to help keep together tools for each event.<br />
<br />
See the [[Events HowTo]] as well.<br />
<br />
== How does the box look like? ==<br />
TODO, picture<br />
<br />
== What's in the box? ==<br />
Box contents can be donated, directly, or through http://www.mageia.org/donate/.<br />
<br />
* contents checklist including inventory (for CDs/stickers/goodies) and state of tablecloths (washed/not washed).<br />
* cash box<br />
* a pen and a notebook<br />
<br />
Showcase:<br />
* big posters with Mageia logo - we have some<br />
* kakemono - we have one (and can get extra banners if wanted); posters fit in kakemono case<br />
<br />
Distribute:<br />
* CD, DVD - we have some discs left for Mageia 1, we need a solution for Mageia 2<br />
<br />
Goodies:<br />
* tshirts - we have some left from FOSDEM 2011 - we need an inventory and new series<br />
* stationery (stickers, contact list, flyers, contact cards/business cards, blank pre-printed CDs (to burn on the stand), CD sleeves) - we have some left - we need new ones - for booth and to distribute to attendees when one speaks at a conference<br />
<br />
== Where is the box? ==<br />
<br />
=== Current location of the box ===<br />
<br />
=== Current goodies around Europe ===<br />
<br />
{| style="color:black; cellpadding="5%" cellpadding="5%" cellspacing="0" border="1"<br />
|Country <br />
|city <br />
|Tshirts <br />
|stickers <br />
|flyers <br />
|USB Keys <br />
|pens <br />
|Tablecloth <br />
|kakemono <br />
|others <br />
|-<br />
|France <br />
|Lyon <br />
|16 x S 25 x M <br />
23 x L <br />
XL x 1 <br />
XXL x 3 <br />
ladies - S x 5 - M x 13 - L x 5 - 3 x XL <br />
|<br />
|<br />
|18 USB key <br />
|66 Pens <br />
|1 tablecloth <br />
|1 kakemono <br />
|}<br />
<br />
=== Next, planned locations ===<br />
* Campus du Libre - 6 november 2021 - Lyon France<br />
* Opensource Experience - 9-10 november 2021 - Paris France - https://www.opensource-experience.com<br />
<br />
=== Base locations ===<br />
Ideally, two locations, in France or in its direct periphery. Events that we will attend with this box are among: FOSDEM, LinuxTag, Solutions Linux, RMLL, OWF, JDLL, ORR, what others in Europe?<br />
<br />
=== Transportation costs ===<br />
Use these max limits to estimate roughly the cost:<br />
* weight: 10 kg<br />
* dimensions: 55 x 35 x 25 cm<br />
* declared value: 3000 €<br />
<br />
* cities: Paris, Marseille, Bordeaux, Nantes, Berlin, Bruxelles, London, Barcelona, Madrid, Rome, Lisbon<br />
Indicative average max prices (UPS - https://wwwapps.ups.com/ctc/request):<br />
* Paris -> {Brussel,Berlin}, ~300 €<br />
* Nantes -> Paris, ~100 € (about the same intra France?)<br />
<br />
* 10kg 120 x 60 x 60 cm 6,90€ (intra Germany), 22,00€ Germany->France (http://www.dhl.de/en.html)<br />
<br />
The actual cost may be less (the box may be lighter, smaller) or more (change in transportation fees).<br />
<br />
=== Asking for the box ===<br />
Wanted home candidates (multiple is better):<br />
* Nantes, FR: rda<br />
* Paris, FR: baud (Versailles, for SL, RMLL, PremierSamedi])<br />
* Berlin, DE: ?<br />
* Brussel, BE: ?<br />
* Lyon<br />
* other?<br />
<br />
== Grow the box! ==<br />
<br />
Here are other stuff good to have in the box.<br />
<br />
The whole package (box + contents) must not exceed 10 kg and must keep 55 x 35 x 25 cm (easier for someone to travel with it).<br />
<br />
* BOX itself (wish, no model/size decided) a box to fit all this, that can be handled by a single person, that has wheels and handles. Suggest medium (20kg, international roll-on size or a little larger) suitcase with at least one zipper poclet on the outside (for padlock &c during shipping).<br />
<br />
* (wish) event schedule and [[Events HowTo|howto]] (in this very wiki at least; a print copy is good too)<br />
* (wish) two large pieces of cloth: one white, one black. (see tablecloths in showcase. Black may be redundant...)<br />
* (wish) cables? RJ45, video, USB, multi powerplugs, type <br />
* (wish) small medikit, scissors, thread<br />
* (wish) velcro dots (both hook and fuzz), with adhesive back, two types (standard and strong)<br />
* (wish) good-quality packaging tape in tape-gun<br />
* (wish) good brass padlock to lock suitcase when travelling with someone<br />
* (wish) cycle lock (click-together type with coated cable or chain) to lock Events Box to racks on trains - prevent theft of Box<br />
<br />
Showcase stuff:<br />
* (must have) - 2 tablecloths for exhibition tables, white with mageia logo placed to be at front of table, sized for 2 180cm long x 90cm wide x 80cm high tables (so, (2*180)+(2*80) long and 90+(2*80) wide.) Mageia logo can be on vinyl like banner and poster, and be fixed with double-sided tape or velcro, or can be printed onto the cloth.<br />
* (wish) perspex or portable/foldable metal display stands for leaflets/brochures/cds. Metal will stand on floor beside tables, perspex on table (so metal might work better).<br />
* (wish, no model decided, price tag max 300 €) dedicated projector<br />
* (wish, no model decided, price tag max 200 € each) 2 dedicated laptops or small boxes (cubox, other?): one for projection, the other one for direct manipulation<br />
** one potential candidate, white ASRock Ion330 + keyboard + mouse and cables (second hand, ~150 € worth, rda)<br />
* for projection:<br />
** (wish) simple slides calling for contributors, with specific & easy tasks,<br />
** (wish) project presentation, demonstrating the product,<br />
** (wish) give immediate contact hooks (Web, IRC, Twitter, other events)<br />
** (wish) display a small twitter wall of the current event<br />
<br />
Distribute:<br />
* (wish) a system to dump a Mageia system image to USB key or portable HD<br />
* (wish) mageia-logo USB sticks<br />
* (idea) one of the computer is used either as a Wi-Fi access point (advertised as "Get Mageia") or as a station in the local network, and advertises shared directories (FTP, Samba) containing Mageia ISOs<br />
<br />
<br />
* interactive, live access to forums, IRC channels and other info source about the project<br />
** Maybe a projector connected to a laptop? Maybe more than one? Forums, wiki, an event-central IRC channel? I think a projector displaying a live feed of #mageia-social would be a good place to start. --[[User:Max|max]] 19:56, 16 July 2012 (UTC)<br />
* computers/projectors showcasing the OS: laptops, tablets, projectors<br />
<br />
<br />
== Other projects events boxes ==<br />
* http://live.gnome.org/GnomeEventsBox<br />
* other ?<br />
<br />
== Other ideas of goodies ==<br />
* USB key <br />
** 4 GB should be enough, ~5 € and could be proposed at 10 € with Mageia logo<br />
** http://www.memoriasusb.com<br />
* USB card<br />
** was here at Fosdem 2013, not seen since :/ 2 GB card with Mageia logo<br />
* stickers<br />
** see https://wiki.mageia.org/en/Commercial_vendors#Goodies_vendors<br />
<br />
== Documents to promote Mageia ==<br />
<br />
<br />
* stickers (meta-key, powered by, GNU/Linux Mageia logo) : http://download.tuxfamily.org/cauldron/mageia/logo/<br />
* prez : http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7A.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/FOSDEM%202014%20Flyer.odt french and english versions<br />
* http://www.mageia.org/about/media/ mainly logo & CD/DVD covers, available in SVG<br />
* FOSDEM 2015 flyer: [[File:Mageia_flyer_2015_EN.odt]]<br />
* http://stormi.lautre.net/fichiers/jdll/2015/ french and english version showed at JDLL 2015</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Mageia_8_Errata-fr&diff=51052Mageia 8 Errata-fr2021-03-18T14:38:54Z<p>Dtux: some correction on typo</p>
<hr />
<div>[[Category:Erratas]]<br />
[[Category:Mageia 8]]<br />
<br />
{{Bandeau multi-langues-fr|[[Mageia_8_Errata-de|Deutsch]] ; [[Mageia_8_Errata|English]] ; [[Erratas de Mageia 8|Español]] ; [[Mageia_8_Errata-fr|Français]] ; [[Mageia_8_Erratas do Mageia|Português (Portugal)]] ;}}<br />
<br />
== Notes ==<br />
<br />
Cette page est un complément des [[Mageia 8 Notes de version-fr|Notes de version]].<br />
<br />
<!--'''Cette page reflète actuellement la sortie de RC.''' Elle sera révisée pour toute nouvelle RC, et pour les ISO définitives.--><br />
'''Les rubriques ci-dessous précédées de « CORRIGÉ », ont une mise à jour disponible.'''<br />
Donc si vous rencontrez un problème marqué comme résolu, essayez de faire une mise à jour complète. Certains problèmes peuvent nécessiter une déconnexion/login ou un redémarrage. D’autres sont des problèmes d’installation ou de mise à niveau. Notze que la publication d'une mise à jour peut demander 24H pour être disponible sur [http://mirrors.mageia.org/status votre mirroir].<br />
<br />
Seuls les problèmes importants concernant les paquets contenus dans les ISO sont énumérés ici. Nous avons beaucoup de logiciels supplémentaires dans les dépôts.<br />
<br />
Un problème non répertorié que vous voyez peut-être résolu si vous faites une mise à jour complète.<br />
<br />
Voir également les sections des Notes de versions [[Mageia_8_Notes_de_version-fr#Problèmes connus|Problèmes connus]] et [[Mageia_8_Notes_de_version-fr#Signaler un bogue|Rapport de bogue]].<br />
<br />
Attention, nous ajouterons les problèmes provenant de l’outil de suivi des bogues, à savoir<!--[https://bugs.mageia.org/buglist.cgi?keywords=8rc1 rc1], [https://bugs.mageia.org/buglist.cgi?keywords=8rc2 rc2]-->, [https://bugs.mageia.org/buglist.cgi?keywords=FOR_ERRATA8 Pour ERRATA 8], [https://bugs.mageia.org/buglist.cgi?keywords=FOR_RELEASENOTES8 Pour les notes de versions 8] au fur et à mesure qu’ils seront signalés.<br />
<br />
== Démarrage ==<br />
<br />
== Images autonomes ==<br />
<br />
== Images d’installation ==<br />
<br />
=== Plantage à la fin de l’installation ===<br />
<br />
{{bug|27838}} Certains ordinateurs ont des firmwares bogués, ce qui fait que les écritures sur la NVRAM EFI échouent à la fin de l’installation de Mageia.<br />
<br />
Solution de contournement : Lors de la configuration du chargeur de démarrage à la fin de l’installation : Selectionner rEFInd à la place de GRUB, cocher « Install in /EFI/BOOT », décocher l’option de stockage dans la NVRAM ''(Nouveau pour Mageia 8)''<br />
<br />
=== Installateur réseau ===<br />
<br />
* Sur certaines machines UEFI, l’ISO d’Installation Réseau démarre avec un '''message d’erreur Grub''' :<br><br />
''error: ../../grub-core/video/readers/png.c:595 invalid filter value''<br><br />
Et affiche le menu Grub2 en mode texte au lieu du mode graphique.<br />
Le fonctionnement n’est pas affecté ; il s’agit simplement d’une bizarrerie esthétique. {{bug|28225}}<br />
* Si la source de l’installation de Mageia se trouve sur un périphérique USB formaté avec le système de fichiers '''exFAT''', vous devrez peut-être débrancher et rebrancher le périphérique USB pour avoir accès à la partition. [https://bugs.mageia.org/show_bug.cgi?id=28371#c23 Comment#23 dans mga#28371]<br />
<br />
=== L’image d’installation 32 bits doit être sur DVD pour fonctionner comme dépôt. ===<br />
<br />
Après l’installation du système, les ISOs de l’installation classique peuvent être utilisés comme dépôt, pour installer des logiciels sans utiliser de connexion Internet.<br />
<br />
L’ISO 64 bits fonctionne comme dépôt à la fois sur DVD et sur clé USB. Les ISO 32 bits fonctionnent uniquement comme dépôt à partir d’un DVD.<br />
<br />
== Graphiques ==<br />
<br />
=== AMD/ATI ===<br />
<br />
CORRIGÉ (?){{bug|28154}} – Les médias autonomes ne démarrent pas avec certains GPU Radeon HD ou avec un système installé avec l’ISO classique.<br />
<br />
Des corrections sont en cours. Veuillez vous assurer que toutes les mises à jour disponibles sont installées avant de signaler les problèmes rencontrés.<br />
<br />
Pour les cartes graphiques AMD de la famille Southern Islands (Tahiti, Pitcairn, Oland, Verde, Hainan) et Sea Islands (Kaveri, Bonaire, Hawaii, Kabini, Mullins), nous utilisons par défaut le nouveau pilote amdgpu au lieu de l’ancien pilote radeon, et nous voulons savoir s’il fonctionne ou non correctement sur votre matériel.<br />
<br />
Si cela ne fonctionne pas, vous pouvez vous revenir à l’ancien pilote en ajoutant ce qui suit [[Comment_ajouter_des_options_au_noyau-fr#Avec le chargeur de boot Grub 2|en ligne de commande au noyau]] :<br />
<br />
Pour les cartes Southern Island :<br />
radeon.si_support=1 amdgpu.si_support=0<br />
<br />
Pour les cartes Sea Islands :<br />
radeon.cik_support=1 amdgpu.cik_support=0<br />
<br />
=== Nvidia ===<br />
<br />
Nvidia a négligé de régler les problèmes de sécurité de son pilote de la série 340, nous avons donc dû le retirer des dépôts officiels. Voir les [[Mageia 8 Notes de version-fr#Pilote propriétaire NVIDIA|Notes de version]].<br />
<br />
== Environnements de bureaux ==<br />
<br />
{{Bug|23929}} - Le répertoire « Desktop » sous $HOME n’a pas été traduit lors de l'installation de '''Plasma ou MATE uniquement'''.<br />
<br />
{{Bug|28378}} - '''SDDM greeter''' ne se souvient pas de la session précédemment exécutée. - '''correction manuelle''': Dans {{file|/etc/sddm.conf}} dans la ligne {{cmd|<nowiki>RememberLastSession=false</nowiki>}} changez false en true. Ceci fera l'objet d'une mise à jour. Cette mise à jour définit également le paramètre {{cmd|<nowiki>RememberLastUser=false</nowiki>}}, vous pouvez le définir comme true si vous souhaitez que le dernier utilisateur soit présélectionné lors de la connexion.<br />
<br />
=== Plasma ===<br />
<br />
La session '''Wayland''' avec les pilotes nonfree 455 (actuels) de Nvidia est disponible en s’assurant que « nokmsboot » est supprimé et que « nouveau.modeset=0 » est passé à la ligne de commande du noyau. {{bug|27296}} – La session Plasma Wayland est cassée, et {{bug|28365}} – Le centre de contrôle ne démarre pas avec Plasma Wayland (correction temporaire : en tant qu’utilisateur normal, premier problème {{cmd|xhost +si:localuser:root}}) <br />
<br />
Les effets de bureau '''Compiz''' ne sont plus compatibles avec Plasma. Si vous l’utilisez avec Plasma sur Mageia 7, désactivez-le dans {{prog|Centre de contrôle Mageia}} {{menu|Matériel -> Configurez les effets bureau 3D}} – '''avant''' de mettre à niveau, et si vous voulez que Compiz cesse d’être disponible pour un autre environnement de bureau, désinstallez-le. Après l’installation ou la mise à niveau de Mageia, vous trouverez les effets de bureau dans {{menu|Configuration du système}} (icône de la barre des tâches) -> {{menu|Espace de travail}} -> {{menu|Comportement de l’espace de travail}} -> {{menu|Effets de bureau}}.<br />
<br />
L’extension clic droit ''kde-rootactions-servicemenu'' de '''Dolphin''' est supprimée, car elle est délaissée en amont et présente des problèmes.<br />
<br />
{{bug|27147}} – Connexions successives multi-utilisateurs, plasmashell ne se connecte plus à n’importe quel utilisateur après s’être éteint.<br />
<br />
{{bug|27183}} – Les réglages par défaut de l’intégration de spectacle de Mageia manquent dans configuration du système de plasma – ''Dans certains cas, après la mise à niveau.'' CORRECTION : Lancer Spectacle, sélectionner le bouton {{menu|Configurer -> Raccourcis -> Lancer Spectacle}}. Changer le paramètre de « Personnalisé » vers « Par défaut » (Imprimer), et confirmer la demande de réassignation dans la fenêtre qui s’affiche. <br />
<br />
{{bug|27362}} – startplasma-x11 engendre un processus zombie « (peut le rendre léthargique) »<br />
<br />
<br />
{{bug|28095}} – Le changement d’avatar ne fonctionne pas avec l’installation classique de Mageia 8 mais fonctionne avec l’installation autonome. '''Correction manuelle [https://bugs.mageia.org/show_bug.cgi?id=28095#c5 ici].'''<br />
<br />
{{bug|28287}} – Le nouvel espace de travail plasma ne permet pas de '''déverrouiller les widgets lors de la mise à jour''' depuis l’ancienne version.<br />
Les widgets du bureau et des panneaux de Plasma 5 ne peuvent pas être verrouillés ou déverrouillés à partir de la version 5.18 de Plasma. Cela signifie que tout widget verrouillé avant la mise à niveau ne peut être déverrouillé après. '''Par conséquent, avant de mettre à niveau''', assurez-vous de déverrouiller tous ces widgets.<br />
Si par la suite vous trouvez des widgets verrouillés, cela les déverrouillera :<br />
{{cmd|$ qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"}}<br />
<br />
{{bug|28299}} – Les applications GTK se plaignent (dans le journal) de l’absence de window_decorations.css. – [https://bugs.mageia.org/show_bug.cgi?id=28299#c1 Solution ici]<br />
<br />
<!--CORRIGÉ {{bug|28311}} – Erreur de segmentation avec Dolphin 20.12.0 lors de l’ouverture d’un nouvel onglet alors qu’il y a du texte dans le champ de recherche.<br />
<br />
CORRIGÉ dans la prochaine ISO {{bug|28324}} – Erreurs de segmentation avec Dolphin – Sur les systèmes installés à partir du média « live » autonome Bureau Plasma – [https://bugs.mageia.org/show_bug.cgi?id=28324#c21 Solution ici]--><br />
{{bug|28342}} – Pas d’ombres pour les menus GTK avec les applications GTK sous l’environnement Plasma. Lorsque le thème « Breeze » est défini dans Configuration du système => Apparence des applications => Style d’application => Configurer le style des applications GNOME/GTK, il n’y a pas d’ombre dans les menus GTK et le clic droit GTK. Contournement : Réglez le sur « Adwaita » (qui est par défaut).<br />
<br />
=== GNOME ===<br />
<br />
'''Wayland :''' Par défaut, GNOME utilise le serveur d’affichage Wayland. Wayland n’est pas encore complètement mature, et peut ne pas fonctionner correctement sur certains matériels. Normalement, GNOME reviendra automatiquement à l’utilisation du serveur d’affichage X.org si Wayland ne démarre pas, mais dans certains cas, cela ne marche pas. Si le bureau GNOME ne se lance pas après avoir complété la sélection initiale de la langue et de la locale, ou si vous rencontrez des problèmes d’affichage, vous pouvez essayer de forcer GNOME à utiliser le serveur d’affichage X.org en ajoutant {{cmd|nowayland}} aux options de démarrage dans le menu de démarrage initial (Appuyez sur la touche {{keypress|e}} pour modifier les options de démarrage).<br />
<br />
'''Network :''' Par défaut, le service NetworkManager est activé à la place des anciens services de gestion de réseau. Vous pouvez utiliser le menu déroulant accessible depuis le coin supérieur droit du bureau GNOME pour effectuer toute configuration réseau nécessaire. Pour les connexions filaires, le réseau est généralement configuré automatiquement et vous n’avez rien à faire. Pour les réseaux sans fil, vous devrez généralement sélectionner un point d’accès et, s’il est protégé par un mot de passe, entrer ce dernier. La configuration du réseau via le MCC/drakconnect devrait également fonctionner dans la plupart des cas.<br />
<br />
<!--=== Cinnamon ===<br />
<br />
CORRIGÉ {{bug|28129}} (Sur architecture 32 bits) – '''Nemo''' est suspendu au départ du lanceur ou du terminal.--><br />
=== Xfce ===<br />
<br />
{{bug|24134}} – Après la connexion, l’écran peut afficher des bandes noires et blanches ou des effets particuliers pendant quelques secondes.<br />
<br />
{{bug|27795}} – Avec Xfce, net_applet ne réagit pas correctement aux changements d’état de la connexion.<br />
<br />
=== LXQt ===<br />
<br />
{{bug|28360}} Le compositeur pour la transparence, généralement utilisé avec Openbox, était {{pkg|compton}}. Celui-ci est déprécié et remplacé par {{pkg|'''picom'''}}. '''Si vous passez de Mageia 7''', le fichier de configuration {{file|~/.config/compton.conf}} peut avoir des paramètres incompatibles qui doivent être modifiés – Ou simplement supprimer ce fichier. Malheureusement, nous n’avons pas encore d’outil de configuration Picom.<br />
<br />
Picom recherche la configuration dans l’ordre suivant : {{file|~/.config/picom.conf}}, {{file|~/.config/compton.conf}}, {{file|/etc/xdg/picom.conf}}. Cela signifie qu’un picom.conf personnalisé peut résider dans {{folder|~/.config/}} pour une configuration personnelle ou dans {{folder|/etc/xdg/}} pour une configuration à l’échelle du système. Donc, pour une personnalisation par utilisateur, il faut faire une copie du fichier {{file|/etc/xdg/picom.conf}} vers {{folder|~/.config/}} et l’éditer.<br />
<br />
Si vous souhaitez plutôt utiliser la configuration de compton-conf similaire à celle de Mageia 7, installez le rpm de compton-conf puis copiez {{file|/usr/share/compton-conf/compton.conf.example}} et éditez-le comme ci-dessous.<br />
<br />
Comment modifier les paramètres de Compton pour les rendre compatibles avec Picom : Renomer {{file|~/.config/compton.conf}} vers {{file|picom.conf}}, et y désactive les lignes commençant par : {{cmd|no_dnd_shadow, no_dock_shadow, clear shadow, menu_opacity, alpha_step, paint-on-overlay}} en les préparant avec un #. Faites lire la ligne commençant par vsync {{cmd|<nowiki>vsync = false;</nowiki>}}, et remplacer toute la ligne commençant par glx-swap-method avec {{cmd|<nowiki>use-damage = true;</nowiki>}}.<br />
<br />
Pour démarrer Picom: {{menu|Mageia -> Accessoires -> picom}}. Pour que Picom démarre automatiquement à l’ouverture de session : {{menu|LXQt centre de configuration -> Paramètres LXQt -> Paramètres de Session -> Autostart -> Ajouter}} Nom : Picom, Commande : picom.<br />
Un peu d’aide, si nécessaire : 1) Lancer {{cmd|picom}} depuis un terminal et voir la sortie, sortir avec Ctrl-C. 2) {{file|/etc/xdg/picom.conf}} ont des commentaires.<br />
<!--<br />
- - -<br />
<br />
CORRIGÉ {{Bug|26144}} - lxqt a le thème d’icône brisé tel qu’il est installé. – ''correctif manuel [https://bugs.mageia.org/show_bug.cgi?id=26144#c17 here].''<br />
<br />
=== Mate ===<br />
<br />
CORRIGÉ {{Bug|28202}} – Mate : Les entrées du menu sont vides.--><br />
<br />
== Logiciels ==<br />
<br />
<!--=== Les applications qui s’exécutent en mode root ne fonctionnent pas en mode graphique. ===<br />
<br />
'''{{bug|28280}} – Drakxtools ne se lance pas en mode graphique après avoir configuré le réseau.'''<br />
<br />
Le centre de contrôle Mageia échouera en mode graphique si le nom d’hôte du réseau est laissé à sa valeur par défaut de localhost.<br />
<br />
Les solutions de contournement actuelles consistent à préciser un nom d’hôte autre que « localhost » lors de la configuration du réseau, ou avant de lancer le CCM à exécuter en tant qu’utilisateur standard<br />
{{console|xhost +si:localuser:root<br>localuser:root being added to access control list}}<br />
<br />
Un correctif approprié sera décidé et mis en œuvre avant la production des images ISO finales.<br />
<br />
Il a également été démontré que ce bogue affecte le SDDM dans certains cas. {{bug|27601}}<br />
--><br />
=== Mageia Welcome ===<br />
<br />
{{bug|28328}} – Steam ne peut pas être installé en un clic avec le bouton proposé avec Mageia Welcome si les dépôts 32 bits ne sont pas être activés, comme c’est le cas par défaut. [[Mageia_8_Notes_de_version-fr#Dépôts 32 bits sur des systèmes 64 bits|Les dépôts 32 bits doivent être activés]] pour compléter l’installation.<br />
<br />
=== Flatpak ===<br />
<br />
Plasma Discover et Gnome-software préfèrent [[Les_méthodes_pour_installer_des_programmes-fr#Flatpak|Flatpak]] [https://bugs.mageia.org/show_bug.cgi?id=27620#c5 aux paquets RPM de Mageia].<br />
<br />
<!--=== Vidéo ===<br />
<br />
CORRIGÉ {{bug|27377}} – VLC diffuse de l’audio mais pas de la vidéo.--><br />
=== Logiciels divers ===<br />
<br />
{{Bug|28097}} - Erreur de segmentation xviewer, également absent du menu des applications.</br><br />
CORRIGÉ lors de la mise à jour {{bug|28363}} – VLC plante à l’ouverture d’un fichier MKV lorsque le codec vidéo est AV1.<br />
<br />
== Divers ==<br />
<br />
=== Hibernation ===<br />
<br />
{{bug|28528}} - Sortir de l'hibernation au lieu de repartir à zéro. '''Correction manuelle''' : voir le bogue en cause.<br />
<br />
=== Programme de téléchargement ===<br />
<br />
==== Téléchargement des logiciels RPMs ====<br />
<br />
Pour quelques personnes, la méthode de téléchargement par défaut échoue par intermittence. '''Une autre méthode consiste à''' démarrer {{cmd|drakrpm-edit-media}} qui est un des modules du {{prog|Centre de contrôle de Mageia}} qui se trouve dans {{menu|Gestion des logiciels -> Configurer les sources pour installer et mettre à jour des logiciels}}. Dans le menu {{menu|Options -> Options générales}} mettre « Programme de téléchargement à utiliser » sur « wget ». {{bug|24362}}<br />
<br />
=== Impression ===<br />
<br />
==== PImprimante en double – ce n’est pas un bogue ====<br />
<br />
Vous pouvez voir votre imprimante affichée deux fois. En effet, toutes les imprimantes disponibles sont affichées sur le serveur CUPS local (localhost) et sur tous les serveurs CUPS connectés. Ainsi, si vous partagez une imprimante sur le réseau, ce qui est le cas par défaut, elle sera affichée en double sur l’ordinateur partagé. Ce comportement n’est pas propre à Mageia.<br />
<br />
Solution de contournement : Dites à CUPS de ne pas partager le travail de la file d’attente des imprimantes sur le réseau local si vous n’avez pas besoin de l’utiliser depuis un autre ordinateur. Allez dans {{prog|Centre de contrôle Mageia}} Section {{menu|Matériel > Configurer l’impression}} menu {{menu|Serveur -> Réglages}}.<br />
<br />
=== Shell / Terminals ===<br />
<br />
==== « mode de collage entre crochets » affectant le copier-coller ====<br />
<br />
Par défaut, readline 8.1 a activé le mode de collage « entre crochets », qui est également actif, notamment dans le shell bash. Cela signifie que si quelque chose est collé dans votre terminal, le texte collé sera entouré de caractères d’échappement invisibles \e[200~ et \e[201~</br><br />
L’effet manifeste est que les couleurs d’arrière-plan et de premier plan sont remplacées par le texte collé, et qu’il faut également appuyer sur une touche ou cliquer avec la souris pour pouvoir exécuter le texte collé.</br><br />
Pour plus d’informations à ce sujet, voir [https://cirw.in/blog/bracketed-paste bracketed paste mode].</br><br />
</br><br />
Ceci peut être désactivé pour bash en ajoutant la ligne {{cmd|<nowiki>bind 'set enable-bracketed-paste off'</nowiki>}} au fichier {{file|~/.bashrc}}. les modifications sur le fichier {{file|~/.bashrc}} prendront effet au prochain lancement du shell bash.<br />
</br></br><br />
Il devrait également être possible de désactiver cette fonction en ajoutant le paramètre {{cmd|<nowiki>set enable-bracketed-paste off</nowiki>}} au fichier {{file|~/.inputrc}}, mais cela ne semble pas avoir d’effet.<br />
<br />
== Difficultés sur la mise à niveau ==<br />
<br />
Assurez-vous de suivre l’une des procédures indiquées dans [[Mageia_8_Notes_de_version-fr#Mise à niveau depuis Mageia 7|les notes de mise de version]]. Évitez les interférences de l’économiseur d’écran ! {{bug|25251}}<br />
<br />
=== Si la mise à niveau échoue ===<br />
<br />
Si vous ne pouvez pas démarrer votre machine dans un état fonctionnel, démarrez sur l’ISO classique et effectuez une mise à niveau. Gardez à l’esprit '''qu’il ne faut pas formater''' les partitions. C’est important : vous devez '''activer tous les dépôts de mise à jour''' qui ont été actifs lors d’une mise à jour ou d’une version précédente. Notez également que l’installation classique n’utilise pas de pilotes nonfree, vous pouvez avoir besoin d’une connexion filaire pour avoir un accès à internet. Si cela vous est impossible, essayez l’image d’installation réseau avec le micro-code non libre. Il y a davantage de pilote pour le wifi. Pour plus d’information consulter [[Mageia 8 Notes de version-fr#Supports d’installation disponibles|Supports d’installation disponibles]].<br />
<br />
Si toutes les tentatives de mise à jour échouent, la solution de repli consiste à effectuer une nouvelle installation, en conservant éventuellement le dossier {{folder|/home}}, dans ce cas (NE PAS LE FORMATER).<br />
<br />
=== Mise à niveau à l’aide de DNF ===<br />
<br />
'''Installer une version supplémentaire du noyau''' – DNF utilise une méthode différente de celle de l’outil d’installation Mageia pour sélectionner la version du noyau. Cela peut avoir pour conséquence qu’un système qui utilisait un kernel desktop, après la mise à niveau ait à la fois des kernels desktop et server installés, et le kernel server est utilisé. Pour corriger cela, sélectionner au démarrage le kernel desktop, puis désinstaller le kernel server {{bug|28272}}.<br />
<br />
=== Suppression de PHP7 ===<br />
<br />
Mageia 8 n’a pas de PHP7. Cela peut poser des problèmes si vous avez un logiciel qui est incompatible avec PHP8.<br />
<br />
Exemples :<br />
* [[Mageia_8_Notes_de_version-fr#Nextcloud|'''Nextcloud''' arrive dans le dépôt backport]]<br />
* Client de messagerie '''Roundcube''' {{bug|28533}} en cours de résolution<br />
<br />
=== Paquetages retirés de la distribution ===<br />
<br />
Consulter [[Mageia 8 Notes de version-fr#Paquetages retirés de la distribution|à la fin des notes de version]].<br />
<br />
==== VirtualBox ====<br />
<br />
[[Mageia_8_Release_Notes#VirtualBox|Il n’y a plus d’hôte]] VirtualBox 32 bits.<br />
<br />
=== Difficultés diverses sur la mise à niveau ===<br />
<br />
<br />
''''' Nous nous efforçons de publier des mises à jour pour résoudre les problèmes. Consultez les bogues pour connaître les dernières nouvelles. '''''<br />
<br />
{{bug|28007}} – llvm-11.0 Les paquets mga8 entrent en conflit avec les paquets mga7 llvm-devel lors de la mise à jour de MGA7 en MGA8<br />
<br />
{{bug|28479}} – conflits entre les paquets batik et la mise à niveau de Mageia 7 à 8<br />
<br />
CORRIGÉ avec la mise à niveau vers Mageia 8 {{bug|28481}} – npm a une version plus élevée sur Mageia 7 que sur Mageia 8, ce qui entraîne des problèmes de mise à niveau.<br />
<br />
CORRIGÉ avec la mise à niveau vers Mageia 8 {{bug|28485}} – mythtv: la mise à jour de MGA7->MGA8 échoue sur des conflits de fichiers.<br />
<br />
{{bug|28503}} – '''php-json''' provient de Mageia 7 et casse PHP dans Mageia 8 – php-json est maintenant inclus, il n’y a plus d’extension. CORRECTION : Supprimez le php-json persistant. La mise à jour arrive pour faire cela automatiquement.<br />
<br />
{{bug|28522}} - Les conflits de fichiers avec '''opencv-devel''' provoquent des erreurs en cascade lors de la mise à niveau de Mageia 7 vers Mageia 8<br />
<br />
{{bug|28550}} – Si UID est 500, la variable $PATH ne contient pas le répertoire {{folder|/usr/games}}, par conséquent '''les jeux ne peuvent pas être lancés'''. Cela concerne les systèmes installés à l’origine avec Mageia version 6 ou antérieure et mis à jour depuis, ou un paramétrage manuel de l''''UID < 1000'''. <br />
<br />
==== Samba ====<br />
<br />
{{bug|28042}} – Pendant la mise à niveau vers MGA8 – ERROR:'script' failed for samba-client-4.10.18-1.1mga7.x86_64</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Mageia_8_Errata-fr&diff=51049Mageia 8 Errata-fr2021-03-18T08:27:29Z<p>Dtux: corrected a word</p>
<hr />
<div>[[Category:Erratas]]<br />
[[Category:Mageia 8]]<br />
<br />
{{Bandeau multi-langues-fr|[[Mageia_8_Errata-de|Deutsch]] ; [[Mageia_8_Errata|English]] ; [[Erratas de Mageia 8|Español]] ; [[Mageia_8_Errata-fr|Français]] ; [[Mageia_8_Erratas do Mageia|Português (Portugal)]] ;}}<br />
<br />
== Notes ==<br />
<br />
Cette page est un complément des [[Mageia 8 Notes de version-fr|Notes de version]].<br />
<br />
<!--'''Cette page reflète actuellement la sortie de RC.''' Elle sera révisée pour toute nouvelle RC, et pour les ISO définitives.--><br />
'''Les rubriques ci-dessous précédées de « CORRIGÉ », ont une mise à jour disponible.'''<br />
Donc si vous rencontrez un problème marqué comme résolu, essayez de faire une mise à jour complète. Certains problèmes peuvent nécessiter une déconnexion/login ou un redémarrage. D’autres sont des problèmes d’installation ou de mise à niveau. Notze que la publication d'une mise à jour peut demander 24H pour être disponible sur [http://mirrors.mageia.org/status votre mirroir].<br />
<br />
Seuls les problèmes importants concernant les paquets contenus dans les ISO sont énumérés ici. Nous avons beaucoup de logiciels supplémentaires dans les dépôts.<br />
<br />
Un problème non répertorié que vous voyez peut-être résolu si vous faites une mise à jour complète.<br />
<br />
Voir également les sections des Notes de versions [[Mageia_8_Notes_de_version-fr#Problèmes connus|Problèmes connus]] et [[Mageia_8_Notes_de_version-fr#Signaler un bogue|Rapport de bogue]].<br />
<br />
Attention, nous ajouterons les problèmes provenant de l’outil de suivi des bogues, à savoir<!--[https://bugs.mageia.org/buglist.cgi?keywords=8rc1 rc1], [https://bugs.mageia.org/buglist.cgi?keywords=8rc2 rc2]-->, [https://bugs.mageia.org/buglist.cgi?keywords=FOR_ERRATA8 Pour ERRATA 8], [https://bugs.mageia.org/buglist.cgi?keywords=FOR_RELEASENOTES8 Pour les notes de versions 8] au fur et à mesure qu’ils seront signalés.<br />
<br />
== Démarrage ==<br />
<br />
== Images autonomes ==<br />
<br />
== Images d’installation ==<br />
<br />
=== Plantage à la fin de l’installation ===<br />
<br />
{{bug|27838}} Certains ordinateurs ont des firmwares bogués, ce qui fait que les écritures sur la NVRAM EFI échouent à la fin de l’installation de Mageia.<br />
<br />
Solution de contournement : Lors de la configuration du chargeur de démarrage à la fin de l’installation : Selectionner rEFInd à la place de GRUB, cocher « Install in /EFI/BOOT », décocher l’option de stockage dans la NVRAM ''(Nouveau pour Mageia 8)''<br />
<br />
=== Installateur réseau ===<br />
<br />
* Sur certaines machines UEFI, l’ISO d’Installation Réseau démarre avec un '''message d’erreur Grub''' :<br><br />
''error: ../../grub-core/video/readers/png.c:595 invalid filter value''<br><br />
Et affiche le menu Grub2 en mode texte au lieu du mode graphique.<br />
Le fonctionnement n’est pas affecté ; il s’agit simplement d’une bizarrerie esthétique. {{bug|28225}}<br />
* Si la source de l’installation de Mageia se trouve sur un périphérique USB formaté avec le système de fichiers '''exFAT''', vous devrez peut-être débrancher et rebrancher le périphérique USB pour avoir accès à la partition. [https://bugs.mageia.org/show_bug.cgi?id=28371#c23 Comment#23 dans mga#28371]<br />
<br />
=== L’image d’installation 32 bits doit être sur DVD pour fonctionner comme dépôt. ===<br />
<br />
Après l’installation du système, les ISOs de l’installation classique peuvent être utilisés comme dépôt, pour installer des logiciels sans utiliser de connexion Internet.<br />
<br />
L’ISO 64 bits fonctionne comme dépôt à la fois sur DVD et sur clé USB. Les ISO 32 bits fonctionnent uniquement comme dépôt à partir d’un DVD.<br />
<br />
== Graphiques ==<br />
<br />
=== AMD/ATI ===<br />
<br />
CORRIGÉ (?){{bug|28154}} – Les médias autonomes ne démarrent pas avec certains GPU Radeon HD ou avec un système installé avec l’ISO classique.<br />
<br />
Des corrections sont en cours. Veuillez vous assurer que toutes les mises à jour disponibles sont installées avant de signaler les problèmes rencontrés.<br />
<br />
Pour les cartes graphiques AMD de la famille Southern Islands (Tahiti, Pitcairn, Oland, Verde, Hainan) et Sea Islands (Kaveri, Bonaire, Hawaii, Kabini, Mullins), nous utilisons par défaut le nouveau pilote amdgpu au lieu de l’ancien pilote radeon, et nous voulons savoir s’il fonctionne ou non correctement sur votre matériel.<br />
<br />
Si cela ne fonctionne pas, vous pouvez vous revenir à l’ancien pilote en ajoutant ce qui suit [[Comment_ajouter_des_options_au_noyau-fr#Avec le chargeur de boot Grub 2|en ligne de commande au noyau]] :<br />
<br />
Pour les cartes Southern Island :<br />
radeon.si_support=1 amdgpu.si_support=0<br />
<br />
Pour les cartes Sea Islands :<br />
radeon.cik_support=1 amdgpu.cik_support=0<br />
<br />
=== Nvidia ===<br />
<br />
Nvidia a négligé de régler les problèmes de sécurité de son pilote de la série 340, nous avons donc dû le retirer des dépôts officiels. Voir les [[Mageia 8 Notes de version-fr#Pilote propriétaire NVIDIA|Notes de version]].<br />
<br />
== Environnements de bureaux ==<br />
<br />
{{Bug|23929}} - Le répertoire « Desktop » sous $HOME n’a pas été traduit lors de l'installation de '''Plasma ou MATE uniquement'''.<br />
<br />
{{Bug|28378}} - '''SDDM greeter''' ne se souvient pas de la session précédemment exécutée. - '''correction manuelle''': Dans {{file|/etc/sddm.conf}} dans la ligne {{cmd|<nowiki>RememberLastSession=false</nowiki>}} changez false en true. Ceci fera l'objet d'une mise à jour. Cette mise à jour définit également le paramètre {{cmd|<nowiki>RememberLastUser=false</nowiki>}}, vous pouvez le définir comme true si vous souhaitez que le dernier utilisateur soit présélectionné lors de la connexion.<br />
<br />
=== Plasma ===<br />
<br />
La session '''Wayland''' avec les pilotes nonfree 455 (actuels) de Nvidia est disponible en s’assurant que « nokmsboot » est supprimé et que « nouveau.modeset=0 » est passé à la ligne de commande du noyau. {{bug|27296}} – La session Plasma Wayland est cassée, et {{bug|28365}} – Le centre de contrôle ne démarre pas avec Plasma Wayland (correction temporaire : en tant qu’utilisateur normal, premier problème {{cmd|xhost +si:localuser:root}}) <br />
<br />
Les effets de bureau '''Compiz''' ne sont plus compatibles avec Plasma. Si vous l’utilisez avec Plasma sur Mageia 7, désactivez-le dans {{prog|Centre de contrôle Mageia}} {{menu|Matériel -> Configurez les effets bureau 3D}} – '''avant''' de mettre à niveau, et si vous voulez que Compiz cesse d’être disponible pour un autre environnement de bureau, désinstallez-le. Après l’installation ou la mise à niveau de Mageia, vous trouverez les effets de bureau dans {{menu|Configuration du système}} (icône de la barre des tâches) -> {{menu|Espace de travail}} -> {{menu|Comportement de l’espace de travail}} -> {{menu|Effets de bureau}}.<br />
<br />
L’extension clic droit ''kde-rootactions-servicemenu'' de '''Dolphin''' est supprimée, car elle est délaissée en amont et présente des problèmes.<br />
<br />
{{bug|27147}} – Connexions successives multi-utilisateurs, plasmashell ne se connecte plus à n’importe quel utilisateur après s’être éteint.<br />
<br />
{{bug|27183}} – Les réglages par défaut de l’intégration de spectacle de Mageia manquent dans configuration du système de plasma – ''Dans certains cas, après la mise à niveau.'' CORRECTION : Lancer Spectacle, sélectionner le bouton {{menu|Configurer -> Raccourcis -> Lancer Spectacle}}. Changer le paramètre de « Personnalisé » vers « Par défaut » (Imprimer), et confirmer la demande de réassignation dans la fenêtre qui s’affiche. <br />
<br />
{{bug|27362}} – startplasma-x11 engendre un processus zombie « (peut le rendre léthargique) »<br />
<br />
<br />
{{bug|28095}} – Le changement d’avatar ne fonctionne pas avec l’installation classique de Mageia 8 mais fonctionne avec l’installation autonome. '''Correction manuelle [https://bugs.mageia.org/show_bug.cgi?id=28095#c5 ici].'''<br />
<br />
{{bug|28287}} – Le nouvel espace de travail plasma ne permet pas de '''déverrouiller les widgets lors de la mise à jour''' depuis l’ancienne version.<br />
Les widgets du bureau et des panneaux de Plasma 5 ne peuvent pas être verrouillés ou déverrouillés à partir de la version 5.18 de Plasma. Cela signifie que tout widget verrouillé avant la mise à niveau ne peut être déverrouillé après. '''Par conséquent, avant de mettre à niveau''', assurez-vous de déverrouiller tous ces widgets.<br />
Si par la suite vous trouvez des widgets verrouillés, cela les déverrouillera :<br />
{{cmd|$ qdbus org.kde.plasmashell /PlasmaShell evaluateScript "lockCorona(false)"}}<br />
<br />
{{bug|28299}} – Les applications GTK se plaignent (dans le journal) de l’absence de window_decorations.css. – [https://bugs.mageia.org/show_bug.cgi?id=28299#c1 Solution ici]<br />
<br />
<!--CORRIGÉ {{bug|28311}} – Erreur de segmentation avec Dolphin 20.12.0 lors de l’ouverture d’un nouvel onglet alors qu’il y a du texte dans le champ de recherche.<br />
<br />
CORRIGÉ dans la prochaine ISO {{bug|28324}} – Erreurs de segmentation avec Dolphin – Sur les systèmes installés à partir du média « live » autonome Bureau Plasma – [https://bugs.mageia.org/show_bug.cgi?id=28324#c21 Solution ici]--><br />
{{bug|28342}} – Pas d’ombres pour les menus GTK avec les applications GTK sous l’environnement Plasma. Lorsque le thème « Breeze » est défini dans Configuration du système => Apparence des applications => Style d’application => Configurer le style des applications GNOME/GTK, il n’y a pas d’ombre dans les menus GTK et le clic droit GTK. Contournement : Réglez le sur « Adwaita » (qui est par défaut).<br />
<br />
=== GNOME ===<br />
<br />
'''Wayland :''' Par défaut, GNOME utilise le serveur d’affichage Wayland. Wayland n’est pas encore complètement mature, et peut ne pas fonctionner correctement sur certains matériels. Normalement, GNOME reviendra automatiquement à l’utilisation du serveur d’affichage X.org si Wayland ne démarre pas, mais dans certains cas, cela ne marche pas. Si le bureau GNOME ne se lance pas après avoir complété la sélection initiale de la langue et de la locale, ou si vous rencontrez des problèmes d’affichage, vous pouvez essayer de forcer GNOME à utiliser le serveur d’affichage X.org en ajoutant {{cmd|nowayland}} aux options de démarrage dans le menu de démarrage initial (Appuyez sur la touche {{keypress|e}} pour modifier les options de démarrage).<br />
<br />
'''Network :''' Par défaut, le service NetworkManager est activé à la place des anciens services de gestion de réseau. Vous pouvez utiliser le menu déroulant accessible depuis le coin supérieur droit du bureau GNOME pour effectuer toute configuration réseau nécessaire. Pour les connexions filaires, le réseau est généralement configuré automatiquement et vous n’avez rien à faire. Pour les réseaux sans fil, vous devrez généralement sélectionner un point d’accès et, s’il est protégé par un mot de passe, entrer ce dernier. La configuration du réseau via le MCC/drakconnect devrait également fonctionner dans la plupart des cas.<br />
<br />
<!--=== Cinnamon ===<br />
<br />
CORRIGÉ {{bug|28129}} (Sur architecture 32 bits) – '''Nemo''' est suspendu au départ du lanceur ou du terminal.--><br />
=== Xfce ===<br />
<br />
{{bug|24134}} – Après la connexion, l’écran peut afficher des bandes noires et blanches ou des effets particuliers pendant quelques secondes.<br />
<br />
{{bug|27795}} – Avec Xfce, net_applet ne réagit pas correctement aux changements d’état de la connexion.<br />
<br />
=== LXQt ===<br />
<br />
{{bug|28360}} Le compositeur pour la transparence, généralement utilisé avec Openbox, était {{pkg|compton}}. Celui-ci est déprécié et remplacé par {{pkg|'''picom'''}}. '''Si vous passez de Mageia 7''', le fichier de configuration {{file|~/.config/compton.conf}} peut avoir des paramètres incompatibles qui doivent être modifiés – Ou simplement supprimer ce fichier. Malheureusement, nous n’avons pas encore d’outil de configuration Picom.<br />
<br />
Picom recherche la configuration dans l’ordre suivant : {{file|~/.config/picom.conf}}, {{file|~/.config/compton.conf}}, {{file|/etc/xdg/picom.conf}}. Cela signifie qu’un picom.conf personnalisé peut résider dans {{folder|~/.config/}} pour une configuration personnelle ou dans {{folder|/etc/xdg/}} pour une configuration à l’échelle du système. Donc, pour une personnalisation selon la copie de l’utilisateur {{file|/etc/xdg/picom.conf}} vers {{folder|~/.config/}} et l’éditer.<br />
<br />
Si vous souhaitez plutôt utiliser la configuration de compton-conf similaire à celle de Mageia 7, installez le rpm de compton-conf puis copiez {{file|/usr/share/compton-conf/compton.conf.example}} et éditez-le comme ci-dessous.<br />
<br />
Comment modifier les paramètres de Compton pour les rendre compatibles avec Picom : Renomer {{file|~/.config/compton.conf}} vers {{file|picom.conf}}, et y désactive les lignes commençant par : {{cmd|no_dnd_shadow, no_dock_shadow, clear shadow, menu_opacity, alpha_step, paint-on-overlay}} en les préparant avec un #. Faites lire la ligne commençant par vsync {{cmd|<nowiki>vsync = false;</nowiki>}}, et remplacer toute la ligne commençant par glx-swap-method avec {{cmd|<nowiki>use-damage = true;</nowiki>}}.<br />
<br />
Pour démarrer Picom: {{menu|Mageia -> Accessoires -> picom}}. Pour que Picom démarre automatiquement à l’ouverture de session : {{menu|LXQt centre de configuration -> Paramètres LXQt -> Paramètres de Session -> Autostart -> Ajouter}} Nom : Picom, Commande : picom.<br />
Un peu d’aide, si nécessaire : 1) Lancer {{cmd|picom}} depuis un terminal et voir la sortie, sortir avec Ctrl-C. 2) {{file|/etc/xdg/picom.conf}} ont des commentaires.<br />
<!--<br />
- - -<br />
<br />
CORRIGÉ {{Bug|26144}} - lxqt a le thème d’icône brisé tel qu’il est installé. – ''correctif manuel [https://bugs.mageia.org/show_bug.cgi?id=26144#c17 here].''<br />
<br />
=== Mate ===<br />
<br />
CORRIGÉ {{Bug|28202}} – Mate : Les entrées du menu sont vides.--><br />
== Logiciels ==<br />
<br />
<!--=== Les applications qui s’exécutent en mode root ne fonctionnent pas en mode graphique. ===<br />
<br />
'''{{bug|28280}} – Drakxtools ne se lance pas en mode graphique après avoir configuré le réseau.'''<br />
<br />
Le centre de contrôle Mageia échouera en mode graphique si le nom d’hôte du réseau est laissé à sa valeur par défaut de localhost.<br />
<br />
Les solutions de contournement actuelles consistent à préciser un nom d’hôte autre que « localhost » lors de la configuration du réseau, ou avant de lancer le CCM à exécuter en tant qu’utilisateur standard<br />
{{console|xhost +si:localuser:root<br>localuser:root being added to access control list}}<br />
<br />
Un correctif approprié sera décidé et mis en œuvre avant la production des images ISO finales.<br />
<br />
Il a également été démontré que ce bogue affecte le SDDM dans certains cas. {{bug|27601}}<br />
--><br />
=== Mageia Welcome ===<br />
<br />
{{bug|28328}} – Steam ne peut pas être installé en un clic avec le bouton proposé avec Mageia Welcome si les dépôts 32 bits ne sont pas être activés, comme c’est le cas par défaut. [[Mageia_8_Notes_de_version-fr#Dépôts 32 bits sur des systèmes 64 bits|Les dépôts 32 bits doivent être activés]] pour compléter l’installation.<br />
<br />
=== Flatpak ===<br />
<br />
Plasma Discover et Gnome-software préfèrent [[Les_méthodes_pour_installer_des_programmes-fr#Flatpak|Flatpak]] [https://bugs.mageia.org/show_bug.cgi?id=27620#c5 aux paquets RPM de Mageia].<br />
<br />
<!--=== Vidéo ===<br />
<br />
CORRIGÉ {{bug|27377}} – VLC diffuse de l’audio mais pas de la vidéo.--><br />
=== Logiciels divers ===<br />
<br />
{{Bug|28097}} - Erreur de segmentation xviewer, également absent du menu des applications.<br />
CORRIGÉ lors de la mise à jour {{bug|28363}} – VLC plante à l’ouverture d’un fichier MKV lorsque le codec vidéo est AV1.<br />
<br />
== Divers ==<br />
<br />
=== Hybernation ===<br />
<br />
{{bug|28528}} - Sortir de l'hibernation au lieu de repartir à zéro. '''Correction manuelle''' : voir le bogue en cause.<br />
<br />
=== Programme de téléchargement ===<br />
<br />
==== Téléchargement des logiciels RPMs ====<br />
<br />
Pour quelques personnes, la méthode de téléchargement par défaut échoue par intermittence. '''Une autre méthode consiste à''' démarrer {{cmd|drakrpm-edit-media}} qui est un des modules du {{prog|Centre de contrôle de Mageia}} qui se trouve dans {{menu|Gestion des logiciels -> Configurer les sources pour installer et mettre à jour des logiciels}}. Dans le menu {{menu|Options -> Options générales}} mettre « Programme de téléchargement à utiliser » sur « wget ». {{bug|24362}}<br />
<br />
=== Impression ===<br />
<br />
==== PImprimante en double – ce n’est pas un bogue ====<br />
<br />
Vous pouvez voir votre imprimante affichée deux fois. En effet, toutes les imprimantes disponibles sont affichées sur le serveur CUPS local (localhost) et sur tous les serveurs CUPS connectés. Ainsi, si vous partagez une imprimante sur le réseau, ce qui est le cas par défaut, elle sera affichée en double sur l’ordinateur partagé. Ce comportement n’est pas propre à Mageia.<br />
<br />
Solution de contournement : Dites à CUPS de ne pas partager le travail de la file d’attente des imprimantes sur le réseau local si vous n’avez pas besoin de l’utiliser depuis un autre ordinateur. Allez dans {{prog|Centre de contrôle Mageia}} Section {{menu|Matériel > Configurer l’impression}} menu {{menu|Serveur -> Réglages}}.<br />
<br />
=== Shell / Terminals ===<br />
<br />
==== « mode de collage entre crochets » affectant le copier-coller ====<br />
<br />
Par défaut, readline 8.1 a activé le mode de collage « entre crochets », qui est également actif, notamment dans le shell bash. Cela signifie que si quelque chose est collé dans votre terminal, le texte collé sera entouré de caractères d’échappement invisibles \e[200~ et \e[201~</br><br />
L’effet manifeste est que les couleurs d’arrière-plan et de premier plan sont remplacées par le texte collé, et qu’il faut également appuyer sur une touche ou cliquer avec la souris pour pouvoir exécuter le texte collé.</br><br />
Pour plus d’informations à ce sujet, voir [https://cirw.in/blog/bracketed-paste bracketed paste mode].</br><br />
</br><br />
Ceci peut être désactivé pour bash en ajoutant la ligne {{cmd|<nowiki>bind 'set enable-bracketed-paste off'</nowiki>}} au fichier {{file|~/.bashrc}}. les modifications sur le fichier {{file|~/.bashrc}} prendront effet au prochain lancement du shell bash.<br />
</br></br><br />
Il devrait également être possible de désactiver cette fonction en ajoutant le paramètre {{cmd|<nowiki>set enable-bracketed-paste off</nowiki>}} au fichier {{file|~/.inputrc}}, mais cela ne semble pas avoir d’effet.<br />
<br />
== Difficultés sur la mise à niveau ==<br />
<br />
Assurez-vous de suivre l’une des procédures indiquées dans [[Mageia_8_Notes_de_version-fr#Mise à niveau depuis Mageia 7|les notes de mise de version]]. Évitez les interférences de l’économiseur d’écran ! {{bug|25251}}<br />
<br />
=== Si la mise à niveau échoue ===<br />
<br />
Si vous ne pouvez pas démarrer votre machine dans un état fonctionnel, démarrez sur l’ISO classique et effectuez une mise à niveau. Gardez à l’esprit '''qu’il ne faut pas formater''' les partitions. C’est important : vous devez '''activer tous les dépôts de mise à jour''' qui ont été actifs lors d’une mise à jour ou d’une version précédente. Notez également que l’installation classique n’utilise pas de pilotes nonfree, vous pouvez avoir besoin d’une connexion filaire pour avoir un accès à internet. Si cela vous est impossible, essayez l’image d’installation réseau avec le micro-code non libre. Il y a davantage de pilote pour le wifi. Pour plus d’information consulter [[Mageia 8 Notes de version-fr#Supports d’installation disponibles|Supports d’installation disponibles]].<br />
<br />
Si toutes les tentatives de mise à jour échouent, la solution de repli consiste à effectuer une nouvelle installation, en conservant éventuellement le dossier {{folder|/home}}, dans ce cas (NE PAS LE FORMATER).<br />
<br />
=== Mise à niveau à l’aide de DNF ===<br />
<br />
'''Installer une version suplémentaire du noyau''' – DNF utilise une méthode différente de celle de l’outil d’installation Mageia pour sélectionner la version du noyau. Cela peut avoir pour conséquence qu’un système qui utilisait un kernel desktop, après la mise à niveau ait à la fois des kernels desktop et server installés, et le kernel server est utilisé. Pour corriger cela, sélectionner au démarrage le kernel desktop, puis désinstaller le kernel server {{bug|28272}}.<br />
<br />
=== Suppression de PHP7 ===<br />
<br />
Mageia 8 n’a pas de PHP7. Cela peut poser des problèmes si vous avez un logiciel qui est incompatible avec PHP8.<br />
<br />
Exemples :<br />
* [[Mageia_8_Notes_de_version-fr#Nextcloud|'''Nextcloud''' arrive dans le dépôt backport]]<br />
* Client de messagerie '''Roundcube''' {{bug|28533}} en cours de résolution<br />
<br />
=== Paquetages retirés de la distribution ===<br />
<br />
Consulter [[Mageia 8 Notes de version-fr#Paquetages retirés de la distribution|à la fin des notes de version]].<br />
<br />
==== VirtualBox ====<br />
<br />
[[Mageia_8_Release_Notes#VirtualBox|Il n’y a plus d’hôte]] VirtualBox 32 bits.<br />
<br />
=== Difficultés diverses sur la mise à niveau ===<br />
<br />
<br />
''''' Nous nous efforçons de publier des mises à jour pour résoudre les problèmes. Consultez les bogues pour connaître les dernières nouvelles. '''''<br />
<br />
{{bug|28007}} – llvm-11.0 Les paquets mga8 entrent en conflit avec les paquets mga7 llvm-devel lors de la mise à jour de MGA7 en MGA8<br />
<br />
{{bug|28479}} – conflits entre les paquets batik et la mise à niveau de Mageia 7 à 8<br />
<br />
CORRIGÉ avec la mise à niveau vers Mageia 8 {{bug|28481}} – npm a une version plus élevée sur Mageia 7 que sur Mageia 8, ce qui entraîne des problèmes de mise à niveau.<br />
<br />
CORRIGÉ avec la mise à niveau vers Mageia 8 {{bug|28485}} – mythtv: la mise à jour de MGA7->MGA8 échoue sur des conflits de fichiers.<br />
<br />
{{bug|28503}} – '''php-json''' provient de Mageia 7 et casse PHP dans Mageia 8 – php-json est maintenant inclus, il n’y a plus d’extension. CORRECTION : Supprimez le php-json persistant. La mise à jour arrive pour faire cela automatiquement.<br />
<br />
{{bug|28522}} - Les conflits de fichiers avec '''opencv-devel''' provoquent des erreurs en cascade lors de la mise à niveau de Mageia 7 vers Mageia 8<br />
<br />
{{bug|28550}} – Si UID est 500, la variable $PATH ne contient pas le répertoire {{folder|/usr/games}}, par conséquent '''les jeux ne peuvent pas être lancés'''. Cela concerne les systèmes installés à l’origine avec Mageia version 6 ou antérieure et mis à jour depuis, ou un paramétrage manuel de l''''UID < 1000'''. <br />
<br />
==== Samba ====<br />
<br />
{{bug|28042}} – Pendant la mise à niveau vers MGA8 – ERROR:'script' failed for samba-client-4.10.18-1.1mga7.x86_64</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Using_Zoom_communication_application&diff=47141Using Zoom communication application2020-04-22T18:35:27Z<p>Dtux: added # prompt for root as this is the default prompt in Mageia</p>
<hr />
<div>[[file:ZoomLogo.png]]<br />
<br />
<br />
= Introduction =<br />
<br />
<b>Zoom</b> is an audio and video conferencing system available for PCs and mobiles: Linux, Apple, Windows, Android, Blackberry.<br />
<br />
This page describes how to install <b>Zoom</b> in Mageia 6 Linux and later.<br />
<br />
For more information, please see: [https://support.zoom.us/hc/en-us/categories/200101697 Getting started with Zoom]<br />
<br />
Note that Zoom client is free but is not available via the Mageia packaging system.<br />
Zoom calls up to 40 minutes are free.<br />
<br />
= Benefits =<br />
<br />
<b>Zoom</b> makes it easy to have voice and video conference calls.<br />
Unlike some other VOIP systems it does not limit the number of people on a call.<br />
You can share your desktop, have text chat, and record your meetings.<br />
<br />
<br />
= Preparation =<br />
<br />
== Install pre-requisites ==<br />
<br />
As root, install packages that are needed for Zoom:<br />
<br />
32 bits installation:<br />
<pre><br />
# urpmi libxcb-xtest0 # needed by Zoom<br />
</pre><br />
64 bits installation:<br />
<pre><br />
# urpmi lib64xcb-xtest0 # needed by Zoom<br />
</pre><br />
(You can use sudo command if it is configured on your system)<br />
<br />
== Download Zoom ==<br />
<br />
Download from [https://zoom.us/download?os=linux Zoom's download centre].<br />
Unfortunately, there is no port for Mageia but we can use the Fedora version.<br />
<br />
From the <i>Select Linux type</i> select <b>Fedora</b>.<br />
<br />
Select correct <i>OA architecture</i> to match your system (eg 32 or 64 bit).<br />
<br />
Click on <b>Download</b><br />
<br />
Alternatively, from command line:<br />
<br />
<pre><br />
cd ~/Downloads<br />
wget https://zoom.us/client/latest/zoom_x86_64.rpm<br />
<br />
</pre><br />
<br />
Example:<br />
<br />
<pre><br />
[user@localhost Downloads]$ wget https://zoom.us/client/latest/zoom_x86_64.rpm<br />
--2018-11-03 16:05:20-- https://zoom.us/client/latest/zoom_x86_64.rpm<br />
Resolving zoom.us... 52.202.62.235<br />
Connecting to zoom.us|52.202.62.235|:443... connected.<br />
HTTP request sent, awaiting response... 302 Found<br />
Location: https://d11yldzmag5yn.cloudfront.net/prod/2.4.129780.0915/zoom_x86_64.rpm [following]<br />
--2018-11-03 16:05:21-- https://d11yldzmag5yn.cloudfront.net/prod/2.4.129780.0915/zoom_x86_64.rpm<br />
Resolving d11yldzmag5yn.cloudfront.net... 143.204.178.155, 143.204.178.138, 143.204.178.90, ...<br />
Connecting to d11yldzmag5yn.cloudfront.net|143.204.178.155|:443... connected.<br />
HTTP request sent, awaiting response... 200 OK<br />
Length: 64157086 (61M) [binary/octet-stream]<br />
Saving to: ‘zoom_x86_64.rpm’<br />
<br />
zoom_x86_64.rpm 27%[=========================> ] 16.67M 472KB/s eta 99s <br />
</pre><br />
<br />
<br />
= Install Zoom =<br />
<br />
As root, install the downloaded Zoom rpm.<br />
<br />
Note that we are using "--nodeps" because this is an RPM for Fedora and we have already sorted dependencies with our pre-requisites install.<br />
<br />
<pre><br />
# rpm -ivh --nodeps ~/Downloads/zoom_x86_64.rpm<br />
</pre><br />
<br />
Example:<br />
<br />
<pre><br />
[root@localhost ~]# rpm -ivh --nodeps ~/Downloads/zoom_x86_64.rpm<br />
warning: /home/mpb/Downloads/zoom_x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 61a7c71d: NOKEY<br />
Preparing... ################################# [100%]<br />
Updating / installing...<br />
1:zoom-2.4.129780.0915-1 ################################# [100%]<br />
run post install script, action is 1...<br />
</pre><br />
<br />
<br />
= Run Zoom =<br />
<br />
Zoom gets installed as <b>/usr/bin/zoom</b>. <br />
<br />
So all we have to do is start it in the desktop as: Applications -> Internet -> Zoom.<br />
<br />
Alternatively from command line:<br />
<br />
<pre><br />
zoom<br />
</pre><br />
<br />
This will result in the splash screen being displayed:<br />
<br />
[[file:2018_11_03_Zoom_splash_screen.png]]<br />
<br />
<br />
= Register for free Zoom account =<br />
<br />
Once you have registered with Zoom for a free account you can host a meeting.<br />
<br />
Login to your account and then schedule a meeting and share the meeting details with your meeting attendees.<br />
<br />
People can join meetings either using the zoom client software or using a URL in their browser (generated by scheduling a meeting).<br />
<br />
<br />
= Login and check settings =<br />
<br />
Once you have logged in to the zoom client, you can click on <i>settings</i> (at top right) and check your speakers and microphone are working OK.<br />
<br />
[[file:2018_11_03_Zoom_post_login_screen_redacted.png]]<br />
<br />
= Updates =<br />
<br />
Since the zoom package is not ported to Mageia and not in the Mageia URPMI package lists it will not get updated when <i>urpmi --auto-update</i> is run.<br />
Until a better method is found the only way to update is from time to time re-download the zoom rpm and check if it is different from the previous downloaded zoom rpm.<br />
<br />
(update 2019_07_11)<br />
<br />
with reference to:<br />
<br />
<pre><br />
ID: CVE-2019-13450 <br />
Title: Zoom Client Remote Security Vulnerability<br />
Vendor: Zoom<br />
Description: Zoom Client is exposed to a remote security vulnerability. An attacker can leverage this issue to bypass security restrictions and perform unauthorized actions. Remote attackers can force a user to join a video call with the video camera active. This occurs because any web site can interact with the Zoom web server on localhost port 19421 or 19424. <br />
*CVSS v2 Base Score: 9.0 (AV:N/AC:M/Au:N/C:C/I:C/A:P)<br />
</pre><br />
<br />
Updated zoom client as follows:<br />
<br />
Downloaded the current version:<br />
<br />
<pre><br />
$ cd ~/Downloads/zoom/<br />
$ wget https://zoom.us/client/latest/zoom_x86_64.rpm<br />
</pre><br />
<br />
Rename download for current date:<br />
<br />
<pre><br />
$ mv zoom_x86_64.rpm zoom_x86_64_2019_07_11.rpm<br />
</pre><br />
<br />
Remove existing installed zoom package:<br />
<br />
<pre><br />
# rpm -qa | sort | grep zoom<br />
zoom-2.6.149990.1216-1<br />
<br />
# urpme zoom-2.6.149990.1216-1<br />
password:<br />
</pre><br />
<br />
Install new zoom package:<br />
<br />
<pre><br />
# rpm -ivh --nodeps /home/mpb/Downloads/zoom/zoom_x86_64_2019_07_11.rpm<br />
Preparing... ################################# [100%]<br />
Updating / installing...<br />
1:zoom-2.8.252201.0616-1 ################################# [100%]<br />
run post install script, action is 1...<br />
current home is /root<br />
Unknown media type in type 'all/all'<br />
Unknown media type in type 'all/allfiles'<br />
</pre><br />
<br />
Display newly installed package:<br />
<br />
<pre><br />
# rpm -qa | grep zoom<br />
zoom-2.8.252201.0616-1<br />
</pre><br />
<br />
= References =<br />
<br />
#Zoom https://zoom.us/</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Using_Zoom_communication_application&diff=47140Using Zoom communication application2020-04-22T18:26:27Z<p>Dtux: removed sudo commands as sudo is not supported by default in Mageia</p>
<hr />
<div>[[file:ZoomLogo.png]]<br />
<br />
<br />
= Introduction =<br />
<br />
<b>Zoom</b> is an audio and video conferencing system available for PCs and mobiles: Linux, Apple, Windows, Android, Blackberry.<br />
<br />
This page describes how to install <b>Zoom</b> in Mageia 6 Linux and later.<br />
<br />
For more information, please see: [https://support.zoom.us/hc/en-us/categories/200101697 Getting started with Zoom]<br />
<br />
Note that Zoom client is free but is not available via the Mageia packaging system.<br />
Zoom calls up to 40 minutes are free.<br />
<br />
= Benefits =<br />
<br />
<b>Zoom</b> makes it easy to have voice and video conference calls.<br />
Unlike some other VOIP systems it does not limit the number of people on a call.<br />
You can share your desktop, have text chat, and record your meetings.<br />
<br />
<br />
= Preparation =<br />
<br />
== Install pre-requisites ==<br />
<br />
As root, install packages that are needed for Zoom:<br />
<br />
32 bits installation:<br />
<pre><br />
urpmi libxcb-xtest0 # needed by Zoom<br />
</pre><br />
64 bits installation:<br />
<pre><br />
urpmi lib64xcb-xtest0 # needed by Zoom<br />
</pre><br />
(You can use sudo command if it is configured on your system)<br />
<br />
== Download Zoom ==<br />
<br />
Download from [https://zoom.us/download?os=linux Zoom's download centre].<br />
Unfortunately, there is no port for Mageia but we can use the Fedora version.<br />
<br />
From the <i>Select Linux type</i> select <b>Fedora</b>.<br />
<br />
Select correct <i>OA architecture</i> to match your system (eg 32 or 64 bit).<br />
<br />
Click on <b>Download</b><br />
<br />
Alternatively, from command line:<br />
<br />
<pre><br />
cd ~/Downloads<br />
wget https://zoom.us/client/latest/zoom_x86_64.rpm<br />
<br />
</pre><br />
<br />
Example:<br />
<br />
<pre><br />
[user@localhost Downloads]$ wget https://zoom.us/client/latest/zoom_x86_64.rpm<br />
--2018-11-03 16:05:20-- https://zoom.us/client/latest/zoom_x86_64.rpm<br />
Resolving zoom.us... 52.202.62.235<br />
Connecting to zoom.us|52.202.62.235|:443... connected.<br />
HTTP request sent, awaiting response... 302 Found<br />
Location: https://d11yldzmag5yn.cloudfront.net/prod/2.4.129780.0915/zoom_x86_64.rpm [following]<br />
--2018-11-03 16:05:21-- https://d11yldzmag5yn.cloudfront.net/prod/2.4.129780.0915/zoom_x86_64.rpm<br />
Resolving d11yldzmag5yn.cloudfront.net... 143.204.178.155, 143.204.178.138, 143.204.178.90, ...<br />
Connecting to d11yldzmag5yn.cloudfront.net|143.204.178.155|:443... connected.<br />
HTTP request sent, awaiting response... 200 OK<br />
Length: 64157086 (61M) [binary/octet-stream]<br />
Saving to: ‘zoom_x86_64.rpm’<br />
<br />
zoom_x86_64.rpm 27%[=========================> ] 16.67M 472KB/s eta 99s <br />
</pre><br />
<br />
<br />
= Install Zoom =<br />
<br />
As root, install the downloaded Zoom rpm.<br />
<br />
Note that we are using "--nodeps" because this is an RPM for Fedora and we have already sorted dependencies with our pre-requisites install.<br />
<br />
<pre><br />
rpm -ivh --nodeps ~/Downloads/zoom_x86_64.rpm<br />
</pre><br />
<br />
Example:<br />
<br />
<pre><br />
[user@localhost ~]$ rpm -ivh --nodeps ~/Downloads/zoom_x86_64.rpm<br />
warning: /home/mpb/Downloads/zoom_x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 61a7c71d: NOKEY<br />
Preparing... ################################# [100%]<br />
Updating / installing...<br />
1:zoom-2.4.129780.0915-1 ################################# [100%]<br />
run post install script, action is 1...<br />
</pre><br />
<br />
<br />
= Run Zoom =<br />
<br />
Zoom gets installed as <b>/usr/bin/zoom</b>. <br />
<br />
So all we have to do is start it in the desktop as: Applications -> Internet -> Zoom.<br />
<br />
Alternatively from command line:<br />
<br />
<pre><br />
zoom<br />
</pre><br />
<br />
This will result in the splash screen being displayed:<br />
<br />
[[file:2018_11_03_Zoom_splash_screen.png]]<br />
<br />
<br />
= Register for free Zoom account =<br />
<br />
Once you have registered with Zoom for a free account you can host a meeting.<br />
<br />
Login to your account and then schedule a meeting and share the meeting details with your meeting attendees.<br />
<br />
People can join meetings either using the zoom client software or using a URL in their browser (generated by scheduling a meeting).<br />
<br />
<br />
= Login and check settings =<br />
<br />
Once you have logged in to the zoom client, you can click on <i>settings</i> (at top right) and check your speakers and microphone are working OK.<br />
<br />
[[file:2018_11_03_Zoom_post_login_screen_redacted.png]]<br />
<br />
= Updates =<br />
<br />
Since the zoom package is not ported to Mageia and not in the Mageia URPMI package lists it will not get updated when <i>urpmi --auto-update</i> is run.<br />
Until a better method is found the only way to update is from time to time re-download the zoom rpm and check if it is different from the previous downloaded zoom rpm.<br />
<br />
(update 2019_07_11)<br />
<br />
with reference to:<br />
<br />
<pre><br />
ID: CVE-2019-13450 <br />
Title: Zoom Client Remote Security Vulnerability<br />
Vendor: Zoom<br />
Description: Zoom Client is exposed to a remote security vulnerability. An attacker can leverage this issue to bypass security restrictions and perform unauthorized actions. Remote attackers can force a user to join a video call with the video camera active. This occurs because any web site can interact with the Zoom web server on localhost port 19421 or 19424. <br />
*CVSS v2 Base Score: 9.0 (AV:N/AC:M/Au:N/C:C/I:C/A:P)<br />
</pre><br />
<br />
Updated zoom client as follows:<br />
<br />
Downloaded the current version:<br />
<br />
<pre><br />
cd ~/Downloads/zoom/<br />
wget https://zoom.us/client/latest/zoom_x86_64.rpm<br />
</pre><br />
<br />
Rename download for current date:<br />
<br />
<pre><br />
mv zoom_x86_64.rpm zoom_x86_64_2019_07_11.rpm<br />
</pre><br />
<br />
Remove existing installed zoom package:<br />
<br />
<pre><br />
$ rpm -qa | sort | grep zoom<br />
zoom-2.6.149990.1216-1<br />
<br />
$ /bin/sudo urpme zoom-2.6.149990.1216-1<br />
password:<br />
</pre><br />
<br />
Install new zoom package:<br />
<br />
<pre><br />
$ /bin/sudo rpm -ivh --nodeps /home/mpb/Downloads/zoom/zoom_x86_64_2019_07_11.rpm<br />
Preparing... ################################# [100%]<br />
Updating / installing...<br />
1:zoom-2.8.252201.0616-1 ################################# [100%]<br />
run post install script, action is 1...<br />
current home is /root<br />
Unknown media type in type 'all/all'<br />
Unknown media type in type 'all/allfiles'<br />
</pre><br />
<br />
Display newly installed package:<br />
<br />
<pre><br />
$ rpm -qa | grep zoom<br />
zoom-2.8.252201.0616-1<br />
</pre><br />
<br />
= References =<br />
<br />
#Zoom https://zoom.us/</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Consignes_du_fichier_spec_pour_RPM-fr&diff=46985Consignes du fichier spec pour RPM-fr2020-04-07T10:07:29Z<p>Dtux: ending translation</p>
<hr />
<div>{{Bandeau multi-langues-fr|[[RPM_Spec_file_policy|English]] ; [[Consignes_du_fichier_spec_pour_RPM-fr|français]] ;}}<br />
<br />
<br />
== Spec header ==<br />
<br />
L’en-tête du fichier .spec rpm contient les informations importantes sur la version, la source, le correctif, les besoins et les exigences de compilation pour les paquets que vous souhaitez construire. <br />
<br />
=== Définition des macros ===<br />
<br />
La première partie du fichier .spec doit comprendre les définitions des macros, comme illustré ci-dessous :<br />
<br />
%define major 0<br />
%define libname %mklibname aide %{major}<br />
<br />
Toutes les déclarations %define doivent être faites ici, avec des commentaires le cas échéant. Comme indiqué ci-dessus, il convient de les aligner correctement (utilisez deux largeurs de tabulation après la définition '' name '' ou la colonne 25 (troisième tabulation), car cela permet des noms de définition plus longs).<br />
<br />
{{Note-fr | Définir des macros explicites pour Name, Version et Release est inutile, car elles sont implicitement définies à partir des balises correspondantes.}}<br />
<br />
=== Name, Version et Release ===<br />
La première section doit contenir le nom standard, les étiquettes de version et de Release :<br />
Name : aide <br />
Version : 0.13.1<br />
Release: %mkrel 1<br />
<br />
Name doit être le nom en amont du projet logiciel, toujours en minuscules.<br />
<br />
=== Summary, Name, Sources et Patches ===<br />
La section suivante de l’en-tête se présenterait comme suit :<br />
<br />
Summary: Advanced Intrusion Detection Environment <br />
License: GPLv2+<br />
Group: Monitoring<br />
URL: http://sourceforge.net/projects/aide<br />
Source0: http://prdownloads.sourceforge.net/aide/%{name}-%{version}.tar.gz<br />
Source1: http://prdownloads.sourceforge.net/aide/%{name}-%{version}.tar.gz.asc<br />
Source2: aide.conf<br />
Source3: aidecheck<br />
Source4: aideupdate<br />
Source5: aideinit<br />
Source6: aideinit.8<br />
Patch0: some.patch<br />
<br />
Comme on le voit, tout est dans un ordre très linéaire :<br />
<br />
# Summary tag -- Une brève description du paquetage, sur une ligne, 79 caractères maximum, pas de point a la fin, premier caractère en majuscule et sans espace<br />
# License tag -- Se reporter à la [http://fedoraproject.org/wiki/Licensing Politique de licence]<br />
# Group tag -- [[RPM_groups_policy|Le groupe Mageia]] auquel appartient ce paquetage<br />
# URL -- La page d’accueil du paquetage<br />
# Source0... -- Les fichiers source<br />
# Patch0... -- Les correctifs<br />
<br />
Les fichiers source doivent obligatoirement commencer par '''Source0'''. Ne pas utiliser '''Source :''' et ensuite '''Source1''' : Si un paquetage n’a qu’un seul fichier source, utilisez toujours '''Source0''', car il peut ne pas toujours avoir un seul fichier source. De même pour le terme Patch0 ; commencez toujours par '''Patch0 :''', et jamais uniquement par '''Patch :'''. Si un fichier source a une URL téléchargeable dont il est issu, elle doit être incluse.<br />
<br />
{{attention-fr | Si le fichier source est mal nommé, il peut être renommé en ajoutant #/%{name}-%{version}.tar.xz à l’url SOURCE.}}<br />
<br />
Les tabulations sont ici plus courtes que les définitions, en grande partie parce que les définitions peuvent être, et le sont souvent, plus longues, alors que les balises Source, Name, etc. ne le sont généralement pas. Au lieu de passer à la colonne 25, utilisez la colonne 17 ou la deuxième tabulation. Il est important que tout soit aligné à gauche pour la « deuxième colonne » ou les valeurs des mots-clés car cela maximise la lisibilité.<br />
<br />
=== Nommage des Patchs (correctifs) ===<br />
Il existe une méthode standard pour nommer les patchs qui est documentée dans [[Consignes_empaqueter-fr#L'étiquette patch (correctif, rustine) | Consignes pour empaqueter]].<br />
<br />
=== Build Root, Requires, etc. ===<br />
La partie suivante de la norme RPM concerne les exigences de construction et c’est peut-être l’une des parties les plus fastidieuses et potentiellement incohérentes de toute norme. BuildRequires devrait être listé à chaque ligne pour une lisibilité maximale ; au lieu de regrouper plusieurs BuildRequires sur une seule ligne, utilisez une balise BuildRequires par dépendance. Tandis que RPM peut être capable de « voir » rapidement cette très longue ligne de BuildRequires, les personnes ne le peuvent pas et bien que cela puisse rendre la spécification plus longue, cela devient plus facile à lire.<br />
<br />
Buildroot peut être omis en toute sécurité, puisqu’il est automatiquement soustrait par « rpm » lors de la construction. Pour des raisons historiques, il est toujours présent dans les spécifications de Mandriva (versions antérieures à 2008.0) mais n’est pas nécessaire pour Mageia.<br />
Cela devrait rester cohérent d’une spécification à l’autre. Par exemple :<br />
<br />
BuildRequires: flex<br />
BuildRequires: glibc-devel<br />
BuildRequires: glibc-static-devel<br />
BuildRequires: mhash-devel<br />
BuildRequires: zlib-devel<br />
BuildRequires: bison<br />
<br />
=== Requires, Obsoletes, Provides, Conflicts, etc. ===<br />
Le dernier ensemble de balises dans l’en-tête RPM sont pour Requires, Obsolètes, Provides, Conflicts, etc. et elles doivent être définies au même titre que pour BuildRequires, une par ligne.<br />
Requires(pre): foo<br />
Requires(postun): foo<br />
Conflicts: tripwire<br />
Provides: AIDE+gpg<br />
Obsoletes: bar<br />
Encore une fois, gardez à l’esprit les tabulations. Si vous utilisez « Requires (postun)", vous passerez au-delà de la tabulation de la colonne 17. Dans ces cas, utilisez un espace unique.<br />
Notez également l'ordre. Au lieu de mélanger Requires et Provides, gardez-les dans un ordre distinct.<br />
<br />
# Requires, Requires (pre), Requires (post), etc. -- tous les prérequis doivent venir en premier, un par ligne<br />
# Conflicts -- tous les conflits passent au second plan<br />
# Provides et Obsoletes -- tous provides et obsoletes viennent en troisième position et peuvent être mélangées, car elles ont tendance à être étroitement liées.<br />
<br />
=== Description ===<br />
Le %description vient en dernier, et fournit la description du paquet. Les lignes doivent comporter 76 caractères.<br />
<br />
Un en-tête de spec RPM final ressemblerait à :<br />
<br />
Name : aide<br />
Version : 0.13.1<br />
Release: %mkrel 1<br />
<br />
%define major 0<br />
%define libname %mklibname aide %{major}<br />
%define somereallylongname foo<br />
<br />
Summary: Advanced Intrusion Detection Environment<br />
License: GPLv2+<br />
Group: Monitoring<br />
URL: http://sourceforge.net/projects/aide<br />
Source0: http://prdownloads.sourceforge.net/aide/%{name}-%{version}.tar.gz<br />
Source1: http://prdownloads.sourceforge.net/aide/%{name}-%{version}.tar.gz.asc<br />
Source2: aide.conf<br />
Source3: aidecheck<br />
Source4: aideupdate<br />
Source5: aideinit<br />
Source6: aideinit.8<br />
Patch0: some.patch<br />
<br />
Buildrequires: flex<br />
BuildRequires: glibc-devel<br />
BuildRequires: glibc-static-devel<br />
BuildRequires: mhash-devel<br />
BuildRequires: zlib-devel<br />
BuildRequires: bison<br />
<br />
Requires: gnupg<br />
Requires(pre): foo<br />
Requires(postun): foo<br />
Conflicts: tripwire<br />
Provides: AIDE+gpg<br />
Obsoletes: bar<br />
<br />
%description<br />
AIDE (Advanced Intrusion Detection Environment) est une alternative gratuite aux<br />
Tripwire. Il fait les mêmes choses que le Tripwire semi-libre et plus encore.<br />
C’est un outil de surveillance de l’intégrité du système de fichiers.<br />
<br />
Pour les paquetages qui créent plusieurs sous-paquets, suivez les directives ci-dessus pour chacun d’eux.<br />
<br />
=== %prep ===<br />
<br />
La section %prep suit toutes les définitions de paquets. Il devrait y avoir au moins deux lignes blanches pour séparer la fin de la dernière %description de %prep. Une simple section %prep ressemblerait à : <br />
<br />
%prep<br />
%setup -q<br />
<br />
=== Autres conventions ===<br />
<br />
Voici une liste des autres conventions qui doivent être observées dans les fichiers spec de Mageia :<br />
<br />
==== Macros système et macros définissables par l’utilisateur ====<br />
Les macros système sont celles définies dans les fichiers /etc/rpm/macros.d/ et incluent notament %_install_info, entre autres. Une macro système est quelque chose qui fait quelque chose ou calcule quelque chose. Ce n’est pas une simple définition comme %{_tmppath} qui se traduit simplement par un chemin. Les macros système doivent être écrites sans accolades, c’est-à-dire au format %_install_info et non %{_install_info}. Les macros définissables par l’utilisateur, qui incluent %{_tmppath} ou %{_bindir} doivent être écrites avec des accolades, c’est-à-dire au format %{_tmppath} et non %_tmppath. Cela facilite la lecture de la spécification car tout le monde utilisera une convention similaire pour les « accolades ».<br />
Si vous n’êtes pas sûr de savoir lequel utiliser, gardez à l’esprit qu’une macro comme %{_libdir} fournit une valeur (dans ce cas, /usr/lib), alors qu’une macro comme %_install_info exécute en fait du code de toute sorte.<br />
<br />
* Utilisez %{_libdir}, plutôt que %_libdir<br />
* Utilisez %_install_info, plutôt que %{_install_info}<br />
<br />
Utilisez systématiquement ce mécanisme et tous les fichiers de spécifications seront beaucoup plus faciles à lire.<br />
<br />
==== Macro standard ====<br />
Le fait de conserver les noms de macros cohérentes dans les fichiers de spécifications améliore la lisibilité.<br />
* %{upstream_name} lorsque le nom de la version en amont diffère de celui de la version du paquetage<br />
* %{upstream_version} lorsque la version en amont diffère de celle du paquetage<br />
<br />
==== Variables ====<br />
Les variables qui sont vraiment des définitions, comme $RPM_OPT_FLAGS ou $RPM_BUILD_ROOT ne doivent pas être utilisées. Les macros telles que %{optflags} et %{buildroot} doivent être utilisées à la place. Gardez Les variables "$*" strictement limitées aux construction liées au shell et non aux définitions basées sur RPM.<br />
<br />
==== Journal des modifications ====<br />
Jetez un oeil à notre [[Consignes_empaqueter-fr#Journal_des_modifications|Consignes pour empaqueter-Journal des modifications]]<br />
<br />
==== Gestion des sources ====<br />
Les fichiers sources ont généralement été traités en utilisant des macros %{SOURCExx}, mais ceci est inefficace pour quelques raisons simples :<br />
* pas besoin de monter et descendre dans le fichier spec pour comprendre ce qu’est %{SOURCE12}.<br />
* les fichiers sources peuvent être facilement renumérotés sans avoir à effectuer de multiples modifications<br />
Au lieu de cela, utiliser %{_sourcedir}/foo dans le fichier spec est préférable, car il rend les choses plus faciles à lire et plus faciles à travailler. Par exemple, comparez:<br />
Source12: something.pam<br />
…<br />
install -m 0644 %{SOURCE12} %{buildroot}%{_sysconfdir}/pam.d/<br />
<br />
vers:<br />
<br />
Source12: something.pam<br />
…<br />
install -m 0644 %{_sourcedir}/something.pam %{buildroot}%{_sysconfdir}/pam.d/<br />
<br />
Les fichiers sources ne doivent pas contenir les macros %{version} ou %{name} sauf s’il s’agit des fichiers sources originaux en amont.<br />
<br />
Les fichiers patch ne doivent jamais contenir les macros %{version} ou %{name}.<br />
<br />
==== Resources ====<br />
<br />
* Fedora's guidelines:<br />
** How to create a GNU Hello RPM package;<br />
** How to create an RPM package;<br />
* Packaging guidelines.<br />
** Mageia RPM HOWTO - the Mageia RPM HOWTO (contains good information and should be seen as supplemental to this policy)<br />
<br />
==== Changements et suggestions possibles en fonction de la proposition ====<br />
<br />
Cette section détaille certaines modifications techniques qui ne font pas partie de la proposition, mais qui devront peut-être être mises en œuvre pour que la proposition soit la plus efficace possible :<br />
*<br />
<br />
==== Les choses obsolètes, devraient être jetées là où on les voit ====<br />
<br />
Le <tt>mgagnome</tt> a une sous-commande <tt>clean-spec</tt> pour vous faciliter cela.<br />
<br />
* <tt>%clean</tt> section, est maintenant réalisée automatiquement par RPM lui-même<br />
* <tt>rm -rf %{buildroot}</tt> n’est plus nécessaire explicitement dans <tt>%install</tt> puisque cela si fait automatiquement<br />
* <tt>BuildRoot:</tt> définition<br />
* <tt>%defattr(-,root,root)</tt> est inutile, doit être retiré. Utilisez <tt>%defattr</tt> uniquement si vous voulez vraiment changer les permissions par défaut en amont. De tous les fichiers suivants après la macro <tt>%defattr</tt>. C’est rarement nécessaire.<br />
* changer <tt>%py_requires</tt> en <tt>BuildRequires: python</tt><br />
* changer <tt>%py_requires -d</tt> en <tt>BuildRequires: python</tt> et <tt>BuildRequires: python-devel</tt> <br />
* supprimer des variables telles que name, version, release si elles ne sont pas définies de manière conditionnelle. Par exemple :<br />
# fichier de spécifications avec des variables inutiles pour name/version/release<br />
%define name modulename<br />
%define version 1.2.3<br />
%define release %mkrel 1<br />
<br />
Name: %name<br />
Version: %version<br />
Release: %release<br />
<br />
# Procédez comme suit à la place:<br />
Name: modulename<br />
Version: 1.2.3<br />
Release: %mkrel 1<br />
<br />
== Voir également ==<br />
<br />
* [[Mageia-Mandriva-Fedora-SUSE RPM Spec Lingo]] - a lingo for the equivalents of the various RPM spec macros in the various distributions.<br />
<br />
[[Category:Contributors]]<br />
[[Category:Packaging]]<br />
[[Category:Policies]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=How_to_create_an_update_advisory&diff=46337How to create an update advisory2020-02-03T18:53:23Z<p>Dtux: mgaadv initqaconf need ~/.mga-advisories dir</p>
<hr />
<div>[[Category:QA]]<br />
Updates advisories are managed using [[Mgaadv|mgaadv]] and SVN. This page explains how to set up and configure a system, and create or amend an update advisory.<br />
<br />
== What are Advisories? ==<br />
<br />
Any proposed package update needs to include an advisory, which is the information which<br />
will be included in the update announcement that is intended for users and system administrators,<br />
describing the issues that have been fixed by the update as well as any other steps they may need to take<br />
besides just installing the updated packages. Advisories will usually (or always, in the case of security<br />
updates) include references, which are links to web pages which provide even more information about<br />
the issues. The advisory will first identify the name of the source package(s) for which security issues<br />
are being fixed. Then it will include descriptions of the security vulnerabilities, including CVE<br />
identifiers, if applicable. Information that users or system administrators may need to know about the<br />
update follows next. Finally, the references are listed. Also, the names and versions of the updated<br />
packages need to be listed in the bug report so that the QA Team knows what needs to be tested and the<br />
sysadmins will know which packages need to be pushed as updates once the testing has completed.<br />
<br />
The descriptions of the security issues usually follow a format that is similar to that used on the<br />
CVE website, which identifies the affected software and version range, the type of security<br />
vulnerability, and the affected portion of the software's functionality or code. The type of vulnerability<br />
can include the type of software flaw (double-free, use-after-free, buffer over-read, buffer overflow,<br />
integer overflow, null pointer dereference, divide-by-zero, reachable assertion, etc) and the impact of the<br />
issue (denial of service, information disclosure, remote code execution, privilege escalation, etc). These<br />
descriptions can be taken from the CVE entries themselves, other vendors' advisories, other vendors' bug<br />
or security tracker entries, or upstream or third-party advisories or announcements for the issues.<br />
Sometimes we have to piece the available information together and write the descriptions ourselves. In<br />
cases where very little or no information about the vulnerabilities is available, the advisory is written in<br />
a more generic manner, usually just indicating that the package has been updated to a certain newer<br />
version and that it fixes bugs and/or security issues.<br />
<br />
The references will include links to the CVE entries on the CVE website; other vendors'<br />
advisories, especially if they are the source of information that we used to write our descriptions or fix<br />
packages, or if they include useful additional information; upstream advisories, and third-party<br />
advisories if appropriate. If we updated the software to a newer version, we also include links to the<br />
release announcements, release notes, or change logs for the new versions if possible.<br />
<br />
<BR><br />
To see what they look like, the current on-line list of them is at http://svnweb.mageia.org/advisories/ ; GoTo a recent page and click the ''Rev'' column to see the actual current text of individual advisories. Equally, once you have set up the advisory system on your box,<br />
$ cd ~/mageia-advisories/advisories<br />
$ ls<br />
$ less <filename><br />
will show them locally. (The extra final ID... line is not our affair). Here is a typical security example:<br />
<pre><br />
type: security<br />
subject: Updated python-yaml packages fix security vulnerability<br />
CVE:<br />
- CVE-2014-9130<br />
src:<br />
4:<br />
core:<br />
- python-yaml-3.10-5.1.mga4<br />
description: |<br />
Jonathan Gray and Stanislaw Pitucha found an assertion failure in the way<br />
wrapped strings are parsed in Python-YAML, a YAML parser and emitter for<br />
Python. An attacker able to load specially crafted YAML input into an<br />
application using python-yaml could cause the application to crash.<br />
<br />
This issue is similar to CVE-2014-9130, but the assertion was independently<br />
implemented in Python-YAML.<br />
references:<br />
- https://bugs.mageia.org/show_bug.cgi?id=14917<br />
- http://advisories.mageia.org/MGASA-2014-0508.html<br />
- https://www.debian.org/security/2014/dsa-3115<br />
ID: MGASA-2015-0004<br />
</pre><br />
<br />
= SVN access =<br />
<br />
As a prelude, install SVN.<BR><br />
To be able to add or edit advisories, you need to have commit access to the svn server. So you must be in the [http://people.mageia.org/g/mga-packagers-committers.html packagers] or [http://people.mageia.org/g/mga-qa.html QA] ldap group. This is done by sysadmins.<br />
The steps shown below should be sufficient, and not require reference to [[Packagers_ssh]].<br />
<br />
== Creating an SSH key ==<br />
<br />
First of all you will need to create an RSA SSH authentication key.<br />
Install the ''openssh'' package if it is not already installed.<br />
<br />
* Do it as your normal local user, no need for root.<br />
* Give a passphrase. There is no way to recover a lost passphrase, so make sure to select one that is both strong and easily remembered by you.<br />
* Call the key 'mageia' rather than the default 'id_rsa'. It separates it from your regular ssh key which you might want to use elsewhere for passwordless logins etc. e.g.<br />
$ ssh-keygen -t rsa -f .ssh/mageia<br />
This will generate 2 files:<BR><br />
1) ''~/.ssh/mageia'', which contains the protocol version 2 RSA authentication identity of the user; the ''private'' key.<br />
This file must not be readable for other users, as it will be ignored by ssh-agent if this condition is not satisfied:<br />
$ chmod 600 ~/.ssh/mageia<br />
2) ''~/.ssh/mageia.pub'', which contains the protocol version 2 RSA ''public'' key for authentication.<br />
It is this file's ''contents'' that you upload.<br />
<br />
== Uploading your SSH key ==<br />
<br />
You need to upload your public SSH key to the mageia server before you are allowed to connect to the SVN. This is done through https://identity.mageia.org/.<br />
When connected with your account, add the '''attribute''' ''sshPublicKey'' with the content of your public key ''~/.ssh/mageia.pub''.<br />
<br />
Once your SSH key has been added, it can take up to ten minutes for the key to be active on the server.<br />
<br />
To check that your ssh key has been correctly uploaded, try to connect with ssh to ''svn.mageia.org''<br />
$ ssh <MageiaUsername>@svn.mageia.org :<br />
If your ssh key is accepted, you should see something like the following messages :-<br />
Enter passphrase for key '/home/<mylocaluser>/.ssh/mageia':<br />
You tried to execute:<br />
Sorry, you are not allowed to execute that command.<br />
You are member of the following groups :<br />
mga-users mga-shell_access mga-board mga-council mga-qa<br />
mga-qa-committers mga-iso-testers<br />
Connection to svn.mageia.org closed.<br />
This means that your ssh key was correctly uploaded to the server.<br />
<br />
The following command should then work :<br />
$ svn ls svn+ssh://svn.mageia.org/svn/advisories/<br />
<br />
It is recommended to add a config for ssh, in ~/.ssh, so that it always automatically associates the MageiaUser with svn.mageia.org.<br />
Create ''~/.ssh/config'' with this inside it:<br />
<pre><br />
Host svn.mageia.org<br />
IdentityFile /home/<localUser>/.ssh/mageia<br />
Hostname svn.mageia.org<br />
User lewyssmith<br />
Compression yes<br />
CompressionLevel 9<br />
ServerAliveInterval 120<br />
ForwardX11 no<br />
ForwardAgent yes<br />
<br />
Host *<br />
ForwardX11 yes<br />
ForwardAgent yes<br />
</pre><br />
The file should be chmod 600 <localuser> so it is only accessible to you, same as<br />
for the private keys, or ssh will complain.<br />
<br />
You can test it with the command you did before and leave the remote<br />
username off this time. It *should* be automatic to use it for that host<br />
now. eg:<br />
<br />
$ ssh svn.mageia.org<br />
Enter passphrase for key '/home/mylocaluser/.ssh/mageia':<br />
You tried to execute:<br />
Sorry, you are not allowed to execute that command.<br />
You are member of the following groups :<br />
mga-users mga-shell_access mga-board mga-council mga-qa<br />
mga-qa-committers mga-iso-testers<br />
Connection to svn.mageia.org closed.<br />
<br />
= Advisories Installation & Configuration =<br />
<br />
==Installation==<br />
First create the ''advisories'' directory in advance, to prevent mgaadv initqaconf from failing. It will need to be able to accommodate perhaps 50Mb.<br />
<pre><br />
mkdir ~/mageia-advisories/<br />
mkdir ~/.mga-advisories<br />
</pre><br />
Or it can be put anywhere and use a symlink in the home directory pointing to the chosen location:<br />
$ mkdir -p <path-to-where-you-want-the-advisories/><br />
$ ln -s <actual-path> ~/mageia-advisories<br />
<br />
Then install the package ''mga-advisories'' :<br />
# urpmi mga-advisories<br />
<br />
== Configuration ==<br />
<br />
Configuration of ''mgaadv'' is done using the command ''mgaadv initqaconf'' :<br />
<pre><br />
$ mgaadv initqaconf<br />
</pre><br />
<br />
This should open a text editor with something like this :<br />
<pre><br />
---<br />
advisories_dir: /home/boklm/mageia-advisories/advisories<br />
mode: qa<br />
out_dir: /home/boklm/mageia-advisories/html<br />
status_dir: /home/boklm/mageia-advisories/status<br />
</pre><br />
You can change this if you you want :<br />
* advisories_dir: the directory where advisories infos are (a checkout of the advisories svn repository)<br />
* out_dir: the directory where html pages will be saved<br />
* status_dir: directory where status of the advisories is saved<br />
After saving the file and closing the text editor it should checkout the advisories svn in the ''advisories_dir'' directory.<br />
<BR><br />
If you want to edit the configuration later, the file is ''.mga-advisories/mga-advisories.conf'' in your home directory.<br />
<br />
By default it will save advisories in the directory ''mageia-advisories'' under your home directory; typically:<br />
$ tree -d mageia-advisories<br />
mageia-advisories<br />
├── advisories<br />
├── html<br />
└── status<br />
It is the 'advisories' sub-directory that actually contains them (or will).<br />
<br />
You may want to subscribe to ''qa-commits'' mailing list to see e-mails<br />
detailing commits in our repository, but this will create a lot of e-mail traffic. You will also get occasional emails<br />
when they commit mageiasync updates.<br />
https://ml.mageia.org/l/info/qa-commits<br />
<br />
===Advisory template===<br />
<br />
The guts of creating advisories is an editing template, pre-formatted and primed with key information. This is at<br />
''/usr/share/mga-advisories/tmpl/newadvisory.adv'', and issued thus:<br />
<pre><br />
type: [% type %]<br />
[% IF type == 'security' -%]<br />
subject: Updated [% name %] packages fix security vulnerability<br />
CVE:<br />
- CVE-2014-XXXX<br />
[% ELSE -%]<br />
subject: Updated [% name %] packages fix [something]<br />
[% END -%]<br />
src:<br />
5:<br />
core:<br />
- [% name %]-1.0-1.mga5<br />
description: |<br />
Advisory text to describe the update.<br />
Wrap lines at ~75 chars.<br />
references:<br />
- https://bugs.mageia.org/show_bug.cgi?id=[% bugnum %]<br />
</pre><br />
It is worth adapting it to your personal preferences, ''preserving the exact formatting'' e.g<br />
* If we are currently maintaining just one Mageia release, put that after 'src:'.<br />
* If we are currently maintaining 2 releases, put in a 'src' stanza for each one. It is easier to delete the unused stanza (an update for just one release), than to duplicate and modify it. It also serves as a reminder about updates to two releases, e.g.<br />
<pre><br />
...<br />
src:<br />
5:<br />
core:<br />
- [% name %]-1.0-1.mga5<br />
6:<br />
core:<br />
- [% name %]-1.0-1.mga6<br />
description: |<br />
...<br />
</pre><br />
<br />
= Creating (or modifying) an Advisory =<br />
<br />
== Overview ==<br />
The process of uploading a new advisory involves first changing into<br />
~/mageia-advisories/advisories, syncing your collection of files with<br />
the server (svn up) then creating the advisory (eg. mgaadv new security<br />
17780 graphite2), copy/paste info from bugzilla into the editor it opens<br />
& format it to YAML indents and 75ish characters line wrap, save the<br />
file and exit the editor. That will have created a local .adv file (eg.<br />
17780.adv) in which you then tell svn to track (svn add 17780.adv) and do a<br />
quick check with a diff (svn diff), which shows differences local<br />
compared to the server, to make sure it's the only thing different from<br />
the server and as a last check before uploading. Then if all is OK commit<br />
it, or check it in, to the server (svn ci -m "Add sec adv 5 graphite2<br />
mga#17780").<br />
<br />
===Always start===<br />
* Be logged into the bug in Bugzilla:<br />
- it has all the necessary information, normally in just one Comment.<BR><br />
- so that you can update the bug to note the advisory..<br />
* Put yourself into your local advisories directory, and synchronise it with the the remote one:<br />
$ cd ~/mageia-advisories/advisories/<br />
$ svn up<br />
<br />
== Create a new Advisory ==<br />
<br />
Creating a new advisory is done with the command ''mgaadv new'' :<br />
<pre><br />
$ mgaadv new [type] [bugnum] [name]<br />
</pre><br />
<br />
* Replace [type] with the type of advisory (''security'' or ''bugfix'').<br />
* Replace [bugnum] with the bugzilla number of the bug used to track the update.<br />
* Replace [name] with the basic name of the SRPM, before -version and .src.rpm. Watch out for SRPM names which include '-'.<BR><br />
If >1 SRPM is involved, just cite the main one and adapt subsequent editing accordingly.<br />
<br />
It should open a text editor with something like this :<br />
<pre><br />
type: bugfix<br />
subject: Updated [package] package fixes [something]<br />
CVE:<br />
- CVE-xxxx-yyyy<br />
src:<br />
2:<br />
core:<br />
- something-1.0-1.mga2<br />
3:<br />
core:<br />
- something-1.0-1.mga3<br />
description: |<br />
Advisory text to describe the update.<br />
Wrap lines at ~75 chars.<br />
references:<br />
- https://bugs.mageia.org/show_bug.cgi?id=12345<br />
</pre><br />
<br />
The format of the file is YAML (see the [http://en.wikipedia.org/wiki/YAML wikipedia page] for basic syntax). The format is very precise, and getting it exactly right constitutes the bulk of the work.<br />
<BR>- Use '''spaces''' rather than tabs to indent.<br />
<BR>- Leave a '''blank line''', without a space in it, at the end of the advisory file. SVN needs this for some<br />
reason. If you forget, you will see a message about it in svn diff and the commit email.<br />
<br />
You should edit the following infos :<br />
* ''subject'': a one line summary of the advisory. This is already filled in. For security advisories, a common adaptation is to pluralise vulnerability/ies. <BR><br />
- [package] is the basic SRPM name only.<BR><br />
- [something] is a minimal summary of what is fixed for bugfixes.<br />
<br />
* ''CVE'': if it is a ''security'' update, a list of CVE identifiers, one per line. This is often the trickiest editing job; the time to do a security advisory depends largely on the number of CVEs. They can be given in:<BR><br />
- The bug title.<BR><br />
- The Advisory description, per paragraph.<BR><br />
- The Advisory description as a list at the end.<BR><br />
- The 'references' CVE URLs, the end of these.<BR><br />
If there are just a few, it is easiest to pick them out individually from the description or bug title.<BR><br />
If the description ends with a list of CVEs, copy them en gros from there and split them up.<BR><br />
If there are many scattered throughout the description, the bug 'references' normally contain a contiguous list of all CVE URLs. Easiest then is to copy this list en gros, and edit each line to leave just the terminal CVE.<BR><br />
It is worth cross-checking the bug CVEs between the Description and References URL list, to make sure one is not omitted (count), or that a number is not inconsistent.<br />
<br />
* ''src'': the list of SRPMs, in a tree of the mageia ''release'' and ''media'' as shown. This is nominally filled in, *do* correct it. '''Omit''' the '.src.rpm' suffixes. Most Advisory errors arise from the source tree not being right.<br />
Note that:<BR><br />
- if the update relates to ''nonfree'' or ''tainted'' SRPMs, rather than ''core'', adapt the 'src' tree appropriately. Rarely, an update can include both 'core' and 'tainted' SRPMs, and hence both trees under the release.<BR><br />
- all SRPMs include after the version the Mageia release 'mgax' which must correspond with the release tree.<BR><br />
- for ''core'' srpms, the name ends with the release '.mgax'.<BR><br />
<pre><br />
src:<br />
6:<br />
core:<br />
- srpm-1.0-1.mga6<br />
</pre><br />
<br />
- for ''nonfree'' or ''tainted'' SRPMs the name ends with the ''media'', which must correspond with the media tree, e.g.<br />
<pre><br />
src:<br />
5:<br />
nonfree:<br />
- srpm-1.0-1.mga5.nonfree<br />
6:<br />
tainted:<br />
- srpm-1.0-1.mga6.tainted<br />
</pre><br />
<br />
* ''description'': a longer description of the update. Text should be wrapped at '''<= 75 chars''' (Kwrite is the editor normally invoked, which shows the column number). Preserve the 2 leading spaces on non-blank lines (Kwrite's auto-indent helps here).<br />
<br />
* ''references'': a list of URLs. The references have the '''bug''' as the first link; that is how it starts out, so just add the extra ref's below it. ''Do *not* add CVE URLs'' here, as they are added automatically in the advisory. Just copy the contiguous list of 'reference' URLs. Be careful about the final ''blank'' line if auto-indent adds spaces; check that the cursor moves immediately from the end of the last reference URL to the ''start'' of the next [last] line.<br />
<br />
When you finished editing the advisory, simply ''Save'' the file, quit the editor. Its name is [bugnum].adv in the advisories directory. Beware editors that automatically create a backup copy of the file [bugnum].adv~ ; these are a nuisance.<br />
<br />
===Add the new advisory to SVN===<br />
<br />
Then add the new file to SVN:<br />
<pre><br />
$ svn add <bugnum>.adv<br />
A <bugnum>.adv<br />
</pre><br />
Finish as in ''Final Steps'' below.<br />
<br />
== Modifying an existing advisory ==<br />
<br />
This will already exist in .../advisories/<bugnum>.adv . Changes are purely contextual: to correct a malformed advisory, revise the text, add CVEs or references etc. Simply edit your local copy according to the rules above, then finish as follows.<br />
<br />
== Final steps ==<br />
<br />
* Review the end result, and changes, before you commit:<br />
<pre><br />
$ less <bugnum>.adv<br />
$ svn diff<br />
</pre><br />
Use of 'less' gives a nice clean view of what the advisory looks like. It will NOT show the final blank line<BR><br />
'svn diff' should show (after the 1st line) entirely '+' lines for a new advisory, changed lines for an amended one. It will warn "\ No newline at end of file" if that is the case.<BR><br />
If you see anything wrong, edit the advisory to correct it; then repeat the commands above.<br />
<br />
* Once satisfied that the Advisory is correct, ''commit'' it thus (ci = check in):<br />
$ svn ci -m '<commit message>'<br />
Adding xxxx.adv<br />
Transmitting file data .<br />
Committed revision xxx.<br />
where 'commit message' is free format, conventionally something like: <BR><br />
[Add|Correct|Update] [security|bugfix] advisory [MageiaRelease(s)] [short SRPM name(s)] mga#[bugnum]<br />
<br />
For example (assuming it's an advisory for the 'xmoto' package with bug number 12345):<br />
<pre><br />
[New advisory for a Mageia 5 security update]<br />
$ svn ci -m 'Add security advisory M5 xmoto mga#12345'<br />
<br />
[New bugfix advisory Mageia4 & Mageia5]<br />
$ svn ci -m 'Add bugfix advisory M4/M5 xmoto mga#12345'<br />
<br />
[Corrected security update Mageia4 advisory]<br />
$ svn ci -m 'Correct security advisory M4 xmoto mga#12345'<br />
<br />
[Revised advisory for Mageia4 & 5 bugfix update]<br />
$ svn ci -m 'Update bugfix advisory M4/M5 xmoto mga#12345'<br />
</pre><br />
<br />
* Once the advisory is commited, update the bug:-<BR><br />
- Add the word 'advisory' to the Whiteboard;<BR><br />
- UNtick the 'Add me to the CC list' (unless you really want to receive all subsequent bug comments & changes);<BR><br />
- Possibly add a Comment that the advisory is done, and from which Comment(s) it was taken. This should not be necessary in simple cases: Bugzilla automatically notes the Whiteboard change.<br />
<br />
===Other commands===<br />
$ mgaadv list<br />
Lists ''all'' advisories, with their IDs. It takes a long time.<br />
$ mgaadv show <advisoryID><br />
shows a text version of the advisory, but in a different format. It also takes a long time.<br />
<br />
== Testing the advisory ==<br />
This is ''very'' optional. You can use ''mgaadv mksite'' command to generate the advisories web site to check that your new advisory is displayed correctly:<br />
<pre><br />
$ mgaadv mksite<br />
</pre><br />
Then open a web browser to view the ''out_dir'' directory defined in mgaadv configuration, conventionally /home/<localuser>/mageia-advisories/html .<br />
<br />
== Publishing advisory ==<br />
This is the final step, once the commited Advisory is in place and deemed correct.<BR><br />
Publishing is done by assigning an ID to an advisory. In the future, it is planned that ''mga-advisories'' moves the updated packages to the updates repository automatically, but it is not ready yet. For now, this part still needs to be done by the sysadmin team.<br />
<br />
= Adding old advisories =<br />
If someone has a lot of time, it's possible to add old advisories from https://wiki.mageia.org/en/Support/Advisories/.<br />
<br />
To add already published advisories, the process is the same, with the following differences in the advisory file :<br />
<br />
* set the ''ID'' manually<br />
* set the ''no_mail'' option so that an email is not sent for this already published advisory<br />
* set ''pubtime'' to the publication time of the update, as epoch value<br />
<br />
Example :<br />
<pre><br />
no_mail: 1<br />
pubtime: 1339329600<br />
ID: MGASA-2012-0112<br />
</pre><br />
<br />
To know the epoch value of a date, you can use the following command (in this example for 2012-06-10) :<br />
<pre><br />
$ date +"%s" -d '2012-06-10 13:00'<br />
</pre></div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Paris_Open_Source_Summit_2019&diff=45533Paris Open Source Summit 20192019-10-14T09:50:58Z<p>Dtux: Created page with "Category:Events Category:Open_Source Category:2019 = Contact = * Lebarhon * Magnux77 * Dtux * BAud == Comment == * IT professionals only - Salon réservé aux pr..."</p>
<hr />
<div>[[Category:Events]] [[Category:Open_Source]] [[Category:2019]]<br />
<br />
= Contact =<br />
* Lebarhon<br />
* Magnux77<br />
* Dtux<br />
* BAud<br />
<br />
== Comment ==<br />
* IT professionals only - Salon réservé aux professionnels mais ouvert au grand public tout de même<br />
* Previously Solutions Linux / Open Source merged with Open World Forum - Ancien salon Solutions Linux / Open Source fusionné avec Open World Forum.<br />
<br />
==Who's coming - Qui vient ?==<br />
Let us know if you can come and see us, just edit below, we'll be happy to see you, no obligation anyway.<br />
<br />
Serez vous là ? Nous serions heureux de vous rencontrer, faites le nous savoir en vous inscrivant ci-dessous, aucune obligation cependant.<br />
* <br />
* <br />
*<br />
<br />
= Informations =<br />
<br />
== Opening Schedule - Jours et horaires d'ouverture ==<br />
* Mardi/Tuesday 10 and mercredi/Wendesday 11 décembre/December : 09H00 à 18H00<br />
<br />
== Localization - Lieu ==<br />
* Dock Pullmann Plaine Saint-Denis (France) - Metro : ligne 12 Front Populaire<br />
<br />
== Access - Accès ==<br />
* [http://www.opensourcesummit.paris/Informations+pratiques_154_160.html Informations]<br />
<br />
== Planning ==<br />
<br />
{| align=center cellpadding="5%" cellpadding="5%" cellspacing="0" class="wikitable" width=100%<br />
! rowspan="2"|Nom - Nickname - Mail<br />
! colspan="2"|<br />
! colspan="2"|<br />
|- <br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
|-<br />
|-<br />
|-<br />
|-<br />
| magnux77<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
|-<br />
| dtux<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
|-<br />
| ?<br />
| ?<br />
| ?<br />
| ?<br />
| ?<br />
|-<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
== Equipment - Matériel ==<br />
* [http://www.opensourcesummit.paris/preinscription.html?code=bandeauhaut&lg=fr Badges] to request (for free) - Faire les demandes de [http://www.opensourcesummit.paris/preinscription.html?code=bandeauhaut&lg=fr badge] (gratuit)<br />
* Nappe, kakemono, rallonge électrique.<br />
* goodies : CD/DVD/USB key, T-shirts, stickers (meta-key + powered by Mageia + GNU/Linux Mageia), pen in wood with mageia name & logo<br />
<br />
<br />
...<br />
<br />
<br />
== Debriefing ==</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Paris_Open_Source_Summit_2018&diff=45532Paris Open Source Summit 20182019-10-14T09:38:23Z<p>Dtux: bad year in tag</p>
<hr />
<div>[[Category:Events]] [[Category:Open_Source]] [[Category:2018]]<br />
<br />
= Contact =<br />
* Lebarhon<br />
* Magnux77<br />
* Dtux<br />
* BAud<br />
<br />
== Comment ==<br />
* IT professionals only - Salon réservé aux professionnels mais ouvert au grand public tout de même<br />
* Previously Solutions Linux / Open Source merged with Open World Forum - Ancien salon Solutions Linux / Open Source fusionné avec Open World Forum.<br />
<br />
==Who's coming - Qui vient ?==<br />
Let us know if you can come and see us, just edit below, we'll be happy to see you, no obligation anyway.<br />
<br />
Serez vous là ? Nous serions heureux de vous rencontrer, faites le nous savoir en vous inscrivant ci-dessous, aucune obligation cependant.<br />
* <br />
* <br />
*<br />
<br />
= Informations =<br />
<br />
== Opening Schedule - Jours et horaires d'ouverture ==<br />
* Mercredi/Wednesday 5 and jeudi/Thursday 6 décembre/December : 09H00 à 19H00<br />
<br />
== Localization - Lieu ==<br />
* Dock Pullmann Plaine Saint-Denis (France) - Metro : ligne 12 Front Populaire<br />
<br />
== Access - Accès ==<br />
* [http://www.opensourcesummit.paris//Informations+pratiques_154_160.html Informations]<br />
<br />
== Planning ==<br />
<br />
{| align=center cellpadding="5%" cellpadding="5%" cellspacing="0" class="wikitable" width=100%<br />
! rowspan="2"|Nom - Nickname - Mail<br />
! colspan="2"|<br />
! colspan="2"|<br />
|- <br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
|-<br />
|-<br />
|-<br />
| Lebarhon<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
| align=center|Jusqu'à 17h00<br />
|-<br />
| magnux77<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
|-<br />
| dtux<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
| align=center|x<br />
|-<br />
| ?<br />
| ?<br />
| ?<br />
| ?<br />
| ?<br />
|-<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|-<br />
| -<br />
| -<br />
| -<br />
| -<br />
| -<br />
|}<br />
<br />
== Equipment - Matériel ==<br />
* [http://www.opensourcesummit.paris/preinscription.html?code=bandeauhaut&lg=fr Badges] to request (for free) - Faire les demandes de [http://www.opensourcesummit.paris/preinscription.html?code=bandeauhaut&lg=fr badge] (gratuit)<br />
* Nappe, kakemono <br />
* goodies : CD/DVD/USB key, T-shirts, stickers (meta-key + powered by Mageia + GNU/Linux Mageia), pen in wood with mageia name & logo<br />
<br />
<br />
...<br />
<br />
<br />
== Debriefing ==<br />
We were 4 at the stand, between our friends Debian GNU/Linux and Oisux (a French LUG, having the magia logo on their kakemono), in front of an alley which enhanced our visibility.<br />
<br />
We've had many interesting discussions with users, with people from IBM or DGA (French Army), some knowing us from Mandrake or Mandriva years, some using our distribution day to day.<br />
<br />
A demo of Mageia working on ARM Raspberry Pi thanks to DTux<.<br />
<br />
As usual, the wifi was a pity : do not count on having network, just bring your own mirror on hard disk for such events :-)<br />
<br />
We renewed our subscription to April.org thanks to ennael< :-) (and found some bitcoins remaining that should let our association being self-sustainable for the coming years.<br />
<br />
Our VIP badges enabled us to benefit from morning coffea, fruit-juice and some appetitizers to sustain ourselves.<br />
<br />
== Log - Suivi ==<br />
* Volunteers are welcome - Les volontaires sont les bienvenus.<br />
* Some flyers printed: http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7A.pdf source : http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7.odt (100 should be suficient)<br />
* Announcement on Mageia blog ? - Une annonce sur le blog Mageia ?<br />
* stickers : http://download.tuxfamily.org/cauldron/mageia/logo/</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Archive:Mageia_7_Errata-fr&diff=45331Archive:Mageia 7 Errata-fr2019-07-24T13:47:28Z<p>Dtux: added PMB issue</p>
<hr />
<div>{{bandeau multi-langues-fr|[[Mageia_7_Errata-de|Deutsch]] ; [[Mageia_7_Errata|English]] ; [[Erratas de Mageia 7|Español]] ; [[Mageia_7_Errata-fr|Français]] }}<br />
<!--'''This information is available in other languages''':<br /><br />
<br />
* [https://wiki.mageia.org/de/Mageia_7_Errata Deutsch]<br />
* [[Mageia_7_Errata|English]]<br />
* [[Erratas_de_Mageia_7|Español]]<br />
* [[Mageia_7_Errata-fr|Français]]--><br />
<br />
<br />
= Mageia 7 =<br />
Notez que nous continuons d’ajouter des problèmes de la liste [https://bugs.mageia.org/buglist.cgi?keywords=FOR_ERRATA7%2C%20&keywords_type=allwords&order=Importance&query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED des bogues dans notre Bugzilla qui nécessitent encore une entrée d’errata pour Mageia 7]<br />
<br />
<br />
==Amorçage==<br />
Il a été constaté que sur certains matériels, le système s’arrêtait après le choix de la ligne d’amorçage dans Grub, avec un rectangle noir inséré dans le fond d’écran de Grub. La cause suspectée est le microcode Intel en lien avec le BIOS, le microcode étant chargé pour faire fonctionner le microprocesseur Intel i7 de dernière génération. Les modèles ASUS UX333, UX433 et UX533 sont identifiés comme présentant ce problème. Un moyen de contournement est d’ajouter {{cmd|dis_ucode_ldr}} sur la ligne d’amorçage du noyau dans Grub. Mi-juin 2019, des mises à jour de BIOS permettent de résoudre le problème. Voir [https://bugs.mageia.org/show_bug.cgi?id=24979 mga#24979].<br />
<br />
=== LVM et/ou LUKS avec des anciens udisks ===<br />
Avant de mettre à jour un système utilisant LVM et/ou LUKS depuis mga6, les udisks doivent être désinstallés manuellement. Parce que si udisks est installé au démarrage de Mageia 7, il vous laissera tomber au moment du débogage du shell. Si cela se produit, dans le shell, appuyez sur {{keypress|Ctrl}}-{{keypress|D}} et il démarrera normalement et vous pourrez effectuer la désinstallation. Consultez [https://bugs.mageia.org/show_bug.cgi?id=24949 mga#24949].<br />
<br />
=== GRUB ne réussit pas à démarrer avec le système de fichiers JFS ===<br />
Si vous utilisez la version précédente de GRUB ''et'' le système de fichiers JFS, vous devez passer à GRUB2 avant de mettre à niveau vers Mageia 7, voir [https://bugs.mageia.org/show_bug.cgi?id=25009 mga#25009].<br />
<br />
=== 3 formes rectangulaires avec point d’interrogation lors du démarrage ===<br />
Après avoir sélectionné pour démarrer Mageia dans le menu grub2, le démarrage présente un écran gris avec trois formes rectangulaires avec des points d’interrogation dans celles-ci. Le système démarre normalement et passe à l’écran de connexion standard ou à la connexion automatique selon la configuration. Cela se produit si vous utilisez le pilote nvidia340 (et très probablement, tout autre pilote qui ne prend pas en charge la gestion des modes d’affichage par le noyau). Bug [https://bugs.mageia.org/show_bug.cgi?id=19642#c36 mga#19642 comment 36] contient des solutions de contournement possibles.<br />
<br />
== Médias Live ==<br />
<br />
=== GNOME ===<br />
<br />
1) par défaut GNOME utilise le serveur d’affichage Wayland. Wayland n’est pas encore complètement mature, et peut ne pas fonctionner correctement sur certains matériels. Normalement GNOME devrait automatiquement basculer sur le serveur d’affichage X.org si Wayland ne démarre pas, mais dans certains cas, cela ne se produit pas. Si le bureau GNOME ne réussit pas à démarrer après avoir terminé la sélection de votre langue principale et de votre pays, ou si vous rencontrez des problèmes d’affichage, vous pouvez essayer de forcer GNOME à utiliser le serveur d’affichage X.org en ajoutant ''nowayland'' dans les options de démarrage dans le menu initial d’amorçage ({{Keypress-fr|F6}} pour l’amorçage classique, « {{Keypress-fr|e}} » si vous utilisez l’amorçage UEFI).<br />
<br />
2) Par défaut, le service NetworkManager est activé à la place de l’ancien service de gestion de réseau draknetcenter. L’aspect positif, est que l’applet NetworkManager intégré au bureau GNOME fonctionne ; l’aspect négatif, est que la tentative de configuration de votre connexion réseau via le MCC ne fonctionnera pas. Utilisez le menu déroulant accessible depuis le coin supérieur droit du bureau GNOME pour effectuer toute configuration du réseau. Pour les connexions filaires, le réseau est généralement configuré automatiquement et vous n’avez pas besoin de faire quoi que ce soit. Pour les réseaux sans fil, vous aurez besoin de sélectionner un point d’accès et, s’il est protégé par un mot de passe, de saisir celui-ci.<br />
<br />
=== Cartes graphiques qui ne fonctionnent pas ===<br />
<br />
Certaines cartes graphiques ne fonctionnent pas correctement lorsque vous utilisez le fichier xorg.conf qui est créé par harddrake lors du démarrage du système Live. Si vous n’avez pas d’affichage graphique à la fin du cycle de démarrage, essayez d’ajouter ''noxorgconf'' dans les options de démarrage dans le menu d’amorçage initial (F6 pour l’amorçage classique, « e » si vous utilisez l’amorçage UEFI).<br />
<br />
Certaines cartes graphiques NVIDIA ne fonctionnent pas du tout avec le pilote vidéo libre (nouveau). Dans ce cas, essayez de remplacer '''xdriver=free''' par '''xdriver=modesetting''' dans les options d’amorçage du premier menu, ou bien essayez d’utiliser le pilote non-libre (propriétaire) en le sélectionnant directement dans le menu de démarrage.<br />
Avec Intel 810 – UHD Graphics 620, KDE Plasma, GNOME, et plusieurs autres environnements de bureau affichent un bureau/barre des tâches vide. L’environnement de bureau Xfce fonctionne parfaitement. Voir [https://bugs.mageia.org/show_bug.cgi?id=25022 mga#25022] pour plus de détails.<br />
<br />
<br />
=== Cartes wifi non opérationnelles ===<br />
<br />
Certaines cartes wifis Broadcom sont connues pour poser des problèmes, parce qu’elles ne fonctionnent qu’avec leur pilote propriétaire qui, pour des questions de licence, peut ne pas avoir été pré-construit sur les images ISOs et doit être chargé au démarrage. Une fois que Mageia est installé, vous pouvez configurer la connexion Wi-Fi et redémarrer.<br />
<br />
<br />
=== Conserver un chargeur d’amorçage tiers ===<br />
<br />
Si, durant l’installation à partir d’un média autonome, vous souhaitez conserver votre chargeur d’amorçage existant, alors continuez, lorsque vous arrivez à l’écran concernant le chargeur d’amorçage, vers l’écran suivant, intitulé ''Mageia Live'', où vous verrez un bouton ''Avancé'' en dessous de l’option « vérifier la présence d’un autre OS ».<br />
<br />
Dans cette section ''Avancé'', il y a une case « ne pas modifier l’ESP ou la MBR ». Cocher cette case empêchera la modification de votre chargeur d’amorçage actuel. Vous devrez alors ajouter vous-même Mageia à vos options d’amorçage. <!--[https://bugs.mageia.org/show_bug.cgi?id=19949#c21 bug 19949 commentaire 21]--><br />
Voir aussi [https://doc.mageia.org/draklive/7/fr/content/setupBootloader.html Notre manuel d’installation de Mageia 7 à partir d’un support autonome (live)].<br />
<br />
== Médias d’installation classique ==<br />
<br />
=== Contourner les firmwares UEFI bogués ===<br />
<br />
Certains rapports de bogues indiquent qu’un retour aux paramètres UEFI par défaut peut résoudre certains problèmes, tandis que d’autres comme le Lenovo Yoga 720 nécessitaient certaines astuces : bizarrement, après avoir démarré une fois en mode Legacy, être revenu en mode UEFI avec les paramètres par défaut, puis passer une nouvelle fois du mode Legacy au mode UEFI en désactivant le démarrage sécurisé (secure boot), les ISO Live et d’installation classique fonctionnent. Très sembable à [https://forums.lenovo.com/t5/Linux-Discussion/Install-linux-in-Lenovo-Yoga-720/td-p/3633251 cette expérience.]<br />
<br />
<br />
=== Conserver un chargeur d’amorçage tiers ===<br />
<br />
Si pendant l’installation de Mageia 7 vous souhaitez éviter d’écraser le MBR (PC-BIOS) ou de changer l’option par défaut dans le nvram UEFI, alors à l’écran ''Résumé'' vous devez entrer dans la section Bootloader et ensuite passer à l’écran SUIVANT intitulé 'BOOTLOADER CONFIGURATION' où il existe un bouton ''Avancé''.<br />
<br />
Dans cette section ''Avancé'', il y a une case « ne pas modifier l’ESP ou la MBR ». Cocher cette case empêchera la modification de votre chargeur d’amorçage. Vous devrez alors ajouter vous-même Mageia à vos options d’amorçage. <!--[https://bugs.mageia.org/show_bug.cgi?id=19949#c21 bug 19949 commentaire 21]--><br />
Voir aussi [https://doc.mageia.org/installer/7/fr/content/setupBootloader.html#d4e969 notre manuel d’installation de Mageia 7]<br />
<br />
{{attention-fr|Si vous choisissez cette option, ajouter une entrée Mageia dans le chargeur d’amorçage de Windows par Easybcd ne fonctionne pas, car Grub2 n’est installé dans aucune de vos partitions Linux.}}<br />
<br />
== Problèmes de mise à niveau ==<br />
<br />
=== Considérations générales ===<br />
<br />
* Assurez-vous que votre système Mageia 6 soit à jour.<br />
* Si vous le pouvez, sauvegardez-le par exemple avec Partclone ou Clonezilla afin de pouvoir le restaurer si nécessaire.<br />
* Utilisez l’image d’installation classique adaptée à votre architecture.<br />
<br />
Selon le moment où un invité VirtualBox a été créé avec Mageia 6, {{cmd | nokmsboot}} sera présent comme entrée dans les options de démarrage du noyau ou non. Si c’est le cas, une mise à jour de Mageia 6 vers Mageia 7 échouera et ne redémarrera pas correctement. Pour de meilleurs résultats, l’option de démarrage {{cmd | nokmsboot}} doit être supprimée avant de commencer la mise à niveau. <br />
Le moyen le plus simple est de démarrer le système invité avant la mise à niveau, d’exécuter le centre de contrôle Mageia à l’intérieur du système invité, de choisir « Démarrage », puis de configurer le démarrage du système. L’écran suivant contient les options de démarrage du noyau. Si {{cmd | nokmsboot}} est présent, supprimez simplement l’entrée, et cliquez sur « Terminer ». Une alternative est de le supprimer lors de la phase de la mise à niveau « après l’installation ». « Paramétrer le système d’amorçage » est l’une des choses qui peuvent être configurées. Le processus est le même que si vous aviez utilisé le Centre de contrôle Mageia.<br />
Enfin, si vous avez manqué tout cela et que votre invité mis à niveau ne démarre pas, redémarrez celui-ci.<br />
Lorsque le menu grub2 apparaît, appuyez sur {{Keypress|e}} de votre clavier. Ceci affichera un écran en mode texte qui peut être modifié temporairement, pour ce démarrage. Cherchez la ligne qui commence par « linux16 ». Utilisez les touches fléchées de votre clavier pour aller à cette ligne et vous déplacer le long de celle-ci et effacez {{cmd | nokmsboot}} à l’aide de la touche {{Keypress|Suppr}}. Faites attention à ne pas supprimer ou ajouter quoi que ce soit d’autre. Une fois terminé, appuyez sur {{Keypress|Ctrl}}{{Keypress|x}} et le démarrage devrait être réussi. Une fois dans le PC hôte, utilisez le MCC comme décrit ci-dessus pour rendre le changement permanent.<br />
<br />
=== Conseils pour les mises à niveau complexes ===<br />
<br />
Les mises à jour importantes ou complexes peuvent échouer avec le message « transactions failed » avant la fin, notamment en raison de conflits de paquets ou de dépendances manquantes. Ceci est dû en partie à la procédure de mise à niveau en tant que transactions groupées qui dépendent des transactions ultérieures ; et aussi au fait que la plupart des paquetages de mise à niveau existent sur le média de mise à niveau, les autres dans le média en ligne. Les notes suivantes devraient vous aider grandement. Ils sont basés sur une mise à jour de Mageia 5 avec plus de 4600 paquets. Consultez d'abord « points généraux » ci-dessus.<br />
<br />
* Exécutez la mise à niveau en utilisant Mageia-7-[arch]-DVD.iso<br />
* Ajouter des médias supplémentaires (ftp, http, autre)<br />
* Un conflit apparaît lorsqu’on choisit ''média supplémentaire''<BR><br />
N’AJOUTEZ AUCUN média, laissez la valeur « Aucun ».<br />
* Tant qu’aucun des RPMs en conflit N’EST inclus dans l’iso, la mise à niveau est réussie.<BR><br />
Après le redémarrage de Mga7, l’utilisateur devra toujours installer tous les rpms ignorés pendant la mise à niveau.<br />
* Ajoutez les mirroirs Mga7 (n’oubliez pas d’ajouter les miroirs 32-bit si vous les avez aussi activés dans l’installation de Mageia 6 64-bit)<br />
* Exécutez ''urpmi --auto-select'' et à o/n sélectionnez n<br />
* Notez le nombre de rpm nécessaires qu’il fallait installer.<br />
* Exécutez ''urpmi --auto-select --split-length'' (notez le nombre de rpms)<br />
* Tous les rpms doivent être installés et le système est entièrement mis à jour<br />
<br />
== Problèmes liés au logiciel ==<br />
<br />
=== Applications Plasma ===<br />
<br />
==== Thème d’apparence de l’espace de travail « Oxygen »====<br />
<br />
Sachez que le thème Oxygène Plasma peut présenter un risque de fuite de mémoire lorsqu’il est utilisé avec certaines cartes graphiques ou pilotes matériels Intel. Alors que la cause exacte est toujours en cours de recherche, lorsque le problème apparaît, il consomme toute la mémoire disponible, ce qui entraîne un ralentissement des performances au fur et à mesure que le swap se remplit, suivi par l’élimination des processus hors mémoire dans un ordre aléatoire. La mise à mort aléatoire de processus peut entraîner corruption de fichiers, en fonction de ce qui a été écrit quand le processus a été tué. Jusqu’à ce que la cause exacte soit identifiée et corrigée, le problème peut être évité en gardant le thème Breeze par défaut sélectionné, au lieu de le changer en oxygen.<br />
<br />
=== Applications Cinnamon ===<br />
<br />
==== Bureau Cinnamon ====<br />
<br />
Cinnamon nécessite que *cinnamon-screensaver* soit ajouté manuellement après l’installation. Choisissez un autre bureau lors de la connexion (ex : IceWM-session), configurez le média en ligne et ajoutez le package *cinnamon-screensaver*. Déconnectez-vous, passez sur l’environement *Cinnamon* et connectez-vous.<br />
<br />
<br />
=== Applications GNOME ===<br />
==== GNOME sur wayland et su - ====<br />
<br />
Certaines commandes drak précédemment invoquées depuis un terminal en tant que root « su - » n’affiche plus l’interface graphique, mais une interface ncurses. Si cela se produit, quittez l’interface ncurses, quittez le terminal qui est connecté en root et se connecter comme simple utilisateur dans le terminal pour demander la commande drak. Une fenêtre s’affiche pour demander le mot de passe root et après avoir saisi le mot de passe correct, l’interface graphique attendue s’affiche.<br />
<br />
==== Récupération des données de l'application Evolution après une mise à niveau ====<br />
Le format de fichier d’Evolution est passé de 2.32 à 3.x. Dans les deux cas, les données étaient stockées dans {{folder|~/.local/share/evolution/mail/local/}} selon [http://www.freedesktop.org/wiki/Specifications/basedir-spec les specifications du répertoire de base XDG]. Dans ce répertoire de données, le format et l’arborescence ont changé.<br />
<br />
[https://forums.linuxmint.com/viewtopic.php?t=88648 Cet article] du forum linuxmint explique de quelle manière récupérer vos données. <br />
<br />
{{note-fr|Les dépôts officiels n’ont pas l’application {{cmd|mb2md}}, si vous voulez essayer d’utiliser {{cmd|mb2md}} vous devez l’installer depuis les dépôts du BlogDrake en tant que root<br />
}}<br />
<br />
{{root console|urpmi --force <nowiki>http://ftp.blogdrake.net/mageia/mageia7/free/noarch/mb2md-3.20-1bdk.mga7.noarch.rpm</nowiki>}}<br />
<br />
=== Applications Xfce ===<br />
==== Déchirure de l’écran lors de l’ouverture de session ====<br />
<br />
Il a été constaté que sur du matériel ancien, il y a des [https://en.wikipedia.org/wiki/Screen_tearing#/media/File:Tearing_(simulated).jpg déchirures d’écran] après avoir entré votre nom d’utilisateur et votre mot de passe dans la fenêtre de connexion et avant que le bureau soit entièrement affiché.<br />
Consultez [https://bugs.mageia.org/show_bug.cgi?id=24134 Mageia Bugzilla]<br />
<br />
Si vous êtes concerné, choisissez un pilote vidéo libre après vous être connecté.<br />
<br />
=== IceWM ===<br />
==== Les fenêtres survivent à la fermeture ====<br />
Avec un matériel spécifique, la fenêtre de fermeture de l’application ne disparaît pas, bien que l’application soit vraiment fermée. Cela ne se produit pas lors d’une ouverture de « session IceWM ». Consultez [https://bugs.mageia.org/show_bug.cgi?id=23595 mga#23595]<br />
<br />
=== Netflix et d’autres sites qui nécessitent un plugin widevine ne fonctionnent pas avec Chromium ===<br />
<br />
Widevine, un plugin de navigateur permettant la lecture de vidéos protégées par DRM, ne s’installera pas correctement dans le navigateur chromium que fournit Mageia.<br />
<br />
Voir [https://bugs.mageia.org/show_bug.cgi?id=24835 mga#24835] pour davantage de details.<br />
<br />
Pour l’instant, si vous avez besoin de widevine, utilisez Firefox.<br />
<!--<br />
[http://blogdrake.net Blogdrake], la communauté Espagnol a créé un fichier script qui installe le plugin widevine pour les navigateurs basés sur chromium.<br />
<br />
Installez le [http://ftp.blogdrake.net/mageia/mageia7/free/noarch/Tuningdrake-2.2.2-19bdk.mga7.noarch.rpm dernier paquet Tuningdrake pour Mageia 7] depuis le dépôt Blogdrake et exécuter {{cmd|get-widevine}} depuis un terminal<br />
<br />
Si la version widevine installée par le script ne fonctionne pas, essayez d’installer une autre version en cours d’exécution {{cmd|<nowiki>Widevine_Version=SomeVersion get-widevine</nowiki>}} ou '''SomeVersion''' pourrait être n’importe lequel [https://dl.google.com/widevine-cdm/versions.txt version supportée]<br />
<br />
<br />
{{attention-fr|Pour obtenir les mises à jour du paquet (et des scripts), ajoutez au moins le dépôt noarch de Blogdrake.<br />
{{cmd|urpmi.addmedia BDK-Free-noarch http://ftp.blogdrake.net/mageia/mageia7/free/noarch}} }}<br />
<br />
{{note-fr|* Certains sites pourraient nécessiter l’utilisation d’un faux useragent<br />
* Pour garder widevine à jour, exécutez {{cmd|get-widevine}} chaque fois que le navigateur chromium est mis à jour<br />
* Google ne fournit plus la version 32 bits du greffon widevine, de telle sorte que la version du greffon chargée par le script sur les systèmes 32 bits pourrait ne plus fonctionner dans le futur}}<br />
--><br />
<br />
=== NFS serveur ===<br />
<br />
La dernière version de {{pkg|nfs-utils}} 2.3.4 apporte des changements mineurs dans la gestion de la configuration.<br />
<br />
Tout d’abord, l’analyse du fichier {{file|/etc/export}} semble être plus rigoureuse, et l’utilisation de l’astérisque, autrement dit (192.168.0.0.*), au lieu de la notation CIDR c.a.d. (192.168.0.0/24), n’est plus supportée. Vous pouvez envisager de créer un fichier dans le répertoire {{folder|/etc/exports.d}} et de placer uniquement vos modifications dans un fichier sous le nom de votre choix qui se termine par.exports.<br /><br />
Voir {{cmd|man exports}}.<br />
<br />
Deuxièmement, l’utilisation de {{file|/etc/sysconfig/nfs}} pour définir les paramètres de ligne de commande pour divers utilitaires NFS n’est plus supportée, au profit du fichier de configuration {{file|/etc/nfs.conf}}.<br />
Un script ({{file|/usr/libexec/nfs-utils/nfsconvert.sh}}) est disponible pour la conversion, et le service systemd {{prog|nfs-convert}}, qui est une dépendance des autres services nfs, devrait automatiquement l’exécuter si nécessaire.<br />
<br />
=== Serveur Bind===<br />
<br />
==== Changement de configuration====<br />
<br />
Depuis bind 9.11.5P1-2mga7, les fichiers nécessaires pour exécuter bind en chroot sont maintenant embarqués dans des sous-paquets distincts :<br />
* {{pkg|bind-chroot}} pour bind standard<br />
* {{pkg|bind-sdb-chroot}} pour bind avec support SDB<br />
<br />
Les unités de systemd suivent la même logique :<br />
* le service {{prog|bind}} lance bind<br />
* le service {{prog|bind-sdb}} lance bind avec le support SDB<br />
* le service {{prog|bind-chroot}} lance bind en chroot<br />
* le service {{prog|bind-sdb-chroot}} lance bind avec le support SDB en chroot<br />
<br />
====Autres problèmes====<br />
<br />
À cause du transfert de certains utilitaires entre {{pkg|bind}} et {{pkg|bind-utils}}, une transaction d’installation qui essaie de mettre à jour uniquement l’un de ces paquets échouera dû à un conflit de fichiers.<br />
<br />
La clé de zone racine publique qui est nécessaire pour la validation DNSSEC est absente du paquet.<br />
<br />
Les deux problèmes devraient être résolus par des mises à jour en attente de validation.<br />
<br />
===Installation de Steam===<br />
Comme Steam a besoin de bibliothèques 32 bits et que les dépôts 32 bits ne sont plus activés par défaut, il est nécessaire d’activer les dépôts 32 bits (Core et Updates) pour l’installation de Steam. Le signe que les dépôts ne sont pas activés est que l’installation ne trouve pas certaines bibliothèques.<br />
<br />
===PMB===<br />
PhpMyBibli n'est pas encore compatible avec php 7 qui est livré avec Mageia 7, et il ne fonctionne donc plus.<br />
La mise-à-jour de PMB est en cours upstream, nous la packagerons dès qu'elle sera disponible. <br />
[[Category:Mageia 7]] [[Category:French]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Archive:_Mageia_7_Errata&diff=45330Archive: Mageia 7 Errata2019-07-24T13:43:54Z<p>Dtux: added PMB issue</p>
<hr />
<div>[[Category:Mageia 7]]<br />
{{multi language banner|[[Mageia_7_Errata-de|Deutsch]] ; [[Mageia_7_Errata|English]] ; [[Erratas de Mageia 7|Español]] ; [[Mageia_7_Errata-fr|Français]] }}<br />
<!--'''This information is available in other languages''':<br /><br />
<br />
* [https://wiki.mageia.org/de/Mageia_7_Errata Deutsch]<br />
* [[Mageia_7_Errata|English]]<br />
* [[Erratas_de_Mageia_7|Español]]<br />
* [[Mageia_7_Errata-fr|Français]]--><br />
<br />
<br />
=Mageia 7=<br />
<br />
Note that we're still adding issues from the list of [https://bugs.mageia.org/buglist.cgi?keywords=FOR_ERRATA7%2C%20&keywords_type=allwords&order=Importance&query_format=advanced&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED bugs in our Bugzilla that still need an errata entry for Mageia 7]<br />
<br />
==Boot==<br />
===Some recent Intel systems===<br />
With some recent hardware, the boot stops after selecting the Grub entry, but before that the kernel comes in action. The identified culprit is the microcode from Intel and last Intel i7 generation processors. This is reported for Asus UX333, UX433 or UX533. A workaround is to add a kernel option ''dis_ucode_ldr''. The solution seems to be a BIOS update. See [https://bugs.mageia.org/show_bug.cgi?id=24979 mga#24979].<br />
<br />
===3 rectangle shapes with question mark during boot===<br />
After selecting to boot Mageia in the grub2 menu the booting presents a grey screen with three rectangle shapes with question marks in them. The system boots normally and proceeds to the normal Login screen, or automatic logon depending on configuration. This happens if you are using the nvidia340 driver (and quite likely, any other driver that doesn't support kernel mode setting). Bug [https://bugs.mageia.org/show_bug.cgi?id=19642#c36 mga#19642 comment 36] contains possible workarounds.<br />
<br />
=== Some machines fail booting 32 bit installer and live iso ===<br />
See [https://bugs.mageia.org/show_bug.cgi?id=23431 mga#23431]. Remedy: use 64 bit versions.<br />
<br />
==Live images==<br />
<br />
===GNOME===<br />
<br />
1) By default GNOME uses the Wayland display server. Wayland is still not fully mature, and may not work well on some hardware. Normally GNOME will automatically fall back to using the X.org display server if Wayland fails to start, but in some cases this fails to happen. If the GNOME desktop fails to launch after completing the initial language and locale selection, or if you experience display problems, you can try forcing GNOME to use the X.org display server by adding {{cmd|nowayland}} to the boot options in the initial boot menu (press {{keypress-fr|e}} to edit the boot options).<br />
<br />
2) By default the NetworkManager service is enabled in place of the old network management services. On the plus side, this means that the NetworkManager applet integrated into the GNOME desktop works; on the minus side it means that attempting to configure your network connection via the MCC does not work. Use the drop-down menu accessible from the top right corner of the GNOME desktop to perform any necessary network configuration. For wired connections, the network is usually configured automatically and you don't need to do anything. For wireless networks, you will usually need to select an access point and, if it is password-protected, enter the password.<br />
<br />
=== Non-working graphics ===<br />
<br />
Some graphics hardware does not work correctly when using the xorg.conf file that gets created by harddrake when booting the Live system. If you have no graphical display at the end of the boot cycle, try adding ''noxorgconf'' to the boot options in the initial boot menu (press {{keypress-fr|e}} to edit the boot options).<br />
<br />
Some NVIDIA graphics cards don't work at all with the free video driver (nouveau). In this case, try replacing ''xdriver=free'' with ''xdriver=modesetting'' in the boot options in the initial boot menu, or alternatively, try using the non-free (proprietary) drivers by selection directly in the boot menu.<br />
<br />
With Intel 810 - UHD Graphics 620, KDE Plasma, GNOME, and several other desktop environments<br />
display a blank desktop/panel. The Xfce desktop environment does work fully.<br />
See [https://bugs.mageia.org/show_bug.cgi?id=25022 mga#25022] for details.<br />
<br />
=== Non-working wifi cards ===<br />
Some wifi hardware from Broadcom is known not to work, because they only work with their proprietary driver which we because of licensing issues not can have pre-built on the isos, and it need be loaded at boot time. Once Mageia is installed you can configure the wifi and reboot.<br />
<br />
===Retaining a third party bootloader===<br />
If, during live install, you want to retain your existing third party bootloader, then, when you get the bootloader screen, proceed to the NEXT screen titled 'Mageia Live' where there is an 'Advanced' button below the 'Probe Foreign OS' option.<br />
<br />
In this advanced section there is a checkbox labeled "Do not touch ESP or MBR". Checking this box will stop your current bootloader from being modified. You will then need to add Mageia to a bootloader yourself.<!--[https://bugs.mageia.org/show_bug.cgi?id=19949#c21 bug 19949 comment 21]--><br />
See also [https://doc.mageia.org/draklive/7/en/content/setupBootloader.html our Mageia 7 version of the Live install manual].<br />
<br />
==Classic installer images==<br />
<br />
===Fighting buggy UEFI firmwares===<br />
<br />
There are some reports about that resetting to default UEFI settings may solve problems, while others such as Lenovo Yoga 720 needed some fiddling: Strangely after booting once in Legacy mode, back to UEFI settings and change back from legacy mode to UEFI and with secure boot disabled, both Live and Classic installed iso worked. Very similar to [https://forums.lenovo.com/t5/Linux-Discussion/Install-linux-in-Lenovo-Yoga-720/td-p/3633251 this experience.]<br />
<br />
===Retaining an existing third party bootloader===<br />
<br />
If during installation of Mageia 7 you wish to avoid overwriting the MBR (PC-BIOS) or changing the default option in the UEFI nvram then at the 'Summary' screen you MUST enter the Bootloader section and then proceed to the NEXT screen titled 'BOOTLOADER CONFIGURATION' where there is an 'Advanced' button.<br />
<br />
In this advanced section there is a checkbox labeled "Do not touch ESP or MBR". Checking this box will stop your current bootloader from being modified. You will then need to add Mageia to a bootloader yourself.<!--[https://bugs.mageia.org/show_bug.cgi?id=19949#c21 bug 19949 comment 21]--><br />
See also [https://doc.mageia.org/installer/7/en/content/setupBootloader.html#d4e985 our Mageia 7 version of the installer manual].<BR><br />
{{warning|If you choose this option, add Mageia entry in Windows bootloader by Easybcd does not work because GRUB2 is not installed in one of your Linux partition.}}<br />
<br />
==Upgrade issues==<br />
<br />
===General points===<br />
* Ensure that your Mageia 6 system is fully up-to-date.<br />
* If you can, back it up e.g. using Partclone or Clonezilla so that you can restore it if necessary.<br />
* Use the Classic ISO appropriate to your architecture.<br />
<!--<br />
{{note|Please also read the page "[[From Mageia 6 to 7]]" to avoid Upgrade issues.}} --><br />
<br />
===Upgrading a VirtualBox guest===<br />
Depending on when it was created, a Mageia 6 VirtualBox guest may or may not use {{cmd|nokmsboot}} as one of the kernel boot options.<br />
If there, an upgrade install from Mageia 6 to Mageia 7 will fail to reboot properly. For best results, the {{cmd|nokmsboot}} boot option should be removed before beginning the upgrade. <br />
<br />
The easiest way to do this is to boot the guest before the upgrade, run the Mageia Control Center inside the guest, choose Boot, then Set up the boot system. The kernel boot options will be shown on the second screen. If {{cmd|nokmsboot}} is there, simply delete it, and click on "Finish." An alternative is to remove it during the "Post-install Configuration" phase of the upgrade. "Set up the boot system" is one of the things that can be configured. The process is the same as if done with MCC.<br />
<br />
Finally, if you missed all this and your upgraded guest fails to boot, shut it down and then restart it. When the grub2 menu appears, press {{keypress | e}} on your keyboard. This will bring up a text screen that can be edited temporarily, for this boot. Look for the line that begins with {{cmd|linux16}}. Use the arrow keys of your keyboard to go to that line and move along it and use the {{keypress | delete}} key to remove {{cmd|nokmsboot}}. Be careful not to delete or add anything else. When finished, press {{keypress | Ctrl}} {{keypress | x}} and the boot should be successful. Once in the guest, use MCC as described above to make the change permanent.<br />
<br />
===LVM and/or LUKS with old udisks===<br />
Before upgrading a system using LVM and/or LUKS from mga6, {{pkg|udisks}} need to be uninstalled manually. Because if udisks is installed when Mageia 7 boots, it will time out and drop you to debug shell. If that happens, there in the shell press {{keypress|Ctrl}}-{{keypress|D}} and it will boot up normally and you can make the uninstall. See [https://bugs.mageia.org/show_bug.cgi?id=24949 mga#24949].<br />
<br />
===GRUB fail to boot with JFS file system===<br />
If you use legacy GRUB ''and'' the filesystem JFS, you need to upgrade to GRUB2 before upgrading to Mageia 7, See [https://bugs.mageia.org/show_bug.cgi?id=25009 mga#25009]; presumably fixed in grub-0.97-48.1.mga7, so if you enable online update media and internet connection during the upgrade (or use network installation), it should work.<br />
<br />
===Advice for complex upgrades===<br />
Large or complex upgrades may fail with message "transactions failed" before finishing, notably citing package conflicts or missing dependencies. This is partly due to the upgrade proceeding as grouped transactions which depend on later ones, and also to the fact that most upgrade packages exist on the upgrade media, others in online media. The following notes should get you through. They are based on an upgrade from Mageia 5 with over 4600 packages. First see '[[#General_points|general points]]' above.<br />
<br />
* Run the upgrade using the Mageia-7-[arch]-DVD.iso<br />
* Add supplemental media (ftp, http, other) <br />
* If|when Conflict is presented, when taken back to 'supplemental media' <BR><br />
DO NOT ADD any media, leave it set as ''None''. <br />
* As long as the conflicting rpms ARE NOT included in the iso then the upgrade will now complete successfully.<br />
<br />
After rebooting to Mga7 user will still need to install any rpms skipped<br />
during the upgrade:<br />
* Add Mga7 Mirror (don't forget to add 32-bit mirrors if you also had them active in Mageia 6 64-bit installation)<br />
* Run 'urpmi --auto-select' and at y/n select n<br />
* Make note of the number of rpms which needed to be installed<br />
* Run urpmi --auto-select --split-length (noted # of rpms)<br />
* All rpms should install and system is fully updated<br />
<br />
===Packages with mga6 suffix===<br />
Take care of this if you use to check if you still have some old packages after the upgrade.<br />
Due to [[Mageia7MassRebuildWorkingPage#Other_old_packages.2C_either_failed_to_build_or_got_rejected|some issues]] in the development cycle of mageia 7 some packages still have mga6 suffix, you can see [https://bugs.mageia.org/attachment.cgi?id=11055 here] the list of packages.<br />
<br />
See [https://bugs.mageia.org/show_bug.cgi?id=24895 mga#24895].<br />
<br />
==Software issues==<br />
<br />
===Plasma Applications===<br />
<br />
====Oxygen Look And Feel Workspace Theme====<br />
<br />
Be aware that the Plasma Oxygen theme may demonstrate a memory leak when used with some Intel hardware graphics cards/drivers. While the exact cause is still being tracked down, when the problem does show up, it consumes all available memory, resulting in slowing performance as the swap fills up, followed by out of memory killing of processes in random order. The random killing of processes may result in<br />
file corruption, depending on what being written when the process was killed. Until the exact cause has been tracked down and fixed, the issue may be avoided by keeping the default breeze theme selected, instead of changing it to oxygen.<br />
<br />
===Cinnamon Applications===<br />
<br />
====Cinnamon Desktop====<br />
<br />
Cinnamon requires {{pkg|cinnamon-screensaver}} to be installed. If you select Cinnamon in the installer, or if you manually install the {{pkg|task-cinnamon}} or {{pkg|task-cinnamon-minimal}} meta-packages, this will be done automatically, but if you choose to manually install the {{pkg|cinnamon}} package by itself, Cinnamon will not work until you also install the {{pkg|cinnamon-screensaver}} package. See [https://bugs.mageia.org/show_bug.cgi?id=23899 mga#23899].<br />
<br />
=== GNOME Applications ===<br />
==== GNOME on Wayland and su - ====<br />
<br />
Some drak commands previously invoked from a "su -" root terminal no longer presents a user GUI interface, rather a ncurses interface.<br />
If this occurs, exit the ncurses interface, exit the root terminal and re-invoke as normal user terminal the drak command.<br />
A password popup will occur requesting root password and after the correct password is entered, the expected GUI interface is presented.<br />
<br />
==== Recover Evolution data after an upgrade ====<br />
Evolution format changed from 2.32 to 3.x. In both cases, the data was stored in {{folder|~/.local/share/evolution/mail/local/}} according to [http://www.freedesktop.org/wiki/Specifications/basedir-spec XDG Base Directory Specification]. Inside that data directory, the format and the tree structure changed.<br />
<br />
[https://forums.linuxmint.com/viewtopic.php?t=88648 This article] in linuxmint forums explain how recover your data.<br />
<br />
{{note|The official repositories don't have the application {{cmd|mb2md}}, if you want to try use {{cmd|mb2md}} you must install from the BlogDrake's repositories as root<br />
}}<br />
<br />
{{root console|urpmi --force <nowiki>http://ftp.blogdrake.net/mageia/mageia7/free/noarch/mb2md-3.20-1bdk.mga7.noarch.rpm</nowiki>}}<br />
<br />
=== Xfce Applications===<br />
====Screen tearing at login====<br />
<br />
It has been found that on some older hardware that there is some screen tearing after entering your user name and password into the login greeter and before the full presentation of the desktop.<br />
See [https://bugs.mageia.org/show_bug.cgi?id=24134 mga#24134].<br />
<br />
If you are affected, choose a free video driver after logging in.<br />
<br />
=== IceWM===<br />
====Windows survive to closing====<br />
With some specific hardware, the window of closing application doesn't disappear, although the application is really closed. This doesn't occur by an opening session with "IceWM session". See [https://bugs.mageia.org/show_bug.cgi?id=23595 mga#23595]<br />
=== Netflix and other sites that require widevine plugin are not working in Chromium===<br />
<br />
Widevine, a browser plugin to allow playback of DRM-protected videos, will not install successfully in the chromium-browser distributed by Mageia.<br />
See [https://bugs.mageia.org/show_bug.cgi?id=24835 mga#24835] for more details.<br />
<br />
For the moment, if you use some site that need widevine plugin, try with firefox.<br />
<!--<br />
[http://blogdrake.net Blogdrake], the Spanish community has created a script that install the widevine plugin for browsers based in chromium.<br />
<br />
Install the [http://ftp.blogdrake.net/mageia/mageia7/free/noarch/Tuningdrake-2.2.2-19bdk.mga7.noarch.rpm last Tuningdrake package for Mageia 7] from Blogdrake's repositories and run {{cmd|get-widevine}} from a terminal emulator<br />
<br />
If the widevine version installed by the script don't works try install other version running {{cmd|<nowiki>Widevine_Version=SomeVersion get-widevine</nowiki>}} where '''SomeVersion''' could be any of [https://dl.google.com/widevine-cdm/versions.txt supported versions]<br />
<br />
{{warning|To get updates to the package (and the scripts) at less add the Blogdrake's noarch repository<br />
{{cmd|urpmi.addmedia BDK-Free-noarch http://ftp.blogdrake.net/mageia/mageia7/free/noarch}} }}<br />
<br />
{{note|* Some sites could require fake the useragent<br />
* To keep widevine update run {{cmd|get-widevine}} each time the chromium browser is updated<br />
* Google don't build anymore the widevine plugin for 32bit architecture, so maybe the version of the plugin downloaded by the script in 32bit systems couldn't work or if does could fail in the future}}--><br />
<br />
=== NFS server ===<br />
<br />
Latest {{pkg|nfs-utils}} 2.3.4 brings minor configuration handling changes.<br />
<br />
First, parsing of {{file|/etc/export}} file seems to be stricter, and usage of wildcard, ie 192.168.0.*), instead of CIDR notation, ie 192.168.0.0/24, is no longer supported. You may want to consider creating a file in the directory {{folder|/etc/exports.d}} and placing just your changes in a file name of your choice ending in .exports. <br /><br />
See {{cmd|man exports}}.<br />
<br />
Second, usage of {{file|/etc/sysconfig/nfs}} to define command-line parameters for various NFS utilities is no longer supported, in favour of {{file|/etc/nfs.conf}} configuration file. A script ({{file|/usr/libexec/nfs-utils/nfsconvert.sh}}) is available for conversion, and the {{prog|nfs-convert}} systemd service, which is a dependency of other nfs services, should automatically run it if needed.<br />
<br />
=== Bind server ===<br />
<br />
==== Setup changes ====<br />
<br />
Starting with bind 9.11.5P1-2mga7, the files needed to run bind in a chroot are now shipped in distinct subpackages:<br />
* {{pkg|bind-chroot}} for the standard bind<br />
* {{pkg|bind-sdb-chroot}} for bind with SDB support<br />
<br />
The new systemd units follow the same logic:<br />
* {{prog|bind}} service runs bind<br />
* {{prog|bind-sdb}} service runs bind with SDB support<br />
* {{prog|bind-chroot}} service runs bind in a chroot<br />
* {{prog|bind-sdb-chroot}} service runs with SDB support in a chroot<br />
<br />
==== Additional issues ====<br />
<br />
Due to some utilities transfer between the {{pkg|bind}} and the {{pkg|bind-utils}} packages, an rpm transaction trying to update only one of those package will fail because of a file conflict.<br />
<br />
The root zone public key, needed for DNSSEC validation, is missing from the package.<br />
<br />
Both issues are fixed in a pending package update. <br />
<br />
=== Steam installation ===<br />
As Steam needs some 32 bit libraries, you have to manually enable 32bit repositories (Core and Updates) as they are no longer enabled by default. The indication that they are not enabled is that some libraries can't be found.<br />
<br />
=== PMB ===<br />
Phpmybibli is not yet compatible with php7, so you can not upgrade to Mageia 7 which as only php 7.3.<br />
The upgrade of PMB to php 7.3 is a work in progress upstream, so we will package it as soon as it will be available.</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Saned-fr&diff=44423Saned-fr2019-05-25T22:31:13Z<p>Dtux: Created page with "{{bandeau multi-langues-fr|English ; Francais ;}} Category:Documentation Category:Howtos {{introduction|Saned est un serveur pour le partage..."</p>
<hr />
<div>{{bandeau multi-langues-fr|[[Saned|English]] ; [[Saned-fr|Francais]] ;}}<br />
[[Category:Documentation]]<br />
[[Category:Howtos]]<br />
{{introduction|Saned est un serveur pour le partage de scanner}}<br />
<br />
=== Installation et configuration côté serveur ===<br />
<br />
Dans un terminal, en administrateur, taper:<br />
<pre><br />
urpmi saned<br />
</pre><br />
<br />
Une fois installé, il faut activer le service :<br />
<pre><br />
systemctl enable saned.socket<br />
</pre><br />
<br />
Il faut ensuite configurer le partage.<br />
<pre><br />
scannerdrake<br />
</pre><br />
Vous pouvez, à ce moment là, configurer le scanner si ce n'était pas déjà fait.<br />
<br />
Après ça, dans la fenêtre de configuration du partage, cliquez sur «Partage de scanner».<br />
<br />
Dans la nouvelle fenêtre, cochez «Les scanners de cette machine sont utilisables par les autres ordinateurs».<br />
<br />
Ensuite, cliquez sur «Partage de scanners pour les hôtes» et sur «Ajouter un hôte».<br />
<br />
Vous pouvez maintenant choisir de partager le scanner avec toutes les machines distantes ou avec une ou plusieurs machines en entrant l'adresse IP et le masque de sous-réseau (eg: 192.168.0.1/24).<br />
<br />
Faite «OK» pour enregistrer, et c'est fini pour le côté serveur.<br />
<br />
=== Configuration côté client ===<br />
<br />
Ouvrir le «Centre de contrôle Mageia»<br />
<br />
Dans la colonne de gauche, cliquez sur «Matériel»<br />
<br />
Cliquez ensuite sur «Configurer le scanneur»<br />
<br />
Après ça, dans la fenêtre de configuration du partage, cliquez sur «Partage de scanner».<br />
<br />
Cochez «Utiliser des scanners sur des ordinateurs distants»<br />
<br />
Cliquez sur «Utiliser des scanners sur les hôtes:»<br />
<br />
Cliquez sur «Ajouter un hôte»<br />
<br />
Vous pouvez maintenant choisir le serveur en entrant l'adresse IP.</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Systemd-networkd&diff=44422Systemd-networkd2019-05-25T21:27:30Z<p>Dtux: </p>
<hr />
<div>[[Category:Documentation]]<br />
<br />
<br />
{{Note|This document, for Mageia version 6, contains some configuration that is not default for Mageia and can break your network}}<br />
<br />
[[Category:Documentation]]<br />
<br />
This document discusses the default network configuration of Mageia 6 more in<br />
detail, with a strong focus on wired network interfaces.<br />
<br />
This document contains some advanced configuration, and in not meant for beginners.<br />
<br />
=== Network Interface Names ===<br />
<br />
Before going into the configuration, it's important to know more about the<br />
names of the network interfaces. <br />
<br />
To identify the available network interfaces, execute the command:<br />
<br />
<pre><br />
ls /sys/class/net<br />
</pre><br />
<br />
or<br />
<br />
<pre><br />
ip link show<br />
</pre><br />
<br />
or<br />
<br />
<pre><br />
networkctl list<br />
</pre><br />
<br />
The naming of the interfaces is described in the Predictable Network Interface<br />
Names scheme. For more information visit:<br />
* https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/<br />
* https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c#L20<br />
<br />
The kernel is responsible for recognizing hardware, after that it will hand it<br />
over to systemd-udev and this process loads the necessary driver and names the<br />
network interface.<br><br />
The following command will give you all the details:<br />
<br />
<pre><br />
udevadm info /sys/class/net/<device name><br />
</pre><br />
<br />
=== The ip command ===<br />
<br />
The ip command can give you more information about the device:<br />
<br />
<pre><br />
ip -d link show <device name><br />
</pre><br />
<br />
And about the ip address that is configured on the interface:<br />
<br />
<pre><br />
ip address show dev <device name><br />
</pre><br />
<br />
And shows the default gateway:<br />
<br />
<pre><br />
ip route show 0.0.0.0/0 <br />
</pre><br />
<br />
You can do many other things with the ip command, such as assigning an ip<br />
address to a network interface, add/change routes etc. But everything you'll do<br />
is not persistent across reboots.<br />
<br />
That's why you need a Network Manager such as NetworkManager or<br />
systemd-networkd. Mageia 6 is using systemd-networkd by default.<br />
<br />
=== network service ===<br />
<br />
The network service is used to configure your network.<br />
If you configure your network via the Mageia Control Center,<br />
the configuration is saved in a<br />
/etc/sysconfig/network-scripts/ifcfg-<device name> file.<br />
These configuration files are parsed at boot-time via the network service<br />
(/etc/rc.d/init.d/network).<br />
<br />
As an example of the content:<br />
<br />
<pre><br />
DEVICE=enp3s0f1<br />
BOOTPROTO=dhcp<br />
ONBOOT=yes<br />
</pre><br />
<br />
In the example above, the device name is enp3s0f1. <br />
<br />
If you know what you are doing, you can also manually make changes in this file,<br />
or even create your own configuration files.<br />
<br />
The good news about this configuration is that it is compatible with NetworkManager, just add:<br />
<br />
<pre><br />
NM_CONTROLLED=yes<br />
</pre><br />
<br />
However the network service is not very flexible and sometimes hard to configure in more complex environments.<br />
<br />
=== systemd-networkd ===<br />
<br />
You can also use another approach, using systemd-networkd configuration files.<br />
<br />
Please note that this is not the Mageia standard configuration,<br />
but it will give you more options and flexibility. <br />
<br />
The daemon is started by default. Check the status:<br />
<br />
<pre><br />
systemctl status systemd-networkd<br />
</pre><br />
<br />
Create the directory for systemd-networkd configuration files:<br />
<br />
<pre><br />
/bin/su -c "mkdir /etc/systemd/network"<br />
</pre><br />
<br />
And create a .network file, e.g. home.network. <br />
<br />
<pre><br />
[Match]<br />
Name = enp3s0f1<br />
<br />
[Network]<br />
Description = Home Network<br />
DHCP = yes<br />
</pre><br />
<br />
For more examples see: man 5 systemd.network. In my example, the interface name<br />
is enp3s0f1. Let's remove the old configuration:<br />
<br />
<pre><br />
/bin/su -c "rm /etc/sysconfig/network-scripts/ifcfg-enp3s0f1"<br />
</pre><br />
<br />
Restart systemd-networkd:<br />
<br />
<pre><br />
systemctl restart systemd-networkd<br />
</pre><br />
<br />
If you migrated everything (!) to systemd-networkd you can stop using the network<br />
service:<br />
<br />
<pre><br />
systemctl stop network<br />
systemctl disable network<br />
systemctl mask network<br />
systemctl stop network-up<br />
systemctl disable network-up<br />
</pre><br />
<br />
But: Use this option only if you really need the flexibility or you want to get more<br />
knowledge about systemd!!!<br />
<br />
=== DNS ===<br />
<br />
The network service updates /etc/resolv.conf. That file configures the<br />
nameserver for resolving and your search domain.<br />
<br />
You can use the nslookup, dig or host utility to verify the resolving.<br />
<br />
If you disabled the network service, you'll need to configure systemd-resolved.<br />
<br />
The configuration is easy, if you don't receive the nameservers via DHCP, add a<br />
<br />
<pre><br />
DNS=<br />
</pre><br />
<br />
entry to the .network file<br />
<br />
To use systemd-resolved, create a symbolic link:<br />
<br />
<pre><br />
/bin/su -c "ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf"<br />
</pre><br />
<br />
The service itself is started by default, check the status:<br />
<br />
<pre><br />
systemctl status systemd-resolved.service<br />
</pre><br />
<br />
=== Hostname ===<br />
<br />
You can configure the hostname during the installation of Mageia.<br />
It will write the configuration to the file /etc/hostname<br />
<br />
Alternatively you can use the hostname command.<br />
<br />
First check the current name:<br />
<br />
<pre><br />
hostnamectl status<br />
</pre><br />
<br />
And change it with:<br />
<br />
<pre><br />
/bin/su -c "hostnamectl set-hostname <full qualified hostname>"<br />
</pre><br />
<br />
As an alternative, manahost is available, which is part of the manatools package.</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Documentation-fr&diff=44421Documentation-fr2019-05-25T21:23:40Z<p>Dtux: /* Logiciel */</p>
<hr />
<div>[[Category:Documentation]]<br />
[[Category:French]]<br />
{{information-fr|Cette page est en travaux. Vous constaterez que de nombreux liens redirigent encore vers leurs homologues anglais. N'oubliez pas que le wiki est librement modifiable et la participation de tous est encouragée pour l'améliorer.}}<br />
<br><br />
<div><br />
<div style="text-align: center; padding-bottom: .2em; padding-top: .2em; background-color: #1272b1;"><br />
<span style="font-family: sans-serif; font-size: 3em; color: #ffffff">Documentation Mageia</span><br><br />
<span style="font-family: sans-serif; font-size: 2em; color: #ffffff">L'ensemble de la Documentation pour les utilisateurs de Mageia</span><br />
</div><br />
<div><br />
{| style="float: left;"<br />
|[[File:Germany.png|x15px|border|Deutsch|link=https://wiki.mageia.org/en/Dokumentation-de]]<br />
|[[File:United_Kingdom.png|x15px|border|English|link=https://wiki.mageia.org/en/Documentation]]<br />
|[[File:Spain.png|x15px|border|Español|link=https://wiki.mageia.org/en/Documentaci%C3%B3n]]<br />
|[[File:Portugal.png|x15px|border|Português|link=https://wiki.mageia.org/en/Documentacao_pt-PT]]<br />
|}<br />
</div><br><br><br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2;"><br />
__TOC__<br />
[[image:Mageia6.png|thumb|300px|''Mageia 6 [[Mageia_6_Notes_de_version-fr|Notes de version]] et [[Mageia_6_Errata-fr|Errata]]'']]<br />
</div><br />
=[[File:Mageia.png|32px]] Découverte de Linux et de Mageia (pour les nouveaux venus) =<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
*[[Environnements_de_bureau-fr | Environnements de bureau]]<br />
*[[Premiers_pas_avec_Gnome-fr | Premiers pas avec Gnome]]<br />
*[[Premiers_pas_avec_KDE-fr | Premiers pas avec KDE]]<br />
*[[Premiers_pas_avec_Linux_et_Mageia-fr | Premier pas avec Linux et Mageia]]<br />
*[[Premiers_pas_avec_LXDE-fr | Premiers pas avec LXDE]]<br />
*[[Premiers_pas_avec_Mate-fr | Premiers pas avec avec Mate]]<br />
*[[Premiers_pas_avec_la_ligne_de_commande_et_exemples_utiles-fr | Premiers pas avec les lignes de commandes et quelques exemples concrets]]<br />
*[[Premiers_pas_avec_Xfce-fr | Premiers pas avec Xfce]]<br />
*[[Liste_des_applications-fr| Liste des applications]]<br />
*[[LXDE desktop | Bureau LXDE]](en)<br />
*[[MATE_Desktop | Bureau MATE]](en)<br />
*[[De_Windows_à_Mageia-fr|De Windows à Mageia]]<br />
*[[Guide_du_débutant-fr | Guide du débutant]]<br />
*[[Présentation de Mageia pour les nouveaux arrivants-fr|Présentation de Mageia pour les nouveaux arrivants]]<br />
*[[Razorqt Desktop | Bureau Razorqt]](en)<br />
<br />
</div><br />
<br><br />
<br />
=[[File:Applications_section.png |32px]] Installation =<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
{|style="text-align:center; border: 2px solid red; -webkit-column-break-inside: avoid; page-break-inside: avoid; break-inside: avoid; -webkit-column-break-after: column; page-break-after: column; break-after: column"<br />
!Manuel de l'utilisateur en plusieurs langues.<br/><br/><br />
[http://doc.mageia.org En ligne, PDF et au format EPUB]<br><br />
<!--[http://docteam.mageia.nl/PDF/installer/ pdf format]<br><br />
[http://docteam.mageia.nl/EPUB/installer/ epub format]<br>--><br />
|-<br />
|Édité et généré par [http://www.calenco.com Calenco] Component Content Management Syst.<br />
|-<br />
|}<br/><br />
*[[Auto inst]](en) : Automated installation<br />
*[[Copier_un_ISO_de_Mageia_sur_une_cl%C3%A9_USB_-_outils_alternatifs-fr|Copier une image ISO sur une Clé USB - outils alternatifs]]<br />
*[[Comment_ajouter_des_options_au_noyau-fr|Comment ajouter des options au noyau]]<br />
*[[Comment_choisir_la_meilleure_méthode_de_mise_à_niveau-fr|Comment choisir la meilleure méthode de mise à niveau]]<br />
*[[Gestion_des_logiciels-fr#Installer_et_supprimer_des_logiciels|Installer et supprimer des logiciels]]<br />
*[[Supports_d'installation-fr|Supports d'installation]]<br />
*[[Installation_sur_un_SSD_(Solid_State_Drive)_fr|Installation sur un SSD (Solid State Drive)]]<br />
*[[Installer_Mageia_depuis_un_support_«_Live_»-fr|Installer Mageia depuis un support « Live »]]<br />
*[[Installation of Mageia in dual boot with Windows]](en)<br />
*[[Installation_sur_les_systèmes_avec_firmware_UEFI-fr|<span style="color:purple;">Installation sur les systèmes avec firmware UEFI</span>]]<br />
*[[Installing Mageia from ISO on disk]](en)<br />
*[[Installing Mageia on a removable drive]](en)<br />
*[[Gestion_des_logiciels-fr#Configurer_les_sources_pour_installer_et_mettre_.C3.A0_jour|Configurer les dépôts Mageia]]<br />
*[[Installing_Mageia_on_ChromeOS_devices|Installing Mageia on ChromeOS devices]](en)<br />
*[[IsoDumper_:_écrire_une_image_ISO_sur_une_clef_USB-fr|IsoDumper : écrire une image ISO sur une clef USB]]<br />
*[[Linx-7_tablet_dual_boot]] (en)<br />
*[[Mageia_en_dual_boot_avec_Windows8_et_suivants-fr|<span style="color:purple;">Mageia en dual boot avec Windows8 et suivants</span>]](UEFI)<br />
*[[Mageia_Netinstall_iso_(Boot.iso)-fr|Mageia_Netinstall_iso_(Boot.iso)]]<br />
*[[Mageia Live USB|Mageia Live USB]]<br />
*[[UEFI-fr|UEFI]]<br />
*[[Les_méthodes_pour_installer_des_programmes-fr|Les méthodes pour installer des programmes]]<br />
*[[Graver_une_image_ISO_sur_DVD-fr|Graver une image ISO sur DVD]]<br />
</div><br />
<br><br />
<br />
=[[File:Drakconf.png|32px]] Outils du CCM (aussi appelés Draktools) = <br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
{|style="text-align:center; border: 2px solid red; -webkit-column-break-inside: avoid; page-break-inside: avoid; break-inside: avoid"<br />
! Manuel de l'utilisateur en plusieurs langues :<br />
[http://doc.mageia.org En ligne, PDF et au format EPUB]<br><br />
<!--[http://docteam.mageia.nl/PDF/MCC/ pdf format]<br><br />
[http://docteam.mageia.nl/EPUB/MCC/ epub format]--><br />
|-<br />
|Édité et généré par [http://www.calenco.com Calenco] Component Content Management Syst.<br />
|-<br />
|}<br />
*[[Drakguard]](en)<br />
*[[Draklive]](en)<br />
*[[Activer_les_dépôts_Testing-fr|Activer les dépôts Testing]]<br />
*[[Installation_et_suppression_de_logiciels-fr|Installation et suppression de logiciels]]<br />
*[[Gestion_des_logiciels-fr#Configurer_les_sources_pour_installer_et_mettre_.C3.A0_jour|Configurer les dépôts Mageia]]<br />
*[[Installez_et_supprimez_des_logiciels_pour_les_profanes-fr|Installez et supprimez des logiciels pour les profanes]]<br />
*[[Msec]](en) : (Sécurité de Mageia)<br />
*[[Server Wizards]](en)<br />
*[[Gestion_des_logiciels-fr|<span style="color:green;">Gestion des logiciels</span>]]<br />
<br />
</div><br />
<br><br />
<br />
=[[File:Configuration_section.png |32px]] Configurer et utiliser Mageia =<br />
<span style="color:green;">{{note-fr|Les liens en vert sont accessibles pour les débutants}}</span><br />
== Logiciel ==<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em; ">[[File:Network-workgroup.png|32px]] Réseau - Internet</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Azure|Azure]](en)<br />
*[[Citrix Receiver]] (en)<br />
*[[Comment développer un site internet-fr|Comment développer un site internet]]<br />
*[[Cookbook web2project]](en)<br />
*[[Create a mirror inside your corporate network|Create a mirror inside your corporate network]](en)<br />
*[[Dma_Dragonfly_Mail_Agent|Dma Dragonfly Mail Agent]](en)<br />
*[[Dmesgs_compared]](en)<br />
*[[Dropbox|<span style="color:green;">Dropbox</span>]](en)<br />
*[[Finding_Mageia_rsync_servers]](en)<br />
*[[Flash Plugin Installation|<span style="color:green;">Installation de Flash Plugin</span>]](en)<br />
*[[Google Earth|<span style="color:green;">Google Earth</span>]](en)<br />
*[[Google talk video chat|<span style="color:green;">Google talk video chat</span>]](en)<br />
*[[How to use iscsi]](en)<br />
*[[Hubic-fr|<span style="color:green;">Hubic</span>]]<br />
*[[Install_java_oracle|<span style="color:green;">Installer Java Oracle</span>]](en)<br />
*[[Installing OpenAFS Client]] (en)<br />
*[[Nextcloud-fr|Nextcloud]]<br />
*[[Systemd-networkd|Systemd-networkd]](en)<br />
*[[Saned]]<br />
<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Packaging_section.png|32px]] Gestion des paquets</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Réaliser_votre_propre_rétroportage-fr|Réaliser votre propre rétroportage]]<br />
*[[How_to_find_a_source_RPM]](en)<br />
*[[Supprimer_des_paquets-fr|Supprimer des paquets <span style="color: red"> <br/> AVERTISSEMENT <br />
à propos de '''{{cmd|urpme --auto-orphans}}'''!</span>]]<br />
*[[Utilisation_de_DNF-fr | Utilisation de DNF]]<br />
*[[Upgrading_with_urpmi|<span style="color:green;">Upgrading_with_urpmi</span>]](en)<br />
*[[URPMI-fr|<span style="color:green;">URPMI</span>]]<br />
*[[Urpmi-proxy]](en)<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Security_section.png|32px]] Sécurité</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Configurer_sudo-fr|<span style="color:green;">Configurer sudo</span>]]<br />
*[[Customize Mageia to use in protected environments|Optimiser Mageia pour l'utiliser dans un environnement sécurisé]](en)<br />
*[[Fail2ban|<span style="color:green;">Fail2ban</span>]](en)<br />
*[[Firewall]](en)<br />
*[[Super_Utilisateur-fr|<span style="color:green;">Super Utilisateur</span>]]<br />
*[[VeraCrypt-fr]](OBSOLÈTE)[[Truecrypt-fr]]<br />
*[[Gérer les Groupes d'utilisateur|<span style="color:green;">Gérer les Groupes d'utilisateur</span>]]<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color:#262F45; font-size: 1.6em;">[[File:App-other.png|32px]] Autres</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[As_easy_as_a_shell]](en)<br />
*[[Bluefish|<span style="color:green;">Bluefish</span>]](en)<br />
*[[Cauldron-fr|Cauldron]]<br />
*[[Chroot]](en)<br />
*[[Debugging software crashes]](en)<br />
*[[Display Managers|<span style="color:green;">Display Managers</span>]](en)<br />
*[[Drakcowsay|<span style="color:green;">Drakcowsay</span>]](en)<br />
*[[Troubleshooting section for the manual|General troubleshooting]] (en)<br />
*[[Grub2-efi_et_Mageia-fr|Grub2-efi et Mageia-fr]]<br />
*[[How to add adb to console in Mageia]](en)<br />
*[[How to add a new Window Manager or Display Manager]](en)<br />
*[[How to configure an Android build environment in Mageia]](en)<br />
*[[How to do some easy commands|<span style="color:green;">How (en)to do some easy commands</span>]](en)<br />
*[[Input methods]] (en)<br />
*[[Installer_VMware_Workstation_11_avec_mageia_5-fr|Installer VMware Workstation 11 avec Mageia 5]]<br />
*[[Installing_VMware_workstation_12.5.9_in_Mageia_6|Installer VMware Workstation 12.5.9 avec Mageia 6]](en)<br />
*[[Liste_des_applications-fr|Liste des applications]]<br />
*[[MariaDB-fr|MariaDB]] (Base de données)<br />
*[[Nomachine]](en)<br />
*[[Openbox]](en)<br />
*[[Speeding up KDE|<span style="color:green;">Speeding up KDE</span>]](en)<br />
*[[Useful polkit policies]](en)<br />
*[[Virt-Manager|Virt-Manager]] (en)<br />
*[[VirtualBox|<span style="color:green;">VirtualBox</span>]](en)<br />
<br />
</div><br />
<br><br />
<br />
==Matériel==<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Computer.png|32px]] Affichage et serveur graphique</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Bumblebee|<span style="color:green;">Bumblebee</span>]](en)<br />
*[[Comment_changer_un_mauvais_pilote_graphique-fr|<span style="color:green;">Comment changer un mauvais pilote graphique</span>]]<br />
*[[Media center with Mageia]](en)<br />
*[[Configurer_le_serveur_d'affichage-fr|<span style="color:green;">Configurer le serveur d'affichage</span>]]<br />
*[[Adapter_plasma_à_la_définition_de_l'écran|<span style="color:green;">Adapter Plasma à la définition de l'écran</span>]]<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Sound_editors_section.png|32px]] Sons</div> <br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Media center with Mageia]](en)<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Network-workgroup.png|32px]] Réseau</div> <br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Configurer_un_réseau_wifi-fr|<span style="color:green;">Configurer un réseau wifi</span>]] et dépannage<br />
*[[Skype with video|<span style="color:green;">Skype with video</span>]](en)<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color:#262F45; font-size: 1.6em;">[[File:Printer.png|32px]] Scanners et imprimantes</div> <br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Epson_scanners|<span style="color:green;">Epson scanners</span>]](en)<br />
*[[Cloudprinting_to_CUPS|Cloudprinting to CUPS]](en)<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:App-other.png|32px]] Autres</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Blackberry Playbook access|<span style="color:green;">Blackberry Playbook access</span>]](en)<br />
*[[Comment_ajouter_des_options_au_noyau-fr|Comment ajouter des options au noyau]]<br />
*[[EFI:_can_no_longer_boot_into_Mageia|EFI : can no longer boot into Mageia]](en)<br />
*[[Efibootmgr]](en)<br />
*[[File transfer with Android devices]] (en)<br />
*[[Troubleshooting section for the manual|General troubleshooting]] (en)<br />
*[[Archive:LIRC|LIRC]] (Infra-red Remote Control)(en)<br />
*[[Journalisation-fr|Journalisation]]<br />
*[[MakeBootCD|<span style="color:green;">MakeBootCD</span>]] How to make a bootable CD (en)<br />
*[[Power saving|<span style="color:green;">Power saving</span>]](en)<br />
*[[RAID and EVMS]](en)<br />
*[[Remote Control with libCEC]](en)<br />
*[[Mode de sauvetage-fr|Mode de sauvetage]]<br />
<br />
</div><br />
<br><br />
<br />
= La communauté =<br />
'''Aidez nous à améliorer la documentation''', ne serait-ce que pour quelques heures, vos questions sont les bienvenues sur [irc://irc.freenode.net/#mageia-doc le canal IRC #mageia-doc], [https://ml.mageia.org/l/info/doc-discuss la liste de diffusion « doc-discuss »] ou sur le [https://forums.mageia.org/en/index.php forum ] en anglais ainsi que sur le forum [http://www.mageialinux-online.org/ MLO] LA référence française.<br><br />
'''Nous rencontrer dans la vie, la vraie pour trouver de l'aide ou des informations''' : [[Mageia_wiki:Current_events | Evénements de l'année]](en)<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
{|style="text-align:center; border: 2px solid red; -webkit-column-break-inside: avoid; page-break-inside: avoid; break-inside: avoid"<br />
! Documentation pour les contributeurs : [[:category:doc|doc]]<br><br />
Rejoignez l'équipe :<br><br />
[[Équipe_de_documentation-fr|Équipe de documentation]]<br><br />
Notre priorité récurrente :<br> [[Captures d'écran MCC et Installateur manquantes-fr| Aidez-nous à obtenir les capture d'écrans manquantes dans votre langue]].<br />
|-<br />
|}<br />
*[[Bugzilla-fr|Introduction à Bugzilla]]<br />
*[[Comment_demander_de_l'aide-fr|Comment demander de l'aide]]<br />
*[[Comment_écrire_une_page_wiki-fr|Comment écrire une page wiki]] <br />
*[[Comment_signaler_un_bogue_correctement-fr|Comment signaler un bogue correctement]]<br />
*[[Cauldron-fr|Comment utiliser Cauldron]]<br />
*[[Finding Mageia rsync servers]] (en)<br />
*[[Comment utiliser IRC-fr|Comment utiliser IRC]]<br />
*[[Robot IRC-fr|Robot IRC]]<br />
*[[Les_canaux_IRC_de_Mageia-fr|Les canaux IRC de Mageia]]<br />
*[[Compte_utilisateur_Mageia.org-fr|Compte utilisateur Mageia.org]]<br />
*[[Liste de diffusion-fr|Liste de diffusion]]<br />
*[[Mgasoft-fr|Mgasoft]]<br />
*[[Liste des miroirs-fr|Liste des miroirs]]<br />
*[[Sophie-fr|Sophie]]<br />
*[[Transifex and git syncing]] (en)<br />
*[[What is i18n, what is l10n]] (en)<br />
<br />
</div><br />
<br><br />
Retrouvez [[:category:documentation|Ici]](en) tous les liens de cette page triés par ordre alphabétique et d'autres informations à propos de la documentation.<br />
<br />
[[Category:Documentation]]<br />
[[Category:French]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Saned&diff=44420Saned2019-05-25T21:20:23Z<p>Dtux: Created page with "Category:Documentation Category:Howtos {{introduction|Saned is a server for scanner sharing}} === Installing and configuring Saned (server side) === In a terminal,..."</p>
<hr />
<div>[[Category:Documentation]]<br />
[[Category:Howtos]]<br />
{{introduction|Saned is a server for scanner sharing}}<br />
<br />
=== Installing and configuring Saned (server side) ===<br />
<br />
In a terminal, as root user, type :<br />
<pre><br />
urpmi saned<br />
</pre><br />
<br />
Once installed<br />
<pre><br />
systemctl enable saned<br />
</pre><br />
<br />
configuration, type <br />
<pre><br />
scannerdrake<br />
</pre><br />
if your scanner is not yet configured, you can now do it.<br />
Once configured, click on the button "scanner sharing"<br />
You can choose to share with all computers or you can type IP adresse of authorized computers.<br />
<br />
=== Configuring scanner (client side) ===<br />
<br />
Type <br />
<pre><br />
scannerdrake<br />
</pre><br />
<br />
choose "use scanner on distant computer"<br />
enter IP adresse of saned server</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Documentation&diff=44414Documentation2019-05-25T20:49:52Z<p>Dtux: /* 32px Configuring and using Mageia */</p>
<hr />
<div>[[Category:Documentation]]<br />
<div style="text-align: center; padding-bottom: .2em; padding-top: .2em; background-color: #1272b1;"><br />
<span style="font-family: sans-serif; font-size: 3em; color: #ffffff">Documentation Portal</span><br><br />
<span style="font-family: sans-serif; font-size: 2em; color: #ffffff">for Mageia users</span><br />
</div><br />
<div><br />
{| style="float: left;"<br />
|[[File:Germany.png|x15px|border|Deutsch|link=https://wiki.mageia.org/en/Dokumentation-de]]<br />
|[[File:France.png|x15px|border|Français|link=https://wiki.mageia.org/en/Documentation-fr]]<br />
|[[File:Spain.png|x15px|border|Español|link=https://wiki.mageia.org/en/Documentaci%C3%B3n]]<br />
|[[File:Portugal.png|x15px|border|Português|link=https://wiki.mageia.org/en/Documentacao_pt-PT]]<br />
|}<br />
</div><br><br><br />
<br />
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2;"><br />
__TOC__<br />
[[image:Mageia6.png|thumb|300px|''Mageia 6 [[Mageia 6 Release Notes|release notes]] and [[Mageia 6 Errata|errata]]'']]<br />
</div><br />
== [[File:Mageia.png|32px]] Discovery of Linux and Mageia ==<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
*[[Desktop environments]]<br />
*[[First step with Gnome|First step with GNOME]]<br />
*[[First step with KDE]]<br />
*[[First step with Linux and Mageia]]<br />
*[[First step with LXDE]]<br />
*[[First step with Mate]]<br />
*[[First step with the command line and useful examples]]<br />
*[[First step with Xfce]]<br />
*[[List of applications]]<br />
*[[LXDE desktop]]<br />
*[[MATE Desktop]]<br />
*[[Newcomers start here]]<br />
*[[Presentation of Mageia for beginners]]<br />
</div><br />
<br />
== The Community ==<br />
<p>'''Help us to improve our documentation''', even for a few hours. Questions welcome on the [irc://irc.freenode.net/#mageia-doc #mageia-doc IRC channel], [https://ml.mageia.org/l/info/doc-discuss doc-discuss mailing list] or [https://forums.mageia.org/en/index.php forum ].<br><br />
'''Meet us in real life for help or information''': [[Mageia_wiki:Current_events | Events of the year]]</p><br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
{|style="text-align:center; border: 2px solid red; -webkit-column-break-inside: avoid; page-break-inside: avoid; break-inside: avoid"<br />
! Contributors documentation: [[:category:doc|doc]]<br><br />
Join the team:<br><br />
[[Documentation team]]<br><br />
Our current priority:<br> [[Missing MCC and installer screenshots|Help us to get the missing screenshots in your language]]<br />
|-<br />
|}<br />
*[[Bugzilla]]: to file a bug<br />
*[[How to report a bug properly]]<br />
*How to use [[Cauldron]]<br />
*[[Finding Mageia rsync servers]]<br />
*[[How to ask help|How to ask for help]]<br />
*[[How to use IRC]]<br />
*[[How to write a wiki page]]<br />
*[[IRC bots]]<br />
*[[Mageia IRC Channels]]<br />
*[[Mageia.org user account]]<br />
*[[Mailing lists]]<br />
*[[Mirror List]]<br />
*[[Sophie]]<br />
*[[Transifex and git syncing]]<br />
*[[What is i18n, what is l10n]]<br />
</div><br />
<br />
== [[File:Applications_section.png |32px]] Installation ==<br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
{|style="text-align:center; border: 2px solid red; -webkit-column-break-inside: avoid; page-break-inside: avoid; break-inside: avoid; -webkit-column-break-after: column; page-break-after: column; break-after: column"<br />
!User manuals in many languages:<br><br />
[http://doc.mageia.org Online, PDF and EPUB format]<br><br />
<!--[http://docteam.mageia.nl/PDF/installer/ pdf format]<br><br />
[http://docteam.mageia.nl/EPUB/installer/ epub format]<br>--><br />
|-<br />
|Edited and generated by the [http://www.calenco.com calenco] Component Content Management Syst.<br />
|-<br />
|}<br />
*[[Auto inst]]: Automated installation<br />
*[[Dump Mageia ISO on a USB flash drive - Alternative tools|Dump Mageia ISO on a USB flash drive - alternative tools]]<br />
*[[How_to_choose_the_right_Mageia_upgrade_method|How to choose the right Mageia upgrade method]]<br />
*[[How to set up kernel options]]<br />
*[[Installation Media]]<br />
*[[Installation on a SSD (Solid State Drive)|Installation on an SSD (Solid State Drive)]]<br />
*[[Installation of Mageia in dual boot with Windows]]<br />
*[[Installing on systems with UEFI firmware|<span style="color:purple;">Installing on systems with UEFI firmware</span>]]<br />
*[[Installing Mageia from ISO on disk]]<br />
*[[Installing Mageia on a removable drive]]<br />
*[[Installing Mageia on ChromeOS devices|Installing Mageia on ChromeOS devices]]<br />
*[[IsoDumper Writing ISO images on USB sticks]]<br />
*[[Linx-7_tablet_dual_boot]]<br />
*[[Mageia in dual boot with Windows8 and over|<span style="color:purple;">Mageia in dual boot with Windows8 and onwards</span>]] (UEFI)<br />
*[[Mageia Live USB|Mageia Live USB]]<br />
*[[Mageia Netinstall Iso (Boot.iso)]]<br />
*[[Ways_to_install_programs|Ways to install programs]]<br />
*[[Writing CD and DVD images]]<br />
</div><br />
<br><br />
<br />
== [[File:Drakconf.png|32px]] MCC tools (also called Draktools) == <br />
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4;"><br />
{|style="text-align:center; border: 2px solid red; -webkit-column-break-inside: avoid; page-break-inside: avoid; break-inside: avoid"<br />
! User manuals in many languages:<br />
[http://doc.mageia.org Online, PDF and EPUB format]<br><br />
<!--[http://docteam.mageia.nl/PDF/MCC/ pdf format]<br><br />
[http://docteam.mageia.nl/EPUB/MCC/ epub format]--><br />
|-<br />
|Edited and generated by the [http://www.calenco.com calenco] Component Content Management Syst.<br />
|-<br />
|}<br />
*[[Drakguard]]<br />
*[[Draklive]]<br />
*[[Enabling the Testing media]]<br />
*[[Installing and removing software]]<br />
*[[Install and remove software for beginners|Installing and removing software for beginners]]<br />
*[[Install media in Mageia for beginners|Mageia install media for beginners]]<br />
*[[Msec]] (Mageia security)<br />
*[[Server Wizards]]<br />
*[[Software management]]<br />
</div><br />
<br><br />
<br />
== [[File:Configuration_section.png |32px]] Configuring and using Mageia ==<br />
<span style="color:green;">{{note|Links in green are intended for newcomers}}</span><br />
=== Software ===<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em; ">[[File:Network-workgroup.png|32px]] Network - Internet</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Azure|Azure]]<br />
*[[Citrix Receiver]]<br />
*[[Cookbook web2project]]<br />
*[[Create a mirror inside your corporate network|Create a mirror inside your corporate network]]<br />
*[[Dma_Dragonfly_Mail_Agent|Dma Dragonfly Mail Agent]]<br />
*[[Dmesgs_compared|Dmesgs compared]]<br />
*[[Dropbox|<span style="color:green;">Dropbox</span>]]<br />
*[[Finding_Mageia_rsync_servers|Finding Mageia rsync servers]]<br />
*[[Flash Plugin Installation|<span style="color:green;">Flash Plugin Installation</span>]]<br />
*[[Google Earth|<span style="color:green;">Google Earth</span>]]<br />
*[[Google talk video chat|<span style="color:green;">Google talk video chat</span>]]<br />
*[[How to develop a Website]]<br />
*[[How to use iscsi]]<br />
*[[Install java oracle|<span style="color:green;">Install java oracle</span>]]<br />
*[[Installing OpenAFS Client]] <br />
*[[OwnCloud]] / [[Nextcloud]]<br />
*[[Saned]]<br />
*[[Systemd-networkd|Systemd-networkd]]<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Packaging_section.png|32px]] Package Management</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Fedora COPR|Building packages with Fedora COPR]]<br />
*[[OpenSUSE Build Service|Building packages with OpenSUSE Build Service]]<br />
*[[Using Mock|Building packages using Mock]]<br />
*[[Using the LiveCD Tools|Building Live images]]<br />
*[[How to do your own backports]]<br />
*[[How to find a source RPM]]<br />
*[[Removing packages]] <span style="color: red">WARNING about '''{{cmd|urpme --auto-orphans}}'''!</span><br />
*[[Upgrading with urpmi|<span style="color:green;">Upgrading with urpmi</span>]]<br />
*[[URPMI|<span style="color:green;">URPMI</span>]]<br />
*[[Urpmi-proxy]]<br />
*[[Using_DNF|Using DNF]]<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Security_section.png|32px]] Security</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Configuring sudo|<span style="color:green;">Configuring sudo</span>]]<br />
*[[Customize Mageia to use in protected environments]]<br />
*[[Fail2ban|<span style="color:green;">Fail2ban</span>]]<br />
*[[Firewall]]<br />
*[[Root|<span style="color:green;">Root</span>]]<br />
*[[Truecrypt]]<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color:#262F45; font-size: 1.6em;">[[File:App-other.png|32px]] Others</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[As_easy_as_a_shell|As easy as a shell]]<br />
*[[Cauldron]]<br />
*[[Chroot]]<br />
*[[Debugging software crashes]]<br />
*[[Display Managers|<span style="color:green;">Display Managers</span>]]<br />
*[[Drakcowsay|<span style="color:green;">Drakcowsay</span>]]<br />
*[[Troubleshooting section for the manual|General troubleshooting]]<br />
*[[Grub2-efi_and_Mageia|Grub2-efi and Mageia]]<br />
*[[How to add adb to console in Mageia]]<br />
*[[How to add a new Window Manager or Display Manager]]<br />
*[[How to configure an Android build environment in Mageia]]<br />
*[[Input methods]]<br />
*[[Installing_VMware_workstation_12.5.9_in_Mageia_6]]<br />
*[[List_of_applications|List of applications]]<br />
*[[MariaDB]] (Database)<br />
*[[Nomachine]]<br />
*[[Openbox]]<br />
*[[Useful polkit policies]]<br />
*[[Virt-Manager|Virt-Manager]]<br />
*[[VirtualBox|<span style="color:green;">VirtualBox</span>]]<br />
*[[Ways_to_install_programs|<span style="color:green;">Ways to install programs</span>]] (more than packaged)<br />
</div><br />
<br><br />
<br />
=== Hardware ===<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Computer.png|32px]] Graphic and display</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Bumblebee|<span style="color:green;">Bumblebee</span>]]<br />
*[[How to change a wrong graphic driver|<span style="color:green;">How to change a wrong graphic driver</span>]]<br />
*[[Media center with Mageia]]<br />
*[[Setup the graphical server|<span style="color:green;">Setup the graphical server</span>]]<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Sound_editors_section.png|32px]] Sound</div> <br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Media center with Mageia]]<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:Network-workgroup.png|32px]] Network</div> <br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Setup wireless networking|<span style="color:green;">Setup wireless networking</span>]] and troubleshooting<br />
*[[Skype with video|<span style="color:green;">Skype with video</span>]]<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color:#262F45; font-size: 1.6em;">[[File:Printer.png|32px]] Scanners and Printers</div> <br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Epson scanners|<span style="color:green;">Epson scanners</span>]]<br />
*[[Cloudprinting_to_CUPS|Cloudprinting to CUPS]]<br />
<br />
</div><br />
<br />
<br />
<div style="margin-left:24px; color: #262F45; font-size: 1.6em;">[[File:App-other.png|32px]] Others</div><br />
<div style="margin-left:48px; column-count:3;-moz-column-count:3;-webkit-column-count:3;"><br />
*[[Blackberry Playbook access|<span style="color:green;">Blackberry Playbook access</span>]]<br />
*[[EFI: can no longer boot into Mageia]]<br />
*[[Efibootmgr]]<br />
*[[File transfer with Android devices]]<br />
*[[Troubleshooting section for the manual|General troubleshooting]]<br />
*[[How to delete a partition with fdisk]]<br />
*[[How_to_set_up_kernel_options|How to set up kernel options]]<br />
*[[Logging|Logging]]<br />
*[[MakeBootCD|<span style="color:green;">MakeBootCD</span>]] How to make a bootable CD<br />
*[[Power saving|<span style="color:green;">Power saving</span>]]<br />
*[[RAID and EVMS]]<br />
*[[Remote Control with libCEC]]<br />
*[[Rescue|Rescue]]<br />
<br />
</div><br />
<br><br />
<br />
<br />
For an alphabetical list of the Documentation pages look [[:category:documentation|here]].</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Packaging_guidelines&diff=44271Packaging guidelines2019-05-10T10:58:44Z<p>Dtux: obsoleting %apply_patch by autopatch -p[01]</p>
<hr />
<div>{{multi language banner|[[Packaging_guidelines|English]] ; [[Consignes_empaqueter-fr|Français]] ; }}<br />
<br />
[[File:Warning_Icon.png]]<br />
'''This page is WORK IN PROGRESS''' and needs to be adapted to Mageia packaging policies. Feel free to proofread and correct where needed. Markup in ''Italic'' shows passages which need to be revised. <br />
<br />
= Mageia Packaging Guidelines =<br />
<br />
<br />
These guidelines are based on Fedora, OpenSUSE, Meego and other distributions' guidelines.<br />
<br />
== Maintaining a Package ==<br />
Every package in Mageia needs a maintainer (AKA owner, bug owner). Any package without an owner will automatically be nominated for deletion from Mageia. A package maintainer is responsible for making sure that<br />
* packages are up to date with latest upstream<br />
* packages consistently build in the Mageia build system and fix build failures when they occur<br />
* package meta data in the RPM spec file is accurate<br />
* the license of the package is correct<br />
* she/he follow upstream for any critical security issues and fix them as soon as possible<br />
* she/he provides information about major changes to other packagers and maintainer to allow enough time for fixing compatibility issues<br />
<br />
Currently the data about ownership of packages is tracked in http://pkgsubmit.mageia.org/data/maintdb.txt and unmaintained packages are listed in http://pkgsubmit.mageia.org/data/unmaintained.txt. This will be better integrated and managed at a later point, and we will have a grace period for unmaintained packages. After the grace period, packages without a maintainer will be reviewed and any packages without a maintainer will be nominated for deletion.<br />
<br />
To add yourself as a maintainer of a package, please follow the steps below:<br />
* Update to the most recent version of mgarepo<br />
* Identify the packages of which you are the ultimate maintainer<br />
* Do the following for every package you want to maintain:<br />
mgarepo maintdb set [packagename] [yourlogin]<br />
* This can be done only by packagers, apprentices have no rights to the maintdb command<br />
*'''You can only do this if the package is currently maintained by nobody!'''<br />
* Your request will be processed immediately and you will then be the maintainer of the package. Good deed, you helped save some unmaintained packages. Now go on and show some love to them :)<br />
<br />
<br />
The current status can be seen here: http://pkgsubmit.mageia.org/data/maintdb.txt<br />
or if you already have a full packager account (i.e. you're not an apprentice) you can query the maintainer database like so:<br />
mgarepo maintdb get [packagename]<br />
or you can ask Sophie on IRC:<br />
:maint [packagename]<br />
<br />
<br />
== [WIP] Non-maintainer updates==<br />
Mageia has a lot of packages and relatively few packagers. We, as a community, always do what we do to make Mageia a better distribution and if/when we step on somebody's toes, we've done it in good faith because we want to make Mageia the best it can be.<br />
<br />
This development deserves a set of guidelines or policies and here is a Work In Progress list proposed on @dev.<br />
<br />
* Non-maintainer release bumps are fine, no need to ask maintainer, unless it's a substantial change (most of the time those are rebuilds or small fixes)<br />
* Non-maintainer version bumps should be discussed with the registered maintainer (in maintdb), when:<br />
** The package is well-established as being maintained by one person or a group of persons (firefox, KDE stack, kernel, etc.)<br />
** The maintainer is active, i.e. has been working on packages, MLs or bugzilla during the last couple of months<br />
** The version bump is substantial: major/minor bump or soname change, non-trivial spec changes like syncing with another distro that was not the maintainer's documented update workflow<br />
* For security issues, non-maintainer uploads are fine if the maintainer hasn't commented on the bug report yet and a reasonable amount of time has passed. Of course, use common sense, if it's the kernel or glibc, give the maintainer a chance to review your changes.<br />
* In other cases, use empathy and your best judgement. Sending a two lines email to a maintainer to notify of your wish to update a package doesn't cost much. Many times, you'd even get an answer saying that you can go ahead and thanking you for your work, which is always worth taking IMO :)<br />
* When doing non-maintainer uploads, be conservative with your changes. Don't drop patches that you don't understand, ask the maintainer, and use the answer to better document the purpose of said patches. Don't sync with a new upstream or another distro without asking (unless that package is identified as synced with a given distro, e.g. rust or firefox).<br />
<br />
== Package Naming ==<br />
* The base package names (used for svn and src.rpm) should be the upstream name of the software project, always lowercase. Upstream names can contain digits, '+', '_' or '.', but no other special characters. Really exceptionally, uppercase letters can be allowed if there is proper justification (e.g. perl packages) or historical reasons.<br />
* Package names that are built by Mageia packagers from the upstream name by adding suffixes should always use '-' as delimiter (e.g. foo-devel or foo-plugins as derived from the foo package). All '_' and '+' in package names must come from upstream naming! The '.' in package names should only come upstream or standard versioning schemes.<br />
* The spec file should be named using the %{name}.spec scheme, i.e. the name of the source package and svn directory should be used as the name for the spec.<br />
<br />
== Version and Release ==<br />
<br />
Package Versions look like : X.Y.Z - R mga V<br />
* X.Y.Z is the 'Version' number which should represent the version of the project<br />
''* R is the 'Release' tag which needs to be always incremented after committing a change to the package before submitting this package for a new build<br />
* mga is the distsuffix<br />
* V is the distro version number''<br />
<br />
=== Version ===<br />
<br />
The Version field in the spec file is where you should put the current version of the software being packaged. <br />
There are some cases in which a source file comes with a "version number" containing non-numeric characters:<br />
<br />
* Pre-release packages: Packages released as "pre-release" versions, prior to a "final" version. Example tags include "alpha", "beta", "rc", "cvs", "git", "svn", etc..., and should be appended to the Release Tag, and not to the Version field. Details can be found below:<br />
<br />
=== Pre-Release Versions ===<br />
<br />
For pre-release or development packages the Release tag should start with "0." so when this software becomes final and does not change Version, we can assure a safe upgrade to the stable version by just changing Release to 1.<br />
<br />
Example:<br />
<pre><br />
mysourcefile-2.9rc2.tar.gz yields a specfile containing Version: 2.9 and Release: %mkrel 0.rc2.1<br />
</pre><br />
<br />
For each rebuilt of the same pre-released package, just increase the Release tag; for instance, 0.rc2.1 would become 0.rc2.2 etc...<br />
<br />
It is recommended to use the macro "%mkrel -c rc2 1" to generate 0.rc2.1.<br />
<br />
For svn or git checkouts, it is preferred to include the date of the snapshot, with or without the release number or git hash (which should at least be as comments in the spec file). The following are acceptable:<br />
<pre><br />
%mkrel -c svn20130213 1<br />
%mkrel -c 20130213svn85423 1<br />
%mkrel -c git20130213 1<br />
%mkrel -c 20130213gitae25f2 1<br />
</pre><br />
<br />
rtmpdump can help deal with snapshots, with its %snap and %mkrel usage:<br />
http://svnweb.mageia.org/packages/cauldron/rtmpdump/current/SPECS/rtmpdump.spec?view=markup<br />
<br />
=== Release ===<br />
<br />
The release number should start with 1, and be set back to 1 with every new version, ''and increased by one with any change in the package.''<br />
<br />
<br />
=== Sub-Release (only applies for updates) ===<br />
<br />
See relevant section of our [https://wiki.mageia.org/en/Updates_policy#Maintainer_.28or_any_interested_packager.29 updates policy]<br />
<br />
== Tags ==<br />
*The Packager tag should not be used in spec files. The identities of the packagers are evident from the changelog entries. By not using the Packager tag, you also avoid seeing bad binaries rebuilt by someone else with your name in the header. See also the [http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html#S3-RPM-INSIDE-PACKAGER-TAG Maximum RPM definition of the Packager tag] . If you need to include information about the packager in the rpms '''you''' built, use <code>%packager</code> in your <code>~/.rpmmacros</code> instead.<br />
*The Vendor tag also should not be used. It is set automatically by the build system.<br />
<br />
*Usually, the PreReq tag should be replaced by plain Requires. For more info, see [http://www.rpm.org/max-rpm-snapshot/s1-rpm-depend-manual-dependencies.html#S3-RPM-DEPEND-FINE-GRAINED Maximum RPM fine-grained dependencies chapter].<br />
* The Source tag documents where to find the upstream sources for the rpm. In most cases, this should be a complete URL to the upstream tarball. Best practice would be using macros like %version and %name where possible to allow for automatic updates, but this is not necessary.<br />
<br />
=== Summary Tag ===<br />
This tag is a single line string describing the package. The maximum length is 79 characters and it should start with an uppercase letter and not with a space. The summary must not end with a dot (.) <br />
If this bothers you from a grammatical point of view, sit down, take a deep breath, and get over it.<br />
<br />
The name of the package should not be repeated in its summary. This is often redundant<br />
information and looks silly in various programs' output.<br />
<br />
It should fit all standard situations and not assume any special context. It should be helpful alone, in alphabetically sorted or unsorted lists of some selected packages, and in alphabetically sorted or unsorted lists of all packages.<br />
<br />
It should describe the package's main function and point out any special properties of the package to support the user comparing similar packages. For example, the two words "Web Browser" summarize any web browser, but using additional adjectives (like minimalistic, complex, GNOME, KDE, text-based, fast, or author's) helps characterize a specific package.<br />
<br />
The summary should be brief and to the point without including redundant information.<br />
<br />
The RPM spec file contains only the English version to keep the RPM database small.<br />
<br />
=== RPM Group Tag ===<br />
<br />
The RPM group tag is used to group packages by the types of functionality they provide, and also makes up the list of Categories in rpmdrake. Following is the list of the groups to use for building an RPM package for Mageia. It is now different from the old one invented and used by Red Hat, because it appeared (from our point of view) that it was no longer suitable for today's distribution. You can still see it at [http://wayback.archive.org/web/20080512000048/http://www.rpm.org/RPM-HOWTO/]<br />
<br />
For a complete list please read [[RPM_groups_policy|Mageia policy]]<br />
<br />
=== BuildRoot ===<br />
The BuildRoot tag is deprecated and should be removed where encountered, as it is handled directly by rpm in Mageia.<br />
<br />
=== PreReq ===<br />
<br />
''Packages should not use the PreReq tag. Once upon a time, in dependency loops PreReq used to "win" over the conventional Requires when RPM determined the installation order in a transaction. This is no longer the case.''<br />
<br />
=== Requires / Explicit Requires ===<br />
Packages should only contain Requires if those are absolutely necessary for the program to work correctly. Use versioned ''Requires'' where needed as explained below.<br />
<br />
Packages must not contain explicit Requires on libraries except when absolutely necessary. When explicit library Requires are necessary, there should be a spec file comment justifying it.<br />
<br />
We generally rely on [[rpmbuild]] to automatically add dependencies on library SONAMEs, shell script interpreters, and modules used by programs written in popular scripting languages like Perl & Python.<br />
Modern package management tools are capable of resolving such dependencies to determine the required packages. Explicit dependencies on specific package names may aid the inexperienced user who attempts to install RPM packages manually, however, history has shown that such dependencies add confusion when library or files are moved from one package to another, when packages get renamed, or when one out of multiple alternative packages would suffice. Additionally, in some cases, old explicit dependencies on package names require unnecessary updates & rebuilds. <br />
<br />
rpmbuild will automatically add ''versioned'' dependencies in a few cases: on library SONAMEs (which operate as library major version numbers), weak symbol versions from glibc, and the Perl or Python API version when installing a binary or versioned extension module. Explicit versioned dependencies are required when they are needed to allow correct updates on stable release or upgrades from one release to another, and are helpful when backporting packages. However, they can become out-of-date, inaccurate and superfluous over time, and should be revisited once the versions in question become ancient history. The rule of thumb is to add (or keep) an explicit version if it is required for upgrading from either of the last two stable releases.<br />
<br />
Versioned dependencies are especially critical for upgraded and backported packages in a stable release. Users may elect to install a subset of packages during an upgrade which could leave an older version of a necessary package installed and result in a non-functioning system.<br />
<br />
An exemplary rationale for a versioned explicit dependency:<br />
<pre><br />
# The automatic dependency on libfubar.so.1 is insufficient,<br />
# as we strictly need at least the release that fixes two segfaults.<br />
Requires: libfubar >= 0:1.2.3-7<br />
</pre><br />
<br />
==== Exceptions from automatically generated Requires/Provides ====<br />
<br />
As all files in a package are automatically scanned what facilities they require and what they provide, it is sometimes necessary to change this and exclude some of those facilities. To do this, you can do it like this:<br />
<br />
# Suppress automatically generated Requires for devel packages<br />
%global __requires_exclude devel\(.*\)<br />
<br />
or<br />
<br />
----------- This requires some editing as the code has changed (October 2014)<br />
<br />
Use now for pear packages:<br />
%global __requires_exclude pear\\(Blowfish/DefaultKey.php\\)<br />
<br />
<br />
-----------<br />
<br />
# Suppress automatically generated Requires for pear packages<br />
%global __requires_exclude pear(vendor/autoload.php)\\|pear(xmlapi.php)<br />
<br />
# we don't want to provide private python extension libs<br />
%define __provides_exclude_from ^(%{python_sitearch}/.*\\.so\\|%{python3_sitearch}/.*\\.so)$<br />
<br />
<br />
<br />
You can also see [https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering this page] in the Fedora wiki for more information on this.<br />
<br />
===== Debugging loop dependencies ======<br />
An issue is often the existence of too much ordering hints which conflicts between themselves.<br />
As such librpm has to break the dependencies cycle and do so randomly in order to have some kind of ordering as a perfect ordering isn't possible when deps tags conflicts.<br />
<br />
One can use "urpmi --debug-librpm --deploops" in order to debug such situations...<br />
<br />
Upgrades from previous releases can be solved by breaking depsloops.<br />
<br />
=== BuildRequires ===<br />
<br />
In package development and testing, please verify that your package is not missing any necessary build dependencies. Having proper build requirements saves the time of all developers and testers as well as build systems because they will not need to search for missing build requirements manually. It is also a safety feature that prevents builds that would not otherwise fail, but would be missing crucial features. For example, a graphical application may exclude PNG support after its '''configure''' script detects that libpng is not installed.<br />
<br />
BuildRequires should be listed one per line for maximum readability; instead of cramming multiple BuildRequires on a single line, use one BuildRequires tag per dependency. While RPM may be able to quickly “view” that really long line of BuildRequires, humans cannot and while this may make the spec longer, it makes it easier to read. <br />
Before adding BuildRequires to any package, please be comfortable with [[#Explicit Requires| Requires]] .<br />
Also please check that you don't add unnecessary BuildRequires. If you BuildRequire package "A" and this has Requires on package "B" and "C" it's useless to buildrequire package "B" and "C" additionally. You can check this with <code>urpmq -pd</code> on package "A".<br />
<br />
You should always use architecture-independent virtual provides as BuildRequires. Arch-independent virtual provides are for example '''%name-devel''' (which has to manually added according to [[Libraries_policy|our library policy]] or '''pkgconfig(name)''' (which is available for many packages already, and automatically generated) <br />
<br />
For example don't use libsqlite3-devel, but use either sqlite3-devel or pkgconfig(sqlite3). You can check which virtual provides a -devel package has like so:<br />
rpm -q --provides lib64sqlite3-devel<br />
which would result in these:<br />
<pre><br />
libsqlite3-devel = 3.7.6.2-3.mga1<br />
sqlite3-devel = 3.7.6.2-3.mga1<br />
pkgconfig(sqlite3) = 3.7.6.2<br />
devel(libsqlite3(64bit))<br />
lib64sqlite3-devel = 3.7.6.2-3.mga1<br />
lib64sqlite3-devel(x86-64) = 3.7.6.2-3.mga1<br />
</pre><br />
As you can see, only the two recommended above bear no reference to the architecture, unlike devel(libsqlite3(64bit)) or lib64sqlite3-devel(x86-64).<br />
<br />
'''IMPORTANT:'''<br />
If you use some binaries like '''desktop-file-install''' you must buildrequire the packages which contain them, otherwise, the package will fail to build on the Mageia build system.<br />
<br />
<br />
When you build a package locally, you can easily install the BuildRequires of package foo using the command:<br />
urpmi foo.spec<br />
(or urpmi --buildrequires foo.spec or urpmi --buildrequires foo.src.rpm which would be the more correct syntax)<br />
It will pull in all packages listed in the spec-file as BuildRequires.<br />
<br />
<br />
=== ExclusiveArch / ExcludeArch / %ifarch / %ifnarch === <br />
<br />
Use ExclusiveArch when you are sure the package only works on some architectures. Use ExcludeArch when you know the package doesn't work on some arch, but don't know the exact arches it does work on.<br />
<br />
For x86 (i586) the macro to use is %ix86.<br />
<br />
%ifarch/%ifnarch should be avoided as much as possible, at least for patching. In general, you should not apply a patch conditionally only for one architecture. This will also give an rpmlint warning:<br />
<br />
<br />
<pre>%ifarch-applied-patch<br />
A patch is applied inside an %ifarch block. Patches must be<br />
applied on all architectures and may contain necessary configure<br />
and/or code patch to be effective only on a given arch.</pre><br />
<br />
=== Sources ===<br />
Source files must begin with Source0, do not use Source: and then Source1:; if a package has exactly one source file, still use Source0 as it may not always continue to have exactly one source file. <br />
If a source file has a downloadable URL that it came from, it must be included. In most cases this should be a complete URL to the upstream tarball. Best practice would be to use macros like %version and %name for this URL where possible to allow for automatic updates, but this is not necessary.<br />
<br />
=== Patches ===<br />
Each problem should be solved in a separate patch. To allow easy maintenance of patches, the source of the patch should be indicated, especially if the patch may need to be updated from the same source in the future. When the patch is first added, the source of the patch should be stated in the commit message. It also helps to have a comment in the SPEC where the patch comes from, which should be a complete URL to the upstream if this is not obvious, and a description what the patch does in short simple words, if that is not clearly self-evident from the patch name.<br />
<br />
Patches should start from Patch0 keyword in SPEC, similar to the Source tag.<br />
Patches should be named in a very explicit manner to make it very clear against which version of the software the patch was originally generated or applied. To that end, patch names usually follow the convention of '''[package_name]-[version]-[description].[filename suffix]''':<br />
<br />
*'''[package_name]''' is the name of the package it applies against, such as 'shadow-utils' or 'gnupg'<br />
*'''[version]''' is the version of the program this patch was developed against, such as 1.0. If a patch is rediffed because the old patch does not apply to a new version, a new patch must be created with the appropriate name – it is inappropriate to rediff foo-1.0-linking-fix.patch against foo-1.2 and continue to use the same patch name. The new patch must be named foo-1.2-linking-fix.patch. ''For historical purposes, patches should be moved in svn; instead of doing “svn rm foo-1.0-linking-fix.patch” and “svn add foo-1.2-linking-fix.patch”, the original patch should be moved and then the newly-derived patch copied and committed; i.e. “svn mv foo-1.0-linking-fix.patch foo-1.2-linking-fix.patch; svn commit”''<br />
*'''[description]''' is a short description of the patch's purpose<br />
*'''[filename suffix]''' Normally this is <code class="filename">.patch</code> or in some cases, mostly when reusing upstream patches <code class="filename">.diff</code><br />
<br />
Patches should be in the unified format (<span>'''diff -u'''</span>) and should be applied with 1 strip level in the spec file (<span>'''%patch -p1'''</span>). The only exceptions are the patches obtained from another primary source site. The original name, suffix, and format is preserved in this case.<br />
Each patch should be kept in plaintext format and uncompressed, to allow for usage with SVN web frontend for example.<br />
<br />
For the patches to be applied, the patches should be mentioned in %prep below %setup, and should be done as follows<br />
<br />
%patch0 -p1 -b .foobar<br />
*-p1 is the patch level, relative from where the patch is applied from<br />
*-b is the suffix that is appended to the backup files which the patch command creates, in this case .foobar, this should similar to or derived from the [description] part of the patch filename (see above).<br />
<br />
To create patches, you can ease your work by using something like http://labix.org/patcher<br />
<br />
*'''Using %apply_patches''' (deprecated, use '''%autopatch''' instead)<br />
This may be used to replace all the %patchN lines in %prep and can save space in the spec file (especially in packages with many upstream patches) as it will apply all patches listed with one command. However, for this to work '''all''' the patches must be '''-p1''' and the PatchN: keyword definitions '''must''' be placed immediately following the SourceN: definitions in the spec file, otherwise they may be silently ignored (no error messages during build) so be careful.<br />
<br />
*'''%autopatch -p[01]'''<br />
This works essentially the same way as '''%apply_patches'''. This is a new standard macro from upstream RPM, and therefore provides better compatibility with other distributions.<br />
<br />
=== %clean ===<br />
<br />
The %clean section is deprecated and should be removed where encountered, as it is handled directly by rpm in Mageia.<br />
<br />
== Documentation ==<br />
Any relevant documentation included in the source distribution should be included in the package. Irrelevant documentation include build instructions, the omnipresent ''INSTALL'' file containing generic build instructions, for example, and documentation for non-Linux systems, e.g. ''README.MSDOS''. Pay also attention to which subpackage you include documentation in, for example, API documentation belongs in the -devel subpackage, not the main one. Or if there's a lot of documentation, consider putting it into a subpackage. In this case, it is recommended to use <code>*-doc</code> as the subpackage name, and <code>Documentation</code> as the value of the <code>Group</code> tag.<br />
<br />
Also, if a package includes something as <code>%doc</code>, it must not affect the runtime of the application. To summarize: If it is in <code>%doc</code>, the program must run properly if it is not present.<br />
<br />
Check that documentation file permissions allow reading by normal users.<br />
<br />
When only English man pages are available, install them uncompressed to <code>%{buildroot}%{_mandir}/manX/</code> (where X is the appropriate section number). They will be automatically compressed before being packaged, so they must be referred to in the %<code>files</code> section with a wildcard, e.g. <code>%{_mandir}/man1/xyzzy.1*</code>. Man pages will be automatically given the <code>%doc</code> attribute, so don't add that explicitly.<br />
<br />
== Devel Packages ==<br />
If the software being packaged contains files intended solely for development, those files should be put in a -devel subpackage. The following are examples of file types which should be in -devel:<br />
* Header files (such as .h files)<br />
* Unversioned shared libraries (such as libfoo.so). Versioned shared libraries (such as libfoo.so.3, libfoo.so.3.0.0) should not be in -devel.<br />
<br />
A good rule of thumb is if the file is used for development and not needed for the base package to run properly, it should go in -devel.<br />
<br />
''<br />
.a files and .la files should generally not be included anywhere. They are only useful when one wants to statically link a program against the library (i.e. include the library in the program binary itself, so the library isn't needed at run-time), which is generally not done in Mageia.<br />
Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases, it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- ie: Removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.''<br />
<br />
=== Requiring Base Package ===<br />
Devel packages must require the base package using a fully versioned dependency:<br />
<code>Requires: %{name} = %{version}-%{release}</code><br />
Usually, subpackages other than -devel should also require the base package using a fully versioned dependency.<br />
<br />
=== Pkgconfig Files ===<br />
The placement of pkgconfig(.pc) files depends on their usecase. Since they are almost always used for development purposes, they should be placed in a -devel package.<br />
A reasonable exception is when the main package itself is a development tool not installed in a user runtime, such as gcc or gdb.<br />
<br />
== Shared Libraries ==<br />
Whenever possible (and feasible), Mageia Packages containing libraries should build them as shared libraries.<br />
<br />
An ldconfig isn't needed anymore for libraries in <code>%post</code> and <code>%postun</code>, this is handled automagically by RPM filetriggers . If this is encountered, please remove the ldconfig calls and if this is the only purpose of %post / %postun then remove the whole %post / %postun section<br />
<br />
See [[Libraries policy]] for more details on how to package libraries.<br />
<br />
== Configuration files ==<br />
<br />
Configuration files must be marked as such in packages.<br />
<br />
''As a rule of thumb, use <code>%config(noreplace)</code> instead of plain <code>%config</code> unless your best, educated guess is that doing so will break things. In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use <code>noreplace</code> is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision. Whenever plain <code>%config</code> is used, add a brief comment to the specfile explaining why.''<br />
<br />
Don't use %config or %config(noreplace) under /usr. /usr is deemed to not contain configuration files in Mageia.<br />
<br />
== Service Management / Initscripts ==<br />
<br />
Since Mageia 3 [http://www.freedesktop.org/wiki/Software/systemd systemd] is the only init system offered, however, it is still able to support SystemV-style initscripts with the caveat that they must contain valid LSB headers to allow for proper dependency information to be extracted.<br />
<br />
Mageia 2 supported both SystemV and systemd boots and thus required both a SystemV-style initscript and (optionally) a systemd unit.<br />
<br />
Mageia 1 only supported SystemV.<br />
<br />
For more information on packaging services see the [[System_Service_policy|System Service policy]].<br />
<br />
== Desktop files ==<br />
<br />
If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws an X window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] ,<br />
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify]<br />
entries.<br />
Please always validate .desktop files via <code>desktop-file-validate</code> from the package desktop-file-utils.<br />
<br />
=== Icon key in Desktop Files ===<br />
''The icon key can only be specified in one way:<br />
<br />
* Short name without file extension/path:<br />
<code>Icon=comical</code><br />
<br />
The short name without file extension allows for icon theming (it assumes .png by default, then tries .svg and finally .xpm)''<br />
<br />
=== .desktop file creation ===<br />
If the package doesn't already include and install its own .desktop file, you need to make your own. You can do this by generating a .desktop file you create as a Source: (such as Source3: %{name}.desktop) or generating it in the spec file via a "here document". Here is an example of such a here document, the green part is the contents of the .desktop file<br />
<br />
<br />
mkdir -p %{buildroot}%{_datadir}/applications<br />
cat > %{buildroot}%{_datadir}/applications/%{name}.desktop << EOF<br />
<span style="color:#0c0;">[Desktop Entry]<br />
Name=Ginkgo<br />
Comment=Ginkgo is a graphical front-end for Nepomuk<br />
Exec=%{_bindir}/%{name}<br />
Icon=nepomuk<br />
Type=Application<br />
Categories=Utility;KDE;Qt;</span><br />
EOF<br />
<br />
=== Localizing .desktop files ===<br />
The values of Name or GenericName are displayed as captions to the graphical desktop icon, so they should be localized according to the [http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s04.html Desktop Entry Specification]. Most of the time, only ''language'' codes or ''language/country'' codes are needed to select the intended system locale. For example:<br />
<br />
<pre><br />
[Desktop Entry]<br />
Type=Application<br />
Name=Clocks<br />
Name[de]=Uhrzeit<br />
Name[es]=Relojes<br />
Name[fr]=Horloges<br />
Name[pt_BR]=Relógios<br />
Name[zh_CN]=时钟<br />
</pre><br />
<br />
In the above .desktop file, <tt>[de]</tt> specifies the German language locale, covering any German-speaking locale, such as <tt>de_DE</tt> or <tt>de_AT</tt>.<br />
<br />
'''Note:''' Since a ''language/country'' code (e.g. <tt>pt_BR</tt>) is more specific than a ''language'' code (e.g. <tt>pt</tt>), a string for the <tt>pt_BR</tt> locale will '''not''' be used for the Portuguese language locale (<tt>pt</tt>). If a string is appropriate for every Portuguese locale, you can use "<tt>Name[pt]</tt>" instead.<br />
<br />
=== desktop-file-install usage ===<br />
<code>desktop-file-install</code> SHOULD be used if there are changes desired to an upstream provided .desktop file (such as add/removing categories, etc). Note: The limited available editing options can be queried via <code>desktop-file-install --help-edit</code> or <code>desktop-file-install --help-all</code><br />
<br />
Here are some usage examples:<br />
<br />
<br />
desktop-file-install --vendor="%{_real_vendor}" \<br />
--remove-category="Application" \<br />
--add-category="Settings;HardwareSettings;" \<br />
--dir %{buildroot}%{_datadir}/applications %{buildroot}%{_datadir}/applications/%{name}.desktop<br />
<br />
<br />
desktop-file-install --vendor="%{_real_vendor}" \<br />
--dir=%{buildroot}%{_datadir}/applications \<br />
--remove-category='Application' \<br />
--remove-category='Utility' \<br />
--add-category='System' \<br />
--add-category='Settings' \<br />
--add-category='Printing' \<br />
--add-category='Qt' \<br />
--add-category='HardwareSettings' \<br />
--add-category='X-Mageia-CrossDesktop' \<br />
--remove-key='Version' \<br />
%{buildroot}%{_datadir}/applications/hplip.desktop<br />
<br />
The installation of the desktop file on the target system does not have to be handled manually anymore as had to be done previously in %post/%postun, this is automagically handled now via [[RPM filetriggers]]. Just make sure that all desktop files you want to install are correct and validated as pointed out above.<br />
<br />
=== MandrivaLinux special categories ===<br />
<br />
In many older .desktop files in packages imported from Mandriva there are deprecated X-MandrivaLinux category entries. They were used when switching from Debian Menu System to Freedesktop XDG menu system, and are deprecated and should be replaced by standard Freedesktop categories. Those can be seen in <br />
[http://standards.freedesktop.org/menu-spec/latest/apa.html Freedesktop specification]<br />
<br />
The only Mandriva one that has an equivalent in Mageia is '''X-MandrivaLinux-CrossDesktop'''. This is for applications which have toolkit-related categories (like GTK, QT, KDE) in their desktop files (and would thus be shown in ''More'' submenu in other desktop environments) when we want them to ''not'' go to the ''More'' submenu on any desktop. These entries should be replaced by '''X-Mageia-CrossDesktop'''. For reference have a look at this bugreport: [https://bugs.mageia.org/show_bug.cgi?id=2449 Bug 2449 - X-MandrivaLinux-* should be dropped]<br />
<br />
Here's one example on how it should be done. totem.desktop file from Totem media player contains:<br />
Categories=GTK;GNOME;AudioVideo;Player;Video;X-MandrivaLinux-CrossDesktop;X-MandrivaLinux-Multimedia-Video;<br />
<br />
So X-MandrivaLinux-CrossDesktop should be replaced by X-Mageia-CrossDesktop (or one could remove the GTK and GNOME categories from the desktop file, but this will also remove information which could be useful to some desktop environments)<br />
<br />
Also X-MandrivaLinux-Multimedia-Video is such a deprecated category and should definitely not be used anymore, instead replaced by the main Freedesktop category '''AudioVideo''' and supplemented by at least one additional category from http://standards.freedesktop.org/menu-spec/latest/apa.html.<br />
As this is already the case (AudioVideo;Player;Video; see above) this X-MandrivaLinux category should simply be removed.<br />
<br />
== Macros vs. variables ==<br />
'''%{buildroot} and %{optflags} vs $RPM_BUILD_ROOT and $RPM_OPT_FLAGS'''<br />
There are generally two styles of defining the rpm BuildRoot and Optimization Flags in a spec file:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5%"<br />
|-<br />
| ||macro style || variable style<br />
|-<br />
|Build Root||%{buildroot}||$RPM_BUILD_ROOT<br />
|-<br />
|Opt. Flags||%{optflags}||$RPM_OPT_FLAGS<br />
|}<br />
<br />
According to [https://wiki.mageia.org/en/RPM_Specfile_policy#Variables our SPEC syntax policy]<br />
variables which are really definitions, such as $RPM_OPT_FLAGS or $RPM_BUILD_ROOT must not be used. Macros like %{optflags} and %{buildroot} must be used instead. Keep "$*" variables strictly limited to shell constructs and not RPM-based definitions.<br />
<br />
== Handling Locale Files ==<br />
Locale files, also known as localisations or (as an abbreviation) l10n files or i18n files (short form of internationalisation, the number shows how many letters have been left out) are compiled .mo files.<br />
'''This section is not about man pages.'''<br />
<br />
<!-- If a given package includes translations, add<br />
<pre><br />
BuildRequires: gettext<br />
</pre><br />
If you don't, your package could fail to generate translation files in the buildroot.--><br />
<br />
(If a package includes translations, it is no longer needed to add the gettext BuildRequire, because gettext is already present in the build environment.)<br/><br />
<br />
Mageia includes an rpm macro called <code>%find_lang</code>. This macro will locate all of the locale files that belong to your package (by name), and put this list in a file. You can then use that file to include all of the locales. <code>%find_lang</code> should be run in the %install section of your spec file, after all of the files have been installed into the buildroot. The correct syntax for <code>%find_lang</code> is usually:<br />
<pre><br />
%find_lang %{name}<br />
</pre><br />
In some cases, the application may use a different "name" for its locales. You may have to look at the locale files and see what they are named. If they are named <code>myapp.mo</code>, then you will need to pass <code>myapp</code> to <code>%find_lang</code> instead of <code>%{name</code>}.<br />
After <code>%find_lang</code> is run, it will generate a file in the active directory (by default, the top level of the source dir). This file will be named based on what you passed as the option to the <code>%find_lang</code> macro. Usually, it will be named <code>%{name}.lang</code>. You should then use this file in the <code>%files</code> list to include the locales detected by <code>%find_lang</code>. To do this, you should include it with the -f parameter to <code>%files</code>.<br />
<pre><br />
%files -f %{name}.lang<br />
%{_bindir}/foobar<br />
...<br />
</pre><br />
If you are already using the -f parameter for the <code>%files</code> section where the locales should live, just append the contents of <code>%{name}.lang</code> to the end of the file that you are already using with -f. (Note that only one file may be used with <code>%files -f</code>.)<br />
<br />
'''Why do we need to use %find_lang?'''<br />
<br />
Using <code>%find_lang</code> helps keep the spec file simple, and helps avoid several other packaging mistakes.<br />
<br />
* Packages that use <code>%{_datadir}/*</code> to grab all the locale files in one line also grab ownership of the locale directories, which is not permitted.<br />
* Most packages that have locales have lots of locales. Using <code>%find_lang</code> is much easier in the spec file than having to do:<br />
<pre><br />
%{_datadir}/locale/ar/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/be/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/cs/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/de/LC_MESSAGES/%{name}.mo<br />
%{_datadir}/locale/es/LC_MESSAGES/%{name}.mo<br />
...<br />
</pre><br />
* As new locale files appear in later package revisions, <code>%find_lang</code> will automatically include them when it is run, preventing you from having to update the spec any more than is necessary.<br />
<br />
Keep in mind that usage of <code>%find_lang</code> in packages containing locales is a MUST.<br />
<br />
== Scriptlets ==<br />
Great care should be taken when using scriptlets in Mageia packages. If scriptlets are used, those scriptlets must be sane. <br />
<br />
<br />
'''Scriptlets requirements'''<br />
Do not use the <code>Requires(pre,post)</code> style notation for scriptlet dependencies, because of two bugs in RPM. Instead, they should be split like this:<br />
<pre><br />
Requires(pre): ...<br />
Requires(post): ...<br />
</pre><br />
For more information, see [http://www.redhat.com/archives/fedora-devel-list/2004-April/msg00674.html www.redhat.com] .<br />
<br />
'''Running scriptlets only in certain situations'''<br />
When the rpm command executes the scriptlets in a package it indicates if the action preformed is an install, erase, upgrade or reinstall by passing an integer argument to the script in question according to the following:<br />
<br />
{| border="1" cellspacing="0" cellpadding="5%" style="text-align: center"<br />
||macro || install || erase || upgrade || reinstall<br />
|-<br />
||%pre || 1 || - || 2 || 2<br />
|-<br />
||%post || 1 || - || 2 || 2<br />
|-<br />
||%preun || - || 0 || 1 || -<br />
|-<br />
||%postun || - || 0 || 1 || -<br />
|}<br />
<br />
This means that for example a package that installs an init script with the <code>chkconfig</code> command should uninstall it only on erase and not upgrade with the following snippet:<br />
<pre><br />
%preun<br />
if [ $1 -eq 0 ] ; then<br />
/sbin/chkconfig --del %{name}<br />
fi<br />
</pre><br />
See also <code>/usr/share/doc/rpm-*/triggers</code>, which gives a more formal, generalized definition about the integer value(s) passed to various scripts.<br />
<br />
'''Scriplets are only allowed to write in certain directories'''<br />
Build scripts of packages (%prep, %build, %install, %check and %clean) may only alter files (create, modify, delete) under %{buildroot}, %{_builddir} and valid temporary locations like /tmp, /var/tmp (or $TMPDIR or %{_tmppath} as set by the rpmbuild process) according to the following matrix<br />
<br />
{| border="1" cellspacing="0" cellpadding="5%" style="text-align: center"<br />
|-<br />
| || /tmp, /var/tmp, $TMPDIR, %{_tmppath} || %{_builddir} || %{buildroot}<br />
|-<br />
|%prep || yes || yes || no<br />
|-<br />
|%build || yes || yes || no<br />
|-<br />
|%install || yes || yes || yes<br />
|-<br />
|%check || yes || yes || no<br />
|-<br />
|%clean || yes || yes || yes<br />
|}<br />
<br />
Further clarification: That should hold true irrespective of the builder's uid.<br />
<br />
== Use of Epochs ==<br />
The Epoch tag in RPM is to be used only as a last resort and should be avoided whenever possible. However, it is sometimes necessary to use an Epoch to handle upstream versioning changes or to ease the transition from third-party repositories. <br />
<br />
<br />
<br />
== Writing a package from scratch ==<br />
<br />
If you want to create a package from scratch, here is a skeleton SPEC where you just need to replace '''foo''' with the proper values according to these guidelines<br />
<br />
<pre>Name: foo <br />
Version: 1.0<br />
Release: %mkrel 1<br />
Summary: foo<br />
License: foo<br />
Group: foo<br />
URL: foo<br />
Source0: %name-%version.tar.bz2<br />
<br />
%description<br />
foo<br />
<br />
<br />
%prep<br />
%setup -q<br />
<br />
%build<br />
%configure2_5x<br />
<br />
%make<br />
<br />
%install<br />
%makeinstall<br />
<br />
%find_lang %name<br />
<br />
%files -n %name<br />
</pre><br />
<br />
== Modifying existing Packages ==<br />
<br />
If you base a new package on an existing non-Mageia package, make sure you verify the correctness of the package and it's spec file to understand exactly what has been done to package the software. Do not submit a package without knowing what those strange, but innocent-looking commands do.<br />
<br />
In particular, you should<br />
<br />
* ensure that original tarballs are self-contained pristine tarballs. The tarball should not contain symlinks that reference outside the tarball root directory<br />
* verify any sources and patches and remove patches or sources that:<br />
** are related to platforms we do not support (example: sparc, ia64, ppc, ...)<br />
** Implement features we do not support (example: selinux)<br />
** Read every patch and understand what it does, if it is needed, put an explanation in the header justifying why the patch is needed.<br />
* verify that the license stated in the spec file matches the actual license of the software, for this, it is advised to also look/grep in the header files of the source code to verify the license information<br />
* skim the summary and description for typos and oddities (see Summary and description ),<br />
* make sure that the correct build root is used,<br />
* ensure that macro usage is consistent and that the macros are available in Mageia (see Macros )<br />
<br />
Keep old changelog entries to credit the original authors. Entries that are several years old or refer to ancient versions of the software may be erased. If you end up doing radical changes and re-write most of the spec file anyway, feel free to start the changelog from scratch. In other words, use your best judgement.<br />
<br />
== Changelogs ==<br />
<br />
This section describes the Mageia policy for RPM changelogs. (Original changelogs included in the original source are not affected by this policy.) <br />
<br />
Please consider that a "normal end user with some technical skills" should be able to read and understand an RPM changelog. Changelog entries have to be in reverse chronological order: newer change log entries are listed above older entries, with the first entry being the most recent. <br />
<br />
Please bear in mind that Mageia changelogs will be automatically parsed to prepare distribution release notes and to report on bugs and CVEs and malformed entries may not be read correctly.<br />
<br />
=== General information ===<br />
<br />
* Changelogs are stored in the SVN commit logs, but should still be considered as part of the final spec when committing to svn (see below)<br />
* The %changelog section must not be used in the .spec file as the svn commit logs produce the RPM changelog upon build <br />
* one supplies a commit message when commiting changes, either via '''svn ci''' or '''mgarepo ci''' via the option '''-m '- this is my commit message''''<br />
* provide meaningful and detailed commit messages and make them verbose enough that those coming later do not need to look at a diff of changes to see what actually happened. <br />
<br />
*<span style="color:#c00;font-weight:bold;">A bad example would be:</span><br />
- fixed foo<br />
This tells no one anything and after a year, whoever made the commit likely has no idea what they did in that commit.<br />
*<span style="color:#0c0;font-weight:bold;">A good example would be:</span><br />
<br />
- rediffed description.patch to fix foo<br />
- added foo-manpages.tar.bz2 to provide such and such for foo<br />
- dropped cvsfix32.patch; merged upstream<br />
<br />
The above is far more telling as to what was actually done. Note that source files must be referred to by their full name (in the above, foo-manpages.tar.bz2, not "S23" or "source23" or something similar). Patches do not need to be referred to by their full names, but can be referred to by the "description" portion of the patch. For instance, the first comment is "rediffed description.patch to fix foo", where description.patch is noted. The patch could in reality be named foo-1.2-mga-description.patch; the prefix (foo-1.2-mga) can be dropped as it should be fairly straightforward to determine what patch has modified/added/removed based on the unique description of the patch. If the patch name is not unique (i.e. there is foo-1.2-mga-description.patch and foo-1.0-cvs-description.patch), then one of the patch names can (and probably should) be changed or the entire patch name should be noted in the changelog.<br />
Do not refer to source files or patch numbers numerically (i.e. using S23 or P12) as patches and source files may be renumbered from time to time and a patch number is not guaranteed to remain consistent.<br />
<br />
* when adding multi-line commit messages, every seperate entry must begin with the '-' character. Like <br />
- Bumped release<br />
- Added foo.patch<br />
<br />
This is optional for single line messages, as in that case it's automatically added if not present<br />
To create a multi-line message simply leave the current line unterminated (no final quote mark) and hit ENTER and continue writing. Finally, terminate the last line with a quote mark. Or write the commit messages into a file and use the -F option for svn ci / mgarepo ci.<br />
<br />
=== External References ===<br />
<br />
Each external reference (bug numbers etc) should be of the form:<br />
"(" + external reference code + bug number +")"<br />
<br />
Currently defined:<br />
* Mageia Bugs : mga#<br />
* Common Vulnerability / Exposure : CVE<br />
<br />
'''Bug Numbers in the change log'''<br />
<br />
During maintenance of a distribution, every change has to be marked with the correct bug number. Normally this has to be a number from https://bugs.mageia.org/. Add an entry with the bugzilla number and a short description of the bug summary. For example:<br />
- Removed invalid desktop Category "Application" (mga#4654).<br />
- Symlink icon to pixmaps dir (mga#2108)<br />
- Added gnome-ui-properties to control-center (mga#1960).<br />
<br />
New packages related to new features will refer also to the corresponding bug number in bugzilla, For example:<br />
- Adding Qt Contacts support (mga#8011)<br />
<br />
'''CVE numbers in change log'''<br />
<br />
As with bug numbers: Add a short description (normally the CVE summary should be enough), the Bugzilla and the CVE number to the changelog entry, and also the name and origin of the patch fixing that CVE. Example:<br />
- fix CVE-2012-1234, denial of service through user stupidity (fix-cve-2012-1234.patch, from upstream).<br />
<br />
=== Spec File changes ===<br />
Be as precise as possible! This is especially important if you remove something from the spec file. <br />
<br />
* Removing original source code must be declared in spec file with a comment ("useful for FreeBSD only" for example) - not necessary to repeat the comment in specfile.<br />
* Extra commands (for example during %install) can be illustrated with a short comment in spec file<br />
* Adding/Removing packages from Requires/Provides must be described in the changelog<br />
* one thing which should not be done without communicating with the maintainer beforehand is reindentation of some parts of the SPEC file. Albeit only small changes in the spec itself (like exchanging a space by one/two tabs between the Tags in the preamble and the values) the diff which is produced by this will be huge.<br />
<br />
=== Source Code changes ===<br />
<br />
Document the most important changes but limit verbosity.<br />
<br />
* look into the source changelog and pick up the most important changes for the distribution (changes for other operating systems are not important). Include what has changed in the new version, usually in the level of detail of a NEWS file; the change log files are usually too long. More than '''10-15 lines''' shouldn't be necessary to describe the most important changes.<br />
* arrange the original changes behind the version update information. Example:<br />
- Update to 1.3.2:<br />
+ fixes memory leak in import function<br />
+ new API command: unlock_client()<br />
+ the following bugs are closed by this new upstream release:<br />
++ ............ [mga:332]<br />
++ ............ [mga:337]<br />
- split of devel package<br />
* If upstream does not provide a meaningful change log, then only do the best effort. Don't waste too much time over it.<br />
* If the upstream tarball really has not changed except for the version number, just the version number in the change log would be fine. Same goes for packages just containing some graphics or theming (unless upstream already provides something that fits). If the upstream changes just consist of "updated translation" or "several bug fixes" even that can be sufficient for a changelog entry (unless these bug fixes contain something you find worth mentioning).<br />
<br />
== Packaging Static Libraries ==<br />
Packages including libraries should exclude static libs as far as possible (eg by configuring with ''--disable-static''). Static libraries should only be included in exceptional circumstances. Applications linking against libraries should as far as possible link against shared libraries, not static versions.<br />
<br />
''.a files and .la files should generally not be included anywhere. They are only useful when one wants to statically link a program against the library (i.e. include the library in the program binary itself, so the library isn't needed at run-time), which is generally not done in Mageia.<br />
Libtool archives, ''foo.la'' files, should not be included. Packages using libtool will install these by default even if you configure with ''--disable-static'', so they may need to be removed before packaging. Due to bugs in older versions of libtool or bugs in programs that use it, there are times when it is not always possible to remove *.la files without modifying the program. In most cases, it is fairly easy to work with upstream to fix these issues. Note that if you are updating a library in a stable release (not devel) and the package already contains *.la files, removing the *.la files should be treated as an API/ABI change -- i.e. removing them changes the interface that the library gives to the rest of the world and should not be undertaken lightly.''<br />
<br />
<br />
=== Packaging Static Libraries ===<br />
* In general, packagers are strongly encouraged not to ship static libs unless a compelling reason exists.<br />
<br />
* We want to be able to track which packages are using static libraries (so we can find which packages need to be rebuilt if a security flaw in a static library is fixed, for instance). There are two scenarios in which static libraries are packaged:<br />
# '''Static libraries and shared libraries.''' In this case, the static libraries must be placed in a ''*-static-devel'' subpackage. Separating the static libraries from the other development files in ''*-devel'' allow us to track this usage by checking which packages <code>BuildRequire</code> the ''*-static-devel'' package. The intent is that whenever possible, packages will move away from using these static libraries, to the shared libraries.<br />
# '''Static libraries only.''' When a package only provides static libraries you can place all the static library files in the ''*-devel'' subpackage.<br />
<br />
* If (and only if) a package has shared libraries which require static libraries to be functional, the static libraries can be included in the ''*-devel'' subpackage.<br />
<br />
=== Statically Linking Executables ===<br />
* Static linkage is a special exception and should be decided on a case-by-case basis. The packager must provide rationale for linking statically, including precedences where available, to release engineering for approval.<br />
<br />
== Obsoleting a package ==<br />
When a package is no longer needed in the distribution it should be obsoleted and removed from cauldron.<br />
<br />
To obsolete and remove a package from cauldron :<br />
* on svn, move the package to the directory svn+ssh://svn.mageia.org/svn/packages/obsolete/ (see also [https://wiki.mageia.org/en/Packagers_svn#How_to_drop_a_package_from_SVN.3F How to drop a package from SVN] )<br />
* if the package is replaced by the other one which provides the same functionality, add it as obsolete in the new package. '''Using versioned obsoletes is recommended (Obsoletes: foo < last cauldron version + 1) - This applies to all subpackages which should be obsoleted!'''<br />
* if the package is not replaced by an other one and is simply dropped, obsolete it by the task-obsolete package. Don't forget to add a comment with the reason for obsoleting, or a link to the discussion on the mailing list explaining the reasons.). '''Using versioned obsoletes is recommended (Obsoletes: foo < last cauldron version + 1) - This applies to all subpackages which should be obsoleted!'''<br />
<br />
When a package is obsoleted by another package it will automatically be removed from the cauldron repository.<br />
<br />
''This was imported from [http://wiki.meego.com MeeGo wiki] licensed under CC-By 3.0''<br /><br />
''As the wiki doesn't exist anymore, have a look at the archived version: <br />
http://wayback.archive.org/web/20130903235324/http://wiki.meego.com/Main_Page<br />
<br />
== Specific languages ==<br />
<br />
see https://en.opensuse.org/openSUSE:Packaging_nodejs<br />
<br />
[[Category:Packaging]]<br />
[[Category:Policies]]<br />
[[Category:Contributors]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Fosdem_2019&diff=42758Fosdem 20192019-01-25T14:29:31Z<p>Dtux: /* People who will join the Saturday night dinner */</p>
<hr />
<div>[[Category:Events]] [[Category:Fosdem]] [[Category:2019]]<br />
<br />
<br />
'''Date :''' 2019-02-02 - 2019-02-03<br /><br />
'''Place :''' Brussels, Université Libre<br /><br />
'''Person in charge :''' <br /><br />
<br />
We have no official stand this year, so skipping all the usual organizational boilerplate. Maybe we can give some goodies to our friends at Fedora? :-)<br />
<br />
Keeping this page as a means to list people who will be there nevertheless and maybe have a meeting/dinner.<br />
<br />
== Who will be there ==<br />
<br />
=== Belgium ===<br />
* AL13N ?<br />
* <your nick or name><br />
<br />
=== Brexitland ===<br />
<br />
* sebsebseb<br />
* pterjan ?<br />
<br />
=== Denmark ===<br />
* Akien<br />
* <br />
<br />
=== Finland ===<br />
* tmb ?<br />
*<br />
<br />
=== France ===<br />
* BAud<br />
* Ennael<br />
* Stormi<br />
* Bcornec<br />
* DTux<br />
<br />
=== Germany ===<br />
* <br />
* <br />
<br />
=== Italy ===<br />
* Pasmatt ?<br />
*<br />
<br />
=== Netherlands ===<br />
<br />
* Marja ?<br />
* Olav<br />
<br />
=== Sweden ===<br />
<br />
* Oden ?<br />
<br />
== Non-GA meeting at Fosdem==<br />
<br />
<br />
<br />
=== List of people who'd like to attend ===<br />
<br />
Tell us if you're coming, no need to spend time on a stand: we don't have one, maybe we'll have a meeting for one hour and a good time saturday's evening at a restaurant to be defined (perhaps Léon's, to be confirmed)<br />
<br />
* baud<br />
* stormi (available for a meeting if there's one)<br />
* DTux<br />
<br />
== Friday Night beer ==<br />
<br />
just come one day before the event, don't drink more than 4 beers to be effective on saturday by 10 A.M. on-site :-) <br />
<br />
===People who will join===<br />
<br />
* BAud & Nim at Delirium Café https://fosdem.org/2018/beerevent/ from ~21h to 23h30<br />
<br />
* sebsebseb might go to that smokey uh venue!<br />
<br />
<br />
<br />
=== Beer: Where & When ===<br />
<br />
Where:<br />
*<br />
*<br />
<br />
(Or meet in a central place and walk to a pub from there?)<br />
<br />
When:<br />
*<br />
*<br />
<br />
<br />
<br />
== Dinner Saturday night ==<br />
<br />
=== One or two volunteers to organize it:===<br />
* <your nick or name><br />
* <your nick or name><br />
<br />
<br />
=== Dinner: Where & When ===<br />
<br />
Where: <br />
* Leon de Bruxelles as usual?<br />
*<br />
<br />
When: <br />
* saturday 20h?<br />
*<br />
<br />
===People who will join the Saturday night dinner===<br />
<br />
* BAud & Nim<br />
* sebsebseb probably<br />
* Bcornec<br />
* stormi possibly<br />
* DTux<br />
<br />
== People who would like to go for dinner on Sunday evening ==<br />
<br />
* <your nick or name><br />
* etc.<br />
<br />
<br />
<br />
== People who would like to meet up again on the Monday before going home ==<br />
<br />
* <your nick or name><br />
* etc.<br />
<br />
== Transportation & accommodation ==<br />
=== Offers ===<br />
<br />
<br />
=== Requests ===<br />
<br />
<br />
=== Hotels ===<br />
* Some of us will stay at [http://www.villa-royale.be/EN/index.html Hotel Villa Royale].<br> During all previous Fosdems since Mageia was born, some of our contributors stayed there. We can give good marks. It now (beginning of January 2017) costs € 60 for a single person per night, taxes and breakfast included.<br />
* An alternative could be [http://www.thonhotels.com/hotels/countrys/belgium/brussels/hotel-bristol-stephanie/ Hotel Bristol Stephanie].<br> It's somewhat near Fosdem (3km) and near Gran Place (2km), very luxurious. Single room € /night; double room €; club room (4persons) € . Not included: breakfast buffet €/person; city tax €/room.<br />
* [http://uk.hotels.com/ho424252/hotel-sabina-brussels-belgium/?locale=en_GB&pos=HCOM_UK Hotel Sabina]. Call them directly to have breakfast included in the price (~46 € for 1 night for 1 person-room, including tax & breakfast). Near Metro Madou which is one change from Fosdem and near Brussel Zuid (Bruxelles Midi) train station.<br />
<br />
Take care with the announced prices: usually breakfast is from 12 to 16 €, and tax is 4 € per night. Call them directly rather than booking via platforms :-). Confirm by mail to know what you're paying for.<br />
<br />
NH Brussels Louise at least one Mageian will be staying there this year!</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Fosdem_2019&diff=42757Fosdem 20192019-01-25T14:28:16Z<p>Dtux: /* List of people who'd like to attend */</p>
<hr />
<div>[[Category:Events]] [[Category:Fosdem]] [[Category:2019]]<br />
<br />
<br />
'''Date :''' 2019-02-02 - 2019-02-03<br /><br />
'''Place :''' Brussels, Université Libre<br /><br />
'''Person in charge :''' <br /><br />
<br />
We have no official stand this year, so skipping all the usual organizational boilerplate. Maybe we can give some goodies to our friends at Fedora? :-)<br />
<br />
Keeping this page as a means to list people who will be there nevertheless and maybe have a meeting/dinner.<br />
<br />
== Who will be there ==<br />
<br />
=== Belgium ===<br />
* AL13N ?<br />
* <your nick or name><br />
<br />
=== Brexitland ===<br />
<br />
* sebsebseb<br />
* pterjan ?<br />
<br />
=== Denmark ===<br />
* Akien<br />
* <br />
<br />
=== Finland ===<br />
* tmb ?<br />
*<br />
<br />
=== France ===<br />
* BAud<br />
* Ennael<br />
* Stormi<br />
* Bcornec<br />
* DTux<br />
<br />
=== Germany ===<br />
* <br />
* <br />
<br />
=== Italy ===<br />
* Pasmatt ?<br />
*<br />
<br />
=== Netherlands ===<br />
<br />
* Marja ?<br />
* Olav<br />
<br />
=== Sweden ===<br />
<br />
* Oden ?<br />
<br />
== Non-GA meeting at Fosdem==<br />
<br />
<br />
<br />
=== List of people who'd like to attend ===<br />
<br />
Tell us if you're coming, no need to spend time on a stand: we don't have one, maybe we'll have a meeting for one hour and a good time saturday's evening at a restaurant to be defined (perhaps Léon's, to be confirmed)<br />
<br />
* baud<br />
* stormi (available for a meeting if there's one)<br />
* DTux<br />
<br />
== Friday Night beer ==<br />
<br />
just come one day before the event, don't drink more than 4 beers to be effective on saturday by 10 A.M. on-site :-) <br />
<br />
===People who will join===<br />
<br />
* BAud & Nim at Delirium Café https://fosdem.org/2018/beerevent/ from ~21h to 23h30<br />
<br />
* sebsebseb might go to that smokey uh venue!<br />
<br />
<br />
<br />
=== Beer: Where & When ===<br />
<br />
Where:<br />
*<br />
*<br />
<br />
(Or meet in a central place and walk to a pub from there?)<br />
<br />
When:<br />
*<br />
*<br />
<br />
<br />
<br />
== Dinner Saturday night ==<br />
<br />
=== One or two volunteers to organize it:===<br />
* <your nick or name><br />
* <your nick or name><br />
<br />
<br />
=== Dinner: Where & When ===<br />
<br />
Where: <br />
* Leon de Bruxelles as usual?<br />
*<br />
<br />
When: <br />
* saturday 20h?<br />
*<br />
<br />
===People who will join the Saturday night dinner===<br />
<br />
* BAud & Nim<br />
* sebsebseb probably<br />
* Bcornec<br />
* stormi possibly<br />
<br />
== People who would like to go for dinner on Sunday evening ==<br />
<br />
* <your nick or name><br />
* etc.<br />
<br />
<br />
<br />
== People who would like to meet up again on the Monday before going home ==<br />
<br />
* <your nick or name><br />
* etc.<br />
<br />
== Transportation & accommodation ==<br />
=== Offers ===<br />
<br />
<br />
=== Requests ===<br />
<br />
<br />
=== Hotels ===<br />
* Some of us will stay at [http://www.villa-royale.be/EN/index.html Hotel Villa Royale].<br> During all previous Fosdems since Mageia was born, some of our contributors stayed there. We can give good marks. It now (beginning of January 2017) costs € 60 for a single person per night, taxes and breakfast included.<br />
* An alternative could be [http://www.thonhotels.com/hotels/countrys/belgium/brussels/hotel-bristol-stephanie/ Hotel Bristol Stephanie].<br> It's somewhat near Fosdem (3km) and near Gran Place (2km), very luxurious. Single room € /night; double room €; club room (4persons) € . Not included: breakfast buffet €/person; city tax €/room.<br />
* [http://uk.hotels.com/ho424252/hotel-sabina-brussels-belgium/?locale=en_GB&pos=HCOM_UK Hotel Sabina]. Call them directly to have breakfast included in the price (~46 € for 1 night for 1 person-room, including tax & breakfast). Near Metro Madou which is one change from Fosdem and near Brussel Zuid (Bruxelles Midi) train station.<br />
<br />
Take care with the announced prices: usually breakfast is from 12 to 16 €, and tax is 4 € per night. Call them directly rather than booking via platforms :-). Confirm by mail to know what you're paying for.<br />
<br />
NH Brussels Louise at least one Mageian will be staying there this year!</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Fosdem_2019&diff=42756Fosdem 20192019-01-25T14:27:32Z<p>Dtux: /* Who will be there */</p>
<hr />
<div>[[Category:Events]] [[Category:Fosdem]] [[Category:2019]]<br />
<br />
<br />
'''Date :''' 2019-02-02 - 2019-02-03<br /><br />
'''Place :''' Brussels, Université Libre<br /><br />
'''Person in charge :''' <br /><br />
<br />
We have no official stand this year, so skipping all the usual organizational boilerplate. Maybe we can give some goodies to our friends at Fedora? :-)<br />
<br />
Keeping this page as a means to list people who will be there nevertheless and maybe have a meeting/dinner.<br />
<br />
== Who will be there ==<br />
<br />
=== Belgium ===<br />
* AL13N ?<br />
* <your nick or name><br />
<br />
=== Brexitland ===<br />
<br />
* sebsebseb<br />
* pterjan ?<br />
<br />
=== Denmark ===<br />
* Akien<br />
* <br />
<br />
=== Finland ===<br />
* tmb ?<br />
*<br />
<br />
=== France ===<br />
* BAud<br />
* Ennael<br />
* Stormi<br />
* Bcornec<br />
* DTux<br />
<br />
=== Germany ===<br />
* <br />
* <br />
<br />
=== Italy ===<br />
* Pasmatt ?<br />
*<br />
<br />
=== Netherlands ===<br />
<br />
* Marja ?<br />
* Olav<br />
<br />
=== Sweden ===<br />
<br />
* Oden ?<br />
<br />
== Non-GA meeting at Fosdem==<br />
<br />
<br />
<br />
=== List of people who'd like to attend ===<br />
<br />
Tell us if you're coming, no need to spend time on a stand: we don't have one, maybe we'll have a meeting for one hour and a good time saturday's evening at a restaurant to be defined (perhaps Léon's, to be confirmed)<br />
<br />
* baud<br />
* stormi (available for a meeting if there's one)<br />
<br />
== Friday Night beer ==<br />
<br />
just come one day before the event, don't drink more than 4 beers to be effective on saturday by 10 A.M. on-site :-) <br />
<br />
===People who will join===<br />
<br />
* BAud & Nim at Delirium Café https://fosdem.org/2018/beerevent/ from ~21h to 23h30<br />
<br />
* sebsebseb might go to that smokey uh venue!<br />
<br />
<br />
<br />
=== Beer: Where & When ===<br />
<br />
Where:<br />
*<br />
*<br />
<br />
(Or meet in a central place and walk to a pub from there?)<br />
<br />
When:<br />
*<br />
*<br />
<br />
<br />
<br />
== Dinner Saturday night ==<br />
<br />
=== One or two volunteers to organize it:===<br />
* <your nick or name><br />
* <your nick or name><br />
<br />
<br />
=== Dinner: Where & When ===<br />
<br />
Where: <br />
* Leon de Bruxelles as usual?<br />
*<br />
<br />
When: <br />
* saturday 20h?<br />
*<br />
<br />
===People who will join the Saturday night dinner===<br />
<br />
* BAud & Nim<br />
* sebsebseb probably<br />
* Bcornec<br />
* stormi possibly<br />
<br />
== People who would like to go for dinner on Sunday evening ==<br />
<br />
* <your nick or name><br />
* etc.<br />
<br />
<br />
<br />
== People who would like to meet up again on the Monday before going home ==<br />
<br />
* <your nick or name><br />
* etc.<br />
<br />
== Transportation & accommodation ==<br />
=== Offers ===<br />
<br />
<br />
=== Requests ===<br />
<br />
<br />
=== Hotels ===<br />
* Some of us will stay at [http://www.villa-royale.be/EN/index.html Hotel Villa Royale].<br> During all previous Fosdems since Mageia was born, some of our contributors stayed there. We can give good marks. It now (beginning of January 2017) costs € 60 for a single person per night, taxes and breakfast included.<br />
* An alternative could be [http://www.thonhotels.com/hotels/countrys/belgium/brussels/hotel-bristol-stephanie/ Hotel Bristol Stephanie].<br> It's somewhat near Fosdem (3km) and near Gran Place (2km), very luxurious. Single room € /night; double room €; club room (4persons) € . Not included: breakfast buffet €/person; city tax €/room.<br />
* [http://uk.hotels.com/ho424252/hotel-sabina-brussels-belgium/?locale=en_GB&pos=HCOM_UK Hotel Sabina]. Call them directly to have breakfast included in the price (~46 € for 1 night for 1 person-room, including tax & breakfast). Near Metro Madou which is one change from Fosdem and near Brussel Zuid (Bruxelles Midi) train station.<br />
<br />
Take care with the announced prices: usually breakfast is from 12 to 16 €, and tax is 4 € per night. Call them directly rather than booking via platforms :-). Confirm by mail to know what you're paying for.<br />
<br />
NH Brussels Louise at least one Mageian will be staying there this year!</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Draklive&diff=41968Draklive2018-11-21T17:18:21Z<p>Dtux: changed link of mklivecd project</p>
<hr />
<div>{{introduction|{{prog|draklive}} is a mastering tool that builds a live distribution according to a configuration file, creates a master image, and optionally installs it on a device. It is the tool used and maintained by Mageia to build the distribution Live medias.}}<br />
<br />
== Advantages ==<br />
{{prog|draklive}}'s philosophy is to keep the live distribution as close as possible to a normal Mageia Linux distribution. All live-specific tweaks are done in a tiny {{prog|initrd}} script. Since the Draklive initrd script is generated on-the-fly, it is very small, and is quite easy to debug should there be any problems.<br />
<br />
The list of drivers included in the {{prog|initrd}} is adjusted during the live distribution creation, according to the medium type. {{prog|draklive}} uses the DrakX libraries to ensure an up-to-date drivers list is used.<br />
<br />
Once the {{prog|initrd}} script has finished booting, the system's root device will be used transparently by the distribution, and no additional tricks are required.<br />
<br />
Hardware detection is done with {{prog|harddrake}}, providing reliable integration with the host system.<br />
<br />
== Features ==<br />
* live CD<br />
* live distribution on USB key<br />
* easy to test over NFS<br />
* uses the Mageia installer to create the live system<br />
* fully read-write live system (using {{prog|unionfs}})<br />
* automatic hardware configuration (using {{prog|harddrake}})<br />
* generic code structure to make new technical choices quickly usable<br />
<br />
== Quickstart ==<br />
'''Before continuing:''' The following packages <b>must</b> be installed on your system: {{pkg|x11-server-xnest}} {{pkg|squashfs-tools}} {{pkg|syslinux}} {{pkg|mkisofs}} {{pkg|rsync}} {{pkg|curl}} {{pkg|mtools}}.<br>For a better compression {{pkg|squashfs3-tools}} is required.<br />
<br />
=== Getting the tool ===<br />
Normally this is done by simply installing the {{pkg|draklive}} package. If you want to make any changes to the draklive tool itself, you can instead get the source code by<br />
git clone git://git.mageia.org/software/build-system/draklive/<br />
and then in subsequent instructions replace the {{cmd|draklive}} command by {{cmd|perl -I../draklive/lib ../draklive/draklive}} (this assumes you check out draklive in the same directory as draklive-config).<br />
<br />
=== Getting the config files ===<br />
git clone git://git.mageia.org/software/build-system/draklive-config/<br />
cd draklive-config<br />
<br />
Then, edit the repository address (and other local settings) in {{file|config/settings.cfg}}. Note that the repository address can be a URL to a remote server or a simple path to a local file system. If you are intending to create your own "remixed" Live ISO (and hence likely take a few attempts to get it just right), it is worth setting up your own local repository mirror to save repeatedly downloading the files.<br />
<br />
=== Building a live CD or live USB ===<br />
{{root console|draklive --clean --all}}<br />
<br />
See the output of '''{{cmd|draklive --help}}''' for more details.<br />
<br />
=== Recording a live USB ===<br />
{{root console|draklive --record --device /dev/sdX}}<br />
<br />
Where /dev/sdX is your USB key disk device (not partition)<br />
<br />
== Configuration ==<br />
=== Example ===<br />
<pre><br />
{<br />
system => {<br />
root => '/chroot/live/4',<br />
repository => '/mnt/BIG/dis/4/i586',<br />
auto_install => 'config/auto_inst.cfg.pl',<br />
rpmsrate => 'config/rpmsrate',<br />
vga_mode => 788,<br />
install_env => {<br />
},<br />
},<br />
media => {<br />
storage => 'cdrom',<br />
},<br />
mount => $predefined{mounts}{volatile_squash_union},<br />
};<br />
</pre><br />
<br />
=== Example: Creating a bootable cdrom for old computers unable to boot from a USB key ===<br />
Modify the file {{file|config/live.cfg}} media hash as follows:<br />
<br />
<pre><br />
media => { storage => 'usb', boot => 'cdrom' },<br />
</pre><br />
<br />
And then run the command:<br />
<br />
<pre><br />
perl -I../draklive/lib ../draklive/draklive --config config/live.cfg --boot-only --boot --master<br />
</pre><br />
<br />
This will create the iso file: {{file|/your_workdir/images/boot.iso}} ({{file|your_workdir}} is {{file|/var/lib/draklive}} by default)<br />
<br />
=== Choosing Desktop Environnement ===<br />
To change the target desktop, pass<br />
--desktop=PLASMA5|GNOME|xfce4|LXDE|Enlightenment<br />
<br />
=== Package selection ===<br />
If you need to adjust packages selection, edit 'rpmsrate_flags_chosen' for rpmsrate categories, 'default_packages' for additional packages, 'skipped_packages' to save space.<br />
<br />
=== Exhaustive description ===<br />
The configuration file should contain a hash of settings. Some settings have to be filled in the top-level, others have to be grouped in sub-hashes.<br />
<br />
==== system sub-hash ====<br />
This hash describes the installed distribution.<br />
<br />
* {{cmd|root}}: path of the installed distribution<br />
* {{cmd|repository}}: path to the installer repository<br />
* {{cmd|auto_install}}: installer {{file|auto_inst.cfg.pl}} file<br />
* {{cmd|patch_install}}: installer patch file (actually defcfg file)<br />
* {{cmd|postInstall}}: commands to be run (using <b>{{cmd|bash -c}}</b> after all the additional_media/rpm/patches steps are done)<br />
* {{cmd|install_env}}: hash reference of variables that should be passed to install (they will be usable in the {{file|auto_inst.cfg.pl}} as well)<br />
* {{cmd|additional_modules}}: array reference of {{file|.ko}} modules to be copied and loaded in the {{file|initrd}}<br />
* {{cmd|rpmsrate}}: local {{prog|rpmsrate}} path (useful to add/modify/remove packages rate)<br />
* {{cmd|patches}}: array reference of patches to be applied directly in system root<br />
* {{cmd|rpms}}: array reference of rpms to be installed after installation<br />
* {{cmd|vga_mode}}: graphical mode which the live distribution should use<br />
* {{cmd|splash}}: set to <i>no</i> if you don't want to use a splash (default is <i>yes</i>)<br />
* {{cmd|kernel}}: default kernel release (optional)<br />
<br />
==== media sub-hash ====<br />
This hash describes which medium access should be used.<br />
<br />
* {{cmd|storage}}: medium type (<i>cdrom</i> or <i>usb</i>)<br />
<br />
Optional fields:<br />
<br />
* {{cmd|boot}}: boot medium type to be used with {{cmd|--boot-only}} option, if any (<i>cdrom</i> or <i>usb</i>)<br />
<br />
Or customised settings:<br />
<br />
* {{cmd|$custom{media}{nfs}->(<i>module name</i>, <i>live system IP address</i>, <i>NFS source</i>)}}<br />
<br />
==== extra_media sub-array ====<br />
This array should contain all extra media (see media sub-hash description) that the live system should support. This allows to make live systems using different boot types, using the copy wizard. For example, if the default media is of the ''cdrom'' type, and the extra media array contains a media using the ''usb'' type, the running live CD will allow to duplicate itself to both USB keys and CDs.<br />
<br />
==== mount sub-hash ====<br />
This hash describes how the live components have to be mounted together.<br />
<br />
Some basic setups are predefined:<br />
<br />
* {{cmd|$predefined{mounts}{simple_union} }}: use the media contents as raw root, and mount it with a tmpfs using {{prog|unionfs}}, to get a RW system<br />
* {{cmd|$predefined{mounts}{volatile_squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, uses a tmpfs, and mounts them together using {{prog|unionfs}}<br />
* {{cmd|$predefined{mounts}{squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, a {{file|system.loop}} ext2 read-writable loopback file, and mounts them together using {{prog|unionfs}}<br />
* {{cmd|$predefined{mounts}{multi_squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, optionally uses a read-only {{file|system.sqfs}} "patch", a tmpfs, and mounts them together using {{prog|unionfs}}<br />
<br />
Or build your own mount type:<br />
<br />
{{...}}<br />
<br />
==== top-level settings ====<br />
Live settings:<br />
<br />
* {{cmd|post}}: array of commands to be run at end of {{cmd|initrd}}<br />
* {{cmd|copy_initrd}}: copy the {{file|initrd}} to this location at the end of the {{cmd|initrd}} step (e.g. to {{file|/var/lib/tftpboot/live.rdz}})<br />
* {{cmd|debug}}: include some debug tools in {{cmd|initrd}} ({{prog|busybox}}, {{prog|strace}}, {{prog|ping}}) and run a debug shell at beginning of {{cmd|initrd}}<br />
<br />
Directory settings (all optional):<br />
<br />
* {{cmd|workdir}}: {{prog|draklive}} working directory (defaults to {{file|/tmp/draklive}})<br />
* {{cmd|mnt}}: temporary mount point for {{prog|draklive}}<br />
<br />
<br />
== References ==<br />
=== draklive tools and One configuration files ===<br />
<br />
* https://wiki.mageia.org/en/Building_the_Live_ISOs<br />
* https://wiki.mageia.org/en/Auto_inst<br />
* http://gitweb.mageia.org/software/build-system/draklive/<br />
* http://gitweb.mageia.org/software/build-system/draklive-config/<br />
* <b>perldoc draklive</b><br />
<br />
=== Other live tools ===<br />
* [https://github.com/unity-linux/mklivecd mklivecd]<br />
* [http://www.linux-live.org/ linux-live]<br />
* [http://wiki.debian.org/DebianLive/ Debian live tools] (make-live and casper)<br />
<br />
<br />
== Overlay filesystems ==<br />
==== UnionFS ====<br />
<br />
* http://www.fsl.cs.sunysb.edu/project-unionfs.html<br />
* http://www.unionfs.org/<br />
* http://www.linuxjournal.com/article/7714<br />
<br />
==== Other ====<br />
* [http://www.atconsultancy.nl/cowloop/ cowloop]<br />
* [http://www.denx.de/wiki/bin/view/Know/MiniFOHome mini_fo (the mini fanout overlay file system)]<br />
* [http://aufs.sourceforge.net/ aufs: another unionfs]<br />
<br />
<br />
== Debug ==<br />
<br />
If you need to debug the draklive you need to search for the file ddebug.log in the build directory of the live installation.<br />
<br />
== FAQ ==<br />
* Missing squashfs and lzma files?<br />
<br />
In case you get an error "missing squashfs" and "missing lzma" you should uninstall the dkms-lzma and dkms-squashfs and install kernel-lzma and kernel-squashfs. You have to reboot the system after this and before starting draklive, modprobe squashfs. Also you can add in live.cfg in the section "rpms": "media/main/squashfs-lzma-kernel-2.6.31.5-desktop-1mnb-3.3-11mdv2010.0.i586.rpm" and "media/main/lzma-kernel-2.6.31.5-desktop-1mnb-4.43-28mdv2010.0.i586.rpm".<br />
<br />
<br />
<br />
{{Template:MdvImport}}<br />
[[fr:Draklive]]<br />
<br />
[[Category:Contributors]]<br />
[[Category:Howtos]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=QA_ISO_testers&diff=41922QA ISO testers2018-11-16T16:33:38Z<p>Dtux: </p>
<hr />
<div>[[Category:QA]]<br />
<br />
<br />
'''Please only add your details below if you intend to [[Pre-release_ISO_testing|test development snapshots, stabilisation shaphots, RC pre-release ISOs]] as part of the QA team or as active BugSquad member. You need to also subscribe to the [https://wiki.mageia.org/en/QA_ISO_testers qa-discuss mailing list] if you haven't done so already. It's a good idea to post a message to qa-discuss when you add your name to this list, so the change is noticed.'''<br />
<br />
=Read this before you add yourself to the list=<br />
<br />
<br />
This page is here to help us to keep in touch with you. Sorry for the list of rules but we do have to restrict access to the server.<br />
<br />
<br />
This is a necessary step as pre-release ISOs are not held on a public server, so somebody will need this information to contact you directly with further instructions and download details. Notification of pre-release ISO availability and discussion takes place on qa-discuss.<br />
<br />
<br />
The server is a development server with limited bandwidth, so please do not share the details you will be given with anybody else. Please ensure that you do not inadvertently use them in any public emails, such as those to the mailing list or on any open IRC channel or forum. <br />
<br />
<br />
It is also a good idea, but not mandatory, to leave information about the hardware you use in the [[QA_iso_hardware_list|QA hardware list]]. Please keep this information up-to-date if you choose to do so.<br />
<br />
= The list =<br />
<br />
IRC/Forums nick - Name - email address<br />
<br />
'''Please do not wipe the ones in the first three lists, unless they resigned:'''<br/><br/><br />
<br />
=='''QA-team, Bugsquad and Packaging-team leaders/council representatives:'''==<br />
* MrsB - Claire Robinson - eeeemail at gmail dot com<br />
* davidwhodgins - Dave Hodgins - davidwhodgins at gmail dot com<br />
* lewyssmith - Lewis - lewyssmith_à_onetel_point_com <br />
* wilcal - Bill Kenney - wilcal dot int at gmail dot com<br />
* stormi - Samuel Verschelde - stormi at laposte dot net<br />
* marja - Marja van Waes - marja11 at xs4all dot nl<br />
* akien - Rémi Verschelde - rverschelde@gmail.com<br />
* MageiaTJ - Thomas J Andrews - andrewsfarm at gmail dot com<br/><br/><br />
<br />
=='''Desktop environment maintainers:'''==<br />
* KDE - neoclust - Nicolas Lécureuil - neoclust at mageia dot org<br />
* KDE - daviddavid - David Geiger - geiger.david68210 at gmail dot com<br />
* Gnome - ovitters - Olav Vitters - olav at vitters dot nl<br />
* XFCE - wally_ - Jani Välimaa - wally at mageia dot org <br />
* Cinnamon - jquant - Joseph Wang - joequant at gmail dot com<br />
* Mate - tarakbumba - Atilla ÖNTAŞ - tarakbumba at gmail dot com - TO BE REPLACED. Removed from cc list<br />
* LXDE - ns80 - Nicolas Salguero - nicolas dot salguero at laposte dot net<br/><br/><br />
<br />
=='''Important iso bug squashers:'''==<br />
* coling - Colin Guthrie - mageia at colin dot guthr dot ie<br />
* tv - Thierry Vignaud - thierry dot vignaud at gmail dot com <br />
* martinw - Martin Whitaker - mageia at martin-whitaker dot me dot uk <br />
* barjac - Barry Jackson zen25000 (at) zen (dot) co (dot) uk<br />
<br/><br/><br />
<br />
=='''All other active iso-testers:'''==<br />
Adding a separate list for BugSquad iso-testers, because BugSquad needs its members so very badly that avoiding the slightest impression that they're a member of QA team seems needed.<br><br />
--[[User:Marja|marja]] 06:30, 9 February 2016 (UTC)<br />
<br />
==='''For BugSquad:'''===<br />
*Chromo - Nic Baxter - nic at nicbaxter dot com dot au<br />
<br />
==='''For Qa team:'''===<br />
Additional testers, please add your id to the end of this list in the format IRC nick, Name, email address. For example<br />
* davidwhodgins - Dave Hodgins -davidwhodgins at gmail dot com<br />
<br />
* benmc - Ben McMonagle - westel at xtra dot co nz<br />
<br />
* bri_an - Brian Rockwell - brtians1 at gmail dot com<br />
<br />
* eslrahc - Charles A Edwards - cae at eslrahc dot com<br />
<br />
* linuxero - Muhammad Tailounie - mageia at mtailounie dot net<br />
<br />
* stroibe974 - Sébastien Morin - sebsweb at gmail dot com<br />
<br />
* daviddavid - David Geiger - geiger.david68210 at gmail dot com<br />
<br />
* krisNL - Chris - shybluenight at gmail dot com<br />
<br />
*hviaene - Herman Viaene - herman dot viaene at edpnet dot be<br />
<br />
* lebarhon - André Desmottes - lebarhon at free dot fr<br />
<br />
* tarazed - Len Lawrence - tarazed25 at gmail dot com<br />
<br />
* rindolf - Shlomi Fish - shlomif at shlomifish dot org<br />
<br />
* schultz - Donald Stewart - watersnowrock at gmail dot com<br />
<br />
* dtux - Daniel Tartavel - contact at librepc dot com</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=QA_ISO_testers&diff=41921QA ISO testers2018-11-16T16:32:22Z<p>Dtux: added DTux in iso testing list</p>
<hr />
<div>[[Category:QA]]<br />
<br />
<br />
'''Please only add your details below if you intend to [[Pre-release_ISO_testing|test development snapshots, stabilisation shaphots, RC pre-release ISOs]] as part of the QA team or as active BugSquad member. You need to also subscribe to the [https://wiki.mageia.org/en/QA_ISO_testers qa-discuss mailing list] if you haven't done so already. It's a good idea to post a message to qa-discuss when you add your name to this list, so the change is noticed.'''<br />
<br />
=Read this before you add yourself to the list=<br />
<br />
<br />
This page is here to help us to keep in touch with you. Sorry for the list of rules but we do have to restrict access to the server.<br />
<br />
<br />
This is a necessary step as pre-release ISOs are not held on a public server, so somebody will need this information to contact you directly with further instructions and download details. Notification of pre-release ISO availability and discussion takes place on qa-discuss.<br />
<br />
<br />
The server is a development server with limited bandwidth, so please do not share the details you will be given with anybody else. Please ensure that you do not inadvertently use them in any public emails, such as those to the mailing list or on any open IRC channel or forum. <br />
<br />
<br />
It is also a good idea, but not mandatory, to leave information about the hardware you use in the [[QA_iso_hardware_list|QA hardware list]]. Please keep this information up-to-date if you choose to do so.<br />
<br />
= The list =<br />
<br />
IRC/Forums nick - Name - email address<br />
<br />
'''Please do not wipe the ones in the first three lists, unless they resigned:'''<br/><br/><br />
<br />
=='''QA-team, Bugsquad and Packaging-team leaders/council representatives:'''==<br />
* MrsB - Claire Robinson - eeeemail at gmail dot com<br />
* davidwhodgins - Dave Hodgins - davidwhodgins at gmail dot com<br />
* lewyssmith - Lewis - lewyssmith_à_onetel_point_com <br />
* wilcal - Bill Kenney - wilcal dot int at gmail dot com<br />
* stormi - Samuel Verschelde - stormi at laposte dot net<br />
* marja - Marja van Waes - marja11 at xs4all dot nl<br />
* akien - Rémi Verschelde - rverschelde@gmail.com<br />
* MageiaTJ - Thomas J Andrews - andrewsfarm at gmail dot com<br/><br/><br />
<br />
=='''Desktop environment maintainers:'''==<br />
* KDE - neoclust - Nicolas Lécureuil - neoclust at mageia dot org<br />
* KDE - daviddavid - David Geiger - geiger.david68210 at gmail dot com<br />
* Gnome - ovitters - Olav Vitters - olav at vitters dot nl<br />
* XFCE - wally_ - Jani Välimaa - wally at mageia dot org <br />
* Cinnamon - jquant - Joseph Wang - joequant at gmail dot com<br />
* Mate - tarakbumba - Atilla ÖNTAŞ - tarakbumba at gmail dot com - TO BE REPLACED. Removed from cc list<br />
* LXDE - ns80 - Nicolas Salguero - nicolas dot salguero at laposte dot net<br/><br/><br />
<br />
=='''Important iso bug squashers:'''==<br />
* coling - Colin Guthrie - mageia at colin dot guthr dot ie<br />
* tv - Thierry Vignaud - thierry dot vignaud at gmail dot com <br />
* martinw - Martin Whitaker - mageia at martin-whitaker dot me dot uk <br />
* barjac - Barry Jackson zen25000 (at) zen (dot) co (dot) uk<br />
<br/><br/><br />
<br />
=='''All other active iso-testers:'''==<br />
Adding a separate list for BugSquad iso-testers, because BugSquad needs its members so very badly that avoiding the slightest impression that they're a member of QA team seems needed.<br><br />
--[[User:Marja|marja]] 06:30, 9 February 2016 (UTC)<br />
<br />
==='''For BugSquad:'''===<br />
*Chromo - Nic Baxter - nic at nicbaxter dot com dot au<br />
<br />
==='''For Qa team:'''===<br />
Additional testers, please add your id to the end of this list in the format IRC nick, Name, email address. For example<br />
* davidwhodgins - Dave Hodgins -davidwhodgins at gmail dot com<br />
<br />
* benmc - Ben McMonagle - westel at xtra dot co nz<br />
<br />
* bri_an - Brian Rockwell - brtians1 at gmail dot com<br />
<br />
* eslrahc - Charles A Edwards - cae at eslrahc dot com<br />
<br />
* linuxero - Muhammad Tailounie - mageia at mtailounie dot net<br />
<br />
* stroibe974 - Sébastien Morin - sebsweb at gmail dot com<br />
<br />
* daviddavid - David Geiger - geiger.david68210 at gmail dot com<br />
<br />
* krisNL - Chris - shybluenight at gmail dot com<br />
<br />
*hviaene - Herman Viaene - herman dot viaene at edpnet dot be<br />
<br />
* lebarhon - André Desmottes - lebarhon at free dot fr<br />
<br />
* tarazed - Len Lawrence - tarazed25 at gmail dot com<br />
<br />
* rindolf - Shlomi Fish - shlomif at shlomifish dot org<br />
<br />
* schultz - Donald Stewart - watersnowrock at gmail dot com<br />
<br />
* DTux - Daniel Tartavel - contact at librepc dot com</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Events_Box&diff=41852Events Box2018-11-09T17:54:09Z<p>Dtux: next events in France</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Marcom]]<br />
[[Category:Atelier]]<br />
[[Category:Events]]<br />
<br />
We need a first, small, limited events box to help keep together tools for each event.<br />
<br />
See the [[Events HowTo]] as well.<br />
<br />
== How does the box look like? ==<br />
TODO, picture<br />
<br />
== What's in the box? ==<br />
Box contents can be donated, directly, or through http://www.mageia.org/donate/.<br />
<br />
* contents checklist including inventory (for CDs/stickers/goodies) and state of tablecloths (washed/not washed).<br />
* cash box<br />
* a pen and a notebook<br />
<br />
Showcase:<br />
* big posters with Mageia logo - we have some<br />
* kakemono - we have one (and can get extra banners if wanted); posters fit in kakemono case<br />
<br />
Distribute:<br />
* CD, DVD - we have some discs left for Mageia 1, we need a solution for Mageia 2<br />
<br />
Goodies:<br />
* tshirts - we have some left from FOSDEM 2011 - we need an inventory and new series<br />
* stationery (stickers, contact list, flyers, contact cards/business cards, blank pre-printed CDs (to burn on the stand), CD sleeves) - we have some left - we need new ones - for booth and to distribute to attendees when one speaks at a conference<br />
<br />
== Where is the box? ==<br />
<br />
=== Current location of the box ===<br />
<br />
=== Current goodies around Europe ===<br />
{|+class="wikitable"<br />
|-<br />
|Country | city | T-shirts | stickers | flyers | USB Keys | pens | Tablecloth | kakemono | others |<br />
|-<br />
|France | Lyon | 16 x S - 25 x M - 23 x L - XL x 1 - XXL x 3 - ladies - S x 5 - M x 13 - L x 5 - 3 x XL | 18 USB key | 66 Pens | 1 tablecloth | 1 kakemono |<br />
|-<br />
|}<br />
<br />
=== Next, planned locations ===<br />
Campus du Libre - november, 10 2018 - Lyon France<br />
Capitole du Libre - november, 17-18 2018 - Toulouse France<br />
Paris Open Source Summit - december, 5-6 2018 - Paris France<br />
JM2L - december,15 2018 - Sophia-anitpolis - France<br />
<br />
=== Base locations ===<br />
Ideally, two locations, in France or in its direct periphery. Events that we will attend with this box are among: FOSDEM, LinuxTag, Solutions Linux, RMLL, OWF, JDLL, ORR, what others in Europe?<br />
<br />
=== Transportation costs ===<br />
Use these max limits to estimate roughly the cost:<br />
* weight: 10 kg<br />
* dimensions: 55 x 35 x 25 cm<br />
* declared value: 3000 €<br />
<br />
* cities: Paris, Marseille, Bordeaux, Nantes, Berlin, Bruxelles, London, Barcelona, Madrid, Rome, Lisbon<br />
Indicative average max prices (UPS - https://wwwapps.ups.com/ctc/request):<br />
* Paris -> {Brussel,Berlin}, ~300 €<br />
* Nantes -> Paris, ~100 € (about the same intra France?)<br />
<br />
* 10kg 120 x 60 x 60 cm 6,90€ (intra Germany), 22,00€ Germany->France (http://www.dhl.de/en.html)<br />
<br />
The actual cost may be less (the box may be lighter, smaller) or more (change in transportation fees).<br />
<br />
=== Asking for the box ===<br />
Wanted home candidates (multiple is better):<br />
* Nantes, FR: rda<br />
* Paris, FR: baud (Versailles, for SL, RMLL, PremierSamedi])<br />
* Berlin, DE: ?<br />
* Brussel, BE: ?<br />
* Lyon<br />
* other?<br />
<br />
== Grow the box! ==<br />
<br />
Here are other stuff good to have in the box.<br />
<br />
The whole package (box + contents) must not exceed 10 kg and must keep 55 x 35 x 25 cm (easier for someone to travel with it).<br />
<br />
* BOX itself (wish, no model/size decided) a box to fit all this, that can be handled by a single person, that has wheels and handles. Suggest medium (20kg, international roll-on size or a little larger) suitcase with at least one zipper poclet on the outside (for padlock &c during shipping).<br />
<br />
* (wish) event schedule and [[Events HowTo|howto]] (in this very wiki at least; a print copy is good too)<br />
* (wish) two large pieces of cloth: one white, one black. (see tablecloths in showcase. Black may be redundant...)<br />
* (wish) cables? RJ45, video, USB, multi powerplugs, type <br />
* (wish) small medikit, scissors, thread<br />
* (wish) velcro dots (both hook and fuzz), with adhesive back, two types (standard and strong)<br />
* (wish) good-quality packaging tape in tape-gun<br />
* (wish) good brass padlock to lock suitcase when travelling with someone<br />
* (wish) cycle lock (click-together type with coated cable or chain) to lock Events Box to racks on trains - prevent theft of Box<br />
<br />
Showcase stuff:<br />
* (must have) - 2 tablecloths for exhibition tables, white with mageia logo placed to be at front of table, sized for 2 180cm long x 90cm wide x 80cm high tables (so, (2*180)+(2*80) long and 90+(2*80) wide.) Mageia logo can be on vinyl like banner and poster, and be fixed with double-sided tape or velcro, or can be printed onto the cloth.<br />
* (wish) perspex or portable/foldable metal display stands for leaflets/brochures/cds. Metal will stand on floor beside tables, perspex on table (so metal might work better).<br />
* (wish, no model decided, price tag max 300 €) dedicated projector<br />
* (wish, no model decided, price tag max 200 € each) 2 dedicated laptops or small boxes (cubox, other?): one for projection, the other one for direct manipulation<br />
** one potential candidate, white ASRock Ion330 + keyboard + mouse and cables (second hand, ~150 € worth, rda)<br />
* for projection:<br />
** (wish) simple slides calling for contributors, with specific & easy tasks,<br />
** (wish) project presentation, demonstrating the product,<br />
** (wish) give immediate contact hooks (Web, IRC, Twitter, other events)<br />
** (wish) display a small twitter wall of the current event<br />
<br />
Distribute:<br />
* (wish) a system to dump a Mageia system image to USB key or portable HD<br />
* (wish) mageia-logo USB sticks<br />
* (idea) one of the computer is used either as a Wi-Fi access point (advertised as "Get Mageia") or as a station in the local network, and advertises shared directories (FTP, Samba) containing Mageia ISOs<br />
<br />
<br />
* interactive, live access to forums, IRC channels and other info source about the project<br />
** Maybe a projector connected to a laptop? Maybe more than one? Forums, wiki, an event-central IRC channel? I think a projector displaying a live feed of #mageia-social would be a good place to start. --[[User:Max|max]] 19:56, 16 July 2012 (UTC)<br />
* computers/projectors showcasing the OS: laptops, tablets, projectors<br />
<br />
<br />
== Other projects events boxes ==<br />
* http://live.gnome.org/GnomeEventsBox<br />
* other ?<br />
<br />
== Other ideas of goodies ==<br />
* USB key <br />
** 4 GB should be enough, ~5 € and could be proposed at 10 € with Mageia logo<br />
** http://www.memoriasusb.com<br />
* USB card<br />
** was here at Fosdem 2013, not seen since :/ 2 GB card with Mageia logo<br />
* stickers<br />
** see https://wiki.mageia.org/en/Commercial_vendors#Goodies_vendors<br />
<br />
== Documents to promote Mageia ==<br />
<br />
<br />
* stickers (meta-key, powered by, GNU/Linux Mageia logo) : http://download.tuxfamily.org/cauldron/mageia/logo/<br />
* prez : http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7A.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/FOSDEM%202014%20Flyer.odt french and english versions<br />
* http://www.mageia.org/about/media/ mainly logo & CD/DVD covers, available in SVG<br />
* FOSDEM 2015 flyer: [[File:Mageia_flyer_2015_EN.odt]]<br />
* http://stormi.lautre.net/fichiers/jdll/2015/ french and english version showed at JDLL 2015</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Events_Box&diff=41851Events Box2018-11-09T17:02:14Z<p>Dtux: </p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Marcom]]<br />
[[Category:Atelier]]<br />
[[Category:Events]]<br />
<br />
We need a first, small, limited events box to help keep together tools for each event.<br />
<br />
See the [[Events HowTo]] as well.<br />
<br />
== How does the box look like? ==<br />
TODO, picture<br />
<br />
== What's in the box? ==<br />
Box contents can be donated, directly, or through http://www.mageia.org/donate/.<br />
<br />
* contents checklist including inventory (for CDs/stickers/goodies) and state of tablecloths (washed/not washed).<br />
* cash box<br />
* a pen and a notebook<br />
<br />
Showcase:<br />
* big posters with Mageia logo - we have some<br />
* kakemono - we have one (and can get extra banners if wanted); posters fit in kakemono case<br />
<br />
Distribute:<br />
* CD, DVD - we have some discs left for Mageia 1, we need a solution for Mageia 2<br />
<br />
Goodies:<br />
* tshirts - we have some left from FOSDEM 2011 - we need an inventory and new series<br />
* stationery (stickers, contact list, flyers, contact cards/business cards, blank pre-printed CDs (to burn on the stand), CD sleeves) - we have some left - we need new ones - for booth and to distribute to attendees when one speaks at a conference<br />
<br />
== Where is the box? ==<br />
<br />
=== Current location of the box ===<br />
<br />
=== Current goodies around Europe ===<br />
{|+class="wikitable"<br />
|-<br />
|Country | city | T-shirts | stickers | flyers | USB Keys | pens | Tablecloth | kakemono | others |<br />
|-<br />
|France | Lyon | 16 x S - 25 x M - 23 x L - XL x 1 - XXL x 3 - ladies - S x 5 - M x 13 - L x 5 - 3 x XL | 18 USB key | 66 Pens | 1 tablecloth | 1 kakemono |<br />
|-<br />
|}<br />
<br />
=== Next, planned locations ===<br />
<br />
=== Base locations ===<br />
Ideally, two locations, in France or in its direct periphery. Events that we will attend with this box are among: FOSDEM, LinuxTag, Solutions Linux, RMLL, OWF, JDLL, ORR, what others in Europe?<br />
<br />
=== Transportation costs ===<br />
Use these max limits to estimate roughly the cost:<br />
* weight: 10 kg<br />
* dimensions: 55 x 35 x 25 cm<br />
* declared value: 3000 €<br />
<br />
* cities: Paris, Marseille, Bordeaux, Nantes, Berlin, Bruxelles, London, Barcelona, Madrid, Rome, Lisbon<br />
Indicative average max prices (UPS - https://wwwapps.ups.com/ctc/request):<br />
* Paris -> {Brussel,Berlin}, ~300 €<br />
* Nantes -> Paris, ~100 € (about the same intra France?)<br />
<br />
* 10kg 120 x 60 x 60 cm 6,90€ (intra Germany), 22,00€ Germany->France (http://www.dhl.de/en.html)<br />
<br />
The actual cost may be less (the box may be lighter, smaller) or more (change in transportation fees).<br />
<br />
=== Asking for the box ===<br />
Wanted home candidates (multiple is better):<br />
* Nantes, FR: rda<br />
* Paris, FR: baud (Versailles, for SL, RMLL, PremierSamedi])<br />
* Berlin, DE: ?<br />
* Brussel, BE: ?<br />
* Lyon<br />
* other?<br />
<br />
== Grow the box! ==<br />
<br />
Here are other stuff good to have in the box.<br />
<br />
The whole package (box + contents) must not exceed 10 kg and must keep 55 x 35 x 25 cm (easier for someone to travel with it).<br />
<br />
* BOX itself (wish, no model/size decided) a box to fit all this, that can be handled by a single person, that has wheels and handles. Suggest medium (20kg, international roll-on size or a little larger) suitcase with at least one zipper poclet on the outside (for padlock &c during shipping).<br />
<br />
* (wish) event schedule and [[Events HowTo|howto]] (in this very wiki at least; a print copy is good too)<br />
* (wish) two large pieces of cloth: one white, one black. (see tablecloths in showcase. Black may be redundant...)<br />
* (wish) cables? RJ45, video, USB, multi powerplugs, type <br />
* (wish) small medikit, scissors, thread<br />
* (wish) velcro dots (both hook and fuzz), with adhesive back, two types (standard and strong)<br />
* (wish) good-quality packaging tape in tape-gun<br />
* (wish) good brass padlock to lock suitcase when travelling with someone<br />
* (wish) cycle lock (click-together type with coated cable or chain) to lock Events Box to racks on trains - prevent theft of Box<br />
<br />
Showcase stuff:<br />
* (must have) - 2 tablecloths for exhibition tables, white with mageia logo placed to be at front of table, sized for 2 180cm long x 90cm wide x 80cm high tables (so, (2*180)+(2*80) long and 90+(2*80) wide.) Mageia logo can be on vinyl like banner and poster, and be fixed with double-sided tape or velcro, or can be printed onto the cloth.<br />
* (wish) perspex or portable/foldable metal display stands for leaflets/brochures/cds. Metal will stand on floor beside tables, perspex on table (so metal might work better).<br />
* (wish, no model decided, price tag max 300 €) dedicated projector<br />
* (wish, no model decided, price tag max 200 € each) 2 dedicated laptops or small boxes (cubox, other?): one for projection, the other one for direct manipulation<br />
** one potential candidate, white ASRock Ion330 + keyboard + mouse and cables (second hand, ~150 € worth, rda)<br />
* for projection:<br />
** (wish) simple slides calling for contributors, with specific & easy tasks,<br />
** (wish) project presentation, demonstrating the product,<br />
** (wish) give immediate contact hooks (Web, IRC, Twitter, other events)<br />
** (wish) display a small twitter wall of the current event<br />
<br />
Distribute:<br />
* (wish) a system to dump a Mageia system image to USB key or portable HD<br />
* (wish) mageia-logo USB sticks<br />
* (idea) one of the computer is used either as a Wi-Fi access point (advertised as "Get Mageia") or as a station in the local network, and advertises shared directories (FTP, Samba) containing Mageia ISOs<br />
<br />
<br />
* interactive, live access to forums, IRC channels and other info source about the project<br />
** Maybe a projector connected to a laptop? Maybe more than one? Forums, wiki, an event-central IRC channel? I think a projector displaying a live feed of #mageia-social would be a good place to start. --[[User:Max|max]] 19:56, 16 July 2012 (UTC)<br />
* computers/projectors showcasing the OS: laptops, tablets, projectors<br />
<br />
<br />
== Other projects events boxes ==<br />
* http://live.gnome.org/GnomeEventsBox<br />
* other ?<br />
<br />
== Other ideas of goodies ==<br />
* USB key <br />
** 4 GB should be enough, ~5 € and could be proposed at 10 € with Mageia logo<br />
** http://www.memoriasusb.com<br />
* USB card<br />
** was here at Fosdem 2013, not seen since :/ 2 GB card with Mageia logo<br />
* stickers<br />
** see https://wiki.mageia.org/en/Commercial_vendors#Goodies_vendors<br />
<br />
== Documents to promote Mageia ==<br />
<br />
<br />
* stickers (meta-key, powered by, GNU/Linux Mageia logo) : http://download.tuxfamily.org/cauldron/mageia/logo/<br />
* prez : http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7A.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2017_Flyer_enfr_7.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.odt source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/FOSDEM%202014%20Flyer.odt french and english versions<br />
* http://www.mageia.org/about/media/ mainly logo & CD/DVD covers, available in SVG<br />
* FOSDEM 2015 flyer: [[File:Mageia_flyer_2015_EN.odt]]<br />
* http://stormi.lautre.net/fichiers/jdll/2015/ french and english version showed at JDLL 2015</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Local_Communities_Team&diff=39993Local Communities Team2018-06-09T13:54:49Z<p>Dtux: /* Russia */ [http://mageialinux.ru/ http://mageialinux.ru/] content has no relations with Mageia</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Local communities]]<br />
<br />
<br />
== Join/contact the team ==<br />
* Add your name below under your country (please add your country, too, if it isn't in the list, yet)<br />
'''- Please use the template as shown below! - '''<br />
* sign up for [https://ml.mageia.org/l/review/local-discuss the local-discuss mailing list]<br />
* We are now organizing the team, please join our [https://ml.mageia.org/l/review/local-discuss ml] if you want to help.<br />
* join irc://irc.freenode.net/#mageia<br />
* '''''team leader:'' Otto Sá (otto)'''<br />
* '''''deputy team leader:'' Oliver Burger (obgr_seneca)'''<br />
<br />
<br />
<br />
Register below for the Local Communities Team: help to spread Mageia in different users groups, manage communication and relations with development team, work with atelier team...<br />
<br />
'''Use the following template to register:'''<br />
* <FirstName Lastname> (<nick>) - <email> - <how you can help><br />
<br />
''' For example: '''<br />
* <AbdusSalam> (<Barket>) - <abdussalam.bd09@gmail.com> - <Marketing><br />
<br />
'''Please insert your name in alphabetic order.'''<br />
<br />
== List of registered people ==<br />
<br />
=== Australia ===<br />
<br />
* Trish Fraser (trishf42) - press@ contact and user help for Mageia users in Australia/NZ<br />
<br />
=== Bangladesh ===<br />
* AbdusSalam - barket - abdussalam.bd09@gmail.com - Help Bangladeshi to introduce Mandriva inshaAllah.<br />
* Muntasim-Ul-Haque (Jeeshan) - tranjeeshan@gmail.com - Encourage people to use Mageia in Bangladesh.<br />
<br />
=== Belgium ===<br />
<br />
For Flemish part, see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Brazil ===<br />
* Adjamilton Júnior - ajunior at brasifort.com.br - i18n-pt_BR Team Leader. Help with brazilian free software community.<br />
* Aracele Torres - araceletorres at gmail.com - Help with brazilian free software community.<br />
* Filipe Saraiva - filip.saraiva at gmail.com - Help with brazilian free software community.<br />
* Lucas Emanoel - <del>lucasemanoel AT valedosambito DOT com</del> - Help with brazilian free software community.<br />
** ''Mail bounced:'' <code>550 #5.1.0 Address rejected</code><br />
* Paulo Ricardo G de Oliveira - User and student programming "C and PHP".<br />
* Otto Sa – ottosa at gmail.com - the Founder of Mageia do Brazil (ex MageiaBr) at http://mageiadobrasil.com.br/portal/ , the support forum located at http://www.mageiadobrasil.com.br/forum/index.php and The Mageia do Brasil wiki at http://www.mageiadobrasil.com.br/wiki/doku.php<br />
* Márcio Padula (Padula) - padula1000 at gmail.com - i-18n-pt_BR team translator, Mageia do Brasil webmaster and administrator (who made the New Mageia do Brasil) .<br />
* macxi - terra agua at gmail com, documentation, translation and community support.<br />
<br />
=== Canada ===<br />
* Glen Millard - bartockbat - szilverthorne AT gmail DOT com - Need a presence in The Great White North - help with FSF in Canada<br />
* J.P. Pasnak - Linegod - pasnak AT warpedsystems DOT sk Dot ca - work with Canadian LUGs<br />
<br />
=== China, Mainland of (PRC) ===<br />
* Jiang Yike - futureway (at) asia.com - The Chinese Community of Mageia and Mandriva Linux<br />
=== Dutch language ===<br />
<br />
* Maarten Vanraes - AL13N<br />
* Marja van Waes - marja<br />
* Remco Rijnders - remmy<br />
<br />
=== English Speaking International Users Community ===<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Glen Millard - szilverthorne AT gmail DOT com - Let me know what you need!<br />
* Paul Willard - paul at loudas dot com - English community manager<br />
<br />
=== Finland ===<br />
* Renni Reposalo - renni at pcuf dot fi - Finnish community<br />
<br />
=== France ===<br />
* Arnaud Vacquier (aranud87/aranud) - aranud at mageia-debutant.fr (PGP:0xFBC19522) Admin mageia-debutant.fr<br />
* Benoît Audouard (baud123) - baud123 at tuxfamily.org Moderator LinuxFr.org & French community, advertising at events, support on irc chans either in english, french, spanish, cooperation/contact with international communities possible<br />
* Frank Kober (dharanamrs) - goemusic#yahoo#fr - interactions with international and French linux audio user communities (linuxaudio.org, linuxmao.org)<br />
* Frédéric Cuif - fredux86 AT gmail.com - French community, law team, comm team <br />
* Jean-Luc CINELLI (Enzolyte) - enzolyte AT mageialinux-online DOT org - Admin MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Marianne Lombard (jehane) - jehane at tuxette dot fr - french community, advertising Mageia on events, organising stands on events, translations, support on irc chans (french and english)<br />
* Michael Scherer (misc) - misc@zarb.org - packaging community, ex cooker chef<br />
* Olivier Méjean (goom) - omejean at yahoo.fr - French community, relation with devel team, comm team; Mageia community magazine<br />
* Pascal VERDIEL (yopman) - Admin MLO,a forum dedicated to help beginners and spread the word of Mageia.(French community) <br />
* Patrick DUBEAU (DaaX) - daax at mageialinux-online dot org - Webmaster MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Roddy FOLETTE - <del>roddy.folette@rfconseilsinfos.com</del> (French community : dedicated to help beginners and spread the word of Mageia in Réunion, ile Maurice and around the Indian Ocean countries)<br />
**''E-mail address bounces:'' <code>DNS Error: Domain name not found</code><br />
* Thomas Lottmann (Skiper) - skiperdrake AT gmail DOT com - French community, communication, advertising and events, interacting with international and french communities, working and helping various community projects. <br />
* Yvan Munoz (muny) mr.yvan.munoz@gmail.com (French Community : atmosphere)<br />
* Jean Marie Dubosc (JMGLV) -jean.marie.dubosc_at_gmail-dot_com -French Community-<br />
* LSDM (Yves Specht) - lsdm@laposte.net -<br />
<br />
=== German (not just Germany) ===<br />
* Florian Hubold (doktor5000) - doktor5000 AT arcor DOT de - German community: moderate forum, interacting with international community<br />
* Oliver Burger (obgr_seneca) - oliver.bgr AT gmail DOT com - German community: moderate forum, advertising Mageia on events, interacting with international community<br />
* Wolfgang Bornath (wobo) - molch.b@googlemail.com - founder & admin of the German Mandriva user community, regular participation at German events, interested in international communication<br />
<br />
=== Greece ===<br />
* Dimitrios Glentadakis (dglent) - dglent@gmail.com - Greek community (mageia-gr.org)<br />
* Dimitris Tsiamasiotis (dtsiamasiotis) - dtsiamasiotis AT gmail.com - Greek community<br />
* Xaris Yfantis (Xaris) - <del>sinzoda1 (AT) otenet (DOT) gr</del> - Greek community<br />
**''Mail bounced:'' <code>550 5.1.1 ... Usern unknown</code><br />
<br />
=== India ===<br />
* Anshul Jain (anshuljain) - anshulajain (at) gmail (dot) com- Promotion at various Linux User Groups in India, communicating with the corporate world for Linux as a desktop & deployment platform <br />
<br />
=== Iran ===<br />
* Mahmoud Fereydouni (fereydouni) - fereydouni (at) gmail (dot) com, admin (at) mageia (dot) ir - Persian Users Community Founder & Manager, Translator, Customized package developer and QA.<br />
<br />
=== Indonesia ===<br />
* Luthfi Emka (panahbiru) - panahbiru at gmail dot com - Indonesian Mageia Blogs and Forums (mageia.web.id)<br />
* Muhamad Abdullkadir - muhamad at iscs dot cc - Spread Mageia in Indonesia<br />
<br />
=== Italy ===<br />
* Angelo Naselli - anaselli at linux dot it - packager, developer, mentor, Italian community member (mageia online - mageiaonline.it). <br />
* Marcello Anni - marcello.anni at alice dot it - Italian community: translations, howtos, relation with devel team, relation with international communities, moderate forum, PR, press releases<br />
* Matteo Pasotti - matteo dot pasotti at gmail dot com - packager, developer, translator, Italian community member (mageia online - mageiaonline.it).<br />
* Stefano Negro - stblack at gmail.com - translator, tester at QA team<br />
<br />
=== Netherlands, The ===<br />
<br />
see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Norway ===<br />
* Olav Dahlum (olorin_) - odahlum at gmail dot com - Norwegian community member<br />
<br />
=== Pakistan ===<br />
* M Younis Soomro (mysoomro) - myounis.mcs@gmail.com - Trying to introduce and spread Linux (Mageia & other distros) in Pakistan.<br />
<br />
=== Paraguay ===<br />
* KSEltar (kseltar) - kseltar(at)gmail.com - Deshn FLOSS community: promotion of Mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Poland ===<br />
* Daniel Napora (napcok) - napcok at gmail dot com - Polish community ([http://mageia.org.pl])<br />
<br />
=== Portugal ===<br />
* Manuela Silva - alfalb - manuelaDOTsilvaATskyDOTcom - Interpreter/translator and proof-reader<br />
* Alfredo Silva - alfalb - alfalbDOTasATgmailDOTcom - Translator and proof-reader<br />
<br />
=== Romania ===<br />
* Cazacu Bogdan (Bogo) - cazacu DOT bogdan AT gmail DOT com - Romanian community. forum moderation, achieving deadlines as part of the romanian group for the international group.<br />
* Florin Cătălin RUSSEN (Piratu) - cfrussen AT yahoo DOT co DOT uk - Romanian community: moderate forum, interacting with international community<br />
* Florin Pulbere (Gremlin) - kernelgremlin AT gmail DOT com - Romanian community.<br />
<br />
=== Russia ===<br />
* Eugene Zhuravlev (macdowell) - macdowell AT cybsec DOT org - Russian community<br />
* Mitya (mitya) - mitya AT cargosoft DOT ru - promotion at Russian opensource news sites (linux.org.ru), #mageia-ru<br />
* ?? (tejen) - ?? - Mageia website and forum<br />
* Alexey Dolotov (sevo44) - dolotov44 AT yandex DOT ru - wants to help take good care of the Russian forums and wiki, including of security (ssl certificate and back-ups) and considers moving forums and wiki to a different domain to be able to do that <!--https://forum.mageia-linux.ru/ https://wiki.mageia-linux.ru/--><br />
<br />
=== Serbia ===<br />
* Toma Janković (tomaja) - tomaja@linuxo.org - Serbian community: promotion of mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Slovenia ===<br />
* Filip Komar (filip) - filip(at)mageia.org - translation<br />
<br />
=== South Africa ===<br />
* Rory Albertyn (Gripen) - nicodeamus(at)gmail.com - South African community<br />
<br />
=== Spanish (not just Spain) ===<br />
* barsalatino - barsalatino - barsalatino@gmail.com - Spanish-speaking community (Blogdrake)<br />
* Drakedalfa - drakedalfa - drakedalfa at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Diego Bello - jacen - dbello at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Felix Martos (asinkeBOFH) - felix.martos AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Fernando Anthony Ristaño (Drakor) - drakorbofh AT gmail DOT com - Spanish-speaking community (Blogdrake) and Argentina community (Ardriva) - - promoting mageia on events in Argentina<br />
* Gonzalo Igartua (GregoryBravas) - <del>gigartua@ AT mail.com DOT</del> - Spanish-speaking community (BlogDrake)<br />
** ''E-mail bounces when leaving out the dot "." after "com"'' <code>550 5.1.1 ... User is unknown {mx-us011}</code> <br />
* Sinner from the Prairy (SinnerBOFH) - sinnerbofh AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Tomàs Deltell (Annubis) - tomasdeltell AT gmx DOT es - Spanish-speaking community (Blogdrake)<br />
* vfmBOFH - vfmBOFH - vfmbofh(at)gmail.com - Spanish-speaking community (Blogdrake)<br />
<br />
Available domain names: mageia-es.org, mageia.com.ar<br />
<br />
=== Swedish (not just Sweden) ===<br />
* David V. Wallin (dvwallin) - <del>david AT ngweb DOT se</del> <br />
** ''E-mail bounced:'' <code>DNS Error: Domain name not found</code><br />
* Kristoffer Grundström (Umeaboy) - kristoffer dot grundstrom 1983 at gmail dot com - Founder and operator of the Swedish IRC-channels #mageia-sv and mageia-se<br />
* Sebastian (sebsebseb) - #mageia-sv and #mageia-se - Swedish Channels IRC Operator<br />
<br />
=== Taiwan ===<br />
[http://groups.google.com/group/mageia-taiwan Mageia Taiwanese user group]<br />
* 姚智偉 (kira) - elegant . pegasus AT gmail . com = Taiwanese user group moderator.<br />
* You-Cheng Hsieh (yochenhsieh) - yochenhsieh AT gmail . com - Taiwanese user group moderator.<br />
<br />
=== Turkey ===<br />
* Atilla ÖNTAŞ - <tarakbumba> - tarakbumba@gmail.com - Turkish community (Mandriva Turkiye).<br />
<br />
=== Tunisia ===<br />
* Beltaif Belgacem - <Gasston> - beltaif_bel@live.fr - Tunisia community.<br />
<br />
=== United Arab Emirates === <br />
* Ali Jawad (theforsaken) - amjjawad AT gmail DOT com - Ready for anything to help out, just let me know.<br />
<br />
=== United Kingdom ===<br />
* Margot Lawrence - margot at otfordduckscomputers.co.uk - IRC #mageia-uk & user help for people physically located in the UK<br />
* Sebastian (sebsebseb) - #mageia-uk irc channel - UK Users Community Founder<br />
<br />
=== United States ===<br />
* Alan Augustson (VoodooDali) - alan DOT augustson AT gmail DOT com - Chicago, IL, US. Longtime Mandriva user, interested in communications, marketing and artwork. NOT a programmer/developer; more like an advanced user.<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Kevin E. Ivey (lnxguy) - ik04[at]isot.com - Longtime Mandrake/Mandriva user and supporter since Day One. Founder of the Fort Hood Area Linux Users Group- HoodLUG. Active in advocacy efforts for Linux/FOSS.<br />
* Tracy W. Holz - tracy[at]htredneck.com - Live in the Dallas area, Involved in the Open Source/Linux podcast area, I go by the nick - Holzster<br />
* Josh King (dotmil) - josh AT dotmil.org - Abilene, TX area; working within F/OSS for nearly a decade now. Professional system admin, part time hacker and jack of many trades</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Local_Communities_Team&diff=39991Local Communities Team2018-06-09T13:48:46Z<p>Dtux: [http://mageia.nl/cgi-bin/mailman/listinfo/vraagje Dutch mailing list] not existing anymore</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Local communities]]<br />
<br />
<br />
== Join/contact the team ==<br />
* Add your name below under your country (please add your country, too, if it isn't in the list, yet)<br />
'''- Please use the template as shown below! - '''<br />
* sign up for [https://ml.mageia.org/l/review/local-discuss the local-discuss mailing list]<br />
* We are now organizing the team, please join our [https://ml.mageia.org/l/review/local-discuss ml] if you want to help.<br />
* join irc://irc.freenode.net/#mageia<br />
* '''''team leader:'' Otto Sá (otto)'''<br />
* '''''deputy team leader:'' Oliver Burger (obgr_seneca)'''<br />
<br />
<br />
<br />
Register below for the Local Communities Team: help to spread Mageia in different users groups, manage communication and relations with development team, work with atelier team...<br />
<br />
'''Use the following template to register:'''<br />
* <FirstName Lastname> (<nick>) - <email> - <how you can help><br />
<br />
''' For example: '''<br />
* <AbdusSalam> (<Barket>) - <abdussalam.bd09@gmail.com> - <Marketing><br />
<br />
'''Please insert your name in alphabetic order.'''<br />
<br />
== List of registered people ==<br />
<br />
=== Australia ===<br />
<br />
* Trish Fraser (trishf42) - press@ contact and user help for Mageia users in Australia/NZ<br />
<br />
=== Bangladesh ===<br />
* AbdusSalam - barket - abdussalam.bd09@gmail.com - Help Bangladeshi to introduce Mandriva inshaAllah.<br />
* Muntasim-Ul-Haque (Jeeshan) - tranjeeshan@gmail.com - Encourage people to use Mageia in Bangladesh.<br />
<br />
=== Belgium ===<br />
<br />
For Flemish part, see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Brazil ===<br />
* Adjamilton Júnior - ajunior at brasifort.com.br - i18n-pt_BR Team Leader. Help with brazilian free software community.<br />
* Aracele Torres - araceletorres at gmail.com - Help with brazilian free software community.<br />
* Filipe Saraiva - filip.saraiva at gmail.com - Help with brazilian free software community.<br />
* Lucas Emanoel - <del>lucasemanoel AT valedosambito DOT com</del> - Help with brazilian free software community.<br />
** ''Mail bounced:'' <code>550 #5.1.0 Address rejected</code><br />
* Paulo Ricardo G de Oliveira - User and student programming "C and PHP".<br />
* Otto Sa – ottosa at gmail.com - the Founder of Mageia do Brazil (ex MageiaBr) at http://mageiadobrasil.com.br/portal/ , the support forum located at http://www.mageiadobrasil.com.br/forum/index.php and The Mageia do Brasil wiki at http://www.mageiadobrasil.com.br/wiki/doku.php<br />
* Márcio Padula (Padula) - padula1000 at gmail.com - i-18n-pt_BR team translator, Mageia do Brasil webmaster and administrator (who made the New Mageia do Brasil) .<br />
* macxi - terra agua at gmail com, documentation, translation and community support.<br />
<br />
=== Canada ===<br />
* Glen Millard - bartockbat - szilverthorne AT gmail DOT com - Need a presence in The Great White North - help with FSF in Canada<br />
* J.P. Pasnak - Linegod - pasnak AT warpedsystems DOT sk Dot ca - work with Canadian LUGs<br />
<br />
=== China, Mainland of (PRC) ===<br />
* Jiang Yike - futureway (at) asia.com - The Chinese Community of Mageia and Mandriva Linux<br />
=== Dutch language ===<br />
<br />
* Maarten Vanraes - AL13N<br />
* Marja van Waes - marja<br />
* Remco Rijnders - remmy<br />
<br />
=== English Speaking International Users Community ===<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Glen Millard - szilverthorne AT gmail DOT com - Let me know what you need!<br />
* Paul Willard - paul at loudas dot com - English community manager<br />
<br />
=== Finland ===<br />
* Renni Reposalo - renni at pcuf dot fi - Finnish community<br />
<br />
=== France ===<br />
* Arnaud Vacquier (aranud87/aranud) - aranud at mageia-debutant.fr (PGP:0xFBC19522) Admin mageia-debutant.fr<br />
* Benoît Audouard (baud123) - baud123 at tuxfamily.org Moderator LinuxFr.org & French community, advertising at events, support on irc chans either in english, french, spanish, cooperation/contact with international communities possible<br />
* Frank Kober (dharanamrs) - goemusic#yahoo#fr - interactions with international and French linux audio user communities (linuxaudio.org, linuxmao.org)<br />
* Frédéric Cuif - fredux86 AT gmail.com - French community, law team, comm team <br />
* Jean-Luc CINELLI (Enzolyte) - enzolyte AT mageialinux-online DOT org - Admin MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Marianne Lombard (jehane) - jehane at tuxette dot fr - french community, advertising Mageia on events, organising stands on events, translations, support on irc chans (french and english)<br />
* Michael Scherer (misc) - misc@zarb.org - packaging community, ex cooker chef<br />
* Olivier Méjean (goom) - omejean at yahoo.fr - French community, relation with devel team, comm team; Mageia community magazine<br />
* Pascal VERDIEL (yopman) - Admin MLO,a forum dedicated to help beginners and spread the word of Mageia.(French community) <br />
* Patrick DUBEAU (DaaX) - daax at mageialinux-online dot org - Webmaster MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Roddy FOLETTE - <del>roddy.folette@rfconseilsinfos.com</del> (French community : dedicated to help beginners and spread the word of Mageia in Réunion, ile Maurice and around the Indian Ocean countries)<br />
**''E-mail address bounces:'' <code>DNS Error: Domain name not found</code><br />
* Thomas Lottmann (Skiper) - skiperdrake AT gmail DOT com - French community, communication, advertising and events, interacting with international and french communities, working and helping various community projects. <br />
* Yvan Munoz (muny) mr.yvan.munoz@gmail.com (French Community : atmosphere)<br />
* Jean Marie Dubosc (JMGLV) -jean.marie.dubosc_at_gmail-dot_com -French Community-<br />
* LSDM (Yves Specht) - lsdm@laposte.net -<br />
<br />
=== German (not just Germany) ===<br />
* Florian Hubold (doktor5000) - doktor5000 AT arcor DOT de - German community: moderate forum, interacting with international community<br />
* Oliver Burger (obgr_seneca) - oliver.bgr AT gmail DOT com - German community: moderate forum, advertising Mageia on events, interacting with international community<br />
* Wolfgang Bornath (wobo) - molch.b@googlemail.com - founder & admin of the German Mandriva user community, regular participation at German events, interested in international communication<br />
<br />
=== Greece ===<br />
* Dimitrios Glentadakis (dglent) - dglent@gmail.com - Greek community (mageia-gr.org)<br />
* Dimitris Tsiamasiotis (dtsiamasiotis) - dtsiamasiotis AT gmail.com - Greek community<br />
* Xaris Yfantis (Xaris) - <del>sinzoda1 (AT) otenet (DOT) gr</del> - Greek community<br />
**''Mail bounced:'' <code>550 5.1.1 ... Usern unknown</code><br />
<br />
=== India ===<br />
* Anshul Jain (anshuljain) - anshulajain (at) gmail (dot) com- Promotion at various Linux User Groups in India, communicating with the corporate world for Linux as a desktop & deployment platform <br />
<br />
=== Iran ===<br />
* Mahmoud Fereydouni (fereydouni) - fereydouni (at) gmail (dot) com, admin (at) mageia (dot) ir - Persian Users Community Founder & Manager, Translator, Customized package developer and QA.<br />
<br />
=== Indonesia ===<br />
* Luthfi Emka (panahbiru) - panahbiru at gmail dot com - Indonesian Mageia Blogs and Forums (mageia.web.id)<br />
* Muhamad Abdullkadir - muhamad at iscs dot cc - Spread Mageia in Indonesia<br />
<br />
=== Italy ===<br />
* Angelo Naselli - anaselli at linux dot it - packager, developer, mentor, Italian community member (mageia online - mageiaonline.it). <br />
* Marcello Anni - marcello.anni at alice dot it - Italian community: translations, howtos, relation with devel team, relation with international communities, moderate forum, PR, press releases<br />
* Matteo Pasotti - matteo dot pasotti at gmail dot com - packager, developer, translator, Italian community member (mageia online - mageiaonline.it).<br />
* Stefano Negro - stblack at gmail.com - translator, tester at QA team<br />
<br />
=== Netherlands, The ===<br />
<br />
see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Norway ===<br />
* Olav Dahlum (olorin_) - odahlum at gmail dot com - Norwegian community member<br />
<br />
=== Pakistan ===<br />
* M Younis Soomro (mysoomro) - myounis.mcs@gmail.com - Trying to introduce and spread Linux (Mageia & other distros) in Pakistan.<br />
<br />
=== Paraguay ===<br />
* KSEltar (kseltar) - kseltar(at)gmail.com - Deshn FLOSS community: promotion of Mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Poland ===<br />
* Daniel Napora (napcok) - napcok at gmail dot com - Polish community ([http://mageia.org.pl])<br />
<br />
=== Portugal ===<br />
* Manuela Silva - alfalb - manuelaDOTsilvaATskyDOTcom - Interpreter/translator and proof-reader<br />
* Alfredo Silva - alfalb - alfalbDOTasATgmailDOTcom - Translator and proof-reader<br />
<br />
=== Romania ===<br />
* Cazacu Bogdan (Bogo) - cazacu DOT bogdan AT gmail DOT com - Romanian community. forum moderation, achieving deadlines as part of the romanian group for the international group.<br />
* Florin Cătălin RUSSEN (Piratu) - cfrussen AT yahoo DOT co DOT uk - Romanian community: moderate forum, interacting with international community<br />
* Florin Pulbere (Gremlin) - kernelgremlin AT gmail DOT com - Romanian community.<br />
<br />
=== Russia ===<br />
* Eugene Zhuravlev (macdowell) - macdowell AT cybsec DOT org - Russian community<br />
* Mitya (mitya) - mitya AT cargosoft DOT ru - promotion at Russian opensource news sites (linux.org.ru), #mageia-ru<br />
* ?? (tejen) - ?? - Mageia website and forum [http://mageialinux.ru/ http://mageialinux.ru/]<br />
* Alexey Dolotov (sevo44) - dolotov44 AT yandex DOT ru - wants to help take good care of the Russian forums and wiki, including of security (ssl certificate and back-ups) and considers moving forums and wiki to a different domain to be able to do that <!--https://forum.mageia-linux.ru/ https://wiki.mageia-linux.ru/--><br />
<br />
=== Serbia ===<br />
* Toma Janković (tomaja) - tomaja@linuxo.org - Serbian community: promotion of mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Slovenia ===<br />
* Filip Komar (filip) - filip(at)mageia.org - translation<br />
<br />
=== South Africa ===<br />
* Rory Albertyn (Gripen) - nicodeamus(at)gmail.com - South African community<br />
<br />
=== Spanish (not just Spain) ===<br />
* barsalatino - barsalatino - barsalatino@gmail.com - Spanish-speaking community (Blogdrake)<br />
* Drakedalfa - drakedalfa - drakedalfa at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Diego Bello - jacen - dbello at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Felix Martos (asinkeBOFH) - felix.martos AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Fernando Anthony Ristaño (Drakor) - drakorbofh AT gmail DOT com - Spanish-speaking community (Blogdrake) and Argentina community (Ardriva) - - promoting mageia on events in Argentina<br />
* Gonzalo Igartua (GregoryBravas) - <del>gigartua@ AT mail.com DOT</del> - Spanish-speaking community (BlogDrake)<br />
** ''E-mail bounces when leaving out the dot "." after "com"'' <code>550 5.1.1 ... User is unknown {mx-us011}</code> <br />
* Sinner from the Prairy (SinnerBOFH) - sinnerbofh AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Tomàs Deltell (Annubis) - tomasdeltell AT gmx DOT es - Spanish-speaking community (Blogdrake)<br />
* vfmBOFH - vfmBOFH - vfmbofh(at)gmail.com - Spanish-speaking community (Blogdrake)<br />
<br />
Available domain names: mageia-es.org, mageia.com.ar<br />
<br />
=== Swedish (not just Sweden) ===<br />
* David V. Wallin (dvwallin) - <del>david AT ngweb DOT se</del> <br />
** ''E-mail bounced:'' <code>DNS Error: Domain name not found</code><br />
* Kristoffer Grundström (Umeaboy) - kristoffer dot grundstrom 1983 at gmail dot com - Founder and operator of the Swedish IRC-channels #mageia-sv and mageia-se<br />
* Sebastian (sebsebseb) - #mageia-sv and #mageia-se - Swedish Channels IRC Operator<br />
<br />
=== Taiwan ===<br />
[http://groups.google.com/group/mageia-taiwan Mageia Taiwanese user group]<br />
* 姚智偉 (kira) - elegant . pegasus AT gmail . com = Taiwanese user group moderator.<br />
* You-Cheng Hsieh (yochenhsieh) - yochenhsieh AT gmail . com - Taiwanese user group moderator.<br />
<br />
=== Turkey ===<br />
* Atilla ÖNTAŞ - <tarakbumba> - tarakbumba@gmail.com - Turkish community (Mandriva Turkiye).<br />
<br />
=== Tunisia ===<br />
* Beltaif Belgacem - <Gasston> - beltaif_bel@live.fr - Tunisia community.<br />
<br />
=== United Arab Emirates === <br />
* Ali Jawad (theforsaken) - amjjawad AT gmail DOT com - Ready for anything to help out, just let me know.<br />
<br />
=== United Kingdom ===<br />
* Margot Lawrence - margot at otfordduckscomputers.co.uk - IRC #mageia-uk & user help for people physically located in the UK<br />
* Sebastian (sebsebseb) - #mageia-uk irc channel - UK Users Community Founder<br />
<br />
=== United States ===<br />
* Alan Augustson (VoodooDali) - alan DOT augustson AT gmail DOT com - Chicago, IL, US. Longtime Mandriva user, interested in communications, marketing and artwork. NOT a programmer/developer; more like an advanced user.<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Kevin E. Ivey (lnxguy) - ik04[at]isot.com - Longtime Mandrake/Mandriva user and supporter since Day One. Founder of the Fort Hood Area Linux Users Group- HoodLUG. Active in advocacy efforts for Linux/FOSS.<br />
* Tracy W. Holz - tracy[at]htredneck.com - Live in the Dallas area, Involved in the Open Source/Linux podcast area, I go by the nick - Holzster<br />
* Josh King (dotmil) - josh AT dotmil.org - Abilene, TX area; working within F/OSS for nearly a decade now. Professional system admin, part time hacker and jack of many trades</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Local_Communities_Team&diff=39990Local Communities Team2018-06-09T13:45:00Z<p>Dtux: http://mageia-se.org for the Swedish Community not existing anymore</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Local communities]]<br />
<br />
<br />
== Join/contact the team ==<br />
* Add your name below under your country (please add your country, too, if it isn't in the list, yet)<br />
'''- Please use the template as shown below! - '''<br />
* sign up for [https://ml.mageia.org/l/review/local-discuss the local-discuss mailing list]<br />
* We are now organizing the team, please join our [https://ml.mageia.org/l/review/local-discuss ml] if you want to help.<br />
* join irc://irc.freenode.net/#mageia<br />
* '''''team leader:'' Otto Sá (otto)'''<br />
* '''''deputy team leader:'' Oliver Burger (obgr_seneca)'''<br />
<br />
<br />
<br />
Register below for the Local Communities Team: help to spread Mageia in different users groups, manage communication and relations with development team, work with atelier team...<br />
<br />
'''Use the following template to register:'''<br />
* <FirstName Lastname> (<nick>) - <email> - <how you can help><br />
<br />
''' For example: '''<br />
* <AbdusSalam> (<Barket>) - <abdussalam.bd09@gmail.com> - <Marketing><br />
<br />
'''Please insert your name in alphabetic order.'''<br />
<br />
== List of registered people ==<br />
<br />
=== Australia ===<br />
<br />
* Trish Fraser (trishf42) - press@ contact and user help for Mageia users in Australia/NZ<br />
<br />
=== Bangladesh ===<br />
* AbdusSalam - barket - abdussalam.bd09@gmail.com - Help Bangladeshi to introduce Mandriva inshaAllah.<br />
* Muntasim-Ul-Haque (Jeeshan) - tranjeeshan@gmail.com - Encourage people to use Mageia in Bangladesh.<br />
<br />
=== Belgium ===<br />
<br />
For Flemish part, see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Brazil ===<br />
* Adjamilton Júnior - ajunior at brasifort.com.br - i18n-pt_BR Team Leader. Help with brazilian free software community.<br />
* Aracele Torres - araceletorres at gmail.com - Help with brazilian free software community.<br />
* Filipe Saraiva - filip.saraiva at gmail.com - Help with brazilian free software community.<br />
* Lucas Emanoel - <del>lucasemanoel AT valedosambito DOT com</del> - Help with brazilian free software community.<br />
** ''Mail bounced:'' <code>550 #5.1.0 Address rejected</code><br />
* Paulo Ricardo G de Oliveira - User and student programming "C and PHP".<br />
* Otto Sa – ottosa at gmail.com - the Founder of Mageia do Brazil (ex MageiaBr) at http://mageiadobrasil.com.br/portal/ , the support forum located at http://www.mageiadobrasil.com.br/forum/index.php and The Mageia do Brasil wiki at http://www.mageiadobrasil.com.br/wiki/doku.php<br />
* Márcio Padula (Padula) - padula1000 at gmail.com - i-18n-pt_BR team translator, Mageia do Brasil webmaster and administrator (who made the New Mageia do Brasil) .<br />
* macxi - terra agua at gmail com, documentation, translation and community support.<br />
<br />
=== Canada ===<br />
* Glen Millard - bartockbat - szilverthorne AT gmail DOT com - Need a presence in The Great White North - help with FSF in Canada<br />
* J.P. Pasnak - Linegod - pasnak AT warpedsystems DOT sk Dot ca - work with Canadian LUGs<br />
<br />
=== China, Mainland of (PRC) ===<br />
* Jiang Yike - futureway (at) asia.com - The Chinese Community of Mageia and Mandriva Linux<br />
=== Dutch language ===<br />
<br />
* Maarten Vanraes - AL13N<br />
* Marja van Waes - marja<br />
* Remco Rijnders - remmy - [http://mageia.nl/cgi-bin/mailman/listinfo/vraagje Dutch mailing list]<br />
<br />
=== English Speaking International Users Community ===<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Glen Millard - szilverthorne AT gmail DOT com - Let me know what you need!<br />
* Paul Willard - paul at loudas dot com - English community manager<br />
<br />
=== Finland ===<br />
* Renni Reposalo - renni at pcuf dot fi - Finnish community<br />
<br />
=== France ===<br />
* Arnaud Vacquier (aranud87/aranud) - aranud at mageia-debutant.fr (PGP:0xFBC19522) Admin mageia-debutant.fr<br />
* Benoît Audouard (baud123) - baud123 at tuxfamily.org Moderator LinuxFr.org & French community, advertising at events, support on irc chans either in english, french, spanish, cooperation/contact with international communities possible<br />
* Frank Kober (dharanamrs) - goemusic#yahoo#fr - interactions with international and French linux audio user communities (linuxaudio.org, linuxmao.org)<br />
* Frédéric Cuif - fredux86 AT gmail.com - French community, law team, comm team <br />
* Jean-Luc CINELLI (Enzolyte) - enzolyte AT mageialinux-online DOT org - Admin MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Marianne Lombard (jehane) - jehane at tuxette dot fr - french community, advertising Mageia on events, organising stands on events, translations, support on irc chans (french and english)<br />
* Michael Scherer (misc) - misc@zarb.org - packaging community, ex cooker chef<br />
* Olivier Méjean (goom) - omejean at yahoo.fr - French community, relation with devel team, comm team; Mageia community magazine<br />
* Pascal VERDIEL (yopman) - Admin MLO,a forum dedicated to help beginners and spread the word of Mageia.(French community) <br />
* Patrick DUBEAU (DaaX) - daax at mageialinux-online dot org - Webmaster MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Roddy FOLETTE - <del>roddy.folette@rfconseilsinfos.com</del> (French community : dedicated to help beginners and spread the word of Mageia in Réunion, ile Maurice and around the Indian Ocean countries)<br />
**''E-mail address bounces:'' <code>DNS Error: Domain name not found</code><br />
* Thomas Lottmann (Skiper) - skiperdrake AT gmail DOT com - French community, communication, advertising and events, interacting with international and french communities, working and helping various community projects. <br />
* Yvan Munoz (muny) mr.yvan.munoz@gmail.com (French Community : atmosphere)<br />
* Jean Marie Dubosc (JMGLV) -jean.marie.dubosc_at_gmail-dot_com -French Community-<br />
* LSDM (Yves Specht) - lsdm@laposte.net -<br />
<br />
=== German (not just Germany) ===<br />
* Florian Hubold (doktor5000) - doktor5000 AT arcor DOT de - German community: moderate forum, interacting with international community<br />
* Oliver Burger (obgr_seneca) - oliver.bgr AT gmail DOT com - German community: moderate forum, advertising Mageia on events, interacting with international community<br />
* Wolfgang Bornath (wobo) - molch.b@googlemail.com - founder & admin of the German Mandriva user community, regular participation at German events, interested in international communication<br />
<br />
=== Greece ===<br />
* Dimitrios Glentadakis (dglent) - dglent@gmail.com - Greek community (mageia-gr.org)<br />
* Dimitris Tsiamasiotis (dtsiamasiotis) - dtsiamasiotis AT gmail.com - Greek community<br />
* Xaris Yfantis (Xaris) - <del>sinzoda1 (AT) otenet (DOT) gr</del> - Greek community<br />
**''Mail bounced:'' <code>550 5.1.1 ... Usern unknown</code><br />
<br />
=== India ===<br />
* Anshul Jain (anshuljain) - anshulajain (at) gmail (dot) com- Promotion at various Linux User Groups in India, communicating with the corporate world for Linux as a desktop & deployment platform <br />
<br />
=== Iran ===<br />
* Mahmoud Fereydouni (fereydouni) - fereydouni (at) gmail (dot) com, admin (at) mageia (dot) ir - Persian Users Community Founder & Manager, Translator, Customized package developer and QA.<br />
<br />
=== Indonesia ===<br />
* Luthfi Emka (panahbiru) - panahbiru at gmail dot com - Indonesian Mageia Blogs and Forums (mageia.web.id)<br />
* Muhamad Abdullkadir - muhamad at iscs dot cc - Spread Mageia in Indonesia<br />
<br />
=== Italy ===<br />
* Angelo Naselli - anaselli at linux dot it - packager, developer, mentor, Italian community member (mageia online - mageiaonline.it). <br />
* Marcello Anni - marcello.anni at alice dot it - Italian community: translations, howtos, relation with devel team, relation with international communities, moderate forum, PR, press releases<br />
* Matteo Pasotti - matteo dot pasotti at gmail dot com - packager, developer, translator, Italian community member (mageia online - mageiaonline.it).<br />
* Stefano Negro - stblack at gmail.com - translator, tester at QA team<br />
<br />
=== Netherlands, The ===<br />
<br />
see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Norway ===<br />
* Olav Dahlum (olorin_) - odahlum at gmail dot com - Norwegian community member<br />
<br />
=== Pakistan ===<br />
* M Younis Soomro (mysoomro) - myounis.mcs@gmail.com - Trying to introduce and spread Linux (Mageia & other distros) in Pakistan.<br />
<br />
=== Paraguay ===<br />
* KSEltar (kseltar) - kseltar(at)gmail.com - Deshn FLOSS community: promotion of Mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Poland ===<br />
* Daniel Napora (napcok) - napcok at gmail dot com - Polish community ([http://mageia.org.pl])<br />
<br />
=== Portugal ===<br />
* Manuela Silva - alfalb - manuelaDOTsilvaATskyDOTcom - Interpreter/translator and proof-reader<br />
* Alfredo Silva - alfalb - alfalbDOTasATgmailDOTcom - Translator and proof-reader<br />
<br />
=== Romania ===<br />
* Cazacu Bogdan (Bogo) - cazacu DOT bogdan AT gmail DOT com - Romanian community. forum moderation, achieving deadlines as part of the romanian group for the international group.<br />
* Florin Cătălin RUSSEN (Piratu) - cfrussen AT yahoo DOT co DOT uk - Romanian community: moderate forum, interacting with international community<br />
* Florin Pulbere (Gremlin) - kernelgremlin AT gmail DOT com - Romanian community.<br />
<br />
=== Russia ===<br />
* Eugene Zhuravlev (macdowell) - macdowell AT cybsec DOT org - Russian community<br />
* Mitya (mitya) - mitya AT cargosoft DOT ru - promotion at Russian opensource news sites (linux.org.ru), #mageia-ru<br />
* ?? (tejen) - ?? - Mageia website and forum [http://mageialinux.ru/ http://mageialinux.ru/]<br />
* Alexey Dolotov (sevo44) - dolotov44 AT yandex DOT ru - wants to help take good care of the Russian forums and wiki, including of security (ssl certificate and back-ups) and considers moving forums and wiki to a different domain to be able to do that <!--https://forum.mageia-linux.ru/ https://wiki.mageia-linux.ru/--><br />
<br />
=== Serbia ===<br />
* Toma Janković (tomaja) - tomaja@linuxo.org - Serbian community: promotion of mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Slovenia ===<br />
* Filip Komar (filip) - filip(at)mageia.org - translation<br />
<br />
=== South Africa ===<br />
* Rory Albertyn (Gripen) - nicodeamus(at)gmail.com - South African community<br />
<br />
=== Spanish (not just Spain) ===<br />
* barsalatino - barsalatino - barsalatino@gmail.com - Spanish-speaking community (Blogdrake)<br />
* Drakedalfa - drakedalfa - drakedalfa at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Diego Bello - jacen - dbello at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Felix Martos (asinkeBOFH) - felix.martos AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Fernando Anthony Ristaño (Drakor) - drakorbofh AT gmail DOT com - Spanish-speaking community (Blogdrake) and Argentina community (Ardriva) - - promoting mageia on events in Argentina<br />
* Gonzalo Igartua (GregoryBravas) - <del>gigartua@ AT mail.com DOT</del> - Spanish-speaking community (BlogDrake)<br />
** ''E-mail bounces when leaving out the dot "." after "com"'' <code>550 5.1.1 ... User is unknown {mx-us011}</code> <br />
* Sinner from the Prairy (SinnerBOFH) - sinnerbofh AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Tomàs Deltell (Annubis) - tomasdeltell AT gmx DOT es - Spanish-speaking community (Blogdrake)<br />
* vfmBOFH - vfmBOFH - vfmbofh(at)gmail.com - Spanish-speaking community (Blogdrake)<br />
<br />
Available domain names: mageia-es.org, mageia.com.ar<br />
<br />
=== Swedish (not just Sweden) ===<br />
* David V. Wallin (dvwallin) - <del>david AT ngweb DOT se</del> <br />
** ''E-mail bounced:'' <code>DNS Error: Domain name not found</code><br />
* Kristoffer Grundström (Umeaboy) - kristoffer dot grundstrom 1983 at gmail dot com - Founder and operator of the Swedish IRC-channels #mageia-sv and mageia-se<br />
* Sebastian (sebsebseb) - #mageia-sv and #mageia-se - Swedish Channels IRC Operator<br />
<br />
=== Taiwan ===<br />
[http://groups.google.com/group/mageia-taiwan Mageia Taiwanese user group]<br />
* 姚智偉 (kira) - elegant . pegasus AT gmail . com = Taiwanese user group moderator.<br />
* You-Cheng Hsieh (yochenhsieh) - yochenhsieh AT gmail . com - Taiwanese user group moderator.<br />
<br />
=== Turkey ===<br />
* Atilla ÖNTAŞ - <tarakbumba> - tarakbumba@gmail.com - Turkish community (Mandriva Turkiye).<br />
<br />
=== Tunisia ===<br />
* Beltaif Belgacem - <Gasston> - beltaif_bel@live.fr - Tunisia community.<br />
<br />
=== United Arab Emirates === <br />
* Ali Jawad (theforsaken) - amjjawad AT gmail DOT com - Ready for anything to help out, just let me know.<br />
<br />
=== United Kingdom ===<br />
* Margot Lawrence - margot at otfordduckscomputers.co.uk - IRC #mageia-uk & user help for people physically located in the UK<br />
* Sebastian (sebsebseb) - #mageia-uk irc channel - UK Users Community Founder<br />
<br />
=== United States ===<br />
* Alan Augustson (VoodooDali) - alan DOT augustson AT gmail DOT com - Chicago, IL, US. Longtime Mandriva user, interested in communications, marketing and artwork. NOT a programmer/developer; more like an advanced user.<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Kevin E. Ivey (lnxguy) - ik04[at]isot.com - Longtime Mandrake/Mandriva user and supporter since Day One. Founder of the Fort Hood Area Linux Users Group- HoodLUG. Active in advocacy efforts for Linux/FOSS.<br />
* Tracy W. Holz - tracy[at]htredneck.com - Live in the Dallas area, Involved in the Open Source/Linux podcast area, I go by the nick - Holzster<br />
* Josh King (dotmil) - josh AT dotmil.org - Abilene, TX area; working within F/OSS for nearly a decade now. Professional system admin, part time hacker and jack of many trades</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Local_Communities_Team&diff=39989Local Communities Team2018-06-09T13:42:18Z<p>Dtux: ([http://www.mageia-ru.org]) not existing</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Local communities]]<br />
<br />
<br />
== Join/contact the team ==<br />
* Add your name below under your country (please add your country, too, if it isn't in the list, yet)<br />
'''- Please use the template as shown below! - '''<br />
* sign up for [https://ml.mageia.org/l/review/local-discuss the local-discuss mailing list]<br />
* We are now organizing the team, please join our [https://ml.mageia.org/l/review/local-discuss ml] if you want to help.<br />
* join irc://irc.freenode.net/#mageia<br />
* '''''team leader:'' Otto Sá (otto)'''<br />
* '''''deputy team leader:'' Oliver Burger (obgr_seneca)'''<br />
<br />
<br />
<br />
Register below for the Local Communities Team: help to spread Mageia in different users groups, manage communication and relations with development team, work with atelier team...<br />
<br />
'''Use the following template to register:'''<br />
* <FirstName Lastname> (<nick>) - <email> - <how you can help><br />
<br />
''' For example: '''<br />
* <AbdusSalam> (<Barket>) - <abdussalam.bd09@gmail.com> - <Marketing><br />
<br />
'''Please insert your name in alphabetic order.'''<br />
<br />
== List of registered people ==<br />
<br />
=== Australia ===<br />
<br />
* Trish Fraser (trishf42) - press@ contact and user help for Mageia users in Australia/NZ<br />
<br />
=== Bangladesh ===<br />
* AbdusSalam - barket - abdussalam.bd09@gmail.com - Help Bangladeshi to introduce Mandriva inshaAllah.<br />
* Muntasim-Ul-Haque (Jeeshan) - tranjeeshan@gmail.com - Encourage people to use Mageia in Bangladesh.<br />
<br />
=== Belgium ===<br />
<br />
For Flemish part, see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Brazil ===<br />
* Adjamilton Júnior - ajunior at brasifort.com.br - i18n-pt_BR Team Leader. Help with brazilian free software community.<br />
* Aracele Torres - araceletorres at gmail.com - Help with brazilian free software community.<br />
* Filipe Saraiva - filip.saraiva at gmail.com - Help with brazilian free software community.<br />
* Lucas Emanoel - <del>lucasemanoel AT valedosambito DOT com</del> - Help with brazilian free software community.<br />
** ''Mail bounced:'' <code>550 #5.1.0 Address rejected</code><br />
* Paulo Ricardo G de Oliveira - User and student programming "C and PHP".<br />
* Otto Sa – ottosa at gmail.com - the Founder of Mageia do Brazil (ex MageiaBr) at http://mageiadobrasil.com.br/portal/ , the support forum located at http://www.mageiadobrasil.com.br/forum/index.php and The Mageia do Brasil wiki at http://www.mageiadobrasil.com.br/wiki/doku.php<br />
* Márcio Padula (Padula) - padula1000 at gmail.com - i-18n-pt_BR team translator, Mageia do Brasil webmaster and administrator (who made the New Mageia do Brasil) .<br />
* macxi - terra agua at gmail com, documentation, translation and community support.<br />
<br />
=== Canada ===<br />
* Glen Millard - bartockbat - szilverthorne AT gmail DOT com - Need a presence in The Great White North - help with FSF in Canada<br />
* J.P. Pasnak - Linegod - pasnak AT warpedsystems DOT sk Dot ca - work with Canadian LUGs<br />
<br />
=== China, Mainland of (PRC) ===<br />
* Jiang Yike - futureway (at) asia.com - The Chinese Community of Mageia and Mandriva Linux<br />
=== Dutch language ===<br />
<br />
* Maarten Vanraes - AL13N<br />
* Marja van Waes - marja<br />
* Remco Rijnders - remmy - [http://mageia.nl/cgi-bin/mailman/listinfo/vraagje Dutch mailing list]<br />
<br />
=== English Speaking International Users Community ===<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Glen Millard - szilverthorne AT gmail DOT com - Let me know what you need!<br />
* Paul Willard - paul at loudas dot com - English community manager<br />
<br />
=== Finland ===<br />
* Renni Reposalo - renni at pcuf dot fi - Finnish community<br />
<br />
=== France ===<br />
* Arnaud Vacquier (aranud87/aranud) - aranud at mageia-debutant.fr (PGP:0xFBC19522) Admin mageia-debutant.fr<br />
* Benoît Audouard (baud123) - baud123 at tuxfamily.org Moderator LinuxFr.org & French community, advertising at events, support on irc chans either in english, french, spanish, cooperation/contact with international communities possible<br />
* Frank Kober (dharanamrs) - goemusic#yahoo#fr - interactions with international and French linux audio user communities (linuxaudio.org, linuxmao.org)<br />
* Frédéric Cuif - fredux86 AT gmail.com - French community, law team, comm team <br />
* Jean-Luc CINELLI (Enzolyte) - enzolyte AT mageialinux-online DOT org - Admin MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Marianne Lombard (jehane) - jehane at tuxette dot fr - french community, advertising Mageia on events, organising stands on events, translations, support on irc chans (french and english)<br />
* Michael Scherer (misc) - misc@zarb.org - packaging community, ex cooker chef<br />
* Olivier Méjean (goom) - omejean at yahoo.fr - French community, relation with devel team, comm team; Mageia community magazine<br />
* Pascal VERDIEL (yopman) - Admin MLO,a forum dedicated to help beginners and spread the word of Mageia.(French community) <br />
* Patrick DUBEAU (DaaX) - daax at mageialinux-online dot org - Webmaster MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Roddy FOLETTE - <del>roddy.folette@rfconseilsinfos.com</del> (French community : dedicated to help beginners and spread the word of Mageia in Réunion, ile Maurice and around the Indian Ocean countries)<br />
**''E-mail address bounces:'' <code>DNS Error: Domain name not found</code><br />
* Thomas Lottmann (Skiper) - skiperdrake AT gmail DOT com - French community, communication, advertising and events, interacting with international and french communities, working and helping various community projects. <br />
* Yvan Munoz (muny) mr.yvan.munoz@gmail.com (French Community : atmosphere)<br />
* Jean Marie Dubosc (JMGLV) -jean.marie.dubosc_at_gmail-dot_com -French Community-<br />
* LSDM (Yves Specht) - lsdm@laposte.net -<br />
<br />
=== German (not just Germany) ===<br />
* Florian Hubold (doktor5000) - doktor5000 AT arcor DOT de - German community: moderate forum, interacting with international community<br />
* Oliver Burger (obgr_seneca) - oliver.bgr AT gmail DOT com - German community: moderate forum, advertising Mageia on events, interacting with international community<br />
* Wolfgang Bornath (wobo) - molch.b@googlemail.com - founder & admin of the German Mandriva user community, regular participation at German events, interested in international communication<br />
<br />
=== Greece ===<br />
* Dimitrios Glentadakis (dglent) - dglent@gmail.com - Greek community (mageia-gr.org)<br />
* Dimitris Tsiamasiotis (dtsiamasiotis) - dtsiamasiotis AT gmail.com - Greek community<br />
* Xaris Yfantis (Xaris) - <del>sinzoda1 (AT) otenet (DOT) gr</del> - Greek community<br />
**''Mail bounced:'' <code>550 5.1.1 ... Usern unknown</code><br />
<br />
=== India ===<br />
* Anshul Jain (anshuljain) - anshulajain (at) gmail (dot) com- Promotion at various Linux User Groups in India, communicating with the corporate world for Linux as a desktop & deployment platform <br />
<br />
=== Iran ===<br />
* Mahmoud Fereydouni (fereydouni) - fereydouni (at) gmail (dot) com, admin (at) mageia (dot) ir - Persian Users Community Founder & Manager, Translator, Customized package developer and QA.<br />
<br />
=== Indonesia ===<br />
* Luthfi Emka (panahbiru) - panahbiru at gmail dot com - Indonesian Mageia Blogs and Forums (mageia.web.id)<br />
* Muhamad Abdullkadir - muhamad at iscs dot cc - Spread Mageia in Indonesia<br />
<br />
=== Italy ===<br />
* Angelo Naselli - anaselli at linux dot it - packager, developer, mentor, Italian community member (mageia online - mageiaonline.it). <br />
* Marcello Anni - marcello.anni at alice dot it - Italian community: translations, howtos, relation with devel team, relation with international communities, moderate forum, PR, press releases<br />
* Matteo Pasotti - matteo dot pasotti at gmail dot com - packager, developer, translator, Italian community member (mageia online - mageiaonline.it).<br />
* Stefano Negro - stblack at gmail.com - translator, tester at QA team<br />
<br />
=== Netherlands, The ===<br />
<br />
see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Norway ===<br />
* Olav Dahlum (olorin_) - odahlum at gmail dot com - Norwegian community member<br />
<br />
=== Pakistan ===<br />
* M Younis Soomro (mysoomro) - myounis.mcs@gmail.com - Trying to introduce and spread Linux (Mageia & other distros) in Pakistan.<br />
<br />
=== Paraguay ===<br />
* KSEltar (kseltar) - kseltar(at)gmail.com - Deshn FLOSS community: promotion of Mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Poland ===<br />
* Daniel Napora (napcok) - napcok at gmail dot com - Polish community ([http://mageia.org.pl])<br />
<br />
=== Portugal ===<br />
* Manuela Silva - alfalb - manuelaDOTsilvaATskyDOTcom - Interpreter/translator and proof-reader<br />
* Alfredo Silva - alfalb - alfalbDOTasATgmailDOTcom - Translator and proof-reader<br />
<br />
=== Romania ===<br />
* Cazacu Bogdan (Bogo) - cazacu DOT bogdan AT gmail DOT com - Romanian community. forum moderation, achieving deadlines as part of the romanian group for the international group.<br />
* Florin Cătălin RUSSEN (Piratu) - cfrussen AT yahoo DOT co DOT uk - Romanian community: moderate forum, interacting with international community<br />
* Florin Pulbere (Gremlin) - kernelgremlin AT gmail DOT com - Romanian community.<br />
<br />
=== Russia ===<br />
* Eugene Zhuravlev (macdowell) - macdowell AT cybsec DOT org - Russian community<br />
* Mitya (mitya) - mitya AT cargosoft DOT ru - promotion at Russian opensource news sites (linux.org.ru), #mageia-ru<br />
* ?? (tejen) - ?? - Mageia website and forum [http://mageialinux.ru/ http://mageialinux.ru/]<br />
* Alexey Dolotov (sevo44) - dolotov44 AT yandex DOT ru - wants to help take good care of the Russian forums and wiki, including of security (ssl certificate and back-ups) and considers moving forums and wiki to a different domain to be able to do that <!--https://forum.mageia-linux.ru/ https://wiki.mageia-linux.ru/--><br />
<br />
=== Serbia ===<br />
* Toma Janković (tomaja) - tomaja@linuxo.org - Serbian community: promotion of mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Slovenia ===<br />
* Filip Komar (filip) - filip(at)mageia.org - translation<br />
<br />
=== South Africa ===<br />
* Rory Albertyn (Gripen) - nicodeamus(at)gmail.com - South African community<br />
<br />
=== Spanish (not just Spain) ===<br />
* barsalatino - barsalatino - barsalatino@gmail.com - Spanish-speaking community (Blogdrake)<br />
* Drakedalfa - drakedalfa - drakedalfa at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Diego Bello - jacen - dbello at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Felix Martos (asinkeBOFH) - felix.martos AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Fernando Anthony Ristaño (Drakor) - drakorbofh AT gmail DOT com - Spanish-speaking community (Blogdrake) and Argentina community (Ardriva) - - promoting mageia on events in Argentina<br />
* Gonzalo Igartua (GregoryBravas) - <del>gigartua@ AT mail.com DOT</del> - Spanish-speaking community (BlogDrake)<br />
** ''E-mail bounces when leaving out the dot "." after "com"'' <code>550 5.1.1 ... User is unknown {mx-us011}</code> <br />
* Sinner from the Prairy (SinnerBOFH) - sinnerbofh AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Tomàs Deltell (Annubis) - tomasdeltell AT gmx DOT es - Spanish-speaking community (Blogdrake)<br />
* vfmBOFH - vfmBOFH - vfmbofh(at)gmail.com - Spanish-speaking community (Blogdrake)<br />
<br />
Available domain names: mageia-es.org, mageia.com.ar<br />
<br />
=== Swedish (not just Sweden) ===<br />
* David V. Wallin (dvwallin) - <del>david AT ngweb DOT se</del> - Running http://mageia-se.org for the Swedish Community<br />
** ''E-mail bounced:'' <code>DNS Error: Domain name not found</code><br />
* Kristoffer Grundström (Umeaboy) - kristoffer dot grundstrom 1983 at gmail dot com - Founder and operator of the Swedish IRC-channels #mageia-sv and mageia-se<br />
* Sebastian (sebsebseb) - #mageia-sv and #mageia-se - Swedish Channels IRC Operator<br />
<br />
=== Taiwan ===<br />
[http://groups.google.com/group/mageia-taiwan Mageia Taiwanese user group]<br />
* 姚智偉 (kira) - elegant . pegasus AT gmail . com = Taiwanese user group moderator.<br />
* You-Cheng Hsieh (yochenhsieh) - yochenhsieh AT gmail . com - Taiwanese user group moderator.<br />
<br />
=== Turkey ===<br />
* Atilla ÖNTAŞ - <tarakbumba> - tarakbumba@gmail.com - Turkish community (Mandriva Turkiye).<br />
<br />
=== Tunisia ===<br />
* Beltaif Belgacem - <Gasston> - beltaif_bel@live.fr - Tunisia community.<br />
<br />
=== United Arab Emirates === <br />
* Ali Jawad (theforsaken) - amjjawad AT gmail DOT com - Ready for anything to help out, just let me know.<br />
<br />
=== United Kingdom ===<br />
* Margot Lawrence - margot at otfordduckscomputers.co.uk - IRC #mageia-uk & user help for people physically located in the UK<br />
* Sebastian (sebsebseb) - #mageia-uk irc channel - UK Users Community Founder<br />
<br />
=== United States ===<br />
* Alan Augustson (VoodooDali) - alan DOT augustson AT gmail DOT com - Chicago, IL, US. Longtime Mandriva user, interested in communications, marketing and artwork. NOT a programmer/developer; more like an advanced user.<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Kevin E. Ivey (lnxguy) - ik04[at]isot.com - Longtime Mandrake/Mandriva user and supporter since Day One. Founder of the Fort Hood Area Linux Users Group- HoodLUG. Active in advocacy efforts for Linux/FOSS.<br />
* Tracy W. Holz - tracy[at]htredneck.com - Live in the Dallas area, Involved in the Open Source/Linux podcast area, I go by the nick - Holzster<br />
* Josh King (dotmil) - josh AT dotmil.org - Abilene, TX area; working within F/OSS for nearly a decade now. Professional system admin, part time hacker and jack of many trades</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Local_Communities_Team&diff=39987Local Communities Team2018-06-09T13:41:16Z<p>Dtux: ( http://mageiausers.org ) not existing</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Local communities]]<br />
<br />
<br />
== Join/contact the team ==<br />
* Add your name below under your country (please add your country, too, if it isn't in the list, yet)<br />
'''- Please use the template as shown below! - '''<br />
* sign up for [https://ml.mageia.org/l/review/local-discuss the local-discuss mailing list]<br />
* We are now organizing the team, please join our [https://ml.mageia.org/l/review/local-discuss ml] if you want to help.<br />
* join irc://irc.freenode.net/#mageia<br />
* '''''team leader:'' Otto Sá (otto)'''<br />
* '''''deputy team leader:'' Oliver Burger (obgr_seneca)'''<br />
<br />
<br />
<br />
Register below for the Local Communities Team: help to spread Mageia in different users groups, manage communication and relations with development team, work with atelier team...<br />
<br />
'''Use the following template to register:'''<br />
* <FirstName Lastname> (<nick>) - <email> - <how you can help><br />
<br />
''' For example: '''<br />
* <AbdusSalam> (<Barket>) - <abdussalam.bd09@gmail.com> - <Marketing><br />
<br />
'''Please insert your name in alphabetic order.'''<br />
<br />
== List of registered people ==<br />
<br />
=== Australia ===<br />
<br />
* Trish Fraser (trishf42) - press@ contact and user help for Mageia users in Australia/NZ<br />
<br />
=== Bangladesh ===<br />
* AbdusSalam - barket - abdussalam.bd09@gmail.com - Help Bangladeshi to introduce Mandriva inshaAllah.<br />
* Muntasim-Ul-Haque (Jeeshan) - tranjeeshan@gmail.com - Encourage people to use Mageia in Bangladesh.<br />
<br />
=== Belgium ===<br />
<br />
For Flemish part, see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Brazil ===<br />
* Adjamilton Júnior - ajunior at brasifort.com.br - i18n-pt_BR Team Leader. Help with brazilian free software community.<br />
* Aracele Torres - araceletorres at gmail.com - Help with brazilian free software community.<br />
* Filipe Saraiva - filip.saraiva at gmail.com - Help with brazilian free software community.<br />
* Lucas Emanoel - <del>lucasemanoel AT valedosambito DOT com</del> - Help with brazilian free software community.<br />
** ''Mail bounced:'' <code>550 #5.1.0 Address rejected</code><br />
* Paulo Ricardo G de Oliveira - User and student programming "C and PHP".<br />
* Otto Sa – ottosa at gmail.com - the Founder of Mageia do Brazil (ex MageiaBr) at http://mageiadobrasil.com.br/portal/ , the support forum located at http://www.mageiadobrasil.com.br/forum/index.php and The Mageia do Brasil wiki at http://www.mageiadobrasil.com.br/wiki/doku.php<br />
* Márcio Padula (Padula) - padula1000 at gmail.com - i-18n-pt_BR team translator, Mageia do Brasil webmaster and administrator (who made the New Mageia do Brasil) .<br />
* macxi - terra agua at gmail com, documentation, translation and community support.<br />
<br />
=== Canada ===<br />
* Glen Millard - bartockbat - szilverthorne AT gmail DOT com - Need a presence in The Great White North - help with FSF in Canada<br />
* J.P. Pasnak - Linegod - pasnak AT warpedsystems DOT sk Dot ca - work with Canadian LUGs<br />
<br />
=== China, Mainland of (PRC) ===<br />
* Jiang Yike - futureway (at) asia.com - The Chinese Community of Mageia and Mandriva Linux<br />
=== Dutch language ===<br />
<br />
* Maarten Vanraes - AL13N<br />
* Marja van Waes - marja<br />
* Remco Rijnders - remmy - [http://mageia.nl/cgi-bin/mailman/listinfo/vraagje Dutch mailing list]<br />
<br />
=== English Speaking International Users Community ===<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Glen Millard - szilverthorne AT gmail DOT com - Let me know what you need!<br />
* Paul Willard - paul at loudas dot com - English community manager<br />
<br />
=== Finland ===<br />
* Renni Reposalo - renni at pcuf dot fi - Finnish community<br />
<br />
=== France ===<br />
* Arnaud Vacquier (aranud87/aranud) - aranud at mageia-debutant.fr (PGP:0xFBC19522) Admin mageia-debutant.fr<br />
* Benoît Audouard (baud123) - baud123 at tuxfamily.org Moderator LinuxFr.org & French community, advertising at events, support on irc chans either in english, french, spanish, cooperation/contact with international communities possible<br />
* Frank Kober (dharanamrs) - goemusic#yahoo#fr - interactions with international and French linux audio user communities (linuxaudio.org, linuxmao.org)<br />
* Frédéric Cuif - fredux86 AT gmail.com - French community, law team, comm team <br />
* Jean-Luc CINELLI (Enzolyte) - enzolyte AT mageialinux-online DOT org - Admin MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Marianne Lombard (jehane) - jehane at tuxette dot fr - french community, advertising Mageia on events, organising stands on events, translations, support on irc chans (french and english)<br />
* Michael Scherer (misc) - misc@zarb.org - packaging community, ex cooker chef<br />
* Olivier Méjean (goom) - omejean at yahoo.fr - French community, relation with devel team, comm team; Mageia community magazine<br />
* Pascal VERDIEL (yopman) - Admin MLO,a forum dedicated to help beginners and spread the word of Mageia.(French community) <br />
* Patrick DUBEAU (DaaX) - daax at mageialinux-online dot org - Webmaster MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Roddy FOLETTE - <del>roddy.folette@rfconseilsinfos.com</del> (French community : dedicated to help beginners and spread the word of Mageia in Réunion, ile Maurice and around the Indian Ocean countries)<br />
**''E-mail address bounces:'' <code>DNS Error: Domain name not found</code><br />
* Thomas Lottmann (Skiper) - skiperdrake AT gmail DOT com - French community, communication, advertising and events, interacting with international and french communities, working and helping various community projects. <br />
* Yvan Munoz (muny) mr.yvan.munoz@gmail.com (French Community : atmosphere)<br />
* Jean Marie Dubosc (JMGLV) -jean.marie.dubosc_at_gmail-dot_com -French Community-<br />
* LSDM (Yves Specht) - lsdm@laposte.net -<br />
<br />
=== German (not just Germany) ===<br />
* Florian Hubold (doktor5000) - doktor5000 AT arcor DOT de - German community: moderate forum, interacting with international community<br />
* Oliver Burger (obgr_seneca) - oliver.bgr AT gmail DOT com - German community: moderate forum, advertising Mageia on events, interacting with international community<br />
* Wolfgang Bornath (wobo) - molch.b@googlemail.com - founder & admin of the German Mandriva user community, regular participation at German events, interested in international communication<br />
<br />
=== Greece ===<br />
* Dimitrios Glentadakis (dglent) - dglent@gmail.com - Greek community (mageia-gr.org)<br />
* Dimitris Tsiamasiotis (dtsiamasiotis) - dtsiamasiotis AT gmail.com - Greek community<br />
* Xaris Yfantis (Xaris) - <del>sinzoda1 (AT) otenet (DOT) gr</del> - Greek community<br />
**''Mail bounced:'' <code>550 5.1.1 ... Usern unknown</code><br />
<br />
=== India ===<br />
* Anshul Jain (anshuljain) - anshulajain (at) gmail (dot) com- Promotion at various Linux User Groups in India, communicating with the corporate world for Linux as a desktop & deployment platform <br />
<br />
=== Iran ===<br />
* Mahmoud Fereydouni (fereydouni) - fereydouni (at) gmail (dot) com, admin (at) mageia (dot) ir - Persian Users Community Founder & Manager, Translator, Customized package developer and QA.<br />
<br />
=== Indonesia ===<br />
* Luthfi Emka (panahbiru) - panahbiru at gmail dot com - Indonesian Mageia Blogs and Forums (mageia.web.id)<br />
* Muhamad Abdullkadir - muhamad at iscs dot cc - Spread Mageia in Indonesia<br />
<br />
=== Italy ===<br />
* Angelo Naselli - anaselli at linux dot it - packager, developer, mentor, Italian community member (mageia online - mageiaonline.it). <br />
* Marcello Anni - marcello.anni at alice dot it - Italian community: translations, howtos, relation with devel team, relation with international communities, moderate forum, PR, press releases<br />
* Matteo Pasotti - matteo dot pasotti at gmail dot com - packager, developer, translator, Italian community member (mageia online - mageiaonline.it).<br />
* Stefano Negro - stblack at gmail.com - translator, tester at QA team<br />
<br />
=== Netherlands, The ===<br />
<br />
see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Norway ===<br />
* Olav Dahlum (olorin_) - odahlum at gmail dot com - Norwegian community member<br />
<br />
=== Pakistan ===<br />
* M Younis Soomro (mysoomro) - myounis.mcs@gmail.com - Trying to introduce and spread Linux (Mageia & other distros) in Pakistan.<br />
<br />
=== Paraguay ===<br />
* KSEltar (kseltar) - kseltar(at)gmail.com - Deshn FLOSS community: promotion of Mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Poland ===<br />
* Daniel Napora (napcok) - napcok at gmail dot com - Polish community ([http://mageia.org.pl])<br />
<br />
=== Portugal ===<br />
* Manuela Silva - alfalb - manuelaDOTsilvaATskyDOTcom - Interpreter/translator and proof-reader<br />
* Alfredo Silva - alfalb - alfalbDOTasATgmailDOTcom - Translator and proof-reader<br />
<br />
=== Romania ===<br />
* Cazacu Bogdan (Bogo) - cazacu DOT bogdan AT gmail DOT com - Romanian community. forum moderation, achieving deadlines as part of the romanian group for the international group.<br />
* Florin Cătălin RUSSEN (Piratu) - cfrussen AT yahoo DOT co DOT uk - Romanian community: moderate forum, interacting with international community<br />
* Florin Pulbere (Gremlin) - kernelgremlin AT gmail DOT com - Romanian community.<br />
<br />
=== Russia ===<br />
* Eugene Zhuravlev (macdowell) - macdowell AT cybsec DOT org - Russian community ([http://www.mageia-ru.org])<br />
* Mitya (mitya) - mitya AT cargosoft DOT ru - promotion at Russian opensource news sites (linux.org.ru), #mageia-ru<br />
* ?? (tejen) - ?? - Mageia website and forum [http://mageialinux.ru/ http://mageialinux.ru/]<br />
* Alexey Dolotov (sevo44) - dolotov44 AT yandex DOT ru - wants to help take good care of the Russian forums and wiki, including of security (ssl certificate and back-ups) and considers moving forums and wiki to a different domain to be able to do that <!--https://forum.mageia-linux.ru/ https://wiki.mageia-linux.ru/--><br />
<br />
=== Serbia ===<br />
* Toma Janković (tomaja) - tomaja@linuxo.org - Serbian community: promotion of mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Slovenia ===<br />
* Filip Komar (filip) - filip(at)mageia.org - translation<br />
<br />
=== South Africa ===<br />
* Rory Albertyn (Gripen) - nicodeamus(at)gmail.com - South African community<br />
<br />
=== Spanish (not just Spain) ===<br />
* barsalatino - barsalatino - barsalatino@gmail.com - Spanish-speaking community (Blogdrake)<br />
* Drakedalfa - drakedalfa - drakedalfa at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Diego Bello - jacen - dbello at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Felix Martos (asinkeBOFH) - felix.martos AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Fernando Anthony Ristaño (Drakor) - drakorbofh AT gmail DOT com - Spanish-speaking community (Blogdrake) and Argentina community (Ardriva) - - promoting mageia on events in Argentina<br />
* Gonzalo Igartua (GregoryBravas) - <del>gigartua@ AT mail.com DOT</del> - Spanish-speaking community (BlogDrake)<br />
** ''E-mail bounces when leaving out the dot "." after "com"'' <code>550 5.1.1 ... User is unknown {mx-us011}</code> <br />
* Sinner from the Prairy (SinnerBOFH) - sinnerbofh AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Tomàs Deltell (Annubis) - tomasdeltell AT gmx DOT es - Spanish-speaking community (Blogdrake)<br />
* vfmBOFH - vfmBOFH - vfmbofh(at)gmail.com - Spanish-speaking community (Blogdrake)<br />
<br />
Available domain names: mageia-es.org, mageia.com.ar<br />
<br />
=== Swedish (not just Sweden) ===<br />
* David V. Wallin (dvwallin) - <del>david AT ngweb DOT se</del> - Running http://mageia-se.org for the Swedish Community<br />
** ''E-mail bounced:'' <code>DNS Error: Domain name not found</code><br />
* Kristoffer Grundström (Umeaboy) - kristoffer dot grundstrom 1983 at gmail dot com - Founder and operator of the Swedish IRC-channels #mageia-sv and mageia-se<br />
* Sebastian (sebsebseb) - #mageia-sv and #mageia-se - Swedish Channels IRC Operator<br />
<br />
=== Taiwan ===<br />
[http://groups.google.com/group/mageia-taiwan Mageia Taiwanese user group]<br />
* 姚智偉 (kira) - elegant . pegasus AT gmail . com = Taiwanese user group moderator.<br />
* You-Cheng Hsieh (yochenhsieh) - yochenhsieh AT gmail . com - Taiwanese user group moderator.<br />
<br />
=== Turkey ===<br />
* Atilla ÖNTAŞ - <tarakbumba> - tarakbumba@gmail.com - Turkish community (Mandriva Turkiye).<br />
<br />
=== Tunisia ===<br />
* Beltaif Belgacem - <Gasston> - beltaif_bel@live.fr - Tunisia community.<br />
<br />
=== United Arab Emirates === <br />
* Ali Jawad (theforsaken) - amjjawad AT gmail DOT com - Ready for anything to help out, just let me know.<br />
<br />
=== United Kingdom ===<br />
* Margot Lawrence - margot at otfordduckscomputers.co.uk - IRC #mageia-uk & user help for people physically located in the UK<br />
* Sebastian (sebsebseb) - #mageia-uk irc channel - UK Users Community Founder<br />
<br />
=== United States ===<br />
* Alan Augustson (VoodooDali) - alan DOT augustson AT gmail DOT com - Chicago, IL, US. Longtime Mandriva user, interested in communications, marketing and artwork. NOT a programmer/developer; more like an advanced user.<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Kevin E. Ivey (lnxguy) - ik04[at]isot.com - Longtime Mandrake/Mandriva user and supporter since Day One. Founder of the Fort Hood Area Linux Users Group- HoodLUG. Active in advocacy efforts for Linux/FOSS.<br />
* Tracy W. Holz - tracy[at]htredneck.com - Live in the Dallas area, Involved in the Open Source/Linux podcast area, I go by the nick - Holzster<br />
* Josh King (dotmil) - josh AT dotmil.org - Abilene, TX area; working within F/OSS for nearly a decade now. Professional system admin, part time hacker and jack of many trades</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Local_Communities_Team&diff=39983Local Communities Team2018-06-09T13:29:11Z<p>Dtux: Supression of the link of the china community owned by another</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Local communities]]<br />
<br />
<br />
== Join/contact the team ==<br />
* Add your name below under your country (please add your country, too, if it isn't in the list, yet)<br />
'''- Please use the template as shown below! - '''<br />
* sign up for [https://ml.mageia.org/l/review/local-discuss the local-discuss mailing list]<br />
* We are now organizing the team, please join our [https://ml.mageia.org/l/review/local-discuss ml] if you want to help.<br />
* join irc://irc.freenode.net/#mageia<br />
* '''''team leader:'' Otto Sá (otto)'''<br />
* '''''deputy team leader:'' Oliver Burger (obgr_seneca)'''<br />
<br />
<br />
<br />
Register below for the Local Communities Team: help to spread Mageia in different users groups, manage communication and relations with development team, work with atelier team...<br />
<br />
'''Use the following template to register:'''<br />
* <FirstName Lastname> (<nick>) - <email> - <how you can help><br />
<br />
''' For example: '''<br />
* <AbdusSalam> (<Barket>) - <abdussalam.bd09@gmail.com> - <Marketing><br />
<br />
'''Please insert your name in alphabetic order.'''<br />
<br />
== List of registered people ==<br />
<br />
=== Australia ===<br />
<br />
* Trish Fraser (trishf42) - press@ contact and user help for Mageia users in Australia/NZ<br />
<br />
=== Bangladesh ===<br />
* AbdusSalam - barket - abdussalam.bd09@gmail.com - Help Bangladeshi to introduce Mandriva inshaAllah.<br />
* Muntasim-Ul-Haque (Jeeshan) - tranjeeshan@gmail.com - Encourage people to use Mageia in Bangladesh.<br />
<br />
=== Belgium ===<br />
<br />
For Flemish part, see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Brazil ===<br />
* Adjamilton Júnior - ajunior at brasifort.com.br - i18n-pt_BR Team Leader. Help with brazilian free software community.<br />
* Aracele Torres - araceletorres at gmail.com - Help with brazilian free software community.<br />
* Filipe Saraiva - filip.saraiva at gmail.com - Help with brazilian free software community.<br />
* Lucas Emanoel - <del>lucasemanoel AT valedosambito DOT com</del> - Help with brazilian free software community.<br />
** ''Mail bounced:'' <code>550 #5.1.0 Address rejected</code><br />
* Paulo Ricardo G de Oliveira - User and student programming "C and PHP".<br />
* Otto Sa – ottosa at gmail.com - the Founder of Mageia do Brazil (ex MageiaBr) at http://mageiadobrasil.com.br/portal/ , the support forum located at http://www.mageiadobrasil.com.br/forum/index.php and The Mageia do Brasil wiki at http://www.mageiadobrasil.com.br/wiki/doku.php<br />
* Márcio Padula (Padula) - padula1000 at gmail.com - i-18n-pt_BR team translator, Mageia do Brasil webmaster and administrator (who made the New Mageia do Brasil) .<br />
* macxi - terra agua at gmail com, documentation, translation and community support.<br />
<br />
=== Canada ===<br />
* Glen Millard - bartockbat - szilverthorne AT gmail DOT com - Need a presence in The Great White North - help with FSF in Canada<br />
* J.P. Pasnak - Linegod - pasnak AT warpedsystems DOT sk Dot ca - work with Canadian LUGs<br />
<br />
=== China, Mainland of (PRC) ===<br />
* Jiang Yike - futureway (at) asia.com - The Chinese Community of Mageia and Mandriva Linux<br />
=== Dutch language ===<br />
<br />
* Maarten Vanraes - AL13N<br />
* Marja van Waes - marja<br />
* Remco Rijnders - remmy - [http://mageia.nl/cgi-bin/mailman/listinfo/vraagje Dutch mailing list]<br />
<br />
=== English Speaking International Users Community ===<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Glen Millard - szilverthorne AT gmail DOT com - Let me know what you need!<br />
* Paul Willard - paul at loudas dot com - English community manager ( http://mageiausers.org )<br />
<br />
=== Finland ===<br />
* Renni Reposalo - renni at pcuf dot fi - Finnish community<br />
<br />
=== France ===<br />
* Arnaud Vacquier (aranud87/aranud) - aranud at mageia-debutant.fr (PGP:0xFBC19522) Admin mageia-debutant.fr<br />
* Benoît Audouard (baud123) - baud123 at tuxfamily.org Moderator LinuxFr.org & French community, advertising at events, support on irc chans either in english, french, spanish, cooperation/contact with international communities possible<br />
* Frank Kober (dharanamrs) - goemusic#yahoo#fr - interactions with international and French linux audio user communities (linuxaudio.org, linuxmao.org)<br />
* Frédéric Cuif - fredux86 AT gmail.com - French community, law team, comm team <br />
* Jean-Luc CINELLI (Enzolyte) - enzolyte AT mageialinux-online DOT org - Admin MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Marianne Lombard (jehane) - jehane at tuxette dot fr - french community, advertising Mageia on events, organising stands on events, translations, support on irc chans (french and english)<br />
* Michael Scherer (misc) - misc@zarb.org - packaging community, ex cooker chef<br />
* Olivier Méjean (goom) - omejean at yahoo.fr - French community, relation with devel team, comm team; Mageia community magazine<br />
* Pascal VERDIEL (yopman) - Admin MLO,a forum dedicated to help beginners and spread the word of Mageia.(French community) <br />
* Patrick DUBEAU (DaaX) - daax at mageialinux-online dot org - Webmaster MLO, a forum dedicated to help beginners and spread the word on Mageia. Communication, advertising and events, interacting with international and french communities, working and helping various community projects. (French community)<br />
* Roddy FOLETTE - <del>roddy.folette@rfconseilsinfos.com</del> (French community : dedicated to help beginners and spread the word of Mageia in Réunion, ile Maurice and around the Indian Ocean countries)<br />
**''E-mail address bounces:'' <code>DNS Error: Domain name not found</code><br />
* Thomas Lottmann (Skiper) - skiperdrake AT gmail DOT com - French community, communication, advertising and events, interacting with international and french communities, working and helping various community projects. <br />
* Yvan Munoz (muny) mr.yvan.munoz@gmail.com (French Community : atmosphere)<br />
* Jean Marie Dubosc (JMGLV) -jean.marie.dubosc_at_gmail-dot_com -French Community-<br />
* LSDM (Yves Specht) - lsdm@laposte.net -<br />
<br />
=== German (not just Germany) ===<br />
* Florian Hubold (doktor5000) - doktor5000 AT arcor DOT de - German community: moderate forum, interacting with international community<br />
* Oliver Burger (obgr_seneca) - oliver.bgr AT gmail DOT com - German community: moderate forum, advertising Mageia on events, interacting with international community<br />
* Wolfgang Bornath (wobo) - molch.b@googlemail.com - founder & admin of the German Mandriva user community, regular participation at German events, interested in international communication<br />
<br />
=== Greece ===<br />
* Dimitrios Glentadakis (dglent) - dglent@gmail.com - Greek community (mageia-gr.org)<br />
* Dimitris Tsiamasiotis (dtsiamasiotis) - dtsiamasiotis AT gmail.com - Greek community<br />
* Xaris Yfantis (Xaris) - <del>sinzoda1 (AT) otenet (DOT) gr</del> - Greek community<br />
**''Mail bounced:'' <code>550 5.1.1 ... Usern unknown</code><br />
<br />
=== India ===<br />
* Anshul Jain (anshuljain) - anshulajain (at) gmail (dot) com- Promotion at various Linux User Groups in India, communicating with the corporate world for Linux as a desktop & deployment platform <br />
<br />
=== Iran ===<br />
* Mahmoud Fereydouni (fereydouni) - fereydouni (at) gmail (dot) com, admin (at) mageia (dot) ir - Persian Users Community Founder & Manager, Translator, Customized package developer and QA.<br />
<br />
=== Indonesia ===<br />
* Luthfi Emka (panahbiru) - panahbiru at gmail dot com - Indonesian Mageia Blogs and Forums (mageia.web.id)<br />
* Muhamad Abdullkadir - muhamad at iscs dot cc - Spread Mageia in Indonesia<br />
<br />
=== Italy ===<br />
* Angelo Naselli - anaselli at linux dot it - packager, developer, mentor, Italian community member (mageia online - mageiaonline.it). <br />
* Marcello Anni - marcello.anni at alice dot it - Italian community: translations, howtos, relation with devel team, relation with international communities, moderate forum, PR, press releases<br />
* Matteo Pasotti - matteo dot pasotti at gmail dot com - packager, developer, translator, Italian community member (mageia online - mageiaonline.it).<br />
* Stefano Negro - stblack at gmail.com - translator, tester at QA team<br />
<br />
=== Netherlands, The ===<br />
<br />
see [[Users_Community_team#Dutch_language]]<br />
<br />
=== Norway ===<br />
* Olav Dahlum (olorin_) - odahlum at gmail dot com - Norwegian community member<br />
<br />
=== Pakistan ===<br />
* M Younis Soomro (mysoomro) - myounis.mcs@gmail.com - Trying to introduce and spread Linux (Mageia & other distros) in Pakistan.<br />
<br />
=== Paraguay ===<br />
* KSEltar (kseltar) - kseltar(at)gmail.com - Deshn FLOSS community: promotion of Mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Poland ===<br />
* Daniel Napora (napcok) - napcok at gmail dot com - Polish community ([http://mageia.org.pl])<br />
<br />
=== Portugal ===<br />
* Manuela Silva - alfalb - manuelaDOTsilvaATskyDOTcom - Interpreter/translator and proof-reader<br />
* Alfredo Silva - alfalb - alfalbDOTasATgmailDOTcom - Translator and proof-reader<br />
<br />
=== Romania ===<br />
* Cazacu Bogdan (Bogo) - cazacu DOT bogdan AT gmail DOT com - Romanian community. forum moderation, achieving deadlines as part of the romanian group for the international group.<br />
* Florin Cătălin RUSSEN (Piratu) - cfrussen AT yahoo DOT co DOT uk - Romanian community: moderate forum, interacting with international community<br />
* Florin Pulbere (Gremlin) - kernelgremlin AT gmail DOT com - Romanian community.<br />
<br />
=== Russia ===<br />
* Eugene Zhuravlev (macdowell) - macdowell AT cybsec DOT org - Russian community ([http://www.mageia-ru.org])<br />
* Mitya (mitya) - mitya AT cargosoft DOT ru - promotion at Russian opensource news sites (linux.org.ru), #mageia-ru<br />
* ?? (tejen) - ?? - Mageia website and forum [http://mageialinux.ru/ http://mageialinux.ru/]<br />
* Alexey Dolotov (sevo44) - dolotov44 AT yandex DOT ru - wants to help take good care of the Russian forums and wiki, including of security (ssl certificate and back-ups) and considers moving forums and wiki to a different domain to be able to do that <!--https://forum.mageia-linux.ru/ https://wiki.mageia-linux.ru/--><br />
<br />
=== Serbia ===<br />
* Toma Janković (tomaja) - tomaja@linuxo.org - Serbian community: promotion of mageia, translations, howtos, interactions with the international communities, etc.<br />
<br />
=== Slovenia ===<br />
* Filip Komar (filip) - filip(at)mageia.org - translation<br />
<br />
=== South Africa ===<br />
* Rory Albertyn (Gripen) - nicodeamus(at)gmail.com - South African community<br />
<br />
=== Spanish (not just Spain) ===<br />
* barsalatino - barsalatino - barsalatino@gmail.com - Spanish-speaking community (Blogdrake)<br />
* Drakedalfa - drakedalfa - drakedalfa at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Diego Bello - jacen - dbello at gmail.com - Spanish-speaking community (Blogdrake)<br />
* Felix Martos (asinkeBOFH) - felix.martos AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Fernando Anthony Ristaño (Drakor) - drakorbofh AT gmail DOT com - Spanish-speaking community (Blogdrake) and Argentina community (Ardriva) - - promoting mageia on events in Argentina<br />
* Gonzalo Igartua (GregoryBravas) - <del>gigartua@ AT mail.com DOT</del> - Spanish-speaking community (BlogDrake)<br />
** ''E-mail bounces when leaving out the dot "." after "com"'' <code>550 5.1.1 ... User is unknown {mx-us011}</code> <br />
* Sinner from the Prairy (SinnerBOFH) - sinnerbofh AT gmail DOT com - Spanish-speaking community (BlogDrake)<br />
* Tomàs Deltell (Annubis) - tomasdeltell AT gmx DOT es - Spanish-speaking community (Blogdrake)<br />
* vfmBOFH - vfmBOFH - vfmbofh(at)gmail.com - Spanish-speaking community (Blogdrake)<br />
<br />
Available domain names: mageia-es.org, mageia.com.ar<br />
<br />
=== Swedish (not just Sweden) ===<br />
* David V. Wallin (dvwallin) - <del>david AT ngweb DOT se</del> - Running http://mageia-se.org for the Swedish Community<br />
** ''E-mail bounced:'' <code>DNS Error: Domain name not found</code><br />
* Kristoffer Grundström (Umeaboy) - kristoffer dot grundstrom 1983 at gmail dot com - Founder and operator of the Swedish IRC-channels #mageia-sv and mageia-se<br />
* Sebastian (sebsebseb) - #mageia-sv and #mageia-se - Swedish Channels IRC Operator<br />
<br />
=== Taiwan ===<br />
[http://groups.google.com/group/mageia-taiwan Mageia Taiwanese user group]<br />
* 姚智偉 (kira) - elegant . pegasus AT gmail . com = Taiwanese user group moderator.<br />
* You-Cheng Hsieh (yochenhsieh) - yochenhsieh AT gmail . com - Taiwanese user group moderator.<br />
<br />
=== Turkey ===<br />
* Atilla ÖNTAŞ - <tarakbumba> - tarakbumba@gmail.com - Turkish community (Mandriva Turkiye).<br />
<br />
=== Tunisia ===<br />
* Beltaif Belgacem - <Gasston> - beltaif_bel@live.fr - Tunisia community.<br />
<br />
=== United Arab Emirates === <br />
* Ali Jawad (theforsaken) - amjjawad AT gmail DOT com - Ready for anything to help out, just let me know.<br />
<br />
=== United Kingdom ===<br />
* Margot Lawrence - margot at otfordduckscomputers.co.uk - IRC #mageia-uk & user help for people physically located in the UK<br />
* Sebastian (sebsebseb) - #mageia-uk irc channel - UK Users Community Founder<br />
<br />
=== United States ===<br />
* Alan Augustson (VoodooDali) - alan DOT augustson AT gmail DOT com - Chicago, IL, US. Longtime Mandriva user, interested in communications, marketing and artwork. NOT a programmer/developer; more like an advanced user.<br />
* Fini Decima - finid [AT] LinuxBSDos.com - Publisher of http://linuxbsdos.com<br />
* Kevin E. Ivey (lnxguy) - ik04[at]isot.com - Longtime Mandrake/Mandriva user and supporter since Day One. Founder of the Fort Hood Area Linux Users Group- HoodLUG. Active in advocacy efforts for Linux/FOSS.<br />
* Tracy W. Holz - tracy[at]htredneck.com - Live in the Dallas area, Involved in the Open Source/Linux podcast area, I go by the nick - Holzster<br />
* Josh King (dotmil) - josh AT dotmil.org - Abilene, TX area; working within F/OSS for nearly a decade now. Professional system admin, part time hacker and jack of many trades</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Building_the_Live_ISOs&diff=37561Building the Live ISOs2017-10-07T09:48:58Z<p>Dtux: modified helpfull links</p>
<hr />
<div>[By Martin Whitaker]<br />
<br />
=Background=<br />
<br />
The tool used to create the Live ISOs is [[draklive]]. This is packaged and available to be installed <br />
on any Mageia system. The latest version is in cauldron and has been back-ported to infra5, to allow <br />
its use on the Mageia build servers.<br />
<br />
==draklive builds the ISOs in four steps==<br />
<br />
===1. Install===<br />
This uses the classic installer to install a standard Mageia system into a dummy root file system <br />
and then performs any post-install "tweaks" specified by user. The only significant difference to a <br />
standard install is that it installs support for all hardware (rather than detecting what is <br />
required for the target machine), and (optionally) installs support for all locales.<br />
<br />
===2. Boot===<br />
This creates the initrd and installs the bootloader in the dummy file system. It also prepares the <br />
additional files needed for booting a hybrid ISO (i.e. booting either from a real DVD or from a USB <br />
stick).<br />
===3. Loop===<br />
This compresses the dummy file system into a 'squashfs' file system image. This gets stored on the <br />
final ISO in the file 'loopbacks/distrib-lzma.sqfs'. When you boot a Live system, this gets mounted <br />
(read-only) and merged with a RAM disk using the 'unionfs' filesystem. This merging with a RAM disk <br />
is what allows changes to be made to a running Live system.<br />
===4. Master===<br />
This builds the final ISO image from the files created in the Boot and Loop steps.<br />
<br />
draklive provides a number of other functions, but none of these are used in creating the Live ISOs.<br />
<br />
==The Live ISO composition is specified by three configuration files==<br />
<br />
===1. settings===<br />
<br />
Specified via the --settings command line option (defaults to ./config/settings.cfg). This is a <br />
simple text file.<br />
<br />
Contains the most basic settings: DE, arch, region(s), path to repository, path to build dir, etc. <br />
Most can be overridden by the --define command line option, which saves editing the file when <br />
generating the different flavours of Live ISO.<br />
<br />
===2. config===<br />
<br />
Specified via the --config command line option (defaults to ./config/live.cfg). This uses perl syntax.<br />
<br />
Contains a more detailed specification of the Live ISO makeup. Mostly this is the "tweaks" mentioned <br />
above.<br />
<br />
===3. auto_install===<br />
<br />
Specified via the $system->{auto_install} setting in the config file (defaults to <br />
./config/auto_inst.cfg.pl). This uses perl syntax.<br />
<br />
This is the standard method of driving the classic installer in non-interactive mode. Mostly it is <br />
used for package selection. The file format is extensively documented at <br />
https://wiki.mageia.org/en/Auto_inst.<br />
<br />
Any other files used to create the Live ISOs will be referenced in one of the above files.<br />
<br />
=Building Locally=<br />
<br />
Although draklive can be configured to use a remote repository, if you are going to do this more <br />
than once it is advisable to create a local mirror. I do this by:<br />
<br />
MIRROR=rsync://rsync.mirrorservice.org/mageia.org/pub/mageia<br />
LOCAL_REPO=<path to big disk partition>/mageia<br />
RELEASE=cauldron<br />
rsync -avuH --delete $MIRROR/distrib/$RELEASE/i586 $LOCAL_REPO/distrib/$RELEASE/<br />
rsync -avuH --delete $MIRROR/distrib/$RELEASE/x86_64 $LOCAL_REPO/distrib/$RELEASE/<br />
<br />
Be warned that these take a considerable amount of disk space - currently 71GB for cauldron/i586 and <br />
73GB for cauldron/x86_64. If you only want to build for one arch, you only need to mirror that arch.<br />
<br />
Now follow the following steps:<br />
<br />
1. Install draklive and its dependencies:<br />
sudo urpmi draklive<br />
If you want to make any changes to the draklive tool itself, you can instead get the source code by<br />
git clone git://git.mageia.org/software/build-system/draklive/<br />
and then in subsequent instructions replace the ''draklive'' command by<br />
perl -I../draklive/lib ../draklive/draklive <br />
(this assumes you check out draklive in the same directory as draklive-config). <br />
<br />
2. Clone the draklive-config repository and cd into the checked out copy:<br />
<br />
git clone git://git.mageia.org/software/build-system/draklive-config<br />
cd draklive-config<br />
<br />
3. In draklive-config, modify ./config/settings.cfg to:<br />
* change the repository path, e.g.<br />
repository=$LOCAL_REPO/distrib/$RELEASE<br />
* change the version number, e.g.<br />
version=6-rc<br />
* change builddir and chroot to somewhere suitable on your local disk<br />
* builddir currently requires up to 5GB per Live flavour<br />
* chroot currently requires up to 8.5GB per Live flavour<br />
{{note| Don't enable updates_repository (this enables the testing repositories).}}<br />
<br />
4. In draklive-config, modify ./files/mga_rpms/update_media.sh to change the repository path, e.g.<br />
<br />
bcdmedia=$LOCAL_REPO/distrib/$RELEASE<br />
<br />
then update the local repo that will be included on the Live ISO<br />
(used for building the proprietary drivers and for installing grub2):<br />
<br />
pushd ./files/mga_rpms<br />
./update_media.sh<br />
popd<br />
<br />
5. In draklive-config, as root, run all four draklive stages:<br />
<br />
sudo draklive --all --define desktop=$DESKTOP --define arch=$ARCH<br />
<br />
where $DESKTOP can be one of<br />
<br />
* GNOME<br />
* Plasma<br />
* Xfce<br />
<br />
and $ARCH can be one of<br />
<br />
* i586<br />
* x86_64<br />
<br />
If you just want to build the default DE/arch specified by ./config/settings.cfg, then use:<br />
<br />
sudo draklive --all<br />
<br />
When rebuilding you just repeat step 5 (and step 4 if you have updated your local mirror). You can <br />
start from scratch by adding the option '--clean'. Alternatively you can just rerun some of the <br />
steps by replacing '--all' with one or more of<br />
<pre><br />
--install<br />
--boot<br />
--loop<br />
--master<br />
</pre><br />
This is useful when testing bug fixes - you can change individual files in the dummy file system and <br />
then just rerun the --loop and --master steps. The steps will be run in the correct order, <br />
regardless of which order you write them.<br />
<br />
NOTE: As an alternative to changing the paths in the configuration files, you can create soft links <br />
in your local file system to mimic the paths used on the Mageia server. This makes things easier <br />
when you want to commit other changes to the git repository.<br />
<br />
=Building on the Mageia Server=<br />
<br />
You will need a sysadmin to create you a login account on the build server (currently 'rabbit') and <br />
add you to the mga-users, mga-packagers, and mga-iso_makers groups. You will also need to have set <br />
up ssh as described in https://wiki.mageia.org/en/Packagers_ssh<br />
<br />
You connect to the server via ssh, e.g.<br />
<br />
ssh my_mageia_id@rabbit.mageia.org<br />
<br />
This gives you a command prompt on the server.<br />
<br />
To build a full set of Live ISOs, follow the following steps:<br />
<br />
* Clone the draklive-config repository and cd into the checked out copy:<br />
<br />
git clone git://git.mageia.org/software/build-system/draklive-config<br />
cd draklive-config<br />
<br />
* Execute the build script:<br />
<br />
./tools/build_live.sh &<br />
<br />
(run in the background in case your ssh connection goes down - the build should keep going)<br />
<br />
The ISOs are built on a RAM disk (/home/draklive/var_data) and then copied to the rsync directory <br />
(/home/bcd//home/bcd/public_html/isos/trial-builds/) from where you can download them onto your <br />
local machine using your preferred rsync tool (e.g. mageiasync). Because there isn't enough space on <br />
the RAM disk for all four builds, build_live.sh deletes them from the RAM disk once they have been <br />
copied to the rsync directory.<br />
<br />
You can of course build individual ISOs, by following the steps in 'Building Locally'.<br />
<br />
Because the dummy file system has the same file access permissions as a real system, you have <br />
limited access to it. This makes it hard to debug problems on the Mageia server, as the install logs <br />
are stored in /root/drakx on the dummy file system, and can only be read by root. I generally debug <br />
problems by building locally, but if the problems only occur on the Mageia server, I add some <br />
commands in the postInstall section in ./config/live.cfg to make the logs readable. Just remember to <br />
undo that before releasing the ISOs!<br />
<br />
The local repository on the build server is in /home/bcd/build_bcd/pieces. It is manually sync'd <br />
with the master repository by:<br />
<br />
sudo -u bcd /home/bcd/sync_pieces.sh<br />
<br />
This repository is also used for building the classic ISOs, so co-ordinate this with the other ISO <br />
builders. It is vital for all ISO builds that the local repository doesn't change during the build <br />
process.<br />
<br />
==Helpfull links==<br />
* Draklive documentation [https://wiki.mageia.org/en/Draklive]<br />
* Auto_inst.cfg.pl manual pages [https://wiki.mageia.org/en/Auto_inst]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Building_the_Live_ISOs&diff=37560Building the Live ISOs2017-10-07T09:39:05Z<p>Dtux: add helpfull links</p>
<hr />
<div>[By Martin Whitaker]<br />
<br />
=Background=<br />
<br />
The tool used to create the Live ISOs is [[draklive]]. This is packaged and available to be installed <br />
on any Mageia system. The latest version is in cauldron and has been back-ported to infra5, to allow <br />
its use on the Mageia build servers.<br />
<br />
==draklive builds the ISOs in four steps==<br />
<br />
===1. Install===<br />
This uses the classic installer to install a standard Mageia system into a dummy root file system <br />
and then performs any post-install "tweaks" specified by user. The only significant difference to a <br />
standard install is that it installs support for all hardware (rather than detecting what is <br />
required for the target machine), and (optionally) installs support for all locales.<br />
<br />
===2. Boot===<br />
This creates the initrd and installs the bootloader in the dummy file system. It also prepares the <br />
additional files needed for booting a hybrid ISO (i.e. booting either from a real DVD or from a USB <br />
stick).<br />
===3. Loop===<br />
This compresses the dummy file system into a 'squashfs' file system image. This gets stored on the <br />
final ISO in the file 'loopbacks/distrib-lzma.sqfs'. When you boot a Live system, this gets mounted <br />
(read-only) and merged with a RAM disk using the 'unionfs' filesystem. This merging with a RAM disk <br />
is what allows changes to be made to a running Live system.<br />
===4. Master===<br />
This builds the final ISO image from the files created in the Boot and Loop steps.<br />
<br />
draklive provides a number of other functions, but none of these are used in creating the Live ISOs.<br />
<br />
==The Live ISO composition is specified by three configuration files==<br />
<br />
===1. settings===<br />
<br />
Specified via the --settings command line option (defaults to ./config/settings.cfg). This is a <br />
simple text file.<br />
<br />
Contains the most basic settings: DE, arch, region(s), path to repository, path to build dir, etc. <br />
Most can be overridden by the --define command line option, which saves editing the file when <br />
generating the different flavours of Live ISO.<br />
<br />
===2. config===<br />
<br />
Specified via the --config command line option (defaults to ./config/live.cfg). This uses perl syntax.<br />
<br />
Contains a more detailed specification of the Live ISO makeup. Mostly this is the "tweaks" mentioned <br />
above.<br />
<br />
===3. auto_install===<br />
<br />
Specified via the $system->{auto_install} setting in the config file (defaults to <br />
./config/auto_inst.cfg.pl). This uses perl syntax.<br />
<br />
This is the standard method of driving the classic installer in non-interactive mode. Mostly it is <br />
used for package selection. The file format is extensively documented at <br />
https://wiki.mageia.org/en/Auto_inst.<br />
<br />
Any other files used to create the Live ISOs will be referenced in one of the above files.<br />
<br />
=Building Locally=<br />
<br />
Although draklive can be configured to use a remote repository, if you are going to do this more <br />
than once it is advisable to create a local mirror. I do this by:<br />
<br />
MIRROR=rsync://rsync.mirrorservice.org/mageia.org/pub/mageia<br />
LOCAL_REPO=<path to big disk partition>/mageia<br />
RELEASE=cauldron<br />
rsync -avuH --delete $MIRROR/distrib/$RELEASE/i586 $LOCAL_REPO/distrib/$RELEASE/<br />
rsync -avuH --delete $MIRROR/distrib/$RELEASE/x86_64 $LOCAL_REPO/distrib/$RELEASE/<br />
<br />
Be warned that these take a considerable amount of disk space - currently 71GB for cauldron/i586 and <br />
73GB for cauldron/x86_64. If you only want to build for one arch, you only need to mirror that arch.<br />
<br />
Now follow the following steps:<br />
<br />
1. Install draklive and its dependencies:<br />
sudo urpmi draklive<br />
If you want to make any changes to the draklive tool itself, you can instead get the source code by<br />
git clone git://git.mageia.org/software/build-system/draklive/<br />
and then in subsequent instructions replace the ''draklive'' command by<br />
perl -I../draklive/lib ../draklive/draklive <br />
(this assumes you check out draklive in the same directory as draklive-config). <br />
<br />
2. Clone the draklive-config repository and cd into the checked out copy:<br />
<br />
git clone git://git.mageia.org/software/build-system/draklive-config<br />
cd draklive-config<br />
<br />
3. In draklive-config, modify ./config/settings.cfg to:<br />
* change the repository path, e.g.<br />
repository=$LOCAL_REPO/distrib/$RELEASE<br />
* change the version number, e.g.<br />
version=6-rc<br />
* change builddir and chroot to somewhere suitable on your local disk<br />
* builddir currently requires up to 5GB per Live flavour<br />
* chroot currently requires up to 8.5GB per Live flavour<br />
{{note| Don't enable updates_repository (this enables the testing repositories).}}<br />
<br />
4. In draklive-config, modify ./files/mga_rpms/update_media.sh to change the repository path, e.g.<br />
<br />
bcdmedia=$LOCAL_REPO/distrib/$RELEASE<br />
<br />
then update the local repo that will be included on the Live ISO<br />
(used for building the proprietary drivers and for installing grub2):<br />
<br />
pushd ./files/mga_rpms<br />
./update_media.sh<br />
popd<br />
<br />
5. In draklive-config, as root, run all four draklive stages:<br />
<br />
sudo draklive --all --define desktop=$DESKTOP --define arch=$ARCH<br />
<br />
where $DESKTOP can be one of<br />
<br />
* GNOME<br />
* Plasma<br />
* Xfce<br />
<br />
and $ARCH can be one of<br />
<br />
* i586<br />
* x86_64<br />
<br />
If you just want to build the default DE/arch specified by ./config/settings.cfg, then use:<br />
<br />
sudo draklive --all<br />
<br />
When rebuilding you just repeat step 5 (and step 4 if you have updated your local mirror). You can <br />
start from scratch by adding the option '--clean'. Alternatively you can just rerun some of the <br />
steps by replacing '--all' with one or more of<br />
<pre><br />
--install<br />
--boot<br />
--loop<br />
--master<br />
</pre><br />
This is useful when testing bug fixes - you can change individual files in the dummy file system and <br />
then just rerun the --loop and --master steps. The steps will be run in the correct order, <br />
regardless of which order you write them.<br />
<br />
NOTE: As an alternative to changing the paths in the configuration files, you can create soft links <br />
in your local file system to mimic the paths used on the Mageia server. This makes things easier <br />
when you want to commit other changes to the git repository.<br />
<br />
=Building on the Mageia Server=<br />
<br />
You will need a sysadmin to create you a login account on the build server (currently 'rabbit') and <br />
add you to the mga-users, mga-packagers, and mga-iso_makers groups. You will also need to have set <br />
up ssh as described in https://wiki.mageia.org/en/Packagers_ssh<br />
<br />
You connect to the server via ssh, e.g.<br />
<br />
ssh my_mageia_id@rabbit.mageia.org<br />
<br />
This gives you a command prompt on the server.<br />
<br />
To build a full set of Live ISOs, follow the following steps:<br />
<br />
* Clone the draklive-config repository and cd into the checked out copy:<br />
<br />
git clone git://git.mageia.org/software/build-system/draklive-config<br />
cd draklive-config<br />
<br />
* Execute the build script:<br />
<br />
./tools/build_live.sh &<br />
<br />
(run in the background in case your ssh connection goes down - the build should keep going)<br />
<br />
The ISOs are built on a RAM disk (/home/draklive/var_data) and then copied to the rsync directory <br />
(/home/bcd//home/bcd/public_html/isos/trial-builds/) from where you can download them onto your <br />
local machine using your preferred rsync tool (e.g. mageiasync). Because there isn't enough space on <br />
the RAM disk for all four builds, build_live.sh deletes them from the RAM disk once they have been <br />
copied to the rsync directory.<br />
<br />
You can of course build individual ISOs, by following the steps in 'Building Locally'.<br />
<br />
Because the dummy file system has the same file access permissions as a real system, you have <br />
limited access to it. This makes it hard to debug problems on the Mageia server, as the install logs <br />
are stored in /root/drakx on the dummy file system, and can only be read by root. I generally debug <br />
problems by building locally, but if the problems only occur on the Mageia server, I add some <br />
commands in the postInstall section in ./config/live.cfg to make the logs readable. Just remember to <br />
undo that before releasing the ISOs!<br />
<br />
The local repository on the build server is in /home/bcd/build_bcd/pieces. It is manually sync'd <br />
with the master repository by:<br />
<br />
sudo -u bcd /home/bcd/sync_pieces.sh<br />
<br />
This repository is also used for building the classic ISOs, so co-ordinate this with the other ISO <br />
builders. It is vital for all ISO builds that the local repository doesn't change during the build <br />
process.<br />
<br />
==Helpfull links==<br />
https://wiki.mageia.org/en/Draklive<br />
https://wiki.mageia.org/en/Auto_inst</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Draklive&diff=37559Draklive2017-10-07T09:37:06Z<p>Dtux: add a link in references</p>
<hr />
<div>{{introduction|{{prog|draklive}} is a mastering tool that builds a live distribution according to a configuration file, creates a master image, and optionally installs it on a device. It is the tool used and maintained by Mageia to build the distribution Live medias.}}<br />
<br />
== Advantages ==<br />
{{prog|draklive}}'s philosophy is to keep the live distribution as close as possible to a normal Mageia Linux distribution. All live-specific tweaks are done in a tiny {{prog|initrd}} script. Since the Draklive initrd script is generated on-the-fly, it is very small, and is quite easy to debug should there be any problems.<br />
<br />
The list of drivers included in the {{prog|initrd}} is adjusted during the live distribution creation, according to the medium type. {{prog|draklive}} uses the DrakX libraries to ensure an up-to-date drivers list is used.<br />
<br />
Once the {{prog|initrd}} script has finished booting, the system's root device will be used transparently by the distribution, and no additional tricks are required.<br />
<br />
Hardware detection is done with {{prog|harddrake}}, providing reliable integration with the host system.<br />
<br />
== Features ==<br />
* live CD<br />
* live distribution on USB key<br />
* easy to test over NFS<br />
* uses the Mageia installer to create the live system<br />
* fully read-write live system (using {{prog|unionfs}})<br />
* automatic hardware configuration (using {{prog|harddrake}})<br />
* generic code structure to make new technical choices quickly usable<br />
<br />
== Quickstart ==<br />
'''Before continuing:''' The following packages <b>must</b> be installed on your system: {{pkg|x11-server-xnest}} {{pkg|squashfs-tools}} {{pkg|syslinux}} {{pkg|mkisofs}} {{pkg|rsync}} {{pkg|curl}} {{pkg|mtools}}.<br>For a better compression {{pkg|squashfs3-tools}} is required.<br />
<br />
=== Getting the tool ===<br />
Normally this is done by simply installing the {{pkg|draklive}} package. If you want to make any changes to the draklive tool itself, you can instead get the source code by<br />
git clone git://git.mageia.org/software/build-system/draklive/<br />
and then in subsequent instructions replace the {{cmd|draklive}} command by {{cmd|perl -I../draklive/lib ../draklive/draklive}} (this assumes you check out draklive in the same directory as draklive-config).<br />
<br />
=== Getting the config files ===<br />
git clone git://git.mageia.org/software/build-system/draklive-config/<br />
cd draklive-config<br />
<br />
Then, edit the repository address (and other local settings) in {{file|config/settings.cfg}}. Note that the repository address can be a URL to a remote server or a simple path to a local file system. If you are intending to create your own "remixed" Live ISO (and hence likely take a few attempts to get it just right), it is worth setting up your own local repository mirror to save repeatedly downloading the files.<br />
<br />
=== Building a live CD or live USB ===<br />
{{root console|draklive --clean --all}}<br />
<br />
See the output of '''{{cmd|draklive --help}}''' for more details.<br />
<br />
=== Recording a live USB ===<br />
{{root console|draklive --record --device /dev/sdX}}<br />
<br />
Where /dev/sdX is your USB key disk device (not partition)<br />
<br />
== Configuration ==<br />
=== Example ===<br />
<pre><br />
{<br />
system => {<br />
root => '/chroot/live/4',<br />
repository => '/mnt/BIG/dis/4/i586',<br />
auto_install => 'config/auto_inst.cfg.pl',<br />
rpmsrate => 'config/rpmsrate',<br />
vga_mode => 788,<br />
install_env => {<br />
},<br />
},<br />
media => {<br />
storage => 'cdrom',<br />
},<br />
mount => $predefined{mounts}{volatile_squash_union},<br />
};<br />
</pre><br />
<br />
=== Example: Creating a bootable cdrom for old computers unable to boot from a USB key ===<br />
Modify the file {{file|config/live.cfg}} media hash as follows:<br />
<br />
<pre><br />
media => { storage => 'usb', boot => 'cdrom' },<br />
</pre><br />
<br />
And then run the command:<br />
<br />
<pre><br />
perl -I../draklive/lib ../draklive/draklive --config config/live.cfg --boot-only --boot --master<br />
</pre><br />
<br />
This will create the iso file: {{file|/your_workdir/images/boot.iso}} ({{file|your_workdir}} is {{file|/var/lib/draklive}} by default)<br />
<br />
=== Choosing Desktop Environnement ===<br />
To change the target desktop, pass<br />
--desktop=PLASMA5|GNOME|xfce4|LXDE|Enlightenment<br />
<br />
=== Package selection ===<br />
If you need to adjust packages selection, edit 'rpmsrate_flags_chosen' for rpmsrate categories, 'default_packages' for additional packages, 'skipped_packages' to save space.<br />
<br />
=== Exhaustive description ===<br />
The configuration file should contain a hash of settings. Some settings have to be filled in the top-level, others have to be grouped in sub-hashes.<br />
<br />
==== system sub-hash ====<br />
This hash describes the installed distribution.<br />
<br />
* {{cmd|root}}: path of the installed distribution<br />
* {{cmd|repository}}: path to the installer repository<br />
* {{cmd|auto_install}}: installer {{file|auto_inst.cfg.pl}} file<br />
* {{cmd|patch_install}}: installer patch file (actually defcfg file)<br />
* {{cmd|postInstall}}: commands to be run (using <b>{{cmd|bash -c}}</b> after all the additional_media/rpm/patches steps are done)<br />
* {{cmd|install_env}}: hash reference of variables that should be passed to install (they will be usable in the {{file|auto_inst.cfg.pl}} as well)<br />
* {{cmd|additional_modules}}: array reference of {{file|.ko}} modules to be copied and loaded in the {{file|initrd}}<br />
* {{cmd|rpmsrate}}: local {{prog|rpmsrate}} path (useful to add/modify/remove packages rate)<br />
* {{cmd|patches}}: array reference of patches to be applied directly in system root<br />
* {{cmd|rpms}}: array reference of rpms to be installed after installation<br />
* {{cmd|vga_mode}}: graphical mode which the live distribution should use<br />
* {{cmd|splash}}: set to <i>no</i> if you don't want to use a splash (default is <i>yes</i>)<br />
* {{cmd|kernel}}: default kernel release (optional)<br />
<br />
==== media sub-hash ====<br />
This hash describes which medium access should be used.<br />
<br />
* {{cmd|storage}}: medium type (<i>cdrom</i> or <i>usb</i>)<br />
<br />
Optional fields:<br />
<br />
* {{cmd|boot}}: boot medium type to be used with {{cmd|--boot-only}} option, if any (<i>cdrom</i> or <i>usb</i>)<br />
<br />
Or customised settings:<br />
<br />
* {{cmd|$custom{media}{nfs}->(<i>module name</i>, <i>live system IP address</i>, <i>NFS source</i>)}}<br />
<br />
==== extra_media sub-array ====<br />
This array should contain all extra media (see media sub-hash description) that the live system should support. This allows to make live systems using different boot types, using the copy wizard. For example, if the default media is of the ''cdrom'' type, and the extra media array contains a media using the ''usb'' type, the running live CD will allow to duplicate itself to both USB keys and CDs.<br />
<br />
==== mount sub-hash ====<br />
This hash describes how the live components have to be mounted together.<br />
<br />
Some basic setups are predefined:<br />
<br />
* {{cmd|$predefined{mounts}{simple_union} }}: use the media contents as raw root, and mount it with a tmpfs using {{prog|unionfs}}, to get a RW system<br />
* {{cmd|$predefined{mounts}{volatile_squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, uses a tmpfs, and mounts them together using {{prog|unionfs}}<br />
* {{cmd|$predefined{mounts}{squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, a {{file|system.loop}} ext2 read-writable loopback file, and mounts them together using {{prog|unionfs}}<br />
* {{cmd|$predefined{mounts}{multi_squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, optionally uses a read-only {{file|system.sqfs}} "patch", a tmpfs, and mounts them together using {{prog|unionfs}}<br />
<br />
Or build your own mount type:<br />
<br />
{{...}}<br />
<br />
==== top-level settings ====<br />
Live settings:<br />
<br />
* {{cmd|post}}: array of commands to be run at end of {{cmd|initrd}}<br />
* {{cmd|copy_initrd}}: copy the {{file|initrd}} to this location at the end of the {{cmd|initrd}} step (e.g. to {{file|/var/lib/tftpboot/live.rdz}})<br />
* {{cmd|debug}}: include some debug tools in {{cmd|initrd}} ({{prog|busybox}}, {{prog|strace}}, {{prog|ping}}) and run a debug shell at beginning of {{cmd|initrd}}<br />
<br />
Directory settings (all optional):<br />
<br />
* {{cmd|workdir}}: {{prog|draklive}} working directory (defaults to {{file|/tmp/draklive}})<br />
* {{cmd|mnt}}: temporary mount point for {{prog|draklive}}<br />
<br />
<br />
== References ==<br />
=== draklive tools and One configuration files ===<br />
<br />
* https://wiki.mageia.org/en/Building_the_Live_ISOs<br />
* https://wiki.mageia.org/en/Auto_inst<br />
* http://gitweb.mageia.org/software/build-system/draklive/<br />
* http://gitweb.mageia.org/software/build-system/draklive-config/<br />
* <b>perldoc draklive</b><br />
<br />
=== Other live tools ===<br />
* [http://livecd.berlios.de/ mklivecd]<br />
* [http://www.linux-live.org/ linux-live]<br />
* [http://wiki.debian.org/DebianLive/ Debian live tools] (make-live and casper)<br />
<br />
<br />
== Overlay filesystems ==<br />
==== UnionFS ====<br />
<br />
* http://www.fsl.cs.sunysb.edu/project-unionfs.html<br />
* http://www.unionfs.org/<br />
* http://www.linuxjournal.com/article/7714<br />
<br />
==== Other ====<br />
* [http://www.atconsultancy.nl/cowloop/ cowloop]<br />
* [http://www.denx.de/wiki/bin/view/Know/MiniFOHome mini_fo (the mini fanout overlay file system)]<br />
* [http://aufs.sourceforge.net/ aufs: another unionfs]<br />
<br />
<br />
== Debug ==<br />
<br />
If you need to debug the draklive you need to search for the file ddebug.log in the build directory of the live installation.<br />
<br />
== FAQ ==<br />
* Missing squashfs and lzma files?<br />
<br />
In case you get an error "missing squashfs" and "missing lzma" you should uninstall the dkms-lzma and dkms-squashfs and install kernel-lzma and kernel-squashfs. You have to reboot the system after this and before starting draklive, modprobe squashfs. Also you can add in live.cfg in the section "rpms": "media/main/squashfs-lzma-kernel-2.6.31.5-desktop-1mnb-3.3-11mdv2010.0.i586.rpm" and "media/main/lzma-kernel-2.6.31.5-desktop-1mnb-4.43-28mdv2010.0.i586.rpm".<br />
<br />
<br />
<br />
{{Template:MdvImport}}<br />
[[fr:Draklive]]<br />
<br />
[[Category:Contributors]]<br />
[[Category:Howtos]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Draklive&diff=37558Draklive2017-10-07T09:35:28Z<p>Dtux: Add a link in rferences</p>
<hr />
<div>{{introduction|{{prog|draklive}} is a mastering tool that builds a live distribution according to a configuration file, creates a master image, and optionally installs it on a device. It is the tool used and maintained by Mageia to build the distribution Live medias.}}<br />
<br />
== Advantages ==<br />
{{prog|draklive}}'s philosophy is to keep the live distribution as close as possible to a normal Mageia Linux distribution. All live-specific tweaks are done in a tiny {{prog|initrd}} script. Since the Draklive initrd script is generated on-the-fly, it is very small, and is quite easy to debug should there be any problems.<br />
<br />
The list of drivers included in the {{prog|initrd}} is adjusted during the live distribution creation, according to the medium type. {{prog|draklive}} uses the DrakX libraries to ensure an up-to-date drivers list is used.<br />
<br />
Once the {{prog|initrd}} script has finished booting, the system's root device will be used transparently by the distribution, and no additional tricks are required.<br />
<br />
Hardware detection is done with {{prog|harddrake}}, providing reliable integration with the host system.<br />
<br />
== Features ==<br />
* live CD<br />
* live distribution on USB key<br />
* easy to test over NFS<br />
* uses the Mageia installer to create the live system<br />
* fully read-write live system (using {{prog|unionfs}})<br />
* automatic hardware configuration (using {{prog|harddrake}})<br />
* generic code structure to make new technical choices quickly usable<br />
<br />
== Quickstart ==<br />
'''Before continuing:''' The following packages <b>must</b> be installed on your system: {{pkg|x11-server-xnest}} {{pkg|squashfs-tools}} {{pkg|syslinux}} {{pkg|mkisofs}} {{pkg|rsync}} {{pkg|curl}} {{pkg|mtools}}.<br>For a better compression {{pkg|squashfs3-tools}} is required.<br />
<br />
=== Getting the tool ===<br />
Normally this is done by simply installing the {{pkg|draklive}} package. If you want to make any changes to the draklive tool itself, you can instead get the source code by<br />
git clone git://git.mageia.org/software/build-system/draklive/<br />
and then in subsequent instructions replace the {{cmd|draklive}} command by {{cmd|perl -I../draklive/lib ../draklive/draklive}} (this assumes you check out draklive in the same directory as draklive-config).<br />
<br />
=== Getting the config files ===<br />
git clone git://git.mageia.org/software/build-system/draklive-config/<br />
cd draklive-config<br />
<br />
Then, edit the repository address (and other local settings) in {{file|config/settings.cfg}}. Note that the repository address can be a URL to a remote server or a simple path to a local file system. If you are intending to create your own "remixed" Live ISO (and hence likely take a few attempts to get it just right), it is worth setting up your own local repository mirror to save repeatedly downloading the files.<br />
<br />
=== Building a live CD or live USB ===<br />
{{root console|draklive --clean --all}}<br />
<br />
See the output of '''{{cmd|draklive --help}}''' for more details.<br />
<br />
=== Recording a live USB ===<br />
{{root console|draklive --record --device /dev/sdX}}<br />
<br />
Where /dev/sdX is your USB key disk device (not partition)<br />
<br />
== Configuration ==<br />
=== Example ===<br />
<pre><br />
{<br />
system => {<br />
root => '/chroot/live/4',<br />
repository => '/mnt/BIG/dis/4/i586',<br />
auto_install => 'config/auto_inst.cfg.pl',<br />
rpmsrate => 'config/rpmsrate',<br />
vga_mode => 788,<br />
install_env => {<br />
},<br />
},<br />
media => {<br />
storage => 'cdrom',<br />
},<br />
mount => $predefined{mounts}{volatile_squash_union},<br />
};<br />
</pre><br />
<br />
=== Example: Creating a bootable cdrom for old computers unable to boot from a USB key ===<br />
Modify the file {{file|config/live.cfg}} media hash as follows:<br />
<br />
<pre><br />
media => { storage => 'usb', boot => 'cdrom' },<br />
</pre><br />
<br />
And then run the command:<br />
<br />
<pre><br />
perl -I../draklive/lib ../draklive/draklive --config config/live.cfg --boot-only --boot --master<br />
</pre><br />
<br />
This will create the iso file: {{file|/your_workdir/images/boot.iso}} ({{file|your_workdir}} is {{file|/var/lib/draklive}} by default)<br />
<br />
=== Choosing Desktop Environnement ===<br />
To change the target desktop, pass<br />
--desktop=PLASMA5|GNOME|xfce4|LXDE|Enlightenment<br />
<br />
=== Package selection ===<br />
If you need to adjust packages selection, edit 'rpmsrate_flags_chosen' for rpmsrate categories, 'default_packages' for additional packages, 'skipped_packages' to save space.<br />
<br />
=== Exhaustive description ===<br />
The configuration file should contain a hash of settings. Some settings have to be filled in the top-level, others have to be grouped in sub-hashes.<br />
<br />
==== system sub-hash ====<br />
This hash describes the installed distribution.<br />
<br />
* {{cmd|root}}: path of the installed distribution<br />
* {{cmd|repository}}: path to the installer repository<br />
* {{cmd|auto_install}}: installer {{file|auto_inst.cfg.pl}} file<br />
* {{cmd|patch_install}}: installer patch file (actually defcfg file)<br />
* {{cmd|postInstall}}: commands to be run (using <b>{{cmd|bash -c}}</b> after all the additional_media/rpm/patches steps are done)<br />
* {{cmd|install_env}}: hash reference of variables that should be passed to install (they will be usable in the {{file|auto_inst.cfg.pl}} as well)<br />
* {{cmd|additional_modules}}: array reference of {{file|.ko}} modules to be copied and loaded in the {{file|initrd}}<br />
* {{cmd|rpmsrate}}: local {{prog|rpmsrate}} path (useful to add/modify/remove packages rate)<br />
* {{cmd|patches}}: array reference of patches to be applied directly in system root<br />
* {{cmd|rpms}}: array reference of rpms to be installed after installation<br />
* {{cmd|vga_mode}}: graphical mode which the live distribution should use<br />
* {{cmd|splash}}: set to <i>no</i> if you don't want to use a splash (default is <i>yes</i>)<br />
* {{cmd|kernel}}: default kernel release (optional)<br />
<br />
==== media sub-hash ====<br />
This hash describes which medium access should be used.<br />
<br />
* {{cmd|storage}}: medium type (<i>cdrom</i> or <i>usb</i>)<br />
<br />
Optional fields:<br />
<br />
* {{cmd|boot}}: boot medium type to be used with {{cmd|--boot-only}} option, if any (<i>cdrom</i> or <i>usb</i>)<br />
<br />
Or customised settings:<br />
<br />
* {{cmd|$custom{media}{nfs}->(<i>module name</i>, <i>live system IP address</i>, <i>NFS source</i>)}}<br />
<br />
==== extra_media sub-array ====<br />
This array should contain all extra media (see media sub-hash description) that the live system should support. This allows to make live systems using different boot types, using the copy wizard. For example, if the default media is of the ''cdrom'' type, and the extra media array contains a media using the ''usb'' type, the running live CD will allow to duplicate itself to both USB keys and CDs.<br />
<br />
==== mount sub-hash ====<br />
This hash describes how the live components have to be mounted together.<br />
<br />
Some basic setups are predefined:<br />
<br />
* {{cmd|$predefined{mounts}{simple_union} }}: use the media contents as raw root, and mount it with a tmpfs using {{prog|unionfs}}, to get a RW system<br />
* {{cmd|$predefined{mounts}{volatile_squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, uses a tmpfs, and mounts them together using {{prog|unionfs}}<br />
* {{cmd|$predefined{mounts}{squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, a {{file|system.loop}} ext2 read-writable loopback file, and mounts them together using {{prog|unionfs}}<br />
* {{cmd|$predefined{mounts}{multi_squash_union} }}: compress the distribution in a {{file|distrib.sqfs}} file, optionally uses a read-only {{file|system.sqfs}} "patch", a tmpfs, and mounts them together using {{prog|unionfs}}<br />
<br />
Or build your own mount type:<br />
<br />
{{...}}<br />
<br />
==== top-level settings ====<br />
Live settings:<br />
<br />
* {{cmd|post}}: array of commands to be run at end of {{cmd|initrd}}<br />
* {{cmd|copy_initrd}}: copy the {{file|initrd}} to this location at the end of the {{cmd|initrd}} step (e.g. to {{file|/var/lib/tftpboot/live.rdz}})<br />
* {{cmd|debug}}: include some debug tools in {{cmd|initrd}} ({{prog|busybox}}, {{prog|strace}}, {{prog|ping}}) and run a debug shell at beginning of {{cmd|initrd}}<br />
<br />
Directory settings (all optional):<br />
<br />
* {{cmd|workdir}}: {{prog|draklive}} working directory (defaults to {{file|/tmp/draklive}})<br />
* {{cmd|mnt}}: temporary mount point for {{prog|draklive}}<br />
<br />
<br />
== References ==<br />
=== draklive tools and One configuration files ===<br />
<br />
* https://wiki.mageia.org/en/Building_the_Live_ISOs<br />
* http://gitweb.mageia.org/software/build-system/draklive/<br />
* http://gitweb.mageia.org/software/build-system/draklive-config/<br />
* <b>perldoc draklive</b><br />
<br />
=== Other live tools ===<br />
* [http://livecd.berlios.de/ mklivecd]<br />
* [http://www.linux-live.org/ linux-live]<br />
* [http://wiki.debian.org/DebianLive/ Debian live tools] (make-live and casper)<br />
<br />
<br />
== Overlay filesystems ==<br />
==== UnionFS ====<br />
<br />
* http://www.fsl.cs.sunysb.edu/project-unionfs.html<br />
* http://www.unionfs.org/<br />
* http://www.linuxjournal.com/article/7714<br />
<br />
==== Other ====<br />
* [http://www.atconsultancy.nl/cowloop/ cowloop]<br />
* [http://www.denx.de/wiki/bin/view/Know/MiniFOHome mini_fo (the mini fanout overlay file system)]<br />
* [http://aufs.sourceforge.net/ aufs: another unionfs]<br />
<br />
<br />
== Debug ==<br />
<br />
If you need to debug the draklive you need to search for the file ddebug.log in the build directory of the live installation.<br />
<br />
== FAQ ==<br />
* Missing squashfs and lzma files?<br />
<br />
In case you get an error "missing squashfs" and "missing lzma" you should uninstall the dkms-lzma and dkms-squashfs and install kernel-lzma and kernel-squashfs. You have to reboot the system after this and before starting draklive, modprobe squashfs. Also you can add in live.cfg in the section "rpms": "media/main/squashfs-lzma-kernel-2.6.31.5-desktop-1mnb-3.3-11mdv2010.0.i586.rpm" and "media/main/lzma-kernel-2.6.31.5-desktop-1mnb-4.43-28mdv2010.0.i586.rpm".<br />
<br />
<br />
<br />
{{Template:MdvImport}}<br />
[[fr:Draklive]]<br />
<br />
[[Category:Contributors]]<br />
[[Category:Howtos]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Events_Box&diff=33312Events Box2016-08-29T21:25:15Z<p>Dtux: /* Asking for the box */</p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Marcom]]<br />
[[Category:Atelier]]<br />
[[Category:Events]]<br />
<br />
We need a first, small, limited events box to help keep together tools for each event.<br />
<br />
See the [[Events HowTo]] as well.<br />
<br />
== How does the box look like? ==<br />
TODO, picture<br />
<br />
== What's in the box? ==<br />
Box contents can be donated, directly, or through http://www.mageia.org/donate/.<br />
<br />
* contents checklist including inventory (for CDs/stickers/goodies) and state of tablecloths (washed/not washed).<br />
* cash box<br />
* a pen and a notebook<br />
<br />
Showcase:<br />
* big posters with Mageia logo - we have some<br />
* kakemono - we have one (and can get extra banners if wanted); posters fit in kakemono case<br />
<br />
Distribute:<br />
* CD, DVD - we have some discs left for Mageia 1, we need a solution for Mageia 2<br />
<br />
Goodies:<br />
* tshirts - we have some left from FOSDEM 2011 - we need an inventory and new series<br />
* stationery (stickers, contact list, flyers, contact cards/business cards, blank pre-printed CDs (to burn on the stand), CD sleeves) - we have some left - we need new ones - for booth and to distribute to attendees when one speaks at a conference<br />
<br />
== Where is the box? ==<br />
<br />
=== Current location of the box ===<br />
<br />
=== Current goodies around Europe ===<br />
{|+class="wikitable"<br />
|-<br />
|Country | city | T-shirts | stickers | flyers | USB Keys | pens | Tablecloth | kakemono | others |<br />
|-<br />
|France | Lyon | 4 x S - 5 x M - 5 x L-ladies - 10 x XL - 2 x XXL | 1 USB key | 8 Pens | 1 tablecloth | 1 kakemono |<br />
|-<br />
|}<br />
<br />
=== Next, planned locations ===<br />
<br />
=== Base locations ===<br />
Ideally, two locations, in France or in its direct periphery. Events that we will attend with this box are among: FOSDEM, LinuxTag, Solutions Linux, RMLL, OWF, JDLL, ORR, what others in Europe?<br />
<br />
=== Transportation costs ===<br />
Use these max limits to estimate roughly the cost:<br />
* weight: 10 kg<br />
* dimensions: 55 x 35 x 25 cm<br />
* declared value: 3000 €<br />
<br />
* cities: Paris, Marseille, Bordeaux, Nantes, Berlin, Bruxelles, London, Barcelona, Madrid, Rome, Lisbon<br />
Indicative average max prices (UPS - https://wwwapps.ups.com/ctc/request):<br />
* Paris -> {Brussel,Berlin}, ~300 €<br />
* Nantes -> Paris, ~100 € (about the same intra France?)<br />
<br />
* 10kg 120 x 60 x 60 cm 6,90€ (intra Germany), 22,00€ Germany->France (http://www.dhl.de/en.html)<br />
<br />
The actual cost may be less (the box may be lighter, smaller) or more (change in transportation fees).<br />
<br />
=== Asking for the box ===<br />
Wanted home candidates (multiple is better):<br />
* Nantes, FR: rda<br />
* Paris, FR: baud (Versailles, for SL, RMLL, PremierSamedi])<br />
* Berlin, DE: ?<br />
* Brussel, BE: ?<br />
* Lyon<br />
* other?<br />
<br />
== Grow the box! ==<br />
<br />
Here are other stuff good to have in the box.<br />
<br />
The whole package (box + contents) must not exceed 10 kg and must keep 55 x 35 x 25 cm (easier for someone to travel with it).<br />
<br />
* BOX itself (wish, no model/size decided) a box to fit all this, that can be handled by a single person, that has wheels and handles. Suggest medium (20kg, international roll-on size or a little larger) suitcase with at least one zipper poclet on the outside (for padlock &c during shipping).<br />
<br />
* (wish) event schedule and [[Events HowTo|howto]] (in this very wiki at least; a print copy is good too)<br />
* (wish) two large pieces of cloth: one white, one black. (see tablecloths in showcase. Black may be redundant...)<br />
* (wish) cables? RJ45, video, USB, multi powerplugs, type <br />
* (wish) small medikit, scissors, thread<br />
* (wish) velcro dots (both hook and fuzz), with adhesive back, two types (standard and strong)<br />
* (wish) good-quality packaging tape in tape-gun<br />
* (wish) good brass padlock to lock suitcase when travelling with someone<br />
* (wish) cycle lock (click-together type with coated cable or chain) to lock Events Box to racks on trains - prevent theft of Box<br />
<br />
Showcase stuff:<br />
* (must have) - 2 tablecloths for exhibition tables, white with mageia logo placed to be at front of table, sized for 2 180cm long x 90cm wide x 80cm high tables (so, (2*180)+(2*80) long and 90+(2*80) wide.) Mageia logo can be on vinyl like banner and poster, and be fixed with double-sided tape or velcro, or can be printed onto the cloth.<br />
* (wish) perspex or portable/foldable metal display stands for leaflets/brochures/cds. Metal will stand on floor beside tables, perspex on table (so metal might work better).<br />
* (wish, no model decided, price tag max 300 €) dedicated projector<br />
* (wish, no model decided, price tag max 200 € each) 2 dedicated laptops or small boxes (cubox, other?): one for projection, the other one for direct manipulation<br />
** one potential candidate, white ASRock Ion330 + keyboard + mouse and cables (second hand, ~150 € worth, rda)<br />
* for projection:<br />
** (wish) simple slides calling for contributors, with specific & easy tasks,<br />
** (wish) project presentation, demonstrating the product,<br />
** (wish) give immediate contact hooks (Web, IRC, Twitter, other events)<br />
** (wish) display a small twitter wall of the current event<br />
<br />
Distribute:<br />
* (wish) a system to dump a Mageia system image to USB key or portable HD<br />
* (wish) mageia-logo USB sticks<br />
* (idea) one of the computer is used either as a Wi-Fi access point (advertised as "Get Mageia") or as a station in the local network, and advertises shared directories (FTP, Samba) containing Mageia ISOs<br />
<br />
<br />
* interactive, live access to forums, IRC channels and other info source about the project<br />
** Maybe a projector connected to a laptop? Maybe more than one? Forums, wiki, an event-central IRC channel? I think a projector displaying a live feed of #mageia-social would be a good place to start. --[[User:Max|max]] 19:56, 16 July 2012 (UTC)<br />
* computers/projectors showcasing the OS: laptops, tablets, projectors<br />
<br />
<br />
== Other projects events boxes ==<br />
* http://live.gnome.org/GnomeEventsBox<br />
* other ?<br />
<br />
== Other ideas of goodies ==<br />
* USB key <br />
** 4 GB should be enough, ~5 € and could be proposed at 10 € with Mageia logo<br />
** http://www.memoriasusb.com<br />
* USB card<br />
** was here at Fosdem 2013, not seen since :/ 2 GB card with Mageia logo<br />
* stickers<br />
** see https://wiki.mageia.org/en/Commercial_vendors#Goodies_vendors<br />
<br />
== Documents to promote Mageia ==<br />
<br />
<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/FOSDEM%202014%20Flyer.odt french and english versions<br />
* http://www.mageia.org/about/media/ mainly logo & CD/DVD covers, available in SVG<br />
* FOSDEM 2015 flyer: [[File:Mageia_flyer_2015_EN.odt]]<br />
* http://stormi.lautre.net/fichiers/jdll/2015/ french and english version showed at JDLL 2015</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Events_Box&diff=32715Events Box2016-06-16T13:57:52Z<p>Dtux: </p>
<hr />
<div>[[Category:Contributors]]<br />
[[Category:Marcom]]<br />
[[Category:Atelier]]<br />
[[Category:Events]]<br />
<br />
We need a first, small, limited events box to help keep together tools for each event.<br />
<br />
See the [[Events HowTo]] as well.<br />
<br />
== How does the box look like? ==<br />
TODO, picture<br />
<br />
== What's in the box? ==<br />
Box contents can be donated, directly, or through http://www.mageia.org/donate/.<br />
<br />
* contents checklist including inventory (for CDs/stickers/goodies) and state of tablecloths (washed/not washed).<br />
* cash box<br />
* a pen and a notebook<br />
<br />
Showcase:<br />
* big posters with Mageia logo - we have some<br />
* kakemono - we have one (and can get extra banners if wanted); posters fit in kakemono case<br />
<br />
Distribute:<br />
* CD, DVD - we have some discs left for Mageia 1, we need a solution for Mageia 2<br />
<br />
Goodies:<br />
* tshirts - we have some left from FOSDEM 2011 - we need an inventory and new series<br />
* stationery (stickers, contact list, flyers, contact cards/business cards, blank pre-printed CDs (to burn on the stand), CD sleeves) - we have some left - we need new ones - for booth and to distribute to attendees when one speaks at a conference<br />
<br />
== Where is the box? ==<br />
<br />
=== Current location of the box ===<br />
<br />
=== Current goodies around Europe ===<br />
{|+class="wikitable"<br />
|-<br />
|Country | city | T-shirts | stickers | flyers | USB Keys | pens | Tablecloth | kakemono | others |<br />
|-<br />
|France | Lyon | 4 x S - 5 x M - 5 x L-ladies - 10 x XL - 2 x XXL | 1 USB key | 8 Pens | 1 tablecloth | 1 kakemono |<br />
|-<br />
|}<br />
<br />
=== Next, planned locations ===<br />
<br />
=== Base locations ===<br />
Ideally, two locations, in France or in its direct periphery. Events that we will attend with this box are among: FOSDEM, LinuxTag, Solutions Linux, RMLL, OWF, JDLL, ORR, what others in Europe?<br />
<br />
=== Transportation costs ===<br />
Use these max limits to estimate roughly the cost:<br />
* weight: 10 kg<br />
* dimensions: 55 x 35 x 25 cm<br />
* declared value: 3000 €<br />
<br />
* cities: Paris, Marseille, Bordeaux, Nantes, Berlin, Bruxelles, London, Barcelona, Madrid, Rome, Lisbon<br />
Indicative average max prices (UPS - https://wwwapps.ups.com/ctc/request):<br />
* Paris -> {Brussel,Berlin}, ~300 €<br />
* Nantes -> Paris, ~100 € (about the same intra France?)<br />
<br />
* 10kg 120 x 60 x 60 cm 6,90€ (intra Germany), 22,00€ Germany->France (http://www.dhl.de/en.html)<br />
<br />
The actual cost may be less (the box may be lighter, smaller) or more (change in transportation fees).<br />
<br />
=== Asking for the box ===<br />
Wanted home candidates (multiple is better):<br />
* Nantes, FR: rda<br />
* Paris, FR: baud (Versailles, for SL, RMLL, PremierSamedi])<br />
* Berlin, DE: ?<br />
* Brussel, BE: ?<br />
* other?<br />
<br />
== Grow the box! ==<br />
<br />
Here are other stuff good to have in the box.<br />
<br />
The whole package (box + contents) must not exceed 10 kg and must keep 55 x 35 x 25 cm (easier for someone to travel with it).<br />
<br />
* BOX itself (wish, no model/size decided) a box to fit all this, that can be handled by a single person, that has wheels and handles. Suggest medium (20kg, international roll-on size or a little larger) suitcase with at least one zipper poclet on the outside (for padlock &c during shipping).<br />
<br />
* (wish) event schedule and [[Events HowTo|howto]] (in this very wiki at least; a print copy is good too)<br />
* (wish) two large pieces of cloth: one white, one black. (see tablecloths in showcase. Black may be redundant...)<br />
* (wish) cables? RJ45, video, USB, multi powerplugs, type <br />
* (wish) small medikit, scissors, thread<br />
* (wish) velcro dots (both hook and fuzz), with adhesive back, two types (standard and strong)<br />
* (wish) good-quality packaging tape in tape-gun<br />
* (wish) good brass padlock to lock suitcase when travelling with someone<br />
* (wish) cycle lock (click-together type with coated cable or chain) to lock Events Box to racks on trains - prevent theft of Box<br />
<br />
Showcase stuff:<br />
* (must have) - 2 tablecloths for exhibition tables, white with mageia logo placed to be at front of table, sized for 2 180cm long x 90cm wide x 80cm high tables (so, (2*180)+(2*80) long and 90+(2*80) wide.) Mageia logo can be on vinyl like banner and poster, and be fixed with double-sided tape or velcro, or can be printed onto the cloth.<br />
* (wish) perspex or portable/foldable metal display stands for leaflets/brochures/cds. Metal will stand on floor beside tables, perspex on table (so metal might work better).<br />
* (wish, no model decided, price tag max 300 €) dedicated projector<br />
* (wish, no model decided, price tag max 200 € each) 2 dedicated laptops or small boxes (cubox, other?): one for projection, the other one for direct manipulation<br />
** one potential candidate, white ASRock Ion330 + keyboard + mouse and cables (second hand, ~150 € worth, rda)<br />
* for projection:<br />
** (wish) simple slides calling for contributors, with specific & easy tasks,<br />
** (wish) project presentation, demonstrating the product,<br />
** (wish) give immediate contact hooks (Web, IRC, Twitter, other events)<br />
** (wish) display a small twitter wall of the current event<br />
<br />
Distribute:<br />
* (wish) a system to dump a Mageia system image to USB key or portable HD<br />
* (wish) mageia-logo USB sticks<br />
* (idea) one of the computer is used either as a Wi-Fi access point (advertised as "Get Mageia") or as a station in the local network, and advertises shared directories (FTP, Samba) containing Mageia ISOs<br />
<br />
<br />
* interactive, live access to forums, IRC channels and other info source about the project<br />
** Maybe a projector connected to a laptop? Maybe more than one? Forums, wiki, an event-central IRC channel? I think a projector displaying a live feed of #mageia-social would be a good place to start. --[[User:Max|max]] 19:56, 16 July 2012 (UTC)<br />
* computers/projectors showcasing the OS: laptops, tablets, projectors<br />
<br />
<br />
== Other projects events boxes ==<br />
* http://live.gnome.org/GnomeEventsBox<br />
* other ?<br />
<br />
== Other ideas of goodies ==<br />
* USB key <br />
** 4 GB should be enough, ~5 € and could be proposed at 10 € with Mageia logo<br />
** http://www.memoriasusb.com<br />
* USB card<br />
** was here at Fosdem 2013, not seen since :/ 2 GB card with Mageia logo<br />
* stickers<br />
** see https://wiki.mageia.org/en/Commercial_vendors#Goodies_vendors<br />
<br />
== Documents to promote Mageia ==<br />
<br />
<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf - [ [http://download.tuxfamily.org/cauldron/mageia/doc/RMLL_2015_Flyer_enfr.pdf source as Odt] ]<br />
* http://download.tuxfamily.org/cauldron/mageia/doc/FOSDEM%202014%20Flyer.odt french and english versions<br />
* http://www.mageia.org/about/media/ mainly logo & CD/DVD covers, available in SVG<br />
* FOSDEM 2015 flyer: [[File:Mageia_flyer_2015_EN.odt]]<br />
* http://stormi.lautre.net/fichiers/jdll/2015/ french and english version showed at JDLL 2015</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Construire_des_paquetages_RPM-fr&diff=29795Construire des paquetages RPM-fr2015-11-08T13:07:10Z<p>Dtux: Changed Mandriva by Mageia</p>
<hr />
<div>Cette page est aussi disponible en :<br />
* [https://wiki.mageia.org/en/Packagers_RPM_tutorial Anglais]<br />
<br />
<br />
<div style="text-align:justify"><br />
{{introduction-fr|Ce tutoriel est destiné à aider ceux qui voudraient produire des paquetages logiciels bien intégrés à la distribution Mageia GNU/Linux. Il insiste sur les (légères) différences entre ces paquetages et ceux destinés à d'autres distributions utilisant les RPM. Ce document devrait être utile aux développeurs Mageia mais aussi à tous les utilisateurs intéressés par la création de paquetages.<br />
<br />
La distribution Mageia Linux est éditée et distribuée par la communauté bénévole de Mageia.org, avec l'aide de nombreux contributeurs, testeurs et traducteurs.}}<br />
<br />
<br />
= Avant-propos =<br />
<br />
Dans ce document, nous supposons que le lecteur est familiarisé avec un système GNU/linux. Il connait les commandes de base, la structure des répertoires et a déjà utilisé la commande {{cmd|rpm}}, ne serait-ce que pour installer des paquetages.<br />
<br />
Ce document est construit comme une recette pas à pas pour obtenir un paquetage .rpm qui s'intègre bien à la distribution Mageia, que ce soit à partir d'un {{prog|rpm}} source ou à partir d'une archive {{cmd|tar}}.<br />
<br />
En bref, RPM désigne trois choses :<br />
* un programme pour créer ou installer des paquetages ;<br />
* un format utilisé dans des paquetages (source ou binaire) créés par le programme {{prog|Rpm}} ;<br />
* un fichier appelé paquetage qui contient les sources ou le binaire ainsi qu'une en-tête d'information sur la méthode d'installation ou de désinstallation du programme.<br />
<br />
Du point de vue de l'utilisateur, le programme {{prog|rpm}} est un remarquable programme de gestion de paquetages. Il pilote en fait toutes les actions sur un paquetage RPM. Il peut ainsi, entre autres :<br />
* installer ou mettre à jour un paquetage en vérifiant ses dépendances ;<br />
* exécuter des actions pendant l'installation pour rendre le programme installé prêt à l'emploi ;<br />
* restaurer des fichiers d'un paquetage effacés accidentellement ;<br />
* dire si un paquetage est déjà installé ;<br />
* trouver de quel paquetage provient un fichier particulier ;<br />
* vérifier l'installation courante et le respect des dépendances pour tous les paquetages installés ;<br />
* ...<br />
<br />
Du point de vue du programmeur, le programme {{prog|rpm}} est un empaqueteur qui encapsule dans un seul fichier .rpm toutes les informations nécessaires à l'installation d'un programme sur une plate-forme donnée.<br />
<br />
Il est important de distinguer dès le début les paquetages sources ( {{file|.src.rpm}} ) et les paquetages binaires ({{file|.<archtype>.rpm}}).<br />
<br />
Les premiers contiennent l'arborescence entière des sources du programme, plus tout ce que le réalisateur du paquetage a ajouté pour qu'il puisse être configuré, compilé et finalement installé. Cela consiste généralement en un fichier ayant l'extension {{file|.spec}} (le fichier utilisé pour dire à {{prog|rpm}} les opérations à effectuer pour créer le paquetage binaire) ainsi que des correctifs, si nécessaire. <br />
<br />
Les seconds contiennent le binaire compilé, ainsi que tous les fichiers (documentation, fichiers de configuration, icones,...) qui seront installés sur le système cible. Ils contiennent aussi la procédure qui installe les fichiers aux emplacements corrects, ainsi que les actions qui rendent le programme opérationnel.<br />
<br />
<br />
== Installer le logiciel ==<br />
<br />
=== Les bases ===<br />
<br />
Bien que RPM ait été conçu à l'origine pour la distribution [http://www.redhat.com Red Hat Linux], il a été adopté par d'autres distributions : [http://www.mandriva.com Mandriva Linux], [http://www.suse.com/index_us.html Suse], etc. {{prog|rpm}} est déja installé sur ces systèmes.<br />
<br />
Les {{file|rpm}} binaires que vous construirez pour Mageia ne fonctionnent pas forcément sur toutes les distributions, ni même sur toutes les versions de Mageia, bien que des efforts soient fait pour rester compatible avec Red Hat.<br />
<br />
<br />
=== Construire des paquetages pour Mageia ===<br />
<br />
Construire des paquetages pour Cauldron (la version de développement de Mageia Linux) est toujours sujet à de petits patchs et améliorations apportés au programme RPM en cours. Récupérez sur un miroir Cauldron:<br />
* Le paquetage {{pkg|rpm}} qui est notre version patchée de celui de Red Hat.<br />
* Le paquetage {{pkg|rpm-build}} qui contient des scripts destinés à construire des paquetages.<br />
* Le paquetage {{pkg|spec-helper}}, qui est un outil qui minimise les fichiers specs en faisant automatiquement des opérations telles que diminuer la taille des binaires et compresser les pages du manuel {{file|man}}.<br />
* Le paquetage {{pkg|libtool}}, utilisé par certains scripts de configuration pour construire des bibliothèques de fonctions partagées.<br />
* Le paquetage {{pkg|rpmlint}} qui est utilisé pour vérifier la validité du paquetage {{file|src.rpm}} généré.<br />
<br />
== Tâches préliminaires ==<br />
<br />
=== Installer les paquetages requis ===<br />
<br />
Pour pouvoir construire des RPM, vous devez avoir installé au préalable le paquetage {{pkg|rpm-build}}. Pour savoir comment installer des paquetages, veuillez vous référer à la page [[https://wiki.mageia.org/en/Gestion_des_logiciels-fr#Installer_et_supprimer_des_logiciels | Gestion des logiciels]].<br />
<br />
<br />
=== Créer les répertoires requis ===<br />
<br />
Pour construire des paquetages, RPM a besoin d'une arborescence spéciale dans le dossier personnel de l'utilisateur. Cette arborescence peut être créée en tapant dans une console :<br />
{{console-fr|mkdir -p ~/rpm/{BUILD,RPMS/{i586,noarch,x86_64},SOURCES,SRPMS,SPECS,tmp} }}<br />
<br />
{{attention-fr|'''Il est dangereux de construire des RPM en tant que root''', puisque les fichiers binaires sont installés sur le système avant d'être empaquetés. Il faut donc toujours construire ses RPM en tant qu'utilisateur normal afin de ne jamais polluer accidentellement son système.}}<br />
<br />
Vérifiez bien que l'arborescence est de la forme:<br />
* {{file|~/rpm/BUILD}} : dossier où se fait la compilation des sources.<br />
* {{file|~/rpm/RPMS}} : contient les répertoires, un par architecture, qui contiendront les paquetages binaires générés.<br />
* {{file|~/rpm/RPMS/i586}} : le répertoire où seront stockés les paquetages binaires créés pour les processeurs i586.<br />
* {{file|~/rpm/RPMS/x86_64}} : le répertoire où seront stockés les paquetages binaires créés pour les processeurs X86_64.<br />
* {{file|~/rpm/RPMS/noarch}} : le répertoire où seront stockés les paquetages binaires ''noarch'' (c'est-à-dire indépendants de l'architecture du processeur). générés. <b>Ndla</b> : c'est souvent le cas des applications écrites dans des langages interprétés (php,perl,python,ruby...).<br />
* {{file|~/rpm/SOURCES}} : contient les fichiers sources (par exemple monpaquetage.tar.bz2 ).<br />
* {{file|~/rpm/SPECS}}: contient les fameux fichiers {{file|spec}} que nous devons écrire. <br />
* {{file|~/rpm/SRPMS}} : RPM sources après la construction.<br />
* {{file|~/rpm/tmp}} : dossier temporaire de travail pour RPM.<br />
<br />
{{note|Les dossiers d'architecture sous {{file|~/rpm/RPMS}} sont indispensables. S'ils manquent, un message d'erreur s'affichera.}}<br />
<br />
<br />
=== Créer le fichier .rpmmacros ===<br />
<br />
Pour pouvoir construire des paquetages pour Mageia, vous devrez au préalable créer le fichier de configuration {{file|.rpmmacros}} dans votre [[répertoire personnel]] et y copier/coller le contenu ci-dessous<br />
<pre><br />
%_topdir %(echo $HOME)/rpm<br />
%_tmppath %(echo $HOME)/rpm/tmp<br />
<br />
# If you want your packages to be GPG signed automatically, add these three lines<br />
# replacing 'Mageialinux' with your GPG name. You may also use rpm --resign<br />
# to sign the packages later.<br />
%_signature gpg<br />
%_gpg_name Mageialinux<br />
%_gpg_path ~/.gnupg<br />
<br />
# Add your name and e-mail into the %packager field below. You may also want to<br />
# also replace vendor with yourself.<br />
%packager John Doe <foo@mail.invalid><br />
%distribution Mageia Linux<br />
%distributor Mageia.org<br />
<br />
# If you want your packages to have your own distsuffix instead of mdv, add it<br />
# here like this<br />
#%distsuffix foo<br />
</pre><br />
<br />
Attention, ne pas définir ''%optflags'', puisqu'elle est déjà définie globalement dans le fichier {{file|/usr/lib/rpm/rpmrc}}.<br />
<br />
Le programme {{prog|rpm}} est maintenant correctement configuré pour construire des paquetages. <br />
<br />
{{note|Tout ce qui précède peut se faire d'un seul coup en lançant le script ''repsetup.sh.}}<br />
<br />
<br />
== Construire un RPM ==<br />
<br />
=== A partir d'un RPM source existant ===<br />
<br />
C'est généralement le cas pour les paquetages qui font partie intégrante de la distribution.<br />
<br />
Les derniers fichiers RPM de Cauldron sont disponibles sur n'importe quel miroir de la liste disponible sur [[http://mageia.madb.org/default/home/release/cauldron/application/0/arch/x86_64 | ici]]. Dans cette hiérarchie, on trouve les répertoires :<br />
<br />
* {{file|SRPMS}} : pour les RPM sources,<br />
* {{file|media/main}} : pour les RPM binaires.<br />
* {{file|media/contrib}} : pour les RPM binaires de {{file|contrib}}.<br />
<br />
Une fois téléchargé le RPM source à modifier pour Mageia dans le dossier {{file|~/rpm/SRPMS}}, exécutez simplement {{cmd|rpm -ivh <lepaquet>.src.rpm}} et ceci installera toutes les sources dans le répertoire {{file|~rpm/SOURCES}}. On peut aussi configurer {{prog|urpmi}} pour télécharger les sources (voir [[https://wiki.mageia.org/en/URPMI-fr#urpmi.addmedia|Installation de sources d'un paquet]])<br />
<br />
Par exemple :<br />
<br />
{{console-fr|rpm -i SRPMS/ktron-1.0.1-2mdk.src.rpm}}<br />
Puis ensuite pour vérifier que la source le fichier spec ont bien été installés:<br />
{{console-fr|ls -R ~/rpm <br />
BUILD:<br />
<br />
RPMS:<br />
noarch/ i386/ i586/ i686/<br />
<br />
SPECS:<br />
ktron.spec<br />
<br />
SOURCES:<br />
ktron-1.0.1.tar.bz2<br />
<br />
SRPMS:<br />
<br />
tmp}}<br />
<br />
On voit que {{prog|rpm}} a installé dans notre arborescence {{file|~/rpm}} le fichier source {{file|ktron-1.0.1.tar.bz2}} et le fichier {{file|spec}}. Même avant de construire une nouvelle version d'un paquetage, il peut être utile de faire un ''build'' sur le paquetage courant pour comprendre comment il est compilé et s'il compile. La commande magique pour cela est {{cmd|rpmbuild}} avec l'option {{cmd|-ba}}:<br />
<br />
{{console-fr|cd ~/rpm/SPECS}}<br />
{{console-fr|rpmbuild -ba ktron.spec}}<br />
Si la construction se termine sans erreur (cela peut durer des heures pour des paquetages comme les kernels), on retrouve le RPM binaire et le RPM src respectivement dans les répertoires {{file|~/rpm/RPMS/i586}} et {{file|~/rpm/SRPMS/}}. Le fichier log de l'opération de construction, qui peut être très long, peut être enregistré pour le relire plus tard.<br />
{{console-fr|ls -l ~/rpm/RPMS/i586/ktron-1.0.1-2mdk.i586.rpm}}<br />
{{console-fr|ls -l ~/rpm/SRPMS/ktron-1.0.1-2mdk.src.rpm}}<br />
<br />
Pour installer le RPM binaire, il faut être sous [[root|root(en)]], mais c'est inutile pour construire un {{file|.rpm}} ou décompresser un {{file|.src.rpm}}.<br />
<br />
On retrouve dans les sous-répertoires {{file|~/rpm/BUILD}} les sources patchées (si un ou plusieurs patchs ont été fournis dans {{file|~/rpm/SOURCES}}), les binaires, les librairies compilées, les pages de man etc. <br />
Le fichier spec décrit les fichiers source et les patchs à appliquer avant construction, ainsi que la manière de construire le paquetage et de l'installer.<br />
<br />
Il ne nous reste plus (dans cet exemple pour améliorer ktron) qu'à modifier le fichier spec et à reconstruire le paquetage.<br />
<br />
Il est important de noter que chaque paquetage intégré dans Mageia est stocké sur un système SVN, visible via [https://svnweb.mageia.org/ l'interface web]. Ainsi, les états successifs du paquetage sont enregistrés, de sorte que le développeur peut consulter les archives pour vérifier des modifications précédentes et éventuellement revenir à une version précédente du logiciel.<br />
<br />
Chaque fichier spec est donc disponible dans un sous-dossier portant le nom du logiciel dans le dossier {{file|packages/cauldron}}.<br />
<br />
==== Vérifications préliminaires ====<br />
<br />
* Licence: Malgré la prédominance de la licence GPL, il existe d'autres licences libres (comme BSD, MIT, etc) ou non libres. Vérifiez attentivement la licence du logiciel pour déterminer si ce programme peut être incorporé ou non à la distribution. En effet, nous n'acceptons pas de logiciels non libres, sauf dans la section non-free. Nous ne pouvons pas non plus accepter de logiciels dont la licence ne nous permet pas de les distribuer librement. Attention à ces programmes. Vérifiez donc au préalable si un logiciel est acceptable d'après sa [[https://www.mageia.org/fr/about/license/ | licence]].<br />
<br />
* Compression de l'archive: Pour simplifier la maintenance, il est recommandé d'utiliser la méthode de compression utilisée par l'auteur ou le développeur, sans modifications. Si les sources sont fournies dans plusieurs formats de compression, on choisit généralement le .tar.bz2. Évitez de compresser les fichiers au format texte (comme les patchs produits par {{prog|diff}} et autres, les fichiers de configuration, les scripts, etc.). Leur compression économiserait très peu d'espace tout en rendant plus difficile la visualisation des changements, au niveau des diffs produits par Subversion. <br />
<br />
{{note-fr|Pour les <b>paquetages logiciels sensibles</b>, nous recommandons de <b>conserver le format originel de l'archive</b> afin de ne pas altérer le checksum/signature. Ainsi, lorsque quelqu'un souhaitera vérifier la signature des sources via les programmes md5sum, sha1sum ou gpg, il pourra obtenir un résultat équivalent à la valeur indiquée sur le site de téléchargement. ''OpenSSH'' est un exemple d'une telle exception.}}<br />
<br />
<br />
=== Anatomie du fichier .spec ===<br />
<br />
C'est la partie la plus importante de ce document. Le fichier {{file|spec}} contient toutes les informations dont RPM a besoin pour : <br />
<br />
# compiler le programme et construire les RPM binaires et sources,<br />
# installer ou désinstaller le programme sur la machine de l'utilisateur final. <br />
<br />
Le débutant peut être dérouté par le fait que ces deux types d'information sont regroupés dans un seul fichier. Cela est dû à l'arborescence de l'archive tar source, qui contient déjà cette information. Comme la procédure d'installation est extraite au cours du processus d'installation, généralement lancé par un {{cmd|make install}} dans l'arborescence source, les deux parties sont intimement liées.<br />
<br />
En bref, le fichier spec décrit une compilation et une installation simulée, dit à RPM quels fichiers résultants de cette installation doivent être mis dans le paquetage et finalement comment installer ces fichiers dans le système de l'utilisateur. Les commandes sont exécutées en utilisant le shell {{file|/bin/sh}}, de telle sorte que des commandes comme {{cmd|[ -f configure.in ] && autoconf}} sont valides.<br />
<br />
Nous n'allons pas exposer ici en détail toutes les possibilités d'un fichier spec. Le livre [http://www.rpm.org/max-rpm/ Maximum RPM] (cf. section 7) l'explique en profondeur. Nous allons nous contenter de passer en revue les options utilisées dans un exemple de fichier spec standard Mageia.<br />
<br />
Plus vous construirez de RPM, plus vous découvrirez d'options dont nous n'avons pas parlé. RPM est très extensible, nous laissons donc au lecteur le soin de découvrir toutes ces options à titre d'exercice. Il est toujours bon d'ouvrir des fichiers specs et d'y jeter un coup d'œil pour comprendre leur fonctionnement. <br />
<br />
Le lecteur peut également consulter une [https://svnweb.mageia.org/packages/cauldron/ liste de specs et de correctifs].<br />
<br />
<pre><br />
%define name gif2png <br />
%define version 2.0.1 <br />
%define release %mkrel 1 <br />
<br />
Name: %{name} <br />
Summary: Tools for converting websites from using GIFs to using PNGs <br />
Version: %{version} <br />
Release: %{release} <br />
Source0: http://www.tuxedo.org/~esr/gif2png/%{name}-%{version}.tar.bz2 <br />
Source1: %{name}-%{version}-mdk-addon.tar.bz2 <br />
Patch0: gif2png-2.0.1-bugfix.patch <br />
URL: http://www.tuxedo.org/~esr/gif2png/ <br />
<br />
Group: Applications/Multimedia <br />
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot <br />
License: MIT-like <br />
Requires: python <br />
<br />
%description<br />
Tools for converting GIFs to PNGs. The program gif2png converts GIF files<br />
to PNG files. The Python script web2png converts an entire web tree, also<br />
patching HTML pages to keep IMG SRC references correct.<br />
<br />
%prep <br />
%setup -q -a 1 <br />
%patch -p1 <br />
<br />
%build <br />
%configure2_5x <br />
%make<br />
<br />
%install<br />
rm -rf $RPM_BUILD_ROOT<br />
%makeinstall<br />
<br />
%clean <br />
rm -rf $RPM_BUILD_ROOT <br />
<br />
%files <br />
%defattr(-,root,root) <br />
%doc README NEWS COPYING AUTHORS <br />
%{_mandir}/man1/gif2png.1*<br />
%{_mandir}/man1/web2png.1*<br />
%{_bindir}/gif2png <br />
%{_bindir}/web2png <br />
<br />
%changelog <br />
* Mon Nov 02 1999 Camille Begnis <camille@mandrakesoft.com> 2.0.1-1mdk<br />
- Upgraded to 2.0.1 <br />
<br />
* Mon Oct 25 1999 Camille Begnis <camille@mandrakesoft.com> 2.0.0-1mdk<br />
- Specfile adaptations for Mandrake<br />
- add python requirement<br />
- gz to bz2 compression<br />
</pre><br />
<br />
Analysons en détail chaque ligne de ce fichier :<br />
<br />
Attention, un % au début d'une ligne peut signifier soit :<br />
* le début d'une section (prep, build, install, clean)<br />
* un script de macro du shell (setup, patch)<br />
* une instruction utilisée par une section spéciale (defattr, doc, ...) <br />
<br />
Vous pouvez voir à quoi correspond une macro à l'aide de l'instruction rpm --eval <br />
<br />
<pre><br />
rpm --eval "%mkrel 1"<br />
1mdv2010.0<br />
</pre><br />
<br />
<br />
==== Section En-tête ====<br />
<br />
<pre><br />
%define name gif2png<br />
%define version 2.0.1<br />
%define release %mkrel 1<br />
</pre><br />
Ces 3 lignes définissent des constantes utilisables par les sections suivantes du spec, constantes qui seront alors nommées {{macro|%{name} }}, {{macro|%{version} }} et {{macro|%{release} }}. {{macro|%mkrel}} est une macro Mageia qui doit être utilisée pour ajouter le suffixe « mga » et la version de la distribution après le numéro de révision du paquet. <br />
<br />
Nous pouvons maintenant remplir certains champs d'information pour rpm :<br />
<br />
<pre><br />
Name: %{name}<br />
</pre><br />
<br />
C'est le nom du paquetage tel qu'il sera identifié sur la machine de l'utilisateur et dans sa base de données de paquetages une fois installé. <br />
<br />
Noter que "{{macro|%{name} }}" se réfère au « define » précédent.<br />
<br />
<pre><br />
Version: %{version}<br />
Release: %{release}<br />
</pre><br />
<br />
Il est maintenant temps d'expliquer comment est formé le nom d'un paquet. Il est important de toujours respecter ce standard pour que votre travail soit compréhensible par les autres. <br />
<br />
Il existe beaucoup d'autres champs que vous pourriez désirer connaître, mais qui ne sont pas dans notre fichier spec exemple. Vous pourriez en rencontrer certains. Il est peu probable que vous arriviez à tous les retenir si vous commencez tout juste à construire des RPM. Mais après quelque temps, cette liste sera une bonne référence ! <br />
<br />
* Un paquetage binaire se nomme ainsi : {{file|name-version-release.arch.rpm}}<br />
* Un paquetage source se nomme ainsi : {{file|name-version-release.src.rpm}} (par ex: {{file|gif2png-2.0.1-1mdk.src.rpm}} pour notre exemple) <br />
<br />
Le « nom » est généralement celui de l'exécutable principal du paquetage, bien qu'on puisse choisir un autre nom pour des raisons valables.<br />
<br />
La « version » est le numéro de version des sources non patchées, numéro qu'on retrouve dans le nom de fichier de l'archive d'origine : {{file|name-version.tar.gz}}.<br />
<br />
La « release » est un nombre, incrémenté à chaque nouvelle construction du paquetage, suivi d'un suffixe indiquant pour quelle distribution a été construit le paquetage, par exemple "mga2014.1" pour "Mageia 2014.1". Notez que cette extension est obligatoire. Un paquetage peut être reconstruit pour de multiples raisons : l'ajout d'un nouveau correctif (patch) aux sources, une modification du fichier spec, l'ajout d'une icone, etc.<br />
<br />
<pre><br />
Summary: tools for converting websites from using GIFs to using PNGs<br />
</pre><br />
<br />
Le « Summary » est une courte description du paquetage, en une seule ligne. Il est important qu'on puisse comprendre ce que fait le paquet à partir de ce champ, et que cela ne dépasse pas une certaine limite ( 80 caractéres ).<br />
<br />
<pre><br />
Source0: http://www.tuxedo.org/~esr/gif2png/%{name}-%{version}.tar.bz2 <br />
</pre><br />
Cette ligne indique à rpm le fichier source à utiliser pour construire ce paquetage. A noter que le nom est précédé d'une URL complète (optionnelle) pointant vers le site où sont disponibles les sources d'origine ; rpm enlève l'URL, ne gardant que le nom de fichier et cherche ce fichier dans le dossier {{file|~/rpm/SOURCES}}. <br />
Bien que l'URL complète soit optionnelle, elle est recommandée pour que les utilisateurs sachent où trouver les nouvelles sources pour les mettre à jour et recompiler le programme. De plus, cela permet à des outils comme {{prog|mdvsys}} de reconstruire automatiquement de nouvelles versions (cf. [[:en:Development/Packaging/Tools/rpmbuildupdate]] pour plus d'infos).<br />
<br />
S'il y a plus d'un fichier source, on ajoute d'autres lignes sources, comme : Source1: ..., puis Source2: ..., etc.<br />
<br />
<pre><br />
Patch0: gif2png-2.0.1-bugfix.patch<br />
</pre><br />
<br />
Deux raisons à ce champ optionnel :<br />
<br />
# Vous avez corrigé un bogue dans les sources du programme. Vous avez donc généré un correctif, à appliquer aux sources du programme avant compilation.<br />
# Vous avez appris l'existence sur le net d'un correctif ou d'une amélioration pour votre version du programme et vous l'avez téléchargé.<br />
<br />
Il faut éviter d'ajouter trop d'améliorations extérieurs, car elles induisent du travail lors de la mise à jour du paquet. De même, si jamais vous avez intégré à un paquet un correctif que vous avez écrit, il est requis de l'envoyer au développeur du logiciel afin qu'il l'ajoute au code-source, et ainsi partager le travail avec la communauté du libre. <br />
<br />
{{note-fr|Les fichiers patchs doivent être placés dans le dossier même dossier que les sources (~/rpm/SOURCES). Comme pour les sources, il peut y avoir plusieurs correctifs. Ils seront alors désignés dans le fichier spec par des lignes Patch1: ..., puis Patch2: ..., etc.}}<br />
<br />
<pre><br />
URL: http://www.tuxedo.org/~esr/gif2png/<br />
</pre><br />
<br />
Cette ligne (optionnelle mais recommandée) pointe vers la page Web du programme.<br />
<br />
<pre><br />
Group: Multimedia<br />
</pre><br />
<br />
Ceci indique à {{prog|rpm}} à quel emplacement de l'arborescence générale des paquetages placer ce paquetage. Cette information est utilisée par les gestionnaires de paquets tels que {{prog|rpmdrake}}.<br />
<br />
La structure complète des groupes à utiliser, différente de celle de Red Hat, se trouve sur la page [[RPM_groups_policy RPM groups policy(en)]]. Il faut absolument s'y conformer pour que vos paquetages ne se mélangent pas aux autres dans l'arborescence système de l'installeur Mageia, ou dans les gestionnaires de paquets.<br />
<br />
<pre><br />
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-buildroot<br />
</pre><br />
<br />
Cette ligne très importante ne peut être omise. Elle demande à RPM, pour installer le programme, d'utiliser un dossier racine spécial (un pseudo "/") sur la machine où se fait la compilation. Deux raisons à cela :<br />
<br />
# Quand on construit un RPM, on n'a pas d'accès root à la machine et on ne peut donc pas installer le paquetage dans les dossiers systèmes habituels.<br />
# Si on fait l'installation dans l'arborescence système d'une machine, les fichiers du paquetage vont se mélanger avec les autres et, surtout, cela pourrait même être dangereux si le paquetage est déja installé. Beaucoup de gens utilisent {{file|/var/tmp}} ou {{file|/tmp}} comme « BuildRoot ». Ça ne pose pas nécessairement de problème si on est seul utilisateur de la machine, mais s'il y a plusieurs utilisateurs sur cette machine et qu'ils compilent le même paquetage au même moment, {{prog|rpm}} va planter. C'est pourquoi il est préférable de définir {{macro|%{_tmppath} }} vers un sous-dossier de votre répertoire personnel :<br />
<br />
<pre><br />
License: MIT-like<br />
</pre><br />
Ce champ (qui remplace « Copyright ») définit la licence choisie par le propriétaire du Copyright (ou droits d'auteur) qui s'applique au programme empaqueté. C'est le plus souvent la license GPL. Voir cette[[Licensing_policy page]] et [[Licensing_policy#standard_license_names celle-ci]] pour une liste des licences autorisées.<br />
<br />
<pre><br />
Requires: python<br />
</pre><br />
<br />
Cette ligne a été ajoutée parce qu'un des programmes du paquetage est un script python. Il a donc besoin de l'interpréteur {{prog|python}} pour fonctionner. On peut optionnellement demander une numéro de version minimal en ajoutant un signe supérieur (ou égal), par exemple : Requires: python >= 1.5.1.<br />
En pratique, les nouvelles versions de rpm arrive à rajouter la dépendance automatiquement.<br />
<br />
<pre><br />
%description<br />
Tools for converting GIFs to PNGs. The program gif2png converts GIF files<br />
to PNG files. The Python script web2png converts an entire web tree, also<br />
patching HTML pages to keep IMG SRC references correct.<br />
</pre><br />
<br />
Ce champ est spécial parmi ceux de l'en-tête du fichier spec, car c'est un texte entier pouvant faire plusieurs lignes ou paragraphes si nécessaire. C'est une description complète du programme qui va être installé, pour aider l'utilisateur à décider s'il veut installer ou non ce paquetage.<br />
<br />
Vous vous demandez peut-être : "Et les traductions ?" En fait, pour améliorer la lisibilité des fichiers spec, les traductions des champs « Summary » et « description » sont stockés dans un fichier spécial nommé {{file|<package>.po}}.<br />
<br />
Ces fichiers sont stockés dans le module [http://cvs.mandriva.com/cgi-bin/viewvc.cgi/poSPECS poSPECS] du cvs de cooker ['''FIXME''': est-ce encore le cas ? Les fichiers n'ont pas été modifiés en 5 ans...]. Quand un nouveau paquetage est créé, le fichier po de base est automatiquement créé dans ce module pour traduction ultérieure.<br />
<br />
Cette méthode suppose que tous les textes d'un fichier .spec sont écrits en anglais. A l'exception toutefois des paquetages dédiés à un langage précis (ispell-de par exemple). Il est dans ce cas recommandé d'écrire le texte dans les deux 2 langues: anglais et le langage spécifique. On utilise alors les champs spéciaux : Summary(de): ... et {{macro|%description -l de}}.<br />
<br />
<br />
==== Section Prep ====<br />
<br />
<pre><br />
%prep <br />
%setup -q -a 1<br />
%patch0 -p1<br />
</pre><br />
<br />
Cette section contient le script exécuté en premier par rpm. Son rôle est de :<br />
<br />
* créer le dossier racine pour la construction (dans BUILD),<br />
* décompresser les sources originales dans le dossier {{file|~/rpm/BUILD}},<br />
* appliquer aux sources les correctifs éventuels.<br />
<br />
Elle peut être suivi de toute commande voulue par le créateur du paquetage pour que les sources soient prêts pour la compilation.<br />
<br />
<pre><br />
%setup -q -a 1 <br />
</pre><br />
Ceci est un script pré-défini qui :<br />
<br />
* exécute une commande {{cmd|cd}} dans l'arbre de compilation, <br />
* extrait les sources (silencieusement, -q),<br />
* change le propriétaire et les permissions des fichiers sources.<br />
<br />
Par défaut, il n'extrait que le premier source. Il faut utiliser des paramètres pour des sources supplémentaires: dans notre exemple, -a 1 dit que nous voulons aussi extraire le source numéro 1.<br />
<br />
La macro {{macro|%setup}} a d'autres options intéressantes:<br />
<br />
* -c name: l'option « -c » demande de créer d'abord le répertoire racine "nom", puis de s'y déplacer par cd et de décompresser Source0. C'est utile pour certains paquetages qui ont été "tar.bz-ippés" sans répertoire parent.<br />
* -D : ne pas effacer le répertoire avant décompression. Cela ne sert que s'il y a plus d'une macro %setup. A utiliser seulement dans les %setup qui suivent le premier (mais jamais dans le premier). <br />
* -T : cette option remplace l'action par défaut de décompresser la Source (et nécessite alors un -b 0 ou -a 0 pour décompresser le fichier source principal). Nécessaire quand il y a des sources secondaires.<br />
* -n <name> : à utiliser si le nom du rpm est différent de celui en lequel se décompresse le Source. Par exemple, si le rpm se nomme program-version-revision et que le Source se décompresse en program-version-date, le processus de build du rpm ne pourra pas entrer (cd) dans le répertoire program-version, il faut alors utiliser « -n program-version-date », pour que rpm sache dans quel nouveau répertoire il doit continuer.<br />
<br />
<pre><br />
%patch0 -p1<br />
</pre><br />
<br />
Cette macro applique le patch aux sources ; son paramètre "-p<numero>" est passé au programme {{prog|patch}}. Supposons qu'il y ait un autre patch déclaré dans la section en-tête par de Patch1: ... ; il faut ajouter une autre ligne : {{macro|%patch1 -p1}}. Il peut être utile d'ajouter l'option {{cmd|-b .your_suffix}} pour signaler aux autres ce que fait votre patch, ou qui l'a créé. Par exemple, si le patch est de David_david, on peut faire {{macro|%patch -p1 -b .David_david}}. Si c'est Papoteur qui l'a fait, le patch peut être {{macro|%patch -p1 -b .Papoteur}}<br />
<br />
<br />
==== Section Build ====<br />
<br />
<pre><br />
%build <br />
</pre><br />
<br />
Cette section contient le script qui compile réellement le logiciel. Il se compose de commandes lancées sur l'arborescence des sources décompressés.<br />
<br />
<pre><br />
%configure2_5x<br />
</pre><br />
<br />
C'est la ligne, qui configure les sources utilisant autoconf. {{macro|%configure2_5x}} lance un {{cmd|./configure}} avec de nombreuses options telles que <pre>export CFLAGS="$RPM_OPT_FLAGS"</pre> avant le configure, et des options telles que <pre>i586-mageia-linux-gnu --prefix=/usr --datadir=/usr/share</pre> etc.<br />
<br />
Ces arguments ne sont pas toujours gérés par le script de configuration. Dans ce cas, il faut en découvrir la raison puis lancer {{cmd|./configure}} avec les paramètres appropriés. Si cela est géré, on passe le nom de la plateforme cible à l'appel de configure par {{macro|%{''target''platform} }}. Bien sûr, il faut éviter de spécifier l'architecture dans un fichier spec ; sur un ix86, ce paramètre se développera en i586-mageia-linux-gnu, comme vu plus haut. <br />
<br />
{{note-fr|Le paquetage '''libtool''' est nécessaire pour utiliser la macro '''%configure2_5x''' avec des paquetages qui construisent des bibliothèques partagées.}}<br />
<br />
Quand on construit et qu'on teste un paquetage, il faut vérifier que l'hôte cible est bien un i586 ; en particulier, quand on compile sur un processeur d'un type supérieur, par défaut, le script trouve le processeur architecture et optimise pour lui. La macro {{macro|%configure}} est là pour passer outre ce comportement si besoin est.<br />
<br />
<pre><br />
%make<br />
</pre><br />
<br />
C'est une simple macro qui, de base, exécute un make avec les paramètres multiprocesseurs appropriés {{cmd|-j<num>}}.<br />
<br />
Pour des sources qui utilisent {{prog|xmkmf}}, remplacer le make suivant par :<br />
<br />
<pre><br />
make CDEBUGFLAGS="$RPM_OPT_FLAGS" CXXDEBUGFLAGS="$RPM_OPT_FLAGS" <br />
</pre><br />
<br />
Pour les autres paquetages, dans la plupart des cas (mais pas tous), un simple {{cmd|make}} suffit.<br />
<br />
==== Section Install ====<br />
<br />
<pre><br />
%install <br />
</pre><br />
<br />
Cette section contient le script qui installe vraiment le paquet dans le dossier d'installation simulée : {{file|$RPM_BUILD_ROOT}}.<br />
<br />
Ce sont les commandes qui rendent le logiciel fonctionnel sur le système de l'utilisateur.<br />
<br />
<pre><br />
rm -rf $RPM_BUILD_ROOT<br />
</pre><br />
<br />
C'est la première commande exécutée dans la section {{macro|%install}} qui nettoie le dossier d'une éventuelle précédente installation.<br />
<br />
<pre><br />
%makeinstall<br />
</pre><br />
<br />
Cette ligne installe le logiciel dans le dossier d'installation simulée pour des sources préparées par {{prog|autoconf}}. Cette macro se développe en "{{cmd|make install}}" avec diverses options pour que le logiciel soit installé dans le dossier d'installation simulée {{file|$RPM_BUILD_ROOT}}, par exemple <pre>prefix=$RPM_BUILD_ROOT%{_prefix} bindir=$RPM_BUILD_ROOT%{_bindir}</pre> etc. <br />
<br />
Il arrive que le script de configuration soit partiellement cassé auquel cas il faudra aller fouiner dans les fichiers {{file|Makefile}} pour deviner les paramètres optionnels à passer pour que le logiciel s'installe correctement. Une des situations les plus courantes est d'avoir à utiliser <pre>make DESTDIR=$RPM_BUILD_ROOT install</pre>.<br />
<br />
Pour économiser à la fois de l'espace disque et du temps de téléchargement, Mageia utilise xz. Cet aspect est cependant pris en charge en standard par la version de {{prog|rpm}} de Mageia.<br />
<br />
De même que pour les anciennes lignes $RPM_BUILD_ROOT%{_bindir}/* || : il faut les supprimer. <br />
<br />
Tout ceci prépare les fichiers à être empaquetés.<br />
<br />
<pre><br />
%clean<br />
</pre><br />
<br />
Cette section nettoie le dossier de construction {{file|$RPM_BUILD_ROOT}}.<br />
<br />
<pre><br />
rm -rf $RPM_BUILD_ROOT<br />
</pre><br />
<br />
C'est ici que se fait le travail.<br />
<br />
<br />
==== Files section ====<br />
<br />
<pre><br />
%files <br />
</pre><br />
<br />
Cette section est une liste de fichiers à prendre dans le dossier d'installation simulée pour les incorporer au paquetage. Voir le manuel pour d'autres options absentes de cet exemple simple.<br />
<br />
La liste des fichiers doit être écrite à la main dans le fichier spec. On peut la construire en listant tous les fichiers créés par rpm dans le répertoire de construction. Pour cela, on exécute un {{cmd|rpm -bi mypackage.spec}} pour arrêter le processus de construction juste après l'installation simulée. On examine alors le contenu du dossier d'installation simulée, {{file|~/rpm/tmp/gif2png-buildroot}} dans notre cas, pour voir quels fichiers on veut mettre dans le paquetage (le plus souvent, on les met tous). <br />
<br />
{{Note-fr| sur la structure des répertoires : les fichiers installés par votre paquetage doivent suivre les recommandations FHS disponibles sur [http://www.pathname.com/fhs].}}<br />
<br />
<pre><br />
%defattr(-,root,root)<br />
</pre><br />
<br />
Ce champ définit les attributs à appliquer à chaque fichier qui sera copié sur le système de l'utilisateur. Les quatres arguments donnés signifient:<br />
<br />
* - : tous les attributs des fichiers réguliers restent inchangés,<br />
* root : le propriétaire du fichier est root,<br />
* root : le groupe propriétaire du fichier est root,<br />
* (optionnel) 0755 : les attributs du groupe propriétaire appliqués à tous les répertoires possédés par ce paquetage sont 0755 ( rwxr-xr-x ).<br />
<br />
<pre><br />
%doc README NEWS COPYING AUTHORS<br />
</pre><br />
<br />
Le champ spécial {{macro|%doc}} désigne les fichiers qui font partie de la documentation du paquetage. Les dits fichiers seront placés dans {{file|/usr/share/doc/gif2png/}}. Ce dossier sera aussi automatiquement créé. Les fichiers spécifiés par {{macro|%doc}} sont placés relativement au répertoire source décompressé dans {{file|BUILD}}.<br />
<br />
<pre><br />
%{_mandir}/man1/gif2png.1*<br />
%{_mandir}/man1/web2png.1*<br />
</pre><br />
<br />
Il est recommandé de lister ici aussi chaque fichier man ou info séparément. <br />
<br />
Aussi, vous vous demandez peut être pourquoi dire gif2png.1* et non pas gif2png.1.xz. C'est pour préserver la compatibilité avec les autres systèmes qui pourraient utiliser la compression xz. Si on trouve de telles références à xz dans des fichiers specs, les remplacer par un joker. Le plus souvent, on peut aussi utiliser %{_mandir}/man1/* qui prendra tous les fichiers qu'il trouvera.<br />
<br />
<pre><br />
%{_bindir}/gif2png<br />
%{_bindir}/web2png<br />
</pre><br />
<br />
On peut voir qu'il y a des macros pour chaque type de chemin nécessaire. Voici les plus utiles (regardez dans {{file|/usr/lib/rpm/macros}} pour les avoir toutes) : {{macro|%{_prefix} }}, {{macro|%{_bindir} }}, {{macro|%{_sbindir} }}, {{macro|%{_datadir} }}, {{macro|%{_libdir} }}, {{macro|%{_sysconfdir} }}, {{macro|%{_mandir} }}, {{macro|%{_infodir} }}. Pour des jeux, utilisez {{macro|%{_gamesbindir} }} et {{macro|%{_gamesdatadir} }}<br />
<br />
<br />
==== Section Changelog ====<br />
<br />
<pre><br />
%changelog <br />
</pre><br />
<br />
Cette section garde une trace des changements apportés au paquetage. Chaque paragraphe de cette section correspond à une nouvelle version du paquetage avec augmentation du numéro de « release » du paquetage (voir du numéro de version du paquetage si il empaquete une nouvelle version du logiciel). Ces paragraphes doivent respecter la structure suivante :<br />
<br />
<pre><br />
Mon Nov 02 2010 Camille Begnis <camille@mageia.org> 2.0.1-1mga1<br />
</pre><br />
<br />
* La première ligne du paragraphe commence par * avec, dans l'ordre et séparés par un espace :<br />
* 3 lettres pour le jour de la semaine (en anglais)<br />
* 3 lettres pour le mois (en anglais)<br />
* 2 chiffres pour le jour du mois (en anglais)<br />
* 4 chiffres pour l'année <br />
* Prénom du créateur du paquetage<br />
* Nom du créateur du paquetage<br />
* e-mail du créateur du paquetage entre <>.<br />
* version et release des modifications.<br />
<br />
<pre><br />
- Upgraded to 2.0.1<br />
</pre><br />
<br />
Ensuite, une ligne, commençant par un -, par modification appliquée au paquetage.<br />
<br />
Voici des exemples : <br />
<br />
<br />
<pre><br />
- spec file stolen from korganizer. <br />
- last snapshot before release <br />
- Mageia adaptations. <br />
- Fix bug in /etc/zsh use USERNAME instead of USER. <br />
- Remove petit bouchon which annoys other players. <br />
- Improve /etc/z* to source the /etc/profile.d/ files. <br />
- fix typo in examples directory name <br />
- fixed QT libs version requirements <br />
- add patch to handle Earl Grey tea <br />
</pre><br />
<br />
Notez que par défaut que seules les entrées datant de moins d'un an seront préservés lors de la construction du paquet. Si vous voulez modifier cela, changez la valeur de la macro {{macro|%_changelog_truncate}}<br />
<br />
Notez que par défaut uniquement les entrées de moins d'un an seront préservées dans le paquet construit. Pour modifier ce comportement changer la valeur de '''%_changelog_truncate'''.<br />
<br />
=== La construction ===<br />
<br />
Notre fichier {{file|spec}} est enfin complet. Prenez une grande inspiration, asseyez vous et tapez {{cmd|rpm -ba mypackage.spec}}.<br />
<br />
On peut ajouter l'option {{cmd|--clean}} qui nettoie le répertoire {{file|BUILD}} une fois le paquetage construit. Pratique si vous manquez de place disque.<br />
<br />
Vous allez voir apparaître toutes les commandes qu'il effectue pendant la construction. La toute dernière ligne donne le résultat :<br />
<br />
<pre><br />
* 0.01% probabilities: + exit 0<br />
* 99.99% probabilities for other cases. <br />
</pre><br />
<br />
Si vous êtes dans le second cas, regardez les options de construction de RPM ({{cmd|man rpm}}) pour déboguer votre travail, regardez les fichiers {{file|spec}} d'autres personnes, etc... <br />
<br />
Il y a une manière très propre de construire un paquetage :<br />
utilisez {{cmd|rpm -bs --rmspec --rmsource}}, pour supprimer tout ce qui provient de la construction d'origine, puis faites un {{cmd|rpm --rebuild}}.<br />
<br />
<br />
=== Optimiser le build ===<br />
<br />
Quand vous lancerez la commande pour construire le paquet, vous allez sans doute voir des messages comme "{{cmd|foo-devel is necessary for foo2}}".<br />
<br />
Cela signifie qu'il manque des informations dans d'autres paquets utilisés pour la compilation ( habituellement des fichiers du types toto.h ). Si vous ne les avez pas, la compilation va s'arreter ou des fonctionnalités vont manquer dans votre paquet.<br />
<br />
L'endoit où sont compilés les paquets officiels ( le cluster de compilation Mageia ) a déjà un grand nombre de ces paquets installés par les divers utilisateurs. Si un <br />
paquet est requis mais non déclaré dans votre fichier .spec, le paquet va compiler quand même. Cela fonctionnera, mais l'absence de ces informations empechera le build sur des machines n'ayant pas les packages devel non déclarés, rendant le debugage ou la mise à niveau plus difficile.<br />
<br />
Une manière que rechercher ces « BuildRequires manquants » est de commencer l'empaquetage avec seulement les paquets ''devel'' de base installés :<br />
<br />
* {{pkg|glibc-devel}}<br />
* {{pkg|libncurses5-devel}}<br />
* {{pkg|libstdc++6-devel}}<br />
<br />
Ensuite, installez seulement les paquets devel correspondant aux paquets demandés par la commande rpmbuild<br />
<br />
Quand vous lancez le build, observez les messages « checking for... ».<br />
<br />
Si vous voyez quelque chose comme « checking for foo... foo.h not found », cela signifie que le header nécessaire n'a pas été trouvé sur votre système. <br />
Recherchez le paquet devel contenant « foo.h », mais soyez prudent : vous pouvez trouver plus d'un paquet contenant que vous cherchez. Dans ce cas, choisissez le paquet le plus évident. Ne choississez pas un paquet relatif au réseau quand vous buildez une application de son (par exemple).<br />
<br />
Alors installez-le sur votre système, et n'oubliez pas d'ajouter son nom à la section BuildRequires de votre fichier {{file|SPEC}}.<br />
<br />
Des headers manquants peuvent également être trouvé durant la compilation elle-même. Si elle s'arrête, rechercher d'autres éléments manquants "{{file|foo.h}}" et appliquer la même solution.<br />
<br />
<br />
== Vérifier et tester un RPM ==<br />
<br />
Lire les pages [https://bugs.mageia.org/ Bugzilla] pour en savoir plus sur le sujet.<br />
<br />
<br />
=== Tests de base ===<br />
<br />
Les premières étapes à faire sont :<br />
<br />
* Les RPM ont-ils été créés dans les bons dossiers avec des noms corrects ? ({{file|~/rpm/SRPMS/}} et {{file|~/rpm/RPMS/i586/}}).<br />
* Les informations fournies par la commande {{cmd|rpm -qlivp --changelog mypackage.(src.)rpm}} sont-elles correctes ?<br />
<br />
<br />
=== Passer "rpmlint" sur le paquetage ===<br />
<br />
On utilise ensuite le programme {{prog|rpmlint}}, qui effectue des tests variés sur le paquetage. Vous pouvez obtenir un rapport sur le rpm spécifiée en tapant la commande:<br />
{{console-fr|rpmlint mon_paquet.<archtype>.rpm}}<br />
Pour plus de précisions, on peut y ajouter l'option '''-i'''.<br />
Vérifier le {{file|.rpm}} et le {{file|.src.rpm}}.<br />
<br />
Vous pouvez configurer {{prog|rpmlint]}} avec le fichier {{file|~/.rpmilintrc}} ou {{file|/etc/rpmlintrc}}.<br />
<br />
Vous devez définir au moins les suivantes :<br />
<br />
<pre><br />
from Config import *<br />
setOption("Packager","login@email.org")<br />
# default value<br />
# setOption('Packager', 'Mageia Team <http://www.mageia.org>|@mageia.org')<br />
addFilter("E: .* no-signature")<br />
addFilter("W: .* invalid-packager")<br />
addFilter("E: .* no-packager-tag")<br />
addFilter("E: .*-debug .*")<br />
addFilter("W: .*-debug .*") <br />
# not very clean, but easier to maintain<br />
release_tag = os.popen("rpm --eval '%mkrel 1'").readlines()[0][1:-1]<br />
setOption('ReleaseExtension', release_tag)<br />
</pre><br />
<br />
Si vous avez l'intention de créer un rpm approprié pour l'inclure dans les répertoire de Mageia, vous devez également veiller à ce que ''rpmlint-mageia-policy'' soit installé, car il contient les différentes configurations et les politiques utilisés par les empaqueteurs de Mageia.<br />
<br />
''rpmlint'' va vérifier beaucoup de choses comme : tags, binaires, fichiers de configuration, l'emplacement, l'autorisation, la propriété, la conformité FHS, sources, menus, scripts, contenu du fichier de spec... Pour plus de détails consulter /usr/share/rpmlint/config.d/mageia.error.list.<br />
<br />
<br />
=== Test d'installation ===<br />
<br />
Sur une machine, si possible différente de celle sur laquelle a été faite la compilation, faites une mise à jour ou une installation et vérifiez si : <br />
<br />
* Tous les fichiers prévus ont-ils été créés au bon endroit avec les bons droits et les bons propriétaires ? <br />
* Toutes les modifications d'installation (s'il y en a) fonctionnent-elles ? <br />
* Tous les exécutables et la documentation sont-ils accessibles aux utilisateurs à qui ils sont destinés ? <br />
<br />
Les perfectionnistes essaieront des installations et désinstallations diverses et variées pour vérifier que toutes les possibilités prévues sont correctement implémentées, par exemple quand il manque des paquetages requis. <br />
<br />
Si tous ces tests ont été passés avec succès, c'est presque fini et on peut aller à la dernière étape du processus : distribuer le paquetage.<br />
<br />
== Quelque chose ne va pas ? ==<br />
<br />
Bien, il semble que vous ayez lu ce tutoriel, c'est un bon début. Si vous ne trouvez pas votre réponse ici, vous pouvez toujours trouver plus d'informations. <br />
<br />
<br />
=== Pour les généralités RPM ===<br />
# Le RPM-HOWTO officiel (installé en même temps que le programme {{prog|rpm}} sur votre système). <br />
# Le livre ''Maximum RPM'', de Ed Bailey disponible sur [http://www.redhat.com/docs/books/max-rpm/max-rpm-html/]. <br />
# Poser une question dans la mailing list à laquelle vous vous êtes inscrit récemment, au début de ce howto.<br />
<br />
<br />
=== Pour des points plus spécifiques aux RPM Mageia : ===<br />
<br />
Dites un mot à l'équipe Assurance Qualité de Mageia.<br />
<br />
Si vous pensez que l'information que vous avez trouvée peut servir à d'autres, n'hésitez pas à la proposer au contributeur principal de ce document.<br />
<br />
<br />
== A propos des scripts de pré- et post-installation ==<br />
<br />
=== Les bases ===<br />
<br />
Un paquetage RPM est en fait bien plus qu'une simple archive contenant des fichiers à décompresser dans des répertoires spécifiques sur le système client.<br />
<br />
Le système fournit au programmeur une possibilité intéressante : les scripts de pré- et post-installation. Grâce à eux, le créateur du paquetage peut écrire un morceau de code qui sera exécuté sur la machine cliente pendant l'installation ou la suppression du paquetage.<br />
<br />
Il faut connaître certaines particularités de ces scripts pour en tenir compte : premièrement, ils doivent tenir dans un tampon de 8192 octets, deuxièmement, ils ne doivent pas être interactifs. Toute interaction avec l'utilisateur est à proscrire, puisqu'elle empêcherait les procédures automatiques d'installation de RPM de fonctionner.<br />
<br />
<br />
Ces scripts se composent de n'importe quel ensemble de commandes sh valides. En voici quatre : <br />
<br />
* {{macro|%pre}} : ce script s'exécute juste avant l'installation du paquetage sur le système. <br />
* {{macro|%post}} : ce script s'exécute juste après l'installation du paquetage sur le système. <br />
* {{macro|%preun}} : ce script s'exécute juste avant la désinstallation du paquetage du système. <br />
* {{macro|%postun}} : ce script s'exécute juste après la désinstallation du paquetage du système. <br />
<br />
<br />
Ces scripts ont un très grand rayon d'action et il faut les mettre au point avec le plus grand soin pour ne pas perturber le système hôte. Ne pas oublier que ces scripts s'exécuteront en tant que ''root''... Ce sont les tâches système qu'un administrateur système accomplirait pour installer un nouveau programme sur le système. Par exemple : <br />
<br />
* Ajouter un job {{prog|cron}} qui lance le programme à intervalles fixes. <br />
* Lancer {{prog|chkconfig}} pour lancer le démon au moment du boot. <br />
* ...<br />
<br />
<br />
=== Gestion des mises à jour ===<br />
<br />
Permettre la mise à jour, et pas seulement l'installation ou la désinstallation d'un paquetage complique un peu les choses... Le problème vient de ce que le script %postun de la mise à jour s'exécute après le script %post de la vieille version. Et tout ce que fait %post est perdu... <br />
<br />
Il est souvent utile de vérifier qu'une action ne se produit que pendant l'installation et non pendant une mise à jour. De même pour une action qui ne se produit que pendant la désinstallation et non pendant une mise à jour. Le mécanisme de RPM qui gère cela est un argument passé aux scripts %pre, %preun, %post et %postun par défaut. <br />
<br />
Cet argument indique le nombre d'instances de ce RPM qui seront installées sur la machine après l'exécution du script courant. Par exemple, si un nouveau paquetage est installé, 0 sera passé à %pre et 1 sera passé à %post. Quand le paquetage est mis à jour, 1 sera passé au %pre du nouveau RPM, 2 sera passé au %post du nouveau RPM, 2 sera passé au %preun du vieux RPM et 1 sera passé au %postun de l'ancien paquetage. <br />
<br />
<br />
{| border="1" width="500"<br />
|+ align="bottom" style="font-size: 9px; font-weight: bold;" | Table A-1. Valeurs des paramètres passés aux scripts pre et post<br />
! style="background:#efefef;" | Paramètre / Script<br />
! style="background:#efefef;" | %pre <br />
! style="background:#efefef;" | %post <br />
! style="background:#efefef;" | %preun <br />
! style="background:#efefef;" | %postun <br />
|-<br />
| pour une première installation || 1 || 1 || N/C || N/C<br />
|-<br />
| pour une mise à jour || 2 || 2 || 1 || 1 <br />
|-<br />
| pour une désinstallation || N/C || N/C || 0 || 0<br />
|}<br />
<br />
Le programmeur peut ainsi prévoir un fonctionnement différent de ses scripts selon qu'il s'agit d'une installation ou d'une mise à jour.<br />
<br />
* pour les scripts d'installation (%post, %pre) tester si $1 est égal à "1", ce qui signifie une première installation et non une mise à jour, <br />
* pour les scripts de désinstallation ( %postun, %preun) tester si $1 est égal à "0", ce qui signe une suppression complète ; sinon, c'est soit une mise à jour soit un "install --force" du même paquetage.<br />
<br />
<br />
Pour tester cet argument, on utilise la commande ''if'' suivante :<br />
<br />
<pre><br />
%postun<br />
if [ $1 = 0 ]; then<br />
// spécifique à la désinstallation<br />
fi<br />
if [ $1 = 1 ]; then<br />
// spécifique à la mise à jour<br />
fi<br />
</pre><br />
<br />
Un simple test suffit donc à appeler la bonne action au bon moment.<br />
<br />
<br />
== D'autres macros ==<br />
<br />
Pour construire des RPM pour Mageia, d'autres macros permettent de simplifier le fichier {{file|spec}}.<br />
<br />
* '''Gestion des pages info'''. Un exemple est le meilleur professeur :<br />
<br />
<pre><br />
%post<br />
%__install_info %{name}.info<br />
<br />
%preun<br />
%__install_info %{name}.info<br />
</pre><br />
<br />
* Gestion propre des langues. La meilleure méthode n'est pas de créer à la main les fichiers {{file|.mo}} qui se trouvent en général dans {{file|/usr/share/locale/..}}, mais d'utiliser une macro spéciale de la section %install, qui remplira un fichier spécial pour cela :<br />
<br />
<pre><br />
%find_lang %{name}<br />
</pre><br />
<br />
On peut alors utiliser ce fichier dans la liste de fichiers :<br />
<br />
<pre><br />
%files -f %{name}.lang<br />
</pre><br />
<br />
* '''Macros de construction''. Les macros %configure and %makeinstall sont actuellement assez grosses. Elles précisent le préfixe, mais aussi les répertoires communs (comme bindir, datadir, etc.) ; moyennant cela, elles fonctionnent correctement avec des paquetages de taille moyenne, mais nécessitent toujours un peu d'attention pour les autres. La macro %make lance la commande make avec l'option -j appropriée pour bien fonctionner avec les multiprocesseurs. S'il faut appeler manuellement le script {{prog|./configure}}, se souvenir ne '''JAMAIS''' coder l'architecture en dur ; la macro %{_target_platform} est faite pour cela (ou même %{_target_cpu}, si nécessaire). <br />
<br />
* '''Construction de serveurs'''. Pour construire des serveurs plus sûrs, on utilise une macro spécifique, %serverbuild, à utiliser avant que le processus de build ne démarre. Elle permet de meilleures options d'optimisation. La section %build ressemble souvent à :<br />
<br />
<pre><br />
%build<br />
%serverbuild<br />
%configure<br />
%make<br />
</pre><br />
<br />
* '''Macros d'initialisation des scripts'''. Quand on installe un paquetage qui fournit son propre script d'initialisation (les fichiers du répertoire {{file|/etc/init.d}}), il faut les ajouter par un appel du style {{cmd|chkconfig --add ..}}, sauf dans le cas des mises à jour, et il doit être redémarré s'il est en cours de fonctionnement ; en cas de désinstallation, il faut faire les actions inverses ; des macros spécifiques permettent cela sans peine :<br />
<br />
<pre><br />
%post<br />
%_post_service <initscript-name><br />
<br />
%preun<br />
%_preun_service <initscript-name><br />
</pre><br />
<br />
* '''Utilisation de fichiers fantômes'''. Certains paquetages, en particulier des jeux, utilisent parfois un fichier qui varie et qui peut même être absent. C'est ici que les fichiers fantômes sont utiles. Voici un exemple :<br />
<br />
<pre><br />
%install<br />
<br />
(...)<br />
<br />
mkdir -p $RPM_BUILD_ROOT/var/lib/games<br />
touch $RPM_BUILD_ROOT/var/lib/games/methanescores<br />
<br />
%post<br />
%create_ghostfile /var/lib/games/powermanga.hi root games 664<br />
<br />
(...)<br />
<br />
%files<br />
%attr(664, root, games) %ghost /var/lib/games/powermanga.hi<br />
</pre><br />
<br />
La macro %create_ghostfile se développe en :<br />
<br />
<pre><br />
if [ ! -f /var/lib/games/powermanga.hi ]; then <br />
touch /var/lib/games/powermanga.hi<br />
chown root.games /var/lib/games/powermanga.hi<br />
chmod 664 /var/lib/games/powermanga.hi<br />
fi <br />
</pre><br />
<br />
Vous pouvez aussi lister toutes les valeurs et les macros utilisées par rpm depuis les fichiers macros et rpmrc : '''rpm --showrc'''<br />
<br />
<!-- admel : information trouvé ailleurs et non vérifiées :<br />
<br />
* .desktop / MIME association de configuration de type MIME : Le système de menu XDG permet de faire l'association entre une application et un type MIME dans le fichier {{file|.desktop}} . The {{prog|update-desktop-database}} utility should be run if such {{file|.desktop}} file is installed / uninstalled on the system, using macros as shown in the following example:<br />
<br />
<pre><br />
%post<br />
%update_desktop_database<br />
<br />
%postun<br />
%clean_desktop_database<br />
</pre><br />
<br />
* Freedesktop.org MIME type database : the database used to list all available MIME types, with magic and/or extension file pattern should be updated using macros as shown in the following example :<br />
<pre><br />
<br />
%post<br />
%update_mime_database<br />
<br />
%postun<br />
%clean_mime_database<br />
</pre><br />
<br />
* Icon cache : <b>all</b> packages shipping icons stored in {{file|/usr/share/icons/hicolor}} (or other freedesktop icon theme directories, such as {{file|/usr/share/icons/gnome}} or {{file|/usr/share/icons/crystalsvg}} ) <b>must</b> update icon cache, as stated below (icons stored in {{file|/usr/share/icons}}, {{file|/usr/share/icons/mini}} or {{file|/usr/share/icons/large}} are not concerned by this requirement) :<br />
<br />
<pre><br />
...<br />
%file<br />
...<br />
%{_icondir}/hicolor/*<br />
%{_icondir}/crystalsvg/*<br />
....<br />
<br />
%post<br />
%update_icon_cache hicolor<br />
%update_icon_cache crystalsvg<br />
<br />
%postun<br />
%update_icon_cache hicolor<br />
%update_icon_cache crystalsvg<br />
</pre><br />
<br />
* GConf enregistrement de schémas : GNOME GConf schemas doit être installé sinon utiliser la macro suivante:<br />
<br />
<pre><br />
...<br />
# each schema key here corresponds to a file named /etc/gconf/schemas/<key>.schemas<br />
%define schemas apps_gnome_settings_daemon_default_editordesktop_gnome_font_rendering desktop_gnome_peripherals_keyboard_xkb fontilus themus<br />
<br />
%post<br />
%post_install_gconf_schemas %{schemas}<br />
<br />
%preun<br />
%preun_uninstall_gconf_schemas %{schemas}<br />
</pre><br />
<br />
* Scrollkeeper mise à jour de base de données: La base de données scrollkeeper (utilise l'index de la documentation docbook) devrait être mise à jour en installant un fichier {{file|.omf}} comme cela:<br />
<br />
<pre><br />
...<br />
%post<br />
%update_scrollkeeper<br />
<br />
%postun<br />
%clean_scrollkeeper<br />
</pre><br />
--><br />
<br />
== Interaction avec urpmi et rpmdrake ==<br />
<br />
Il faut parfois avertir l'utilisateur d'une précaution à prendre quand on met à jour ou qu'on installe une version particulière d'un paquetage. <br />
Les formats de nom de fichier suivants peuvent être utilisés :<br />
*{{file|README.install.urpmi}} n'est affiché que pour les paquetages installés ;<br />
*{{file|README.version.upgrade.urpmi}} et {{file|README.version.update.urpmi}} : Les affiches seulement pour les paquetages mis à jour ou mis à niveau ;<br />
Sont aussi supportés {{file|README.urpmi}} (affiché dans les deux cas) et {{file|README.upgrade.urpmi/README.update.urpmi}} (toujours affiché lors d'une mise à niveau). Ceux-ci ne doivent pas être utilisés car ils provoquent l'affichage du message à chaque mise à jour ultérieure, même si l'utilisateur a déjà vu le message à plusieurs reprises.<br />
<br />
Tutoriel (exemple avec README.install.urpmi) :<br />
<br />
* Mettre README.install.urpmi dans le répertoire SOURCES/ ; <br />
* Ajouter dans le fichier {{file|spec}} comme ''SourceX'' : README.install.urpmi (remplacez X par un chiffre approprié) ;<br />
* Dans la section '''%install''' : installer -m644%{SourceX} README.install.urpmi (notez l'absence du préfixe %buildroot) ;<br />
* Dans la section '''%files''' : ajouter README.install.urpmi dans une macro %doc, ou ajouter une macro %doc si il n'y en a aucune.<br />
<br />
<br />
== Une alternative: checkinstall ==<br />
<br />
Une autre façon vraiment simple de construire des RPM pour une utilisation personnelle est d'installer le paquet {{pkg|checkinstall}} ; de compiler la source comme d'habitude ({{cmd|./configure && make && sudo make install}}), mais en remplaçant {{cmd|make install}} par {{cmd|checkinstall}}.<br />
Ceci automatise la construction du RPM, tout en étant vraiment simple d'utilisation. <br />
L'avantage consiste dans le fait que vous ne contournez pas le manager RPM en compilant à partir des sources. (Cependant, si vous souhaitez distribuer vos RPM, il est fortement conseillé d'utiliser la méthode vue précédemment.)<br />
<br />
<br />
== Soumettre un paquet ==<br />
<br />
Vous avez réussi à créer le paquet parfait d'un tout nouveau programme, et souhaitez le voir dans les dépôts officiels de Mageia, soumettez le à l'équipe des mainteneurs de Mageia.<br />
<br />
Pour ça on utilise le système de rapport de bug de mageia : [https://bugs.mageia.org/ bugzilla].<br />
<br />
Malheureusement, Bugzilla n'est pas disponible en français, inscrivez-vous [https://identity.mageia.org/register | ici], avec une adresse email valide.<br />
<br />
=== Créer un Rapport de bug ===<br />
<br />
Faites « New », puis choisissez Mageia, ou rendez vous directement [https://bugs.mageia.org/enter_bug.cgi?product=Mageia&format=guided ici].<br />
<br />
* Mettez '''Component''' sur '''Nex RPM Package Request''' ;<br />
* Choisissez la '''Version''' ;<br />
* Choisissez le type d''''architecture''' ;<br />
* Choisissez la '''Version''' ;<br />
* Remplissez le champs '''Source RPM''' ;<br />
* Remplissez '''Summary''' avec le nom du package.<br />
<br />
Dans '''Details''', entrez une description du programme (il est préalablement remplie pour vous aiguiller).<br />
<br />
Envoyez le formulaire, laissez les autres champs vides, ce n'est pas nécessaire de les remplir. Ne cochez '''surtout pas''' les dernières cases, sinon votre rapport ne sera accessible qu'a très peu de personne, qui ne sont absolument pas concernées !<br />
<br />
<!-- admel : Pas su les trouver.<br />
<br />
=== Joindre son spec et ses patchs ===<br />
<br />
Cliquez sur '''Add an attachment''', donnez un nom clair dans le champ '''Description''', cochez la case '''patch''' si le fichier que vous envoyez est un patch, mettez un commentaire pour expliquer ce que fait votre patch.<br />
<br />
Si vous envoyez une nouvelle version d'un fichier, cochez la case correspondant à l'ancien fichier dans le champ '''Obsoletes'''.<br />
--><br />
<br />
[[Category:French]]<br />
[[Category:Packaging]]<br />
[[Category:Software]]<br />
[[Category:System]]<br />
[[Category:Contribute]]<br />
[[Category:RPM]]<br />
[[Category:Howto]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Packagers_Mentoring_Howto&diff=28213Packagers Mentoring Howto2015-07-13T10:17:37Z<p>Dtux: /* How to setup iurt on one’s machine */</p>
<hr />
<div>NOT FINALIZED YET, TODO:<br />
* add more urls <br />
<br />
= I want to be a mentor, how can I do it? =<br />
<br />
Mageia aims to develop as much as possible packagers team so that we can extend list of maintained packages for users. Thus mentoring new packagers should be seen as something formal and important for distribution future. Successfull mentoring means quality for distribution.<br />
<br />
Being a mentor does not mean you should read the documentation for your trainee :). Check [[Packagers_Howto_start|these bases]] are well known before starting.<br />
<br />
IRC chans are available:<br />
* #mageia-dev for development and packaging<br />
* #mageia-mentoring dedicated to discuss padawan and mentor issues <br />
* you may choose what is most appropriate for you (mail, jabber...)<br />
<br />
== Main steps of mentoring process ==<br />
<br />
=== Supervise the account creation procedure ===<br />
<br />
* Your trainee should create an account on http://identity.mageia.org/. This account will be used on the wiki, bugzilla, for mailing list subscribtion, and later for svn access.<br />
* svn commits right: once you think your trainee can commit in Mageia svn, open a request on the bugzilla. See [[Packagers_Howto_start#Getting_your_account_upgraded_for_commit_rights|this page]] for details.<br />
* mailing-lists registration: check it, it's not a formal prerequiresite but important to follow main changes, plans and discussion within Mageia team<br />
<br />
=== Ensure the new packager is familiarized with main packaging resources ===<br />
<br />
* [https://wiki.mageia.org/en/Packagers_svn subversion repository howto]<br />
* build system howto<br />
* [https://wiki.mageia.org/en/Bugzilla Bugzilla howto]<br />
<br />
=== Ensure the new packager is aware of Mageia packaging policies ===<br />
<br />
Or you will have more work explaining why the build system is rejecting their packages<br />
<br />
* [[Policies#Packaging|Packaging policies]]<br />
* [http://mageia.org/wiki/doku.php?id=policies-review Policies review]<br />
<br />
=== Ensure the new packager is aware of consequences ===<br />
<br />
Make them aware of how changes they make could affect the distribution (e.g. pushing a new library major) and what the responsibilities are in that regard (e.g. ensuring that all packages using a library are/can be rebuilt with the new library major).<br />
<br />
New packagers are not necessarily aware of the impact of their changes, here are some advices you should check it's well understood<br />
<br />
* Do '''not''' rush to update any packages that’s available in a newer version. This may have an impact on other packages that are not necessarily compatible with that newer version. This is particularly true for perl or ruby modules which tend to have strong interdependencies on each other<br />
* Before you upgrade a package look at packages which depend on it with **''<nowiki>urpmq --whatrequires foo</nowiki>''**<br />
* If you add the SRPM repository, you’ll be able to see packages which depend on a particular version for building<br />
* Do '''not''' leave a package in a broken state, do not rely on other people to fix your mistakes. <br />
** Please ask if you don’t know how to fix something. We do not expect people to know everything, but we expect people to be responsible and collaborative.<br />
** Likewise, please conform to the policies as much as you can. We do not expect people to know policies by heart, but we do expect that you check these policies when you make a change to a related package. We do expect that you ask if you find something confusing in these policies. This way we can be aware of it being confusing, and fix it, or rephrase it in a more understandable way.<br />
* Announce any changes that could have a strong impact on the mailing lists. people could then be warned about the upgrade, and will eventually help you to rebuild the needed packages. Communication is your best friend.<br />
* Test your changes locally<br />
<br />
=== Mentoring based on concrete examples ===<br />
<br />
It should be the main way to check new packager skills:<br />
<br />
* commits of pending updates<br />
* solve bug reports with patch attached<br />
* solve bug reports considered as trivial<br />
<br />
Here are the main steps you could follow until validation:<br />
# start with local builds for rpms and check all components - push import/commit for him to start with<br />
# give him rights to commit (contact adminsys team) when he is ready and check all commits done<br />
# ask for submit rights once you think he is ready to work on his own<br />
# keep contact with him in case of he needs specific help<br />
<br />
=== Announcing new packager ===<br />
<br />
Once process is over and apprentice got submit right, send a mail to dev mailing announcing new official packager and welcome him/her<br />
<br />
== Focus on tools ==<br />
<br />
The purpose is to describe the steps needed to teach trainees how to use the tools needed to build packages for Mageia:<br />
* make trainees familiar with these tools, and at the same time give tips/best practices<br />
* formalize a bit more how to use these tools the proper way, so that they can be ready to be full-fledged packagers and, hopefully, mentors as well<br />
<br />
During the training, some exercices should also be given to trainees so that they learn how to solve common packaging problems, like string format errors (reminder: import the packaging problems page), or making a package compliant with the various policies we have.<br />
<br />
This page assume that trainees have already some knowledge about how rpm works: SPEC file syntax, steps needed to build packages.<br />
<br />
=== ssh ===<br />
<br />
The first step is to teach how to use ssh, because that’s needed to be able to commit to svn, or submit packages to the Build System. The basic steps required are laid out [[Packagers_ssh|here]].<br />
<br />
=== subversion ===<br />
<br />
The first step is to teach how basic operation work on svn<br />
* svn checkout<br />
* svn add/svn del<br />
* svn status<br />
* svn diff<br />
<br />
Then, trainees need to learn how the mageia subversion is organized:<br />
* one subdirectory per package containing <br />
* SPECS/ directory where the spec file is<br />
* SOURCES/ directory where the patches are<br />
* an additional repository called binrepo where the tarball is located<br />
<br />
Commits should be atomic (ie, a change in the spec file that adds a patch should be in the same commit as the one where the patch is added).<br />
<br />
Warn people to test the package before they commit. Commit should be the last step to teach.<br />
<br />
Don’t forget to teach tips about commits<br />
* How to use SILENT: for little changes to fix a previous commit<br />
* How to use CCBUG (is this svn hook implemented yet ?)<br />
<br />
=== mgarepo ===<br />
<br />
When trainees are comfortable with svn, they can learn how to use mgarepo for checkout instead to save some tedious typing URLs.<br />
see [[Mgarepo|mgarepo howto]]<br />
<br />
=== bm ===<br />
<br />
Many people who aren’t familiar with mdv use rpmbuild to build the package. bm is nice in that it does not require files to be in %_topdir and thus people can build packages inplace<br />
<br />
=== patcher ===<br />
<br />
patcher is a simple tool that’s very useful to generate patches to fix broken packages (git is more powerful, but more complex too). Remind trainees that they should send patches upstream, and warn them about the pain of maintaining patches.<br />
[[http://labix.org/patcher]]<br />
<br />
=== iurt ===<br />
<br />
To test that a package builds in a clean environment, people can learn how to use iurt to simulate a real build. It also helps in triggering missing BuildRequires. More details may be found th the [[iurt]] page.<br />
<br />
==== How to setup iurt on one’s machine ====<br />
<br />
# install iurt<br />
# modify /etc/sudoers to have administrator rights on /usr/sbin/iurt_root_command<br />
# create a source rpm (''rpmbuild -bs'' or ''bm -s'')<br />
# run iurt using a remote repository (need good bandwidth) example with abiword-2.8.6-1.mga1.src.rpm and http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/<br />
iurt --repository http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ \<br />
--chrooted-urpmi http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ \<br />
--rebuild cauldron x86_64 ./SRPMS/abiword-2.8.6-1.mga1.src.rpm <br />
<br />
For 32-bit systems:<br />
iurt --repository http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ \<br />
--chrooted-urpmi http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ \<br />
--rebuild cauldron i586 ./SRPMS/abiword-2.8.6-1.mga1.src.rpm<br />
<br />
Cross compiling from x86_64 to i586: <br />
linux32 iurt --repository http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ \<br />
--chrooted-urpmi http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ \<br />
--rebuild cauldron i586 ./SRPMS/abiword-2.8.6-1.mga1.src.rpm<br />
<br />
==== urpmi-proxy speeds up things ====<br />
<br />
To save time and bandwidth you can set up [[urpmi-proxy]] and then use your proxy's URL:<br />
iurt --repository http://localhost/mageia/distrib/ --rebuild cauldron x86_64 \<br />
--chrooted-urpmi http://localhost/mageia/distrib/<br />
./SRPMS/abiword-2.8.6-1.mga1.src.rpm<br />
<br />
For 32-bit systems:<br />
iurt --repository http://localhost/mageia/distrib/ --rebuild cauldron i586 \<br />
--chrooted-urpmi http://localhost/mageia/distrib/ \<br />
./SRPMS/abiword-2.8.6-1.mga1.src.rpm<br />
<br />
Cross compiling from x86_64 to i586:<br />
linux32 iurt --repository http://localhost/mageia/distrib/ --rebuild cauldron i586 \<br />
--chrooted-urpmi http://localhost/mageia/distrib/ \<br />
./SRPMS/abiword-2.8.6-1.mga1.src.rpm<br />
<br />
=== rpmlint ===<br />
<br />
once trainees are comfortable with the various tool they need to use, a strong focus on quality should be made. rpmlint can ensure some packaging practices are respected, and policies should be emphasized.<br />
<br />
<br />
[[Packagers Team portal|Return to the Packagers portal]]<br />
<br />
[[Category:Contributors]]<br />
[[Category:Packaging]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Remaster_Mageia_Live_Media_Selfmade_ISO&diff=25647Remaster Mageia Live Media Selfmade ISO2015-03-07T12:30:31Z<p>Dtux: package name error on squashfs-tools</p>
<hr />
<div>ATTENTION:<br />
This is a copy of an old document from former mandrivauser.de wiki www.mandrivauser.de/doku/doku.php&id=allgemein:tutorials:selfmadeiso_en<br />
It still refers to Mandriva, but in general it still applies and makes it possible to extract and change a Mageia Live Iso and recreate a bootable image <br />
from it again (commonly referred to as remastering).<br />
It definitely needs adapting, but should mostly work as decribed.<br />
<br />
<br />
<br />
<br />
=== HowTo Customize Your Own Mandriva One ===<br />
<br />
<br />
An implementation of an older article by MIB (Mandriva International Backports), http://mib.pianetalinux.org/mib/forum/index.php?f=20&t=364&rb_v=viewtopic<br />
(Updated and improved by tigger-gg and wobo for Mandriva Linux 2010 Spring)<br />
<br />
This howto shows how you can change the contents of a Mandriva One 2010.1 and customize it to your own needs. It consists of several steps which should be carried out in the same order as they are written in the howto:<br />
<br />
*Create the infrastructure: Create a working directory where you do everything from start to finish.<br />
*Download and install: Download the original ISO image and install the required software<br />
*Unpacking and chroot: Unpack the original ISO image, save files which are needed later, and make the unpacked system your working system<br />
*Tasks in the chroot environment: Configure and customize the new system to your liking, it will become the resulting ISO image of this howto.<br />
*Post-production and Clean-up: Leave the new system and clean-up<br />
*Create the new ISO image: Pack the new system into an ISO image and make it hybrid to be burned to a CD/DVD or transferred to a USB key<br />
<br />
Let's start!<br />
<br />
== 0. Requirements and paths used in this HowTo ==<br />
<br />
<br />
*ISO image file of one of the Mandriva One editions (in this howto we used 2010 Spring ONE-KDE)<br />
*At least 5GB free space in the /home partition on your harddisk to build the new ISO image<br />
<br />
The working directory will be created below the user's home directory. If your user is called wobo then your working directory is /home/user/wobo/isowork. Everything in this howto is happening in this directory and below. Of course you can go your own way but make sure that you will adopt your own directory structure to the howto then.<br />
<br />
== 1. Creating the infrastructure and downloading the original ONE ==<br />
<br />
<br />
Open a terminal window. The following commands will create your work folder, download the ISO image and install the tools we need:<br />
<br />
mkdir isowork<br />
cd isowork<br />
wget -c http://mirror.netcologne.de/mageia/iso/3/Mageia-3-LiveDVD-KDE4-i586-DVD/Mageia-3-LiveDVD-KDE4-i586-DVD.iso<br />
su<br />
[give root password when prompted]<br />
urpmi isomaster squashfs-tools squashfs3-tools syslinux<br />
<br />
You can use another mirror, and another Live image.<br />
<br />
== 2. Unpacking the image and chroot ==<br />
<br />
<br />
Now start isomaster from the terminal window (you are still root!):<br />
<br />
isomaster &<br />
<br />
In the upper section use the „Back“ button to navigate to the new folder isowork/ (navigation works as in the usual file selection GUIs). Doubleclick on the image file mandriva-linux-one-2010-spring-KDE4-europe1-americas-cdrom-i586.iso. This will show the contents of the image file in the lower section of isomaster.<br />
In the lower section doubleclick on loopbacks, mark the file distrib-lzma.sqfs and click on the „Unpack“ button in the menue. This may take a while. After this has been done change into your terminal window but leave isomaster open.<br />
<br />
Now we unpack the squashfs file, it contains the complete operating system.<br />
<br />
unsquashfs distrib-lzma.sqfs<br />
<br />
Now before we go into the unpacked system we will save some files of the original ISO image for later use:<br />
<br />
mkdir file_save<br />
mkdir file_save/etc<br />
mkdir file_save/etc/shorewall<br />
mkdir file_save/etc/sysconfig<br />
cp -r squashfs-root/var/lib/shorewall file_save/<br />
cp squashfs-root/etc/hosts file_save/etc/hosts<br />
cp squashfs-root/etc/modprobe.conf file_save/etc/modprobe.conf<br />
cp squashfs-root/etc/modprobe.preload file_save/etc/modprobe.preload<br />
cp squashfs-root/etc/wpa_supplicant.conf file_save/etc/wpa_supplicant.conf<br />
cp squashfs-root/etc/shorewall/interfaces file_save/etc/shorewall/interfaces<br />
cp squashfs-root/etc/sysconfig/network file_save/etc/sysconfig/network<br />
<br />
As last step before you change into the subdirectory of the unpacked system you want to cut an existing network connection of your running system. This is essential if you want to use a network connection while customizing your new system. Then you change into the subdirectory and make it your root system (aka chroot).<br />
<br />
service network stop <br />
cd squashfs-root<br />
mount -o bind /dev ./dev<br />
mount -o bind /proc ./proc<br />
mount -o bind /sys ./sys<br />
chroot /complete/path/to/isowork/squashfs-root /bin/bash<br />
<br />
Explanation "chroot" in Wikipedia<br />
<br />
Explanation of "SquashFS" in Wikipedia<br />
<br />
== 3. Configuring and Customizing ==<br />
<br />
<br />
Now you are logged in as root to you virtual installation of Mageia KDE, you are already working inside this system. First you may want to configure and start your network connection. Use the Mageia Control Center to do this<br />
<br />
mcc<br />
or<br />
drakconnect<br />
You see the text version of the MCC in your terminal window - use the arrow keys to navigate to Network & Internet, then push the TAB key to go to OK and hit the Enter key. Then select the kind of connection and go on from that.<br />
<br />
After your network connection is up and running you can set the package media as you would do after a normal installation. Use a webtool like SmartUrpmi or the standard mirrorlist. To set up the complete set you only need these command line:<br />
<br />
<br />
urpmi.addmedia --distrib --mirrorlist <br />
<br />
Now you are set to go: roll your own flavor of Mageia Linux! Install and remove what you need and what you don't want. A good way to start is removing all the language packages you will never need plus a few applications you know you never use. In my case this are all languages except German and English (as fallback), Firefox, Amarok and some more.<br />
<br />
urpme -a locales-el locales-es locales-it locales-fr locales-nl locales-pl locales-pt locales-ru locales-tr firefox amarok compiz metisse ekiga evolution kopete ktorrent kmail kontact totem isdn4k slmodem kppp tvtime lancelot<br />
urpmi task-kde4 --no-suggests<br />
<br />
Certainly your mileage may vary and to each his own and all those sayings apply. The only restriction is the size of the resulting ISO image. If you want to burn it to a CD you have to keep the 700MB mark in mind.<br />
<br />
== 4. Leaving chroot ==<br />
<br />
<br />
When you are done and before you leave the chroot environment you have to stop the internet connection. Then you unmount the system links and - being back in your real system you want to restart your networking.<br />
<br />
service network stop<br />
exit<br />
umount ./dev<br />
umount ./proc<br />
umount ./sys<br />
service network start<br />
<br />
== 5. Postproduction, Clean-up ==<br />
<br />
<br />
There are some files which have to removed from the new system. If you have a wifi connection, in the directory squashfs-root remove all files in the directory etc/sysconfig/network-scripts/wireless.d<br />
<br />
rm etc/sysconfig/network-scripts/wireless.d/*<br />
<br />
Then remove the following files in the directory squashfs-root:<br />
<br />
rm etc/sysconfig/network-scripts/ifcfg-wlan0<br />
rm root/bash_history<br />
rm var/run/dhclient-wlan0.pid<br />
rm var/lock/subsys/shorewall<br />
rm var/lib/rpm/installed-through-deps.list.old<br />
rm var/lib/dhcp/dhclient-wlan0.leases<br />
rm var/lib/shorewall/firewall<br />
<br />
Now we will copy the original files we saved to the directory file_save and overwrite the files in squashfs-root/:<br />
<br />
cp -r ../file_save/shorewall var/lib/<br />
cp ../file_save/etc/hosts etc/hosts<br />
cp ../file_save/etc/modprobe.conf etc/modprobe.conf<br />
cp ../file_save/etc/modprobe.preload etc/modprobe.preload<br />
cp ../file_save/etc/wpa_supplicant.conf etc/wpa_supplicant.conf<br />
cp ../file_save/etc/shorewall/interfaces etc/shorewall/interfaces<br />
cp ../file_save/etc/sysconfig/network etc/sysconfig/network<br />
<br />
Done.<br />
<br />
== 6. Creating the new Image ==<br />
<br />
<br />
At last we pack the new system to a SquashFS file which can take some time. Make sure that you are in the correct directory:<br />
<br />
cd /home/user/isowork/squashfs-root<br />
mksquashfs * distrib-lzma.sqfs -comp xz -noappend -no-progress -info -b 1048576<br />
<br />
Now go to the still open isomaster. In the lower section and remove the old file distrib-lzma.sqfs by clicking on „Remove“ in the menue. In the upper section navigate into /isowork/squashfs-root and select the new distrib-lzma.sqfs and click on „Add“.<br />
When this is done open the „File“ menue and select Save under…. Chose a place to store the new ISO image and give a meaningful name. Click on OK and you're done!<br />
<br />
But the resulting .iso file still belongs to root. Change this with<br />
<br />
chown user:user name.iso<br />
<br />
where user:user is your username and the group of your user and name.iso is the ISO image.<br />
<br />
If you want to use your ISO image from a USB key you have to make it hybrid. As user change to where the file was stored and write the command:<br />
<br />
isohybrid -o 1 NAME_OF_THE_ISO_FILE.iso<br />
<br />
Now you can burn the file to a CD or DVD or transfer it to a USB key. The latter is done by root:<br />
<br />
dd if=NAME_OF_THE_ISO_FILE.iso of=/dev/sdX<br />
<br />
where sdX stands for the device name of your USB key which you can find out with<br />
<br />
fdisk -l<br />
<br />
Now we have arrived at the most important step: Test and Enjoy!<br />
<br />
Note: Option -o 1 added to isohybrid command, to avoid triggering bug 5036</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=RMLL_2014&diff=22734RMLL 20142014-06-30T10:52:07Z<p>Dtux: /* Planning */</p>
<hr />
<div>[[Category:Events]] [[Category:RMLL]] [[Category:2014]]<br />
<br />
[https://2014.rmll.info/?lang=en RMLL 2014] will take place in Montpellier - on July 05 to 11 2014.<br />
<br />
[https://2014.rmll.info/?lang=fr RMLL 2014] aura lieu à Montpellier du 05 au 11 Juillet 2014.<br />
<br />
Contact pour l'organisation :<br />
<br />
= Infos pratiques =<br />
<br />
== Jours et horaires d'ouverture ==<br />
* 05 et 06 Juillet 2014 : 10h00 à 01h00<br />
* 07 au 11 Juillet 2014 : 9h00 à 18h00<br />
<br />
== Lieu ==<br />
* [https://2014.rmll.info/Lieux Lieux]<br />
<br />
== Accès ==<br />
<br />
= Le stand =<br />
<br />
== Planning ==<br />
<br />
{| align=center cellpadding="5%" cellpadding="5%" cellspacing="0" class="wikitable" width=100%<br />
! rowspan="2"|Nom - Nickname - Mail<br />
! colspan="2"|05/07/2014<br />
! colspan="2"|06/07/2014 <br />
! colspan="2"|07/07/2014 <br />
! colspan="2"|08/07/2014 <br />
! colspan="2"|09/07/2014 <br />
! colspan="2"|10/07/2014 <br />
! colspan="2"|11/07/2014 <br />
|- <br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
| align=center|'''am'''<br />
| align=center|'''pm'''<br />
|-<br />
| xxx<br />
| x<br />
| <br />
| x<br />
| <br />
| x<br />
| <br />
| x<br />
| <br />
| x<br />
| <br />
| x<br />
| <br />
| x<br />
| <br />
|-<br />
|-<br />
| Arnaud - aranud - aranud@mageia-debutant.fr<br />
| oui<br />
| oui<br />
| oui<br />
| oui<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| Philippe - philippem - philippem@mageia.org<br />
| oui<br />
| oui<br />
| oui<br />
| oui<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|-<br />
|Daniel - DTux - contact@librepc.com <br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
| x<br />
|-}<br />
<br />
== Matériel ==<br />
<br />
* PC portable sous Mageia (aranud)<br />
* Quelques stickers Mageia (aranud)<br />
* [http://www.mageialinux-online.org/forum/topic-18120+vente-de-cles-usb.php Clés USB probablement]<br />
<br />
== Le dîner Mageia ==<br />
Le repas du libre étant classiquement le mercredi, autant se retrouver le mardi soir ?<br />
<br />
== Suivi des annonces ==</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Packagers_Mentoring_Howto&diff=17960Packagers Mentoring Howto2013-06-14T16:36:44Z<p>Dtux: added configuration of sudoers in iurt setup</p>
<hr />
<div>NOT FINALIZED YET, TODO:<br />
* add more urls <br />
<br />
= I want to be a mentor, how can I do it? =<br />
<br />
Mageia aims to develop as much as possible packagers team so that we can extend list of maintained packages for users. Thus mentoring new packagers should be seen as something formal and important for distribution future. Successfull mentoring means quality for distribution.<br />
<br />
Being a mentor does not mean you should read the documentation for your trainee :). Check [[Packagers_Howto_start|these bases]] are well known before starting.<br />
<br />
IRC chans are available:<br />
* #mageia-dev for development and packaging<br />
* #mageia-mentoring dedicated to discuss padawan and mentor issues <br />
* you may choose what is most appropriate for you (mail, jabber...)<br />
<br />
== Main steps of mentoring process ==<br />
<br />
=== Supervise the account creation procedure ===<br />
<br />
* You trainee should create an account on http://identity.mageia.org/. This account will be used on the wiki, bugzilla, for mailing list subscribtion, and later for svn access.<br />
* svn commits right: once you think your trainee can commit in Mageia svn, open a request on the bugzilla. See [[Packagers_Howto_start#Getting_your_account_upgraded_for_commit_rights|this page]] for details.<br />
* mailing-lists registration: check it, it's not a formal prerequiresite but important to follow main changes, plans and discussion within Mageia team<br />
<br />
=== Ensure the new packager is familiarized with main packaging resources ===<br />
<br />
* subversion repository howto<br />
* build system howto<br />
* Bugzilla howto<br />
<br />
=== Ensure the new packager is aware of Mageia packaging policies ===<br />
<br />
Or you will have more work explaining why the build system is rejecting their packages<br />
<br />
* [[Policies#Packaging|Packaging policies]]<br />
* [http://mageia.org/wiki/doku.php?id=policies-review Policies review]<br />
<br />
=== Ensure the new packager is aware of consequences ===<br />
<br />
Make them aware of how changes they make could affect the distribution (e.g. pushing a new library major) and what the responsibilities are in that regard (e.g. ensuring that all packages using a library are/can be rebuilt with the new library major).<br />
<br />
New packagers are not necessarily aware of the impact of their changes, here are some advices you should check it's well understood<br />
<br />
* Do '''not''' rush to update any packages that’s available in a newer version. This may have an impact on other packages that are not necessarily compatible with that newer version. This is particularly true for perl or ruby modules which tend to have strong interdependencies on each other<br />
* Before you upgrade a package look at packages which depend on it with **''<nowiki>urpmq --whatrequires foo</nowiki>''**<br />
* If you add the SRPM repository, you’ll be able to see packages which depend on a particular version for building<br />
* Do '''not''' leave a package in a broken state, do not rely on other people to fix your mistakes. <br />
** Please ask if you don’t know how to fix something. We do not expect people to know everything, but we expect people to be responsible and collaborative.<br />
** Likewise, please conform to the policies as much as you can. We do not expect people to know policies by heart, but we do expect that you check these policies when you make a change to a related package. We do expect that you ask if you find something confusing in these policies. This way we can be aware of it being confusing, and fix it, or rephrase it in a more understandable way.<br />
* Announce any changes that could have a strong impact on the mailing lists. people could then be warned about the upgrade, and will eventually help you to rebuild the needed packages. Communication is your best friend.<br />
* Test your changes locally<br />
<br />
=== Mentoring based on concrete examples ===<br />
<br />
It should be the main way to check new packager skills:<br />
<br />
* commits of pending updates<br />
* solve bug reports with patch attached<br />
* solve bug reports considered as trivial<br />
<br />
Here are the main steps you could follow until validation:<br />
# start with local builds for rpms and check all components - push import/commit for him to start with<br />
# give him rights to commit (contact adminsys team) when he is ready and check all commits done<br />
# ask for submit rights once you think he is ready to work on his own<br />
# keep contact with him in case of he needs specific help<br />
<br />
=== Announcing new packager ===<br />
<br />
Once process is over and apprentice got submit right, send a mail to dev mailing announcing new official packager and welcome him/her<br />
<br />
== Focus on tools ==<br />
<br />
The purpose is to describe the steps needed to teach trainees how to use the tools needed to build packages for Mageia:<br />
* make trainees familiar with these tools, and at the same time give tips/best practices<br />
* formalize a bit more how to use these tools the proper way, so that they can be ready to be full-fledged packagers and, hopefully, mentors as well<br />
<br />
During the training, some exercices should also be given to trainees so that they learn how to solve common packaging problems, like string format errors (reminder: import the packaging problems page), or making a package compliant with the various policies we have.<br />
<br />
This page assume that trainees have already some knowledge about how rpm works: SPEC file syntax, steps needed to build packages.<br />
<br />
=== ssh ===<br />
<br />
The first step is to teach how to use ssh, because that’s needed to be able to commit to svn, or submit packages to the Build System. The basic steps required are laid out [[Packagers_ssh|here]].<br />
<br />
=== subversion ===<br />
<br />
The first step is to teach how basic operation work on svn<br />
* svn checkout<br />
* svn add/svn del<br />
* svn status<br />
* svn diff<br />
<br />
Then, trainees need to learn how the mageia subversion is organized:<br />
* one subdirectory per package containing <br />
* SPECS/ directory where the spec file is<br />
* SOURCES/ directory where the patches are<br />
* an additional repository called binrepo where the tarball is located<br />
<br />
Commits should be atomic (ie, a change in the spec file that adds a patch should be in the same commit as the one where the patch is added).<br />
<br />
Warn people to test the package before they commit. Commit should be the last step to teach.<br />
<br />
Don’t forget to teach tips about commits<br />
* How to use SILENT: for little changes to fix a previous commit<br />
* How to use CCBUG (is this svn hook implemented yet ?)<br />
<br />
=== mgarepo ===<br />
<br />
When trainees are comfortable with svn, they can learn how to use mgarepo for checkout instead to save some tedious typing URLs.<br />
see [[Mgarepo|mgarepo howto]]<br />
<br />
=== bm ===<br />
<br />
Many people who aren’t familiar with mdv use rpmbuild to build the package. bm is nice in that it does not require files to be in %_topdir and thus people can build packages inplace<br />
<br />
=== patcher ===<br />
<br />
patcher is a simple tool that’s very useful to generate patches to fix broken packages (git is more powerful, but more complex too). Remind trainees that they should send patches upstream, and warn them about the pain of maintaining patches.<br />
[[http://labix.org/patcher]]<br />
<br />
=== iurt ===<br />
<br />
To test that a package builds in a clean environment, people can learn how to use iurt to simulate a real build. It also helps in triggering missing BuildRequires.<br />
<br />
==== howto setup iurt on one’s machine ====<br />
<br />
# install iurt<br />
# modify /etc/sudoers to have administrator rights on /usr/sbin/iurt_root_command<br />
# create a source rpm (''rpmbuild -bs'' or ''bm -s'')<br />
# run iurt using a remote repository (need good bandwidth) example with abiword-2.8.6-1.mga1.src.rpm and http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/<br />
iurt --repository http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ --rebuild cauldron x86_64 ./SRPMS/abiword-2.8.6-1.mga1.src.rpm --chrooted-urpmi http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/<br />
<br />
linux32 iurt --repository http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/ --rebuild cauldron i586 ./SRPMS/abiword-2.8.6-1.mga1.src.rpm --chrooted-urpmi http://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/<br />
<br />
===== urpmi-proxy =====<br />
<br />
To save time and bandwidth you can use urpmi-proxy<br />
iurt --repository http://localhost/mageia/distrib/ --rebuild cauldron x86_64 ./SRPMS/abiword-2.8.6-1.mga1.src.rpm --chrooted-urpmi http://localhost/mageia/distrib/<br />
<br />
linux32 iurt --repository http://localhost/mageia/distrib/ --rebuild cauldron i586 ./SRPMS/abiword-2.8.6-1.mga1.src.rpm --chrooted-urpmi http://localhost/mageia/distrib/<br />
<br />
=== rpmlint ===<br />
<br />
once trainees are comfortable with the various tool they need to use, a strong focus on quality should be made. rpmlint can ensure some packaging practices are respected, and policies should be emphasized.<br />
<br />
<br />
[[Packagers Team portal|Return to the Packagers portal]]<br />
<br />
[[Category:Contributors]]<br />
[[Category:Packaging]]</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=MageiaDays1&diff=16576MageiaDays12013-05-13T12:57:07Z<p>Dtux: </p>
<hr />
<div>We are thinking about organizing kind of Mageia days, 2 days to meet each other and speak about Mageia 4 release, development, i18n, QA... We may have a possibility to do it in Bruxelles during RMLL (http://2013.rmll.info/en/index.html). Still before starting this we need to know who could be around so that we have enough people to organize it. <br />
<br />
Add your name to this list :<br />
* Colin Guthrie (coling)<br />
* Nicolas Vigier (boklm)<br />
* Anne Nicolas (ennael)<br />
* Marja van Waes (marja)<br />
* Daniel Tartavel (dtux)</div>Dtuxhttps://wiki.mageia.org/mw-en/index.php?title=Commercial_vendors&diff=15978Commercial vendors2013-04-04T14:17:11Z<p>Dtux: </p>
<hr />
<div>[[Category:Users]][[Category:commercial]]<br />
<br />
For-profit organizations are part of the Mageia ecosystem. The following companies provide commercial services with or around Mageia software, tools or project.<br />
<br />
Note that Mageia.Org does not represent, validate, or endorse these organizations - this space is provided mainly as a reference - and may be redesigned or reindexed later at the [[Org_Board|Board]]'s discretion.<br />
<br />
== Consulting, training, development services ==<br />
<br />
* '''hupstream''' - http://hupstream.com/ - Paris & Nantes, France<br> Open Source Studio. Provides customized, hardware-certified Linux systems; ports your patches to upstream projects; helps you in opening your software project and improving your internal development/collaboration processes and infrastructure. For technological/industrial companies.<br> Operates in Europe (French, English spoken).<br />
<br />
<br />
* '''Name''' - url or contact mean - City, Country<br> presentation in 3/4 sentences: services provided, context, locales/countries managed<br />
<br />
== Hosting ==<br />
The following hosting providers can provide Mageia (virtual) servers :<br />
* '''GigaTux''' - http://www.gigatux.com/distro/mageia_vps<br />
* '''online.net''' - http://www.online.net/serveur-dedie/offres-distributions-gnu-linux.xhtml<br />
* '''Host Virtual''' - https://www.vr.org/os/linux-vps/mageia-vps<br />
* '''Name''' - url, city<br />
<br />
== Hardware vendors ==<br />
* '''Libre PC''' - http://www.librepc.com/ (website in French) - Lyon, France - Selling laptop and desktop computers with Mageia installed<br />
* '''PC-Fixer.be''' - http://www.pc-fixer.be/ (website in French) - Brussels, Belgium - Selling laptop and desktop computers with Mageia preinstalled<br />
* '''Name''' - url, city - type of hardware<br />
<br />
== Software vendors ==<br />
Other than what is already provided in the distribution.<br />
* '''OSdisc''' - http://www.osdisc.com/cgi-bin/view.cgi/products/linux/mageia - CD, DVD, USB flash<br />
<br />
* '''Name''' - url - software products<br />
<br />
== Goodies vendors ==<br />
* '''Unixstickers''' - http://www.unixstickers.com/linux_os_distribution_stickers/mageia_linux_os_sticker - sticker<br />
* '''Librestickers''' - http://www.librestickers.com/index.php/catalogsearch/result/?q=mageia - stickers<br />
<br />
* '''Name''' - url - goodies<br />
<br />
== Notes ==<br />
<br />
* '''Be aware that this list may be out of date, in which case you should advise or update the page with a clear and self-explainitory comment'''.<br />
* If your company provides services or products with or around Mageia software, for individuals or professionals, feel free to add yourself in this list, in the right country, in alphabetical order.<br />
* If you think a company should not be listed here, please contact someone from the [[Org_Board|Board]] or the [[Org_Council|Council]] and explain your reasons.<br />
* '''This page is a draft as of April, 5th''' - see [https://ml.mageia.org/wwsympa-wrapper.fcgi/arc/council/2011-04/msg00001.html this discussion thread] in the Council's list.</div>Dtux