woof-CE needs you
-
- Posts: 109
- Joined: Sat 29 Jul 2017, 03:16
- Location: Wisconsin
Are you using the testing (default) branch of woof-CE?
I renamed my local-repositories/arm/packages-pet directory to force re-downloading all pets, but still don't get any errors.
The latest version of the testing branch (commit 50b0b21) should work properly!?!? I have been testing it and can't duplicate the problems...
I renamed my local-repositories/arm/packages-pet directory to force re-downloading all pets, but still don't get any errors.
The latest version of the testing branch (commit 50b0b21) should work properly!?!? I have been testing it and can't duplicate the problems...
-
- Posts: 109
- Joined: Sat 29 Jul 2017, 03:16
- Location: Wisconsin
[edit] This can't be the problem because downloading still works.
I seem to be able to duplicate the errors in ERROR-2CREATEPACKAGES by deleting the old woof-out directory, running ./merge2out again but skipping ./0setup
After running ./merge2out you have to change to the woof-out* directory and run
./0setup
./1download
./2createpackages
./3builddistro-Z
in order. If the previous step completed successfully you can re-run the next step, but when you run ./merge2out you have to start again at the beginning.
I seem to be able to duplicate the errors in ERROR-2CREATEPACKAGES by deleting the old woof-out directory, running ./merge2out again but skipping ./0setup
After running ./merge2out you have to change to the woof-out* directory and run
./0setup
./1download
./2createpackages
./3builddistro-Z
in order. If the previous step completed successfully you can re-run the next step, but when you run ./merge2out you have to start again at the beginning.
-
- Posts: 109
- Joined: Sat 29 Jul 2017, 03:16
- Location: Wisconsin
-
- Posts: 109
- Joined: Sat 29 Jul 2017, 03:16
- Location: Wisconsin
here's a debian buster 64bit build recipe that can be unzipped & added to your extracted woofce folder.
note that whilst this creates a working puppy, it is a bit of a mongrel as it's using various packages from tahr,xenial & bionic, including bionics kernel.
but you can use it as a starting point, for compiling it's native applications and kernel
EDIT: re uploaded after 1 download
note that whilst this creates a working puppy, it is a bit of a mongrel as it's using various packages from tahr,xenial & bionic, including bionics kernel.
but you can use it as a starting point, for compiling it's native applications and kernel
EDIT: re uploaded after 1 download
- Attachments
-
- dpupbuster64.zip
- (19.58 KiB) Downloaded 200 times
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
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
added a 32bit recipe and fixed devx so compiler should now work in dpupbuster64musher0 wrote:Thanks for this, 666philb.
Would you happen to have a 32-bit version handy?
(No pressure, just asking!)
TIA.
- Attachments
-
- dpupbuster_woofce_32&64.zip
- (39.21 KiB) Downloaded 200 times
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
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Both versions...666philb wrote:added a 32bit recipe and fixed devx so compiler should now work in dpupbuster64
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
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
hi peebee,peebee wrote:Both versions...666philb wrote:added a 32bit recipe and fixed devx so compiler should now work in dpupbuster64
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
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
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
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.
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)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
The provision of a zip is so that you can add this to woof-ce yourself manually....musher0 wrote:There was a delay in incorporating your new recipe into the woof-CE, perhaps?
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
- josejp2424
- Posts: 556
- Joined: Sun 01 Aug 2010, 22:35
- Contact:
woof-ce dpup-buster
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
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 196 times
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.
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)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
@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.(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.
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
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)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
hi musher0,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.(Lines 225-226 of file _00build.conf)Code: Select all
rm -r usr/lib/xorg/modules/input/kbd_drv.so rm -r usr/lib/xorg/modules/input/mouse_drv.so
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.
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
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
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.
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)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)