[Unstable Update] 2023-05-21 - Repository changes

cscs · 13 June 2023 18:58

Huh?
pacdiff -o just prints all pacnew/pacsaves.
pacdiff itself can delete, ignore, or merge them.
The whole reason for these things is so you can preserve your configurations.

anon84230528 · 13 June 2023 20:05

Do the changes in the repos already affect the stable version (Reinstalled with kde-22.1.3-minimal-230529-linux61.iso, then did all stable updates)? I ask because I just came from Arch and there the changes are already done for some time.

Yochanan · 13 June 2023 20:27

No, only the Manjaro unstable branch thus far.

If you want to use Manjaro and stay close to Arch updates, use the unstable branch.

Yochanan · 14 June 2023 21:30

OpenBLAS >= 0.3.23-2 update requires manual intervention

2023-06-14 - Felix Yan

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.

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.

Unfortunately you will get errors on updating if you currently have OpenBLAS installed as the default BLAS implementation:
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
Please append your preferred default BLAS implementation to the regular -Syu command line to get around it. For example:
sudo pacman -Syu blas-openblas
or
sudo pacman -Syu blas

cscs · 14 June 2023 22:00

Well thanks for making me look.
Now I realized I was using blas when I want blas-openblas instead.

GaVenga · 16 June 2023 10:42

The Time Has Come:
Testing finished changing in the repos since “15.06.2023”
( [Testing Update] 2023-06-15 - Kernel, Systemd, Mesa, GNOME 44.2, NVIDIA, ZFS, LibreOffice, PipeWire - #7 by Lila-Kuh )

Yochanan · 16 June 2023 15:17

Thanks for letting me know. I never would have found out unless you told me.

Yochanan · 17 June 2023 19:45

Yochanan · 18 June 2023 13:57

TeX Live package reorganization

2023-06-18 - Antonio Rojas

Starting from version 2023.66594-9, TeX Live packages have been reorganized to mirror upstream collections. Even though the new texlive-basic replaces the old texlive-core, 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 tlmgr utility, eg.
$ tlmgr info euler | grep collection
collection:  collection-latexrecommended
which means the euler CTAN package is contained in texlive-latexrecommended. You may also use pacman -F to query for specific files.

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.

mithrial · 19 June 2023 08:00

This broke latexmk:

$ pamac search --files /usr/bin/latexmk
/usr/bin/latexmk is owned by texlive-bin

$ pamac info texlive-bin
Name                  : texlive-bin
Version               : 2023.66984-7
[...]
Build Date            : Sa 17 Jun 2023 01:29:09 CEST
Install Date          : Mo 19 Jun 2023 09:57:19 CEST

$ which latexmk
latexmk not found

Edit: You have to install texlive-binextra to actually install latexmk.

The file that texlive-bin provides is a broken symlink to /usr//share/texmf-dist/scripts/latexmk/latexmk.pl which can only be resolved by installing the binextra package.

Yochanan · 19 June 2023 14:48

It’s fixed with 2023.66594-13.

freggel.doe · 20 June 2023 11:16

systemd in it’s current state has a regression which leads to (some) problems with libvirtd and other services:

github.com/systemd/systemd

libvirtd socket activation not working since 253.5

opened 12:34PM - 07 Jun 23 UTC

closed 04:18PM - 19 Jun 23 UTC

lkrms

bug 🐛 pid1 regression ⚠️ rc-blocker 🚧

### systemd version the issue has been seen with 253.5 ### Used distribution …Arch Linux (rolling) ### Linux kernel version used 6.3.5-arch1-1 ### CPU architectures issue was seen on x86_64 ### Component systemd ### Expected behaviour you didn't see In its default configuration, `libvirtd.service` starts a `libvirtd` process that times out after 120 seconds of inactivity (no running domains and no connected clients). The service remains active and `libvirtd` is respawned on-demand via systemd socket activation (`libvirtd-ro.socket`, `libvirtd.socket` and `libvirtd-admin.socket` correspond to `/var/lib/libvirt/`{`libvirt-sock-ro`,`libvirt-sock`,`libvirt-admin-sock`}` respectively by default). ### Unexpected behaviour you saw After updating from systemd 253.4 to 253.5, socket activation stopped working. Attempting to connect to `libvirtd` via a socket after it times out yields nothing. Client software (I'm using `virsh` and `virt-manager` on the same host) halts indefinitely as soon as a `libvirtd`-dependent command is issued, and no errors are reported or logged before or after they are terminated (e.g. with Ctrl+C), including by systemd. If `systemctl restart libvirtd.service` is issued in a separate terminal, `libvirtd` starts as normal and any processes trying to connect via a socket succeed immediately (there is no need to cancel the attempt and try again). After rolling back systemd, libvirt and other updates installed at the same time in various combinations, the culprit appears to be systemd 253.5. Downgrading to 253.4 restores the desired behaviour. ### Steps to reproduce the problem - Install a libvirt package with stock systemd unit files - Start libvirtd and/or enable its sockets as needed - Wait for the libvirtd process to terminate after 2 minutes - Run `sudo virsh list` or similar - Wait indefinitely ### Additional program output to the terminal or log subsystem illustrating the issue ```sh Here's output from strace, in the absence of anything appearing in a log entry: https://gist.github.com/lkrms/5bb9ef2e7ad8aa5d89e164b6e3f4d4a6#file-gistfile1-txt ```

It seems to be resolved now by reverting the offending commit:

Arch has already released a fixed systemd package with this single cherry-pick:

As we do not inherit systemd from arch, I’m hoping for an updated package…

edit: Thanks to @Yochanan the patch has landed:

Yochanan · 21 June 2023 18:14

The pamac-gtk Gtk 4 port is finally finished!

Make sure you’re fully up to date first:

sudo pacman -Syu

Then choose which version you prefer:

Install Gtk 4 version:

sudo pacman -S pamac-gtk

Install Gtk 3 version:

sudo pacman -S pamac-gtk3

Zesko · 21 June 2023 20:04

I get a lot of GTK critical messages when clicking on Pamac menu in the GUI in KDE Plasma, this is pamac-gtk. but pamac-gtk3 has no issue. I can reproduce the issue on my system and VM without custom config.

(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.950: _gtk_css_corner_value_get_x: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.950: _gtk_css_corner_value_get_y: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.964: _gtk_css_corner_value_get_x: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.964: _gtk_css_corner_value_get_y: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.964: _gtk_css_corner_value_get_x: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.964: _gtk_css_corner_value_get_y: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.993: _gtk_css_corner_value_get_x: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
(pamac-manager:3193): Gtk-CRITICAL **: 21:52:34.993: _gtk_css_corner_value_get_y: assertion 'corner->class == &GTK_CSS_VALUE_CORNER' failed
...

I reported the issue.

Locutus · 21 June 2023 22:52

How will the gtk4 version affect the Flatpak and Snap plugins?

Yochanan · 21 June 2023 23:09

They’re not related as they’re part of libpamac.

freggel.doe · 22 June 2023 06:43

pamac-gtk and pamac-gtk3 should properly conflict reach other.

edit: Ah, the current pamac-gtk3 package conflicts with pamac-gtk but the current pamac-gtk doesn’t conflict with pamac-gtk3.

Locutus · 22 June 2023 09:30

It still has to interact with them.

jrichard326 · 22 June 2023 10:10

The description of pamac-gtk (gtk4 version) still notes gtk3 in the description. I have installed the gtk4 version and it seems to function well for my use case. Nice work and thank you.

Zesko · 22 June 2023 10:25

Changing some Pamac preferences can not be saved when using pamac-gtk (gtk4)

How to reproduce the issue:

Open pamac-manager
Click Pamac meu → Click “Preferences”
Change number of “Parallel downloads”
or change “mirrors”
or change “Number of versions of each package to keep”
Close and reopen “Preferences”.
As a result, it does not change.