Line #1 of instructions!!!!rockedge wrote:I am attempting to build with a Bionic64-v8, I am switching over to a 32 bit Bionic
Why not build with Arch32Pup?
Line #1 of instructions!!!!rockedge wrote:I am attempting to build with a Bionic64-v8, I am switching over to a 32 bit Bionic
Tried installing Xine with Peebee's latest iso and this os still a bug in the latest iso from Peebee.darry19662018 wrote:Had the same problem with installing xine after dong that I had the same problem.rockedge wrote: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
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
For the cert issue you can try this pet:rockedge wrote: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:a certificate problem. I've encountered this before but for now pressing forward, using the zip version for now. all components are in place.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
@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
Code: Select all
/usr/sbin/nss-systemcerts-import
/etc/ca-certificates/update.d/nss-systemcerts-import
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
Code: Select all
cat: sandbox0/archtemp/desc: Not a directory
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/*'
Code: Select all
find . -wholename "./$a_file2" | cpio -pdu "$OUT_FILE_PATH"
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
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
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
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:rockedge wrote: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:a certificate problem. I've encountered this before but for now pressing forward, using the zip version for now. all components are in place.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
@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
https://wiki.archlinux.org/index.php/Us ... ertificateRunas root.Code: Select all
trust anchor --store myCA.crt
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.
Runas root.Code: Select all
update-ca-trust
For more information, see the update-ca-trust(8 ) manual page.
Code: Select all
trust anchor --store myCA.crt
Code: Select all
trust anchor --store /etc/ssl/certs/ca-certificates.crt
Hello rockedge,rockedge wrote: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
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)rockedge wrote: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 beno matter what adjustment I've made following the instructions. At some point I will find out what I'm doing wrong here!Code: Select all
cat: sandbox0/archtemp/desc: Not a directory
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
Code: Select all
' > sandbox0/archtemp
Code: Select all
for arepo in core extra community ; do
Code: Select all
Packages-arch-32-core
Packages-arch-32-extra
Packages-arch-32-community
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"
Code: Select all
woof-out_arch32/packages-pet
Code: Select all
../local-repositories/x86/packages-pet
Code: Select all
[ ! -e packages-pet ] && ln -s ../local-repositories/${WOOF_TARGETARCH}/packages-pet packages-pet # check exist.
Thankyou Peebee. I'll put this on my plate to trypeebee wrote: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.
http://www.murga-linux.com/puppy/viewto ... 25#1052825s243a wrote:For the cert issue you can try this pet:rockedge wrote: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:a certificate problem. I've encountered this before but for now pressing forward, using the zip version for now. all components are in place.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
@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
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:From:Code: Select all
/usr/sbin/nss-systemcerts-import /etc/ca-certificates/update.d/nss-systemcerts-import
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:
**Comments and blank lines removed. See pastebin link for the comments: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
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/
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
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..
Downloading is working - you're just seeing the repos tested in turn until the package is found and downloaded.rockedge wrote:I am seeing a lot of errors of not finding packages, ./3builddistro is failing as well.
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.
https://wiki.archlinux.org/index.php/Tr ... r_Securityca-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.