So I got the followings today at the uni on a Windows box:

    ping alaplab.
    Pinging alaplab.mit.bme.hu [152.66.252.18] with 32 bytes of data:
    Reply from 152.66.252.18: bytes=32 time<1ms TTL=127
    Reply from 152.66.252.18: bytes=32 time<1ms TTL=127
    Reply from 152.66.252.18: bytes=32 time<1ms TTL=127
    Reply from 152.66.252.18: bytes=32 time<1ms TTL=127
    Ping statistics for 152.66.252.18:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

Now I wonder if they just ignore the dot at the end of the hostname or WTF.

We had this old #3331 bug, and it turns out that Fedora had an s390 patch that fixed it. Of course the patch name is misleading since it fixed something on x86 as well, so it was the last thing I thought to try... :-)

I got a reply reply to my libbtctl patch I sent back in last year:

On Sat, 2008-12-27 at 18:32 +0100, Miklos Vajna wrote: > Hi, > > I recently tried to build libbtctl with mono-2.0 and the build fails > because the .pub signatures are no longer supported. > > A similar commit in evolution-sharp's svn: > > http://svn.gnome.org/viewvc/evolution-sharp?view=revision&revision=191 > > Here is a patch to do the same for libbtctl: > > http://ftp.frugalware.org/pub/frugalware/frugalware-current/source/gnome-extra/libbtctl/mono2.patch > > Of course you can generate your own new key with 'sn -k 1024 > libbtctl.snk' if you don't want to take the one I use right now.

Because the patch wasn't in bugzilla, I missed it for the last ever release of libbtctl.

Use bugzilla in the future.

Cheers

Needless to say, there is no libbtctl component in the GNOME bugzilla.

Yay for bureaucracy!

So we got a bugreport - it seems the solution is just about getting rid of the bundled libcrypto, as it's incopatible with the not-bundled libssl.

Ported erlang and postfix to ppc, the later because I wanted to use git-send-email, and I like to config postfix once, then point all the apps at postfix and then I have to change my pass only at once place when I do so.

I got an i586 machine yesterday with the "please install Linux on it for me" slogan. Sadly we at Frugalware do not support i586. First I wanted to install Slackware, but it turned out that the machine does not read DVDs and I did not wanted to download all the CDs of Slack and it turns out that Slack has no netinstall I ended up installing Fedora. Well, I tried to. The HDD is only 1.2G, and they wanted X on it, so disabled almost everything, except X and blackbox. ;)

But honestly it just does not worth the time, people should just bin such a machine and get a life. :P

So there is such a project, and my relevant ~/.mailcap entry is:

$ grep docx ~/.mailcap
application/vnd.openxmlformats-officedocument.wordprocessingml.document; docx2txt.pl %s -|iconv -c -f utf8 -t latin2; copiousoutput;
application/vnd.openxmlformats-officedocument.wordprocessingml.documen; docx2txt.pl %s - |iconv -c -f utf8 -t latin2; copiousoutput;

I don't exactly know why the later is needed. I haven't checked the RFC. The fact is that sqmail sends the content-type header using format=flowed (no indication about using this format, it just uses it), and mutt doesn't like it. So it's an sqmail or mutt bug. But the workaround is the second entry above.

BTW I started to learn Erlang yesterday, there is a good "Programming Erlang" book, it's more than 500 pages, I managed to read the first ~50 pages.

OTOH Fruglware 1.0rc1 is out. Laying in the bed and releasing from my iBook is fun. :)

Referring to this post, if "diff.denyNonIndexExclude = false" then is IndexInclude true or false?

This is like the recent Mozilla action, I never really figured out if they now like or hate Apple. (OK, other users already told me that the later is the true version.)

It seems I'm too bad in Boolean algebra. ;-)

This was on my TODO for a long time, so I upgraded from 2.4.2 to 2.4.6. Should be non-visible, since this is a minor upgrade.

Oh and I posted a few cosmetic git patches to this thread.

Usually there are 1-2 nasty bugs in each release - after all that's the only eason I push for having at least a pre-release every 2 months.

So today's one was a nasty double free bug in xconfig, so after the install there were no xorg.conf. The fix is now in git, so it should be over, but I was a bit disappointed, as so far Priyank's file descriptor / memory leak fixes were all carefully tested, however this one was obviously bogus, so probably it was not tested at all. OK, hopefully such stuff won't really happen again.

Snip. In VIM, I wanted to do a "Pj" 1000 times. 1000Pj will do "1000P and [one] j", so that's not the right way. qaPjq1000@a will do it: qafooq records foo to the "a" macro, then 1000@a calls it 1000 times. Good to know. ;-)

An old dream is now a reality, bitlbee-skype got a testsuite! :)

If I were at it, I also added a new skyped option to be able to log traffic when the deamon forks into background.

Finally python 3.0 (or python3k) arrived to -current. Of course the external modules are still for 2.6, but that's not something we want to change before 1.0

OTOH, they screwed up something at the uni, the dhcp servers were not functional on the wireless network, so I had time to read my current book, and did not read email till 22h. :-)

While I was away, I totally forgot about a patch they recently applied.

I also reworked my git ls-files parseopt patch today, based on Dscho's comments.