archlinux32.gpg does not exist

Jogoboyo · 2018-09-25 09:50:01

i try install archlinux for android, use TermuxArch https://github.com/sdrausty/TermuxArch, for my device, the script detect x86_64 then install archlinux-bootstrap-2017.03.01-i686.tar.gz automatically. Im stuck when full upgrade. I think about my architectur. Then i found this website (archlinux32) then follow guide on download page, but stuck here...

$ pacman -Syy archlinux32-keyring-transition
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from mirror.archlinux32.org : The requested URL returned error: 404 error: failed to update core (unexpected error) error: failed retrieving file 'extra.db' from mirror.archlinux32.org : The requested URL returned error: 404 error: failed to update extra (unexpected error) error: failed retrieving file 'community.db' from mirror.archlinux32.org : The requested URL returned error: 404
error: failed to update community (unexpected error) error: failed to synchronize any databases error: failed to init transaction (unexpected error)

$ pacman-key --populate archlinux32
==> ERROR: The keyring file /usr/share/pacman/keyrings/archlinux32.gpg does not exist

levi · 2018-09-25 19:10:25

To begin with you're getting errors because mirrors.archlinux32.org doesn't have full x86_64 repositories.

I'm at a loss when you say the script detected your device was x64 then proceeded to download a very old i686 build.

There are ways out of this muddle to install archlinux32 I'm pretty sure, but first I'd like to know why you're installing archlinux32 on a 64-bit machine?

Jogoboyo · 2018-09-26 05:48:59

I am also confused, for you to know, I use Android Asus Zenfone 2, then install Termux, in termux the installed package is marked with i686 architecture, in the repository there is no jdk which I want to install. There is information if you want to install the JDK then you must install TermuxArch, but as I mentioned above, when installing Android devices using x86_64 architecture, but the installation takes i686.

run on Termux

$ uname -a
Linux localhost 3.10.20-x86_64_moor-265462-gfd33dd4 #1 SMP PREEMPT Fri Sep 30 15:31:23 CST 2016 x86_64 Android

run on TermuxArch

$ uname -a
Linux localhost 3.10.20-x86_64_moor-265462-gfd33dd4 #1 SMP PREEMPT Fri Sep 30 15:31:23 CST 2016 x86_64 GNU/Linux

also getprop

$ getprop ro.product.cpu.abi                                                       
x86
$ getprop ro.product.cpu.abilist32
x86,armeabi-v7a,armeabi
$ getprop ro.product.cpu.abilist64

$ getprop ro.product.cpu.abilist
x86,armeabi-v7a,armeabi
$ getprop ro.config.hwrlib
T9_x86
$ getprop sys.kernel.version
3.10.20-x86_64_moor-265462-gfd33dd4

Last edited by Jogoboyo (2018-09-26 06:16:26)

Jogoboyo · 2018-09-26 05:57:06

problem # 1

error: failed retrieving file 'core.db' from mirror.archlinux32.org : The requested URL returned error: 404
error: failed to update core (unexpected error)

can be fixed by changing the architecture part from auto to i686 in pacman.conf. But still having problems

downloading required keys...
error: key "2C146C01A952AC0F" could not be looked up remotely
error: key "C8E8F5A0AF9BA7E7" could not be looked up remotely
error: key "74EDA3C6B06D0506" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded

Last edited by Jogoboyo (2018-09-26 06:33:27)

Jogoboyo · 2018-09-26 13:17:26

Finally, the problem is resolved perfectly, first edit pacman.conf, disable SigLevel by changing the value to Never, then install the ca-certificates-utils first before full upgrade,

pacman -S ca-certificates-utils

After it is installed, run the

pacman -Syu

After full upgrade is complete, check the history during installation, if there is a warning stating that there is a new file created with filename.pacnew then use the filemanager to replace the old file with the newly created file.

For example, a new file named pacman.conf.pacnew, then change the old file name pacman.conf to pacman.conf.bak (for backup if there is a problem can be returned immediately), then rename the new file pacman.conf.pacnew to pacman.conf .

Ignore the warning section:

warning: /etc/group installed as /etc/group.pacnew
warning: /etc/gshadow installed as /etc/gshadow.pacnew
warning: /etc/passwd installed as /etc/passwd.pacnew
warning: /etc/resolv.conf installed as /etc/resolv.conf.pacnew
warning: /etc/shadow installed as /etc/shadow.pacnew

levi · 2018-09-26 17:56:44

Why do you say 'ignore the warning section' after telling us to use those warnings to identify the pacnew files?

FWIW, you may continually need to check for pacnew files. They *should* only be created when your current file is modified from the baseline and there's a new version; if you've not changed any configs they should never accrue. Therefore you usually need to compare the two files (non-pacnew and pacnew) and transfer over your modifications, if they still make sense. Simply copying the new version may often work, but I have to ask why you modified the configs in the first place?

Personally for example I usually only get pacnew files for my mirrorlist, my ssh configs (because I tightened them up), and my account configs (group, passwd, shadow etc). It's perhaps not surprising those are flagged up as modified becuase you need to do a useradd during the bringing up of the machine, but if you just copy over the supplied passwd.pacnew there's a risk you'll nix that account I think, and wipe out your network configs.

I use vimdiff to compare the two and to transfer over changes, using slightly arcane keystrokes I have to look up each time I do it (I think it might be 'go' for get other, but I may be mixing them up with the folding commands I learnt at about the same juncture). I don't usually notice all of the warnings, I'm afraid, so I simply periodically do a 'find /etc -iname \*.pacnew' to list the pacnew files I've accrued. There's usually a grace period where old configs are deprecated but still accepted, so provided I tidy them up before that runs out, I'm grand.

Jogoboyo · 2018-09-27 13:59:28

oh I feel confused to answer you, sorry. But you are better aware of my previous problems, you can visit this first issues. The point is I want to install arclinux on an android device, not on a PC / laptop. For that I have to go through some steps, first I have to install Termux (available on google playstore), after that I install archlinux by following TermuxArch, but it turns out my device has failed when installing it, because of architectural problems, after making the issue in its repository but the owner also did not provide enough solutions, I finally looked for the solution myself, until finally I arrived in this community. So if you see from each stage of the problem that is passed then the part of the file that I mark to ignore that does not need to be updated. That's all, but ... even though I thank the fellow community members for archipelux32 I was willing to reply to my question, and I'm sorry if I was wrong in choosing the title

levi · 2018-09-27 16:10:53

Ah, well either way I'm glad you appear to have solved your problems. Installing arch to an android phone is not in my area of expertise or interest to be honest, but I guess that might change in the future.

Arch Linux

#1 2018-09-25 09:50:01

archlinux32.gpg does not exist

#2 2018-09-25 19:10:25

Re: archlinux32.gpg does not exist

#3 2018-09-26 05:48:59

Re: archlinux32.gpg does not exist

#4 2018-09-26 05:57:06

Re: archlinux32.gpg does not exist

#5 2018-09-26 13:17:26

Re: archlinux32.gpg does not exist

#6 2018-09-26 17:56:44

Re: archlinux32.gpg does not exist

#7 2018-09-27 13:59:28

Re: archlinux32.gpg does not exist

#8 2018-09-27 16:10:53

Re: archlinux32.gpg does not exist

Board footer