Wiki Mageia

← Older revision Revision as of 21:07, 11 October 2025 Line 72: Line 72:  | Death Strandling | Death Strandling  | marche très bien avec Heroic Game Launcher et Proton-GE-proton10-17 | marche très bien avec Heroic Game Launcher et Proton-GE-proton10-17 −Il faut aussi installer vcrun2015 avec winetricks et configurer la version windows 11 dans wincfg.+Il faut aussi installer vcrun2015 avec winetricks (wine et wine32 doivent être installés) et configurer la version windows 11 dans wincfg.     |- |- Scroll44

← Older revision Revision as of 21:06, 11 October 2025 Line 65: Line 65:  | Control | Control  | werkt heel goed met Heroic Game Launcher en Proton-GE-Proton 9.16 | werkt heel goed met Heroic Game Launcher en Proton-GE-Proton 9.16  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Death Stranding  +| werkt erg goed met Heroic Game Launcher en Proton-GE-proton10-17..  +Geïnstalleerd vcrun2015 met winetricks (wine en wine32 moeten geïnstalleerd zijn).  +en stel Windows 11 in winecfg in     |- |- Scroll44

← Older revision Revision as of 21:02, 11 October 2025 Line 65: Line 65:  | Control | Control  | works very well with Heroic Game Launcher and Proton-GE-Proton 9.16 | works very well with Heroic Game Launcher and Proton-GE-Proton 9.16  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Death Stranding  +| works very well with Heroic Game Launcher and Proton-GE-proton10-17.  +Install vcrun2015 with winetricks and set windows 11 in winecfg.     |- |- Line 148: Line 154:  | Ghostrunner | Ghostrunner  | works very well with Heroic Game Launcher and Proton-GE-proton8-32. | works very well with Heroic Game Launcher and Proton-GE-proton8-32. −Install vcrun2019 with winetricks (wine and wine32 must be installed).+Install vcrun 2019 with winetricks (wine and wine32 must be installed).     |- |- Scroll44

← Older revision Revision as of 20:58, 11 October 2025 Line 67: Line 67:  | Control | Control  | marche très bien avec Heroic Game Launcher and Proton-GE-Proton 9.16   | marche très bien avec Heroic Game Launcher and Proton-GE-Proton 9.16    +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Death Strandling  +| marche très bien avec Heroic Game Launcher et Proton-GE-proton10-17  +Il faut aussi installer vcrun2015 avec winetricks et configurer la version windows 11 dans wincfg.     |- |- Scroll44

‎Update advisories repo, then find and fix problems: typo fix

← Older revision Revision as of 14:55, 10 October 2025 (One intermediate revision by the same user not shown)Line 1: Line 1: −This is a short version of what currently is done when pushing updates using [[mgaadv]] to a stable release (''updates_testing'' to ''updates''). There is another page with more details on [[How to create an update advisory]] for use by the QA team.+{{Introduction|This is a short version of what currently is done when pushing updates using [[mgaadv]] to a stable release (''updates_testing'' to ''updates''). There is another page with more details on [[How to create an update advisory]] for use by the QA team.<br><br>    −I here use two terminal windows, one as myself on my local machine and one as root @ duvel. If you haven't already initialized mgaadv on your local machine, do so first.+I here use two terminal windows, one as myself on my local machine and one as root @ duvel. If you haven't already initialized mgaadv on your local machine, do so first.}}     == Install mgaadv on your local machine == == Install mgaadv on your local machine == Line 19: Line 19:  </pre> </pre>    −== Update advisories repo ==+== Update the advisories repo, then find and fix problems ==    −Check that you have latest advisories:+===Check that you have the latest advisories:===  <pre> <pre>  [tmb@laptop ~]$ cd ~/mageia-advisories/advisories [tmb@laptop ~]$ cd ~/mageia-advisories/advisories Line 27: Line 27:  </pre> </pre>    −Check if there is potential problems (for perl advisory parser). This recreates ~/mageia-advisories/html/:+===Check the advisories for potential problems===  +Check whether there are potential problems for the perl advisory parser. This recreates ~/mageia-advisories/html/:  <pre> <pre>  [tmb@laptop advisories]$ mgaadv mksite [tmb@laptop advisories]$ mgaadv mksite  </pre> </pre>    −If you get any perl warnings/errors here, fix them or the advisory mails wont get pushed and website wont be updated. You only need to do this once at the beginning of your session as adding an ID to an advisory will not break it any further, so provided no-one else introduces an error while you're working, it should be fine!+===Fix the problems, if any===  +If you get any perl warnings/errors here, '''fix the related advisories or the advisory mails won't get pushed and the website won't be updated'''. You only need to do this once at the beginning of your session as adding an ID to an advisory will not break it any further, so provided no-one else introduces an error while you're working, it should be fine!     Usually the error is indentation issues or some special chars. For example indentation issues will show: Usually the error is indentation issues or some special chars. For example indentation issues will show: Marja

duplicate to my test space to see whether the page can be made even better.

New page

This is a short version of what currently is done when pushing updates using [[mgaadv]] to a stable release (''updates_testing'' to ''updates''). There is another page with more details on [[How to create an update advisory]] for use by the QA team.

I here use two terminal windows, one as myself on my local machine and one as root @ duvel. If you haven't already initialized mgaadv on your local machine, do so first.

== Install mgaadv on your local machine ==

This is a one-time installation of the advisories tool on your local machine. SVN updates must be performed under your own username, not under the shared mga-advisories user on the server:
<pre>
[root@laptop ~]# urpmi mga-advisories
- installs mgaadv
</pre>

Perform the initial config:
<pre>
[tmb@laptop ~]$ mkdir ~/.mga-advisories
[tmb@laptop ~]$ mgaadv initqaconf
- initializes config file (it opens your text editor to let you edit it)
- initial download of advisories into ~/mageia-advisories/advisories/
</pre>

== Update advisories repo ==

Check that you have latest advisories:
<pre>
[tmb@laptop ~]$ cd ~/mageia-advisories/advisories
[tmb@laptop advisories]$ svn up
</pre>

Check if there is potential problems (for perl advisory parser). This recreates ~/mageia-advisories/html/:
<pre>
[tmb@laptop advisories]$ mgaadv mksite
</pre>

If you get any perl warnings/errors here, fix them or the advisory mails wont get pushed and website wont be updated. You only need to do this once at the beginning of your session as adding an ID to an advisory will not break it any further, so provided no-one else introduces an error while you're working, it should be fine!

Usually the error is indentation issues or some special chars. For example indentation issues will show:

<pre>
YAML Error: Invalid element in map
Code: YAML_LOAD_ERR_BAD_MAP_ELEMENT
Line: 13
Document: 1
at /usr/lib/perl5/vendor_perl/5.18.1/YAML/Loader.pm line 352.
</pre>

== Assign a new advisory ID ==

Check at end of https://madb.mageia.org/tools/updates for advisories ready to be pushed.

Pushing updates (using samba update (bug 12999) as an example)

Assign advisory id (note: sometimes there can be split advisories in which case you would use '''mgaadv publish 12999.mga3''' and '''mgaadv publish 12999.mga4'''). This performs some checks then updates the advisory file in svn (that the QA team created) with the next available MGASA- or MGAA- number:
<pre>
[tmb@laptop advisories]$ mgaadv publish 12999
Found Bug: samba new security issue CVE-2013-4496
Checking for QA validation keyword… ✔
Checking dependent bugs… ✔ (None found)
Assigning ID to advisory 12999… ✔ MGASA-2014-0138
Do you want to publish now? [Y/n]: ✔
Publishing advisory MGASA-2014-0138… ✔
</pre>
If an update has a dependent bug that is still open, this function will warn you and ask if you would like to continue anyway. If you will be pushing that dependent update in the same batch as this one, you may normally select that option and publish anyway (but check the comments in both bugs to make sure there isn't some kind of special procedure needed). If not, then abort and don't publish this update at this time. This warning will appear even if you have already published the dependent bug because the bug status is not changed until the update is pushed (which happens in the next step).

This procedure is called "publishing" but it actually doesn't publish anything. That is done as part of the following step.

== Push the update ==

On duvel, use screen or tmux to make avoid breakages during package move (in case you lose the network connection):
<pre>
[root@duvel ~]# screen
</pre>

Trigger package move, advisory mail, updating of https://advisories.mageia.org/ and closing of bugs on all advisories that were marked in the previous step:
<pre>
[root@duvel ~]$ update_mga-advisories
Re-running as 'mga-advisories' user.
...
</pre>

There will be a whole bunch of debug output and both a sysadmin-report and a qa-report mail will be sent afterwards. The whole procedure can take over 15 minutes for a single advisory. Finally, fix the file permissions on files and directories that were touched:

<pre>
find /distrib/{bootstrap,mirror}/ -user root \! -type l -exec chown schedbot:schedbot {} +
</pre>

And you are done and can exit all screen and terminal windows on duvel.

== Backports ==

The above procedure is for normal updates to a stable release. Updates to ''backports'' do not have an advisory and therefore do not need such an involved process. Instead, follow this process:

# There must be a bug open for the backport. Ensure that QA has tested and approved of the package by ensuring the '''validated_backport''' exists in the bug keywords.
# Run a command of this form on duvel:
<pre>
mga-move-pkg --sync --backport 9/core/foobar-0.1-1.mga10.src.rpm
find /distrib/{bootstrap,mirror}/ -user root \! -type l -exec chown schedbot:schedbot {} +
</pre>
:3. Add a comment to the bug manually to confirm that the package has been moved. Assign the bug to qa-bugs@ml.mageia.org. The QA team will then draft an announcement that they will post to [https://ml.mageia.org/l/info/backports-announce backports-announce].

''NOTE'': This process was developed in 2024 to ensure that users can stay abreast of backports changes. It may change in the future if ''mga-move-pkg'' is updated to automatically mail notifications to backports-announce by itself.

== Errors ==

If a problem occurs during the mga-move-pkg stage, then the program may abort without performing all its steps (including package move, update bug, send e-mail, etc.). If the problem was temporary, try just running the command again. If there is still an issue (you may need to read the e-mail sent to qa-reports@ml to see details) then you may need to manually update the advisory status files to continue.

For example, if an error occurred during the package move stage, then the package(s) may have been moved but the status might not have been updated to reflect that. Subsequent invocations will then try to move a package that no longer exists in the updates_testing media where it's expected, causing an error every time. In this case, you will need to edit the appropriate file in /var/lib/mga-advisories/status/ to add a move line to indicate that the move has, indeed, taken place.

<!--[[Category:Sysadmin]]
[[Category:QA]]--> Marja

‎Backport kernels: syntax typo

← Older revision Revision as of 15:12, 7 October 2025 Line 87: Line 87:  $ sudo rmmod kvm_intel  ''(When using Intel CPU; If you have AMD CPU then instead execute rmmod kvm_amd.)'' <br> $ sudo rmmod kvm_intel  ''(When using Intel CPU; If you have AMD CPU then instead execute rmmod kvm_amd.)'' <br>  $ sudo rmmod kvm <br> $ sudo rmmod kvm <br> −- or blacklist them, see {Bug|34408#c7}}.+- or blacklist them, see {{Bug|34408#c7}}.     == Kernel series in Cauldron == == Kernel series in Cauldron == Morgano

← Older revision Revision as of 19:48, 15 September 2025 Line 201: Line 201:  | werkt heel goed met Steam Proton 7.0.6 | werkt heel goed met Steam Proton 7.0.6  Launch option : PROTON_USE_WINED3D11=1 %command% Launch option : PROTON_USE_WINED3D11=1 %command%  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Styx Master of shadows  +| werkt heel goed met Steam en Proton 9.0-4.     |- |- Scroll44

← Older revision Revision as of 19:47, 15 September 2025 Line 198: Line 198:  | marche très bien avec Steam Proton 7.0.6 | marche très bien avec Steam Proton 7.0.6  Option de lancement : PROTON_USE_WINED3D11=1 %command%. Option de lancement : PROTON_USE_WINED3D11=1 %command%.  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Styx Master of shadows  +| marche très bien sur steam avec proton 9.0-4     |- |- Scroll44

← Older revision Revision as of 19:45, 15 September 2025 Line 199: Line 199:  | works very well with Steam Proton 7.0.6 | works very well with Steam Proton 7.0.6  Launch option : PROTON_USE_WINED3D11=1 %command% Launch option : PROTON_USE_WINED3D11=1 %command%  +  +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Styx Master of shadows  +| works very well with steam avec proton 9.0-4     |- |- Line 210: Line 215:  | works very well with steam and Proton 8.0-4. | works very well with steam and Proton 8.0-4.  Launch option : DXVK_FRAME_RATE=60 PROTON_USE_WINED3D=1 %command% Launch option : DXVK_FRAME_RATE=60 PROTON_USE_WINED3D=1 %command% − +|-  +| style="width: 5%"| [[File:App-accessories.png|25px|center]]  +| Bioshock remastered  +| works very well with steam avec proton 8.0-5  |- |-  | style="width: 5%"| [[File:App-accessories.png|25px|center]] | style="width: 5%"| [[File:App-accessories.png|25px|center]] Scroll44

‎Apprenticeship in progress

← Older revision Revision as of 11:16, 12 September 2025 (2 intermediate revisions by the same user not shown)Line 194: Line 194:  | Template || Example || [https://ml.mageia.org 2025-08-25] || {{yes|Done}} || [https://bugs.mageia.org {{yes|Done}} || [https://bugs.mageia.org {{yes|Done}} || {{yes|Done}} || 5/5<br>app1<br>app2<br>app3<br>app4<br>app5 || {{yes|Done}} || {{yes|Done}} || 10/10<br>app1 app2<br>app3 app4<br>app5 app6<br>app7 app8<br>app9 app10 || 2021-10-17<br>or<br>[https://ml.mageia.org {{yes|Done}} 2021-02-14 | Template || Example || [https://ml.mageia.org 2025-08-25] || {{yes|Done}} || [https://bugs.mageia.org {{yes|Done}} || [https://bugs.mageia.org {{yes|Done}} || {{yes|Done}} || 5/5<br>app1<br>app2<br>app3<br>app4<br>app5 || {{yes|Done}} || {{yes|Done}} || 10/10<br>app1 app2<br>app3 app4<br>app5 app6<br>app7 app8<br>app9 app10 || 2021-10-17<br>or<br>[https://ml.mageia.org {{yes|Done}} 2021-02-14  |- |- −| Moufinure || papoteur || [https://ml.mageia.org/l/arc/dev/2025-08/msg00110.html 2021-02-14] ||  ||  ||  ||  || || || ||  ||+| Moufinure || papoteur || [https://ml.mageia.org/l/arc/dev/2025-08/msg00110.html 2025-08-25] ||  ||  ||  ||  || caprice32  || || ||  ||  |-   |-    |AurelianR    || DavidG ||[https://ml.mageia.org/l/arc/dev/2025-02/msg00006.html 2025-02-04] || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} ||  mingw-libgcrypt<br>ppsspp<br>vowpal-wabbit<br>zh-autoconvert<br>yodl<br>yencode<br>apr-utils<br>(and about a hundred more)|| {{yes|Done}} || {{yes|Done}} || tnef<br>vulkan-memory-allocator<br>dolphin-emu<br>virtuoso-opensource<br>mpich<br>xen<br>vde2<br>ntk<br>tkgate<br>sugar-artwork<br>fluxbox<br>kde-pdf-servicemenu<br>tcp_wrappers<br>goverlay<br>linphone stack || [https://ml.mageia.org/l/arc/dev/2025-07/msg00146.html {{yes|Done}} 2025-07-09 |AurelianR    || DavidG ||[https://ml.mageia.org/l/arc/dev/2025-02/msg00006.html 2025-02-04] || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} || {{yes|Done}} ||  mingw-libgcrypt<br>ppsspp<br>vowpal-wabbit<br>zh-autoconvert<br>yodl<br>yencode<br>apr-utils<br>(and about a hundred more)|| {{yes|Done}} || {{yes|Done}} || tnef<br>vulkan-memory-allocator<br>dolphin-emu<br>virtuoso-opensource<br>mpich<br>xen<br>vde2<br>ntk<br>tkgate<br>sugar-artwork<br>fluxbox<br>kde-pdf-servicemenu<br>tcp_wrappers<br>goverlay<br>linphone stack || [https://ml.mageia.org/l/arc/dev/2025-07/msg00146.html {{yes|Done}} 2025-07-09 Papoteur

‎Cancel the build: Finding build ID

← Older revision Revision as of 05:57, 11 September 2025 Line 13: Line 13:     sudo -u schedbot cancel_build 20231231211004.pterjan.duvel.1487312    sudo -u schedbot cancel_build 20231231211004.pterjan.duvel.1487312    −providing the build ID you just found.+providing the build ID you just found. If ''Status'' isn't available yet, take a look through the process list on duvel for the appropriate remote ''iurt'' invocation and interpolate the build ID from the arguments.     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

Versions update, do backup

← Older revision Revision as of 08:29, 8 September 2025 Line 80: Line 80:  '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''    −'''Regarding kernel-stable-userspace-headers''' contra ''kernel-userspace-headers for 6.6 kernels:'' The packages are used for building applications; use the one for the current kernel you build for. They conflict each other and are handled correctly by urpmi & drakrpm - when you have '''updated mageia-repos and meta-task packages''' to 9.4 versions (at time of writing found in updates_testing) - and using kernel versions 6.6.103+ and 6.12.44+.+'''Regarding kernel-stable-userspace-headers''' contra ''kernel-userspace-headers for 6.6 kernels:'' The packages are used for building applications; use the one for the current kernel you build for. They conflict each other and are handled correctly by urpmi & drakrpm - when you have '''updated mageia-repos and meta-task packages''' to 9.4 versions (at time of writing found in updates_testing) - and using kernel versions 6.6.104+ and 6.12.44+.     '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source Line 99: Line 99:  Note that it is not guaranteed that all series cover all architectures and flavours. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavour (e.g., desktop), or new flavours may emerge (e.g., desktop-tunedv3 for x86_64-v3). Note that it is not guaranteed that all series cover all architectures and flavours. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavour (e.g., desktop), or new flavours may emerge (e.g., desktop-tunedv3 for x86_64-v3).    −'''WARNING:''' Avoid running too fresh kernels on any kind of production system, especially kernels that are still rc versions, release candidates. If you run them to test anyway, please monitor the Linux kernel mailing list and be aware that there is a strong likelihood of bugs that will cause data corruption or other severe issues.+'''WARNING:''' Avoid running too fresh kernels on any kind of production system, especially kernels that are still rc versions, release candidates. If you run them to test anyway, please monitor the Linux kernel mailing list and be aware that there is a strong likelihood of bugs that will cause data corruption or other severe issues. So now even more important that you have backups of your data.     '''TIP:''' Have more than one series installed, to have something to fall back to. '''TIP:''' Have more than one series installed, to have something to fall back to.    −As an example, on August 28 2025 we had the following kernels in Cauldron:+As an example, on September 8, 2025 we had the following kernels in Cauldron: −* kernel-mainline -> 6.17.0-rc3 (x86_64, desktop only)+* kernel-mainline -> 6.17.0-rc4 (x86_64, desktop only)  * kernel-stable-testing -> 6.16.2 (x86_64, desktop only) * kernel-stable-testing -> 6.16.2 (x86_64, desktop only)  ** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)'' ** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)''  * kernel-stable -> 6.15.11 (x86_64, desktop only) * kernel-stable -> 6.15.11 (x86_64, desktop only) −* kernel -> 6.12.43 (all arches, all flavours)+* kernel -> 6.12.45 (all arches, all flavours)  * kernel-lts -> 6.6.100 (all arches, all flavours) * kernel-lts -> 6.6.100 (all arches, all flavours) Morgano

‎For Qa team:

← Older revision Revision as of 15:39, 3 September 2025 Line 118: Line 118:     * mageiatester - Denis - mageiatester at i2pmail dot org * mageiatester - Denis - mageiatester at i2pmail dot org  +  +* udham - udham sidhu - udhams at hotmail dot com     * Morgano - Morgan Leijström - fri at tribun dot eu * Morgano - Morgan Leijström - fri at tribun dot eu     * jank - Jean-Claude Stiegler - jcstiegler at free dot fr * jank - Jean-Claude Stiegler - jcstiegler at free dot fr Davidwhodgins

← Older revision Revision as of 11:24, 3 September 2025 Line 40: Line 40:  Viele Audio- und Video-Codecs sind für die freie Verwendung in kleineren oder größeren Teilen der Welt eingeschränkt und Anwendungen, die diese fest eingebunden haben befinden sich im tainted Repository. Viele Audio- und Video-Codecs sind für die freie Verwendung in kleineren oder größeren Teilen der Welt eingeschränkt und Anwendungen, die diese fest eingebunden haben befinden sich im tainted Repository.    −Empfohlenermaßen solltest Sie vor der Installation prüfen, ob Sie einige der Pakte von dort legal nutzen können, abhängig von der Nutzung und in welchem Teil der Welt Sie sich befinden.+Empfohlenerweise sollten Sie vor der Installation prüfen, ob Sie einige der Pakte von dort legal nutzen können, abhängig von der Nutzung und in welchem Teil der Welt Sie sich befinden.     Wenn Sie alles aus den tainted Quellen aktualisieren möchten, was Sie auf Ihrem System installiert haben: aktivieren Sie beide Quellen, tainted und tainted_updates. Bei 64-Bit System sollten zusätzlich die 32-Bit Quellen aktiviert werden und anschließend als root der Befehl urpmi --auto-select ausgeführt werden. Wenn Sie alles aus den tainted Quellen aktualisieren möchten, was Sie auf Ihrem System installiert haben: aktivieren Sie beide Quellen, tainted und tainted_updates. Bei 64-Bit System sollten zusätzlich die 32-Bit Quellen aktiviert werden und anschließend als root der Befehl urpmi --auto-select ausgeführt werden. Line 126: Line 126:  Beispiele: Wir haben FreeCAD (eine sehr funktionsreiche Anwendung zur technischen CAD welches in starker Entwicklung ist) und Slic3r (3D Drucker), aber eventuell sind Sie daran interessiert die Entwicklerversion einzusetzen um zusätzliche Eigenschaften verwenden zu können. Sie können die von Mageia zur Verfügung gestellte Version installiert lassen oder mehr als eine Version im AppImage Format verwenden. https://forums.mageia.org/en/viewtopic.php?f=7&t=12200 Beispiele: Wir haben FreeCAD (eine sehr funktionsreiche Anwendung zur technischen CAD welches in starker Entwicklung ist) und Slic3r (3D Drucker), aber eventuell sind Sie daran interessiert die Entwicklerversion einzusetzen um zusätzliche Eigenschaften verwenden zu können. Sie können die von Mageia zur Verfügung gestellte Version installiert lassen oder mehr als eine Version im AppImage Format verwenden. https://forums.mageia.org/en/viewtopic.php?f=7&t=12200    −[https://github.com/AppImage/AppImageUpdate {{prog-de|AppImageUpdate}}] kann ausgeführt werden um AppImages auf die neueste Version zu aktualisieren. Es ist selbst ein AppImage und kann sich auch selbst aktualisieren. Da es Delta-Updates verwendet, sind die Downloads sehr klein und effizient. '''Beachten''' Sie, dass Sie derzeit [https://github.com/AppImage/AppImageUpdate/issues/182#issuecomment-972461213 einen Link zu den Zertifikaten erstellen müssen. Leider sind viele AppImages nicht mit den erforderlichen Informationen ausgestattet damit der Updater funktioniert. Ein gutes Beispiel hierfür ist FreeCAD, wodurch Sie eine große Menge an Daten zum herunterladen sparen. Um zu prüfen ob ein AppImage die erforderlichen Aktualisierungsinformationen enthält, geben Sie {{cmd-de|./dasProgramm.AppImage --appimage-updateinformation}} ein; keine Ausgabe bedeutet keine Informationen.+[https://github.com/AppImageCommunity/AppImageUpdate {{prog-de|AppImageUpdate}}] kann ausgeführt werden um AppImages auf die neueste Version zu aktualisieren. Es ist selbst ein AppImage und kann sich auch selbst aktualisieren. Da es Delta-Updates verwendet, sind die Downloads sehr klein und effizient. '''Beachten''' Sie, dass Sie derzeit [https://github.com/AppImageCommunity/AppImageUpdate/issues/182#issuecomment-972461213 einen Link zu den Zertifikaten erstellen müssen. Leider sind viele AppImages nicht mit den erforderlichen Informationen ausgestattet damit der Updater funktioniert. Ein gutes Beispiel hierfür ist FreeCAD, wodurch Sie eine große Menge an Daten zum herunterladen sparen. Um zu prüfen ob ein AppImage die erforderlichen Aktualisierungsinformationen enthält, geben Sie {{cmd-de|./dasProgramm.AppImage --appimage-updateinformation}} ein; keine Ausgabe bedeutet keine Informationen.     {{Note-de|Wenn die AppImage-Anwendung nicht funktioniert weil ihr Abhängigkeiten fehlen, ist dies ein Fehler im AppImage selbst, da es alle benötigten Daten enthalten sollte. Ein unvollständiges AppImage kann mit einigen Distributionen funktionieren, mit anderen allerdings nicht. Wenn Sie also dieses Problem feststellen, informieren Sie den Ersteller des AppImage damit dies korrigiert werden kann.}} {{Note-de|Wenn die AppImage-Anwendung nicht funktioniert weil ihr Abhängigkeiten fehlen, ist dies ein Fehler im AppImage selbst, da es alle benötigten Daten enthalten sollte. Ein unvollständiges AppImage kann mit einigen Distributionen funktionieren, mit anderen allerdings nicht. Wenn Sie also dieses Problem feststellen, informieren Sie den Ersteller des AppImage damit dies korrigiert werden kann.}} Psyca

← Older revision Revision as of 11:21, 3 September 2025 Line 125: Line 125:  Examples: We have FreeCAD (a very capable mechanical CAD in heavy development) and Slic3r (3D printer CAM), but you may be interested in having the development versions to get extra features.  You may still have the Mageia packaged version installed, or more than one version in AppImage format. https://forums.mageia.org/en/viewtopic.php?f=7&t=12200 Examples: We have FreeCAD (a very capable mechanical CAD in heavy development) and Slic3r (3D printer CAM), but you may be interested in having the development versions to get extra features.  You may still have the Mageia packaged version installed, or more than one version in AppImage format. https://forums.mageia.org/en/viewtopic.php?f=7&t=12200    −[https://github.com/AppImageCommunity/AppImageUpdate {{prog|AppImageUpdate}}] can be run to update some AppImages to latest version. It is itself an AppImage, and can also update itself. As it uses delta updates, the downloads are very small and efficient. '''Note''' that you currently need to [https://github.com/AppImage/AppImageUpdate/issues/182#issuecomment-972461213 make a link to certificates.] Unfortunately many AppImages are not prepared with required information for the updater to work. One good example though is FreeCAD, saving you a lot in download size. To check if an AppImage contain update information, issue {{cmd|./thatprogram.AppImage --appimage-updateinformation}}; no output means no info.+[https://github.com/AppImageCommunity/AppImageUpdate {{prog|AppImageUpdate}}] can be run to update some AppImages to latest version. It is itself an AppImage, and can also update itself. As it uses delta updates, the downloads are very small and efficient. '''Note''' that you currently need to [https://github.com/AppImageCommunity/AppImageUpdate/issues/182#issuecomment-972461213 make a link to certificates.] Unfortunately many AppImages are not prepared with required information for the updater to work. One good example though is FreeCAD, saving you a lot in download size. To check if an AppImage contain update information, issue {{cmd|./thatprogram.AppImage --appimage-updateinformation}}; no output means no info.     {{Note|If the AppImage application does not work because it is missing dependencies, that is a fault in the AppImage, as it is supposed to be self-contained. An incomplete AppImage may work on some distributions, and not on others. So if you see that problem, tell the application AppImage creator so they can fix the AppImage.}} {{Note|If the AppImage application does not work because it is missing dependencies, that is a fault in the AppImage, as it is supposed to be self-contained. An incomplete AppImage may work on some distributions, and not on others. So if you see that problem, tell the application AppImage creator so they can fix the AppImage.}} Psyca

‎AppImage: link update

← Older revision Revision as of 22:47, 2 September 2025 Line 125: Line 125:  Examples: We have FreeCAD (a very capable mechanical CAD in heavy development) and Slic3r (3D printer CAM), but you may be interested in having the development versions to get extra features.  You may still have the Mageia packaged version installed, or more than one version in AppImage format. https://forums.mageia.org/en/viewtopic.php?f=7&t=12200 Examples: We have FreeCAD (a very capable mechanical CAD in heavy development) and Slic3r (3D printer CAM), but you may be interested in having the development versions to get extra features.  You may still have the Mageia packaged version installed, or more than one version in AppImage format. https://forums.mageia.org/en/viewtopic.php?f=7&t=12200    −[https://github.com/AppImage/AppImageUpdate {{prog|AppImageUpdate}}] can be run to update some AppImages to latest version. It is itself an AppImage, and can also update itself. As it uses delta updates, the downloads are very small and efficient. '''Note''' that you currently need to [https://github.com/AppImage/AppImageUpdate/issues/182#issuecomment-972461213 make a link to certificates.] Unfortunately many AppImages are not prepared with required information for the updater to work. One good example though is FreeCAD, saving you a lot in download size. To check if an AppImage contain update information, issue {{cmd|./thatprogram.AppImage --appimage-updateinformation}}; no output means no info.+[https://github.com/AppImageCommunity/AppImageUpdate {{prog|AppImageUpdate}}] can be run to update some AppImages to latest version. It is itself an AppImage, and can also update itself. As it uses delta updates, the downloads are very small and efficient. '''Note''' that you currently need to [https://github.com/AppImage/AppImageUpdate/issues/182#issuecomment-972461213 make a link to certificates.] Unfortunately many AppImages are not prepared with required information for the updater to work. One good example though is FreeCAD, saving you a lot in download size. To check if an AppImage contain update information, issue {{cmd|./thatprogram.AppImage --appimage-updateinformation}}; no output means no info.     {{Note|If the AppImage application does not work because it is missing dependencies, that is a fault in the AppImage, as it is supposed to be self-contained. An incomplete AppImage may work on some distributions, and not on others. So if you see that problem, tell the application AppImage creator so they can fix the AppImage.}} {{Note|If the AppImage application does not work because it is missing dependencies, that is a fault in the AppImage, as it is supposed to be self-contained. An incomplete AppImage may work on some distributions, and not on others. So if you see that problem, tell the application AppImage creator so they can fix the AppImage.}} Morgano

‎Alternative synchronisation clients

← Older revision Revision as of 22:02, 2 September 2025 (One intermediate revision by the same user not shown)Line 49: Line 49:  == In the file browser == == In the file browser ==    −* You have no marking on what files are synced (Contrary to i.e NextCloud.) ''(Dolphin on Mageia 9, June 2023.)''   * Right click a file and in the drop-down you see "Dropbox" which expand to an action menu: [[File:Dropbox_file_action_menu.png]] * Right click a file and in the drop-down you see "Dropbox" which expand to an action menu: [[File:Dropbox_file_action_menu.png]]  +* You have no marking on what files are synced.     == Removing Dropbox == == Removing Dropbox == Line 62: Line 62:     * We package {{prog|rclone}} for 64 and 32 bit. It can sync with many cloud storage services. https://rclone.org/dropbox/ * We package {{prog|rclone}} for 64 and 32 bit. It can sync with many cloud storage services. https://rclone.org/dropbox/  +* We package {{prog|seafile-client}} https://www.seafile.com  +* {{prog|Syncthing}} perform serverless cluster type continuous file synchronization, and can keep revisions. https://syncthing.net/ Very good. For many OS. Web interface. To install see [[File_transfer_with_Android_devices#Syncthing|here.]]  +* Nextcloud or Owncloud sync clients with Nextcloud/Owncloud servers. Not packaged. Morgano

add Jim Garrett, improve alphabetical order

← Older revision Revision as of 20:31, 2 September 2025 Line 55: Line 55:     User:ftg User:ftg  +  +User:ghibo  +  +User:Guygoye     User:hugomarc User:hugomarc Line 67: Line 71:     User:jeanroch User:jeanroch −  −User:ghibo  −  −User:Guygoye      User:JerareYoshi User:JerareYoshi     User:jibz User:jibz  +  +User:JimG     User:josh User:josh Marja

← Older revision Revision as of 06:54, 2 September 2025 (One intermediate revision by the same user not shown)Line 76: Line 76:  '''Lassen Sie die aktuellste nicht-backport Version von''' lib64bpf1, cpupower, kernel-userspace-headers installiert, und halten Sie diese aktuell.  ''- wir bieten keine Rückportierung von lib64bpf1 und cpupower an, um nicht die Kompatibilität mit Kernel, welche nicht aus dem Backport Repository sind, zu brechen.'' '''Lassen Sie die aktuellste nicht-backport Version von''' lib64bpf1, cpupower, kernel-userspace-headers installiert, und halten Sie diese aktuell.  ''- wir bieten keine Rückportierung von lib64bpf1 und cpupower an, um nicht die Kompatibilität mit Kernel, welche nicht aus dem Backport Repository sind, zu brechen.''    −'''Betreffend kernel-stable-userspace-headers''' gegen '''kernel-userspace-headers für Kernel 6.6:''' Diese Pakete werden benötigt um Anweundungen zu paketieren; verwenden Sie eins hierfür, um Pakete für Ihren aktuellen Kernel zum Bauen. Sie stehen untereinander in Konflikt und werden von urpmi & drakrpm richtig gehandhabt - wenn Sie die  '''mageia-repos und meta-task packages''' auf Version 9.4 aktualisiert haben (zum Zeitpunkt dieser Mitteilung unter update_testing) - und Verwendung von Kernel 6.6.103+ und 6.12..4+'''Betreffend kernel-stable-userspace-headers''' gegen '''kernel-userspace-headers für Kernel 6.6:''' Diese Pakete werden benötigt um Anwendungen zu paketieren; verwenden Sie eins hierfür, um Pakete für Ihren aktuellen Kernel zum Bauen. Sie stehen untereinander in Konflikt und werden von urpmi & drakrpm richtig gehandhabt - wenn Sie die  '''mageia-repos und meta-task packages''' auf Version 9.4 aktualisiert haben (zum Zeitpunkt dieser Mitteilung unter update_testing) - und Verwendung von Kernel 6.6.103+ und 6.12..4    −'''Remove-Old-Kernels''', {{prog|rok}}, kann werder den Kernel 6.12 erkennen, noch mit diesem umgehen, weshalb Sie nicht mehr benötigte Kernel händisch desintallieren müssen, um Speicherplatz zu sparen - genauso, wie Sie es mit den Kerneln getan haben, bevor rok in Mageia 9 eingeführt wurde. Oder Sie '''machen es nutzbar''', indem Sie in der Konfigurationsdatei {{file|/etc/remove-old-kernels.cfg}} etwas einfügen: Fügen Sie in der Liste unter der Zeile "LISTK=\" folgendes hinzu <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source+'''Remove-Old-Kernels''', {{prog|rok}}, kann werder den Kernel 6.12 erkennen, noch mit diesem umgehen, weshalb Sie nicht mehr benötigte Kernel händisch deintallieren müssen, um Speicherplatz zu sparen - genauso, wie Sie es mit den Kerneln getan haben, bevor rok in Mageia 9 eingeführt wurde. Oder Sie '''machen es nutzbar''', indem Sie in der Konfigurationsdatei {{file|/etc/remove-old-kernels.cfg}} etwas einfügen: Fügen Sie in der Liste unter der Zeile "LISTK=\" folgendes hinzu <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source     '''Falls VirtualBox ausgeführt wird''': Aktuell müssen Sie vor dem Starten des Gasts folgendes ausführen <br> '''Falls VirtualBox ausgeführt wird''': Aktuell müssen Sie vor dem Starten des Gasts folgendes ausführen <br> Line 88: Line 88:  In Cauldron sind die Kernelserien -mainline, -stable-testing, -stable und -lts verfügbar. Diese Serien sind (zumindest aktuell) nur für Cauldron gedacht und bieten die Gelegenheit neuere Hardware auszuprobieren, sowie die Pakete, die zur Erstellung stabiler Kernel benötigt werden, abzustimmen (zum Beispiel: neueres Rust, neueres LLVM, fehlende Bibliotheken, usw.). In Cauldron sind die Kernelserien -mainline, -stable-testing, -stable und -lts verfügbar. Diese Serien sind (zumindest aktuell) nur für Cauldron gedacht und bieten die Gelegenheit neuere Hardware auszuprobieren, sowie die Pakete, die zur Erstellung stabiler Kernel benötigt werden, abzustimmen (zum Beispiel: neueres Rust, neueres LLVM, fehlende Bibliotheken, usw.).    −Die -stable-testing (ehemals -stablenew) Serie ist (zumindes in der Theorie) die neuste stabile Kernelversion nach -mainline, ähnlich zu [https://www.kernel.org upstream], jedoch nicht eins zu eins, da es dort möglicherweise häufiger Änderungen gibt.+Die -stable-testing (ehemals -stablenew) Serie ist (zumindest in der Theorie) die neuste stabile Kernelversion nach -mainline, ähnlich zu [https://www.kernel.org upstream], jedoch nicht eins zu eins, da es dort möglicherweise häufiger Änderungen gibt.     Die -lts Serie ermöglicht auch das Testen der Kompatibilität mit der "vorherigen", zu letzt funktionierenden, LTS Serie, was in vielen Fällen nützlich sein kann, unter anderem bei proprietären Treibern (zum Beispiel NVIDIA), wenn diese nicht mehr mit neueren Kernel erstellt werden können oder um das Verhalten von älterer Hardware, im Vergleich zu neueren Kernel, zu prüfen. Die -lts Serie ermöglicht auch das Testen der Kompatibilität mit der "vorherigen", zu letzt funktionierenden, LTS Serie, was in vielen Fällen nützlich sein kann, unter anderem bei proprietären Treibern (zum Beispiel NVIDIA), wenn diese nicht mehr mit neueren Kernel erstellt werden können oder um das Verhalten von älterer Hardware, im Vergleich zu neueren Kernel, zu prüfen.     Beachten Sie, dass es nicht garantiert ist, dass alle Serien für alle Architekturen und Kernel-Arten verfügbar sind. Einige Serien sind möglicherweise auf einzelne Architekturen (zum Beispiel x86_64) und einzelne Arten (zum Beispiel desktop) beschränkt oder neuere Arten werden veröffentlicht (zum Beispiel desktop-tunedv3 für x86_64-v3). Beachten Sie, dass es nicht garantiert ist, dass alle Serien für alle Architekturen und Kernel-Arten verfügbar sind. Einige Serien sind möglicherweise auf einzelne Architekturen (zum Beispiel x86_64) und einzelne Arten (zum Beispiel desktop) beschränkt oder neuere Arten werden veröffentlicht (zum Beispiel desktop-tunedv3 für x86_64-v3).  +  +'''WARNUNG:''' Verwenden Sie nicht zu neue Kernel auf einem Produktivsystem, vor allem Kernel, welche sich noch in der RC (Release Candidate) Phase befinden. Falls Sie diese trotzdem zum testen verwenden möchten, behalten Sie die Linux Kernel Mailingliste im Auge und beachten Sie die hohe Wahrscheinlichkeit, dass Fehler vorhanden sein können, welche Datenverlust oder ähnliche schwere Probleme verursachen können.  +  +'''TIPP:''' Installieren Sie mehr als eine Serie, damit Sie eine Fallback-Möglichkeit zur Verfügung haben.     Als Beispiel, mit Stand vom 28. August 2025, boten wir folgende Kernel in Cauldron an: Als Beispiel, mit Stand vom 28. August 2025, boten wir folgende Kernel in Cauldron an: Psyca