- Arch-general - lists.archlinux.org

Re: Arch-general Digest, Vol 4, Issue 13
by Frank LoPinto 25 Dec '22

25 Dec '22

Hello Dave, You can get past this by typing pacman-key --recv-keys 76A5EF9054449A5C This will refresh Pierre Schmitz's key. You can check the key id at https://pierre-schmitz.com/about/gpg-keys/pierre-packager-key/ Merry Christmas! Frank On Sun, Dec 25, 2022 at 12:03 AM <arch-general-request(a)lists.archlinux.org> wrote: > Send Arch-general mailing list submissions to > arch-general(a)lists.archlinux.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > arch-general-request(a)lists.archlinux.org > > You can reach the person managing the list at > arch-general-owner(a)lists.archlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Arch-general digest..."Today's Topics: > > 1. pacstrap complaining about corrupt package (David N Murray) > 2. Re: pacstrap complaining about corrupt package (Mike Yuan) > > > > ---------- Forwarded message ---------- > From: David N Murray <dmurray(a)jsbsystems.com> > To: arch-general(a)lists.archlinux.org > Cc: > Bcc: > Date: Sun, 25 Dec 2022 00:12:32 -0500 > Subject: pacstrap complaining about corrupt package > > Hi all, > > Trying to install Arch on a new birthday/Christmas present. I'm manually copying this (abbreviated) because I can't figure out how to get the text off the new box: > > # pacstrap /mnt linux linux-firmware base btrfs-progs intel-ucode nano iw > [snipped the package list and stuff] > :: Retrieving packages... > openssl-3.0.7-4-x86_64 ... > (126/126) checking keys in keyring > (126/126) checking package integrity > error: openssl: signature from "Pierre Schmitz <pierre(a)archlinux.org> <pierre(a)archlinux.org>" is marginal trust > :: File /mnt/var/cache/pacman/pkg/openssl-3.0.7-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). > [failure messages] > > Things I've tried/checked: > * clock on the new box has correct time > * pacman -Syu from another machine. That pulled down a new archlinux-keyring and openssl-3.0.7-4 and it ran fine > * new machine has same mirrorlist that worked with the pacman -Syu > * commented out mirrorlist entries one-at-a-time to see if it was one mirror problem. 5 servers all give the same results. > > The other 125 packages that were downloaded all passed the integrity check (I think). > > Any suggestions? > > TIA, > Dave Murray > > > > > > ---------- Forwarded message ---------- > From: Mike Yuan <me(a)yhndnzj.com> > To: David N Murray <dmurray(a)jsbsystems.com> > Cc: arch-general(a)lists.archlinux.org > Bcc: > Date: Sun, 25 Dec 2022 13:17:14 +0800 > Subject: Re: pacstrap complaining about corrupt package > The keyring shipped in the 2022.12.01 ISO is outdated. You’ll need to > update it using `pacman -Sy archlinux-keyring` first before pacstrap-ping :) > > Hi all, >> >> Trying to install Arch on a new birthday/Christmas present. I'm manually copying this (abbreviated) because I can't figure out how to get the text off the new box: >> >> # pacstrap /mnt linux linux-firmware base btrfs-progs intel-ucode nano iw >> [snipped the package list and stuff] >> :: Retrieving packages... >> openssl-3.0.7-4-x86_64 ... >> (126/126) checking keys in keyring >> (126/126) checking package integrity >> error: openssl: signature from "Pierre Schmitz <pierre(a)archlinux.org> <pierre(a)archlinux.org>" is marginal trust >> :: File /mnt/var/cache/pacman/pkg/openssl-3.0.7-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). >> [failure messages] >> >> Things I've tried/checked: >> * clock on the new box has correct time >> * pacman -Syu from another machine. That pulled down a new archlinux-keyring and openssl-3.0.7-4 and it ran fine >> * new machine has same mirrorlist that worked with the pacman -Syu >> * commented out mirrorlist entries one-at-a-time to see if it was one mirror problem. 5 servers all give the same results. >> >> The other 125 packages that were downloaded all passed the integrity check (I think). >> >> Any suggestions? >> >> TIA, >> Dave Murray >> >> >> _______________________________________________ > Arch-general mailing list -- arch-general(a)lists.archlinux.org > To unsubscribe send an email to arch-general-leave(a)lists.archlinux.org >

1 0

pacstrap complaining about corrupt package
by David N Murray 25 Dec '22

25 Dec '22

Hi all, Trying to install Arch on a new birthday/Christmas present. I'm manually copying this (abbreviated) because I can't figure out how to get the text off the new box: # pacstrap /mnt linux linux-firmware base btrfs-progs intel-ucode nano iw [snipped the package list and stuff] :: Retrieving packages... openssl-3.0.7-4-x86_64 ... (126/126) checking keys in keyring (126/126) checking package integrity error: openssl: signature from "Pierre Schmitz<pierre(a)archlinux.org>" is marginal trust :: File /mnt/var/cache/pacman/pkg/openssl-3.0.7-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). [failure messages] Things I've tried/checked: * clock on the new box has correct time * pacman -Syu from another machine. That pulled down a new archlinux-keyring and openssl-3.0.7-4 and it ran fine * new machine has same mirrorlist that worked with the pacman -Syu * commented out mirrorlist entries one-at-a-time to see if it was one mirror problem. 5 servers all give the same results. The other 125 packages that were downloaded all passed the integrity check (I think). Any suggestions? TIA, Dave Murray

4 5

Re: RFC - thoughts about Arch and init freedom? (proposal for comments on arch-general)
by David C. Rankin 20 Dec '22

20 Dec '22

On 12/16/22 15:46, Andreas Radke wrote: > I suggest to fix this lack of init choice/alternative. I'd like to > implement it into the official Arch Linux repos allowing to choose > some different init replacement. We can either just add a 2nd init > system in the most simple way or allow real init-freedom[3] offering > full choice and leave it up to be further filled by the community. I remember the discussions well. Most of which took place on the arch-general list at the time. It may be helpful to take feedback from the arch-general list, at least to get feedback on the current community thoughts on the matter. For me, I think it is a great idea Andreas. While for desktop use systemd has captured a majority of the distros -- and no complaints, the take-it-or-leave-it if you want Arch seems a bit restrictive. While the change from init-scripts to systemd was uncomfortable at the time, the transition was done well. That said, the point made about providing an alternative init to help with implementation on new architectures is well-taken. While systemd does provide a great deal of functionality, it also fairly heavy. Keeping systemd as a default while providing an alternative init for those that would benefit from -- or just like to use -- an alternative init sounds like a solid way to go. Essentially giving Arch the best of both worlds. -- David C. Rankin, J.D.,P.E.

2 1

xflock4 doesn't work anymore
by Ralf Mardorf 20 Dec '22

20 Dec '22

Hi, usually I lock the screen of my openbox sessions (no DE) on demand by running xflock4 . Today I locked the screen using dm-tool lock , since xflock4 fails. I don't know when it exactly stopped working. The time frame is between the beginning of last week, until today. pacman.log shows [2022-12-16T13:56:41+0100] [ALPM] upgraded xfce4-session (4.16.0-2 -> 4.18.0-1) I wonder if it's a bug or if some changes require to re/start something etc.. Regards, Ralf

1 1

XMPP support for Arch Linux
by Polarian 16 Dec '22

16 Dec '22

Hello, So currently there is two methods (which I know of) with communicating with the Arch Community, those are email (mailing list) and IRC (I believe on libera.chat?!?!?). Is there any plans to support XMPP? Thanks, Polarian

5 5

Re: XMPP support for Arch Linux
by Óscar García Amor 16 Dec '22

16 Dec '22

El vie, 16 dic 2022 a las 10:42, progandy (<admin(a)progandy.de>) escribió: > You seem to have misunderstood xiretza. The channel already exists [1] > and is mentioned in the wiki [2]. Right. I was completely unaware of this. As it does not appear on the main website under the community section, the truth is that I did not even know it existed. In this case maybe what should be done is simply that this information appears where I have commented (IMHO). Greetings [1]: https://matrix.to/#/#archlinux:archlinux.org [2]: https://wiki.archlinux.org/title/Matrix -- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me

2 1

Should git be contained in base-devel group?
by Polarian 15 Dec '22

15 Dec '22

Hello, I do not know which mailing list to send this in but I have a question to bring up. After being brought up in the aur mailing list, I was wondering why is git not in the base-devel group, which contains all the tools needed for building PKGBUILDs, but cloning from the AUR (and a lot of PKGBUILDs) all use git, therefore wouldn't it make sense for this to be include in base-devel? Thanks, Polarian

2 2

update warnings
by Fons Adriaensen 14 Dec '22

14 Dec '22

Hello, A full update gives me a number of warnings about dependency cycles. Can this be safely ignored, or is some special handling required ? TNX, -- FA

2 3

Suggest to use more long options arguments at /etc/makepkg.conf
by u34＠net9.ga 14 Dec '22

14 Dec '22

I think long command line options are more readable compared to short one. There fore, I suggest: --- a/makepkg.conf 2022-12-12 17:00:57.773722168 +0000 +++ b/makepkg.conf 2022-12-12 18:00:46.612320662 +0000 @@ -9,11 +9,11 @@ # #-- The download utilities that makepkg should use to acquire sources # Format: 'protocol::agent' -DLAGENTS=('file::/usr/bin/curl -qgC - -o %o %u' - 'ftp::/usr/bin/curl -qgfC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u' - 'http::/usr/bin/curl -qgb "" -fLC - --retry 3 --retry-delay 3 -o %o %u' - 'https::/usr/bin/curl -qgb "" -fLC - --retry 3 --retry-delay 3 -o %o %u' - 'rsync::/usr/bin/rsync --no-motd -z %u %o' +DLAGENTS=('file::/usr/bin/curl --disable --globoff --continue-at - --output %o %u' + 'ftp::/usr/bin/curl --disable --globoff --fail --continue-at - --ftp-pasv --retry 3 --retry-delay 3 --output %o %u' + 'http::/usr/bin/curl --disable --globoff --cookie "" --fail --location --continue-at - --retry 3 --retry-delay 3 --output %o %u' + 'https::/usr/bin/curl --disable --globoff --cookie "" --fail --location --continue-at - --retry 3 --retry-delay 3 --output %o %u' + 'rsync::/usr/bin/rsync --no-motd --compress %u %o' 'scp::/usr/bin/scp -C %u %o') # Other common tools: @@ -134,15 +134,15 @@ # COMPRESSION DEFAULTS ######################################################################### # -COMPRESSGZ=(gzip -c -f -n) -COMPRESSBZ2=(bzip2 -c -f) -COMPRESSXZ=(xz -c -z -) -COMPRESSZST=(zstd -c -z -q -) -COMPRESSLRZ=(lrzip -q) -COMPRESSLZO=(lzop -q) +COMPRESSGZ=(gzip --to-stdout --force --no-name) +COMPRESSBZ2=(bzip2 --stdout --force) +COMPRESSXZ=(xz --to-stdout --compress -) +COMPRESSZST=(zstd --stdout --compress --quiet -) +COMPRESSLRZ=(lrzip --quiet) +COMPRESSLZO=(lzop --quiet) COMPRESSZ=(compress -c -f) -COMPRESSLZ4=(lz4 -q) -COMPRESSLZ=(lzip -c -f) +COMPRESSLZ4=(lz4 --quiet) +COMPRESSLZ=(lzip --stdout --force) ######################################################################### # EXTENSION DEFAULTS -- u34

7 11

With a XferCommand, pacman -Sw doesn't download packages sig files
by u34＠net9.ga 03 Dec '22

03 Dec '22

With a XferCommand = /usr/bin/curl --socks5-hostname localhost:9451 --silent --show-error --continue-at - --fail-early --fail --output %o %u in pacman.conf, pacman -sync --downloadonly doesn't download packages sig files. Is it because I have not set up a proxy variable? Something else? The pkg.tar.zst is downloaded. Just the detached sig file does not. And there isn't any message to warn about it. Commenting out XferCommand makes the sig files downloaded as well. Manual download also succeed. -- u34

1 0