Installing XBPS Package Manager in Fossapup64

[rockedge]

@wiak

I finally completed a successful build of xbps in Puppy Linux! I am in the process of reading what I can on setting it up to actually communicate with some repos. First to learn where and how then figure out what repos to use and how xbps-install will function.

Screenshot.png (346.95 KiB) Viewed 1403 times

Screenshot(1).png (98.55 KiB) Viewed 1400 times

[rockedge]

So I gave it a run before I go any further attempting to integrate the Puppy Linux repos if at possible. And surprised a bit xbps updated the void repos and began to install xscreensaver with:

Code: Select all

xbps-install -Sy xscreensaver

It made it this far but looks like a certificate and setting up the keys

Code: Select all

libXft-2.3.3_1: collecting files...
glu-9.0.1_1: collecting files...
xscreensaver-5.45_1: collecting files...

[*] Unpacking packages
glibc-2.32_1: unpacking ...
File `./etc/rpc' exists, installing configuration file to `./etc/rpc.new-2.32_1'.
File `./etc/ld.so.conf' exists, installing configuration file to `./etc/ld.so.conf.new-2.32_1'.
File `./etc/gai.conf' exists, installing configuration file to `./etc/gai.conf.new-2.32_1'.
libXau-1.0.9_1: unpacking ...
libXdmcp-1.1.3_1: unpacking ...
libxcb-1.14_1: unpacking ...
libX11-1.7.0_1: unpacking ...
libglvnd-1.3.2_1: unpacking ...
libICE-1.0.10_2: unpacking ...
libuuid-2.36_1: unpacking ...
libSM-1.2.3_1: unpacking ...
libXt-1.2.0_1: unpacking ...
zlib-1.2.11_3: unpacking ...
libzstd-1.4.8_1: unpacking ...
liblzma-5.2.5_1: unpacking ...
bzip2-1.0.8_1: unpacking ...
libelf-0.182_4: unpacking ...
libpcre-8.44_1: unpacking ...
libffi-3.3_2: unpacking ...
libblkid-2.36_1: unpacking ...
libmount-2.36_1: unpacking ...
glib-2.66.2_1: unpacking ...
ncurses-libs-6.2_4: unpacking ...
libreadline8-8.1.000_1: unpacking ...
libgcc-10.2.1pre1_2: unpacking ...
libstdc++-10.2.1pre1_2: unpacking ...
icu-libs-67.1_1: unpacking ...
libxml2-2.9.10_4: unpacking ...
shared-mime-info-2.1_1: unpacking ...
/bin/sh: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
ERROR: shared-mime-info-2.1_1: [unpack] INSTALL script failed to execute pre ACTION: Key has expired
ERROR: shared-mime-info-2.1_1: [unpack] failed to unpack files from archive: Key has expired
Transaction failed! see above for errors.

Also now the system is acting strangely which I will investigate

Code: Select all

id: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
id: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
id: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
bash: [: too many arguments
id: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
mkdir: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
uname: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE
grep: symbol lookup error: /usr/lib/libc.so.6: undefined symbol: _dl_fatal_printf, version GLIBC_PRIVATE

libc was in some way altered and now the system is broken!
The system will not boot and immediately shows the above error.

Will delete the save folder and start over.

[wiak]

Yes, you may likely find it very dodgy to try to integrate xbps in this manner. I am able to integrate Ubuntu Focal dpkg/apt, but that is because I am using compatible libs and apps (since FossaPup using same repos anyway). Note therefore that when I build an dpkg/apt plugin for Bionic it is a completely different addon since has to use matching libs and apps.

What could be done possibly (with muchos work) would be to cut FossaPup down to next to nothing - just enough to boot with Puppy initrd/init, and then replace any still existing libs with Void Linux versions, reboot, and then add xbps package manager. The end result would be like a WeeDogLinux Void flavour but using Puppy initrd/init (PUPMODES and so on) instead of WeeDogLinux initrd/init, and using xbps instead of PPM. In other words it would be one way to produce a Puppy Void. A Puppy Void could no doubt be engineered into woof-CE as an alternative, but that would not have the advantage of using official Void xbps (a woof-CE engineered Puppy Void would be using PPM/Pkg per the usual Pup - unless woof-CE was radically redesigned to use upstream distro's official package manager).

[rockedge]

First I was interested in seeing if I could compile it in Fossapup64, which it did and it ran. That's enough for now since the true integration would be labor intensive.

More of a proof of concept and no expectations that it would work as is.
But it does look cool....

Screenshot(1).png (337.26 KiB) Viewed 1380 times

[wiak]

It does look cool! And once that xbps 'working' stage is reached it certainly can be made to 'work' - to a greater or lesser extend depending how far you go with working towards compatibility between what xbps is likely to bring down and what Ubuntu Focal repos install - afterall alien packages often work in practice so could end up as a very interesting addition.

[rockedge]

@wiak

Even cooler.....

Screenshot(3).png (175.05 KiB) Viewed 1355 times

[wiak]

@wiak

Even cooler.....

Screenshot(3).png

Hahaha. You are becoming extreme!