woof-CE needs you

News, happenings
Message
Author
Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1221 Post by Sailor Enceladus »

Hi belham2,

If you do a build of stretch now, or try the puduan build I uploaded a few days ago, I think your response to it will be something like this. ;) I haven't even tried to patch the jwm-2.3.6 it pulls from Debian yet, so I'm still paranoid that everything will fall apart every time I click the menu, someday... haha. radky's Dpup Stretch 7.5 is definitely the go-to place if you want to get a polished dpup and receive great feedback I think, similar to OscarTalks and Tuuxxx's iso (and yours) in the past. I consider dpup woof-CE branch "a fun base" to work with and build upon which shines when someone makes it their own, same as it always was.

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

woof-CE needs you

#1222 Post by Billtoo »

I did a Puduan b1 build:

System: Host: puppypc4469 Kernel: 4.9.76 i686 (32 bit) Desktop: JWM 2.3.6 Distro: Puduan 7.0.0b1
Machine: Device: desktop System: Hewlett-Packard product: HPE-410f serial: MXX0370KF3
Mobo: FOXCONN model: 2AB1 v: 1.00 BIOS: American Megatrends v: 6.02 date: 07/21/2010
CPU: Hexa core AMD Phenom II X6 1045T (-MCP-) speed/max: 800/2700 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/7570]
Display Server: X.org 1.11.3 driver: radeon tty size: 139x26 Advanced Data: N/A for root
Network: Card-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 1063.1GB (0.6% used)
Weather: Conditions: 39 F (4 C) - light drizzle Time: January 10, 10:38 PM EST
Info: Processes: 204 Uptime: 1 min Memory: 128.5/8091.6MB Client: Shell (bash) inxi: 2.3.5

Added applications with PPM,changed kernel.
I can't get kpat to run, using Firefox-52.5.0 ESR.

It's working pretty well, dual booting from a 64gb flash drive with Stretch-700b1
Attachments
screenshot.jpg
(121.25 KiB) Downloaded 1042 times

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1223 Post by Sailor Enceladus »

I tried a puduan-7.0.0b1 (Devual Ascii) build with woof-CE today. Here's the iso:
http://www.mediafire.com/file/2u3k4rpkwmaba9c
md5sum: 61557bb57b8cbf7cfe273e28264c9c64

The devx is inside, the only thing I did was compile a kernel 4.4.111 nopae and use it in _00build.conf.
I updated this iso to woof-CE commit 5805 too. No more dbus errors :) Trying kpat in ppm again now.

edit: ppm told me a lot of packages for kpat were missing, but they just seem to be missing _i386 or _all at the end?
edit2: reverting this change seems to fix it, for some reason: https://github.com/puppylinux-woof-CE/w ... 1f595f4d09
Attachments
capture32351.png
puduan-7.0.0b1 and kpat
(57.46 KiB) Downloaded 991 times

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1224 Post by mavrothal »

Sailor Enceladus wrote:
I tried a puduan-7.0.0b1 (Devual Ascii) build with woof-CE today. Here's the iso:
http://www.mediafire.com/file/2u3k4rpkwmaba9c
md5sum: 61557bb57b8cbf7cfe273e28264c9c64.
:?
just tried it (fresh download-pupmode 5)
No issue with PPM.
Maybe an old savefile with outdated package database?
Attachments
before.png
(143.38 KiB) Downloaded 911 times
after.png
(149.44 KiB) Downloaded 919 times
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1225 Post by Sailor Enceladus »

Hi mavrothal,

Thanks for testing! The issue is when you try to download "kpat" from ppm. It has 136 dependencies. :lol: I tried it to see what problem Billtoo had. libkf5item was just the first one it complained about, I looked it up in ppm later to see if actually existed. ;) I tried grabbing it manually, then kpat said it only needed 135 dependencies, so I suppose you could search every package kpat wants, download them manually, then grab kpat and it will work, or just change ^ to -F for this particular package (kpat). :)

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#1226 Post by mavrothal »

Sailor Enceladus wrote:Hi mavrothal,

Thanks for testing! The issue is when you try to download "kpat" from ppm. It has 136 dependencies. :lol: I tried it to see what problem Billtoo had. libkf5item was just the first one it complained about, I looked it up in ppm later to see if actually existed. ;) I tried grabbing it manually, then kpat said it only needed 135 dependencies, so I suppose you could search every package kpat wants, download them manually, then grab kpat and it will work, or just change ^ to -F for this particular package (kpat). :)
Not quite sure but this change appears to fix it.
Attachments
kpat.png
(95.59 KiB) Downloaded 830 times
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

#1227 Post by slavvo67 »

Mav,

Not sure if I mentioned but it's good to see you back!

Slavvo67

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1228 Post by Sailor Enceladus »

I tried a "slacko current" build today with the latest woof-CE:
http://www.mediafire.com/folder/kldh509odczdb

edit: Will probably do another update to it soon to refine a few libs.
Attachments
Screenshot.png
(36.33 KiB) Downloaded 415 times

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

#1229 Post by musher0 »

Hello all.

I am beginning to understand the file database DISTRO_PKGS_SPECS-ubuntu-xenial.
(Please keep your comments to yourselves.) ;)

As an example:
If I wish to have a non-jwm Puppy, I put a "no" instead of a yes in front of any jwm line
in that database. Correct?

Now let's say that I wish to provide echinus as a WM instead of jwm. Please forgive my
somewhat childish questions:

-- I create in that database a new line for echinus, yes?
Something like < yes|echinus||exe >, yes?

-- Do all entries in that DB have to be in alphabetical order? My "echinus" entry will have
to be in the proper place with the files beginning with "e", yes?
I cannot place it below the lines concerning "jwm", right?

-- In field 1, do I include the full filename of the echinus pet I have available?
Or just "echinus"?

-- I leave the second field empty, since it is a pet located locally. Yes?

-- Where do I put my echinus pet in the woof-CE local structure so it is incorporated?
In /mnt/sda7/local-repositories/x86/packages-pet?

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

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1230 Post by Sailor Enceladus »

Hi musher0,

I think you got the jist of it. I would also do step 2 here ;)
http://www.murga-linux.com/puppy/viewto ... 639#956639

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

#1231 Post by musher0 »

Many thanks, Sailor E.
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:

#1232 Post by rockedge »

I am working on building an Xenial 64 with woof-CE and using the the kernel #31... I get this error and the ./3builddistro-Z fails and stops.

Code: Select all

huge-4.9.58-xenialpup64.tar.bz2         : 5ef4ab0c3c097b3301cba549a279d410
huge-4.9.58-xenialpup64.tar.bz2.md5.txt : #
5f6c5e1addcc105928c25c0d20de07ce
#
fe94dce1a8be442dbf85774282c0fcbda5931e74
#
4415f572a8f17c14229e5829dab76902e35bb4b2334dc7f42d64418bd71e6fcc
checksum failed
anyone have some insight as to what is going on?
Last edited by rockedge on Sat 03 Feb 2018, 23:35, edited 1 time in total.

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1233 Post by Sailor Enceladus »

@rockedge: I think the syntax in the md5 file is messing things up:
http://distro.ibiblio.org/puppylinux/hu ... z2.md5.txt

I guess it should look more like this:
http://distro.ibiblio.org/puppylinux/hu ... z2.md5.txt

It seems 3builddistro-Z gets confused and grabs the 3rd one from the file (SHA256) or all 3 instead of just the first (MD5).

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

#1234 Post by rockedge »

@Sailor Enceladus
Thanks for the quick info! what you say seems true. Any suggestions before I begin to look into fixing it?

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

#1235 Post by musher0 »

Hello all.

What's with the new woof-CE for xenialPup-7.5 creating xenialpupsave-blabla.?fs
pupsaves instead of plain xenialsave-blabla.?fs pupsaves?

706 version had plain xenialsave pupsaves. Hehe, the new xenialPup-7.5 is getting wordy!
This is not a criticism, I just find it funny.

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

Lassar
Posts: 235
Joined: Tue 08 Jul 2014, 20:01

woof-ce stops working at end of 3builddistro-Z script

#1236 Post by Lassar »

woof-ce stops working at end of 3builddistro-Z script.

I am using xenialpup64-7.5 frugal install with a save folder.

I get this error.

*** INITRD: initrd.gz [x86_64]
*** /DISTRO_SPECS: xenialpup64 7.5 x86_64

chroot: can't execute 'echo': No such file or directory
ERROR: could not 'chroot' into sandbox3/rootfs-complete
This means that something is incomplete, perhaps a library
needed by bash. Check it out. Have to exit script now.

The only change I have made is to _00build.conf

Code: Select all

#
#  persistent configuration options
#
#  see also DISTRO_SPECS DISTRO_PET_REPOS DISTRO_COMPAT_REPOS-*
#
#  **NOTE**: check the original file every once in a while
#            settings might be added or removed...
#

#----------------
#support/findpkgs (called by most scripts)
#----------------
## set to 'no' to speed up process..
CHECK_PKG_DEPENDENCIES=yes

#----------
# 1download
#----------
## this will check all remote pkg repos and choose the working ones
CHECK_REMOTE_PKG_REPOS=yes

#----------
# 2download
#----------
# binaries are usually already stripped. set to 'no' to speed up process
STRIP_BINARIES=yes

#-------------
# 3builddistro
#-------------

## -- Live CD --
## The default is to use the traditional Puppy Live CD (isolinux)
## However there are 2 other options.
## UEFI_ISO overrides GRUB4DOS_ISO if both are set to YES..
## UEFI_ISO also supports legacy BIOS booting
##    On 32 bit systems this will still boot legacy BIOS however it
##      Will not boot 32 bit UEFI machines. These are rare anyway.
UFEI_ISO=yes
G4DOS_ISO=no

## UnionFS: aufs or overlay
## the kernel must properly support your choice
UNIONFS=aufs

## Kernel tarballs repo URL
## for choosing/downloading kernel
KERNEL_REPO_URL=http://distro.ibiblio.org/puppylinux/huge_kernels

## Kernel tarball URL
## avoid being asked questions about downloading/choosing a kernel
#KERNEL_TARBALL_URL=http://distro.ibiblio.org/puppylinux/huge_kernels/huge-3.14.55-slacko_noPAE.tar.bz2

## an array of generically named programs to send to the ADRIVE, FDRIVE, YDRIVE
## ADRV_INC="abiword gnumeric goffice"
ADRV_INC=""
## YDRV_INC=""
YDRV_INC=""
## FDRV_INC="" #this one is very experimental and it's recommended to be left unset
FDRV_INC=""

## Include kernel-kit generated FDRIVE
## set to yes or no or leave commented to be asked the question at build time
#KFDRIVE=no

## build devx? yes/no - any other value = ask
#BUILD_DEVX=yes

## include devx SFS in ISO?
DEVX_IN_ISO=no

## Include the windows puppy installer LICK
## by Luke Lorimer aka <noryb009>
LICK_IN_ISO=no

## compression method to be used (SFS files)
SFSCOMP='-comp xz -Xbcj x86 -b 512K'
#SFSCOMP='-comp xz'
#SFSCOMP='-comp gzip'
#SFSCOMP='-noI -noD -noF -noX'

## if "$WOOF_HOSTARCH" = "$WOOF_TARGETARCH"
## Would you like to strip all binary executables and shared library files?
## These are usually already stripped, although some packages may have the shared
## library files stripped with the '--strip-debug' option only, and extra stripping
## should be okay. It won't do any harm answering yes here.
EXTRA_STRIPPING=yes

## -- Dependency check --
## if $WOOF_HOSTARCH" = "$WOOF_TARGETARCH"
## The script can optionally do a thorough dependency check
## This may take a long time.
CHECK_BINARY_DEPS=yes

## PPM2 or the Classic gui for PPM?
UICHOICE=PPM2

## Puppy is normally run as the 'administrator' (root) user, though there is
## also 'fido' which is not currently very mature.
## The structure of Puppy is such that we consider root to be safe (with a full
## disclaimer of any responsibility if anything does go wrong), but there is a
## compromise, to run as root but to run Internet apps as user 'spot'.
## Note, in a running Puppy 'Menu->System->Login & Security Manager'
##    can be used to enable or disable running as spot.
RUN_INTERNET_APPS_AS_SPOT=no

## Certain Xorg drivers require KMS (Kernel ModeSetting)
## A value of '1' means on, '0' means off.
## assume not using kms at all when boot from sd card (arm arch).
KMS_i915=1
KMS_radeon=1
KMS_nouveau=0

## -- Xorg Auto --
## - This overrides DISTRO_XORG_AUTO in DISTRO_SPECS..
## - For ARM it's always set 'no' (may be changed)
## Do you want Xorg to start automatically at first boot (or at 'pfix=ram'
## kernel boot param) or run Xorg Wizard? The latter has been the case for
## earlier puppies. Automatic startup of X usually works, though in some
## cases may choose the wrong monitor resolution or driver -- which can be"
## fixed by running Xorg Wizard afterward. (yes/no)
XORG_AUTO=yes

## -- Xorg Text DPI (dots por inch) --
## this is overriden by PTHEME - $DEFAULT_THEME_XORG_TEXT_DPI
## see 'rootfs-complete/root/.Xresources' for the current value
## You can specify a font dpi if you wish
##   ...72 78 84 90 96 102 108 1114 120..
XORG_TEXT_DPI=114

## -- pTheme -- applies only if ptheme pkg is being used
##    woof-code/rootfs-packages/ptheme/usr/share/ptheme/globals
## You can choose a ptheme here if you wish
## otherwise 3builddistro will ask you to choose one
#PTHEME="Dark Touch"
#PTHEME="Dark Mouse"
#PTHEME="Bright Touch"
PTHEME="Bright Mouse"

## -- ROX desktop text - black --
## The ROX-Filer desktop text defaults to white with black shadow, but this is
## not best for some light backgound images.
ROX_TEXT_BLACK=no

## ROX-Filer defaults to 'DejaVu Sans 10' font for the desktop. 
## If you would prefer bold text 'DejaVu Sans Bold 10',
## type in a full font specification (ex: Mono 12)
ROXFILER_FONT=DejaVu Sans 12

## -- Xload in JWM --
## By default xload is displayed in JWM. You can disable it here...
JWM_XLOAD=yes

## -- Custom wallpapers -- if mkwallpaper is in $PATH
## Do you want to build some custom wallpapers?
CUSTOM_WALLPAPERS=no

## -- Locale --
## Puppy is built with a default locale LANG=en_US and keyboard layout KMAP=us,
## which may be changed after bootup.
## However, if you are building a language-specific Puppy, you may change the
## defaults. But, please do make sure that your Puppy has a 'langpack' PET
## for your language installed -- if one does not exist, then you will have to
## create one -- see MoManager in the Utility menu, also read the Menu -> Help
## -> HOWTO Internationalization.
## see valid locales in /usr/share/i18n/locales
## (the default is en_US.UTF-8)
DEFAULTLANG=

## -- Keyboard layout --
## Default is english (en, us, "")
## Choose another one if you wish..
##   azerty be-latin1 br-abnt2 br-abnt br-latin1-abnt2 br-latin1-us by cf
##   croat cz de de-latin1 dk dvorak dvorak-l dvorak-r es et fi fr
##   gr hu101 hu il it jp106 lt mk nl no pl pt-latin1 ro ru
##   se sg sk-qwerty sk-qwertz slovene sv-latin1 uk us wangbe
KEYMAP=

## -- Default Apps --
## Not all are implemented in the puppy scripts,
##   but you can specify a default app if you wish...
## If you specify a value it will override anything that previously
##   set that value in the corresponding script...
## These are the current default*apps (scripts) in /usr/local/bin
DEFAULTAPPS="
defaultarchiver=
defaultaudioeditor=
defaultaudiomixer=
defaultaudioplayer=deadbeef
defaultbrowser=
defaultcalendar=
defaultcdplayer=deadbeef
defaultcdrecorder=
defaultchat=hexchat
defaultchmviewer=
defaultconnect=
defaultcontact=
defaultdraw=
defaultemail=claws-mail
defaultfilemanager=
defaulthandler=
defaulthtmleditor=
defaulthtmlviewer=defaultbrowser
defaultimageeditor=
defaultimageviewer=
defaultmediaplayer=
defaultpaint=
defaultpdfviewer=
defaultprocessmanager=
defaultrun=
defaultscreenshot=
defaultspreadsheet=
defaultterminal=urxvt
defaulttexteditor=
defaulttextviewer=
defaultwordprocessor=
"

## - extra commands --
## Here add custom commands to be executed inside sandbox3/rootfs-complete
EXTRA_COMMANDS="rm usr/share/X11/xorg.conf.d/10-amdgpu.conf
sed -i 's/rox/defaultfilemanager/g' root/Choices/ROX-Filer/PuppyPin
sed -i 's/Height>22/Height>28/g' root/.jwm/jwmrc-personal
sed -i 's/"24"/"MENHEIGHT"/g' etc/xdg/templates/_root_.jwmrc
sed -i 's/"24"/"16"/g' /root/.jwmrc
rm -r root/.config/rox.sourceforge.net/MIME-types/application_x-sharedlib
rm -r usr/share/themes/Raleigh
rm -r usr/share/themes/stark-blueish
rm -r usr/share/themes/FlatBlueContrast
rm -r usr/bin/xcalc
rm -r root/.config/autostart/pmcputemp.desktop
rm -r usr/share/applications/Xcalc-scientific-calculator.desktop
rm -r usr/share/applications/jcontrol.desktop
cp -r root/firstrun/yassm usr/local
cp -r root/firstrun/yassm-search.desktop usr/share/applications
rm -r root/firstrun/yassm
rm -r root/firstrun/yassm-search.desktop
cp -r root/firstrun/jwmrc-personal root/.jwm
cp -r root/firstrun/.jwmrc-tray root
cp -r root/firstrun/globicons root/.config/rox.sourceforge.net/ROX-Filer
cp -r root/firstrun/jwmrc-theme root/.jwm
rm -r lib64
ln -s lib lib64
"

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

Re: woof-ce stops working at end of 3builddistro-Z script

#1237 Post by 01micko »

Lassar wrote:

Code: Select all

rm -r lib64
ln -s lib lib64

:?: :!:
Puppy Linux Blog - contact me for access

Lassar
Posts: 235
Joined: Tue 08 Jul 2014, 20:01

#1238 Post by Lassar »

This code was originally in _00build.conf , I never changed it.

Code: Select all

rm -r lib64
ln -s lib lib64
How would the above code affect chroot?


Been doing some research, and the error seems to be associated with chroot.

Maybe there should be a mount -bind before it?

Lassar
Posts: 235
Joined: Tue 08 Jul 2014, 20:01

Have a question about packages?

#1239 Post by Lassar »

Trying to make a bare bones slacko.

Was looking at DISTRO_PKGS_SPECS and noticed that it didn't really show separate libraries for gcc.

For example gcc in packages-slacko take up about 100 mb.

Don't need gcc, only need about 3 libraries taking up about 3 to 4 mb.

If I edit the gcc packages to only include what shared libraries I need, would woof-ce think there is something wrong with the packages I edited.

Or would this work?

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#1240 Post by Sailor Enceladus »

@Lassar: I think gcc is here:
https://github.com/puppylinux-woof-CE/w ... -14.2#L228

exe>dev means gcc_dev all goes into the devx, I guess the packages-slacko/gcc_lib folder is the only one what would go into the puppy.sfs.

Post Reply