Mageia wiki - Recent changes [en]

Pushing updates

Danf — Thu, 11 Jun 2026 16:13:35 GMT

‎Push the update: chown no longer required since 7fb11bfb on puppet

SOP Moving RPMs

Danf — Thu, 11 Jun 2026 01:32:30 GMT

Use --remove-updates for package removal

Mageia 10 Veröffentlichungshinweise-de

Psyca — Wed, 10 Jun 2026 21:43:10 GMT

Mageia 10 Release Notes

Katnatek — Tue, 09 Jun 2026 20:19:16 GMT

‎Artwork: mageia-theme-extra information

QA ISO testers

Doktor5000 — Sun, 07 Jun 2026 20:25:56 GMT

‎For Qa team:: added doktor5000

Mageia 10 Veröffentlichungshinweise-de

Psyca — Sat, 06 Jun 2026 18:52:47 GMT

@@ Line 78: / Line 78: @@
 </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:
+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. Once done, you can exit all screen and terminal windows on duvel.
 == Backports ==

@@ Line 22: / Line 22: @@
 # First, check that this is a valid request. Was this asked by the packager that built the package or the registered maintainer of the package? Is this a removal from '''updates_testing''' (good) or another section (suspect)?
-# Run the '''mga-move-pkg''' in dry-run mode to see what files need to be moved: '''mga-move-pkg --dry-run 9/core/mypackage-99-1.mga9.src.rpm'''
+# Run this to remove the package(s) and update metadata: '''sudo -u schedbot mga-move-pkg --sync --remove-updates-testing 9/core/mypackage-99-1.mga9.src.rpm'''
-# Or, find the RPM files manually under '''/distrib/bootstrap/distrib/9/*/media/{,debug/}core/updates_testing/''' and '''/distrib/bootstrap/distrib/9/SRPMS/core/updates_testing/''' (where 9 is the stable mga release)
+# It is possible to remove packages from update or release in a stable distro, but you should almost '''never''' do it!
 === Cauldron Normal Package Moves ===
@@ Line 44: / Line 43: @@
+'
 <pre>
-Usage: mga-move-pkg/mga-adv-move-pkg [--new-package] [--dry-run] [--sync] [--no-confirm] [--backport] <release>/<section>/<pkg> [[--backport] <release>/<section>/<pkg>...]
+Usage: mga-move-pkg [--dry-run] [--sync] [--no-confirm] [--new-package | --remove-release | --remove-updates | --remove-updates-testing] [--backport] <release>/<section>/<pkg> [[--backport] <release>/<section>/<pkg>...]
 --dry-run     Just display commands and don't run them
 --sync        Update hdlists after move
 --no-confirm  Don't require manual confirmation for each move (only valid if full SRPM names given)
 --backport    The following package is in subsection "backports" (default "updates")
 </pre>
@@ Line 64: / Line 67: @@
 Sometimes packages need to be moved between other sections besides updates. However, sometime it should ''not'' be done with a move. For example, moving from '''updates_testing''' to '''tainted_testing''' should be done by deleting from '''updates_testing''', bumping the release and ''rebuilding'' in '''tainted_testing'''. This is because "tainted" becomes part of the release name embedded in the RPM during the build. If another unusual move is needed, follow this procedure:
-# Evaluate the request. This is even more important here because it's not a usual case. Specifically, consider if it's a move in or out of tainted. TBD
+# Evaluate the request. This is even more important here because it's not a usual case. Specifically, consider if it's a move in or out of tainted. Consider if the risk of messing up the repo is worth doing a move, or if the developer should just bump the release number and rebuild.
 # Find the RPMs under '''/distrib/bootstrap/distrib/cauldron/*/media/core/updates_testing/''' (or the relevant location)
 # Manually move the files, making sure all architectures, the SRPM and all subpackages are removed.
@@ Line 77: / Line 80: @@
 # In most cases, the requester will want to delete the latest version of a package and restore an older version. Make sure the old packages are still available under '''/var/lib/schedbot/old/'''
 # Find the RPMs under '''/distrib/bootstrap/distrib/cauldron/*/media/core/updates_testing/''' (or the relevant location). If the RPMs to remove are indeed from ''updates_testing'' (or ''backports_testing''), then you can use the "Raw Commands" output of '''mga-move-pkg --dry-run 9/core/foobar-0.1-1.mga9.src.rpm''' to find the RPM paths given the SRPM names (add '''--backport''' as appropriate).
-# Delete package(s) manually, making sure all architectures, the SRPM and all subpackages are removed.
+# If possible, run a command like '''sudo -u schedbot mga-move-pkg --remove-updates cauldron/core/mypackage-99-1.mga9.src.rpm''' to delete the SRPM and all the subpackages. Use '''--remove-update-release''' or '''--remove-release''' instead, as appropriate. Otherwise, delete package(s) from bootstrap manually, making sure all architectures, the SRPM and all subpackages are removed.
 # If this is the '''release''' subsection, copy ALL the equivalent older version files back as replacements.
-# Run '''sudo -u schedbot mga-hdlists cauldron core updates_testing''' or as relevant for the removed section.
+# Run '''sudo -u schedbot mga-hdlists cauldron core updates_testing''' or as relevant for the removed section to update the package metadata.
 === Restoring old RPMs ===

← Older revision		Revision as of 21:43, 10 June 2026
Line 59:		Line 59:

	Für den Hauptbildschirmschoner haben wir eine Bildgröße von 3840x2160 im JXL Format ausgewählt, damit diese auf modernen 2k Monitoren und selbst auf 4k Monitoren, gut aussehen, während diese eine ähnliche Speichergröße aufweisen, wie die Bilder in Mageia 9, welche eine niedrigere Auflösung besaßen und das JPG Format nutzten.		Für den Hauptbildschirmschoner haben wir eine Bildgröße von 3840x2160 im JXL Format ausgewählt, damit diese auf modernen 2k Monitoren und selbst auf 4k Monitoren, gut aussehen, während diese eine ähnliche Speichergröße aufweisen, wie die Bilder in Mageia 9, welche eine niedrigere Auflösung besaßen und das JPG Format nutzten.
		+
		+	Beachten Sie, dass wir das Paket {{prog\|mageia-theme-extra}}, mit einigen zusätzlichen Hintergründen, inklusive einige der vorherigen Hintergründen von Mageia, anbieten.

	== Große Entwicklungen ==		== Große Entwicklungen ==

← Older revision		Revision as of 20:19, 9 June 2026
Line 65:		Line 65:

	For the main screensavers, we have chosen an image size of 3840×2160 and the JXL format, allowing them to look great on modern 2K and even 4K monitors, while maintaining a disk space footprint similar to those included in Mageia 9, which used lower resolutions and the JPG format.		For the main screensavers, we have chosen an image size of 3840×2160 and the JXL format, allowing them to look great on modern 2K and even 4K monitors, while maintaining a disk space footprint similar to those included in Mageia 9, which used lower resolutions and the JPG format.
		+
		+	Remember that we have the {{prog\|mageia-theme-extra}} package with some additional backgrounds including some of the previous signature backgrounds for mageia.

	== Major developments ==		== Major developments ==

← Older revision		Revision as of 20:25, 7 June 2026
Line 129:		Line 129:

	* Flavianoep - Flaviano Matos - pehteimoso-bugzilla at yahoo dot com		* Flavianoep - Flaviano Matos - pehteimoso-bugzilla at yahoo dot com
		+
		+	* doktor5000 - Florian Hubold - doktor5000 at arcor dot de

← Older revision		Revision as of 18:52, 6 June 2026
Line 633:		Line 633:

	Diese Kategorie enthält die folgenden Pakete, alphabetisch:		Diese Kategorie enthält die folgenden Pakete, alphabetisch:
		+	* bookworm