woof-CE needs you

[rcrsn51]

Either the pets should be updated...

I would be happy to update them if you would identify the ones that you think need updating.

[radky]

Re: Stretch-7.0.0a2 iso, built with Woof-CE testing 07-Oct-2017, base kernel 4.1.38

Did some testing of a frugal install in a Dell Vostro desktop.
Looking very nice and working well.

The InkscapeLite needs the ruler patch. I believe the source with this applied was uploaded to ibiblio here:-
http://distro.ibiblio.org/puppylinux/sources/i/

Running checkdeps -system mentions the missing libspeexdsp which is part of the speex package. Debian has this thing of splitting packages and although libspeex is in there, the other component, libspeexdsp has been missing from Dpups past and present. Perhaps this can be included in the build recipe in woof-CE so that the headers are in the devx too ?? Some programs need it eg Linphone.

My Vivaldi stable 1.12.955.38 is based on Chromium 61 and runs nicely.

OscarTalks,

For the next release I will include the patched inkscapelite and add the missing libspeexdsp. I'm sure the Woof-CE devs monitor this thread, so maybe the build recipe will be updated.

Also, I downloaded your Vivaldi stable 1.12.955.38 sfs, and it runs very nicely in Dpup. Thank you!

[OscarTalks]

Hello Radky,

Is there something not quite right with libdbus-1 ?
This is the same in the remaster I have been tinkering with so looks like it is at the woof-CE level. I came across it when experimenting with compiling sylpheed and claws-mail (even though I don't really use e-mail clients myself).
There is a libdbus-1.so.3 in /lib and another in /usr/lib
The latter is a link to an older version. Is this from the BK dbus package and the one in /lib is more recent and from the Debian package?
Can the older version be removed from /usr/lib or will this cause problems (eg with the dbus daemon) ?

The errors I was getting pointed initially to libdbus-glib so I tried compiling that from source. This failed until I installed the Debian libdbus and libdbus_DEV over the top.

By the way, there is a plugin in sylpheed (attachment tool) which has to be installed afterwards and is missing from most Puppies, not sure if it is useful for anything.

[Billtoo]

I updated my uefi flash drive install of xenialpup64 that is used on my imac:

root# inxi -bw
System: Host: puppypc6728 Kernel: 4.9.54 x86_64 (64 bit) Desktop: JWM 2.3.6 Distro: xenialpup64 7.0.8.4
Machine: Device: desktop System: Apple product: iMac8 1 v: 1.0 serial: W8811GXLZE2
Mobo: Apple model: Mac-F226BEC8 v: PVT serial: 1
UEFI: Apple v: IM81.88Z.00C1.B00.0802091538 date: 02/09/08
CPU: Dual core Intel Core2 Duo E8135 (-MCP-) speed/max: 1600/2400 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 XT]
Display Server: X.org 1.18.4 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 152x24 Advanced Data: N/A for root
Network: Card-1: Broadcom BCM4321 802.11a/b/g/n driver: b43-pci-bridge
Card-2: Marvell 88E8058 PCI-E Gigabit Ethernet Controller driver: sky2
Drives: HDD Total Size: 282.1GB (3.2% used)
Weather: Conditions: F ( C) Time: October 11, 7:46 PM EDT
Info: Processes: 175 Uptime: 10 min Memory: 219.6/3949.2MB Client: Shell (bash) inxi: 2.3.8
root#


I shanged kernels and updated palemoon to 27.5.1

This install is working well.

[radky]

Hello Radky,

Is there something not quite right with libdbus-1 ?
This is the same in the remaster I have been tinkering with so looks like it is at the woof-CE level. I came across it when experimenting with compiling sylpheed and claws-mail (even though I don't really use e-mail clients myself).
There is a libdbus-1.so.3 in /lib and another in /usr/lib
The latter is a link to an older version. Is this from the BK dbus package and the one in /lib is more recent and from the Debian package?
Can the older version be removed from /usr/lib or will this cause problems (eg with the dbus daemon) ?

The errors I was getting pointed initially to libdbus-glib so I tried compiling that from source. This failed until I installed the Debian libdbus and libdbus_DEV over the top.

By the way, there is a plugin in sylpheed (attachment tool) which has to be installed afterwards and is missing from most Puppies, not sure if it is useful for anything.

Hi OscarTalks,

Debian_stretch dbus packages in Woof-CE download:

1 - woof-out_x86_86_debian_stretch/packages-deb-stretch/libdbus-1-3_1.10.18-1_i386.deb contains the following libdbus files:

Code: Select all

-rw-r--r--      370116  2017-04-05  15:07  lib/i386-linux-gnu/libdbus-1.so.3.14.11                    
lrwxrwxrwx           0  2017-04-05  15:07  lib/i386-linux-gnu/libdbus-1.so.3 -> libdbus-1.so.3.14.11 

2 - woof-out_x86_86_debian_stretch/packages-deb-stretch/libdbus-1-3_1.10.22-0+deb9u1.deb contains the following libdbus files:

Code: Select all

-rw-r--r--      370116  2017-07-30  06:23  lib/i386-linux-gnu/libdbus-1.so.3.14.13                    
lrwxrwxrwx           0  2017-07-30  06:23  lib/i386-linux-gnu/libdbus-1.so.3 -> libdbus-1.so.3.14.13 

Of the two above packages, the latter is the one installed in my build.

---

Woof-CE dbus pet:

3 - woof-out_x86_86_debian_stretch/packages-pet/dbus-1.2.4.2permissive-q1.pet contains the following libdbus files:

Code: Select all

-rwxr-xr-x      274650  2010-01-23  03:45  dbus-1.2.4.2permissive-q1/usr/lib/libdbus-1.so.3.4.0                    
lrwxrwxrwx           0  2011-06-05  22:46  dbus-1.2.4.2permissive-q1/usr/lib/libdbus-1.so.3 -> libdbus-1.so.3.4.0

This ancient pet package is almost eight year old but the package contains at least three bin files (dbus-monitor, dbus-send and dbus-uuidgen) which list libdbus-1.so.3 as a dependency.

The question remains, if the old libdbus-1.so.3 -> libdbus-1.so.3.4.0 files are removed, will the old bin fies work OK with the newer libdbus-1.so.3 -> libdbus-1.so.3.14.13 files. We should know after testing a bit, or is it time for an updated permissive package?

Thanks

[radky]

Hi OscarTalks,

Re: duplication of libdbus-1.so.3 in Dpup Stretch

I removed the two old libdbus files from Dpup Stretch (/usr/lib/libdbus-1.so.3.4.0 and the symlink /usr/lib/libdbus-1.so.3).

After rebooting, dbus is working OK for me.

1 - /var/lib/dbus shows machine-id
2 - /var/run/dbus shows the two requisite entries -> pid and system_bus_socket
3 - The three requisite dbus processes are running

Code: Select all

# ps -aux | grep dbus | grep -v grep
message+  6196  0.0  0.0   2732   112 ? Ss   09:24   0:00 /usr/bin/dbus-daemon --system
root     10993  0.0  0.0   4336   232 ? S     09:26   0:00 dbus-launch --autolaunch 4ea4c3482c74436056aeaafb59dec458 --binary-syntax --close-stderr
root     10994  0.0  0.0   2732  1688 ? Ss   09:26   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

Thanks

[Billtoo]

I remastered a Dpup Stretch build that I did the other day and after adding many applications
it's grown to about 800mb.

video-info-glx 1.5.3 Thu 12 Oct 2017 on Dpup Stretch 7.0.0a2 Linux 4.1.44-pae i686
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)

X Server: Xorg Driver: nvidia
X.Org version: 1.19.2
dimensions: 1920x1080 pixels (707x392 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 387.12

Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Core 0: @1600 1: @1600 2: @1600 3: @1700 MHz

It's working pretty well on my HP desktop.

[Sailor Enceladus]

[Sailor Enceladus]

I compiled another woof-ce Slacko 5.7.1 last night here to mainly address the wifi exploit mentioned in this thread (changelog).

[belham2]

I compiled another woof-ce Slacko 5.7.1 last night here to mainly address the wifi exploit mentioned in this thread (changelog).

Awwwwweee darn it, I thought you were gonna give me a "delta" I could apply to the last ISO I already have (and use)

[watchdog]

I compiled another woof-ce Slacko 5.7.1 last night here to mainly address the wifi exploit mentioned in this thread (changelog).

Thanks Sailor Enceladus! Working well here. I have upgraded the savefile from slacko 5.7. I did a pet package of the included firefox 28.0 in slacko 5.7.1. Firefox 28.0 works well in puppy4 with glibc upgrade to 2.7 version (from original 2.6...).

[belham2]

I compiled another woof-ce Slacko 5.7.1 last night here to mainly address the wifi exploit mentioned in this thread (changelog).

Thanks Sailor Enceladus! Working well here. I have upgraded the savefile from slacko 5.7. I did a pet package of the included firefox 28.0 in slacko 5.7.1. Firefox 28.0 works well in puppy4 with glibc upgrade to 2.7 version (from original 2.6...).

Hi Watchdog,

Yeah, Sailor's 5.7 is nice---it's my go to when any other pup starts messing up and I can't fix it. Can I ask, do you have a download link for your Firefox 28.0 with the glibc 2.7 upgrade? (forgive me if I overlooked it in the 'Browsers & Internet' section ).

Thanks!

[watchdog]

Install in puppy4 libc_upto2.7_415_p4.pet from:

http://www.geocities.jp/cygnus_odile/puppylinux/

Then my firefox28.pet:

https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

[belham2]

Install in puppy4 libc_upto2.7_415_p4.pet from:

http://www.geocities.jp/cygnus_odile/puppylinux/

Then my firefox28.pet:

https://drive.google.com/file/d/0B9iMb4 ... sp=sharing

Thanks, Watchdog!!

[sc0ttman]

Hi there,

I'd like to know how to:

Add the Slackware 14.2 patches repo to the list of available repos in PetGet ina Slacko build..
(this repo: ftp://ftp.slackware.com/pub/slackware/s ... /packages/)

Basically, I want to be able to easily perform security updates in puppy..
So I want the slackware 14.2 patches repo to be included and update-able..

But the patches repo isn't even listed in PetGet.. nor in the setup files like DISTRO_PET_REPOS etc...
In Woof, all I can find is pre-built Packages-puppy-slacko* repo files ..

Secondly (not so important) I want my new slacko build to also include the slacko-14 repo (not just slacko-14.1)...

How do I add new slackware repos?

EDIT 4:

Removed stuff it was suggestions to do the above, but is a bit buggy...

I've since worked out the patches/security stuff gets merged into the main *-official repos during a repo build (or repo update in petget)...

But the new pkgs which get added are not downloadable or installable for me using Petget (see next post)...

Does anyone have the same problem?

[sc0ttman]

Further to the above,

Possible bug in petget/0setup:

I'm using a pretty bog standard Slacko 6.9.x build..

I'm trying to get Slacko to install wpa_supplicant 2.6, which has fixes against a big security problem in wifi (as far as I understand it)...

This wpa_supplicant 2.6 is in the Slackware patches repo.

The 0setup script, used in Woof and Petget, merges the latest pkgs from the "Slackware patches" into
the main *-official repo files, when updating/building Puppys repo files... (as I understand it)..

That's pretty cool, hat's off

However, while Petget successfully lists wpa_supplicant 2.6 in the repo after an update, it wrongly shows (ALREADY INSTALLED)..
Cos I actually only have 2.5 installed..

Even worse, trying to install any new pkgs added from the patches repo (and merged into "Packages-slackware14.2-official" in Petget) fails..
It says "missing libraries".. Even if I download them in the browser and ldd them (none missing)..

Anyone else have (or can anyone reproduce) the same problem?

(I'm well aware I don't understand Woof very well, so don't wanna just start logging spurious Github issues, so am asking here if I have this all correct...)


[As a side note, after updating the repos, my own pkg manager was able to download and install the wpa_supplicant 2.6, and the new bash
listed in patches without a problem (had to use the --force option to override existing pkgs]

-----------

A feature request

On a very related note, if there are new pkgs in the repos, I would love Puppy to print to the console (or terminal emulator) on first run of each boot
the names of all the new pkgs in the repos, just like Ubuntu does...

Especially if it's security fixes.. To that end it might NOT be better to merge the patches/fixes/security pkgs into the main repo files...

Ideally puppy would check for new pkgs at boot, and if new pkgs found, booting to X would be delayed i until after i had seen the msg and
chosen to install/ignore/etc.. and then X loads up.. (so, more like apt-get/ubuntu)

(this could actually be achieved with my pkg manager fairly easily, if puppy didn't merge the new pkgs into the main repo files and instead
kept the patches/fixes repos in their own files, like all the other repos..)

And wouldn't it be less code and hackery in woof to simply treat the patches (etc) repos like normal repos - with their own repo files...?

Again, I don't know enough about Woof to do this a 'proper' way (using Petget, root-fs skeleton, etc) ...

...Any thoughts?

[xpio]

Hi sc0ttman

If it's of any help to you, I am using stock slacko6.9.9.9 as found @ ibiblio, and have updated wpa_supplicant this morning.

I didn't use any of the command line tools, just Puppy Package Manager, and it too listed wpa_supplicant as "already installed", but I think it's normal behavior for PPM, and that it labels app by name, not by version, as such. (It displayed a warning that installed apps are not normally shown in the list, but updates are, with "already installed" label.)

While installing this, it downloaded heaps of other stuff, as qt-4.8.7 is a dependency of wpa_supplicant 2.6. In the end, installer reported that there are missing libraries, but these are from dependencies further down the chain. When checking, it seems that:

File /usr/lib/gstreamer-1.0/libgstcdparanoia.so has these missing library files:
libcdda_interface.so.0 libcdda_paranoia.so.0
File /usr/lib/gstreamer-1.0/libgstlibvisual.so has these missing library files:
libvisual-0.4.so.0

[Sailor Enceladus]

Anyone else have (or can anyone reproduce) the same problem?

A similar thing happened to me. When I ran ./0setup it kept pulling this mysterious list that still had 2.5 in it, even though each list I could find on slackware site said 2.6. Somehow deleting the woof-CE folder, re-running the git command and doing ./merge2out and ./0setup again fixed it. I'm not sure what the issue was, glad it somehow randomly fixed itself eventually

[sc0ttman]

Anyone else have (or can anyone reproduce) the same problem?

A similar thing happened to me. When I ran ./0setup it kept pulling this mysterious list that still had 2.5 in it, even though each list I could find on slackware site said 2.6. Somehow deleting the woof-CE folder, re-running the git command and doing ./merge2out and ./0setup again fixed it. I'm not sure what the issue was, glad it somehow randomly fixed itself eventually

Glad you fixed it, but did you try updating the repos in the Petget of a running Slacko pup that doesn't have those PETs yet, and then installing the newly added PETs? Cos that is what is not working for me..

In other words, I built a Slacko a few weeks back, which didn't include the new wpa_supplicant 2.6 pet, then updated the repos, the new wpa_supplicant (2.6) was then listed in Petget, but after trying to install it, I still only had wpa_supplicant 2.5 installed (when i did wpa_supplicant --version)...

In the end, installer reported that there are missing libraries,

But did you run `wpa_supplicant --version` to check you actually got 2.6? Cos I didn't get 2.6, I still had 2.5 installed..

And, are we sure those deps listed are correct? Does wpa_supplicant really need all those things?? I suspect not.. Most of them are builtins so not too much harm, but still ..

+bzip2,+dbus,+expat,+fontconfig,+freetype,+gcc,+gcc-g++,+glib2,+harfbuzz,+libICE,+libSM,+libX11,+libXau,+libXdmcp,+libXext,+libXrender,+libffi,+libnl3,+libpng,+libxcb,+ncurses,+openssl-solibs,+openssl,+qt,+readline,+util-linux,+zlib

Not gonna derail the whole thread with this problem...

So I will leave a "possible bug report", that "merging new PETs into the main repo files seems not to work for me, and 0setup seems to be the culprit.."

Again, this would need confirming by other users of recent Slacko builds, who update the repos and try to install the newly added pets..

[01micko]

Anyone else have (or can anyone reproduce) the same problem?

A similar thing happened to me. When I ran ./0setup it kept pulling this mysterious list that still had 2.5 in it, even though each list I could find on slackware site said 2.6. Somehow deleting the woof-CE folder, re-running the git command and doing ./merge2out and ./0setup again fixed it. I'm not sure what the issue was, glad it somehow randomly fixed itself eventually

Glad you fixed it, but did you try updating the repos in the Petget of a running Slacko pup that doesn't have those PETs yet, and then installing the newly added PETs? Cos that is what is not working for me..

In other words, I built a Slacko a few weeks back, which didn't include the new wpa_supplicant 2.6 pet, then updated the repos, the new wpa_supplicant (2.6) was then listed in Petget, but after trying to install it, I still only had wpa_supplicant 2.5 installed (when i did wpa_supplicant --version)...

In the end, installer reported that there are missing libraries,

But did you run `wpa_supplicant --version` to check you actually got 2.6? Cos I didn't get 2.6, I still had 2.5 installed..

And, are we sure those deps listed are correct? Does wpa_supplicant really need all those things?? I suspect not.. Most of them are builtins so not too much harm, but still ..

+bzip2,+dbus,+expat,+fontconfig,+freetype,+gcc,+gcc-g++,+glib2,+harfbuzz,+libICE,+libSM,+libX11,+libXau,+libXdmcp,+libXext,+libXrender,+libffi,+libnl3,+libpng,+libxcb,+ncurses,+openssl-solibs,+openssl,+qt,+readline,+util-linux,+zlib

Not gonna derail the whole thread with this problem...

So I will leave a "possible bug report", that "merging new PETs into the main repo files seems not to work for me, and 0setup seems to be the culprit.."

Again, this would need confirming by other users of recent Slacko builds, who update the repos and try to install the newly added pets..

Alrighty,,, a lot of superfluous stuff in the quote but remember PPM checks deps of deps...

Code: Select all

# ldd ./wpa_gui 
	linux-vdso.so.1 (0x00007ffed1ffc000)
	libQtGui.so.4 => /usr/lib64/qt/lib/libQtGui.so.4 (0x00007f1c2df30000)
	libQtCore.so.4 => /usr/lib64/qt/lib/libQtCore.so.4 (0x00007f1c2da35000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1c2d818000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f1c2d49e000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f1c2d194000)
	libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f1c2cf7d000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f1c2cbb4000)
	libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f1c2c9b1000)
	libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f1c2c67a000)
	libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007f1c2c448000)
	libz.so.1 => /lib64/libz.so.1 (0x00007f1c2c232000)
	libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f1c2bf96000)
	libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f1c2bd45000)
	libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f1c2bb3d000)
	libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f1c2b922000)
	libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f1c2b718000)
	libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f1c2b4db000)
	libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f1c2b2c9000)
	libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f1c2af8e000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f1c2ad89000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f1c2ab81000)
	/lib64/ld-linux-x86-64.so.2 (0x000055d782362000)
	libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007f1c2a902000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f1c2a6f2000)
	libffi.so.6 => /usr/lib64/../lib64/libffi.so.6 (0x00007f1c2a4ea000)
	libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f1c2a2e5000)
	libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f1c2a0bb000)
	libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f1c29e9c000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f1c29c98000)
	libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f1c29a93000)

I hear you... wpa_gui?

PPM must include the templates from woof if we are to keep a lean system.

There are plenty of bug reports relating to updating xorg and various other system critical applications.

A drawback of woof? YES. From the start.

Fixable? Probably.

Something to consider in your CLI package manager.

NB> Apologies that I haven't had time to update some slacko/woof stuff but I do hold a full time job and am the full time carer for my Grand son. I think that is a fair excuse and distracts me enough to not put out a half baked Puppy version. I wish I had the skills of Houdini but I don't!

Feel free to PM me or drop me an email and I'll do what I can. (preference = email the '01micko' address which should be findable, spam trackers are awake up to the 'myadress At somedomain DOT com' stuff ).

Cheers!

PS> Scott, nice work on the build scripts. Sort out your github and I'll see what I can do to make you a member of the team.