(old)Puppy Linux Discussion Forum

Posted: **Fri 17 Feb 2017, 15:59**

One thing I noticed is that the updates_mgr (Menu -> Setup -> Updates Manager) in Slacko seems to rely on Packages-slackware-14.2-patches, which doesn't exist anymore in my last build. I guess one has to download and filter the entire Packages-slackware-14.2-official to add the changes to the updates_mgr list now, or grab the packages in the ChangeLog.txt list manually from the slackware site? Dragging the Packages-slackware-14.2-patches from the official 6.9.6.4 seemed to make the updates_mgr 0.21 work again, though the "The list was last updated on" still doesn't show a date beside it for me after.

Posted: **Sat 18 Feb 2017, 00:03**

I did a 32bit build and chose the no.pae 3.14.55 kernel.

System: Host: puppypc16760 Kernel: 3.14.55 i686 (32 bit) Desktop: Openbox 3.6.1 Distro: Slacko Puppy 6.9.6.4
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.18.3 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
tty size: 137x43 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: 1000.2GB (1.5% used)
Weather: Conditions: 27 F (-3 C) - Mostly Cloudy Time: February 17, 6:40 PM EST
Info: Processes: 136 Uptime: 2:01 Memory: 192.6/3289.4MB Client: Shell (bash) inxi: 2.3.8

It would boot on this hp desktop but only to the prompt, most of the
radeon firmware was missing and trying to run xorgwizard did nothing.
There a 2 firmware pets available in PPM and I saved them to a flash
drive after booting on a supported computer and downloading them with
PPM.
I managed to get the pets to install after booting with the nox option
and using petget, then downloaded the firmware with PPM and rebooted to
create the savefile.
Anyway, got it working

There are more applications available in the 32bit build, google-earth
for one.
This build has the newest Firefox,openssl, and other updates too I
think.
I guess updating PPM once in a while will allow getting any future
updates.
It would be great if 01micko had the time to update and post new 32 and
64 bit isos for a new beta.
I'm pretty sure they would be a hit with users, this one runs great

Posted: **Sat 18 Feb 2017, 21:37**

Re: Updates. I generally only use ppm for stuff compiled specifically for puppy that I want to add like the extra pets in the puppy-slacko-14.2 directory, and even then I sometimes just go to ibiblio or the forum to grab things because I find it faster. I don't think looking for security updates like openssl in ppm makes as much sense as having all the slackware updates in a list like before. I guess an alert or sub-menu in ppm that tells you what you can update could work though. As far as I can tell, you currently have to search for the specific program for it to tell that a new version of it is out, even after updating the database.

edit: Making puppies in woof-ce is probably the best way to keep everything up to date though, unless changes bork things

Posted: **Sun 19 Feb 2017, 01:29**

Which Woof-CE? There's Master, Testing, Rationalize... rk someing and legacy. I know the 1st post says use testing but what R the others for?

Posted: **Sun 19 Feb 2017, 01:38**

At least the Rationalize branch has something to do with to optimize code. So they made changes/rewrites to/of the init script in initrd. These changes made all my developments completely useless. That said everything that I'd started to develop in November 2015 is completely useless in Puppies beyond Tahr Puppy.

Posted: **Sun 19 Feb 2017, 02:55**

LazY Puppy wrote:At least the Rationalize branch has something to do with to optimize code. So they made changes/rewrites to/of the init script in initrd. These changes made all my developments completely useless. That said everything that I'd started to develop in November 2015 is completely useless in Puppies beyond Tahr Puppy.

I wonder what stage Tahrpup 6.0.6 was built with. The /etc/DISTRO_SPECS file seems to missing the BUILD_FROM_WOOF= line.

Posted: **Sun 19 Feb 2017, 03:57**

As far as I know: Testing.

I had downloaded Woof-CE Testing for trying to build a Xenial Puppy. Though, its only option to build a Puppy was for Tahr Puppy. I found it complicated to create a Xenial Puppy as there was nothing setup for it to do. So Woof-CE isn't that easy to create a Puppy Version the first time.

I think Xenial was built from Rationalize branch. Though, I won't bet on it, so someone may correct me. At least that version won't accept my developments on T.O.P.L.E.S.S. anymore. And its init script -of course- has some rationalized code like functions to load the Puppy .sfs modules (main, adrv, fdrv, ydrv, zdrv (is there more?)).

Posted: **Sun 19 Feb 2017, 05:27**

Hello all.

Just tried the Testing branch twice.

I spent two half-days trying the Devuan-Ascii and the Debian-Stretch. Both
suffer from the same problem: missing downloads and then missed
compilations. Obviously, if a download failed, you can't assemble the
program, but there are additional programs that were downloaded that the
02 script refuses to assemble.

In the case of the Devuan-Ascii the list of missing downloads was longer
than that of the programs that couldn't be assembled.

In some cases in the Debian-Stretch build, the variant number of the
program was slightly different, had evoived in the repo. Also, I can't get the
script to recognize: baconrecorder, gtkhash and libilp.

The following is thoroughly confusing: the script says a program is missing
in the packages-pet directory but asks you to put the download in the
packages-de*n directory. You download the program, you put it in the
"requested place", but when you try to assemble it, you get the same
error! These information messages need refinements I think, in the form of
more accuracy.

it's better to laugh than cry!!!

If you want details, I can provide my particulars upopn request, but it's
along the lines of the bugs reported by ttuxxx a couple of pages above.

The Devuan-Ascii Pup boots but not X. An error message says it is missing
the /etc/X11/xkb/symbols directory. xorgwizard seems to be working in a
void. From the missings list, it would appear that the X in the Devuan-Ascii
Pup experiment doesn't have all the necessary files.

I might try to build the Debian-Stretch Pup anyway though, because its X
series of components appear complete. I'll see. Some of the other missing
files are applications, such as osmo and gnome-mplayer, so they are not
essential to the construction of the distro. I can re-introduce these apps
afterwards.

BFN.

Posted: **Sun 19 Feb 2017, 06:25**

musher0 wrote:Hello all.

Just tried the Testing branch twice.

I spent two half-days trying the Devuan-Ascii and the Debian-Stretch. Both
suffer from the same problem: missing downloads and then missed
compilations. Obviously, if a download failed, you can't assemble the
program, but there are additional programs that were downloaded that the
02 script refuses to assemble.

In the case of the Devuan-Ascii the list of missing downloads was longer
than that of the programs that couldn't be assembled.

In some cases in the Debian-Stretch build, the variant number of the
program was slightly different, had evoived in the repo. Also, I can't get the
script to recognize: baconrecorder, gtkhash and libilp.

The following is thoroughly confusing: the script says a program is missing
in the packages-pet directory but asks you to put the download in the
packages-de*n directory. You download the program, you put it in the
"requested place", but when you try to assemble it, you get the same
error! These information messages need refinements I think, in the form of
more accuracy.

it's better to laugh than cry!!!

If you want details, I can provide my particulars upopn request, but it's
along the lines of the bugs reported by ttuxxx a couple of pages above.

The Devuan-Ascii Pup boots but not X. An error message says it is missing
the /etc/X11/xkb/symbols directory. xorgwizard seems to be working in a
void. From the missings list, it would appear that the X in the Devuan-Ascii
Pup experiment doesn't have all the necessary files.

I might try to build the Debian-Stretch Pup anyway though, because its X
series of components appear complete. I'll see. Some of the other missing
files are applications, such as osmo and gnome-mplayer, so they are not
essential to the construction of the distro. I can re-introduce these apps
afterwards.

BFN.

LoL I'm doing 100% the same thing you are also trying stretch

, and having the same issue, It tells me I don't have the files while clearly I do have the files, then it also says I need other files and so I find the files and put them in the respective directories and they don't find them, But if you make the missing deb packages into pets and then you manually add the pet.specs it finds them, Well tried it one one so far and it found it. Seriously am I missing something, do I have to run some script for woofce to find all the files in Dpup/local-repositories ??
ttuuxxx

Posted: **Sun 19 Feb 2017, 06:32**

And here's the missing stretch ones plus others like the browser etc.

Posted: **Sun 19 Feb 2017, 07:50**

Thanks for the sad, sniff-shiff, confirmation, ttuxxx!

I rounded up the so-called missing packages in an adrv.

Now I have a nice Dpup-Stretch-7 alpha 1,

370 Mg's counting the
devx. It boots, except it stops at the door, so to speak: no X.

Xorgwizard must me chasing its tail or something. Or maybe the vet cut
the tail?! I tried modesetting and vesa -- nada, rien, nothing. For the rest
of the options, the layout of the xorgwizard has changed a lot, and I had
no taste for adventure left.

I'm also getting messages about "usb 1-10 - something missing" when
loading xorgwizard. But the keyboard and mouse and external HD are all
running ok. In the twilight zone we are, man!

I'm calling it a night! It's a quarter to three (a.m.) here.

However, I'd welcome a "debugger bugger",

preferably an X specialist,
to show up and put his head on the log along with ttuxxx (if he wants to!)
and me, to help this Dpup-Stretch-7 go all the way to desktop.

TIA. See y'all in the morning!

Posted: **Sun 19 Feb 2017, 09:37**

Against my better judgment let me say how I understand things about woof-CE and puppy building.
If no puppy build with a specific “recipe

Posted: **Sun 19 Feb 2017, 11:42**

Wow, I've been watching and reading this thread daily, seeing how Musher, Ttuuxxx, Billtoo, lazyPuppy, et al are getting along doing builds.
Was thinking maybe I'd also give a devuan build a try, and hope for success...but then reading musher & ttuuuxx's problems, I've waited.

Then, alas, just now reading mavrothal's post above, I realize how this ain't gonna happen for me. There's no way (other than luck) I'll be able to discern what needs fixing (problems) in terms of the build scripts. Mavrothal hit the nail on the head for me, as I've been thinking this whole time that maybe doing a build is nothing more than improving/modifying an old build. Sure, I believe I could do a slacko build like Billtoo and sit back & watch it all do its thing, but I was hoping I'd be able to take a Devuan and modify it like I want to.

Thanks, Mavrothal, for providing a 'reality' check. The first post of this thread needs to be modified to reflect this, imho, before it gives goofballs like me the idea that I can atually pull-off my own build without understanding all the complicated crap that goes on in the build scripts. Don't even know how I could think that now...

Posted: **Sun 19 Feb 2017, 13:13**

mavrothal wrote: * As mentioned the recipe for debian-based puppies is 3+ years old. Required packages, package names and dependencies have been changed since. I would rather look at the tahr/xenial package list as base for recent debian builds.

I did a couple of builds early this morning, Xenial 64 and tahr 64.

Xenial64 boots and runs but PPM doesn't work, won't update and fails at
installing anything.
Tahr64 won't boot to the desktop, xorgwizard runs but still can't find
a way to get a video driver to work.

The Xenial says 7.0.7 and the tahr says 6.0.5

Seems I lucked out when I chose Slacko-14.2 which worked fine on both 32
and 64 bit producing an iso with the latest firefox,openssl, and more,
it works great.

EDIT: Here's info from Xenial on my dual core Compaq

System: Host: puppypc30316 Kernel: 4.1.11 x86_64 (64 bit) Desktop: Openbox 3.6.1 Distro: xenialpup64 7.0.7
Machine: Device: desktop System: Compaq-Presario product: AU194AA-A2L CQ5123F serial: MXX9300M0F
Mobo: MSI model: Boston v: 1.0 BIOS: Phoenix v: 5.24 date: 06/19/2009
CPU: Dual core Pentium E5200 (-MCP-) speed/max: 1600/2500 MHz
Graphics: Card: Intel 82G33/G31 Express Integrated Graphics Controller
Display Server: X.org 1.18.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
tty size: 116x49 Advanced Data: N/A for root
Network: Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169
Card-2: Linksys WUSB54GC v1 802.11g Adapter [Ralink RT73] driver: rt73usb
Drives: HDD Total Size: 508.1GB (6.3% used)
Weather: Conditions: 41 F (5 C) - Scattered Clouds Time: February 19, 8:34 AM EST
Info: Processes: 121 Uptime: 2 min Memory: 139.8/3936.6MB Client: Shell (bash) inxi: 2.3.8

Posted: **Sun 19 Feb 2017, 13:38**

Well, I'm using dpup stretch, it does boot to desktop and can compile apps. It's just missing a new kernel compiled with the dpup's gcc 6.3.0. mesa/dri/opengl seems to work fine. Keyboard/mouse/touchpad ok.

About missing apps.. of course they're missing. When you create a new puppy apps are missing, unless you use repos from earlier versions. And I won't add the missing apps, I don't care.

The pet repos at ibiblio are forbidden to (basically) everyone if you want to update stuff or create a new directory with pet pkgs for a new version.

Regarding tahrpup/xenialpup... well phil hasn't updated the config files at the git repo in a long time as far as I know. I don't build upups to try to figure out what's missing or what's wrong.

Will comment about devuan later, and will drop a little bomb.

Posted: **Sun 19 Feb 2017, 14:04**

Billtoo wrote:
mavrothal wrote: * As mentioned the recipe for debian-based puppies is 3+ years old. Required packages, package names and dependencies have been changed since. I would rather look at the tahr/xenial package list as base for recent debian builds.
I did a couple of builds early this morning, Xenial 64 and tahr 64.

Xenial64 boots and runs but PPM doesn't work, won't update and fails at
installing anything.
Tahr64 won't boot to the desktop, xorgwizard runs but still can't find
a way to get a video driver to work.

i'll update the tahrpup build in woofce today (done), but to get X to work type

Code: Select all

rm /usr/share/X11/xorg.conf.d/10-amdgpu.conf

then xwin should fire it up

as for xenial sounds like urxvt isn't working or there's a missing rxvt to urxvt link in /usr/bin

Posted: **Sun 19 Feb 2017, 15:14**

Hello all.

Following mavrothal's suggestion, I downloaded the woof-CE-master to
look at what it can build.

It can build:

debian wheezy
devuan jessie
slackware 13.37, 14.1 and 14.2
trisquel belenos
plus
ubuntu precise, trusty (tahrpup) and xenial

for a total of nine possible Puppy flavors. (Which makes Puppy the most
interesting proposition in the Linux world!)

I built the first two a while ago, when they were in the "Testing" branch.
Hence the interest for me of trying to build a Dpup Stretch to keep up with
the times.

I can also relate to mavrothal's call for woof-CE personnel.

As for me, I don't feel qualified to assume responsibility of a sub-branch
because I'm worth zilch on networks, monitors (read "X"), and hardware
generally, and the idea of learning how to "github" sets me in panic mode.

That said, I sincerely hope that someone qualified hears mavrothal's call
and rejoins jlst on the general* woof-CE maintenance team. Puppy's
survival may depend on it, IMO.

BFN.

~~~~~~~~~~
Note -- * By "general", I mean no offense to either 666philb or 01micko.
As I understand it, they provide much appreciated maintenance for their
specific woof-CE branch.

As well, it's obvious to all that each doesn't work in a "silo", and that
some of their work is sifting out to the other woof-CE branches as well.

Posted: **Sun 19 Feb 2017, 16:25**

Thanks, everyone. I think I'll revisit woof-CE. Problem I might have is hard drive space. Have about 5 separate Quirky downloads that really put a dent in my portable drive space....

Belham2, just a few things before you get going.... you need a significant amount of hard drive space and a lot of patience. The process is long and if it doesn't work out of the box, you may get a bit frustrated. That being said, Puppy always wants more developers, testers and users, of course! Go for it!

Slavvo67

Posted: **Sun 19 Feb 2017, 16:53**

jlst wrote:Well, I'm using dpup stretch, it does boot to desktop and can compile apps. It's just missing a new kernel compiled with the dpup's gcc 6.3.0. mesa/dri/opengl seems to work fine. Keyboard/mouse/touchpad ok.

About missing apps.. of course they're missing. When you create a new puppy apps are missing, unless you use repos from earlier versions. And I won't add the missing apps, I don't care.

The pet repos at ibiblio are forbidden to (basically) everyone if you want to update stuff or create a new directory with pet pkgs for a new version.

Regarding tahrpup/xenialpup... well phil hasn't updated the config files at the git repo in a long time as far as I know. I don't build upups to try to figure out what's missing or what's wrong.

Will comment about devuan later, and will drop a little bomb.

Well out of the box it should build a basic version that takes you to a traditional desktop, Because its using a donor distro its not just building one out of the sky, Using pets from the repo is just fine for things like themes. Anyways Like I said older versions of woof would bring you to a desktop where you could troubleshoot easily, this time around its not doing that, I'm working it out but really its wasting a few days and loads of hours a day that could of been used more productively like compiling some browsers etc. Plus it still doesn't explain why its not picking up some of the DEB packages in local-repositories/x86/packages-deb-stretch, Hell I just want a basic buggy desktop that I can troubleshoot and build on.

ttuuxxx

Posted: **Sun 19 Feb 2017, 17:32**

And here you go Debian Stretch Major Alpha

but working.
ttuuxxx

(old)Puppy Linux Discussion Forum

woof-CE needs you

woof-CE needs you