Wiki de Mageia

← Older revision Revision as of 23:10, 28 June 2025 Line 286: Line 286:     {{Bug|34029}} - '''grisbi''' Wir aktualisieren grisbi, um Nutzern, welche von anderen Distributionen kommen, welche die Version 3.0.4 einsetzen, eine Kompatibilität anzubieten. Allerdings kann der 1st time wizard kein benutzerdefiniertes Verzeichnis für Sicherungen auswählen. Bitte wählen Sie dieses später unter Bearbeiten -> Einstellungen aus. {{Bug|34029}} - '''grisbi''' Wir aktualisieren grisbi, um Nutzern, welche von anderen Distributionen kommen, welche die Version 3.0.4 einsetzen, eine Kompatibilität anzubieten. Allerdings kann der 1st time wizard kein benutzerdefiniertes Verzeichnis für Sicherungen auswählen. Bitte wählen Sie dieses später unter Bearbeiten -> Einstellungen aus.  +  +'''BEHOBEN durch eine Aktualisierung''' {{Bug|34351}} - '''muse''' Bei einigen Desktop-Umgebungen friert muse ein, wenn eine benutzerdefinierte Farbe für einen Track ausgewählt wird. Die gewählte Methode um dieses Problem zu beheben hat einen Seiteneffekt im qt5ct Paket. Näheres hierzu im [https://advisories.mageia.org/MGAA-2025-0064.html advisory].     === Externe Software === === Externe Software === Psyca

‎Various software: Add muse

← Older revision Revision as of 22:59, 28 June 2025 Line 368: Line 368:     {{Bug|34029}} - '''grisbi''' We update grisbi to offer compatibility to users comming from other distributions that have the 3.0.4 version, but the 1st time wizard can't select custom folder for backups, please select it later in Edit -> Preferences {{Bug|34029}} - '''grisbi''' We update grisbi to offer compatibility to users comming from other distributions that have the 3.0.4 version, but the 1st time wizard can't select custom folder for backups, please select it later in Edit -> Preferences  +  +'''FIXED BY UPDATE''' {{Bug|34351}} - '''muse''' In some desktops, Muse freezes when you set a custom color for a track. The selected method to fix the issue have a side effect in the qt5ct package see the [https://advisories.mageia.org/MGAA-2025-0064.html advisory].     <br> <br> Katnatek

Point to e-mail

← Older revision Revision as of 21:23, 28 June 2025 Line 8: Line 8:     Documentation for the full rebuild process is TBD. Documentation for the full rebuild process is TBD.  +  +See [https://ml.mageia.org/l/msg/sysadmin-discuss/2025-06/PLKqH37EC2YbQjvDencaWg this thread] for more info.     == See Also == == See Also == Danf

← Older revision Revision as of 13:05, 28 June 2025 (One intermediate revision by the same user not shown)Line 61: Line 61:   ],  ],  </nowiki>}} </nowiki>}} −* Add a iurt account on the system and add schedbot@duvel ssh public key to iurt@lavand authorized_keys file.  −{{pre|<nowiki>ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD74XjxAUlKsEQngCGQ7uG1waCkd26ZbzUSUHdnQ3VGLxK2X8VTpDAN1xAxrQM2bTmED1o1y3UhI5n3QicJspB8DZUS7CW93bsE6GrIqh9e1HVbZXzV20esU2r68I5GUsBXXS5EQkUQfESAtAvL9cSARo/ZXiJ6yeX5OiFKofD6i1WnkboP6HM3fdG+vNZV5EYq1MU33NOUYR8HMMNFjcAiVpBjM++x1I+rIKro6l3jFKgBMfC1+afAB2o7en3CuqJtpcspb3A8wIKxXLWWK/aU5U8WK2lbixBzNWDb1Ug3HH7/DQdhZsZUe7U5bRlMe9U6OkJasOOeGqAuWrO6kcoN schedbot  −</nowiki>}}  −* Add the iurt and puppet packages on the build node      Then on the Mageia infra repository, that you modify the following way: Then on the Mageia infra repository, that you modify the following way: Line 119: Line 115:  </nowiki>}} </nowiki>}}    −* Add the build node to the ones allowaed to acces the repo+* Add the build node to the ones allowed to acces the repo  {{pre|<nowiki> $repo_allow_from_ips = [ {{pre|<nowiki> $repo_allow_from_ips = [  [...] [...] Line 126: Line 122:  </nowiki>}} </nowiki>}}    −* Finally add your build node to the list for right architecture and to the list of aliases in the same file config.pp:+* Before committing, check your modifications:  +{{pre|<nowiki>git diff  +git add -p  +puppet parser validate manifests/nodes/duvel.pp  +puppet parser validate manifests/nodes/sucuk.pp  +puppet parser validate manifests/nodes/neru.pp  +git commmit -m 'Add a new build node lavand to the infra'  +</nowiki>}}  +The parser validate commands will check the build system for duvel and the DNS configuration for sucuk and neru.  +   +* After the permissions have propagated, add the appropriate internal repository, currently infra_9 for Mageia 9  +{{pre|<nowiki>urpmi.addmedia infra_9 http://repository.mageia.org/distrib/infra_9/aarch64/media/infra/updates  +</nowiki>}}  +   +* Add the iurt and puppet packages on the build node, they should come from the infra repository  +{{pre|<nowiki>urpmi iurt puppet  +</nowiki>}}  +   +* Allow the machine to connect to puppet on duvel  +{{pre|<nowiki>iptables -A INPUT -s x.y.z.t/32 -p tcp -m tcp --dport 8140 -j ACCEPT  +</nowiki>}}  +   +* Register the machine with puppet and apply the config  +{{pre|<nowiki>puppet agent --test --verbose --waitforcert 240  +</nowiki>}}  +   +* While it is waiting, in another terminal on duvel accept and sign the certificate generated  +{{pre|<nowiki>  +puppet ca list  +puppet ca sign lavand.mageia.org  +</nowiki>}}  +   +* Finally add your build node to the list for right architecture in puppet config deployment/mga_buildsystem/manifests/config.pp:  {{pre|<nowiki>build_nodes        => { {{pre|<nowiki>build_nodes        => {  [...] [...] Line 139: Line 167:  The scheduler is rather basic and builds only a package at a time. So having multiple "virtual" entries (named 0, 1, ...) allows to build multiple packages on the same physical build node. The scheduler is rather basic and builds only a package at a time. So having multiple "virtual" entries (named 0, 1, ...) allows to build multiple packages on the same physical build node.    −* Before committing, check your modifications:  −{{pre|<nowiki>git diff  −git add -p  −puppet parser validate manifests/nodes/duvel.pp  −puppet parser validate manifests/nodes/sucuk.pp  −puppet parser validate manifests/nodes/neru.pp  −git commmit -m 'Add a new build node lavand to the infra'  −</nowiki>}}  −The parser validate commands will check the build system for duvel and the DNS configuration for sucuk and neru.      [[Category:Sysadmin]] [[Category:Sysadmin]] Pterjan

Add nospace

← Older revision Revision as of 06:57, 28 June 2025 Line 107: Line 107:     Added for mga8. Added for mga8.  +  +== nospace ==  +  +'''Problem''': The disk ran out of space while the build was in progress.  +  +'''Solution''': The build must be re-run (without change to the package) after sufficient disk space has been restored on the server. If the package requires an extraordinary amount of space for a build, the spec file should be adjusted to reduce the peak space demand, if possible. This might be done by removing unnecessary temporary files between sections of the build process, by deleting large, unneeded files before building begins, or by disabling parallel building.  +  +Added for mga10.     == ocamlunsafestring == == ocamlunsafestring == Danf

← Older revision Revision as of 21:38, 27 June 2025 Line 1: Line 1:  [[Category:Dokumentation]] [[Category:Dokumentation]]  [[Category:Mirrors]] [[Category:Mirrors]]  +[[Category:Sysadmin]]     {{Multi_language_banner-de|[[Spiegelserver Liste-de|Deutsch]] ; [[Mirror_List|English]] ; [[Liste des miroirs-fr|français]] ; [[Spiegelserverlijst-nl|Nederlands]] ; [[Yansı Listesi|Turkisk]] ; [[Listas de espelhos-pt-BR|português brasileiro]] ;}} {{Multi_language_banner-de|[[Spiegelserver Liste-de|Deutsch]] ; [[Mirror_List|English]] ; [[Liste des miroirs-fr|français]] ; [[Spiegelserverlijst-nl|Nederlands]] ; [[Yansı Listesi|Turkisk]] ; [[Listas de espelhos-pt-BR|português brasileiro]] ;}} Psyca

hs-esslingen.de

← Older revision Revision as of 00:33, 27 June 2025 Line 27: Line 27:  | [http://ftp.nluug.nl/pub/os/Linux/distr/mageia/ https://ftp.nluug.nl/]|| NLUUG || Groningen || ftp-admin || ftp-admin [AT] nluug [DOT] nl ||   | [http://ftp.nluug.nl/pub/os/Linux/distr/mageia/ https://ftp.nluug.nl/]|| NLUUG || Groningen || ftp-admin || ftp-admin [AT] nluug [DOT] nl ||    |- |- −| [https://mirror.math.princeton.edu/pub/mageia/ https://mirror.math.princeton.edu/]|| Princeton || Princeton || Benjamin Rose || benrose [AT] math [DOT] princeton [DOT] edu || 1st tier mirror+| [https://mirror.math.princeton.edu/pub/mageia/ https://mirror.math.princeton.edu/]|| Princeton || Princeton || Benjamin Rose || benrose [AT] math [DOT] princeton [DOT] edu || 1st tier mirror    |- |-  | [https://ftp.snt.utwente.nl/pub/os/linux/mageia/ https://ftp.snt.utwente.nl/] || Twente ||  Twente ||ftpcom || ftpcom [AT] snt [DOT] utwente [DOT] nl || | [https://ftp.snt.utwente.nl/pub/os/linux/mageia/ https://ftp.snt.utwente.nl/] || Twente ||  Twente ||ftpcom || ftpcom [AT] snt [DOT] utwente [DOT] nl ||  +|-  +| [https://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/ https://ftp-stud.hs-esslingen.de/] || Esslingen || Esslingen a.N. ||  ||  || [https://ftp-stud.hs-esslingen.de/info/status.php4?details=77 sync log]  |} |} Danf

Kernels, binrepo/, log/

← Older revision Revision as of 20:39, 26 June 2025 Line 4: Line 4:  These collect chroots under /home/iurt/chroot_tmp/iurt/. The longest possible build as of this writing will take 2 days, so running '''find /home/iurt/chroot_tmp/iurt/ -xdev -maxdepth 1 -type d -mtime +7''' will show some candidate directories to delete. Make sure to unmount anything mounted in those chroots first, like procfs (check '''mount'''). While you're cleaning up, unmount any stale nfs mounts for these chroots from /run/netns/chroot_cauldron.*. These collect chroots under /home/iurt/chroot_tmp/iurt/. The longest possible build as of this writing will take 2 days, so running '''find /home/iurt/chroot_tmp/iurt/ -xdev -maxdepth 1 -type d -mtime +7''' will show some candidate directories to delete. Make sure to unmount anything mounted in those chroots first, like procfs (check '''mount'''). While you're cleaning up, unmount any stale nfs mounts for these chroots from /run/netns/chroot_cauldron.*.    −== binrepo ==+== binrepo/ ==  This holds all the source archives for packages alongside the spec files (which are in svn). Deleting files from here means that it becomes impossible to submit a package to the build system that requires that binary archive to build. We need to be able to rebuild from source for currently-supported releases to apply security patches. There are also legal requirements to retain source code for a period under some Open Source licenses (e.g. GPL). Don't just delete files wantonly. This holds all the source archives for packages alongside the spec files (which are in svn). Deleting files from here means that it becomes impossible to submit a package to the build system that requires that binary archive to build. We need to be able to rebuild from source for currently-supported releases to apply security patches. There are also legal requirements to retain source code for a period under some Open Source licenses (e.g. GPL). Don't just delete files wantonly.     Source RPMs also contain the binrepo files, so if a file is removed from binrepo it can be recovered from the associated .src.rpm (assuming we have it around in a long-term archive). So, if a file was in a src.rpm for an obsolete mga release, if we can recover it if needed, and if it is no longer used in cauldron or any current mga release, then it should be fine to remove it. Source RPMs also contain the binrepo files, so if a file is removed from binrepo it can be recovered from the associated .src.rpm (assuming we have it around in a long-term archive). So, if a file was in a src.rpm for an obsolete mga release, if we can recover it if needed, and if it is no longer used in cauldron or any current mga release, then it should be fine to remove it.    −== distrib ==+Individual file removal is easiest performed with the '''mgarepo del <path>''' command, which doesn't have to be done on the binrepo server.  +   +== distrib/ ==  This holds all RPMs and metadata for all supported releases. When this fills, nobody can build any more packages. One strategy to free space is to hard link identical RPMs between bootstrap and mirror for cauldron. Another is to remove obsolete and unsupported releases, although you must first ensure the files are available elsewhere in case we need to fulfill any obligations under the GPL (and other licenses) to provide source code (this responsibility may not actually apply, but you need to be sure about that before deleting). This holds all RPMs and metadata for all supported releases. When this fills, nobody can build any more packages. One strategy to free space is to hard link identical RPMs between bootstrap and mirror for cauldron. Another is to remove obsolete and unsupported releases, although you must first ensure the files are available elsewhere in case we need to fulfill any obligations under the GPL (and other licenses) to provide source code (this responsibility may not actually apply, but you need to be sure about that before deleting).    −== log ==+== log/ ==  If the log partition (/var/log/) is filling up, there are a few things that can be done to make space. Running '''journalctl --vacuum-size=500M''' (with an appropriate size) will make some room immediately by deleting enough older logs so the remainder fit in the given space. Permanently reducing journal log sizes can be done by changing /etc/systemd/journald.conf for the host in puppet. If the log partition (/var/log/) is filling up, there are a few things that can be done to make space. Running '''journalctl --vacuum-size=500M''' (with an appropriate size) will make some room immediately by deleting enough older logs so the remainder fit in the given space. Permanently reducing journal log sizes can be done by changing /etc/systemd/journald.conf for the host in puppet.    −If other logs which are rotated by logrotate are getting too large, the logrorate settings may need to be tweaked. Logs are normally rotated monthly, so changing that to weekly will compress the log files much more often leaving more free space. This can be done by changing the logrotate settings for a service in puppet, possibly using a <% if @hostname == 'HOST' %> conditional. When changing the log rotation period, make sure to also change the number of logs to keep around (the ''rotate'' value); e.g. if changing from monthly to weekly, the maximum number will need to be increased by a factor of 4 to keep around the same log history available.+If other logs which are rotated by logrotate are getting too large, the logrorate settings may need to be tweaked. Logs are normally rotated monthly, so changing that to weekly will compress the log files much more often leaving more free space. This can be done by changing the logrotate settings for a service in puppet, possibly using a'' <% if @hostname == 'HOST' %>'' conditional (see [https://gitweb.mageia.org/infrastructure/puppet/commit/?id=a39a332671b7cb8e99c3ecf8954aeb20223eff14 this commmit] for an example). When changing the log rotation period, make sure to also change the number of logs to keep (the ''rotate'' value); e.g. if changing from monthly to weekly, the maximum number will need to be increased by a factor of 4 to keep around the same log history available.  +   +== Kernels ==  +Servers can often accumulate large, obsolete kernel packages over time that aren't automatically removed when new kernels are installed. Run '''rpm -qf /boot/vmlinuz*''' to see how many such packages there are. Run the '''remove-old-kernels'' program to remove unused kernel packages to free space.     == Expanding partitions == == Expanding partitions == Danf

‎Apprenticeship in progress

← Older revision Revision as of 19:53, 25 June 2025 Line 193: Line 193:  | Template || Example || [https://ml.mageia.org 2021-02-14] || {{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 2021-02-14] || {{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]  |- |- −|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+|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  |- |-  | katnatek || papoteur || [https://ml.mageia.org/l/arc/dev/2023-10/msg00041.html 2023-10-11] || {{yes|Done}} || {{yes|Done}}  || {{yes|Done}} || {{yes|Done}} || lyx<br>mythtv<br>task-plasma5 (spectacle)<br>obconf<br>pidgin-googlechat || {{yes|Done}}  || {{yes|Done}} || python-setuptools-git-versioning python-sphinxcontrib-jquery whatsie evdi awf-extended   | katnatek || papoteur || [https://ml.mageia.org/l/arc/dev/2023-10/msg00041.html 2023-10-11] || {{yes|Done}} || {{yes|Done}}  || {{yes|Done}} || {{yes|Done}} || lyx<br>mythtv<br>task-plasma5 (spectacle)<br>obconf<br>pidgin-googlechat || {{yes|Done}}  || {{yes|Done}} || python-setuptools-git-versioning python-sphinxcontrib-jquery whatsie evdi awf-extended   Daviddavid

cmake35

← Older revision Revision as of 19:38, 25 June 2025 Line 1: Line 1:  The [https://pkgsubmit.mageia.org/autobuild/results.php Autobuild results page] highlights certain common errors encountered in the build in the ''Detected errors'' column. Usually, these result from new compiler versions or additional build-time checks that affect many packages and therefore make them worthwhile to highlight. This page gives information on the detected problems and hints about how to fix them. New checks may be added in [https://gitweb.mageia.org/software/infrastructure/autobuild/tree/bugscan.rb bugscan.rb] The [https://pkgsubmit.mageia.org/autobuild/results.php Autobuild results page] highlights certain common errors encountered in the build in the ''Detected errors'' column. Usually, these result from new compiler versions or additional build-time checks that affect many packages and therefore make them worthwhile to highlight. This page gives information on the detected problems and hints about how to fix them. New checks may be added in [https://gitweb.mageia.org/software/infrastructure/autobuild/tree/bugscan.rb bugscan.rb]     +  +== cmake35 ==  +  +'''Problem''': Build aborts with the error message "Compatibility with CMake < 3.5 has been removed from CMake."  +  +'''Solution''': Update the VERSION argument ''<min>'' value (in CMakeLists.txt) IF the file is truly forwards-compatible.  Or, use the ''<min>...<max>'' syntax to tell CMake that the project requires at least ''<min>'' but has been updated to work with policies introduced by ''<max>'' or earlier. Or, add ''-DCMAKE_POLICY_VERSION_MINIMUM=3.5'' to try configuring anyway.  +  +Added for mga10.     == conflictstrl == == conflictstrl == Danf

Mageia_Release_Countdown

← Older revision Revision as of 00:53, 25 June 2025 Line 12: Line 12:     [[Sysadmin New Release]] [[Sysadmin New Release]]  +[[Mageia Release Countdown]]     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

Category:Sysadmin

← Older revision Revision as of 00:53, 25 June 2025 Line 1: Line 1:  [[Category:Documentation]] [[Category:Documentation]]  [[Category:Mirrors]] [[Category:Mirrors]]  +[[Category:Sysadmin]]     {{Multi_language_banner|[[Spiegelserver Liste-de|Deutsch]] ; [[Mirror_List|English]] ; [[Liste des miroirs-fr|français]] ; [[Spiegelserverlijst-nl|Nederlands]] ; [[Yansı Listesi|Turkisk]] ; [[Listas de espelhos-pt-BR|português brasileiro]] ;}} {{Multi_language_banner|[[Spiegelserver Liste-de|Deutsch]] ; [[Mirror_List|English]] ; [[Liste des miroirs-fr|français]] ; [[Spiegelserverlijst-nl|Nederlands]] ; [[Yansı Listesi|Turkisk]] ; [[Listas de espelhos-pt-BR|português brasileiro]] ;}} Danf

typos

← Older revision Revision as of 00:51, 25 June 2025 Line 6: Line 6:  However there's a trick for rebuilding the first packages in order to bootstrap the new perl. However there's a trick for rebuilding the first packages in order to bootstrap the new perl.    −In order to minimize cauldron disrupting, we'll usually rebuild the packages into core/updates_testing.+In order to minimize cauldron disruption, we'll usually rebuild the packages into core/updates_testing. −Once we've enough rebuild pkgs, they'll be moved into core/release and then any remaining pkg will be fixed.+Once we've enough rebuilt pkgs, they'll be moved into core/release and then any remaining pkgs will be fixed.     == Pass 0 for urpmi: Filesys-Df, Locale-gettext, URPM & XML-LibXML == == Pass 0 for urpmi: Filesys-Df, Locale-gettext, URPM & XML-LibXML ==    −Bootstrapping is tricky, there's a script for that at [https://gitweb.mageia.org/software/build-system/iurt/tree/rebuild_perl_iurt rebuild_perl_iurt] that needs to be run for each architecture :+Bootstrapping is tricky; there's a script for that at [https://gitweb.mageia.org/software/build-system/iurt/tree/rebuild_perl_iurt rebuild_perl_iurt] that needs to be run for each architecture :  <pre> <pre>  perl (not really needed as iurt/rebuild_perl_iurt will build it though it could catch a build error not seen locally) perl (not really needed as iurt/rebuild_perl_iurt will build it though it could catch a build error not seen locally) Line 38: Line 38:  </pre> </pre>    −== Pass 1 : pkgs just depending on base perl, that will enable to rebuild perl pkgs further in the dep tree ==+== Pass 1 : pkgs just depending on base perl, that will enable rebuilding perl pkgs further in the dep tree ==  This list was generated by using "urpmf --requires libperl.so" then sorted by deps : This list was generated by using "urpmf --requires libperl.so" then sorted by deps :    Line 110: Line 110:  </pre> </pre>    −=== Really less urgent: ===+=== Much less urgent: ===  <pre> <pre>  apache-mod_perl apache-mod_perl Line 472: Line 472:  </pre> </pre>    −=== 6b: the other who would only be caught while running perl modules depending on them: ===+=== 6b: the others who would only be caught while running perl modules depending on them: ===  <pre> <pre>  libguestfs libguestfs Line 599: Line 599:  *** either using drakx-in-chroot (See [[Drakx-installer tips and tricks]] for details) *** either using drakx-in-chroot (See [[Drakx-installer tips and tricks]] for details)    −One should just try a cople steps before aborting.+One should just try a couple steps before aborting. −If there's an error after a cople step, everything is OK.+If there's no error after a couple steps, everything is OK.     If there's an error, usually we need to include a missing perl module now needed by some of the modules used by drakx. If there's an error, usually we need to include a missing perl module now needed by some of the modules used by drakx. Line 609: Line 609:  == For references : deps for base packages == == For references : deps for base packages ==    −Those importants needs the following perl pkgs to be rebuild in order to be installable (not listing noarch perl modules from Core/Release)+Those important ones need the following perl pkgs to be rebuilt in order to be installable (not listing noarch perl modules from Core/Release)     perl-URPM needs (for building & running) perl-URPM needs (for building & running) Danf

Category:Sysadmin

← Older revision Revision as of 00:48, 25 June 2025 Line 14: Line 14:     providing the build ID you just found. providing the build ID you just found.  +  +[[Category:Sysadmin]] Danf

Category:Sysadmin

← Older revision Revision as of 00:47, 25 June 2025 Line 37: Line 37:  </pre> </pre>  where XXX is the string after ''userPassword::''. Ensure that what is displayed is different from what you sent it to, or else the password has not yet been changed. where XXX is the string after ''userPassword::''. Ensure that what is displayed is different from what you sent it to, or else the password has not yet been changed.  +  +[[Category:Sysadmin]] Danf

See also

← Older revision Revision as of 00:45, 25 June 2025 Line 8: Line 8:     Documentation for the full rebuild process is TBD. Documentation for the full rebuild process is TBD.  +  +== See Also ==  +  +[[Sysadmin New Release]]     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

Category:Sysadmin

← Older revision Revision as of 00:44, 25 June 2025 Line 24: Line 24:  </pre> </pre>  The previous maintainer's ID will be displayed when done. If the package name is invalid, an error message will be displayed and no reassignment will take place. The previous maintainer's ID will be displayed when done. If the package name is invalid, an error message will be displayed and no reassignment will take place.  +  +  +[[Category:Sysadmin]] Danf

Category:Sysadmin

← Older revision Revision as of 00:44, 25 June 2025 Line 18: Line 18:  ./secondary_submit /distrib/bootstrap/distrib/cauldron/SRPMS/core/release/{foo}.src.rpm cauldron {arch} core/release {user who should get the email in case of failure} ./secondary_submit /distrib/bootstrap/distrib/cauldron/SRPMS/core/release/{foo}.src.rpm cauldron {arch} core/release {user who should get the email in case of failure}  </pre> </pre>  +  +[[Category:Sysadmin]] Danf

Category:Sysadmin

← Older revision Revision as of 00:44, 25 June 2025 Line 42: Line 42:     TBD TBD  +  +[[Category:Sysadmin]] Danf

Category:Sysadmin

← Older revision Revision as of 00:43, 25 June 2025 Line 40: Line 40:  EOF EOF  </pre> </pre>  +  +[[Category:Sysadmin]] Danf