You are not logged in.

#1 2017-08-17 09:58:59

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 823
Website

Comments on the current installation process

I tried the whole process as described on the download page:
https://archlinux32.org/download/, Transition from the Official Repositories

I have some remarks:

1) mirrorlist:

Server = http://mirror.archlinux32.oss/$arch/$repo

should maybe be called:

Server = http://mirror.archlinux32.org/$arch/$repo

(the list I downloaded from https://raw.githubusercontent.com/archl … irrorlist)

2) Keys

pacman -Syyw archlinux32-keyring
:: Synchronizing package databases...
core                                168.0 KiB  1006K/s 00:00 [##################################] 100%
extra                                 2.1 MiB  1583K/s 00:01 [##################################] 100%
community                             4.3 MiB  1149K/s 00:04 [##################################] 100%
resolving dependencies...

Packages (1) archlinux32-keyring-20170628-1

Total Download Size:  0.01 MiB

:: Proceed with download? [Y/n]
:: Retrieving packages...
archlinux32-keyring-20170628-1-any   14.5 KiB  1035K/s 00:00 [##################################] 100%
(1/1) checking keys in keyring                                [##################################] 100%
downloading required keys...
error: key "77BEA194A234FF8F" could not be looked up remotely

easiest for me seems to be to set 'SigLevel=Never' while executing (pacman -Syyw archlinux32-keyring) and
resetting it to the default after this command.

Otherwise, fine job. :-)

Works without any problems..

Last edited by andreas_baumann (2017-08-17 10:01:51)

Offline

#2 2017-08-17 16:41:13

tyzoid
Administrator
From: Ann Arbor, MI
Registered: 2017-06-17
Posts: 86

Re: Comments on the current installation process

Thanks. We'll get this right at some point. There's some debugging that needs to occur to see why that key isn't being inserted into the keyring at ISO build time, but thanks for testing, and for the alternative workaround.

Offline

#3 2017-08-19 07:54:43

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 823
Website

Re: Comments on the current installation process

Offline

#4 2017-08-22 14:52:56

deep42thought
Administrator
From: Jena, Germany
Registered: 2017-06-17
Posts: 608

Re: Comments on the current installation process

.oss is an openNIC tld.
It's listed in the mirror list in case, someone resolves via openNIC and prefers an "open" solution over the official one.
Is there any specific reference to mirror.archlinux32.oss on the download page? If so, we should change it to .org.

Regarding the key: The plan was to let som TU sign the archlinux32-keyring package, so pacman won't complain on an official installation. Until that is done, I prefer to keep the warning - because that is, what's not perfect yet :-)

Offline

Board footer

Powered by FluxBB