woof-CE needs you

News, happenings
Message
Author
User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

#1351 Post by 666philb »

peebee wrote:
666philb wrote:added a 32bit recipe and fixed devx so compiler should now work in dpupbuster64
Both versions...
defaultscreenshot=mntpaint -s
in
_00build.conf

doesn't look quite right....should be mtpaint -s

Access to :
Packages-puppy-bionic-official
zz_busterfix.pet

would be needed for 32-bit build (they're not on ibiblio I think)

Likewise
zz_busterfix64.pet
for 64-bit build
hi peebee,

i uploaded the zz_busterfix pets to the test folder on ibiblio and added it to DISTRO_PET_REPOS so it should grab them.
I've no intention of taking dpupbuster any further, i haven't the time, but if anyone does want to, there's now a base recipe to work from. strip it, add to it, refine it.

If you want a pure puppy debian, you'll need to remove tahrs,xenials & bionics repos from DISTRO_PET_REPOS. go through the build process and check the FINDPKGS-NOT-FOUND.log & the create packages fail log. and then compile these packages in dpupbuster + a kernel.

and ultimately you would make your own zz_fix or at least remove the cruft and alien libs from mine
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#1352 Post by musher0 »

Hi 666philb .

I tried both the woof-CE testing and master, and none had an entry for
creating a DPup-Buster.

There was a delay in incorporating your new recipe into the woof-CE,
perhaps?

I'm not promising anything, but I'd like to look at it. And please do not feel
pressured, I'm in no hurry.

TIA.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#1353 Post by peebee »

musher0 wrote:There was a delay in incorporating your new recipe into the woof-CE, perhaps?
The provision of a zip is so that you can add this to woof-ce yourself manually....
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#1354 Post by musher0 »

" 'I see,' said the blind man." (Proverb)

Thanks.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
josejp2424
Posts: 556
Joined: Sun 01 Aug 2010, 22:35
Contact:

woof-ce dpup-buster

#1355 Post by josejp2424 »

Those who want to try dpup-buster configuration.
Base made on configuration of 666philb.

huge-kernel-4.19.20 dpup-buster
http://www.mediafire.com/folder/usx4dfn2dnfdz/woof-ce
Attachments
buster-woof-ce.tar.bz2
(17.21 KiB) Downloaded 192 times

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#1356 Post by musher0 »

Hi josejp2424.

Thanks, but your mention of 666philb is not reassuring. Did he iron out the bugs in the
recipe he handed me three weeks ago?

666philb is a great Puppy developer, this community owes him a great deal and I do not
want to insult him. Even the best people can be prone to oversights and such. That is
simply being human.

Here is what I am not clear about: (paragraph edited 2019-03-11, 17:23)
is this the Woof-CE YOU, josejp2424, used to create YOUR DPupBuster-7.9.0.2? I am
not testing anything else, after what I went through 3 weeks ago. Pls see:
http://murga-linux.com/puppy/viewtopic. ... 83#1018471
and
http://murga-linux.com/puppy/viewtopic. ... 83#1019065
(end of edit)


Sorry for being so frank.

Best regards to you and all.
Last edited by musher0 on Tue 12 Mar 2019, 14:42, edited 2 times in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#1357 Post by musher0 »

mfb wrote:Reserved
A wise way to be indeed.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#1358 Post by musher0 »

@josejp2424:

I looked at it, and the archive you made available above contains the same non-sense
for older computers in the config file as in the config file offered in the package that
666philb uploaded a couple of pages ago in this thread.

Code: Select all

rm -r usr/lib/xorg/modules/input/kbd_drv.so
rm -r usr/lib/xorg/modules/input/mouse_drv.so
(Lines 225-226 of file _00build.conf)

666philb explained elsewhere that those lines are supposed to be compensated by
other X configs for touch-enabled screens. But removal of those X drivers prevents a
user with a non touch-enabled screen from using the mouse and keyboard once (s)he
gets on the X desktop.

Sorry, I'm not testing anything that contains the above. Please inform me by PM or
otherwise when and where you will have uploaded your recipe for your
DPupBuster-7.9.0.2. TIA. On the other hand, if you wish to keep your recipe a "trade
secret", that's ok too. Nobody will be offended (at least not me).

Best regards.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
666philb
Posts: 3615
Joined: Sun 07 Feb 2010, 12:27
Location: wales ... by the sea

#1359 Post by 666philb »

musher0 wrote:@josejp2424:

I looked at it, and the archive you made available above contains the same non-sense
for older computers in the config file as in the config file offered in the package that
666philb uploaded a couple of pages ago in this thread.

Code: Select all

rm -r usr/lib/xorg/modules/input/kbd_drv.so
rm -r usr/lib/xorg/modules/input/mouse_drv.so
(Lines 225-226 of file _00build.conf)

666philb explained elsewhere that those lines are supposed to be compensated by
other X configs for touch-enabled screens. But removal of those X drivers prevents a
user with a non touch-enabled screen from using the mouse and keyboard once (s)he
gets on the X deskhttps://ftp.nluug.nl/os/Linux/distr/puppylinux/huge_kernels/huge-3.0.103-tahr_noPAE_retro.tar.bz2top.

Sorry, I'm not testing anything that contains the above. Please inform me by PM or
otherwise when and where you will have uploaded your recipe for your
DPupBuster-7.9.0.2. TIA. On the other hand, if you wish to keep your recipe a "trade
secret", that's ok too. Nobody will be offended (at least not me).

Best regards.
hi musher0,

the above fix does work ... check /usr/lib/xorg/modules/input/ in josejp2424s running dpupbuster. kbd & mouse aren't there and your mouse & keyboard are working fine.

i've just discovered myself though whist trying old tahrpup builds that it doesn't work in some kernels, and possibly you used an old kernel in your build where it doesn't work.

don't give up trying woof! & i'm always happy to try and help
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#1360 Post by musher0 »

Hi 666philb.

Thanks for your kind words. I'm not giving up per se on woof-CE.

However, what purpose would it serve that I now try to build another DPupBuster? We
already have a fantastic one, thanks to josejp2424! I do not wish to be his competitor.
All of us here with a certain experience of Puppy should rather try to collaborate. Or at
least keep out of each other's way.

If another "monkey" wishes to try "woofing" a DPupBuster to gain some experience,
that's fine.

As for me, I'm on to other things already.

Once I get some feedback on the beta version there, I'll translate it into English, and
perhaps ask José or Galbi for a Spanish translation as well. I believe Puppy does not
have such a detailed "histories" application; except my old "MRUF-lst", which I now
think was overkill, retrospectively.

Best regards.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

new version of makepup

#1361 Post by wiak »

new version of makepup released but needs testing. I may try DPupBuster 'recipe' on it, but since that hasn't been uploaded to woof-CE github as yet the option isn't available in this current makepup release.

http://www.murga-linux.com/puppy/viewto ... 89#1021589

wiak

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

huge-4.19.12-bionicpup64.tar.bz2.sha256.md5.txt

#1362 Post by wiak »

So I tried a woof-CE build of BionicPup64 using makepup -g

All seemed to go fine till very near the end (frustrating) when I got this woof-CE script result error output:

Code: Select all

--2019-03-14 10:35:38--  http://distro.ibiblio.org/puppylinux/huge_kernels/huge-4.19.12-bionicpup64.tar.bz2.sha256.md5.txt
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2019-03-14 10:35:38 ERROR 404: Not Found.

cat: ../huge_kernel/huge-4.19.12-bionicpup64.tar.bz2.sha256.md5.txt: No such file or directory
huge-4.19.12-bionicpup64.tar.bz2.sha256         : 991b487b150caeb263dd03bed643216c
huge-4.19.12-bionicpup64.tar.bz2.sha256.md5.txt : 
*** WARNING: no checksum
Verifying tarball integrity...
ERROR
So I opened my browser and manually tried the url:

http://distro.ibiblio.org/puppylinux/hu ... 56.md5.txt

and the result was: 404 Not Found.

Makepup doesn't generate the huge kernels list that is downloaded by woof-CE itself via recipe provided by the distro builder, so seems to be something wrong with the BionicPup64 woof-CE recipe (I suspect it is asking for a different kernel version but that version is not yet uploaded to ibiblio?) EDIT: No. Seems to not be working cos the ibiblio stored 4-19.12 hugekernel file is using sha256 checksum rather than md5.

Please let me know.

wiak

EDIT: Ah... Forget it. I'm have asleep cos was up all night. I think I selected the sha256 file as if it was the kernel itself! No wonder it didn't work. :-)
Last edited by wiak on Wed 13 Mar 2019, 22:12, edited 4 times in total.

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

#1363 Post by wiak »

EDIT: refer to my immediately next post for what I think is 'solution'

Regarding the above:

Forget it. My mistake as my edit above explains. I need to sleep. But first I'll try again, since I had put wex, weav, and scrox dotpets into makepup's pets2add folder and I didn't see them being automatically added to the build as the woof-CE scripts terminal output rolled by. Maybe they were, maybe they weren't (EDIT: that bit is fine, I had simply forgotten click Advanced Options checkbox that indicates pet2add is to be used). I'll report back of course on final result.

However, makepup is currently set to use hugekernel selection choice 24 from the list, which turns out to be that sha256 file. It would be nicer if I only got makepup to display the actual hugekernel files rather than everything ibiblio dir provides - alas, that would need some extra preprocessing so users better be careful to make sure it is actual hugekernel they are selecting in makepup (I will however change the current default from 24 to an actual hugekernel number and reupload makepup).

EDIT: fixes now being implemented for soon to be uploaded version 0.1.8

http://www.murga-linux.com/puppy/viewto ... 80#1021680

BionicPup64 build now in progress via makepup 0.1.8; all looking good thus far.

EDIT: Hmmm... I've still got a problem with that sha256 file being thought of as the kernel... I'm working on it. Now trying a straight woof-CE build to see what the difference is.
EDIT2: I'm thinking support/hugekernel.sh in woof-CE may not be accounting for that ibiblio repo hugekernel list sha256* checksum file case (expecting md5sum or no checksum only?), but still to verify and raise issue on woof-CE github if required. I haven't altered the code dealing with all that in makepup, but maybe something has altered at woof-CE in connection with that which I am not aware of?
EDIT3: Line 199 (choose_kernel function) in support/hugekernel has the following, but no grep -v for sha256 case. Might be more to it than that, or something different...:

Code: Select all

for j in `ls -1 ../huge_kernel/*.tar.* 2>/dev/null |grep -v 'md5'`
Should that sha256 extension of one entry I see in the hugekernel repo actually be an md5, or does it need processed as sha256 I wonder (grep -v sha256 etc)? Seems to me the existing wget code in there (line 116) is expecting md5.txt extension. So the hugekernel choice numbering might be getting messed up by that woof-CE script because of that sha256.txt entry being counted in by that script?

wiak
Last edited by wiak on Thu 14 Mar 2019, 02:17, edited 1 time in total.

wiak
Posts: 2040
Joined: Tue 11 Dec 2007, 05:12
Location: not Bulgaria

#1364 Post by wiak »

Following on from my immediately above post, it seems to me that as the code stands in woof-CE/hugekernel.sh, in ibiblio hugekernel repo we need:

huge-4.19.12-bionicpup64.tar.bz2.md5.txt

rather than a:

huge-4.19.12-bionicpup64.tar.bz2.sha256


Or just remove the entries for that kernel version at ibiblio altogether...

of woof-CE is not counting kernel choice variable in /support/hugekernel.sh correctly (and not hiding sha256 entry using grep -v, but that alone won't fix issue probably since only md5sums seem to be getting calculated anyway).

One thing for sure, makepup has problems with the count choice number because of the bz2.sha256 file in the repo for that huge kernel. If I sed out (like grep -v) the sha256 entry in makepup choice window, the result won't match how current support/hugekernel.sh script is seeing things. sha256 file shouldn't be getting regarded as an actual kernel! So easiest 'fix' (disclaimer: I think...) is just to change what is in ibiblio huge kernel repo to a md5.txt as above.

I won't for now upload my next makepup version until issue checked/fixed(?) at woof-CE repo since I think that is where the problem is - I've raised issue on woof-CE github accordingly. Many thanks in advance to the woof-CE team for looking into this for me. If the problem isn't what I currently think, I'll check makepup code itself more thoroughly later for an alternative.

EDIT: But yeah, anyway, I seem to be correct: just done manual woof-CE build and the support/hugekernel.sh choice of huge kernel is including the sha256 file in the listing, which is clearly wrong. I could just leave that to display in makepup too, but would rather not since md5.txt entries are being correctly hidden. If I hide the sha256 file from list displayed my makepup combo then the count used becomes wrong - needs to same count as that done by support/hugekernel.sh, which is why I need that modified or the sha256 file changed to an md5.txt file at ibiblio huge kernel repo.

Code: Select all

23 huge-4.19.12-bionicpup64.tar.bz2
24 huge-4.19.12-bionicpup64.tar.bz2.sha256
25 huge-4.19.23-bionicpup64.tar.bz2
26 huge-4.2.5-slacko64.tar.bz2
27 huge-4.4.70-s32-700_PAE.tar.bz2
28 huge-4.4.70-s64-700.tar.bz2
29 huge-4.4.95-xenial.tar.bz2
30 huge-4.9.13-xenial_noPAE.tar.bz2
31 huge-4.9.13-xenialpup64.tar.bz2
32 huge-4.9.15-xenialpup64.tar.bz2
33 huge-4.9.30-s64-700.tar.bz2
34 huge-4.9.58-xenialpup64.tar.bz2
wiak

User avatar
Lobster
Official Crustacean
Posts: 15522
Joined: Wed 04 May 2005, 06:06
Location: Paradox Realm
Contact:

Which are the mature woof-ce projects?

#1365 Post by Lobster »

As we move towards the next woof-ce build (Puppy 8.1) perfection is not required. Every Puppy is lovable. :mrgreen:

Maturity is the criteria. 8)

What we got? :?:

Slacko7
32bit, 64bit Slackware base, WoofCE
Disco Dingo
Ubuntu base, 32bit, 64bit, WoofCE
DevuanDog
Devuan base (Debian derivative)
ScPup

Is that about right? What am I missing? :roll:
Trying to get the potentials right here: http://wikka.puppylinux.com/Puppy9
Puppy Raspup 8.2Final 8)
Puppy Links Page http://www.smokey01.com/bruceb/puppy.html :D

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#1366 Post by musher0 »

A Devuan build, known in Puppy Land as a "Puduan", and
a Trisquel build, known in Puppy Land as a "LibrePup".
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
rockedge
Posts: 1864
Joined: Wed 11 Apr 2012, 13:32
Location: Connecticut, United States
Contact:

#1367 Post by rockedge »

Corepup.......based on TinyCore

laslo_one
Posts: 2
Joined: Sat 25 May 2019, 07:29
Location: Ukraine

#1368 Post by laslo_one »

Hey, guys! Trying to build a puppy for myself and i'm running into a problem. I'm currently using ARch Linux and want to build a puppy live cd. I've downloaded woofce from git and tried to start it, but i get an error:
i need puppy iso and devx sfs. What should i download and where should i put those files?!

foxpup
Posts: 1132
Joined: Fri 29 Jul 2016, 21:08

#1369 Post by foxpup »

You should use a Puppy or on Arch "run-woof".
Read the README on github.

It is quite easy to install a Puppy frugally (preferred way for Puppy) next to your Arch.
Find a recent Puppy here: http://puppylinux.com/download.html
The frugal install from Arch:
- Make a folder for Puppy in the partition of your choice. This can be where your Arch resides, or not.
Preferably, but not necessarily a 'linux partition' (ext2/3/4).
- Copy initrd.gz, vmlinuz and the .sfs files from the iso into the folder
- Add an entry for Puppy to your current bootloader. If you need examples for this, let us know what bootloader you use.

devx sfs is in ibiblio or you can find a link in the release notes or on the first page of the forum thread for the Puppy version you use.
Make a pupsave (a folder on a linux partition or a file on vfat or ntfs) on first shutdown to save the sessions.
Use SFS_load to load devx sfs (or any other sfs). It will be loaded automatically on next startups.
When you use run-woof from Arch, you will not need devx, it should use the compilers in Arch (I think).
.
Last edited by foxpup on Sat 25 May 2019, 09:53, edited 5 times in total.

foxpup
Posts: 1132
Joined: Fri 29 Jul 2016, 21:08

#1370 Post by foxpup »

.

Post Reply