Another Jammy64pup

[Jasper]

I just made a new LibreOffice package ............ has a single desktop entry under Document.

Works in Fossapup64-5 && JammyPUp64

Libre-Office-7.6.4 - (Approx 196mb - en US & GB dictionaries)
https://www.mediafire.com/file/bizmuuh1 ... 4.pet/file

[Jasper]

I was wondering if it is worth continuing with this.

Ubuntu 24.04 LTS is due for release on 25th April 2024.

A beta should be made beforehand.

[rockedge]

I think it's worth continuing the development of this Jammy64pup. It is possible that Ubuntu 24.04 will exclude running on some computers that are really not that old. And the polish on this is getting better and better with the big plus that it works well.

Plus it is a problem that there are not enough active developers at the moment to make the additions to woof-CE to be able to build a next gen Ubuntu based Puppy Linux.

We are looking for new Developers to join the team at Puppy Linux!!

New Contributors adding talent and skills to build the next generation operating systems and bring them it to Life!

[mistfire]

I think it's worth continuing the development of this Jammy64pup. It is possible that Ubuntu 24.04 will exclude running on some computers that are really not that old. And the polish on this is getting better and better with the big plus that it works well.

Plus it is a problem that there are not enough active developers at the moment to make the additions to woof-CE to be able to build a next gen Ubuntu based Puppy Linux.

We are looking for new Developers to join the team at Puppy Linux!!

New Contributors adding talent and skills to build the next generation operating systems and bring them it to Life!

Maybe it's time to move the target computer of Puppy Linux. The target hardware of Puppy Linux was late 90's and 2000's PC (aka Windows 9x and XP) era pc. It's now time to move the target platform to 2009 model pc (aka Windows 7/8.x/10 era PC) onwards as Windows 11 with high hardware requirements became mainstream and rendered those kind of PC's obsolete despite they have compelling performance.

[dimkr]

From what I read, Canonical is evaluating the possibility of dropping support for anything that doesn't support x86_64-v3 and that's all pre-2015 hardware (if I'm not mistaken) plus many budget CPUs.

IMO it's a waste of time trying to build an Ubuntu-based Puppy: this distro is systemd-only, packages like browsers are slowly converted to snaps (and snap depends on systemd), and hardware support is narrower. Every new Ubuntu release is a more "hostile" base for Puppy than the one before.

Debian is a much better choice: it still supports sysvinit (and has working init scripts needed by Puppy), it has a huge repo with things like browsers, it doesn't force snap on users, and it's way more conservative.

I left the woof-CE organization after I made woof-CE capable of building a Debian-based Puppy with a native Wayland desktop, PipeWire and overlay - no X.Org, no aufs, no GTK+ 2. Anyone can continue this development and ship what could be the best Puppy ever, by the time Debian 13 is out.

[ozsouth]

@dimkr wrote:

From what I read, Canonical is evaluating the possibility of dropping support for anything that doesn't support x86_64-v3 and that's all pre-2015 hardware (if I'm not mistaken) plus many budget CPUs.

IMO it's a waste of time trying to build an Ubuntu-based Puppy: this distro is systemd-only, packages like browsers are slowly converted to snaps (and snap depends on systemd), and hardware support is narrower. Every new Ubuntu release is a more "hostile" base for Puppy than the one before.

Wow. That is disturbing, given how popular ubuntu pups are. Slackware is basically immune to this trend, but has never had the wider appeal. Many of us here are around 70 & cannot reach the level required to develop woof-ce. If Vanilla Dpup is it, then long may it reign.

[wiak]

IMO it's a waste of time trying to build an Ubuntu-based Puppy: this distro is systemd-only, packages like browsers are slowly converted to snaps (and snap depends on systemd), and hardware support is narrower. Every new Ubuntu release is a more "hostile" base for Puppy than the one before.

Through usage I've become a big fan of the XFCE version of Linux Mint nowadays (in the past I used LXDE Linux Mint, but really didn't like it at all). And that Linux Mint is based on Ubuntu but gets rid of all the forced snap stuff and provides Internet browsers as deb packages still - maybe a Pup based on Linux Mint repos would be better alternative to Ubuntu, for those, like myself, who aren't so much into Debian itself? Also, I happen to prefer systemd or runit, though not necessarily essential, but using systemd seems to be less problematic when it comes to setting up some of the modern expected system facilities; so much documentation around seems to expect systemd availability (but yes, choice is a good thing otherwise).

[Clarity]

Actually, what @mistfire and @dimkr are sharing is consistent with a presentation I reviewed and published about on the forum's Chromebook thread.

The open-source firmware replacement group who are working with Intel, AMD, Google, Tovalds, etc recommend nothing earlier than 2018, for now.

I, personally, have 3 Chromebooks (intel and ARM) used for my productions needs that are 2021 and 2022. ALL of my other 64bit PCs used in testing are like me...OLD...very OLD.

This post is not to raise objections from members, rather, this post and the couple above me are talking about open-source and industry efforts afoot. WE dont make the rules.

P.S. I have no axe to grind if SystemD, SysV or any. All most every user coming to this forum are seeking useable stable distros for some productive abilities.

[dimkr]

The open-source firmware replacement group who are working with Intel, AMD, Google, Tovalds, etc recommend nothing earlier than 2018, for now.

If you're talking about those projects to replace Chromebook firmware with standard UEFI, etc', this statement is 100% irrelevant to computers other than Chromebooks. No distro supports these computers out-of-the-box, because they need their firmware to be replaced with coreboot without Google's modifications first. This is not a case of hardware support that gets phased out.

[Clarity]

@dimkr I DID NOT GET THAT from those authors. I kinda disagree with your comment. I am not trying to provoke you, but, am merely sharing the information they presented.

Hope this comment is seen as information. You can review for yourself. I published the weblink on the Chromebook thread.

[dimkr]

information.

Information, but irrelevant and out of context.

[sonny]

@mistfire, @rockedge
Ain't it ironic that we always want to improve the software (o/s) for hardware that we refuse
to upgrade? Technology is evolving. Let alone the economic law of diminishing returns.

[Jasper]

libpng-1.6.42 - PNG library
https://www.mediafire.com/file/qjzvghyz ... 4.pet/file

[Jasper]

Testing!!! Did not add all the libraries ........easy enough to build though

geeqie-GIT-26-02-2024 - an image viewer
https://www.mediafire.com/file/ghcgvuu9 ... 4.pet/file

[Clarity]

hi @Jasper

@user1234

For testing ...

Is there an update for your version 8+ (I only have an v8.0 RC version, from you, from months ago before QEMU's stable release.)

Curious.

[Jasper]

@Clarity

I have just looked at the Qemu website and there are several builds available.

Is there a particular one you would like to try?

8.2.1
Jan 29th 2024

8.1.5
Jan 29th 2024

8.0.5
Sep 21st 2023

[Clarity]

8.2.1 will cover any user who may want to run VMs that emulate other CPUs in the current technology universe.

QEMU site.png (150.37 KiB) Viewed 992 times

But 8.1 should work as well.

[Jasper]

@Clarity

I added 8.20 in this thread earlier:
viewtopic.php?p=110285&hilit=qemu#p110285

[Jasper]

@user1234

I notice that you are still creating test ISO's for this build.

I might be wrong, but I think you are not including the FFMpeg libraries.

Therefore mpv will provide you with video playback.

The build I tested was:

This I reported in the NoblePup thread as well:

viewtopic.php?t=10791

Previously, I did say that I was using JRB's ISO, which does contain FFMpeg 4.2.2.

@dimkr

Is there an outstanding issue here?

[user1234]

@user1234

I notice that you are still creating test ISO's for this build.

I might be wrong, but I think you are not including the FFMpeg libraries.

Therefore mpv will provide you with video playback.

The build I tested was:

This I reported in the NoblePup thread as well:

viewtopic.php?t=10791

Previously, I did say that I was using JRB's ISO, which does contain FFMpeg 4.2.2.

@dimkr

Is there an outstanding issue here?

You're using those test builds? I publish those since I want to use wget to fetch those before doing any commits.

Maybe I should have described them better, like FOR TEST!!!!, but I didn't since I thought no one would be actually viewing them . Actually, the other jammys except jammy64-alpha1 is only for test for me, but you can decide to use them; beware, those builds could be buggy!

Diodon one was basically a failure, since I found that didon won't paste images after copying 'em; you'll have to copy, then go to history and select the image, and then it will allow to paste. So, I decided to look into the diodon issue later on.

---

About ffmpeg, I think I and @dimkr talked about it earlier while adding deadbeef - ffmpeg is big!

I am not sure if it should be added (@dimkr can help).

---

Therefore mpv will provide you with video playback.

I am afraid but I am unable to understand this sentence. Could you please explain more?

[Jasper]

@user1234

It should have read as

"herefore mpv will not provide you with video playback."

Yes, I am using the Test builds .......... isn't this the purpose and to provide feedback to the developer?

I mostly use Fossapup64-95 daily, but use JammyPup on another device as it has updated GlibC, GCC etc.

Which makes it easier to compile new applications.

[user1234]

"herefore mpv will not provide you with video playback."

Video playback works fine on Jammy64. I suppose the issue came with noble64 (I have not started working with that one).

Yes, I am using the Test builds .......... isn't this the purpose and to provide feedback to the developer?

What happens is that whenever I finish some work, I'll run a test build for myself and since I want to use wget to download the test build, I'll have to make it public by publishing it. I use them for testing stuff myself, and thus may not be completely polished.

I thought no one would be following my personal woof-CE fork, so I just release them, 'cause I am a bit lazy and do not want to mess with gh stuff . Once satisfied with the build, I try to get them merged into official woof-CE.

Since there is no official Jammy64 right now, my recommendation is that you use your own fresh build from official woof-CE repo. It is quite simple, just a few button clicks (guide here: https://github.com/puppylinux-woof-CE/w ... -on-GitHub).

Otherwise, you can use https://github.com/lakshayrohila/woof-C ... 0.0-alpha1, which I have devoted to anyone who wants to download Jammy64 built with (almost) latest official woof-CE changes.

[Jasper]

Okay

[Jasper]

This is a simple application and should be able to be compiled for various builds of PuppyOS.

xcoral-4.02.1 - Multi window mouse-based text editor for Unix and X Window System.
https://www.mediafire.com/file/5dbfgqbd ... 4.pet/file

[Jasper]

@user1234

Can you test this for me?

REMOVED

In my build of JammyPup, I get an error when I enter this command into terminal:

Code: Select all

openssl s_client -connect redhat.com:443 -brief

When you use my updated build you do get information back.

[user1234]

@Jasper,

Pardon me, but I don't exactly know what that command does.

I ran it in my VM.

It seems to get some information, but I am unsure if it is the one required:

Screenshot_20240325_220452.png (36.92 KiB) Viewed 653 times

This was the default openssl which I tested with.

[Jasper]

@user1234

Can you try the same command NOT using the OpenSSL that I uploaded?

Do you get the same result?

[user1234]

@user1234

Can you try the same command NOT using the OpenSSL that I uploaded?

Do you get the same result?

That was run NOT using the OpenSSL that you uploaded.

---

EDIT:

I get this error using your PET:

Screenshot_20240325_221451.png (17.48 KiB) Viewed 645 times

[Jasper]

@user1234

Thanks for this.

I am getting mixed results.

The default build returns incomplete info.

Where as my new build gives the same information you posted.

[Jasper]

Some application updates:

bash-5.2.21 - Bourne Again SHell
https://www.mediafire.com/file/sogamm7u ... 4.pet/file

opus-1.5.1 - Audio codec
https://www.mediafire.com/file/i2hkan7g ... 4.pet/file

wavpack-5.7.0 - Audio codec
https://www.mediafire.com/file/6j186quv ... 4.pet/file

xz-5.6.1 - Compression library
REMOVED (30 March 2024)--- Please uninstall this application ASAP
More info here:
https://www.phoronix.com/news/GitHub-Disables-XZ-Repo

The default xz version in JammyPup should be