[SOLVED - Hurrah!] Upgrading from a truly ancient install

levi · 2020-10-28 21:06:59

It will tell you which keys are missing to the best of my knowledge. If you can get the right key for archlinux32-keyring you might be able to install that alone which should sort out all of your key problems. Once you've done that a #pacman -Syu should go through more cleanly.

You may have luck doing a '$sudo pacman-key --recv-keys 5FDCA472AB93292BC678FD59255A76DB9A12601A'. pacman-key seems to be a helper that effectively calls gpg --homedir /etc/pacman.d/gnupg with your specified option.

SDRausty · 2020-10-29 01:35:03

levi wrote:

outdated pacman doesn't support zst compression, and it won't have the right keys.

SDRausty wrote:

The key is now trusted! This is quite a success; thank you for helping levi.

SDRausty wrote:

archlinux32-keyring-20191103-1.0-any.pkg.tar.xz
openssl-1.1.1-1.0-i686.pkg.tar.xz
pacman-5.2.1-1.4-i686.pkg.tar.xz
These three packages installed well. The 'libcrypto.so.1.0.0' error is intriguing. Depending on the versions of the packages that were used, sometimes 'libcrypto.so.1.1' would be the one that's missing. What is the best match for these three packages?

I am not sure if we are just dealing with getting zst compression to work, though this no doubt is a goal. The errors regarding libs and lib components indicated what you reflected in the topic title, "Upgrading from a truly ancient install"; namely versioning... In this case, equalizing the versions of the packages that want installing to achieve the goal of updating the Arch Linux 32 system in Android smartphone. Do you agree?

Last edited by SDRausty (2020-10-29 14:00:35)

SDRausty · 2020-10-29 04:38:12

levi wrote:

pacman-key seems to be a helper that effectively calls gpg --homedir /etc/pacman.d/gnupg with your specified option.

The earlier keyring errors appear resolved; This is the codeset for Arch Linux 32:

# set customized commands for Arch Linux 32                                      
X86INT="for HKPSERVR in \"hkps://keyserver.ubuntu.com\" \"hkp://pgp.mit.edu:11371\" \"hkps://hkps.pool.sks-keyservers.net\"                                       
do                                                                               
printf \"%s\\n\" \"Running gpg --homedir /etc/pacman.d/gnupg --keyserver \$HKPSERVR --recv-keys 0x194e37a47a4c671807bacb37b1117bc1094ea6e9...\"                   
gpg --homedir /etc/pacman.d/gnupg --keyserver \$HKPSERVR --recv-keys 0x194e37a47a4c671807bacb37b1117bc1094ea6e9 && GPGBREAK=\"0\"                                 
[[ -z \"\${GPGBREAK:-}\" ]] || break                                             
done                                                                             
UPGDPKGS=(\"a/archlinux32-keyring/archlinux32-keyring-20191103-1.0-any.pkg.tar.xz\" \"p/pacman/pacman-5.2.1-1.4-i686.pkg.tar.xz\" \"o/openssl/openssl-1.1.1-1.0-i686.pkg.tar.xz\")                                                                 
for UPGDPAKG in \${UPGDPKGS[@]}                                                  
do                                                                               
printf \"%s\\n\" \"Running curl -OL http://archive.archlinux32.org/packages/\$UPGDPAKG\"                                                                          
curl -OL http://archive.archlinux32.org/packages/\$UPGDPAKG                      
done
pacman -U \${UPGDPKGS[@]##*/} --noconfirm && rm -f \${UPGDPKGS[@]##*/} || printf \"\\nThe command \'pacman -U \${UPGDPKGS[@]##*/} --noconfirm\' did not succeed : continuing...\\n\""

Sdrausty wrote:

pacman -Syu
pacman: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

Sdrausty wrote:

equalizing the versions of the packages that want installing to achieve the goal of updating the Arch Linux 32 system in Android smartphone. Do you agree?

levi · 2020-10-29 06:12:06

The simplest way to work out what versions of what packages to use is probably to look at the archives at archive.archlinux32.org/packages/<letter>/<package name> and look at the date of pacman and pick any packages for libs it turns out it depends on (such as libcrypto which comes from openssl) from just before that date. I can't immediately think of a reason why that wouldn't work.

SDRausty · 2020-10-29 16:51:24

levi wrote:

The simplest way ... look at the date of pacman and pick any packages for libs it turns out it depends on (such as libcrypto which comes from openssl) from just before that date.

Thank you for sharing this advice. These were the versions used in the latest attempt to update the system to the current version:

2019-11-04 archlinux32-keyring-20191103-1.0-any.pkg.tar.xz
2019-11-21 pacman-5.2.1-1.4-i686.pkg.tar.xz
2019-11-19 openssl-1.1.1.d-2.0-i686.pkg.tar.xz

(1/1) Arming ConditionNeedsUpdate...
pacman-conf: error while loading shared libraries: 
libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

pacman -Syu
pacman: error while loading shared libraries: 
libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

The linking solution:

ln libcrypto.so.1.1 libcrypto.so.1.0.0
ln libssl.so.1.1 libssl.so.1.0.0
pacman -Syu

pacman: /usr/lib/libc.so.6: 
version `GLIBC_2.28' not found (required by pacman)

pacman: /usr/lib/libc.so.6: 
version `GLIBC_2.27' not found (required by pacman)

pacman: /usr/lib/libc.so.6: 
version `GLIBC_2.28' not found (required by /usr/lib/libalpm.so.12)

pacman: /usr/lib/libc.so.6: 
version `GLIBC_2.25' not found (required by /usr/lib/libcrypto.so.1.1)

The three packages were carefully matched for;

Edit2: The next iteration of the installation is using these packages:

archlinux32-keyring-20191103-1.0-any.pkg.tar.xz
pacman-5.2.1-1.4-i686.pkg.tar.xz
openssl-1.0.2.k-1-i686.pkg.tar.xz

Do you have any advice as far as package selection?

Can you explain the difference between i486 and i686 in current Arch Linux 32 nomenclature please? Are both versions still current and still in use today? If so, are there any major differences in package selection?

Last edited by SDRausty (2020-10-29 17:09:30)

SDRausty · 2020-10-29 17:23:54

Packages (3) 
archlinux32-keyring-20191103-1.0  
openssl-1.0.2.k-1  
pacman-5.2.1-1.4

Total Installed Size:  11.10 MiB
Net Upgrade Size:       0.05 MiB

:: Proceed with installation? [Y/n]
(3/3) checking keys in keyring                       [############################] 100%
(3/3) checking package integrity                     [############################] 100%(3/3) loading package files                          [############################] 100%(3/3) checking for file conflicts                    [############################] 100%
:: Processing package changes...                                                        
(1/3) installing archlinux32-keyring                 [############################] 100%==> Appending keys from archlinux32.gpg...
==> Locally signing trusted keys in keyring...                                            -> Locally signing key CE0BDE71A759A87F23F0F7D8B61DBCE10901C163...                      -> Locally signing key 2FF1E976D6EB2E954A87DC14443904EC9EC51A8A...
  -> Locally signing key D92CDDC155BCC8F550B5FCEC30AB721FE7400FCD...                      -> Locally signing key A0B250C0FC9FC079EC04ADB7A50C0F20AEC3AF00...                      -> Locally signing key 194E37A47A4C671807BACB37B1117BC1094EA6E9...
==> Importing owner trust values...                                                     gpg: inserting ownertrust of 4                                                          gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4                                                          gpg: setting ownertrust to 4                                                            gpg: inserting ownertrust of 4
==> Disabling revoked keys in keyring...                                                  
-> Disabling key C3A8190912128B5A2E96C6023ED6490AEF932C8A...                            
-> Disabling key 7C98C4C3DE926168DC46FBAA3D06644243BF68D3...

==> Updating trust database...                                                          gpg: marginals needed: 3  completes needed: 1  trust model: pgp                         gpg: depth: 0  valid:   1  signed:   3  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   3  signed:   1  trust: 0-, 0q, 0n, 3m, 0f, 0u                   gpg: depth: 2  valid:   1  signed:   0  trust: 1-, 0q, 0n, 0m, 0f, 0u                   
gpg: next trustdb check due at 2020-12-31

(2/3) reinstalling openssl                           
[############################] 100%
(3/3) upgrading pacman                               
[############################] 100%
warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew

New optional dependencies for pacman                                                        perl-locale-gettext: translation support in makepkg-template                        
:: Running post-transaction hooks...

(1/1) Arming ConditionNeedsUpdate...                                                    
pacman-conf: error while loading shared libraries: 
libcrypto.so.1.1: cannot open shared object file: No such file or directory

pacman-conf: error while loading shared libraries: 
libcrypto.so.1.1: cannot open shared object file: No such file or directory

Why is pacman? Edit: I asked this question, but the answer is irrelevant now. This is because the update code sequence has been revised.

(2/3) reinstalling openssl
(3/3) upgrading pacman

Last edited by SDRausty (2020-10-29 22:00:59)

SDRausty · 2020-10-29 17:40:21

levi wrote:

look at the date of pacman and pick any packages for libs it turns out it depends on (such as libcrypto which comes from openssl) from just before that date.

I tried this many times yesterday and today, as well. Pacman always seems to want the other libraries.

The testharness used in attempting to resolve this issue for emulated x86 computer architecture in Android is presented here:

setupTermuxArch p
mkdir ~/arch ; cp ~/archlinux-bootstrap-2017.03.01-i686.tar.gz ~/arch/
setupTermuxArch q

SDRausty · 2020-10-29 17:52:38

levi wrote:

newer isos available here: https://archive.archlinux32.org/iso/
... shouldn't be beyond the wit of man to make a rootfs tar.gz file from an iso ... discovered that it's basically a root fs under a root.i686 folder

Creating a root file system is a rather simple thing to do after installing the system itself; As far as I understand it, it is simply zipping a brand newly installed system into a tar.gz file right after installing the system.

Is the maintainer of the isos published at https://archive.archlinux32.org/iso/ able to also maintain a current rootfs? Do they know about this topic we are discussing here?

Last edited by SDRausty (2020-10-29 17:56:54)

levi · 2020-10-29 18:01:46

I would assume the maintainer is a user or more likely an administrator here. They have the opportunity to read this thread, although it's a bit hard going so I wouldn't blame them if they didn't.

You don't even need an installed system to create a rootfs. I think I explained above how you can do it on any linux system (and probably a mac with enough homebrew on it) using the iso. I must admit it's looking increasingly like that might be the easiest thing to do, given the trouble you're apparently having finding matching packages for an updated pacman.

SDRausty · 2020-10-29 21:50:01

levi wrote:

You don't even need an installed system to create a rootfs. I think I explained above how you can do it on any linux system (and probably a mac with enough homebrew on it) using the iso.

If I only knew a way how to do this without a mount command, then I would not be pursuing this solution I'm stuck at, at present.

Android has certian limitations. One of them is that the mount command doesn't work in Android; Do you know a way how to access the ISO without the mount command from the command line? There are command line commands that can extract an ISO. Do you know any?

Last edited by SDRausty (2020-10-29 21:50:45)

SDRausty · 2020-10-29 21:56:21

Thank you for hanging in there with me on this topic.
Do you know when the zst compression format update began to change?

levi · 2020-10-29 21:57:33

Can't you use the 2017 era archlinux install to do it? That should be functional enough to do it I'd have thought. I'd do the downloading of the iso on a more updated system that's arguably more secure, but if you can put that somewhere the 2017 arch can see it, you could use that presumably.

Edit: The switch the zst compression happened around new year this year. Here's the appropriate news post from the upstream project. It does contain a curious suggestion that might help you also, Eli Schwartz has created a package called pacman-static and does provide builds for i686. That being a static build should contain all significant libs needed to run it.

Last edited by levi (2020-10-29 22:16:23)

SDRausty · 2020-10-29 22:05:37

levi wrote:

Can't you use the 2017 era archlinux install to do it?

I can do it any Arch Linux that I want to with the exception of Arch Linux 32 as long as it is in my Android smartphone. And as I mentioned the mount command does not work. Do you know an alternative command to the mount command as far as unpacking an ISO is concerned?

SDRausty · 2020-10-29 22:09:11

Do I understand correctly what I need the mount command for? This command is to unpack the ISO, or to install?

SDRausty · 2020-10-29 22:19:34

SDRausty wrote:

the mount command [in Android]

This issue https://github.com/termux/termux-packag … ssue+mount has been closed for over a year now. It appears that it is possible to get the mount command to work, but not doable

levi · 2020-10-29 22:23:33

You don't need to unpack it. Just mount it to a folder on you system and it should become accessible to you; that's what mounting does. With that you can repack it into a tar.gz or whatever you need, which will effectively take up disc space, but you only need enough space for the compressed image and some ram.

SDRausty · 2020-10-30 00:50:20

levi wrote:

You don't need to unpack it. Just mount it to a folder on you system and it should become accessible to you;

I understand what you're saying and I understand these steps.

SDRausty wrote:

as I mentioned the mount command does not work [on Android]

SDRausty · 2020-10-30 12:44:55

Packages (4) archlinux32-keyring-20191103-1.0  
libgcrypt-1.8.5-2.0
openssl-1.1.1-1.0  
pacman-5.2.1-1.4

pacman: error while loading shared libraries: 
libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

Continuing the upgrade method to get this project going; if I were to choose different versions of pacman, should I go up in the versioning or down? It seems from what you said levi, I should go up to get the zst compression to work. Am I correct?

Last edited by SDRausty (2020-10-30 12:45:25)

SDRausty · 2020-10-31 01:01:14

I have searched the import key topic extensively with multiple search engines and have learned quite a lot about Arch Linux keys, but I still do not have an answer to this question:

The task I am currently trying to achieve should be quite simple by any standard:
1. Download Arch Linux 32 package,
2. Install this ancient Arch Linux 32 package.

The key may or may not have been expired. The UNTRUSTED pacman setting solution is unpreferred. If this key is rejected, how can it be imported directly from the downloaded package which was downloaded using the https protocol? How can it be imported directly from the package?

What is the easiest way to import a key directly from a downloaded package in Arch Linux 32? Is there a way to query an Arch Linux package for its' key so another linux command can import this key from the package?

Last edited by SDRausty (2020-10-31 01:03:41)

SDRausty · 2020-10-31 01:48:21

levi wrote:

You don't need to unpack it. Just mount it to a folder on you system and it should become accessible to you

This is the point I am trying to drive home. My devices are not boxes with screens and keyboards. Nor are my devices laptops, notebooks and similar.
The devices I prefer at present are in the category of handhelds, smartTV and VR. There are more Android devices, as far as I know, that Arch Linux 32 should be able run on.

This short list of devices can easily be expanded by the systems that Termux runs on. Termux works on other operating systems than Android. I have successfully installed different versions of Arch Linux in my smartphone using Termux and the TermuxArch installer since 2017, but cannot currently successfully install Arch Linux 32.

Proof of this is that all the Arch Linux versions appear to work well, including Arch Linux 32:

SDRausty wrote:

[12:00~]$ uname -m
aarch64
[12:00~]$ startarch+armeabi-v7a c uname -m
armv7l
[12:00~]$ startarch+x86_64 c uname -m
x86_64
[12:01~]$ startarch+x86 c uname -m
i686
[12:01~]$ startarch c uname -m
aarch64

Arch Linux installs and configures on Android 7+ smartphone very smoothly as it uses a published root file system in addition to the published iso files. But Arch Linux 32 does not get this far presently as all the two Arch Linux architecture versions. If there are other available architectures, please let me know.

levi wrote:

it should become accessible

The mount command is inaccessible on traditional Android handheld. By traditional, I mean bought through a store and given vanilla wrapped.

As far as I know, the Android code is open source and the vanilla wrapped can be unwrapped on the insides as well. Google vanilla wraps it for us at the store. We get them for free without contract, by the way. A one month minimum prepaid submission is what is required.

As the mount command is inaccessible in Android, what other commands can be used with the iso file to achieve the task of creating a root file system?

SDRausty · 2020-10-31 02:21:44

Packages (4) 
archlinux32-keyring-20200408-1.0  
lzo-2.10-3.0  
libarchive-3.2.2-3
pacman-5.2.1-1.4

downloading required keys...
:: Import PGP key 2048R/C8E8F5A0AF9BA7E7, "Andreas Baumann (sign) <mail@andreasbaumann.cc>", 
created: 2017-11-02? [Y/n]
:: Import PGP key 4096R/255A76DB9A12601A, "Erich Eckner (just to sign arch packages) <arch-packages@eckner.net>", 
created: 2018-04-09? [Y/n]
(3/4) checking package integrity                     [############################] 100%

These results are now added to a nested for loop that assits with this topic of attempting to install Arch Linux 32 in Android arm7/aarch64 smartphones with TermuxArch that uses Termux PRoot and QEMU which permits architecture emulation.

Last edited by SDRausty (2020-10-31 04:57:33)

levi · 2020-10-31 05:57:09

My apologies then. I was under the impression you had the 2017 archlinux 32-bit image installed, and were able to use that. It should dump you into a root login as far as I know. I was suggesting you could use mount in that, but if that's not possible then I've misunderstood something.

SDRausty wrote:

What is the easiest way to import a key directly from a downloaded package in Arch Linux 32? Is there a way to query an Arch Linux package for its' key so another linux command can import this key from the package?

That's not a supported way of working, but it shouldn't be rocket science to figure it out. If you try to install a package without having its key installed using pacman it will report the key's ID, and you can use that to run gpg --homedir /etc/pacman.d/gnupg --recv-keys although I don't know the best server to use off hand.

SDRausty · 2020-11-02 23:44:58

Thank you for helping with this topic levi! This process went much smoother with your input.

SOLVED: I have managed to upgrade pacman, and the system installs and configures as expected with this 'git' commit. If you wish to try installing in Android, the Arch Linux 32 installer for Android is available here.

NOTE: The TermuxArch command 'orcaconf' that is currently being designed to assist visually impaired users of Arch Linux also appears to work correctly in Arch Linux 32.

Last edited by SDRausty (2020-11-04 22:18:02)

levi · 2020-11-03 08:28:40

Glad to be of service

Title updated.

SDRausty · 2020-11-05 15:31:43

levi wrote:

Glad to be of service
Title updated.

Thank you for updating the title levi, and thank you very much for taking time with this quest. Unfortunately with the most recent testing of the command 'setupTermuxArch qemu' with option 4) x86 with this installation and configuration script; It now fails with errors. The most recent developments are at this link. Testing is requested.

Note: Please note when testing on a standalone Android smartphone, please backup your work before continuing with testing.

Edit: Note 2: Even if stability with the approach that we have taken now is reachieved (updating the ancient 2017 root file system, as opposed to publishing a current rootfs along with the published Arch Linux 32 isos the Arch Linux 32 project graces us with), I believe publishing an updated rootfs is the most stable approach to resolving this topic.

Do you agree?

Last edited by SDRausty (2020-11-05 16:04:52)

Arch Linux

#51 2020-10-28 21:06:59

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#52 2020-10-29 01:35:03

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#53 2020-10-29 04:38:12

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#54 2020-10-29 06:12:06

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#55 2020-10-29 16:51:24

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#56 2020-10-29 17:23:54

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#57 2020-10-29 17:40:21

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#58 2020-10-29 17:52:38

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#59 2020-10-29 18:01:46

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#60 2020-10-29 21:50:01

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#61 2020-10-29 21:56:21

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#62 2020-10-29 21:57:33

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#63 2020-10-29 22:05:37

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#64 2020-10-29 22:09:11

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#65 2020-10-29 22:19:34

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#66 2020-10-29 22:23:33

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#67 2020-10-30 00:50:20

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#68 2020-10-30 12:44:55

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#69 2020-10-31 01:01:14

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#70 2020-10-31 01:48:21

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#71 2020-10-31 02:21:44

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#72 2020-10-31 05:57:09

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#73 2020-11-02 23:44:58

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#74 2020-11-03 08:28:40

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

#75 2020-11-05 15:31:43

Re: [SOLVED - Hurrah!] Upgrading from a truly ancient install

Board footer