musher0 wrote:But now, what does this mean?

http://bfy.tw/26nH

slavvo67 wrote:I'm running Barry's QU 6.2.1 Any suggestions?

Yes, run something that was built using woof-CE (like tahrpup or Slacko) and not Barry's woofQ thing.

No, it's not! Something is wrong with your system's /etc/ssl.

Read the first post. Librepup doesn't have the closed-source, non-free firmware required for your card.

bigpup wrote:Is there something that explains how to use Woof-CE?

Yes, the first post. I gave you the exact command lines to run, what else do you need?

That doesn't make much sense, as the Mesa version should be exactly the same - if you get no flicker with tahrpup, Librepup should behave the same

I fixed that problem. I use the Samba package from tahpup and wish to stick with the solution chosen by 666philb, to avoid double effort.

The testing build looks good! Fonts are crisp and everything seems to be in place. However, fonts-droid is a waste of space because websites don't use it and open-ath9k-htc-firmware cannot be loaded because it's a "huge style" kernel, so I'll have to figure out a different solution for thi...

Hello everyone, woof-CE needs you! Great things are happening in the "testing" branch of woof-CE : - Support for building tahrpup64 - Support for packages of more distros and more distro versions - Speed improvements, new looks and new features in PPM - Support for new kernels - UI improve...

Here's the list of all changes in the upcoming 6.0.2.1: - QupZilla instead of IceCat, with the latest ca-certificates from Trisquel - Updated AbiWord, same version as in tahrpup - open-ath9k-htc-firmware, free software (yes, that's right!) firmware for several ath9k_htc dongles popular among users o...

Yes. The MD5 of the debdb2pupdb that works is e28fe0493d8c5b3ab7f13c2d6a5c2c2f.

Should be fixed.

With the latest binaries (make sure you git pull):

@01micko - attach the relevant parts of Packages-* files, I want to see which fields are corrupt. Besides those small issues here and there (which I'm not worried about), PPM seems to work great. I was able to install several window managers, abrowser with plugins, etc', @mavrothal - maybe you shoul...

It's ready! I committed new find_cat and debdb2pupdb binaries to woof-CE. The database update in PPM should take about 10-15 seconds now, compared to 10-15 minutes . :P Put them in /usr/local/petget and tell me what you think. There's a big chance that some packages previously not shown in PPM will ...

Almost ready! Takes less than a second for the entire process, while the old one takes almost a second per package (and I have 40,000+ of them).

Yes, fixmenus is horrible too. Need to get rid of it ASAP.

There you go: a fixed debdb2pupdb binary . This parser runs in two modes: either via woof-CE or via PPM. I tested only the first use case, but there was a crash that happens 100% of the time when it runs via PPM. Fixed :) Still working on the find_cat replacement and it's crucial to have this thing ...

The database is downloaded to /tmp as well and I ran debdb2pupdb manually to ensure zero download times.

It has nothing to do with file systems. I compared the old and new debdb2pupdb side-by-side and with tmpfs, so no disk was involved

Glad I asked that question. :) It's the consistency in your blog posts ('x86', 'x32', 'ia32' ...) and the documentation you mentioned that caught my attention. x32 is indeed interesting, because of the performance gains under some workloads (like multimedia). However, it's an ABI for x86_64 only, so...

I don't really understand, Barry. Is it x32 or x86? If it's built for x32, how come the same userspace works on x86 too? x32 is x86_64 only AFAIK. Kernel configuration: CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y CONFIG_X86_X32=y Yes, the entire x86 build just works, as-is, with the 64-bit kernel. T...