site  contact  subhomenews

wget, aaaargh!

May 21, 2017 — BarryK
I was fixing a couple of bugs in the package manager, PPM.

I compiled 'vim' in OE, and added it to the online package repository in Then I used the PPM to download and install it, to test all that is working ...which it isn't.

For a start, the "Update database" button was broken. Fixed that.

Then chose 'vim', but it failed to download.

I discovered the reason. The latest release of wget, 1.19.1, no longer logs to stderr, instead to ~/wget-log*

A quick google, this chap has hit the same problem:

I have at least two scripts, probably more, that are now broken. For example "wget .... 2>&1 | .... " or "wget .... 2> logfile" no longer work.

In the latter case, you have to use the "-o" to direct output to a particular logfile. I don't know what to do in the first case, where want to pipe it.

wget has been around since the beginning of time, why make such a fundamental change now? I sent a very polite email to the wget-bugs mail list, asking why.

In the OE build, I have rolled back to wget 1.17.1. This is the same version used in Ubuntu 16.04. In OE, it was easy-peasy to rollabck, I just grabbed the recipe from the "krogoth" release.

In OE:
# bitbake -c clean wget
...then put in the new recipe, in my 'meta-quirky' layer, then...
# bitbake wget

Then, over in woofQ:
# ./0pre-oe-add

...which detects the changed versions in OE, and deletes the old one, imports the 1.17.1 binary tarball.

Oh yeah, vim. It started out early this morning, I compiled vim in OE and imported it to woofQ. Then got distracted by this wget stuff. Now it is 11am.
I want vim as it can convert syntax-highlighted code to HTML output, great for putting code into web pages.

if you want vim for the new Quirky Pyro64, it is here (6MB):

If you download and click on it in Pyro64, Xarchive will open. The mime handler does not (yet) recognise *.tar.xz as possible being a package to install.
Instead, open a terminal where you downloaded it, and run:
# petget `pwd`/vim-8.0.0427-r0-core2-64.tar.xz

Tags: oe

Quirky Pyro64 0.2 alpha

May 19, 2017 — BarryK
It's out! This is the first upload of Pyro64, tagged as alpha-quality, but is looking pretty good.

We are familiar with Puppy and derivatives having the "kitchen sink" in their builds, in a very small size. Well, Pyro includes the "kitchen fridge" as well.

Pyro64 is built with packages compiled from source in OpenEmbedded. It will run on PCs with x86_64 (64-bit) CPUs, of at least "core2" vintage.

Release notes, and how-to-install links:

Download, primary host:

Download, fast mirror site:

Note, I will be uploading the OpenEmbedded development system, with my modifications, plus a tarball of woofQ, later today, watch this blog.

Post feedback here:

Tags: oe, quirky

OE Pyro with meta-quirky

May 19, 2017 — BarryK
Here is all that is needed to compile most of the packages used in Quirky Linux. It is a tarball with a snapshot of OpenEmbedded "pyro" branch, and my customization "meta-quirky" layer.

Create a folder in a partition with a Linux filesystem, at least 150GB free space, and expand the tarball inside the folder, it will expand as folder "oe-qky-src".

Inside oe-qky-src, you will find a readme file that explains what to do next.

Just a few commands to execute, and off you go! Need a fast Internet connection, as over 515 source packages have to be downloaded.

Download oe-qky-src from here:

Fast mirror:

I also uploaded a tarball of woofQ. Once you have all the binary packages, they can be imported into woofQ (see script 0pre-oe), and Quirky Pyro built.

Feedback can be posted here:


SeaMonkey now stable in Pyro64

May 18, 2017 — BarryK
I reported that Firefox and SeaMonkey were unstable in Pyro64:

I have tested a build with icu 56.1 and SeaMonkey 2.48b1 using the system icu, and it is stable.

SeaMonkey is now also using the system sqlite3, as I added the required config settings in the OE build.

SM is also using system nss and nspr libraries, so it ends up a fairly small package.

Trying to get the size down wherever possible, I have created python-tiny, which has just enough in it to satisfy kodi.

I think, getting very close to a first release of Pyro64.
Contemplating doing builds for i686 and armv7 also.

Tags: oe

Chasing bugs in Pyro64

May 16, 2017 — BarryK
As I posted to the Puppy Forum this morning, Kodi now has text, and is working. Forum thread:

The problem that I am now working on, is both Firefox and SeaMonkey are very unstable. From past experience, there are various system libraries that are the cause of this, such as icu, cairo, pango, glib/gio.

I experimented with different configure options, eventually configured with almost everything internal, except, I think system libvpx. Beautiful, completely stable.

Then I introduced system hunspell and icu ...crashes again.

Most likely it is icu, so now I am doing a compile with all the other system libs reintroduced, except using internal icu. Hopefully that will be stable.

If it turns out to definitely be icu, I might do a complete rebuild in OE, using the same version of icu as used in seamonkey (56.1) with the same patches (OE has 58.x).


OE/Yocto Pyro released

May 14, 2017 — BarryK
There was a post on one of the Yocto mail lists, that Pyro, version 2.3, is released:

I have cloned it, and merged my customization layer, and started the build. This is a big build, with "the works", including Firefox, Gimp, Pidgin, Libreoffice, Kodi.

However, I have not solved the problem of no text in Kodi, so I will build Quirky with Xine. Also, Quirky will have SeaMonkey, rather than Firefox.

The plan is that once I am satisfied everything is reasonably sane, I will upload a tarball "oe-qky-src", which is OE with my customizations, so it is ready-to-go for anyone who is interested.

Also, intend to release a Quirky build. It will still have some issues, so might have to be classed as pre-alpha or alpha.


Forum thread to discuss OE and Pyro

May 12, 2017 — BarryK
I have started a thread on the Puppy forum to discuss OpenEmbedded and compiling for Puppy/Quirky:

I mentioned in the first post of that thread, that OE could replace Woof*. A clarification: yes theoretically, but it will require in-depth knowledge of OE and be a lot of work.
It is quite likely something that will never happen.

The compiling environment of Quirky Pyro64 0.1.1, my second build, is sane, and right now I am compiling SeaMonkey 2.48b1. That is, a native compile in a running Pyro64, not using OE.

Tags: oe

First build of Pyro64

May 11, 2017 — BarryK
Quirky built from packages compiled in OpenEmbedded, is codenamed "Pyro64". I have just done the very first build, version 0.1, and get a desktop -- and some bugs, which is to be expected.

The file is 297MB, and it has big apps, including LibreOffice, Kodi, Gimp, Pidgin and Firefox.

Most of the bugs look fixable, but Kodi displays without any text, and after a brief google, no solution has jumped out at me.
It is a common problem, but there does not seem to be any definitive fix.

Fixing Kodi is number one on the to-do list.

What I might do is install the devx pet, and have a go at compiling the latest version.

Tags: oe