Puppy Linux Discussion Forum

Hi @fredx181, you offered:

Other options...:

1. - ISO containing all Desktop variants to choose from, but one is default, so then in the Menu e.g. Start XFCE, Start Openbox, Start JWM etc...

2. - ISO containing only one default Desktop, e.g XFCE, and have in the Menu the options to download and install several other Desktop variants from .xbps packages.

I agree with @rockedge that #1 might be best for several reasons that I can think of:

• Removes the ability for a user to make mistakes requiring forum support

• Easy to manage as its a 'singularity' for development understanding and for user use

• Makes offline use, once the ISO file is downloaded, a no-brainer as all desktops are contained

• Users work well when on a desktop vs text based selections and thought that often get confused

There are additional reasons, I am sure.

Edit: Attempt to make the point 'Users work ...' readable.

As I mentioned before KLV is really close to being a daily driver for me. I really have one application to install which would need to be compiled, that being Frescobaldi, a graphical lilypond file editor. I'm currently looking at the python versions necessary etc.

That set aside for the moment, I started to consider the use of pulse audio and have been trying to get a handle on how it works. There are some good descriptions I'm reading in the ArchWiki, https://wiki.archlinux.org/title/PulseAudio and https://www.freedesktop.org/wiki/Softwa ... r/Modules/

Of particular note I was getting a little insight on how Pulse Audio interacts with ALSA, from the ArchWiki:

Back-end configuration
ALSA
Warning: Do not attempt to change the ALSA configuration files while using the default PulseAudio configuration. The default configuration grabs the hardware devices directly in order to allow all the on-the-fly configurations using the GUIs. Changes to the ALSA configurations will very likely be ignored by PulseAudio and ALSA applications will break randomly while trying to access an ALSA device already used by PulseAudio. If you intend to change the ALSA configurations, also configure PulseAudio manually to output to your own ALSA device and play nice with your configuration.

If you have applications that do not support PulseAudio explicitly but rely on ALSA, these applications will try to access the sound card directly via ALSA and will therefore bypass PulseAudio. PulseAudio will thus not have access to the sound card any more. As a result, all applications relying on PulseAudio will not be working any more, leading to this issue: https://wiki.archlinux.org/title/PulseA ... t_detected

To prevent this, you will need to install the pulseaudio-alsa package. It contains the necessary /etc/alsa/conf.d/99-pulseaudio-default.conf for configuring ALSA to use PulseAudio. Also make sure that ~/.asoundrc does not exist, as it would override the /etc/asound.conf file.

Also install lib32-libpulse and lib32-alsa-plugins if you run a x86_64 system and want to have sound for 32-bit multilib programs like Wine and Steam.

To prevent applications from using ALSA's OSS emulation and bypassing PulseAudio (thereby preventing other applications from playing sound), make sure the module snd_pcm_oss is not being loaded at boot. If it is currently loaded (lsmod | grep oss), disable it by executing:

# rmmod snd_pcm_oss

My question is basically: How is pulse audio configured in KLV?

So I am not looking to turn KLV into an 'audio-distro," I would still like to have a good working knowledge of how to configure applications, pulse, and ALSA to get the most out of it.

EDIT/NOTE: So @rockedge I just used the system wide update command you suggested in the terminal, and that was rather fun. Thanks! Looks like it updated without any issues.

@geo_c This is how the audio components are installed and configured when KLV was built from script and PLUG file:

# Install Audio
#
xbps-install -y pulseaudio pulseaudio-utils alsa-plugins-pulseaudio alsa-utils ffmpeg
ln -s /etc/sv/pulseaudio /etc/runit/runsvdir/default/pulseaudio

Then in /root/Startup/start_pulseaudio PulseAudio is actually started up at system start

#!/bin/sh
pulseaudio --start

rockedge wrote: ↑Thu Jun 02, 2022 1:57 pm

Code: Select all

# Install Audio
#
xbps-install -y pulseaudio pulseaudio-utils alsa-plugins-pulseaudio alsa-utils ffmpeg
ln -s /etc/sv/pulseaudio /etc/runit/runsvdir/default/pulseaudio

Then in /root/Startup/start_pulseaudio PulseAudio is actually started up at system start

Code: Select all

#!/bin/sh
pulseaudio --start

So it looks to me like the Alsa plugins might allow ALSA applications to access ALSA first then route to the Pulse Audio server. Or in the case of input perhaps the other way around. That's my stab-in-dark guess. I'll have to do some experimenting with different applications and see how they run.

@geo_c

Yes KLV is at it's roots, a WeeDog-Void-xfce4 built originally with @wiak's WDL build script(s) and a PLUG file to steer the script, using the Void Linux binaries and package manager. KLV uses the WeeDogLinux (WDL) generic Skeleton initrd.gz but the difference between a "WeeDogged" distro and KLV is that KLV-Airedale is constructed from scratch by the XBPS package manager. What happens is the build script gets a static copy of XBPS which can be mounted and chroot'ed into a system that then can install Void Linux components around itself until the new system can be chroot'ed with it's new XBPS package manager that then begins to install the rest of the system.

Then we come along and start modifying that resulting distro by adding the custom KLV kernel or any huge Puppy Linux kernel so it all can boot on it's own. Also utilities and some tools are borrowed from DebianDog and Puppy Linux are then placed into the system and using some WDL tricks of mixing compressed and uncompressed system directories add some basic configurations and a default desktop background, then compress into SFS and ISO.

WeeDogIT works with the target distro being more "arranged" than is being "built" and using that distro's components.

KLV is built from Void Linux binaries using the XBPS package manager from scratch.
f_00_Void_KLV_XFCE_no-kernel_WDLteam-rc4.plug

# f_00_Void_KLV_XFCE_no-kernel_WDLteam-rc4.plug
# version="1.1.5"; revision="-alpha5"
# Kennel Linux Void outfitted with a xfce4 desktop and no kernel **uses puppy linux kernel**
# Creation date 24Sep2021; Revision date: 19Dec2021
# Copyright Kennel Linux team; Licence MIT

# build this via terminal commands:build_firstrib_rootfs-latest.sh
# export CONNECTION_TIMEOUT=-1  **not needed with v501**
# ./build_firstrib_rootfs-latest.sh void default amd64 f_00_Void_KLV_XFCE_kernel_WDLteam-rc4.plug
# Architecture i386 will probably successfully build too as an alternative to amd64

# login is user=root passwd=root

# All the parameters/commandlines can be appropriately changed:
# Simply comment in or comment out till you have what you desire
# or add new packages to the xbps-install lists.
# You can add as many valid commandlines as you want in here.
#
# base system
xbps-install -y base-minimal ncurses-base bash eudev
xbps-install -y file mc 
xbps-install -y shadow wpa_supplicant  # needed for most wifi
xbps-install -y ntfs-3g zstd

# set up passwd system
pwconv
grpconv
printf "root\nroot\n" | passwd >/dev/null 2>&1 # Quietly set default root passwd to "root"

# set root to use /bin/bash
usermod --shell /bin/bash root

# Set locale to en_US.UTF-8 
sed -i 's/#en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/default/libc-locales
xbps-reconfigure -f glibc-locales

# Set Bash as shell
xbps-alternatives --set bash

## --------------------------------------------------------------------------
## Xorg server, xfce4 Desktop configuration

xbps-install -y xorg xfce4 xfce4-panel xfce4-plugins compton picom
xbps-install -y gvfs yad
xbps-install -y gvfs-smb gvfs-mtp gvfs-cdda

# Optional packages
#
xbps-install -y geany gftp rox ffmpeg mtpaint xfce4-screenshooter
xbps-install -y octoxbps fox guvcview
xbps-install -y e2fsprogs yelp gparted
xbps-install -y dosfstools mtools 
xbps-install -y firefox ntfs-3g

# Install Audio
#
xbps-install -y pulseaudio pulseaudio-utils alsa-plugins-pulseaudio alsa-utils
ln -s /etc/sv/pulseaudio /etc/runit/runsvdir/default/pulseaudio

# Install Network Manager
#
xbps-install -y NetworkManager network-manager-applet
ln -s /etc/sv/NetworkManager /etc/runit/runsvdir/default/NetworkManager

# Set locale to en_US.UTF-8
sed -i 's/#en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/default/libc-locales
xbps-reconfigure -f glibc-locales

# Setup autologin on tty1
#
cp -a /etc/X11/xinit/xinitrc /root/.xinitrc
cp -R /etc/sv/agetty-tty1 /etc/sv/agetty-autologin-tty1
sed -i 's/GETTY_ARGS.*/GETTY_ARGS="--autologin root --noclear"/' /etc/sv/agetty-autologin-tty1/conf  # editing for autologin root

# Arrange to startx in user's .bash_profile (per Arch Wiki)
# Remove this section if not wanting boot straight into X
touch ~/.bash_profile
cat <<'AUTOLOGIN' > /etc/profile.d/autologin.sh
# autologin on tty1
if [ -z "$DISPLAY" ] && [ "$(fgconsole)" -eq 1 ]; then
#  exec startx  # remove the exec if you want back to tty1 on exit X
startx  # remove the exec if you want back to tty1 on exit X
fi
AUTOLOGIN

# Use agetty-autologin-tty1 instead of agetty-tty1 
rm -f /etc/runit/runsvdir/default/agetty-tty1
ln -s /etc/sv/agetty-autologin-tty1 /etc/runit/runsvdir/default/agetty-autologin-tty1
# enable dbus service
ln -s /etc/sv/dbus /etc/runit/runsvdir/default/dbus

# Auto-editing .xinitrc to use xfce4 instead of twm
# Because I'm using exec here the script will end there so no xterms started
#
sed -i 's/twm &/exec xfce4-session/' ~/.xinitrc

## USER CONFIGS: Copy main configs to /etc/skel for all normal users later added
#
xbps-install -y sudo
cp -af /root/. /etc/skel
mkdir -p /etc/skel/.config /etc/skel/.cache /etc/skel/.local/share
echo Still some extra to do here re the likes of runit starting pulseaudio
echo among other user needed config bits and pieces,
echo so probably a few user-config issues noted as needing fixed here

# Give wheel group nopasswd sudo rights and create weedog as wheel group member
echo '%wheel ALL=(ALL) NOPASSWD: ALL' | (VISUAL="tee -a" visudo) # wheel group added to sudo no password required
useradd -m -G wheel -s /bin/bash weedog  # weedog in wheel group so has elevated sudo permissions
printf "weedog\nweedog\n" | passwd weedog >/dev/null 2>&1 # Quietly set default weedog passwd to "weedog"

# Give wheel group nopasswd sudo rights and create spot as wheel group member
echo '%wheel ALL=(ALL) NOPASSWD: ALL' | (VISUAL="tee -a" visudo) # wheel group added to sudo no password required
useradd -m -G wheel -s /bin/bash spot  #spot in wheel group so has elevated sudo permissions
printf "spot\nspot\n" | passwd spot >/dev/null 2>&1 # Quietly set default spot

# add users to groups

usermod -a -G audio weedog
usermod -a -G audio spot
usermod -a -G video weedog
usermod -a -G video spot


echo "desktop build process finished"

Build scripts that use the PLUG files. Using the skeleton initrd.gz and a Puppy Linux kernel only build_firstrib_rootfs-latest.sh needs to be run.

Will build a basic KLV root file system!

./build_firstrib_rootfs-latest.sh void default amd64 f_00_Void_KLV_XFCE_no-kernel_WDLteam-rc4.plug

remove the fake ".gz"

EDIT (by wiak): Please don't use the following attachments! These are OLD versions. I'll provide the latest versions shortly (wiak).

Thanks @rockedge, implementing a weedog script seems way, waY, WAY above my paygrade. The info on Pulse is exactly what I needed to know, and I see the line you quoted in the script.

Just an interesting fun observation by the Xfe file search dialog in KLV:

find: File system loop detected; '/mnt/layers/merged' is part of the same file system loop as '/'.
find: '/proc/734/task/734/net': Invalid argument
find: '/proc/734/net': Invalid argument
find: '/proc/924/task/924/net': Invalid argument
find: '/proc/924/net': Invalid argument

I guess Xfe wasn't built with puppy-linux geniuses in mind!

I'm doing a file search to try and figure out what version of Python is installed in KLV, if any, because the XBPS manager only offers 2.7.18_4 and Frescobaldi 3.2 requires python 3.4 or higher. Seems like in the Xfe search most of the python files are labeled '-310' which means version 3.10? I'm sure there's a easier way to know. edit: ah, I see the python directories are in fact labeled '3.10'

And WOOPS, I'm wrong. XBPS does offer Python 3. version 3.10.4_1 to be exact. XBPS doesn't offer an install option for it, so I guess it's the exact same 3.10 version.

geo_c wrote: ↑Fri Jun 03, 2022 1:09 am

Thanks @rockedge, implementing a weedog script seems way, waY, WAY above my paygrade. The info on Pulse is exactly what I needed to know, and I see the line you quoted in the script.
And WOOPS, I'm wrong XBPS does offer Python 3. version 3.10.4_1 to be exact. XBPS doesn't offer an install option for it, so I guess it's the exact same 3.10 version.

Interesting, Void-Linux appears to have Python 3.10 built-in, but Fossapup has Python 3.8 in the /var/packages/built-in directory.

Frescobaldi 3.2 needs Python 3.4 or higher, while Frescobaldi 2 needs Python 3.2 or higher or Python 2.7 (which seems nonsensical, but that is what the website says: https://www.frescobaldi.org/download. Hmmm. I have to chew on that for awhile.

Hi @geo_c. You're making great progress with this PUP.

Is "Frescobaldi" giving python errors when you attempt to run?

Curious

Clarity wrote: ↑Fri Jun 03, 2022 2:03 am

Hi @geo_c. You're making great progress with this PUP.

Is "Frescobaldi" giving python errors when you attempt to run?

Curious

Frescobaldi is not in the XBPS package manager. I was able to install Frescobaldi 3.13 on Fossapup by going to the Debian site and searching the list of required pyQt dependencies and finding them in the Fossapup PPM or Debian site, and then downloading the Debian Frescobaldi 3.13 package and installing that like a pet.

So I'm looking to do a similar thing in KLV. I downloaded from the Frescobaldi git-page and unzipped the Frescobaldi 3.2 'package' which not technically a package, it's all the application files necessary to run except the python and pythonQt dependencies. It doesn't need to be compiled. So at the moment I'm looking at which exact python/qt file versions I should be installing from XBPS to run this 'portable' of the most up to date version of Frescobaldi, which is version 3.2. But I may be better off going with 3.1.3

BUT, I was reading the readme in the Frescobaldi run directory, and I noticed that I could run it from the terminal with ./frescobaldi, I ran it from a terminal without installing the necessary dependencies knowing it would fail, just to see what it returned, which was this:

root# ./frescobaldi
The 'popplerqt5' module can't be found.
Frescobaldi can't find the 'popplerqt5' module. This module is required for the display of PDF documents. The module is in the python-poppler-qt5 package which needs to be installed.

Frescobaldi can run, but cannot display PDF documents.
Continuing...
The 'qpageview' module can't be found.
Frescobaldi can't find the 'qpageview' module. This module is required for the Music View and other viewers inside Frescobaldi, and can be downloaded from http://github.com/frescobaldi/qpageview.

Unfortunately, Frescobaldi cannot run without it.
Exiting.
root# 

So it may be that Python is up to the task, as I didn't get any message about the python version specifically. Perhaps if I install the handfull of pyQt dependencies from XBPS I'll get it to work.

Clarity wrote: ↑Fri Jun 03, 2022 2:03 am

Hi @geo_c. You're making great progress with this PUP.

I've got it tweaked pretty close to the same level as Fossa, and I'm using the Hercules Icons in KLV. My KLV desktop looks like this:

wednesday food specials wilmington nc

geo_c wrote: ↑Fri Jun 03, 2022 2:48 am

So it may be that Python is up to the task, as I didn't get any message about the python version specifically. Perhaps if I install the handfull of pyQt dependencies from XBPS I'll get it to work.

Do you have Frescobaldi working in KLV-Airedale now?

I note that the poppler-qt5 package is available.

I always find it best to use online Voidlinux.org/packages rather than commanline xbps to search for repo-available packages, so:

https://voidlinux.org/packages/?arch=x86_64&q=poppler

provides a list which includes the needed package: poppler-qt5

and I see from https://github.com/frescobaldi/qpagevie ... NSTALL.rst

Installing qpageview
This package installs one Python package, qpageview, in the usual location for Python modules.

You can install qpageview without downloading it first via pip:

pip install qpageview
You can also install from the source directory:

python3 setup.py install

Looks like you don't even need python pip, rather could just us git to download gpageview and then run that: python3 setup.py install
i.e. assuming git is on your system, you'd just use:

git clone https://github.com/frescobaldi/qpageview

and that would download the gpageview directory with setup.py and associated files in it.
You don't need to understand git use at all otherwise.

geo_c wrote: ↑Fri Jun 03, 2022 1:09 am

Thanks @rockedge, implementing a weedog script seems way, waY, WAY above my paygrade.

You are surely exaggerating geo_c! The process for building is exactly as rockedge described. You simply need the already written build script called build_firstrib_rootfs and the build plugin (which rockedge has given filename of f_00_Void_KLV_XFCE_no-kernel_WDLteam-rc4.plug. Only issue is that currently the build plugin rockedge is able to provide doesn't have some of the iso build extras included in it yet.

./build_firstrib_rootfs-latest.sh void default amd64 f_00_Void_KLV_XFCE_no-kernel_WDLteam-rc4.plug

That is all that is needed to build a weedog root filesystem (which you then add the initrd to, which is just a matter of running a second provided script usually, being build_weedog_initrd).

The plugin file used in the build is just a list of shell script commands really. So anything you manage to do manually can instead simply be put in a text file (that's what a script is after all...) and you thereafter don't need to do the same manual steps (since you put what you did in a simple script... which is their point...).

The only problem, for now, is that at the moment rockedge doesn't have a plugin that contains everything he did manually yet so the one he was able to supply is just enough to build a basic KLV-Airedale rather than the more polished build provided in iso form. The process of building a WDL-based distro is simple itself, and certainly NOT even slightly above the paygrade of most contributors to this forum. For example, if rockedge's plugin was complete, you would simply be adding a few simple xbps-install commands to the end of it for some of your purposes, such as: xbps-install -Sy poppler-qt5
Easy as that, and then poppler-qt5 would be included in your personal build...

wiak wrote: ↑Fri Jun 03, 2022 4:39 am

Looks like you don't even need python pip, rather could just us git to download gpageview and then run that: python3 setup.py install
i.e. assuming git is on your system, you'd just use:

Code: Select all

git clone https://github.com/frescobaldi/qpageview

and that would download the gpageview directory with setup.py and associated files in it.
You don't need to understand git use at all otherwise.

Thanks @wiak, I ran the git command and it returned:

root# git clone https://github.com/frescobaldi/qpageview
Cloning into 'qpageview'...
remote: Enumerating objects: 2617, done.
remote: Counting objects: 100% (460/460), done.
remote: Compressing objects: 100% (193/193), done.
remote: Total 2617 (delta 266), reused 454 (delta 262), pack-reused 2157
Receiving objects: 100% (2617/2617), 837.48 KiB | 6.65 MiB/s, done.
Resolving deltas: 100% (1715/1715), done.

Then I ran: python3 setup.py install
Which returned with an error:

root# python3 setup.py install
Traceback (most recent call last):
  File "/root/qpageview/setup.py", line 32, in <module>
    from qpageview import pkginfo
  File "/root/qpageview/qpageview/__init__.py", line 65, in <module>
    from . import link
  File "/root/qpageview/qpageview/link.py", line 36, in <module>
    from . import page
  File "/root/qpageview/qpageview/page.py", line 32, in <module>
    from PyQt5.QtSvg import QSvgGenerator
ModuleNotFoundError: No module named 'PyQt5.QtSvg'

I installed python-qt5 from XBPS. But not poppler-qt5.

This time when I ran ./frescobaldi it did not return errors in the terminal but booted up the messages in a gui window, and gave me the same messages as the original, saying that it can't find qpageview.

geo_c wrote: ↑Fri Jun 03, 2022 11:55 am

Thanks @wiak, I ran the git command and it returned:
...
Then I ran: python3 setup.py install
Which returned with an error:

Looks like git did the clone okay. Alas, I have never installed that program myself so have no idea why its setup.py would fail, sorry.

wiak wrote: ↑Fri Jun 03, 2022 12:01 pm

geo_c wrote: ↑Fri Jun 03, 2022 11:55 am

Thanks @wiak, I ran the git command and it returned:
...
Then I ran: python3 setup.py install
Which returned with an error:

Looks like git did the clone okay. Alas, I have never installed that program myself so have no idea why its setup.py would fail, sorry.

I edited the previous post, as I'm making some progress I suppose, because this time frescobaldi made it to the gui message window.

Thanks @wiak, I seem be missing something, like where to run the git command. I ran the original git clone qpageview from /root. I decided to try the same approach with python-poppler-qt5 by following the link of the frescobaldi web-page, so I ran git clone from the /frescobaldi-3.2 directory:

root# git clone https://github.com/frescobaldi/python-poppler-qt5
Cloning into 'python-poppler-qt5'...
remote: Enumerating objects: 259, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 259 (delta 40), reused 36 (delta 32), pack-reused 205
Receiving objects: 100% (259/259), 72.17 KiB | 3.01 MiB/s, done.
Resolving deltas: 100% (147/147), done.
root# 

Then changed to the /frescobaldi-3.2/python-poppler-qt5 directory and ran: python3 setup.py install:

root# python3 setup.py install
Traceback (most recent call last):
  File "/root/frescobaldi-3.2/python-poppler-qt5/setup.py", line 42, in <module>
    import sipdistutils
ModuleNotFoundError: No module named 'sipdistutils'

I think maybe I'm just not running from the correct location.

rockedge wrote: ↑Thu Jun 02, 2022 2:19 pm

Build scripts that use the PLUG files. Using the skeleton initrd.gz and a Puppy Linux kernel only build_firstrib_rootfs-latest.sh needs to be run.
...
build_firstrib_rootfs-latest.sh.gz
build_weedog_initrd-latest.sh.gz

I should point out that that build_firstrib_rootfs-latest.sh script you provided @rockege above is a very 'old' one! So far back I can't recall the differences but always best to use the actual latest, which currently can be assured via using the get_WDL_build_firstrib_rootfs... script from this thread post: https://forum.puppylinux.com/viewtopic. ... 093#p37093

Actually, I am really posting for the related reason that there has been a new 'default' repo change by upstream Void: https://voidlinux.org/news/

Eventually I will get back to checking the state of the main WDL build scripts (build_firstrib_rootfs and build_weedog_initrd) since things always change upstream (such as default busybox url and debootstrap urls needed for debian/ubuntu builds, and similarly for when archdebootstrap no longer functioning - I found a working alternative recently for WDL_Arch base build plus my plugin). The build_weedog_initrd major change was a move to a different newer busybox that worked with nvme drives or something like that. I forget already!; I am planning to improve my cherrytree notepad memory organisation (already doing so for my partners business - she is hooked on cherrytree too), and also fix up the old github and/or gitlab weedog sites. Git is wonderful, but that doesn't mean I don't hate it. Cherrytree, on the otherhand, is a simple, but intuitive and beautiful thing (of surprisingly great power), but it all too often still becomes a messy scratchpad for me, which is ridiculous considering how easy cherrytree is to use and organise...

It is a long time indeed since I myself tried to persuade anyone to try out build_firstrib_rootfs and build_weedog_initrd build WDL system mechanism. Very few ever showed much interest in that side of things. I'm not sure many bother with woof-CE either, except in moments of madness. One day I may refine the WDL build process via a yad gui or similar (though the current simple build scripts really are pretty easy to use once tried and understood), where options can simply be chosen (including a list of possible plugins for different distro variations) - a bit like I once tried for woof-CE with 'makepup', which was okay in a way, but too much of a hack, but some kind of frontend gui could be good for WDL building. WeeDogIT, funnily enough, seems from downloads to have been far more successful than the WDL core build scripts - probably because, despite being a commandline run script, it is relatively easy to use and allows frugal installations for so many major upstream distros as an alternative to their normal full installation mechanisms. Also, as I say, I never discuss the overall WDL build process any more - I just use it.

@wiak I also have a mess of organization! There are PLUG and build script files EVERYWHERE across 6 systems all networked. Finding the right one is a real adventure.

I tried to git pull to freshen up the build scripts but ran into a authorization problem (I couldn't get in) so I searched around through what I thought at the time was somewhat organized but turned out to be a wild mess. So is the build script the latest? Probably not.

I have just used a really old build script rc401 which worked very well making a WeeDog64-Void-JWM.

I am now getting all the extra XBPS packages from fredx181 together so I can wget them in the PLUG file. Studying how to set the default background and some other configurations in the PLUG for the xfce4 desktop during the build run. The PLUG to make a polished KLV-Airedale is not far off now.

rockedge wrote: ↑Fri Jun 03, 2022 1:35 pm

I tried to git pull to freshen up the build scripts but ran into a authorization problem (I couldn't get in) so I searched around through what I thought at the time was somewhat organized but turned out to be a wild mess.

Yes, I think a lot of these problems (at least re: build WDL scripts) is my fault; I have had too many side projects and lost control of focus. I don't myself even know anymore where some bits and pieces are - such as for WDL_GO builds, which had some extra script additions: they are not lost per se, just hidden in the hay stack waiting for me to get my act together (which may never happen).

I also have various websites whose content is stored on github and/or gitlab (some for business) and I basically have trouble remembering the username logins and passwords - most of the details were written down by me in some paper notebook or other, but I need to get a hold on it all and organise it better for the sakes of my longterm sanity. Recently been documenting the DNS domains I have set up for some of these bits and pieces, including email security and redirects and whatever - so a start has been made...

@wiak and @rockedge

here's an example of why I say that doing WeeDogIT is above my capabilities,

I rebooted KLV to an older copy prior to my trying to install frescobaldi, and I decided to follow the links on frescobaldi's page, starting with Python-3.6, which took me to: https://www.python.org/downloads/. It's there after choosing the 'Install latest python version' link that I realized that Python-3.10.4.tar.xz is the latest version, which is what is already built-in to KLV. I was thinking that the numeric sequence of '3.10' meant '3.1' as opposed to 3.4 or 3.6, and I'm prone to miss the obvious in so many ways like that.

Of course I learn a lot by trial and error, and the ability to back-up a system just by copying one directory affords me the luxury of being able to 'try away' and fail.

This is why the puppy-linux way of doing things is right up my alley.

So now I'm confident I've got the latest version of python, and I'm going to follow frescobaldi's install order very closely and see how I do.

@wiak

Without confusing the issue with too many details, in the process of installing python-ly needed for frescobaldi, this link recommended ensuring that I could run pip from the command line by entering the command:

python3 -m ensurepip --default-pip

which returned:

root# python3 -m ensurepip --default-pip
Looking in links: /tmp/tmpeg2d0ivu
Requirement already satisfied: setuptools in /usr/lib/python3.10/site-packages (60.9.3)
Processing /tmp/tmpeg2d0ivu/pip-22.0.4-py3-none-any.whl
Installing collected packages: pip
Successfully installed pip-22.0.4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
root# 

So my quick question is: Will I break my XBPS by running pip as root at some point?

@geo_c I have not broken anything yet using pip to install some Python pieces!

I have not tried this yet :

run-as-spot pip install <something>
run-as-weedog pip -v

Update: I ran the same line t0 install :

python3 -m ensurepip --default-pip

rockedge wrote: ↑Fri Jun 03, 2022 4:11 pm

@geo_c I have not broken anything yet using pip to install some Python pieces!

So I had SUCCESS installing python-ly using the setup.py approach. But python-poppler-qt5 looked more complicated, so instead I decided to try a pip install, only the package seems to be misconfigured, or perhaps KLV's version of python is too high, as I got this error:

root# python3 -m pip install python-poppler-qt5
Collecting python-poppler-qt5
  Downloading python-poppler-qt5-21.3.0.tar.gz (28 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... error
  error: subprocess-exited-with-error
  
  �� Preparing metadata (pyproject.toml) did not run successfully.
  ��� exit code: 1
  ������> [27 lines of output]
      Traceback (most recent call last):
        File "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 156, in prepare_metadata_for_build_wheel
          hook = backend.prepare_metadata_for_build_wheel
      AttributeError: module 'sipbuild.api' has no attribute 'prepare_metadata_for_build_wheel'
      
      During handling of the above exception, another exception occurred:
      
      Traceback (most recent call last):
        File "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
          main()
        File "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/usr/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 160, in prepare_metadata_for_build_wheel
          whl_basename = backend.build_wheel(metadata_directory, config_settings)
        File "/tmp/pip-build-env-ijaex0jl/overlay/lib/python3.10/site-packages/sipbuild/api.py", line 51, in build_wheel
          project = AbstractProject.bootstrap('pep517')
        File "/tmp/pip-build-env-ijaex0jl/overlay/lib/python3.10/site-packages/sipbuild/abstract_project.py", line 83, in bootstrap
          project.setup(pyproject, tool, tool_description)
        File "/tmp/pip-build-env-ijaex0jl/overlay/lib/python3.10/site-packages/sipbuild/project.py", line 594, in setup
          self.apply_user_defaults(tool)
        File "/tmp/pip-build-env-ijaex0jl/overlay/lib/python3.10/site-packages/pyqtbuild/project.py", line 70, in apply_user_defaults
          super().apply_user_defaults(tool)
        File "/tmp/pip-build-env-ijaex0jl/overlay/lib/python3.10/site-packages/sipbuild/project.py", line 241, in apply_user_defaults
          self.builder.apply_user_defaults(tool)
        File "/tmp/pip-build-env-ijaex0jl/overlay/lib/python3.10/site-packages/pyqtbuild/builder.py", line 67, in apply_user_defaults
          raise PyProjectOptionException('qmake',
      sipbuild.pyproject.PyProjectOptionException
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

�� Encountered error while generating package metadata.
������> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
WARNING: You are using pip version 22.0.4; however, version 22.1.2 is available.
You should consider upgrading via the '/sbin/python3 -m pip install --upgrade pip' command.
root# 

So I'm debating whether to fall back and start over, or just try and download the python-poppler-qt5 package and attempt it over the top with the setup.py method. edit: actually the problem is python-poppler-qt5 doesn't appear to be a package, and I'm confused at about how to grab it from github: https://github.com/frescobaldi/python-poppler-qt5

rockedge wrote:

@wiak I also have a mess of organization!

May I join the club
I always think at forehand that I can remember things, but turns out not as time is passing.

geo_c wrote: ↑Fri Jun 03, 2022 4:55 pm

So I'm debating whether to fall back and start over, or just try and download the python-poppler-qt5 package and attempt it over the top with the setup.py method. edit: actually the problem is python-poppler-qt5 doesn't appear to be a package, and I'm confused at about how to grab it from github: https://github.com/frescobaldi/python-poppler-qt5

I decided to try @wiak's git clone approach for python-poppler-qt5, which worked and returned:

root# git clone https://github.com/frescobaldi/python-poppler-qt5
Cloning into 'python-poppler-qt5'...
remote: Enumerating objects: 259, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 259 (delta 40), reused 36 (delta 32), pack-reused 205
Receiving objects: 100% (259/259), 72.17 KiB | 2.25 MiB/s, done.
Resolving deltas: 100% (147/147), done.

Then I ran python3 setup.py install which tells me that a module is missing. I don't know whether this is a module that is supposed to be in the python-poppler-qt5 repository, or whether is one that is supposed to be in the system and isn't. The setup.py command returns this:

root# python3 setup.py install
Traceback (most recent call last):
  File "/root/python-poppler-qt5/setup.py", line 42, in <module>
    import sipdistutils
ModuleNotFoundError: No module named 'sipdistutils'

Time to take a break I guess. The weather is really gorgeous today.

@rockedge,

I feel like I'm gumming up this development discussion talking about my python/frescobaldi lessons, so if you want to break this off and place it in a more appropriate area of the forum, I won't be offended.

It's a learning curve, but I'm making some progress by backing up my system along each step, so I can fall back without starting at the beginning.

Rather than use pip install, I have chosen to go with downloading the source and using setup.py.

So far and in this order I have successfully installed:

• PyQt5 from the XBPS package manager

• poppler-qt5 from XBPS

• python-ly from it's source distribution https://pypi.org/project/python-ly/#files using setup.py

• frescobaldi from github using git clone and setup.py

then I run into problems with python-poppler-qt5 after grabbing it with git clone

Form a little internet searching and reading the error messages, I discovered the need to install sip-distutils-dev from XBPS because trying to run the setup.py build command on python-poppler-qt5 returned this message:

root# python setup.py build
Traceback (most recent call last):
  File "/root/python-poppler-qt5/setup.py", line 42, in <module>
    import sipdistutils
ModuleNotFoundError: No module named 'sipdistutils'

A little reading revealed that python is ending distutils altogether in python-3.12 and so it must not be included in 3.10.4

So after running python setup.py build with sip-distutils-dev installed I made a little more headway. But the build script couldn't find the poppler-qt5 package that I installed using XBPS, and returned the following:

root# python setup.py build
Package poppler-qt5 was not found in the pkg-config search path.
Perhaps you should add the directory containing `poppler-qt5.pc'
to the PKG_CONFIG_PATH environment variable
No package 'poppler-qt5' found
/usr/lib/python3.10/site-packages/setuptools/dist.py:738: UserWarning: Usage of dash-separated 'force-manifest' will not be supported in future versions. Please use the underscore name 'force_manifest' instead
  warnings.warn(
running build
running build_ext
Failed to determine Qt version ([Errno 2] No such file or directory: 'qmake')

And so I'm trying to figure out if there is file in the poppler-qt5 directiory that I can add the PKG_CONFIG_PATH enviornment variable to that will get the build working. But first,

Where excactly is the environment variable supposed to be added? Is it somewhere in the python-poppler-qt5 source directory, or somewhere in the KLV system itself?

added: A system search using Xfe doesn't turn up any file named poppler-qt5.pc mentioned in the terminal output, however there are files named /var/db/xbps/.poppler-qt5-files.plist and /var/cache/xbps/poppler-qt5-21.07.0_1.x86_64.xbps

is this installed? Have you tried installing this directly using int-xbps or when right clicking on this xbps file in Thunar?

/var/cache/xbps/poppler-qt5-21.07.0_1.x86_64.xbps

rockedge wrote: ↑Fri Jun 03, 2022 11:28 pm

is this installed?

Code: Select all

/var/cache/xbps/poppler-qt5-21.07.0_1.x86_64.xbps

Yes, I installed it from XBPS, which said the files were installed successfully. I just right clicked on it in Thunar and re-installed, so apparently my previous XBPS install was successful.

putting in sip-distutils-dev was the right move. Have you run a ldconfigin a terminal lately?

rockedge wrote: ↑Fri Jun 03, 2022 11:33 pm

putting in sip-distutils-dev was the right move. Have you run a ldconfigin a terminal lately?

no, I can do that though.