yesterday LGee, desco, voroskoi and me met each other. you can reach a few pictures taken by LGee here

hi

the newest development snapshots's fpms are ready, you can reach at you-know-where. no big changes, 4 new languages, more patches submitted to upstream (we now only use only a gcc-4.1.0 specific one) and so on

(maybe this is true for mutt(-devel) too, i'm not sure)

so. first you need a private key, there is a good howto about it here. then you need to copy gpg.rc (for example from /usr/share/doc/mutt-ng-20060402/samples/gpg.rc) to ~/.muttng, then add the following lines to your muttngrc

source ~/.muttng/gpg.rc
unset crypt_autosign
unset crypt_autoencrypt
set crypt_replysign
set crypt_replyencrypt
set crypt_verify_sig=yes
set pgp_sign_as="0xXXXXXXXX"

where XXXXXXXX is your keyid

for autmatic key downloading on checking signatures, add

keyserver-options auto-key-retrieve

to your ~/.gnupg/gpg.conf

that's all :)

here. also the title is not exactly correct as probably a release candidate was tested :)

i've just set up bogofilter with mutt, it was sooo easy! :)

first you should collect some spam and ham (non-spam) to separate (Maildir) folders

then bogofilter -s -B ~/Maildir/spam/, bogofilter -n -B ~/Maildir/ham. the basic learning is done

to your procmailrc: :0fw | /usr/bin/bogofilter -uep :0: - ^X-Bogosity: Spam .Spam/

finally i've added a macro to my muttrc to be able to simply tell bogofilter it missed something (haven't noticed a spam): macro index S "bogofilter -Ns" (you can add a similar macro for "bogofilter -Sn" - "hey, this is not a spam" - if you want)

that's all :)

after a few days of work (and headache) we (me and janny) put togother a java-enabled version of the openoffice.org package. we built the development milestone (m163) of OOo, so it won't hit -current till 2.0.3 is released. ideally this should re-enable features like help and others which were missing since 2.0.0. at the moment the x86_64 packages are available, but janny will upload i686 ones soon, too

I've written a short howto about how to debug a pacman database error as I was asked many time to do so for others. So there it is, now i can say simply RTFM ;)

probably this is known, but i've just figured out how to get rid of grep when i use

foo |grep ... |sed ...

the magic command is

foo |sed -n '/^match/s/foo/bar/p'

if we're at it, you can even get rid of sed if you use bash and just want to do simple replaces like 1.0 -> 1_0:

$ pkgver=1.0
$ echo ${pkgver//./_}
1_0_0

two intereting tricks remained. the first is about deleting from a pattern to an another one (including both line)

$ echo -e 'a\nb\nc\nd\ne'
a
b
c
d
e
$ echo -e 'a\nb\nc\nd\ne' |sed /b/,/d/d
a
e

the last one is about deleting to the end of the file from a pattern:

$ echo -e 'a\nb\nc\nd\ne' |sed '/c/,$d'
a
b

ok, that's all for today :)

(other nice tricks here)

NewsForge published a review about Frugalware 0.4. Thx boobaa for pointing it out.

basically now the 64bit openoffice has all the features as the 32bit one, even the splashscreen is back, you can reach a screenshot by desco here