NOTE: pacman v7 is currently in [libre-testing]; but it will be promoted to
libre soon
from arch:
With the release of [version 7.0.0] pacman has added support for
downloading packages as a separate user with dropped privileges.
For users with local repos however this might imply that the downl
from arch:
After upgrading to `openssh-9.8p1`, the existing SSH daemon will be unable to
accept new connections (see
<https://gitlab.archlinux.org/archlinux/packaging/packages/openssh/-/issues/5>).
When upgrading remote hosts, please make sure to restart the sshd service
using `systemct
From: "Arch Linux: Recent news updates: David Runge"
TL;DR: Upgrade your systems and container images **now**!
As many of you may have already read [1], the upstream release tarballs for
`xz` in version `5.6.0` and `5.6.1` contain malicious code which adds a
from arch:
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.
First remove mutter43, then immediately perfor
>From Arch:
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
installe
The `base-devel` package group has recently been replaced by a meta package of
the same name.
People that had the `base-devel` package group installed (meaning people that
installed `base-devel` before February 2nd) have to explicitly re-install it to
get the new `base-devel` package install
until https://bugs.archlinux.org/task/76440 is resolved
> FS#76440 : systemd-cryptsetup still refers to libcrypto.so.1.1 after
upgrading to openssl3
URL:
/news/systemd-encrypted-boot-may-be-broken-by-upgrade-systemd-cryptsetup-suggest-to-postpone-upgrading/
__
2022-08-30 - Christian Hesse
Recent changes in grub added a new command option to fwsetup and changed the
way the command is invoked in the generated boot configuration. Depending on
your system hardware and setup this could cause an unbootable system due to
incompatibilities between the instal
if pacman gives an error message like:
> error: failed to prepare transaction (could not satisfy dependencies) ::
removing wxgtk-common breaks dependency 'wxgtk-common' required by
wxgtk2
you will need to uninstall 'wxgtk2' and it's dependents first (the
only such parabola packages are 'freefi
users of a GTK-based desktops (LXDE, MATE, possibly others) on the i686 system,
should refrain from upgrading for some time, or else the desktop may not start
properly - this bug does not affect X86_64
URL: /news/i686-desktop-users-should-refrain-from-upgrading/
10 matches
Mail list logo