How to build (say Ubuntu 22 compatible) Puppy Linux

[RyPuppy]

Goal :
o build Puppy Linux on GitHub platform
o Compatible with Ubuntu 22.04, x86_64
o Customize with Ubuntu packages

This is what I have done so far...

• Start with GitHub's How-To-Guide : Building a Puppy on GitHub

https://github.com/puppylinux-woof-CE/w ... -on-GitHub

Fork from the main WOOF-CE project : puppylinux-woof-CE / woof-CE https://github.com/puppylinux-woof-CE/woof-CE

Question:
At the Step : "Create a new fork"
"Copy the testing branch only" - should we uncheck this option as I am planning to customize and not just test ?

After Navigating to the newly created repository - "https://github.com/<MY-LOGIN-ID>/woof-CE" , clicked on the "Actions" menu option

Question: I got the message

Code: Select all

Workflows aren’t being run on this forked repository

Because this repository contained workflow files when it was forked, we have disabled them from running on this fork. Make sure you understand the configured workflows and their expected usage before enabling Actions on this repository.

I chose to ignore and went with "I understand my WorkFlows. Go Ahead & Enable them"

Clicked on <My Repository> --> Actions Tab --> release workflow --> Click on "Run workflow"

wf.png (28.42 KiB) Viewed 1342 times

I get the ERROR message :

Code: Select all

build / build 
Process exited with error code 1 

Code: Select all

[b]Merge2out[/b]
Run yes "" | sudo -E ./merge2out woof-distro/x86_64/ubuntu/22.04
Missing configuration directory: woof-distro/x86_64/ubuntu/22.04
yes: standard output: Broken pipe
Error: Process completed with exit code 1.

Need help on how to run this workflow.

[dimkr]

You should use "jammy64", not "22.04".

https://github.com/puppylinux-woof-CE/w ... _64/ubuntu

[RyPuppy]

I created 3 workflows and running the 3 jobs

Code: Select all

Branch: testing

1 Human-readable name :              RY.Ubuntu.Jammy64    RY.SlackWare64.15.0    RY.Debian.BookWorm64
2 Version Number :                   1.1                  2.2                    3.3
3 Release name suffix, with leading: -prepreprealpha1     -prepreprealpha1       -prepreprealpha1
4 Architecture:                      x86_64               x86_64                 x86_64
5 Compatible distro:                 ubuntu               slackware64            debian
6 Compatible distro version :        jammy64              15.0                   bookworm64
7 Kernel version :                   5.15.x               5.15.x                 5.15.x
8 File name prefix :                 RY.Ubuntu.Jammy64    RY.SlackWare64.15.0    RY.Debian.BookWorm64

Upload release draft                 --                   --                     --

After Workflow was completed, none of them produced ISO's.

Step "build/build" --> "Upload" :: "build" step was successful but "upload" step was skipped for all 3 workflows.

Following ZIP file was created in each case:

Code: Select all

debian --> release-x86_64-debian-bookworm64-4.zip	( 1000 MB ) 
ubuntu --> release-x86_64-ubuntu-jammy64-3.zip		(  838 MB )
Slackware --> release-x86_64-slackware64-15.0-2.zip	( 1.16 GB )

Here is the link to my Workflows ...
https://github.com/RYRNRY/woof-CE/actions

Question:
How do I enable ISO creation ?

[RyPuppy]

Here are the contents of the 3 ZIP files. They all include ISO & SFS files.

File : release-x86_64-ubuntu-jammy64-3.zip

Code: Select all

devx_RY.Ubuntu.Jammy64_1.1.sfs         134 MB
docx_RY.Ubuntu.Jammy64_1.1.sfs          25 MB
kernel_sources-5.15.76-kernel-kit.sfs  161 MB
nlsx_RY.Ubuntu.Jammy64_1.1.sfs          99 MB
RY.Ubuntu.Jammy64-1.1.iso              457 MB

File : release-x86_64-slackware64-15.0-2.zip

Code: Select all

devx_RY.SlackWare64.15.0_2.2.sfs       273 MB
docx_RY.SlackWare64.15.0_2.2.sfs        89 MB
kernel_sources-5.15.76-kernel-kit.sfs  161 MB
nlsx_RY.SlackWare64.15.0_2.2.sfs        75 MB
RY.SlackWare64.15.0-2.2.iso            647 MB

File : release-x86_64-debian-bookworm64-4.zip

Code: Select all

devx_RY.Debian.BookWorm64_3.3.sfs        147 MB
kernel_sources-5.15.76-kernel-kit.sfs    161 MB
RY.Debian.BookWorm64-3.3-docx-nlsx.iso   742 MB

Quick test of the ISO's will follow...

[RyPuppy]

RY.Debian.BookWorm64-3.3-docx-nlsx.iso

Launched DEBIAN ISO in an VirtualBox running on a Windows.11 host. ISO booted quickly with no issues. Internet was enabled OTB.

Debian-Boot.png (51.06 KiB) Viewed 1279 times

Debian.png (121.94 KiB) Viewed 1279 times

[RyPuppy]

RY.SlackWare64.15.0-2.2.iso

Booted quickly with Internet OTB. Had trouble with controlling the Mouse.

SlackWare.png (90.89 KiB) Viewed 1271 times

[RyPuppy]

RY.Ubuntu.Jammy64-1.1.iso

Ubuntu ISO booted quickly, Internet connection OTB.

Ubuntu.png (247.15 KiB) Viewed 1271 times

[RyPuppy]

Ubunutu-Jammy64 WOOF puppy fails with WiFi.

Comparing with the older FossaPup.9.5 puppy, WiFi driver is installed. I need to install Frizbee networking package/modules. Any suggestions on how to install & enable Frizbee ?

[mikeslr]

@rockedge : The Forum should have a separate Section just for discussions about using Woof.

@RyPuppy , if you mean include Frisbee in your woof build, IDK. If you mean "post Woof build", you can download Frisbee from the link here, viewtopic.php?t=445&sid=0fccf22059cc958 ... d7b67b8591. But I'm not sure if it will appear as an option on the woof-created internet connection wizard or otherwise be available unless rerwin's Network Wizard is also installed. That's also available from the above link.

[dimkr]

If the problem is a missing driver, installing Frisbee won't fix that.

But if you still want to use Frisbee, remove the connman package from DISTRO_PKGS_SPECS (see https://github.com/puppylinux-woof-CE/w ... istro#L160).

What do you mean by "fails with WiFi"?

[RyPuppy]

If the problem is a missing driver, installing Frisbee won't fix that.

But if you still want to use Frisbee, remove the connman package from DISTRO_PKGS_SPECS (see https://github.com/puppylinux-woof-CE/w ... istro#L160).

What do you mean by "fails with WiFi"?

Ubuntu-Jammy-ISO works on my desktop VM as it is using Ethernet.

It fails on my HP Pavillion X360 Laptop which is little less than 10 years old. I am running FossaPup.9.5 on this HP Laptop and WiFi was configured using Frisbee.

WiFI driver RT3290 is loaded on the new ISO.

Code: Select all

$> lspci | grep 3290

02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
02:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

$> modprobe -c rt2800pci | grep 3290 

alias pci:v00001814d00003290sv*sd*bc*sc*i* rt2800pci
alias usb:v18ECp3290d*dc*dsc*dp*ic0Eisc01ip00in* uvcvideo

#-----
$> ls -l /sys/class/net/

lrwxrwxrwx  1 root root 0 Nov  5 18:00 eth0 -> ../../devices/pci0000:00/0000:00:1c.3/0000:04:00.0/net/eth0
lrwxrwxrwx  1 root root 0 Nov  5 18:00 lo -> ../../devices/virtual/net/lo
lrwxrwxrwx  1 root root 0 Nov  5 18:00 wlan0 -> ../../devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/wlan0

When I try to configure WIFI through available Internet-Connection-Wizard, everything is blank. There are no buttons to press scan available WiFi networks.

As WiFi driver rt2800pci does show up, I am guessing, ISO is missing the configuration tools like Frisbee.

[dimkr]

I bet the problem is missing firmware.

If /lib/firmware/rt3290.bin doesn't exist, you'll probably see this in dmesg and https://github.com/puppylinux-woof-CE/woof-CE/pull/3586 will fix it.

[RyPuppy]

I bet the problem is missing firmware.

If /lib/firmware/rt3290.bin doesn't exist, you'll probably see this in dmesg and https://github.com/puppylinux-woof-CE/woof-CE/pull/3586 will fix it.

dimkr - You were right ...

Code: Select all

$> dmesg | grep 3290
 
[    1.926761] pci 0000:02:00.0: [1814:3290] type 00 class 0x028000
[    9.262216] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected
[    9.265671] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected
[   16.606722] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[   16.607024] rt2800pci 0000:02:00.0: Direct firmware load for rt3290.bin failed with error -2

Questions:
1. Looks like rebuilding Ubuntu-Jammy64 using woof-CE will include missing firmware. Do I need to wait or initiate the ACTIONS-> Workflow right away ?
2. I am also building Ubuntu-Jammy64 on my laptop locally using FossaPup-9.5 as the build platform. After completing step ./3builddistro, I could not find any ISO or SFS files created.

FossaPup-9.5 is installed on an partition of 7 GB size by manually copying all SFS files, initrd.gz and vmlinuz to a local folder. Is the Puppy build running out of disk space ?
Do I need to allocate & specify Disk Size with Puppy when O/S is up & running ?

[dimkr]

1. Looks like rebuilding Ubuntu-Jammy64 using woof-CE will include missing firmware.

No, only after I 1) merge the fix 2) run the kernel-kit job to rebuild the kernel packages you use.

Do I need to wait or initiate the ACTIONS-> Workflow right away ?

No, only after the fix is merged and the kernels are rebuilt.

2. I am also building Ubuntu-Jammy64 on my laptop locally using FossaPup-9.5 as the build platform. After completing step ./3builddistro, I could not find any ISO or SFS files created.

Without the 3builddistro output there's not much I can say. There must be some error that you missed.

Generally speaking, 9.5 is a really bad choice for running woof-CE. It's very outdated by now: its CA certificates are old and some downloads fail.

Is the Puppy build running out of disk space ?

I don't know. Have you checked?

[RyPuppy]

...
Generally speaking, 9.5 is a really bad choice for running woof-CE. It's very outdated by now: its CA certificates are old and some downloads fail.
...

Which Puppy Linux ISO should I be installing to build fresh puppy ?
I need one where DEVX modules are pre-installed or readily available.

Thanks for the all timely suggestions...

[dimkr]

I run woof-CE on Vanilla Dpup, and I installed woof-CE's dependencies using apt.

[RyPuppy]

I had recently Installed Vanilla Pup from
https://github.com/dimkr/woof-CE/releas ... 04.61.iso

Ran into WiFi and Keyboard issues I had posted my observations earlier in the following post
viewtopic.php?p=70619&hilit=vanilla+pup#p70619

Installed Vanilla Pup from
https://github.com/dimkr/woof-CE/releas ... .04.61.iso.

Laptop : HP Pavillion x360 with TouchScreen.

Did a manual install by copying all the .SFS files into partition SDA6:/VanillaPup/ along with initrd and vmlinuz.
Booting successfully by adding the following GRUB entry
-----------------------------------------------------------------------------------------------
menuentry "0. Vanilla Pup 22.04.61 - Puppy Linux - [SDA6]" {
set root=(hd0, gpt6)
linux /VanillaPup/vmlinuz psubdir=/VanillaPup pmedia=atahd pupsfs=sda6
initrd /VanillaPup/initrd.gz
}
-----------------------------------------------------------------------------------------------
Directory SDA6: /VanillaPup
bdrv_vanillapup_22.04.61.sfs
fdrv_vanillapup_22.04.61.sfs
puppy_vanillapup_22.04.61.sfs
zdrv_vanillapup_22.04.61.sfs
initrd.gz
vmlinuz
-----------------------------------------------------------------------------------------------

Issues

1. Cannot find the option to configure WiFi network
- Puppy Setup -> Internet ==> can enable / disable Wired/Wireless Network. No Configuration option

2. Making configuration changes results in System Freeze.
- Can only move the cursor. System does not crash but ZERO response when clicking any of the menu items.
- I have to Hard Reboot by pulling the plug. Usually the last configuration change does go through and gets saved.

I am also running FossaPup on this machine with ZERO issues.

Any help is greatly appreciated.

I do have access to my Sons Gaming desktop with 64GB ram and is less than a year old. I have installed UBUNTU-22,04 as an App from Windows-11 Store.

Will I be able to build Puppy Linux from within UBUNTU ?
What additional packages that I may need to build WOOF on ubuntu ?

[dimkr]

Yes, it's possible to run woof-CE on Ubuntu. That's what https://github.com/puppylinux-woof-CE/w ... /build.yml does.

[RyPuppy]

Yes, it's possible to run woof-CE on Ubuntu. That's what https://github.com/puppylinux-woof-CE/w ... /build.yml does.

I ran "woof-CE build" on an Ubuntu-22.04 App/Emulator installed on Windows-11 O/S.

1) Cloning part of the build git clone https://github.com/puppylinux-woof-CE/woof-CE was successful.
2) .merge2out failed with the message to go with recent WOOFCE Puppy distro.

U-Woof-Failure.png (17.11 KiB) Viewed 948 times

[RyPuppy]

1. Looks like rebuilding Ubuntu-Jammy64 using woof-CE will include missing firmware.

No, only after I 1) merge the fix 2) run the kernel-kit job to rebuild the kernel packages you use.

Do I need to wait or initiate the ACTIONS-> Workflow right away ?

No, only after the fix is merged and the kernels are rebuilt.

I was trying to build woof-CE / Kernel-kit on an vanilladpup-9.2.23.iso running within VirtualBox. Kernel build failed and here's the associated 'build.log'.

build.log

Code: Select all

Vanilla Dpup 9.2.23 [x86_64]
gcc (Debian 10.2.1-6) 10.2.1 20210110
git version 2.30.2
mksquashfs version 4.4 (2019/08/29)

Jobs for make: 4
kernel_version=5.15.4
kernel_version_info=x86_64
Linux: 5.15.4
aufs=5.15
aufs_util=5.8
Downloading: ftp://ftp.yandex.ru/pub/linux/kernel//v5.x/linux-5.15.4.tar.xz
Downloading aufs-utils for userspace
This may take a long time as the firmware repository is around 200MB
Extracting the Aufs-util sources
BuildFHSM = false
Extracting the Aufs sources
Extracting the kernel sources
Adding Aufs to the kernel sources

patch -N -p1 < aufs5-kbuild.patch
./build.sh: line 601: patch: command not found
WARNING: failed to add some Aufs patches to the kernel sources.
Check it manually and either CRTL+C to bail or hit enter to go on

patch -N -p1 < aufs5-base.patch
./build.sh: line 601: patch: command not found
WARNING: failed to add some Aufs patches to the kernel sources.
Check it manually and either CRTL+C to bail or hit enter to go on

Do I still need to wait for another day before I can pull the code & run the build locally ?

[dimkr]

./build.sh: line 601: patch: command not found

apt install patch

Do I still need to wait for another day before I can pull the code & run the build locally ?

No, the fix (https://github.com/puppylinux-woof-CE/w ... 790b4608e9) is now merged. If you pull now, you'll have the fix.

If you prefer not to struggle with a local build, wait for https://github.com/puppylinux-woof-CE/w ... 3410879760 to finish.

[RyPuppy]

...
If you prefer not to struggle with a local build, wait for https://github.com/puppylinux-woof-CE/w ... 3410879760 to finish.

I continued with the Kernel-Kit build once the above job had completed. Kernel build is failing at the step make menuconfig and here is the build.log.

build.log

Code: Select all

...
Already up to date.
Extracting the Aufs-util sources
* aufs-util branch: 5.8
Branch 'aufs5.8' set up to track remote branch 'aufs5.8' from 'origin'.
Switched to a new branch 'aufs5.8'
BuildFHSM = false
Extracting the Aufs sources
Branch 'aufs5.15' set up to track remote branch 'aufs5.15' from 'origin'.
Switched to a new branch 'aufs5.15'
Extracting the kernel sources
Adding Aufs to the kernel sources
Reducing the number of consoles and verbosity level
Cleaning the kernel sources
  CLEAN   .config

You now should configure your kernel. The supplied .config
should be already configured but you may want to make changes, plus
the date should be updated.
Hit a number or s to skip:
1. make menuconfig [default] (ncurses based)
2. make gconfig (gtk based gui)
3. make xconfig (qt based gui)
4. make oldconfig
s. skip

Enter option: 1
make menuconfig
  HOSTCC  scripts/basic/fixdep
scripts/basic/fixdep.c:92:10: fatal error: sys/types.h: No such file or directory
   92 | #include <sys/types.h>
      |          ^~~~~~~~~~~~~
compilation terminated.
make[1]: *** [scripts/Makefile.host:95: scripts/basic/fixdep] Error 1
make: *** [Makefile:552: scripts_basic] Error 2

I did not have to use any DEVX..SFS for the Vanilla-PUP.ISO I am currently using. I have been installing the missing package/tool. (For example: , I had to install gcc, FLEX or BISON and many more ...)

Can I address the above error by installing missing package ?

Thanks for everyone's help.

[dimkr]

[Can I address the above error by installing missing package ?

https://github.com/puppylinux-woof-CE/w ... it.yml#L32

[RyPuppy]

I deleted al of my build-folders and initiated a fresh build.

steps followed so far

1. git clone ..woof-CE.. --> Successful
2. apt update
3. apt install build-essential
4. apt install -y --no-install-recommends curl wget ca-certificates git file squashfs-tools xz-utils diffutils patch make flex bison python3 bc bzip2 kmod rsync libelf-dev libssl-dev dwarves gcc gcc-multilib jq
5. apt install libncurses-dev
6. Build Kernel-Kit --> Successful
7. ./0setup --> Successful
8. ./1download --> seeing download failure all over the place

Sample Failure Log

Code: Select all

* Downloading libsdl2-2.0-0_2.0.20+dfsg-2ubuntu1.22.04.1_amd64.deb
  - from http://archive.ubuntu.com/ubuntu/pool/main/libs/libsdl2
/root/PuppyLinux/woof-out 100%[==================================>] 567.95K  1.78MB/s    in 0.3s    
/root/PuppyLinux/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/local/petget/verifypkg.sh: line 25: /tmp/petget_proc/pgks_failed_to_install_forced: No such file or directory
  failed (file not found or corrupted file)
  - from http://mirrors.kernel.org/ubuntu/pool/main/libs/libsdl2
/root/PuppyLinux/woof-out 100%[==================================>] 567.95K   993KB/s    in 0.6s    
/root/PuppyLinux/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/local/petget/verifypkg.sh: line 25: /tmp/petget_proc/pgks_failed_to_install_forced: No such file or directory
  failed (file not found or corrupted file)
  - from ftp.osuosl.org/pub/ubuntu/pool/main/libs/libsdl2
/root/PuppyLinux/woof-out 100%[==================================>] 567.95K  1.71MB/s    in 0.3s    
/root/PuppyLinux/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/local/petget/verifypkg.sh: line 25: /tmp/petget_proc/pgks_failed_to_install_forced: No such file or directory
  failed (file not found or corrupted file)
DOWNLOAD FAIL: libsdl2-2.0-0_2.0.20+dfsg-2ubuntu1.22.04.1_amd64.deb

* Downloading libseccomp2_2.5.3-2ubuntu2_amd64.deb
  - from http://archive.ubuntu.com/ubuntu/pool/main/libs/libseccomp
/root/PuppyLinux/woof-out 100%[==================================>]  46.31K  --.-KB/s    in 0.1s    
/root/PuppyLinux/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/local/petget/verifypkg.sh: line 25: /tmp/petget_proc/pgks_failed_to_install_forced: No such file or directory
  failed (file not found or corrupted file)

File DOWNLOAD-FAILS-deb-jammy has more 600 lines.

Is this behavior expected ?
Is the build script skipping any of the packages not needed for our build ?

[RyPuppy]

I have tried building Ubuntu-Jammy64 PuppyLinux locally many different ways, but always ends up in failure.

Success
I have been successful so far to build Puppy directly only on GitPub by following the Guide:
Building a Puppy on GitHub

https://github.com/puppylinux-woof-CE/w ... on-GitHub

Just this morning, I was able to build the following ISO's on GitHub
1) x86_64 - debian - bookworm64 - kernel-5.15x
2) x86_64 - slackware64 - 15.0 - kernel-5.15x
3) x86_64 - ubuntu - focal64 - kernel-5.15x
4) x86_64 - ubuntu - jammy64 - kernel-5.15x

FAILUREs

Tried to build x86-64-Ubuntu-Jammy64 locally by following Readme.MD - Preparation section " https://github.com/puppylinux-woof-CE/woof-CE "

Code: Select all

Clone   puppylinux-woof-CE/woof-CE from GitHub
./merge2out
cd kernel-kit;  ./build.sh
./0setup
./1download
./2createpackage
./3builddistro

The above scripts kept failing for missing utilities, download-file-corruption < though, I could manually download & view the same with no issues> and other reasons...

I have tried building the above in different linux variants ending in failure.

Question

1. What Puppy variant one should be using to build say 'ubuntu-jammy64' locally?
2. What additional Packages, .sfs's are needed for a successful build
3. If Script fails, do we just comment out / delete the code that is causing the failure and continue ? (e.g. it fails with rox-filer build)
4. Could one post details of their BUILD-ENVIRONMENT. so the new-comers like me can follow the same and have a good start
5. I am sure there must have been 100's of other posts going through this painful process of trying to learn the build process. Could we not make some of these Posts STICKY at the top, so new-comers can get to them quickly.

I acknowledge and am very greatful for the help, we in forum are receiving from member who are smart and have been at this for some time.

[RyPuppy]

I am trying to understand ..

1) If woof-CE build scripts work flawlessly to buid on GitHub with no issues, why do they fail on local build ?

2) Is it possible to capture DEBUG-LOG by modifying the build scripts on GitHub by adding "set -x" at the very top, so we get to see each line as they are executed. This will help us compare the RUN's between GitHub and local build.

On my local build, I do this to debug and understand where the failures are occuring and bypass them or fix them to some degree.

[Clarity]

I like your exposure, here. And your framing questions.

This leads one to think of a possible WoofCE PUP for local and remote WoofCE builds. The name of that WoofCE Development ISO filename could be something that identifies it as a Developer's Edition PUP containing:

• the PUP with its DEVX enclosed

• KVM modules loaded at boot

• SAMBA as most developers keep their dev projects on their central NAS

• A browser chooser that opens immediately after FirstRUN

• And any other subsystems that make this OOTB PUP ready to support most of the elements that devs use.

I am sure some WoofCE developer has already thought of such. But it might not have been forthcoming in the last year as 2 technologies are at play in the linux world currently: the maturing of Wayland and Pipewire. I think as soon as these are sorted in Puppyland, we just might see a developer's version emerge with the built-in characteristics addressing both the questions and the subsystems, answered. These sorted, means that when/if such a dev version emerges, it will not need be upgraded as often as the user distros in the forum.

[RyPuppy]

I like your exposure, here. And your framing questions.

This leads one to think of a possible WoofCE PUP for local and remote WoofCE builds. The name of that WoofCE Development ISO filename could be something that identifies it as a Developer's Edition PUP containing:

• the PUP with its DEVX enclosed

• KVM modules loaded at boot

• SAMBA as most developers keep their dev projects on their central NAS

• A browser chooser that opens immediately after FirstRUN

• And any other subsystems that make this OOTB PUP ready to support most of the elements that devs use.

I am sure some WoofCE developer has already thought of such. But it might not have been forthcoming in the last year as 2 technologies are at play in the linux world currently: the maturing of Wayland and Pipewire. I think as soon as these are sorted in Puppyland, we just might see a developer's version emerge with the built-in characteristics addressing both the questions and the subsystems, answered. These sorted, means that when/if such a dev version emerges, it will not need be upgraded as often as the user distros in the forum.

I can work towards building the Puppy-Build-ISO which can be used for local build of Pup's. Members can then define what the build environment needs to have like (1)Must & (2) Good-to-Have features.
say...
1) IDE - Integrated Development / Build Environment (similar to Eclipse if there is one)
2) Editors - gvim, gedit, ...
3) Package management - apt, dpkg ...
4) Documentation - tools
5) Debug tools when we get stuck
6) others...

One suggestion is - we need to add direct-sticky link to Puppy-Linux-WiKi page on this Forum main page. This helps us to build / constantly improve Help-Documentation w.r.t. PL.

Not everyone is aware of the current WiKi page - "https://github.com/puppylinux-woof-CE/woof-CE/wiki".

[RyPuppy]

Attempting one more time to build "Ubuntu-Jammy64" locally. Script 3builddistro is failing at the step : Installing HUGE kernel to build/

My build Platform : FossaPup.9.5

Disk Space usage

Code: Select all

FP: /mnt/home/PL # df -h .
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda6        11G  5.2G  4.9G  52% /initrd/mnt/dev_save

last part of script run : 3builddistro

Code: Select all

Executing sandbox3/pinstall.sh post-install script...
Configuring Puppy skeleton...
Configuring Puppy Help page...
Setting mtpaint -s as defaultscreenshot app
find: '/usr/lib/qt5/bin': No such file or directory
find: '/usr/lib/x86_64-linux-gnu/qt5/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/support': No such file or directory
find: '/usr/lib/qt5/bin': No such file or directory
find: '/usr/lib/x86_64-linux-gnu/qt5/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/support': No such file or directory
Clearing symlinks in /etc/ssl/certs...
done.
Updating certificates in /etc/ssl/certs...
127 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
ln: failed to create symbolic link 'usr/bin/xmessage': File exists
find: '/usr/lib/qt5/bin': No such file or directory
find: '/usr/lib/x86_64-linux-gnu/qt5/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/support': No such file or directory
find: '/usr/lib/qt5/bin': No such file or directory
find: '/usr/lib/x86_64-linux-gnu/qt5/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/support': No such file or directory
find: '/usr/lib/qt5/bin': No such file or directory
find: '/usr/lib/x86_64-linux-gnu/qt5/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/bin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/rootfs-skeleton/usr/sbin': No such file or directory
find: '/mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/support': No such file or directory

Setting Tahrpup to default

see /mnt/home/PL/woof-out_x86_64_x86_64_ubuntu_jammy64/sandbox3/rootfs-complete/usr/share/ptheme/globals for available themes
that you can specify in build.conf: PTHEME=<theme>
jwm colors: Stark_blueish
jwm tray: xf
jwm size: normal
jwm buttons: default
gtk: stark-blueish
icon theme: Puppy Standard
wallpaper: tahrpup.svg
rox icons arrangement (apps): Minimal_Labelled
rox icons arrangement (drives): Puppy bottom
icons: StandardSvg
cursor: Breeze_Snow
gtkdialog: default
done


pinstall.sh finished OK
setting PS1="\w\$ " as the CLI prompt.
Now setting /etc/os-release file

Installing HUGE kernel to build/
wget: missing URL
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.
Could not get kernel list
If you have connectivity issues (or the site is unreachable)
 place a huge kernel in the 'huge_kernel' directory
Type A in hit enter to retry, any other key to exit

Question:
1. Is it missing URL to download KERNEL in some config file and if so where I can check & update url info ?
2. Alternative is to place "huge kernel". Where can I download the appropriate kernel ?
3. I have'nt build 'kernel' during this run. Was skipping this step as per 'README.md' to try and use prebuilt-kernel. Am I missing a step here ?

Thanks in advance...

[dimkr]

You can download a prebuilt kernel from https://github.com/puppylinux-woof-CE/w ... el-kit.yml. Click on one of the job runs, then on the number below "Artifacts".