woof-CE needs you
new version of makepup
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
http://www.murga-linux.com/puppy/viewto ... 89#1021589
wiak
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
huge-4.19.12-bionicpup64.tar.bz2.sha256.md5.txt
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:
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.
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
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.
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
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...:
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
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'`
wiak
Last edited by wiak on Thu 14 Mar 2019, 02:17, edited 1 time in total.
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
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.
wiak
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
WeeDogLinux forum: https://weedoglinux.rockedge.org/viewforum.php?f=4
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
Tiny Linux Blog: https://www.tinylinux.info/
Check Firmware: http://murga-linux.com/puppy/viewtopic.php?p=1022797
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Which are the mature woof-ce projects?
As we move towards the next woof-ce build (Puppy 8.1) perfection is not required. Every Puppy is lovable.
Maturity is the criteria.
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?
Trying to get the potentials right here: http://wikka.puppylinux.com/Puppy9
Maturity is the criteria.
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?
Trying to get the potentials right here: http://wikka.puppylinux.com/Puppy9
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?!
i need puppy iso and devx sfs. What should i download and where should i put those files?!
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).
.
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.
What is your github username (url please)?mistfire wrote:Hello I made some not so massive changes to the rootfs skeleton of woof-ce. This will improve the puppy a lot especially the package management and portability
Find me on [url=https://www.minds.com/ns_tidder]minds[/url] and on [url=https://www.pearltrees.com/s243a/puppy-linux/id12399810]pearltrees[/url].
I have been wondering the sudden flurry of activities in github. I kind of guess it's you (since you said two posts above that you were going to push some changes), but it's good to have the confirmation. Way to go, mistfiremistfire wrote:@s243a rizalmart on github
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Some distros using Woof-CE use a k3.18.xxx version. Sailor Enceladus' Slacko5.7-WoofCE comes to mind first. That kernel branch has now gone UNSUPPORTED recently (I think in the last 2 weeks). As an info update here, kernel 3.16.70 (dated July 9 )is still available for 3-series needs.
Regards
8Geee
Regards
8Geee
Linux user #498913 "Some people need to reimagine their thinking."
"Zuckerberg: a large city inhabited by mentally challenged people."
"Zuckerberg: a large city inhabited by mentally challenged people."
I try to build upupbb from github. It say that MPlayer-1.4-i686_ubb1903.pet could not found.
Downloading MPlayer-1.4-i686_ubb1903.pet
Where is the link exactly?
Thank you.
Downloading MPlayer-1.4-i686_ubb1903.pet
Code: Select all
- from http://smokey01.com/peebee/upupbb/extras/pet_packages-upupbb
failed (file not found on server or could not finish download)
- from https://raw.githubusercontent.com/puppylinux-woof-CE/woof-CE-noarch/master/pet_packages-upupbb
failed (file not found on server or could not finish download)
- from http://distro.ibiblio.org/puppylinux/pet_packages-upupbb
failed (file not found on server or could not finish download)
- from http://ftp.nluug.nl/ftp/pub/os/Linux/distr/puppylinux/pet_packages-upupbb
failed (file not found on server or could not finish download)
- from http://ftp.cc.uoc.gr/mirrors/linux/puppylinux/pet_packages-upupbb
failed (file not found on server or could not finish download)
- from ftp://mirror.aarnet.edu.au/pub/puppylinux/pet_packages-upupbb
Thank you.
Now uploaded - thanks for report.........recobayu wrote:I try to build upupbb from github. It say that MPlayer-1.4-i686_ubb1903.pet could not found.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
-
- Posts: 1543
- Joined: Mon 22 Feb 2016, 19:43
I tried building a vanilla slacko 5.8.10 woof-CE iso today and uploaded it here:
http://www.mediafire.com/folder/p7599c75b8l19/5.8CE
It's missing a few icons, a few things don't work (like x-virtual keyboard), and doesn't include a browser by default, but might be useful or interesting to someone. It's been working well enough for me for an hour or so.
http://www.mediafire.com/folder/p7599c75b8l19/5.8CE
It's missing a few icons, a few things don't work (like x-virtual keyboard), and doesn't include a browser by default, but might be useful or interesting to someone. It's been working well enough for me for an hour or so.
- Attachments
-
- Screen.jpg
- the default theme
- (32.97 KiB) Downloaded 549 times