Wiki Mageia

‎Unused system packages

← Older revision Revision as of 15:03, 14 August 2025 Line 118: Line 118:  More advanced output: numbered, size in MB, showing versions: More advanced output: numbered, size in MB, showing versions:    $ rpm -qa --queryformat '%{size} %{name}-%{version}-%{release}\n' | sort -k 1,1 -rn | numfmt --field 1 --to=iec | nl | head -20   $ rpm -qa --queryformat '%{size} %{name}-%{version}-%{release}\n' | sort -k 1,1 -rn | numfmt --field 1 --to=iec | nl | head -20  +  +=== Unused system packages ===  +  +One very large package is kernel-firmware-nonfree, about 1,1 GB!  It may contain drivers your system needs, but maybe not so you could try without it.  For example on a Thinkpad T43, I could remove it without noting any regression which of course made huge difference on the small drive.  +  +You may also find some other system packages that is of no use for your particular system, but be careful.  For example you may have installed task-printing which pulled in a lot of printer support, but you do not need support for all printers.     === Check what folders are large === === Check what folders are large === Morgano

‎System: + Backport kernel

← Older revision Revision as of 22:58, 13 August 2025 Line 414: Line 414:     * For GNOME, [[#GNOME|Applet visibility]] need to be enabled. * For GNOME, [[#GNOME|Applet visibility]] need to be enabled.  +  +  +=== Backport kernel ===  +  +Kernel 6.12 is available August 2025.  Note that it need [[Kernel_flavours#Backport_kernels|some care]].     <br> <br> Morgano

+ Backport kernel

← Older revision Revision as of 22:53, 13 August 2025 Line 66: Line 66:  The release follows the up-to-date "release candidates" from kernel.org and can provide support for recent features if not available in standard kernels. The release follows the up-to-date "release candidates" from kernel.org and can provide support for recent features if not available in standard kernels.    −==Kernel series in Cauldron==+== Backport kernels ==  +   +It happens that a kernel get backported to previous Mageia release, i.e from Cauldron to latest official Mageia.  +   +'''In Mageia 9, Kernel 6.12''' is provided in Backport repository for '''x86_64 in desktop flavour''' ''- no other version.''<br>  +''('''In progress''' {{Bug|34545}} August 2025; kernel is currently in backport_testing repo)''<br>  +'''<br>  +Only two packages to install''' (from Backport): <br>  +kernel-stable-desktop-6.12... <br>  +kernel-stable-desktop-devel-6.12...  +   +'''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.''  +   +'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have in parallel with non backport kernel-userspace-headers, but currently is not (See {{Bug|34545}}).  +''  +   +'''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.  +   +'''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br>  +$ sudo rmmod kvm_intel<br>  +$ sudo rmmod kvm  +   +== Kernel series in Cauldron ==     In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.). In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.). Line 76: Line 98:  Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3). Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3).    −As an example, on May 29 2025 we had the following kernels in Cauldron:+As an example, on August 13 2025 we had the following kernels in Cauldron: −* kernel-mainline -> 6.15.0 (x86_64, desktop only)+* kernel-mainline -> 6.16.0 (x86_64, desktop only) −* kernel-stablenew -> 6.14.8 (x86_64, desktop only)+* kernel-stablenew -> 6.15.7 (x86_64, desktop only) −* kernel-stable -> 6.12.30 (x86_64, desktop only)+* kernel-stable -> 6.14.11 (x86_64, desktop only) −* kernel -> 6.12.30 (all arches, all flavours)+* kernel -> 6.12.41 (all arches, all flavours) −* kernel-lts -> 6.6.92 (all arches, all flavours)+* kernel-lts -> 6.6.100 (all arches, all flavours) Morgano

Added draft note as some user believed, MGA10 is already released

← Older revision Revision as of 06:20, 13 August 2025 Line 5: Line 5:     {{multi language banner| ; }} {{multi language banner| ; }}  +  +{{draft}}     {{introduction|Presentation of the evolution, new features, known issues, and the recent changes of the Mageia distribution.}} {{introduction|Presentation of the evolution, new features, known issues, and the recent changes of the Mageia distribution.}} Sturmvogel

‎Other method for cleaning up RPMs: + finding largest folders, + DNF sync, + release updates examples

← Older revision Revision as of 20:31, 12 August 2025 Line 118: Line 118:  More advanced output: numbered, size in MB, showing versions: More advanced output: numbered, size in MB, showing versions:    $ rpm -qa --queryformat '%{size} %{name}-%{version}-%{release}\n' | sort -k 1,1 -rn | numfmt --field 1 --to=iec | nl | head -20   $ rpm -qa --queryformat '%{size} %{name}-%{version}-%{release}\n' | sort -k 1,1 -rn | numfmt --field 1 --to=iec | nl | head -20  +  +=== Check what folders are large ===  +  + # du -mx / | sort -rn | head -50     === Removing packages which are not included in any of your repositories === === Removing packages which are not included in any of your repositories === Line 129: Line 133:  To simply show all packages that are not contained in any of the currently configured repositories, use To simply show all packages that are not contained in any of the currently configured repositories, use    $ urpmq --not-available   $ urpmq --not-available  +  +==== Automated sync to enabled repositories using DNF ====  +  +See [[Using_DNF#Synchronize_with_repos|Synchronize with repos, using DNF]]  +     ==== Check per release suffix ==== ==== Check per release suffix ====    −List all packages not ".mga8":+List all packages not ".mga9": −  $ rpm -qa | grep -v .mga8+  $ rpm -qa | grep -v .mga9    −List all packages from previous version - Mageia 7 here:+List all packages from previous version - Mageia 8 here: −  $ rpm -qa | grep .mga7+  $ rpm -qa | grep .mga8    −For a graphical interface method: {{prog|Mageia Control Center}} section {{menu|Software Management -> Install & Remove Software}}, in first dropdown select: "All", in second: "Installed", and in "Find" field click magnify glass symbol, select "in names" and enter "mga7" (without quotes).+For a graphical interface method: {{prog|Mageia Control Center}} section {{menu|Software Management -> Install & Remove Software}}, in first dropdown select: "All", in second: "Installed", and in "Find" field click magnify glass symbol, select "in names" and enter "mga8" (without quotes).     Removing some packages from previous Mageia release may remove applications of current Mageia release - that happened me for filezilla and vlc, then just reinstall them afterwards. Removing some packages from previous Mageia release may remove applications of current Mageia release - that happened me for filezilla and vlc, then just reinstall them afterwards. Line 150: Line 159:  * Some application you fetched and installed as rpm from other source than Mageia * Some application you fetched and installed as rpm from other source than Mageia  * Application you compiled and packaged locally * Application you compiled and packaged locally −* Application kept from previous Mageia release, [[Mageia_8_Release_Notes#Packages_removed_from_the_distribution|not available in current release]] but still working  +* Application kept from previous Mageia release, [[Mageia_9_Release_Notes#Packages_removed_from_the_distribution|not available in current release]] but still working    * Packages from previous Mageia releases that are needed by some of above cases * Packages from previous Mageia releases that are needed by some of above cases  * ... * ... Morgano

Mention order.rb

← Older revision Revision as of 03:02, 10 August 2025 Line 10: Line 10:     See [https://ml.mageia.org/l/msg/sysadmin-discuss/2025-06/PLKqH37EC2YbQjvDencaWg this thread] for more info. See [https://ml.mageia.org/l/msg/sysadmin-discuss/2025-06/PLKqH37EC2YbQjvDencaWg this thread] for more info.  +  +=== Package Ordering ===  +  +Since some packages are dependant on others, rebuilds need to happen in a specific order. The packages without any other dependencies should be built first, then the packages that only have dependencies among the first batch already rebuilt, and so on until all packages have been rebuilt. When building a subset of packages due to a specific upgraded package, these sets can be determined like this:  +<pre>  +ruby order.rb <UpgradedPackageName>  +</pre>  +''Todo: where is this script located and what are its dependencies?''     == See Also == == See Also == Danf

‎Einleitung

← Older revision Revision as of 21:26, 8 August 2025 Line 16: Line 16:  Zuerst solltest du die '''-debug''' Pakete der Anwendungen installieren und all die Bibliotheken die hier eingebunden sind. Dies ermöglicht es dir, mit Hilfe der ganzen Werkzeuge zur Fehlersuche, sehr nützliche Informationen anzuzeigen.   Zuerst solltest du die '''-debug''' Pakete der Anwendungen installieren und all die Bibliotheken die hier eingebunden sind. Dies ermöglicht es dir, mit Hilfe der ganzen Werkzeuge zur Fehlersuche, sehr nützliche Informationen anzuzeigen.      −'''gdb''' selbst gibt eine handliche Liste der fehlenden  '''-debug''' Pakete zurück, die noch zu installieren sind. Anschließend musst die diese fehlenden '''-debug'''-Pakete installieren und <code>gdb</code> neu starten.+'''gdb''' selbst gibt eine handliche Liste der fehlenden  '''-debug''' Pakete zurück, die noch zu installieren sind. Anschließend musst du die fehlenden '''-debug'''-Pakete installieren und <code>gdb</code> neu starten.  Nun kannst du nützliche Informationen sammeln indem du die nachfolgenden aufgelisteten Werkzeuge verwendest. Nun kannst du nützliche Informationen sammeln indem du die nachfolgenden aufgelisteten Werkzeuge verwendest.  +  +Installiere hierfür das Paket ''urpmi-debuginfo-install'': {{command|urpmi --auto urpmi-debuginfo-install}}     Damit es möglich ist die '''-debug''' Pakete, die du benötigst, zu installieren, musst du die separaten '''-debug''' Repositorys hinzufügen und aktivieren. Wenn du einen vollen Satz an Repositorys mittels der Mageia Softwareverwaltung hinzugefügt hast, ist alles was du tun musst, diese als '''root''' in einem Terminal mit folgendem Kommando zu aktualisieren: Damit es möglich ist die '''-debug''' Pakete, die du benötigst, zu installieren, musst du die separaten '''-debug''' Repositorys hinzufügen und aktivieren. Wenn du einen vollen Satz an Repositorys mittels der Mageia Softwareverwaltung hinzugefügt hast, ist alles was du tun musst, diese als '''root''' in einem Terminal mit folgendem Kommando zu aktualisieren: Psyca

← Older revision Revision as of 13:34, 7 August 2025 (One intermediate revision by the same user not shown)Line 11: Line 11:  == Preliminaries == == Preliminaries ==    −First, you should install the ''-debug'' packages of the applications and all the libraries that might be involved. It will allow all the debugging tools to report more useful information.  +First, you should install the ''-debug'' packages of the applications and all the libraries that might be involved. It will allow all the debugging tools to report more useful information.     gdb itself will give you the command line to run in order to install these '''-debug''' packages and restart {{cmd|gdb}}. gdb itself will give you the command line to run in order to install these '''-debug''' packages and restart {{cmd|gdb}}.  Now you can start collecting useful information using the various tools listed below. Now you can start collecting useful information using the various tools listed below.  +  +To do this, install the package ''urpmi-debuginfo-install'': {{command|urpmi --auto urpmi-debuginfo-install}}     To be able to install -debug packages, you need to add or enable the separate -debug repositories. If you've added a full set of repositories via Mageia software management, all you need to do is update them with the following command in a terminal as root: To be able to install -debug packages, you need to add or enable the separate -debug repositories. If you've added a full set of repositories via Mageia software management, all you need to do is update them with the following command in a terminal as root: Mokraemer