site  contact  subhomenews

Wary Puppy 5.2 released

October 14, 2011 — BarryK
The last official release of Wary Puppy, our build or "edition" of Puppy Linux that targets older hardware, was on September 1, 2011, see announcement:

Since then, development has continued at an intense pace. As this extraction from the Wary 5.2 Announcement page states:

This is a massive upgrade relative to the 5.1.x series. All of the base packages were recompiled in T2. Certain choices were made in T2 with the plan of seamless upgrading from Xorg 7.3 to 7.6 -- that is, the default Wary system has Xorg 7.3, but it is planned that Wary can be upgraded to Xorg 7.6 by installation of a single PET package, and all applications will work before and after. This required some very careful configuration. The idea is to "have our cake and eat it too" -- Xorg 7.3 for old hardware, easy upgrade to 7.6 for newer video hardware. The plan actually seems to be working.
As usual, huge changes yet only a small version-number change. Many bug fixes, upgrades, new packages.

There are fascinating new features in this Puppy. Take the time to peruse the Announcement and Release Notes page:

Also, for an introduction to what Wary is all about, read this page:

The live-CD ISO file is 123.6MB, which might seen pretty small, yet it could have been much smaller -- the build has the "kitchen sink" in terms of kernel drivers, for example very large 3rd-party analog modem drivers. Download:

All the tools needed for C/C++/Vala/BaCon coding and compiling are in this SFS file (109.7MB):
(SFS files are introduced here:

Extra release notes

1. The Puppy Package Manager can install PET packages from the 'wary5' repository. However, we need to test all of the packages in that repo, that they still work. One issue is that 'ffmpeg' got updated in latest Wary, which might have broken a couple of the media player PETs (Gnome-mplayer, Smplayer). This testing will be done ASAP.

2. The pup has the kernel, configured with SMP (multiple CPU cores) support enabled. I did also compile a uniprocessor kernel, however in alpha/beta testing no-one reported a failure with the SMP-enabled kernel on a uniprocessor system that was fixed by using the uniprocessor-enabled kernel. Hence, I have not built a uniprocessor version of Wary 5.2.

3. I am still not 100% certain that an old save-file will upgrade correctly. If you have a save-file from an earlier version of Wary, booting up with 5.2 should upgrade it ok -- if X fails, try rebooting -- if X still fails, try with boot parameter "puppy pfix=purge".

4. Wary 5.2 has a new theme. I would especially like to thank forum member 'dejan555' for the lovely wallpaper. I posted about the theme here:


Wary 5.2 Forum feedback
Username: BarryK
Any feedback on Wary 5.2 can be posted to this thread in the Puppy Linux Forum:

Glade Interface Designer icon missing
Username: broomdodger
"wary 5.2.0 frugal devx_wary_5.2.sfs loaded Glade Interface Designer icon missing

Old savefile breaks Wary
Username: Terryphi
"As previously reported using savefile from Wary breaks Wary 5.2 even when using pfix=purge. Black screen but with bar at bottom from which I can run some added programs but not rox or Puppy programs. Is this anything to do with new gtkdialog ?

Username: Sage
"Downloading, will test later. 106 was excellent. - which version of is most likely to work? I have two at present.

What does future hold now
Username: tronkel
"Looks as though this latest version of Wary has just obsoleted every previous version - because of the the quantum-leap improvements under the hood. Should this Wary 5.2 version not now be considered to be the official Puppy for the end users as well as a working base for the Puppy derivative developers? Does the Woof tree allow say a Slackware or Ubuntu variant to be built using this Wary 5.2 as its base? Congratulations on this milestone version Barry - what an humongous achievement! I wonder what will happen to the Distrowatch rating now.

Wildcards in Woof
Username: Iguleder1
"Barry - I just found some bug in Woof. When you use a wildcard in the second field (e.g the package names), Woof only applies this selection to one package list. I'm trying to build a dpup with the Debian Backports mirror and I got a broken X because of this - Woof only picked the packages from the backports repository but kept the ones from the Squeeze repository out.

pupX set properties of X
Username: broomdodger
"Wary 5.2 frugal pupX set properties of X > Screensaver Usually I disable the screen saver, but just now enabled it for a short delay, and 'blank the screen'. It did not happen ! I tried it with no apps running. Is it broken?

PPM Package can't find libs
Username: GCMartin
"Found PPM pacakges that does NOT install and run adequately. I will PM you with those details. it seems WARY libraries may be problem.

eudora and xorg 7.6
Username: scsijon
"@sage and interested others. I shall create a wary52 packaged eudora in a couple of days (mon-tue), check although I suspect the w5 pet should work out of the hat. @barry and interested others. I built a (rough) 106 with xorg 7.6 as well as the same with xorg 7.4 using woof, just to do a comparison. I found that the 7.6 clearly seems to run faster, it also runs on my old hardware, even those that I had problems with with 7.4 earlier! I wonder why? regards scsijon

xorg 7.6 + pupX set properties of X
Username: broomdodger
"wary 5.2 frugal xorg 7.6 Screen saver blanking works! --AND-- glxgears is 2x faster than xorg 7.2 xorg 7.2 1120 frames in 5.2 seconds = 216.024 FPS xorg 7.6 2363 frames in 5.0 seconds = 472.455 FPS Both using the vesa driver by choosing i810

xorg 7.6 + flsynclient = crash
Username: broomdodger
"acer Aspire ONE wary 5.2 frugal xorg 7.6 flsynclient > click calibrate touchpad and crash xorg 7.2 no problem

Re: Wildcards in Woof
Username: BarryK
"Iguleder, Did you try to force which repo to use? Ex: [i]# yes|abiword|iceword,iceword-plugins|exe,dev,doc,nls|compat:salix[/i] ...'salix' is one of the Slackware repos, the database file Packages-slackware-13.37-salix. The override, in above example "salix", can be any one of the fields in the filename "Packages-slackware-13.37-salix". That override should also work if you have wildcards in 3rd field.

Re2: Wildcards in Woof
Username: BarryK
"This override mechanism was introduced here: Of course with Debian, the database files have different names. I don't know anything about the backports. The standard Debian db files will be: Packages-debian-squeeze-main Packages-debian-squeeze-non-free Packages-debian-squeeze-contrib So you could for example have: [i]yes|abiword|iceword,iceword-plugins|exe,dev,doc,nls|compat:contrib[/i] which case, it is unlikely that you would need the wildcards.

Slow Xorg 7.3
Username: BarryK
"Some Wary testers have reported sluggish Xorg 7.3 (before they tried the Xorg 7.6 upgrade). Try this, see if it improves speed:

Re: wildcards
Username: Iguleder1
"Barry - no, this isn't the problem. These are "compatible distro" packages anyway. The problem is that some of them originate in one repo and the others in another. When I use a wildcard, Woof picks only the packages from the first repo. I can't put that field, since it will force one repository and the other packages will be missing.

Link problem
Username: BarryK
"Probably it needs the http:// in front, otherwise treats it as a local link:

Re3: Wildcards in Woof
Username: BarryK
"Iguleder, Could you get by with splitting it up, for example: [i]yes|iceword|iceword-2*|exe,dev,doc,nls|compat:main yes|iceword-plugins|iceword-plugins*|exe,dev,doc,nls|compat:contrib[/i]

eudora link plus use
Username: scsijon
"sorry barry, will remember for next time. on the other hand I thought i'd try the existing wary5 version before repackaging and it works properly [u]providing you install it's two (dbus, dbus-glib) dependancies before installing it[/u]. please remember you need to reboot after installing dbus and give Eudora a little time to set itself up when started the first time, it has to setup a few files, links and the like for the user.

link & Eudora
Username: Sage
"Thanks for those clarifications, guys. Of course, I did type in the link! Can I ask a supplementary, please? Do we need those two dbus files if we d/l the Eudora file on scsijon's link? Or are those just for folks using the Wary5 version (presumably still in the repo?)?

Fix for old warysave file
Username: Terryphi
"Forum member upnorth has posted a fix for the problem where a savefile from an earlier version of Wary breaks Wary 5.2.

@sage + eudora
Username: scsijon
"you need to check if your version has these two packages in by default or add them from their own, wary doesn't which is why I put them there, hidden directory file /root/.packages/woof-installed-packages is your friend here. pm me (same name) on if further help required, were getting off-topic here sorry barry

"we're getting off-topic here"
Username: Sage
"... not necessarily? Your valuable insight may assist with other Wary-related issues. Either way, many thanks sj and BK - much appreciated. PS Folks who haven't tried Eudora yet might be missing a trick.

Username: cbs
"Installed frugal on my old Sony laptop. Works wonderfully well. However, i would like to request if it is possible to update Viewnior to v.1.0 or 1.1 I would like to use the crop function found only in later versions. Thank you for your hard work.

tray cpu graph - how to add click
Username: broomdodger
"wary 5.2 How / where to edit to add clicking the cpu graph in the tray so it will open a file such as top or hardinfo?

Wary 5.2 printing fix
Username: BarryK
"[b]Notice to Wary 5.2 users[/b] [b]Fix for printing[/b] Printing from some applications is broken. Explanation and fix here: This will be in the next Wary, but you can grab the fix now.

Wary Service Pack 5.2 - 5.2.1
Username: BarryK
"Wary 5.2.1 is a bug-fix release. Currently only available as a PET package for Wary 5.2:

Re heavy CPU
Username: BarryK
"pupok, You might have better luck with the upcoming Wary 5.2.2, which has a uniprocessor kernel. A couple of testers have reported that this has less CPU usage.

Tags: wary