From xerxes at persrex.xyz  Sun Jul 10 15:20:56 2022
From: xerxes at persrex.xyz (Xerxes)
Date: Sun, 10 Jul 2022 08:20:56 -0700
Subject: [Assist] texlive-lang metapackage won't install properly
Message-ID: <89acfab1-2d58-d485-5f20-c5a48ffb341c@persrex.xyz>

Hello everyone,

Don't know how monitored this mailing list is, but I'm having an issue 
installing the texlive-lang metapackage. texlive-most installs just 
fine, but the package texlive-langcyrillic in texlive-lang has files 
that conflict with texlive-bin, so the installation fails. I'll attach 
the pacman output to this email.

To cause the error, just sudo pacman -S texlive-lang and it should break 
(with or without texlive-most installed).

I think it's a bug in the texlive-cyrillic package. It looks like the 
conflicting files are man pages, so it seems like it wouldn't be too 
difficult to fix. I tried to make an issue report on the tracker, but it 
keeps erroring out about my account being too new and my post having too 
many non-dictionary characters, even when I put my pacman output in an 
attached .txt file. So, I thought I might try here instead.

It's also possible I'm just being dumb and this is user error; if so 
please tell me how to fix it!

Thank you!
-------------- next part --------------
[ethanm at parabola ~]$ sudo pacman -S texlive-lang
:: There are 6 members in group texlive-lang:
:: Repository extra
   1) texlive-langchinese  2) texlive-langcyrillic  3) texlive-langextra  4) texlive-langgreek  5) texlive-langjapanese  6) texlive-langkorean

Enter a selection (default=all): 
resolving dependencies...
looking for conflicting packages...

Packages (21) ffcall-2.4-2  gd-2.3.3-4  harfbuzz-icu-4.4.1-1  libavif-0.10.1-2  libde265-1.0.8-2  libheif-1.12.0-3  libsigsegv-2.14-1  libyuv-r2322+3aebf69d-1
              perl-file-which-1.27-2  potrace-1.16-2  t1lib-5.1.2-8  texlive-bin-2021.59745-1.parabola2  texlive-core-2020.55416-1.par2  texlive-latexextra-2020.55418-1.par1
              zziplib-0.13.72-1  texlive-langchinese-2022.62922-1  texlive-langcyrillic-2022.62517-1  texlive-langextra-2022.62837-1  texlive-langgreek-2022.61820-1
              texlive-langjapanese-2022.63011-1  texlive-langkorean-2022.63005-1

Total Installed Size:  1296.45 MiB

:: Proceed with installation? [Y/n] 
(21/21) checking keys in keyring                                                                           [################################################################] 100%
(21/21) checking package integrity                                                                         [################################################################] 100%
(21/21) loading package files                                                                              [################################################################] 100%
(21/21) checking for file conflicts                                                                        [################################################################] 100%
error: failed to commit transaction (conflicting files)
/usr/share/man/man1/rubibtex.1.gz exists in both 'texlive-bin' and 'texlive-langcyrillic'
/usr/share/man/man1/rumakeindex.1.gz exists in both 'texlive-bin' and 'texlive-langcyrillic'
Errors occurred, no packages were upgraded.
[ethanm at parabola ~]$ 

From rysa88 at posteo.net  Fri Jul 15 06:06:44 2022
From: rysa88 at posteo.net (ryan)
Date: Fri, 15 Jul 2022 06:06:44 -0000
Subject: [Assist] Armv7h Package -Murmur/Mumble - No upstream update
Message-ID: <3ca5cf04444d101bf76a8e67fe4830d39c9f84ab.camel@posteo.net>

Hi
The upstream (Archlinux arm) murmur package for armv7h (which we pull
from them) has not updated despite serveral sucessful builds on x86_64,
which (according to the archlinux arm website) should have
automatically built on armv7h etc after this (but has been like this
for months). I have tried to contact upstream to rectify this as the
updates to protobuf and grpc packages break murmur (as the latest
x86_64 build are built against the newer versions of these), however I
have had no response via email from them and the only other way to
contact upstream for this is via a forum that requires non-free
javascript to use. Does anybody know what best way to contact someone
to rectify this?

Many Thanks 
Ry