DistroWatch needs a newer Puppy version listed for Puppy Linux!!!!!

[williwaw]

The "default Woof-CE BookwormPups" (64-bit & 32-bit) are found at:
https://github.com/puppylinux-woof-CE/w ... okworm.yml

This is what radky enhances to produce his BookwormPup64

Built from "testing"?
Incorporating many of the fixes dimkr brought to the project?

[rockedge]

Built from "testing"?
Incorporating many of the fixes dimkr brought to the project?

Yes, I believe so.

[peebee]

The "default Woof-CE BookwormPups" (64-bit & 32-bit) are found at:
https://github.com/puppylinux-woof-CE/w ... okworm.yml

This is what radky enhances to produce his BookwormPup64

Built from "testing"?
Incorporating many of the fixes dimkr brought to the project?

Yes & Yes all changes - "testing" is the only branch that gets updated......

[wanderer]

hi all

it appears to me that we are ready to go

i am assuming that radky and peebee have given their approval

and that bookworm 64 and 32 check all the boxes

i am going to contact distrowatch and begin the process of submitting our new candidates

if anyone objects post now or forever hold your peace

wanderer

[dimkr]

The "default Woof-CE BookwormPups" (64-bit & 32-bit) are found at:
https://github.com/puppylinux-woof-CE/w ... okworm.yml

This is what radky enhances to produce his BookwormPup64

With many modifications - many added packages, big changes in quicksetup, ... it's very far from being reproducible using stock woof-CE.

The dpup built by stock woof-CE is very different from @radky's BookwormPup64, and it's not a good starting point if you want to take over the project and release your own so-called 10.0.7.

[rockedge]

it appears to me that we are ready to go

i am assuming that radky and peebee have given their approval

Yes they have with the footnote that support will be limited in scope.

[wanderer]

hi dimkr

to address your concerns

this time i think we should just submit these excellent distros
since they are ready and we need a new candidate to keep distrowatch active
this i will do

however
we will need a new candidate in about 1 year

i do think it would be interesting and useful
to have a completely reproducible woof-ce puppy
that anyone could just run and get a fully working puppy with no problems
i think it should be based upon debian 12
since in my opinion debian has the most pakages and support
it should have both a 64 and 32 bit version

now is actually a good time to start working on this
since time flies

wanderer

[wanderer]

hi all

i have sent an email to distrowatch to begin the process of submitting radkys bookworm 64 and peebees bookworm 32 as our new candidates
this is a process but should not take too long

now is the time to begin to work on our next submission
which we have a year to complete

an error free woof-ce full featured base distro of debian 12 in both 64 and 32 bit

would any of the puppy gurus be willing to take on this task ?

wanderer

[wanderer]

hi all

jesse at distrowatch has emailed me back

wow that was fast

he says all we need is
a screenshot
and a link to the projects release announcement
they will do the rest

i also think we should update the description

could someone post these on this thread so i can copy them and email them to distrowatch

wanderer

[rockedge]

BookwormPup64 10.0.6 is a primary Woof-CE build of Puppy Linux based on Debian 12.5 binaries

BookwormPup64 highlights
• Local Woof-CE build of Bookworm64 (with customized desktop presentation)
• GTK3 graphical interface (with GTK2 limited to a few legacy applications)
• X.org graphical server (rather than Xwayland)
• Overlay file system (rather than Aufs)
• Apt/Synaptic package management provided by the included bdrv. The original Puppy Package Manager (PPM) is also included but functionality is now constrained to minimize conflict with Apt/Synaptic. Even so, PPM retains compatibility with legacy pet packages.
• DKMS support (Debian's out-of-tree driver building infrastructure) which includes the kbuild.sfs (small builtin subset of the traditional kernel sources). See Note-1 below.
• Bluetooth support
• ConnMan network manager
• Pipewire audio
• Zstd rather than xz compression of SFS files (faster decompression and lower CPU consumption, but 8-15% increase in SFS size)
• Generous assortment of builtin applications available in each menu category (or use APT/Synaptic package management to install your choice of additional applications available in the comprehensive Debian repositories)
• Firefox-ESR browser included as the sole application in the optional adrv. Please note: the adrv is easily removed if a different internet browser is preferred. Additionally, in this release there is no default ydrv, so the user may optionally create and populate a supplemental ydrv with preferred applications.
• Desktop management by JWMdesk-3.7 and companion applications, plus the added convenience of the versatile Synapse Application/File Launcher. For Synapse usage guidelines, please go to Puppy Menu -> Help -> HOWTO use the Synapse Application Launcher.

Note-1: BookwormPup64 supports non-free firmware and DKMS builds of out-of-tree kernel modules.

Note-2: The BookwormPup64 iso is larger than other recent Pups, primarily due to (1) zstd compression of SFS files, (2) support for DKMS and Apt/Synaptic package management, and (3) expanded hardware support in the comprehensive Debian-based fdrv and zdrv.

BW64.jpg (24.33 KiB) Viewed 1600 times

BookwormPup64 10.0.6 Changelog
• New Woof-CE build of BW64 (4 Mar 2024) including Debian 12.5 binary/security updates plus new Woof-CE code that enables enhanced grub2 booting (thanks gyrog). See Note-1 below.
• New kernel build (6.1.76) including upstream Debian fixes/updates plus additional Woof-CE kernel configuration parameters for improved support of eMMC drives (thanks gyrog)
• Add NoteCase Notes Manager (thanks proebler)
• Add libdvdcss library for playing DVD media (thanks OscarTalks)
• Add xserver-xorg-input-evdev library for input events such as laptop suspend on lid closure (thanks retiredt00)
• Add convenient browser access to tldr pages (concise linux man pages). Go to Menu -> Document -> TLDR Pages
• Adjust freedesktop.org.xml mime-types to support m3u/m3u8 media playlists in ROXFiler (thanks OscarTalks & Peebee)
• Adjust laptop suspend parameters to resume without activating Xlock ScreenSaver. If you prefer resuming with Xlock activated (which requires a password to continue to a functional desktop), please go to /etc/acpi/acpi.conf and enable the call to Xlock by prepending (commenting) DISABLE_LOCK with a simple hash mark, #DISABLE_LOCK (thanks amethyst).
• Move Boot Manager to the System menu category (thanks Jasper)
• Move ScreenLiner to the Graphic menu category (thanks MochiMoppel).
• Update install and uninstall functionality of the legacy Puppy Package Manger (thanks rerwin)
• Update legacy Connectwizard to support Connman Internet Connection Manager. This enables on-the-fly switching to/from Connman and legacy Puppy connection utilities such as SNS, Frisbee or Network Wizard (thanks rerwin). ConnMan is the recommended internet connection manager for BW64 but the legacy options are available if you require or prefer an alternate connection manager.
• Update help files for (1) Internet Access and (2) APT package manager (Go to Menu -> Help)
• Update Firefox ESR to 115.8.0
• Bugfix: failed registration of DNS nameserver (null value in resolv.conf) when rebooting with Connman Internet Connection Manager (thanks rerwin)

Note-1: Per gyrog's description, enhanced grub2 booting is provided by new Woof-CE code (in woof-code/support/mk_iso.sh) that generates updated loopback.cfg and grub.cfg files.

The loopback.cfg will now boot Puppy with optional "img_dev=" and "img_loop=" boot parameters. The 'isoboot' script in initrd.gz is already capable of handling these parameters. The new "img_dev=" parameter is the UUID of the partition that contains the ISO file. If the optional "img_dev=" parameter is provided in the linux line of grub.cfg, the 'isoboot' script in initrd.gz does not have to search the partitions for the ISO file.

The updated code that generates the enhanced loopback.cfg is also supported by the new grub.cfg. The functionality of grub.cfg has not really changed, except it now displays a message at boot time indicating if both ucode.cpio and initrd.gz have loaded (or just initrd.gz).

[wanderer]

thank you so much rockedge

you are the man

i will send this in asap

wanderer

[wanderer]

hi all

info has been sent to distrowatch
they may need more stuff
but will email me if they do

so we will wait and see

wanderer

[wanderer]

and now for something completely different

if bigpup had not mentioned that we needed a new distrowatch candidate
we would not have noticed anything was amiss and there would have been a mad scramble
thank you bigpup

however this should not happen again
we need to be alert and proactive

what i propose is
that we develop a candidate ahead of time
so it is ready when we need it

a 1 year time period is about the longest we want to wait
since after 2 years distrowatch will mark us as dormant

as i have posted before
the candidate i would like to see developed is

an error free woof-ce full featured base distro of debian 12 in both 64 and 32 bit

so that *** anyone *** can simply run woof-ce and have a working distro

this base can then continue to be developed hopefully for a very long time

there may be other candidates to choose from
but at least this one will always be available

i have virtually no development skills
but i dont want to wait for others to step up
so i am going to try to start things right now

how i will do it is
i will flounder around
and try to get others to help me

the worst that can happen is that this comes to nothing
and i simply continue to be a pest
but that would not be a significant change in my usual activities as a puppy community member

so this is a formal request to the puppy gurus and the entire puppy community to help this project succeed

i will now try to figure out the basics of the very arcane and complex woof-ce

i will be annoying you all soon

have a nice life

wanderer

[darksun]

I apology as I am likely OT with this short message here but I wish to give it a little bit of visibility.
I have been using *UNIX since more than 20 years and changed many desktop distros. I have fallen in love with puppy linux, its philosophy and its devs; despite I dont post very often in here , https://forum.puppylinux.com is my most bookmark link clicked by far, I read most of the messages that are posted in all the forums.
Apart from words of appreciation I have donated some money to the puppy community and planned a yearly donation at least.
This message of mine is just a wish and kind reflection and a call to whoever can afford to contribute with some cash to this wonderful community of nice people.
I am now ready to be horsewhipped because of this OT message, just dont aim at my genitals.

[peebee]

the candidate i would like to see developed is

an error free woof-ce full featured base distro of debian 12 in both 64 and 32 bit

so that *** anyone *** can simply run woof-ce and have a working distro

Hi @wanderer

BookwormPup32 is already a "woof-ce full featured base distro of debian 12 in 32 bit".......

BookwormPup64 could become so with some work..........

This suggests to me that the "next" Pup should be something different.........

[bigpup]

I say keep it simple.

When someone releases a new version of Puppy and others use it.
Respond with positive posts about it.
It gets any bug fixes or needed improvements.
Seems ready to be the next Puppy version for DistroWatch.

We need to push the issue of getting it submitted to DistroWatch.

I guess we could make a topic where people could post their suggestions,

That was basically what this topic turned into.

[retiredt00]

BookwormPup64 could become so with some work..........

I believe woof-CE has the tools to detect differences between a modify distribution and its woof-CE counterpart and generate patches.
Couldn't it be used to make radky's bookworm as "official" as one desires?

[dimkr]

I believe woof-CE has the tools to detect differences between a modify distribution and its woof-CE counterpart and generate patches.
Couldn't it be used to make radky's bookworm as "official" as one desires?

No, the delta is big. I started extracting the manual changes in BookwormPup64 10.0.6 so we can upstream them into woof-CE. The list is long, and there a magic 'fix-dpup' script that runs at the end of the build. We don't have it because the modified woof-CE tree used to build 10.0.6 isn't available to us.

[retiredt00]

and there a magic 'fix-dpup' script that runs at the end of the build.

Ah yes, that convenient but dreadful thing.
I have noticed that there is a woof-build.conf file that has some configurations/changes/etc for the specific build.
Maybe could be made to pass also the fix-* script (assuming the builder wants to provide it)
This would allow reproducibility (and upstreaming) with minimal effort from the builder.
So if Radky makes a 10.0.7 with that, should be OK.

[Clarity]

Hi ALL

... BookwormPup64 could become so with some work..........

This suggests to me that the "next" Pup should be something different.

I agree with both of these comments. Further, as I know the work is being done in the background on WoofCE GIT by @peebee, @rockedge, @dimkr, @radky and others on GIT, this project looks to meet what I think was the original objective or WoofCE.

This is GREAT as it goes from project thru a development cycle to a completed project landing on Distrowatch (DW). This effort is similar in what FATDOG has done for awhile. As such, it will renew a PUPPY presence on DW, as the old presence is years old.

PeeBee mentions "something different": Assuming he is referencing a candidate, there are several which come to mind and there is the new Noble Ubuntu LTS, as well. Of course, we'll need a 64bit version community edition for taking it thru the paces of development-test phases..

@darksun shares that he has experience that grandfathers Linux; namely Unix. He just may be what the community needs with his background as one of the testers of this project as it goes thru the normal reports of issues that surface with all distros from time to time. His contributions I'm sure is welcomed.

Looking forward to whatever I can; assisting as I go.

@bigpup, @wanderer and others over the past weeks ... THANK YOU!!!

[dimkr]

If you want something 'different', there's a Debian Trixie build configuration in woof-CE that produces a "pure Wayland" Puppy with labwc, sfwbar and spacefm. It produces fully reproducible builds, without any prebuilt .pet packages. It's smaller and lighter compared to what you'd get if you copy-paste BookwormPup64 and rebuild it with the (in development, constantly changing) Debian Trixie packages. On two old laptops of mine, it eats 50-100 MB less RAM and web browsing feels much faster. Take it, develop it, polish it and you'll get a great Puppy release by the time Debian Trixie is out (2025?).

[wanderer]

hi all

wow (in my opinion) this is great (thanks clarity)
if we can have a thread (or use this one)
to keep our eye on the next distrowatch candidate
i think it could be used to do a lot of good things

1. get the whole community involved

2. give the gurus a challenge (which they like)

3. clean up woof-ce (to make reproducible and error free builds)

and probably other things i haven't thought about yet

so the process is (1 year cycle)

1. evaluate and decide on a candidate to develop

2. develop it

3. present it to distrowatch

repeat next year

seems cool to me

wanderer

[fredx181]

@wanderer Although I enjoy seeing your enthusiasm , but really... not all realistic: "easier said than done"

[wanderer]

i know fredx181

but the nice thing about all this is
it costs nothing to discuss things on a thread

we could simply talk about which of the already developed distros we want to present next to distrowatch

we would then be ready when we want to update the page

and it would get the whole community involved

so cheap fun

and thanks for all the work you gurus have done
i am able to use puppy instead of windows because of you

wanderer

[wanderer]

hi all

so this is our new project

we have submitted radkys bookworm64 and peebees bookworm32 to distrowatch
they have not contacted me back
so i assume they are working on changing the page

so now is the time to discuss and settle on the next distrowatch candidate
(we have a 1 year timeframe)

it can be a new one that will be developed
or any developed distro on the puppy forum
i have always felt that its a puppy if the puppy community says its a puppy (but who am i)

any nominations or comments

wanderer

[Jasper]

@wanderer

I found this online and it might be useful to know, I have not tried it myself

[wanderer]

thanks jasper

looks cool

i did use woof-ce or woof a long time ago
and i may try it again
but the devil is in the details
it gave an incomplete distro
so it needed a guru to troubleshoot it

but it is a cool system
and its fun playing with it

wanderer

[Jasper]

@wanderer

One day, I will have to try it myself!!!

Goodluck

[williwaw]

@wanderer

I found this online and it might be useful to know, I have not tried it myself :oops:

numbat?
clone?

if I understand using github correctly, a clone would be for building your own version whereas forking would be better for a collobarative build?

and somehere I can not find at the moment, @dimkr has posted a method for building as a github action that could be forked?

not entirely up to speed with github usage myself , but if a few different folks were to colloborate on the next build, theres is a github workflow that could ease the the building process when more than one arere involved.

[wanderer]

hi all

here are 2 questions relevant to this thread

1. how many distros listed on the forum today would everyone feel comfortable submitting as the next candidate on distrowatch

and

2. if the gurus were interested in developing a new distro what would it be

wanderer