Wiki de Mageia

‎rpm to deb: typo

← Older revision Revision as of 13:26, 14 May 2025 (One intermediate revision by the same user not shown)Line 1: Line 1: −{{introduction|{{prog|alien}} is a program that converts between Red Hat rpm, Debian deb, Stampede slp, Slackware tgz, and Solaris pkg file+{{introduction|{{prog|alien}} is a program that converts between Red Hat rpm, Debian deb, Stampede slp, Slackware tgz, and Solaris pkg file<br>formats. If you want to use a package from another linux distribution than the one you have installed on your system, you<br>can use alien to convert it to your preferred package format and install it. It also supports LSB packages.}} −      formats. If you want to use a package from another linux distribution than the one you have installed on your system, you  −      can use alien to convert it to your preferred package format and install it. It also supports LSB packages.}}      This page will cover how to troubleshoot conversions that not ends successful. This page will cover how to troubleshoot conversions that not ends successful. Line 12: Line 10:     == '''rpm to deb''' == == '''rpm to deb''' == −This was not working out of the box since mageia 8 times {{bug|28607}}, but now in mageia 9 and beyond with the updated packages we can at less provide a procedure that allows to perform the operation.+This was not working out of the box since mageia 8 times {{bug|28607}}, but now in mageia 9 and beyond with the updated packages we can at least provide a procedure that allows to perform the operation.     This conversion can fail like this This conversion can fail like this Psyca

‎2024: Create list for 2025

← Older revision Revision as of 11:22, 14 May 2025 Line 19: Line 19:  = Council members = = Council members =    −==2024==+==2025==    −Please update this list when the elections for your team are done!+Please update this list when the elections for your team are done! For now, the entries of 2024 have been copied to this list.   −IINM, only QA team (end of 2023) and i18n team (in 2023 and 2024) had elections, for all other teams just copying the entries of 2022.        Teams' representatives: Teams' representatives: Line 35: Line 34:  * [[Sysadmin_Team|Sysadmins]]: Pascal Vilarem (Maât) * [[Sysadmin_Team|Sysadmins]]: Pascal Vilarem (Maât)     +  +==2024==  +  +Teams' representatives:  +* [[Atelier_team|Atelier]]: Jose López (joselp), Filip Komar (filip)  +* [[Bug_Squad_Portal|Bug Squad]]: Lewis Smith (lewyssmith), Marja van Waes (marja)  +* [[Documentation team|Documentation]]: Yves Brungard (papoteur)  +* [[Forums team]]: Florian Hubold (doktor5000), Karel Roth (isadora), Pascal Vilarem (Maât  +* [[Internationalisation_Team_(i18n)|I18n]]: Yuri Chornoivan (yurchor), Filip Komar (filip)  +* [[Packagers]]: Nicolas Lécureuil (neoclust)  +* [[QA_Team|QA]]: Thomas J Andrews (TJ)  +* [[Packages_Security_Team|Security Team]]: David Walser (luigiwalser), Nicolas Salguero (ns80)  +* [[Sysadmin_Team|Sysadmins]]: Pascal Vilarem (Maât)     ==2022== ==2022== Marja

‎deb to rpm

← Older revision Revision as of 03:44, 14 May 2025 (One intermediate revision by the same user not shown)Line 93: Line 93:  {{code|mkdir -p BUILDROOT/schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.x86_64}} {{code|mkdir -p BUILDROOT/schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.x86_64}}    −Move the folder that not belong to rpm build '''(BUILD,BUILDROOT,SRPMS)''' to {{folder|BUILDROOT/schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.x86_64}}+Move the folder(s) that not belong to rpm build '''(BUILD,BUILDROOT,SRPMS)''' to {{folder|BUILDROOT/schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.x86_64}}     In this case, {{folder|opt}} and {{folder|usr}}. In this case, {{folder|opt}} and {{folder|usr}}.    −Return if needed to {{folder ~/tmp/schildichat-desktop-alpha-1.11.97~sc.0.test.0}}+Return if needed to {{folder|~/tmp/schildichat-desktop-alpha-1.11.97~sc.0.test.0}}     Run again Run again Katnatek

Created page with "{{introduction|{{prog|alien}} is a program that converts between Red Hat rpm, Debian deb, Stampede slp, Slackware tgz, and Solaris pkg file formats. If you want to use..."

New page

{{introduction|{{prog|alien}} is a program that converts between Red Hat rpm, Debian deb, Stampede slp, Slackware tgz, and Solaris pkg file
formats. If you want to use a package from another linux distribution than the one you have installed on your system, you
can use alien to convert it to your preferred package format and install it. It also supports LSB packages.}}

This page will cover how to troubleshoot conversions that not ends successful.

== Considerations ==
I will work from {{folder|~/tmp}} folder, in this place I store the .rpm and .deb files used in the examples.
You can work from other folder.

{{prog|fakeroot}} command before alien allows to use alien without root permissions.

== '''rpm to deb''' ==
This was not working out of the box since mageia 8 times {{bug|28607}}, but now in mageia 9 and beyond with the updated packages we can at less provide a procedure that allows to perform the operation.

This conversion can fail like this

{{output|fakeroot alien --to-deb mc-4.8.29-1.mga9.x86_64.rpm}}
{{withbr|<nowiki>Package build failed. Here's the log:
dh binary
dh_update_autotools_config
dh_autoreconf
create-stamp debian/debhelper-build-stamp
dh_testroot
dh_prep
debian/rules override_dh_auto_install
make[1]: Entering directory '/home/katnatek/tmp/mc-4.8.29'
mkdir -p debian/mc
# Copy the packages's files.
find . -maxdepth 1 -mindepth 1 -not -name debian -print0 | \
sed -e s#'./'##g | \
xargs -0 -r -i cp -a ./{} debian/mc/{}
make[1]: Leaving directory '/home/katnatek/tmp/mc-4.8.29'
dh_installdocs
dh_installchangelogs
dh_installman
dh_installman: error: mv debian/mc/usr/share/man/es/man1/mc.1.xz.dh-new debian/mc/usr/share/man/es/man1/mc.1.xz: No such file or directory
dh_installman: error: Aborting due to earlier error
make: *** [debian/rules:7: binary] Error 25</nowiki>}}{{Stop}}

'''Solution:''' <br />
{{output|fakeroot alien --to-deb mc-4.8.29-1.mga9.x86_64.rpm -s}}
{{withbr|<nowiki>Directory mc-4.8.29 prepared.</nowiki>}}{{Stop}}

Edit the file {{file|mc-4.8.29/debian/rules}}

Add this after the line 26: {{code|override_dh_installman:}} ,and save the change.

{{code|cd mc-4.8.29}}

{{code|fakeroot dh binary}}

At the end of the process, you will see something like this:
{{pre|<nowiki>dpkg-gencontrol: warning: Depends field of package mc: substitution variable ${shlibs:Depends} used, but is not defined
dpkg-gencontrol: warning: package mc: substitution variable ${perl:Depends} unused, but is defined
dh_md5sums
dh_builddeb
dpkg-deb: building package 'mc' in '../mc_4.8.29-2_amd64.deb'.</nowiki>}}

== '''deb to rpm''' ==

This procedure usually works out of the box like with this deb from debian:

{{code|fakeroot alien --to-rpm bash_5.2.15-2+b7_amd64.deb}}

But some deb files can fail.

{{output|fakeroot alien --to-rpm schildichat-desktop-alpha_1.11.97-sc.0.test.0_amd64.deb}}
{{withbr|<nowiki>Warning: Skipping conversion of scripts in package schildichat-desktop-alpha: postinst postrm
Warning: Use the --scripts parameter to include the scripts.
Package build failed. Here's the log of the command (cd schildichat-desktop-alpha-1.11.97~sc.0.test.0; rpmbuild --buildroot='/home/katnatek/tmp/schildichat-desktop-alpha-1.11.97~sc.0.test.0' -bb --target x86_64 'schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.spec'):
error: line 5: Empty tag: Summary:
Building target platforms: x86_64
Building for target x86_64</nowiki>}}{{Stop}}

'''Solution:''' <br />

{{output|fakeroot alien --to-rpm schildichat-desktop-alpha_1.11.97-sc.0.test.0_amd64.deb -s}}
{{withbr|<nowiki>Warning: Skipping conversion of scripts in package schildichat-desktop-alpha: postinst postrm
Warning: Use the --scripts parameter to include the scripts.
Directory schildichat-desktop-alpha-1.11.97~sc.0.test.0 prepared.</nowiki>}}{{Stop}}

{{code|cd schildichat-desktop-alpha-1.11.97~sc.0.test.0}}

Edit the spec file, put some information in summary, save the change.

{{code|<nowiki>rpmbuild -bb schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.spec --define "_topdir $(pwd)"</nowiki>}}

This will produce lot of errors like:

{{pre|File not found: /home/user/tmp/schildichat-desktop-alpha-1.11.97~sc.0.test.0/BUILDROOT/schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.x86_64/opt/SchildiChatAlpha/v8_context_snapshot.bin}}

{{code|mkdir -p BUILDROOT/schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.x86_64}}

Move the folder that not belong to rpm build '''(BUILD,BUILDROOT,SRPMS)''' to {{folder|BUILDROOT/schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.x86_64}}

In this case, {{folder|opt}} and {{folder|usr}}.

Return if needed to {{folder ~/tmp/schildichat-desktop-alpha-1.11.97~sc.0.test.0}}

Run again

{{code|<nowiki>rpmbuild -bb schildichat-desktop-alpha-1.11.97~sc.0.test.0-2.spec --define "_topdir $(pwd)"</nowiki>}}

{{note|The deb to rpm case as you see is the complex to fix by hand as we have to learn and adapt the steps for each conversion.
The key is the folder BUILDROOT and the string between the first next "/" and the second "/".}} Katnatek

‎How to enforce version freeze: Fix path

← Older revision Revision as of 08:11, 9 May 2025 Line 2: Line 2:     * take a checkout of puppet configuration * take a checkout of puppet configuration −* go to ''modules/buildsystem/templates''+* edit ''deployment/mga_buildsystem/manifests/config.pp'' −* edit ''submit-todo.conf''     −in ''checks/version/cauldron'' ( yaml hierarchy )+in the ''$cauldron_version_check'' object     * change mode from   * change mode from   −  mode: normal+  'mode' => 'normal'  to   to   −  mode: version_freeze+  'mode' => 'version_freeze'     * commit and push * commit and push Line 18: Line 17:  A Release Freeze is done similarly, but with A Release Freeze is done similarly, but with    −  mode: freeze+  'mode' => 'freeze'     == How to add someone to the list of users able to upload == == How to add someone to the list of users able to upload == Danf

‎See Also: Add Trustify

← Older revision Revision as of 09:12, 7 May 2025 Line 125: Line 125:  * [https://vuln.go.dev/ Go Vulnerability Database] * [https://vuln.go.dev/ Go Vulnerability Database]  * [https://guac.sh/ GUAC] SBOM management tool * [https://guac.sh/ GUAC] SBOM management tool  +* [https://github.com/trustification/trustify Trustify] SBOM management tool  * [https://github.com/anchore/grype grype], tool that can look up security issues from a SPDX SBOM * [https://github.com/anchore/grype grype], tool that can look up security issues from a SPDX SBOM  * [https://trivy.dev/ Trivy], tool that can look up security issues from a SPDX SBOM * [https://trivy.dev/ Trivy], tool that can look up security issues from a SPDX SBOM     [[Category:Packaging]] [[Category:Packaging]] Danf

← Older revision Revision as of 14:47, 30 April 2025 Line 402: Line 402:  {{Bug|31623}} - '''hp-toolbox kann nicht den installierten HP Drucker verwenden''', wenn das lpp-usb Paket installiert ist. Problem: Einige Drucker benötigen lpp-usb. '''Workaround''': Wählen Sie, ob lpp-usb für Ihren Drucker installiert werden soll oder nicht. Frische Installationen mit dem klassischen Installer haben dieses Paket nicht vorinstalliert, solange die Online-Repositorien während der Installation nicht verwendet werden. Die Live-Medien haben lpp-usb vorinstalliert. {{Bug|31623}} - '''hp-toolbox kann nicht den installierten HP Drucker verwenden''', wenn das lpp-usb Paket installiert ist. Problem: Einige Drucker benötigen lpp-usb. '''Workaround''': Wählen Sie, ob lpp-usb für Ihren Drucker installiert werden soll oder nicht. Frische Installationen mit dem klassischen Installer haben dieses Paket nicht vorinstalliert, solange die Online-Repositorien während der Installation nicht verwendet werden. Die Live-Medien haben lpp-usb vorinstalliert.    −{{Bug|32198}} - Es wird eine '''leere PDF''' durch den virtuellen Drucker '''cups-pdf''' mit der Version 3.0.1-3.mga9 ausgegeben. Mögliche '''Workarounds:''' Viele Programme können direkt zu PDF Dateien exportieren. Manchmal durch einen Menüeintrag wie  "Datei > Exportieren" (z. B. LibreOffice). Bei einigen Anwendungen wird der PDF Export als Auswahl im Druckdialog angezeigt, wie wenn man einen regulären Drucker auswählt ist dort auch ggf. CUPS-PDF aufgelistet - auch als "Speichern als PDF", "Drucken als PDF" oder etwas ähnliches benannt (Okular, Firefox, Thunderbird, Chromium, ...)+'''BEHOBEN durch eine Aktualisierung:''' {{Bug|32198}} - Es wird eine '''leere PDF''' durch den virtuellen Drucker '''cups-pdf''' mit der Version 3.0.1-3.mga9 ausgegeben. Mögliche '''Alternativen:''' Viele Programme können direkt zu PDF Dateien exportieren. Manchmal durch einen Menüeintrag wie  "Datei > Exportieren" (z. B. LibreOffice). Bei einigen Anwendungen wird der PDF Export als Auswahl im Druckdialog angezeigt, wie wenn man einen regulären Drucker auswählt ist dort auch ggf. CUPS-PDF aufgelistet - auch als "Speichern als PDF", "Drucken als PDF" oder etwas ähnliches benannt (Okular, Firefox, Thunderbird, Chromium, ...), [https://bugs.mageia.org/show_bug.cgi?id=32198#c16 cups-brf] (falls Sie die ausgegebene Datei von .brf zu .pdf umbenennen möchten.     {{Bug|32266}} - Nach dem '''Upgrade von Mageia 8 funktionieren möglicherweise über USB angeschlossene Drucker nicht mehr''' und diese können manuell nicht erneut installiert werden. '''Manuelle Behebung:''' Erzwingen Sie die Entfernung des Druckers als root durch Ausführen des Befehls {{cmd|<nowiki>lpadmin -x <printername></nowiki>}} und installieren Sie danach den Drucker wie gewöhnlich - Sie finden diesen möglicherweise unter den Netzwerkdruckern aufgrund von ipp-usb.service. {{Bug|32266}} - Nach dem '''Upgrade von Mageia 8 funktionieren möglicherweise über USB angeschlossene Drucker nicht mehr''' und diese können manuell nicht erneut installiert werden. '''Manuelle Behebung:''' Erzwingen Sie die Entfernung des Druckers als root durch Ausführen des Befehls {{cmd|<nowiki>lpadmin -x <printername></nowiki>}} und installieren Sie danach den Drucker wie gewöhnlich - Sie finden diesen möglicherweise unter den Netzwerkdruckern aufgrund von ipp-usb.service. Line 409: Line 409:     ==== Boomaga virtueller Drucker ==== ==== Boomaga virtueller Drucker ==== −{{bug|31980}} - Funktioniert manchmal nicht. Es benötigt eine Aktualisierung im upstream, aber die Entwicklung ist seit jahren ins Stocken geraten. Seien Sie glücklich, wenn es funktioniert, was meistens der Fall ist :)  '''Workaround:''' Ein Neustart des Systems hat hierbei Auswirkungen.+{{bug|31859}} Boomaga stürzt bei einigen Anwendungen manchmal ab wenn mit dem virtuellen Drucker gedruckt wird, vor allem Okular. Alternative '''Workarounds:''' 1) Versuchen Sie es erneut, 2) Starten Sie Boomaga, bevor Sie drucken, 3) Verwenden Sie eine andere Anwendung mit Boomaga.    −{{bug|31859}} Boomaga stürzt bei einigen Anwendungen manchmal ab wenn mit dem virtuellen Drucker gedruckt wird, vor allem Okular. Alternative '''Workarounds:''' 1) Versuchen Sie es erneut, 2) Starten Sie Boomaga, bevor Sie drucken, 3) Verwenden Sie eine andere Anwendung mit Boomaga.+{{bug|31980}} - Funktioniert manchmal nicht. Es benötigt eine Aktualisierung im upstream, aber die Entwicklung ist seit Jahren ins Stocken geraten. Seien Sie glücklich, wenn es funktioniert, was meistens der Fall ist :)  '''Workaround:''' Ein Neustart des Systems hat hierbei Auswirkungen. Es scheint, als wäre es auf einigen Systemen seit Frühling 2025 schlimmer geworden, funktioniert jedoch bei auf anderen.     ==== Drucker wird doppelt angezeigt - kein Fehler ==== ==== Drucker wird doppelt angezeigt - kein Fehler ==== Psyca

‎Boomaga virtual printer: Removed duplicate #31980 entry. And it do work on some systems still.

← Older revision Revision as of 13:30, 30 April 2025 Line 518: Line 518:     ==== Boomaga virtual printer ==== ==== Boomaga virtual printer ==== −  −{{bug|31980}} - Sometimes not working at all. Really need upstream update, but is stalled since years.  When it works, which it most often do, be happy :)  '''Workaround:''' System reboot is known to have effect.      {{bug|31859}} - Boomaga sometimes crash when printing to it from some applications, notably Okular. Alternative '''Workarounds: 1.)''' Just try again, '''2.)''' Launch Boomaga first, '''3.)''' Use another application with Boomaga. {{bug|31859}} - Boomaga sometimes crash when printing to it from some applications, notably Okular. Alternative '''Workarounds: 1.)''' Just try again, '''2.)''' Launch Boomaga first, '''3.)''' Use another application with Boomaga.    −{{bug|31980}} - Boomaga not works since the last updates.+{{bug|31980}} - Sometimes not working at all. Really need upstream update, but is stalled since years.  When it works, which it most often do, be happy :)  '''Workaround:''' System reboot is known to have effect.  Seems to have got worse on some systems in spring 2025, but still works on other.     ==== Printer duplicate - not a bug ==== ==== Printer duplicate - not a bug ==== Morgano

‎Boomaga virtual printer: other bug

← Older revision Revision as of 02:23, 30 April 2025 (One intermediate revision by the same user not shown)Line 511: Line 511:  {{Bug|31623}} - '''hp-toolbox can't use the installed HP printer''' if the ipp-usb package is installed.  Problem: some printers need ipp-usb.  '''Workaround''': Choose if you want ipp-usb or not installed for your printer. Fresh installs from Classic installer do not have this package installed unless on-line repositories have been used during installation.  Live media have ipp-usb installed. {{Bug|31623}} - '''hp-toolbox can't use the installed HP printer''' if the ipp-usb package is installed.  Problem: some printers need ipp-usb.  '''Workaround''': Choose if you want ipp-usb or not installed for your printer. Fresh installs from Classic installer do not have this package installed unless on-line repositories have been used during installation.  Live media have ipp-usb installed.    −{{Bug|32198}} - '''Blank pdf''' output from the virtual printer '''cups-pdf''' version 3.0.1-3.mga9.  Fix is in progress.  Possible '''Workarounds:''' Many programs can export pdf directly. Sometimes by a menu entry like "File > Export" (i.e LibreOffice). In some programs the pdf export is a choice in the print dialogue, like choosing any printer and where also CUPS-PDF is listed, named as "Save to pdf", "Print to pdf" or similar. (Okular, Firefox, Thunderbird, Chromium ...)+'''FIXED by Update:''' {{Bug|32198}} - '''Blank pdf''' output from the virtual printer '''cups-pdf''' version 3.0.1-3.mga9.  Possible '''Alternatives:''' Many programs can export pdf directly. Sometimes by a menu entry like "File > Export" (i.e LibreOffice). In some programs the pdf export is a choice in the print dialogue, like choosing any printer and where also CUPS-PDF is listed, named as "Save to pdf", "Print to pdf" or similar. (Okular, Firefox, Thunderbird, Chromium ...), [https://bugs.mageia.org/show_bug.cgi?id=32198#c16 cups-brf] (if you like rename the output file from .brf to .pdf).     {{Bug|32266}} - After '''upgrading from Mageia 8, USB-connected printers may not work''' and it can not be reinstalled manually. '''Manual Fix:''' Remove the printer forcibly by as root execute {{cmd|<nowiki>lpadmin -x <printername></nowiki>}}, then install the printer as usual - you may find it listed under Network Printers due to ipp-usb.service. {{Bug|32266}} - After '''upgrading from Mageia 8, USB-connected printers may not work''' and it can not be reinstalled manually. '''Manual Fix:''' Remove the printer forcibly by as root execute {{cmd|<nowiki>lpadmin -x <printername></nowiki>}}, then install the printer as usual - you may find it listed under Network Printers due to ipp-usb.service. Line 522: Line 522:     {{bug|31859}} - Boomaga sometimes crash when printing to it from some applications, notably Okular. Alternative '''Workarounds: 1.)''' Just try again, '''2.)''' Launch Boomaga first, '''3.)''' Use another application with Boomaga. {{bug|31859}} - Boomaga sometimes crash when printing to it from some applications, notably Okular. Alternative '''Workarounds: 1.)''' Just try again, '''2.)''' Launch Boomaga first, '''3.)''' Use another application with Boomaga.  +  +{{bug|31980}} - Boomaga not works since the last updates.     ==== Printer duplicate - not a bug ==== ==== Printer duplicate - not a bug ==== Katnatek

← Older revision Revision as of 06:02, 29 April 2025 Line 129: Line 129:     <pre># rpm -e --nodeps <package></pre> <pre># rpm -e --nodeps <package></pre>  +  +== Alles von den Testing-Repositorien herunterstufen ==  +Um Ihr System mit den Release- und Updates-Repositorien zu synchronisieren, damit dieses nur noch die Pakete von dort enthält.  +  +# Lesen Sie die hierzu [[Verwenden_von_DNF-de#Synchronisieren_mit_den_Repositorien|den Abschnitt zur Verwendung von DNF]].  +  +# {{cmd|<nowiki>dnf offline-distrosync download --disablerepo=\*testing\* --allowerasing</nowiki>}}     == Perl Module == == Perl Module == Psyca

← Older revision Revision as of 05:56, 29 April 2025 Line 48: Line 48:     "modesetting" mit Nvidia Karten, welches stabiler läuft, verwendet auch das interne nouveau Kernel-Modul für 3D. "nouveau" in Xorg verwendet den nouveau Xorg DDX Treiber, sowie das nouveau Kernel-Modul. Für viele aktuelle Nvidia-Grafikkarten kann der nouveau DDX Treiber nicht verwendet werden, da diese nicht unterstützt werden (zum Beispiel für Nvidia RTX 3xxx und neuer). "modesetting" mit Nvidia Karten, welches stabiler läuft, verwendet auch das interne nouveau Kernel-Modul für 3D. "nouveau" in Xorg verwendet den nouveau Xorg DDX Treiber, sowie das nouveau Kernel-Modul. Für viele aktuelle Nvidia-Grafikkarten kann der nouveau DDX Treiber nicht verwendet werden, da diese nicht unterstützt werden (zum Beispiel für Nvidia RTX 3xxx und neuer).  +  +== nouveau Probleme ==  +=== Fehlende Firmware ===  +Sie finden in den Systemereignissen gegebenenfalls eine Zeile wie  +  +''kernel: nouveau 0000:01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2''  +  +Die Firmware ist dazu da, die Videodekodierung zu beschleunigen und sorgt eventuell für ein stabileres System. Falls Sie keine Probleme feststellen, müssen Sie sich darum nicht stören.  +  +Fehlende Firmware liegt möglicherweise daran, dass die Firmware in diesem Fall weder in kernel-firmware, noch in kernel-firmware-nonfree Paketen vorhanden ist. kernel-firmware wird grundsätzlich installiert und falls Sie kernel-firmware-nonfree nicht installiert haben versuchen Sie diese zu installieren und starten Sie das System neu. Falls Sie weiterhin Probleme feststellen können Sie möglicherweise die benötigte Firmware aus einem Nvidia Treiber extrahieren. Sie finden Informationen, wie Sie dies tun können, indem Sie nach "Direct+firmware+load+for+nouveau"+"failed+with+error+-2" suchen. Die Anwendung können Sie unter https://github.com/envytools/firmware finden. Laden Sie sich den Treiber zum extrahieren von https://www.nvidia.com/en-us/drivers/.  +  +{{fixme|81}} ''Jemand kann dies unter Mageia ausprobieren und hier dokumentieren.''     == Proprietärer AMD Treiber == == Proprietärer AMD Treiber == Line 225: Line 237:    urpmi nvidia470-all   urpmi nvidia470-all    −== icd erzwingen ==+== Hinweise ==  +=== icd erzwingen ===  ''Aus [https://forums.mageia.org/en/viewtopic.php?t=14308 forum], [https://forums.mageia.org/en/viewtopic.php?f=15&t=14946&p=87756#p87756 forum], und {{bug|29563}}'' ''Aus [https://forums.mageia.org/en/viewtopic.php?t=14308 forum], [https://forums.mageia.org/en/viewtopic.php?f=15&t=14946&p=87756#p87756 forum], und {{bug|29563}}''    Line 239: Line 252:  '''Bei Intel''' '''Bei Intel'''    export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json   export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json  +  +=== Beschleunigung ===  +Vergewissern Sie sich händisch, dass Sie den richtigen vdpau Treiber installiert haben. {{Bug|34228}}     == Gamemode == == Gamemode == Line 246: Line 262:  Verwendung: {{cmd|gamemoderun <anwendung>}} Verwendung: {{cmd|gamemoderun <anwendung>}}    −Siehe: [https://github.com/FeralInteractive/gamemode Github]  +Weitere Einzelheiten: [https://github.com/FeralInteractive/gamemode Github]    −== Hybride Grafikkarten ==+=== Hybride Grafikkarten ===  Einige Laptops kommen mit "Hybriden Grafikkarten", dies bedeutet sie haben zwei GPUs: eine mit wenig Stromverbrauch und eine schnelle. Einige Laptops kommen mit "Hybriden Grafikkarten", dies bedeutet sie haben zwei GPUs: eine mit wenig Stromverbrauch und eine schnelle.     Bezüglich der Einrichtung schauen Sie unter [[Bumblebee]] und [[Mageia-prime_for_Optimus|Mageia-prime for Optimus]] Bezüglich der Einrichtung schauen Sie unter [[Bumblebee]] und [[Mageia-prime_for_Optimus|Mageia-prime for Optimus]]    −== Protokolle ==+=== Protokolle ===  * Das Journal des Systems kann mit dem Befehl {{cmd|journalctl}} angezeigt werden. * Das Journal des Systems kann mit dem Befehl {{cmd|journalctl}} angezeigt werden.  * Das Xorg Protokoll kann zum Beispiel über {cmd|less /var/log/Xorg.0.log}} angezeigt werden - Beachten Sie jedoch, ''wenn GDM verwendet wird'', befindet sich das Protokoll unter {{file|$HOME/.local/share/xorg/Xorg.0.log}} und dessen Inhalt wird auch in das Journal geschrieben. * Das Xorg Protokoll kann zum Beispiel über {cmd|less /var/log/Xorg.0.log}} angezeigt werden - Beachten Sie jedoch, ''wenn GDM verwendet wird'', befindet sich das Protokoll unter {{file|$HOME/.local/share/xorg/Xorg.0.log}} und dessen Inhalt wird auch in das Journal geschrieben. Line 259: Line 275:  Beachten Sie, ''wenn Sie modesettings verwenden, wird weiterhin der Name des Kernel-Treibers protokolliert'', zum Beispiel "nouveau" bei Nvidia, da modesetting der X11 (a.k.a. DDX) Treiber ist, welcher über einem Kernel-Gerätetreiber sitzt. Beachten Sie, ''wenn Sie modesettings verwenden, wird weiterhin der Name des Kernel-Treibers protokolliert'', zum Beispiel "nouveau" bei Nvidia, da modesetting der X11 (a.k.a. DDX) Treiber ist, welcher über einem Kernel-Gerätetreiber sitzt.    −== Unterdrücken nerviger Mitteilungen im Terminal und den Protokollen ==+=== Unterdrücken nerviger Mitteilungen im Terminal und den Protokollen ===  Manchmal finden Sie eine ungünstige Anzahl an Firewall Meldungen, welche das dmesg/Journal "verwässern" und diese werden auch im Terminal oder sogar z. B. in Textmodus Anwendungen wie drakx tools in der Konsole angezeigt - sehr störend! Manchmal finden Sie eine ungünstige Anzahl an Firewall Meldungen, welche das dmesg/Journal "verwässern" und diese werden auch im Terminal oder sogar z. B. in Textmodus Anwendungen wie drakx tools in der Konsole angezeigt - sehr störend!    Psyca

← Older revision Revision as of 09:38, 28 April 2025 Line 1: Line 1:  +[[QA Team Portal|Returm to the QA Team Portal]]  {{multi_language_banner|[[QA Tipps und Tricks-de|Deutsch]]; [[QA_Tips_and_Tricks|English]]; [[Trucs et Astuces AQ-fr|français]]; [[QA Tips en Trucs-nl|Nederlands]] ;}} {{multi_language_banner|[[QA Tipps und Tricks-de|Deutsch]]; [[QA_Tips_and_Tricks|English]]; [[Trucs et Astuces AQ-fr|français]]; [[QA Tips en Trucs-nl|Nederlands]] ;}}    Line 116: Line 117:     <pre># rpm -e --nodeps <package></pre> <pre># rpm -e --nodeps <package></pre>  +  +==Downgrade alles vanuit testing repositories ==  +  +Om uw systeem zodanig te synchroniseren, dat het alleen pakketten en versies bevat van de release en update repositories.  +# Lees over [[Using_DNF#Synchronize_with_repos|this usage of DNF]].  +# {{cmd|<nowiki>dnf offline-distrosync download --disablerepo=\*testing\* --allowerasing</nowiki>}}     == Perl-modules == == Perl-modules == Marchugo

+ Downgrade everything from testing repos

← Older revision Revision as of 02:51, 28 April 2025 Line 1: Line 1:  +[[QA Team portal|Return to the QA Team portal]]  +[[Category:Contributors]][[Category:QA]]  +  {{multi_language_banner|[[QA Tipps und Tricks-de|Deutsch]] ; [[QA_Tips_and_Tricks|English]] ; [[Trucs et Astuces AQ-fr|français]] ; [[QA Tips en Trucs-nl|Nederlands]] ; }} {{multi_language_banner|[[QA Tipps und Tricks-de|Deutsch]] ; [[QA_Tips_and_Tricks|English]] ; [[Trucs et Astuces AQ-fr|français]] ; [[QA Tips en Trucs-nl|Nederlands]] ; }}    Line 139: Line 142:     <pre># rpm -e --nodeps <package></pre> <pre># rpm -e --nodeps <package></pre>  +  +== Downgrade everything from testing repos ==  +  +To synchronise your system to only contain packages and versions from release and updates repositories.  +# Read about [[Using_DNF#Synchronize_with_repos|this usage of DNF]].  +# {{cmd|<nowiki>dnf offline-distrosync download --disablerepo=\*testing\* --allowerasing</nowiki>}}     == Perl Modules == == Perl Modules == Line 204: Line 213:  firefox    8801  8841    user  mem    REG    8,2  707048    137291 /usr/lib64/libpixman-1.so.0.32.8 firefox    8801  8841    user  mem    REG    8,2  707048    137291 /usr/lib64/libpixman-1.so.0.32.8  </pre> </pre> −  −  −  −[[QA Team portal|Return to the QA Team portal]]  −[[Category:Contributors]][[Category:QA]]  Morgano

+ Notes, + Acceleration

← Older revision Revision as of 02:20, 28 April 2025 (2 intermediate revisions by the same user not shown)Line 59: Line 59:     "modesetting" with Nvidia cards, though more stable, uses internally kernel's nouveau module too for 3D. "nouveau" in Xorg uses nouveau Xorg DDX driver plus kernel's nouveau module. For many recent NV cards the nouveau DDX can't even be used because they are unsupported (e.g. for NV RTX 3xxx and beyond, etc.). "modesetting" with Nvidia cards, though more stable, uses internally kernel's nouveau module too for 3D. "nouveau" in Xorg uses nouveau Xorg DDX driver plus kernel's nouveau module. For many recent NV cards the nouveau DDX can't even be used because they are unsupported (e.g. for NV RTX 3xxx and beyond, etc.).  +  +<br>  +  +== nouveau problems ==  +  +=== Missing firmware ===  +You may find in system journal a line like  +  +''kernel: nouveau 0000:01:00.0: Direct firmware load for nouveau/nva8_fuc084 failed with error -2''  +   +The firmware is to speed up video decoding, and may help with stability generally.  If you experience no problem you do not need to bother.  +   +Missing firmware may be due to that the firmware in case is not included in neither the kernel-firmware nor kernel-firmware-nonfree packages.  kernel-firmware is installed by default, and if you do not have kernel-firmware-nonfree, try installing that and reboot.  If you still see the problem, you may by able to extract the needed firmware from a nvidia driver.  You will find how to do that by doing a web search on "Direct+firmware+load+for+nouveau"+"failed+with+error+-2", the tool is found at https://github.com/envytools/firmware.  Get driver to extract from at https://www.nvidia.com/en-us/drivers/.  +  +{{fixme|81}} ''Someone try on Mageia and document it here.''     <br> <br> Line 279: Line 294:  <br> <br>    −== Forcing icd ==+== Notes ==  +   +=== Forcing icd ===     ''From [https://forums.mageia.org/en/viewtopic.php?t=14308 forum], [https://forums.mageia.org/en/viewtopic.php?f=15&t=14946&p=87756#p87756 forum], and {{bug|29563}}'' ''From [https://forums.mageia.org/en/viewtopic.php?t=14308 forum], [https://forums.mageia.org/en/viewtopic.php?f=15&t=14946&p=87756#p87756 forum], and {{bug|29563}}'' Line 297: Line 314:  <br> <br>    −== Gamemode ==+=== Acceleration ===  +   +Manually make sure you have a correct vdpau driver.  {{Bug|34228}}  +   +<br>  +   +=== Gamemode ===     Installing the package gamemode, you can launch games and similar applications so they are executed under various speed optimisations. Installing the package gamemode, you can launch games and similar applications so they are executed under various speed optimisations. Line 303: Line 326:  you are running on batteries). you are running on batteries).    −Usage: {{cmd|gamemoderun <application>}}+Usage: {{cmd|gamemoderun <application>}}, Details see: [https://github.com/FeralInteractive/gamemode Github]   −   −See: [https://github.com/FeralInteractive/gamemode Github]        <!-- update and questions in https://bugs.mageia.org/show_bug.cgi?id=33696 --> <!-- update and questions in https://bugs.mageia.org/show_bug.cgi?id=33696 --> Line 311: Line 332:  <br> <br>    −== Hybrid Graphics ==+=== Hybrid Graphics ===     Some laptops comes with "Hybrid Graphics", meaning they have two GPU: one low power, and the other faster.   Some laptops comes with "Hybrid Graphics", meaning they have two GPU: one low power, and the other faster.   Line 319: Line 340:  <br> <br>    −== Logs ==+=== Logs ===     * The system journal, viewed by the command {{cmd|journalctl}} * The system journal, viewed by the command {{cmd|journalctl}} Line 328: Line 349:  <br> <br>    −== Suppress disturbing messages in terminal and logs ==+=== Suppress disturbing messages in terminal and logs ===     Sometimes you find inconvenient number of firewall messages "diluting" dmesg/journal, and they also are output in terminals and even right into i.e text mode applications such as drakx tools in console mode - very disturbing! Sometimes you find inconvenient number of firewall messages "diluting" dmesg/journal, and they also are output in terminals and even right into i.e text mode applications such as drakx tools in console mode - very disturbing! Morgano

Link to gcc porting notes

← Older revision Revision as of 01:17, 26 April 2025 (One intermediate revision by the same user not shown)Line 49: Line 49:     '''Solution''': Patch the source to #include the right standard header file. It's probably an obvious one like #include <stdlib.h> or #include <string.h>. '''Solution''': Patch the source to #include the right standard header file. It's probably an obvious one like #include <stdlib.h> or #include <string.h>.  +  +Added for mga10.  +  +== incompatibleptr ==  +  +'''Problem''': A function is being passed in a value that doesn't match the type in the function prototype.  +  +'''Solution''': If it is a function pointer being called that does not have a full prototype, [https://gcc.gnu.org/gcc-15/porting_to.html#c23 gcc >= 15] assumes arguments are int, whereas previous versions did not check the type of arguments in this case. If lacking a full prototype is the problem and there is no function prototype, add one in an appropriate .h file (or make the partial prototype complete). If compiling a library, make sure that a new prototype doesn't affect backwards compatibility with older applications using the library. If it's not possible to add a prototype, you can add the ''-std=gnu17'' compiler option (e.g. by appending to ''CFLAGS'' before the build step) to revert to the old behaviour (but don't do this to fix a library because it means that all applications using the library will also need to add the flag). If there ''is'' a prototype but it does not match the number of arguments passed in, then it is a compatibility break, likely with some dependent library, and the application will need to be patched to use the correct arguments.     Added for mga10. Added for mga10. Line 139: Line 147:     '''More info''': https://gcc.gnu.org/gcc-14/porting_to.html '''More info''': https://gcc.gnu.org/gcc-14/porting_to.html  +  +Added for mga10.  +  +== toomanyargs ==  +  +'''Problem''': A function is being called that takes more arguments than are being given.  +  +'''Solution''': If the function does not have a prototype, [https://gcc.gnu.org/gcc-15/porting_to.html#c23 gcc >= 15] assumes it takes 0 arguments, whereas previous versions did not check the number of arguments in this case. If lacking a prototype is the problem and there is no function prototype, add one in an appropriate .h file. If compiling a library, make sure that a new prototype doesn't affect backwards compatibility with older applications using the library. If it's not possible to add a prototype, you can add the ''-std=gnu17'' compiler option (e.g. by appending to ''CFLAGS'' before the build step) to revert to the old behaviour (but don't do this to fix a library because it means that all applications using the library will also need to add the flag). If there ''is'' a prototype but it does not match the number of arguments passed in, then it is a compatibility break, likely with some dependent library, and the application will need to be patched to use the correct arguments.     Added for mga10. Added for mga10. Danf

Update, clearly push for using upstream Appimage for now

← Older revision Revision as of 09:59, 22 April 2025 Line 8: Line 8:  <br> <br>    −== Mageia packages ==+== Mageia packaging ==  +   +=== Mageia problem ===  +   +Currently beginning December 2024 we have problems updating it ({{Bug|33697}}).  +# It do not compile on Mageia 9 due to that the Qt6 stack need be updated first, which may not happen.  +# We have no maintainer for it.  +   +So for now use [[#Using_upstream_official_AppImage|upstream official AppImage]]!  +   +=== Mageia packages ===  +''Kept for reference, if we supply packages for Mageia 10 or later.''     Basic: Basic: Line 20: Line 31:       nextcloud-client-nemo-3.13.4-1.mga9.x86_64.rpm      nextcloud-client-nemo-3.13.4-1.mga9.x86_64.rpm    −== Usage ==+=== Usage ===     You start it first time by launching {{prog|nextcloud}}. In its settings there is a check box that makes it autostart when you log in to desktop. You start it first time by launching {{prog|nextcloud}}. In its settings there is a check box that makes it autostart when you log in to desktop.     It lives in system tray. Use right and left mouse click to launch menus. It lives in system tray. Use right and left mouse click to launch menus. −  −[https://docs.nextcloud.com/desktop/latest/ See manual.]      <br> <br> −== Mageia problem ==     −Currently December 2024 we have problems updating it ({{Bug|33697}}).  −# It do not compile on Mageia 9 due to that the Qt6 stack need be updated first, which may not happen.  −# We have no maintainer for it.      == Using upstream official AppImage == == Using upstream official AppImage == Line 58: Line 63:  1. Go to https://nextcloud.com/install/ 1. Go to https://nextcloud.com/install/    −2. Click "DOWNLOAD FOR DESKTOP" -> get "Linux AppImage"+2. In section "Download for desktop", click "Nextcloud Files", then "Linux AppImage".     3. Move it where you want it to live. 3. Move it where you want it to live. Line 69: Line 74:     === Update upstream Appimage === === Update upstream Appimage === −   Easiest way to see if an update is available is in its settings, tab "General": at bottom there is a button to check, and a checkbox to make it check automatically and tell. Easiest way to see if an update is available is in its settings, tab "General": at bottom there is a button to check, and a checkbox to make it check automatically and tell.    Line 76: Line 80:  1. Close it if it is running (right click the system tray icon) 1. Close it if it is running (right click the system tray icon)    −2. Delete the appimage file.+2. Delete the appimage file. (or rename it)     3. Install and start it exactly as described above for new install. 3. Install and start it exactly as described above for new install.     +''Updating automatically, I have not tested. Maybe see our AppImage wiki page for update helpers.''  +  +== Documentation ==    −''Updating automatically, I have not tested. Maybe see our AppImage wiki page for update helpers.''+[https://docs.nextcloud.com/desktop/latest/ Manual] Morgano

buildrequires

← Older revision Revision as of 11:57, 18 April 2025 (One intermediate revision by the same user not shown)Line 43: Line 43:     == Writing the spec-File == == Writing the spec-File ==  +  +We use now ''pyproject'' macros. [https://src.fedoraproject.org/rpms/pyproject-rpm-macros They are documented] by Fedora.     === Tags === === Tags === Line 69: Line 71:    %pyproject_buildrequires   %pyproject_buildrequires    −The directive ''%pyproject_buildrequires'' can take arguments like ''-t'' to include requirements for tests using ''tox''.+The directive <code>%pyproject_buildrequires</code> can take arguments like ''-t'' to include requirements for tests using ''tox''. Other options are available according to how the package is provided, to include requirements for tests. See the [https://src.fedoraproject.org/rpms/pyproject-rpm-macros documentation].     === Requires === === Requires ===    −* Please do not specify <code>python3</code> as a requirement for your package. It will be added automatically in the correct way.+* Please do not specify <code>python3</code> as a requirement for your package. It will be added automatically in the correct way when <code>%pyproject_buildrequires</code> is used. −* The <code>%py_requires</code> macro is no longer needed and has been removed.+   +We automatically relax some versioning in requirements, but sometimes, it will be needed to patch the requirements to avoid rich dependencies.     Sometimes we need to exclude modules from autorequires  : Sometimes we need to exclude modules from autorequires  : Papoteur

← Older revision Revision as of 21:34, 16 April 2025 Line 107: Line 107:     dies speichert die Ausgabe in die Datei '''logfile.txt'''. Bist du fertig, so enthält die Ausgabedatei eine Aufzeichnung deiner '''gdb''' Sitzung. dies speichert die Ausgabe in die Datei '''logfile.txt'''. Bist du fertig, so enthält die Ausgabedatei eine Aufzeichnung deiner '''gdb''' Sitzung.  +  +=== LibreOffice debuggen ===  +Die grundsätzlichen Befehle um libreoffice zu starten sind bash Scripte, welche mit gdb nicht erlaubt sind.  +  +Jedoch wird eine spezielle Befehlsoption angeboten:  +{{cmd|libreoffice --backtrace}}  +  +Diese startet eine gdb Sitzung.     === Apache debuggen in Mageia 2 === === Apache debuggen in Mageia 2 === Psyca

‎Debugging Libreoffice

← Older revision Revision as of 14:00, 14 April 2025 (One intermediate revision by the same user not shown)Line 104: Line 104:     This will save all the output to that logfile.txt. When you're done, the output file will have a record of your gdb session. This will save all the output to that logfile.txt. When you're done, the output file will have a record of your gdb session.  +  +=== Debugging Libreoffice ===  +The default commands to launch libreoffice are bash scripts, which are not allowed with gdb.  +  +However,a special command option is provided:  +{{cmd|libreoffice --backtrace}}  +  +This will launch a gdb session.     === Debugging Apache in Mageia 2 === === Debugging Apache in Mageia 2 === Papoteur

← Older revision Revision as of 11:40, 14 April 2025 Line 31: Line 31:  * [[Ihre_ersten_Schritte_im_QA-Team-de|Mach mit!]] * [[Ihre_ersten_Schritte_im_QA-Team-de|Mach mit!]]    −Das ist alles. Wirklich. Jemand wird Sie im Team willkommen heißen. Das meiste, was Sie wissen müssen um anzufangen, finden Sie bereits [[Ihre_ersten_Schritte_im_QA-Team-de|hier in unserem Wiki]][[File:Flag-united-kingdom02.png|21px|link=]].+Das ist alles. Wirklich. Jemand wird Sie im Team willkommen heißen. Das meiste, was Sie wissen müssen um anzufangen, finden Sie bereits [[Ihre_ersten_Schritte_im_QA-Team-de|hier in unserem Wiki]].     Es ist auch sehr hilfreich wenn Sie zu uns in den irc://irc.libera.chat/#mageia-qa #mageia-qa Libera Chat] Kanal beitreten, wo Fragen schnell beantwortet werden können, und ein [[Sophie-de|Bot]] nützliche Informationen über die verschiedenen Pakete in Mageia zur Verfügung stellt. Hier werden auch jeden ersten und dritten Donnerstag im Monat Meetings abgehalten. Es ist auch sehr hilfreich wenn Sie zu uns in den irc://irc.libera.chat/#mageia-qa #mageia-qa Libera Chat] Kanal beitreten, wo Fragen schnell beantwortet werden können, und ein [[Sophie-de|Bot]] nützliche Informationen über die verschiedenen Pakete in Mageia zur Verfügung stellt. Hier werden auch jeden ersten und dritten Donnerstag im Monat Meetings abgehalten. Psyca