Is there interest in an Arch32 Pup???

[peebee]

I am attempting to build with a Bionic64-v8, I am switching over to a 32 bit Bionic

Line #1 of instructions!!!!

Why not build with Arch32Pup?

[darry19662018]

sudden problems with +10!

I have a system made with the delta +9 and a save folder. deleted everything but the save folder and replaced with +10.

on boot all goes well until the tray is being generated and suddenly geany appears with the freememapplet.desktop opened

the system freezes and I have to eventually perform a hard restart.

will now attempt a boot with no save folder present

Had the same problem with installing xine after dong that I had the same problem.

Tried installing Xine with Peebee's latest iso and this os still a bug in the latest iso from Peebee.

[rockedge]

I am now going to build from woof-CE hosted by ArchPup32

Note: there was no git in the devx and had to install from PPM which lead to the small error on the way:

Code: Select all

# git clone https://github.com/techrockedge/woof-CE.git woof-CE-testingCloning into 'woof-CE-testing'...
fatal: unable to access 'https://github.com/techrockedge/woof-CE.git/': error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none

a certificate problem. I've encountered this before but for now pressing forward, using the zip version for now. all components are in place.

@darry19662018 I am keeping an eye out for this as well. Has not happened again but I have not put ArchPup through anything strenuous as of late but going to be running woof-CE and we will see how it goes

[s243a]

I am now going to build from woof-CE hosted by ArchPup32

Note: there was no git in the devx and had to install from PPM which lead to the small error on the way:

Code: Select all

# git clone https://github.com/techrockedge/woof-CE.git woof-CE-testingCloning into 'woof-CE-testing'...
fatal: unable to access 'https://github.com/techrockedge/woof-CE.git/': error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none

a certificate problem. I've encountered this before but for now pressing forward, using the zip version for now. all components are in place.

@darry19662018 I am keeping an eye out for this as well. Has not happened again but I have not put ArchPup through anything strenuous as of late but going to be running woof-CE and we will see how it goes

For the cert issue you can try this pet:

arch_certs-1.pet

I wasn't going to release it yet because there is something that I'm missing in order to get the certs to work properly with firefox, but the pet covers most of what I've done. I got firefox certs working in a few versions of arch32pup but can't yet figure out the recipe.

The pet installs three packages, which you'll find in /var/tmp, if you extract the pet. These are:
ca-certificates-20181109-3.0-any.pkg.tar.zst
ca-certificates-mozilla-3.51-1.0-pentium4.pkg.tar.zst
ca-certificates-utils-20181109-3.0-any.pkg.tar.zst
*You will be prompted as to whether or not you want to install each pet
**There are from the arch repos

It also installs the following files:

Code: Select all

/usr/sbin/nss-systemcerts-import
/etc/ca-certificates/update.d/nss-systemcerts-import

From:
https://github.com/rbarrois/nss-systemc ... rts-import

It also installs the file:
/usr/sbin/update-ca-certificates
** from the ca-certificates package of debian (sid)


Here is the pinstall.sh script:

Code: Select all

#!/bin/sh
for a_pkg in ca-certificates-20181109- ca-certificates-mozilla ca-certificates-utils-20181109-; do
  petget /var/tmp/$a_pkg*
done
mv /etc/ca-certificates.conf /etc/ca-certificates.conf_back_$$
( cd /usr/share/ca-certificates
 find . -name '*.crt' | sed 's#^./##' > /etc/ca-certificates.conf
)
nss-systemcerts-import
update-ca-certificates
update-ca-trust
for a_profile in /root/.cache/mozilla/firefox/*; do
  mv $a_profile/pkcs11.txt $a_profile/pkcs11.txt_back$$ && \
  cp /etc/pki/nssdb/pkcs11.txt $a_profile/pkcs11.txt
done

**Comments and blank lines removed. See pastebin link for the comments:
https://pastebin.com/AhrEMnyC

P.S. I found something in woof-CE that does some of what is in my above pinstall.sh script. However, I don't know if this HACK is done in arch32pup and if it is I don't think that it is working correctly. See:
woof-CE/woof-code/packages-templates/ca-certificates/

[rockedge]

for some crazy reason I still have not had a smooth run of an ArchPup built with woof-CE on either ArchPup32 or Bionic32. The error continues to be

Code: Select all

cat: sandbox0/archtemp/desc: Not a directory

no matter what adjustment I've made following the instructions. At some point I will find out what I'm doing wrong here!

But I did manage to construct a WeeDog32 (Void Linux) using wiak's scripts in ArchPup, The build was totally successful and used the firstrib00-32-auto.plug

This WeeDog32 is running idling at 99.3 megabytes of used RAM

[s243a]

I created a script to make the tarball. See:

https://pastebin.com/CMEPStet

it uses a list of files and directories to include in the tarball:

Code: Select all

'_00build_2.conf'
'_00build.conf'
'0setup'
'DISTRO_COMPAT_REPOS-arch-32'
'DISTRO_PET_REPOS'
'DISTRO_PET_REPOS-user'
'DISTRO_PKGS_SPECS-arch'
'DISTRO_SPECS'
'huge_kernel/*'
'packages-pet/*'
'Packages-puppy-a32pup-extra'
'packages-templates/*'
'README.md'
'sandbox3/*'
'support/*'
'woof-output-a32pup-20.03/*'

https://pastebin.com/B14vECva

The output can actually be a directory in which case the cpio command is used:

Code: Select all

find . -wholename "./$a_file2" | cpio -pdu "$OUT_FILE_PATH"

or a tar archive, in which case first the tar command is used:

Code: Select all

 if [ -f "$PRE_OUT_FILE_PATH" ]; then            
   tar -r -f "$PRE_OUT_FILE_PATH" $a_file2
 else
   tar -cf "$PRE_OUT_FILE_PATH" $a_file2
 fi

and then the gunzip command:

Code: Select all

case "$OUT_FILE_PATH" in
*.gz)
  #set +x
  gzip -c "$PRE_OUT_FILE_PATH" > "$OUT_FILE_PATH" && rm "$PRE_OUT_FILE_PATH"
  ;;
esac

at the top of the script there is a variable called "out_type" which determines if the output is a file or directory. If the output is a directory it will overwrite the contents of the target (this is the -u option of cipo). The idea of the directory output is to overwrite the files of the woof-CE output (of ./merge2out) that we want. Otherwise we can overwate specific files in the woof-CE output (of ./merge2out) by extracting the tarball as per peebee's instructions.

Code: Select all

IN_FILE="$(realpath ./woof-CE-out-replace.lst)"
out_type=file
case "$out_type" in
directory)
  OUT_FILE=arch32_tarball4woof_ce-20200314
  mkdir -p "$OUT_FILE"
  ;;
*)
  OUT_FILE=arch32_tarball4woof_ce-20200314.tar.gz
  ;;
esac

[s243a]

I am now going to build from woof-CE hosted by ArchPup32

Note: there was no git in the devx and had to install from PPM which lead to the small error on the way:

Code: Select all

# git clone https://github.com/techrockedge/woof-CE.git woof-CE-testingCloning into 'woof-CE-testing'...
fatal: unable to access 'https://github.com/techrockedge/woof-CE.git/': error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none

a certificate problem. I've encountered this before but for now pressing forward, using the zip version for now. all components are in place.

@darry19662018 I am keeping an eye out for this as well. Has not happened again but I have not put ArchPup through anything strenuous as of late but going to be running woof-CE and we will see how it goes

I opened this file as text. It's on my system (perhaps due to this). It seems to contain the signatures of all the certificates in my system. After reading this I recalled something I read on archwiki:

Run

Code: Select all

trust anchor --store myCA.crt 

as root.

The certificate will be written to /etc/ca-certificates/trust-source/myCA.p11-kit and the "legacy" directories automatically updated.

If you get "no configured writable location" or a similar error, import the CA manually:

Copy the certificate to the /etc/ca-certificates/trust-source/anchors directory.
Run

Code: Select all

update-ca-trust

as root.

For more information, see the update-ca-trust(8 ) manual page.

https://wiki.archlinux.org/index.php/Us ... ertificate

What I'm wondering is if instead of typing:

Code: Select all

trust anchor --store myCA.crt

I type

Code: Select all

trust anchor --store /etc/ssl/certs/ca-certificates.crt

clearly I need to do some more reading and/or experimentation.

Edit: here is some related stuff that looks usefull:
https://bgstack15.wordpress.com/2018/10 ... tificates/

[s243a]

Thanks! I have downloaded and setup a github repo

https://github.com/techrockedge/archpup32

I can provide commits, push access for you s243a and peebee if needed.

once a 64 bit is under way I will fork a version as well

Hello rockedge,

could you kindly provide some more info abou this commit:
add woof-CE components - 89772c4

I left some comments on the commit.

[s243a]

for some crazy reason I still have not had a smooth run of an ArchPup built with woof-CE on either ArchPup32 or Bionic32. The error continues to be

Code: Select all

cat: sandbox0/archtemp/desc: Not a directory

no matter what adjustment I've made following the instructions. At some point I will find out what I'm doing wrong here!

But I did manage to construct a WeeDog32 (Void Linux) using wiak's scripts in ArchPup, The build was totally successful and used the firstrib00-32-auto.plug

This WeeDog32 is running idling at 99.3 megabytes of used RAM

I have a hypothesis here and under this hypothesis this isn't an error that you need to wory about. My hypothesis is that prior to running any commands in the pipe an empty file is created for the output of the pipe (i.e. sandbox0/archtemp)

Code: Select all

 ' > sandbox0/archtemp

0setup#L91

This error is nothing to worry about provided the repo files are updated:

Code: Select all

for arepo in core extra community ; do

0setup#L22

The repo files that this script should update are:

Code: Select all

Packages-arch-32-core
Packages-arch-32-extra
Packages-arch-32-community

If you aren't sure if they are being created, delete them and see if the script creates them. Also if you have up to date versions of these files then you don't have to run the 0setup script.

There are two (primary) ways that we can fix this error. We can either not write the output to the sandbox0 directory. Alternatively, we can use the "grep -v" statment to delete archtemp from the list of packages (the directories have the name of the package) that we feed to the awk script. Actually there is a third option. The third option is rather than writing to standard out the awk script can write specifically to a file. For example:

Code: Select all

printf("%s-%s|%s|%s|%s|%s|%s|%s|\n", pkgname, pkgverarr[1], pkgname, pkgverarr[1], pkgverarr[2],provides,mkdeps,optdeps) >> "sandbox0/archtemp2"

0setup#L42 (testing branch)

I noticed that this above statement doesn't seem to cause the same problem as when we write to standard out.

[s243a]

In my latestest testing of this build system, I think I forgot to delete package.pet.

So what I did was moved the folder with the downloaded pets from

Code: Select all

woof-out_arch32/packages-pet

to

Code: Select all

../local-repositories/x86/packages-pet

The reason I did this is that this is how I think the setup is supposed to be per:

Code: Select all

[ ! -e packages-pet ] && ln -s ../local-repositories/${WOOF_TARGETARCH}/packages-pet packages-pet # check exist.

woof-code/_00func#L89

Although, I'm not sure that this symlink creation code actually works properly.

[rockedge]

Hello s243a

interesting point. I will also run a build and keep what you did in mind and repeat it.

[peebee]

OT

Arch64Pup....alpha "proof of concept"...........

http://www.smokey01.com/peebee/downloads/a64pup/

Kernel 5.5.10

Were some challenges, particularly around the fact that Arch64 has yet another lib architecture that is different to both Slackware and Debian/Ubuntu.

The non-standardisation in the 64-bit Linux world over lib architectures is the main reason I prefer to stick with 32-bit.....

Sylpheed does not work on either 32-bit or 64-bit - symbol errors suggest a new version is required.

[peebee]

sylpheed-3.7.0 produced by OscarTalks for ScPup32 works:

http://murga-linux.com/puppy/viewtopic. ... 70#1021170

needs amended repo db attached with -false.gz

[s243a]

OT

Arch64Pup....alpha "proof of concept"...........

http://www.smokey01.com/peebee/downloads/a64pup/

Kernel 5.5.10

Were some challenges, particularly around the fact that Arch64 has yet another lib architecture that is different to both Slackware and Debian/Ubuntu.

The non-standardisation in the 64-bit Linux world over lib architectures is the main reason I prefer to stick with 32-bit.....

Sylpheed does not work on either 32-bit or 64-bit - symbol errors suggest a new version is required.

Thankyou Peebee. I'll put this on my plate to try

[s243a]

I am now going to build from woof-CE hosted by ArchPup32

Note: there was no git in the devx and had to install from PPM which lead to the small error on the way:

Code: Select all

# git clone https://github.com/techrockedge/woof-CE.git woof-CE-testingCloning into 'woof-CE-testing'...
fatal: unable to access 'https://github.com/techrockedge/woof-CE.git/': error setting certificate verify locations:
  CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: none

a certificate problem. I've encountered this before but for now pressing forward, using the zip version for now. all components are in place.

@darry19662018 I am keeping an eye out for this as well. Has not happened again but I have not put ArchPup through anything strenuous as of late but going to be running woof-CE and we will see how it goes

For the cert issue you can try this pet:

arch_certs-1.pet

I wasn't going to release it yet because there is something that I'm missing in order to get the certs to work properly with firefox, but the pet covers most of what I've done. I got firefox certs working in a few versions of arch32pup but can't yet figure out the recipe.

The pet installs three packages, which you'll find in /var/tmp, if you extract the pet. These are:
ca-certificates-20181109-3.0-any.pkg.tar.zst
ca-certificates-mozilla-3.51-1.0-pentium4.pkg.tar.zst
ca-certificates-utils-20181109-3.0-any.pkg.tar.zst
*You will be prompted as to whether or not you want to install each pet
**There are from the arch repos

It also installs the following files:

Code: Select all

/usr/sbin/nss-systemcerts-import
/etc/ca-certificates/update.d/nss-systemcerts-import

From:
https://github.com/rbarrois/nss-systemc ... rts-import

It also installs the file:
/usr/sbin/update-ca-certificates
** from the ca-certificates package of debian (sid)


Here is the pinstall.sh script:

Code: Select all

#!/bin/sh
for a_pkg in ca-certificates-20181109- ca-certificates-mozilla ca-certificates-utils-20181109-; do
  petget /var/tmp/$a_pkg*
done
mv /etc/ca-certificates.conf /etc/ca-certificates.conf_back_$$
( cd /usr/share/ca-certificates
 find . -name '*.crt' | sed 's#^./##' > /etc/ca-certificates.conf
)
nss-systemcerts-import
update-ca-certificates
update-ca-trust
for a_profile in /root/.cache/mozilla/firefox/*; do
  mv $a_profile/pkcs11.txt $a_profile/pkcs11.txt_back$$ && \
  cp /etc/pki/nssdb/pkcs11.txt $a_profile/pkcs11.txt
done

**Comments and blank lines removed. See pastebin link for the comments:
https://pastebin.com/AhrEMnyC

P.S. I found something in woof-CE that does some of what is in my above pinstall.sh script. However, I don't know if this HACK is done in arch32pup and if it is I don't think that it is working correctly. See:
woof-CE/woof-code/packages-templates/ca-certificates/

http://www.murga-linux.com/puppy/viewto ... 25#1052825

I made a new version of this which instead of having the dependencies embedded in the .pet it will prompt the user to download and install the dependencies but only if installed by the petget command. If it is installed in the package manager then it will let the package manager handle the dependencies.

The new pet can be found at:
https://github.com/techrockedge/archpup ... -1.0.1.pet

Which is part of commit commit c607cb6.

Anyway, above is what it is supposed to do, I only tested the pinstall.sh script by its self. I'll do more testing on it tomorrow.

For related discussion see:
detecting if petget is called in pinstall.sh

The pinstall.sh script can be found at:
https://pastebin.com/bwyHBeX9
or by extracting it from the .pet

Also as noted, I'm probably still missing something to get certificates to work with firefox nss feature. I got to figure out what else I did to get them working on previous versions of arch32pup.

[rockedge]

I am seeing a lot of errors of not finding packages, ./3builddistro is failing as well.

Code: Select all

* Downloading firewallstatus_DEV-0.7-i686_s700.pet
  - from http://smokey01.com/peebee/slackocurrent/lxpup/pet_packages-slacko14.2
  failed (file not found on server or could not finish download)
  - from https://raw.githubusercontent.com/puppylinux-woof-CE/woof-CE-noarch/master/pet_packages-slacko14.2
  failed (file not found on server or could not finish download)
  - from http://distro.ibiblio.org/puppylinux/pet_packages-slacko14.2
/initrd/mnt/dev_sav 100%[===================>]   1.20K  --.-KB/s    in 0s      
  success
 flac-1.3.3-1.1-pentium4.pkg.tar.xz flex-2.6.4-3.0-pentium4.pkg.tar.xz
* Downloading fontconfig-2:2.13.91+24+g75eadca-2.1-pentium4.pkg.tar.zst
  - from https://mirror.archlinux32.org//pentium4/extra
 /initrd/mnt/dev_sa  37%[======>             ] 343.75K   121KB/s               

this is a sample and I have the fail logs as well.

Code: Select all

 schroedingerWARNING, PKG DOES NOT EXIST: packages-a32pup/sdl
WARNING, PKG DOES NOT EXIST: packages-a32pup/sed
 shared-mime-info speex squashfs-toolsWARNING, PKG DOES NOT EXIST: packages-a32pup/sqlite
 startup-notificationWARNING, PKG DOES NOT EXIST: packages-a32pup/strace
 streamripperWARNING, PKG DOES NOT EXIST: packages-a32pup/subversion
 svgalib sylpheed sysfsutils sys-info syslinuxWARNING, PKG DOES NOT EXIST: packages-a32pup/systemd-libs
 tar tas texinfo time unrar unzip urxvtset usb-modeswitch-data usb-modeswitch usbutilsWARNING, PKG DOES NOT EXIST: packages-a32pup/util-linux
 v4l-utils vamps viewnior vobcopy vteWARNING, PKG DOES NOT EXIST: packages-a32pup/wayland
 wget wireless-toolsWARNING, PKG DOES NOT EXIST: packages-a32pup/wpa_supplicant
 wvdial wv wvstreams xorgproto x264 x265 xarchive xcb-util xclip xcur2png xdelta xdg_puppy_jwm Xdialog xlock_gui xlockmoreWARNING, PKG DOES NOT EXIST: packages-a32pup/xorg_base_new
 xsaneWARNING, PKG DOES NOT EXIST: packages-a32pup/xserver_xorg
 xsoldier xtransWARNING, PKG DOES NOT EXIST: packages-a32pup/xvidcore
 xz yad yasm zip zlib zstd 00_apup32_fix
Please use the 'official' woofce busybox .pet package..

I am trying another 32 bit build (all attempts are on 32 bit system) I am building with Bionic32+15

[peebee]

I am seeing a lot of errors of not finding packages, ./3builddistro is failing as well.

Downloading is working - you're just seeing the repos tested in turn until the package is found and downloaded.

The other error looks like ./2createpackages has not run for the affected packages....did it run to completion? Suggest doing it again.

[rockedge]

I have in the ERROR-2createpackages.log a very long list like this:

Code: Select all

ERROR: ./packages-pet/alsa-lib-1.2.2-1.0-pentium4.pkg.tar.zst does not exist.
Please find a package that matches, place it in packages-deb-32,
then run this script again and choose to build alsa-lib.

ERROR: ./packages-pet/autoconf-2.69-7.1-any.pkg.tar.zst does not exist.
Please find a package that matches, place it in packages-deb-32,
then run this script again and choose to build autoconf.

I realize that the download script is testing the URL's until it finds the packages but I think my problem is in ./2createpackages and I will check /packages-deb-32 and further track down the error.

[rockedge]

the file alsa-lib-1.2.2-1.0-pentium4.pkg.tar.zst for example is no where to be found. Seems at some point the downloads are incomplete and then the 2createpackages script is failing to build anything. the only file I am seeing in the output directory:
/woof-out_arch32/woof-output-a32pup-20.03/iso-rename.sh

./3builddistro is failing immediately so no ISO is ever created

[s243a]

Here's some more info on ssl certificates in archlinux:

ca-certificates
Is just an anchor point, other packages depend on.
ca-certificates-mozilla
Contains only the /usr/share/ca-certificates/trust-source/mozilla.trust.p11-kit file, generated from the Mozilla CA Certificate Store, which is also part of NSS (/usr/lib/libnssckbi.so).
ca-certificates-utils
Provides the update-ca-trust(8 ) script and the same-named pacman hook.
p11-kit
Provides the trust(1) utility.

https://wiki.archlinux.org/index.php/Tr ... r_Security

What it doesn't seem to document is that in the package "ca-certificates" is the utility "update-ca-certificates", so I don't have to grab this script from debian.