Arch Linux: Recent news updateshttps://archlinux.org/news/The latest and greatest news from the Arch Linux distribution.en-usFri, 11 Aug 2023 14:55:16 +0000budgie-desktop >= 10.7.2-6 update requires manual interventionhttps://archlinux.org/news/budgie-desktop-1072-6-update-requires-manual-intervention/<p>When upgrading from budgie-desktop 10.7.2-5 to 10.7.2-6, the package mutter43 must be replaced with magpie-wm, which currently depends on mutter. As mutter43 conflicts with mutter, manual intervention is required to complete the upgrade.</p> <p>First remove mutter43, then immediately perform the upgrade. Do not relog or reboot between these steps.</p> <p><code>pacman -Rdd mutter43</code></p> <p><code>pacman -Syu</code></p>Campbell JonesFri, 11 Aug 2023 14:55:16 +0000tag:archlinux.org,2023-08-11:/news/budgie-desktop-1072-6-update-requires-manual-intervention/TeX Live package reorganizationhttps://archlinux.org/news/tex-live-package-reorganization/<p>Starting from version 2023.66594-9, TeX Live packages have been reorganized to mirror upstream collections. Even though the new <code>texlive-basic</code> replaces the old <code>texlive-core</code>, many of the texlive-core contents (including language specific files) are now split between different packages. To find out which Arch package contains a specific CTAN package, you can use the <code>tlmgr</code> utility, eg.</p> <pre><code>$ tlmgr info euler | grep collection collection: collection-latexrecommended </code></pre> <p>which means the euler CTAN package is contained in <code>texlive-latexrecommended</code>. You may also use <code>pacman -F</code> to query for specific files.</p> <p>A new metapackage texlive-meta is available to install all subpackages (except for language specific ones), and the new texlive-doc package provides the full documentation for offline use.</p>Antonio RojasSun, 18 Jun 2023 09:14:37 +0000tag:archlinux.org,2023-06-18:/news/tex-live-package-reorganization/OpenBLAS >= 0.3.23-2 update requires manual interventionhttps://archlinux.org/news/openblas-0323-2-update-requires-manual-intervention/<p>The openblas package prior to version 0.3.23-2 doesn't ship optimized LAPACK routine and CBLAS/LAPACKE interfaces for compatibility. This decision has been reverted now, and the ability to choose a different default system BLAS/LAPACK implementation while keeping openblas installed is now provided to allow future co-installation of BLIS, ATLAS, etc.</p> <p>The default BLAS implementation will be used for most packages like NumPy or R. Please install "blas-openblas" and "blas64-openblas" to make OpenBLAS the default BLAS implementation, just like the old behavior.</p> <p>Unfortunately you will get errors on updating if you currently have OpenBLAS installed as the default BLAS implementation:</p> <p>error: failed to prepare transaction (could not satisfy dependencies) :: installing openblas (0.3.23-2) breaks dependency 'blas' required by cblas :: installing openblas (0.3.23-2) breaks dependency 'blas' required by lapack</p> <p>Please append your preferred default BLAS implementation to the regular -Syu command line to get around it. For example:</p> <pre><code>pacman -Syu blas-openblas </code></pre> <p>or</p> <pre><code>pacman -Syu blas </code></pre>Felix YanWed, 14 Jun 2023 20:27:28 +0000tag:archlinux.org,2023-06-14:/news/openblas-0323-2-update-requires-manual-intervention/Git migration completedhttps://archlinux.org/news/git-migration-completed/<p>We are proud to announce that the migration to Git packaging succeeded! 🥳</p> <p>Thanks to everyone who has helped during the migration!</p> <p>Package sources are now available on <a href="https://gitlab.archlinux.org/archlinux/packaging/packages">GitLab</a>. Note that the bugtracker is still <a href="https://bugs.archlinux.org">flyspray</a> and that merge requests are not accepted as of now. We intend to open the issue tracker and merge requests on the Gitlab package repos in the near future.</p> <p>Mirrors are syncing again, but it may take a bit of time until your mirror of choice has caught up.</p> <h2>For users</h2> <p>Update your system and merge the pacman pacnew <code>/etc/pacman.conf.pacnew</code> file. This is required as we have moved the <code>[community]</code> repository into <code>[extra]</code>.</p> <pre><code>$ pacman -Syu "pacman&gt;=6.0.2-7" </code></pre> <p>For users of the now deprecated <code>asp</code> tool, you will need to switch to <code>pkgctl</code>:</p> <pre><code>$ pacman -Syu "devtools&gt;=1:1.0.0-1" $ pkgctl repo clone linux </code></pre> <p>For some more detailed instructions on how to obtain PKGBUILDs see the corresponding wiki <a href="https://wiki.archlinux.org/title/Arch_build_system#Retrieve_PKGBUILD_source">article</a>.</p> <h2>For packagers</h2> <p>Before starting, first uninstall <code>devtools-git-poc</code> and remove any repos from your filesystem that you cloned during the git proof-of-concept testing.</p> <p>Make sure you have both, an updated devtools and pacman on your system:</p> <pre><code>$ pacman -Syu "devtools&gt;=1:1.0.0-1" "pacman&gt;=6.0.2-7" </code></pre> <p>Additionally clean up old chroots in <code>/var/lib/archbuild/</code></p> <pre><code>$ rm -rf /var/lib/archbuild/ # or optionally, use the --clean option for pkgctl build *ONCE* $ pkgctl build --clean </code></pre> <p>For instruction on how to use <code>pkgctl</code>, please take a look at the "How to be a packager" wiki <a href="https://wiki.archlinux.org/title/DeveloperWiki:HOWTO_Be_A_Packager">article</a> and also consult the man page of each subcommand for further information:</p> <pre><code>$ man pkgctl-build $ man pkgctl-repo-clone </code></pre>Levente PolyakSun, 21 May 2023 11:14:50 +0000tag:archlinux.org,2023-05-21:/news/git-migration-completed/Git migration announcementhttps://archlinux.org/news/git-migration-announcement/<p>This Friday morning (2023-05-19) the Git packaging migration will start until Sunday (2023-05-21). The Arch Linux packaging team will not be able to update packages in any of the repositories during this period.</p> <p>Notification when the migration starts, and when it is completed, will be published on the <code>[arch-dev-public]</code> mailing list.</p> <h2>How does this impact Arch Linux users?</h2> <p>The <code>[testing]</code> repository will be split into <code>[core-testing]</code> and <code>[extra-testing]</code>, the <code>[staging]</code> repository will be split into <code>[core-staging]</code> and <code>[extra-staging]</code>. The <code>[community]</code> repository will be merged into <code>[extra]</code> and will therefore be empty after the migration.</p> <p>All affected repositories will be provided as empty repositories for a transition period after the migration. For regular users, this means that everything works as before.</p> <p><strong>Note:</strong> After the migration is done, users that have the testing repositories enabled need to include the new repositories (<code>[core-testing]</code> and <code>[extra-testing]</code> instead of <code>[testing]</code>) in their <code>pacman.conf</code> before updating their system.</p> <p>Other changes:</p> <ul> <li><a href="https://archlinux.org/svn/">SVN access</a> is discontinued and will dissappear.</li> <li>The svn2git mirror will no longer be updated.</li> <li><code>asp</code>, which relies on the svn2git mirror, will stop working. It is replaced by <a href="https://man.archlinux.org/man/pkgctl-repo-clone.1.en"><code>pkgctl repo clone</code></a>.</li> </ul> <h2>How does this impact Arch Linux tier 1 mirrors?</h2> <p>During the migration rsync and HTTP access will be shut down. We will send an email notification to arch-mirrors once everything has been finished.</p> <h2>How does this impact Arch Linux packagers?</h2> <p>Packagers will not be able to patch and update their packages. The internal Tier 0 mirror is also going to be disabled for the duration of this migration.</p>Jelle van der WaaMon, 15 May 2023 19:50:21 +0000tag:archlinux.org,2023-05-15:/news/git-migration-announcement/Switch to the base-devel meta package requires manual interventionhttps://archlinux.org/news/switch-to-the-base-devel-meta-package-requires-manual-intervention/<p>On February 2nd, the <code>base-devel</code> package group has been replaced by a meta package of the same name.<br /> If you installed the <code>base-devel</code> package group prior to this date, explicitly re-install it to get the new <code>base-devel</code> package installed on the system: </p> <p><code>pacman -Syu base-devel</code></p>Robin CandauSun, 12 Feb 2023 14:43:35 +0000tag:archlinux.org,2023-02-12:/news/switch-to-the-base-devel-meta-package-requires-manual-intervention/PHP 8.2 update and introduction of legacy branchhttps://archlinux.org/news/php-82-update-and-introduction-of-legacy-branch/<p>The <a href="https://archlinux.org/packages/extra/x86_64/php/">php</a> packages have been updated to the latest version 8.2. In addition to this, a new set of <a href="https://archlinux.org/packages/extra/x86_64/php-legacy/">php-legacy</a> packages have been introduced. These will follow the oldest but still <a href="https://www.php.net/supported-versions.php">actively supported PHP</a> branch. This enables users to install the latest version but also introduces the option to use third party applications that might rely on an older version. Both branches will be kept up to date following our rolling release model. <code>php</code> and <code>php-legacy</code> can be installed at the same time as the latter uses a <code>-legacy</code> suffix for its binaries and configuration files.</p> <p>In addition to this, the <a href="https://archlinux.org/news/php-80-and-php-7-legacy-packages-are-available/">php7</a> packages have been removed as they reached end of life. The <code>imap</code> extension will no longer be provided as it relies on the <code>c-client</code> library which has been abandoned for many years.</p>Pierre SchmitzFri, 13 Jan 2023 14:46:04 +0000tag:archlinux.org,2023-01-13:/news/php-82-update-and-introduction-of-legacy-branch/In memory of Jonathon Fernyhoughhttps://archlinux.org/news/in-memory-of-jonathon-fernyhough/<p>Arch Linux mourns the sudden loss of Jonathon Fernyhough, known in our community as <code>jonathon</code>, who passed away on Saturday night.</p> <p>Jonathon was an active participant and contributor to Arch Linux, several derived distributions, the AUR and through personal repositories. He was enthusiastic, helpful and eager to contribute towards improving the free and open source software community as a whole.</p> <p>On behalf of the wider Arch Linux community, our condolences go out to his family and friends.</p>Morten LinderudThu, 12 Jan 2023 12:12:16 +0000tag:archlinux.org,2023-01-12:/news/in-memory-of-jonathon-fernyhough/Removing python2 from the repositorieshttps://archlinux.org/news/removing-python2-from-the-repositories/<p>Python 2 went <a href="https://www.python.org/doc/sunset-python-2/">end of life</a> January 2020. Since then we have been actively cutting down the number of projects depending on <code>python2</code> in our repositories, and we have finally been able to drop it from our distribution. If you still have <code>python2</code> installed on your system consider removing it and any python2 package.</p> <p>If you still require the python2 package you can keep it around, but please be aware that there will be no security updates. If you need a patched package please consult the AUR, or use an <a href="https://wiki.archlinux.org/title/Unofficial_user_repositories">unofficial user repository</a>.</p>Jelle van der WaaFri, 23 Sep 2022 08:42:36 +0000tag:archlinux.org,2022-09-23:/news/removing-python2-from-the-repositories/Arch Linux mailing list changeshttps://archlinux.org/news/arch-linux-mailing-list-changes/<p>As part of <a href="https://archlinux.org/todo/conversion-of-programs-that-use-python-2-to-python-3/">dropping Python 2</a> which is EOL, we have migrated our mailing lists from mailman2 to mailman3.</p> <p>Rewriting of the "From" header and subject (to prepend the list name) have been disabled to keep the DKIM signature intact. This means "<a href="https://wiki.archlinux.org/title/General_guidelines#Reply_to_the_mailing_list">reply to mailing list</a>" must be used when replying to the list and you may need to update your filters and rules matching the "From" header.</p> <p><strong>All existing subscriptions are migrated and you do not need to re-subscribe.</strong> For managing your subscriptions a new mailman3 account <a href="https://lists.archlinux.org/accounts/signup/">must be registered</a>.</p>Kristian KlausenFri, 16 Sep 2022 13:11:30 +0000tag:archlinux.org,2022-09-16:/news/arch-linux-mailing-list-changes/