Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Poor review with heartwarming community response

Whoa, been quite a long time since I’ve blogged last time now and the longer it’s been, I’ve felt that I’ve needed to come up with something of more interest to blog about once I finally do some blogging again… ;)

Well, I read this poor review of Mandriva Linux 2010 (the only poor review I’ve seen so far actually), which I got a bit provoked about, not that much because I’m taking things personal, but it’s rather more about stupid people pisses me off! ;p

The reviewer seemed to only actually try review the One edition and then trailed off making up his own irrelevant and ignorant FUD conclusions about the Powerpack version which he didn’t tested, about how we seemed to be more interested
in pushing proprietary software (despite he later made some ignorat complains about the trouble from lack of this in the Free edition later on), then on and on.
With such amazingly borderline retarded and biased ranted I just had to write a longer comment on the article myself (which is something I seldom do), and in the process I was very happy to see that others shared my annoyance and awareness of ignorance as well- Pretty much all comments flamed the article, most of them based on very nice insight and knowledge about the distribution and it’s strengths, especially in comparision with others, this also from many people who weren’t even using Mandriva!

I found it really nice to see that we seem to finally gain a more favorable impression and also really our users finally growing aware of our strenghts and all.

I really hope to see this being a growing trend with a community hopefully finally starting to really be growing again for real! :)

Oh btw. Happy new year to all of you, even those of you who doesn’t deserve it or that I just don’t like. ;p


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Desperately looking for a job

A couple of weeks ago I broke up with my girlfriend over four years..

Considering that I’m unemployed student, she’ll be moving out soon and that I don’t get any scolarship for the summer, this leaves me in a pretty desperate situation.

So these days I’m looking for a job, but the job marked isn’t all that great right now, I’ve spent today applying for several jobs, but not much promising nor interesting so far..

I figure that I might as well announce my search here as well in hope of someone picking it up and offering me some cool (or at least not too crappy;) job after reading it. :D

So short about me, I’m at the end of my master degree in computer science with only my master thesis left to complete (thus no other courses occupying my time, leaving me available for near full time employment) and I’ve been heavily involved in the development of Mandriva Linux (in about every aspect at various stages) since 2001 and several other free software projects since.

My favourite programming languages are C, C++ and Python, I’m also experienced with Assembly, Java, PHP and Perl. (Some of the projects I’m currently involved in might give some idea about my background and fields of interest.)

While I’m preferably looking for a local job, I’m open for remote jobs as well, so feel free to get in touch wherever you might be if you have a possible job available for me. :D

I’m also maintaing a LinkedIn profile for anyone who’d like to see, feel free to connect, for anyone who’d like I’d be happy to provide you with a more complete CV, grades and any other info you’d like as well.

So if you’re a hot chick eager to pay my rent or a potential new employer, be cool and send me a mail!


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Interviewed by MAGNUM

The french Mandriva Linux community magazine MAGNUM has just published their 06 issue where they’ve started a series of interviews with open source developers, and at the end of last year I had the honour of being their first to interview for this. :)

The interview were conducted by mail, and since I was running late, had a friend visiting and stressed getting it done by time promised, I didn’t get time to read before I replied with my answers (that didn’t prevent me from writing in great lengths though;), so I hope it doesn’t come off as something to be easily misinterpreted, taken out of context etc., I suspect some of my points might not seem as balanced as intended..

Oh well.

You can also the original in english here.


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

PylibLZMA 0.5.2 & some Gdium / mips cooker work

I’ve had it lying around without no changes taking place for almost a month now, so I figured that I’d just go on and release pyliblzma 0.5.2 as I never updated the cooker package to 0.5.1 (which fixes some nasty bugs) because I was planning on releasing 0.5.2 right away anyways..

I never got that far due to various reasons which made me not getting very far with anything in general, so now I’ll just release it out there! :)

This version is mainly synchronizing code with bz2module.c from python upstream adding various bug fixes, new python 2.6/3.0 specific features etc. and I also rewrote much of the code to be more in sync for easier maintenance for myself and any others.

Related to this release I added a nice patch to python in cooker to automatically disable python’s memory allocator (pyalloc) when running under valgrind to make it easier to debug, this made my work a lot easier when debugging with valgrind and should do the same for anyone else on mandriva debugging python stuff with valgrind as well. :)

Since I returned from FOSDEM I’ve also done quite some work on getting to know the the Gdium & the mips platform, merging stuff from the Mandriva Glinux mips tree to cooker and on the toolchain in cooker. Cross crompilers should now build properly on most platforms so that one can build a mips compiler on ie. x86_64, so this should be in place for the system gcc 4.3 compiler, I’ve also since imported a gcc4.4 package to start work on gcc 4.4 and to clean it up a bit and eventually get a complete cross compiler toolchain for mips with all the nice mips related improvements introduced in the upcoming gcc 4.4 release. :)

I’m not really sure on what the plans are for the mips cooker tree yet, but I’m planning on getting the complete toolchain built to build everything on my quad core x86_64 rather than on the 900 mhz loongson Gdium netbook of mine, then I should be able to easily build the full distribution in relative short time and also make it easier for others as well on non-mipsel architectures.

Working on this now I get to reuse a lot of the work and experience from the past with my (hobby;) efforts on the sparc port, so it’s a nice thing to see it not going to waste even if not being more than a sporadically maintained port on a hobby basis. :D


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

post-FOSDEM

It’s been over a week since I got back from FOSDEM, so about time I should blog a bit about it. :)

So coming back from FOSDEM last year I was a bit disappointed about Mandriva presence, this year
we had our own booth at least and I must say that it was quite succesful! :)

I hung out at the booth a lot of the time and our booth was next to the Ubuntu booth (those bastards!;), and guess what?
We seemed to actually attract a “lot” more attention than our neighbour booth most of the time, I’m not sure at what the
Ubuntu people presented in their booth (I actually forgot to really check it out:/), but since they didn’t seem to catch
my attention I guess they didn’t seem to have that much interesting and flashy stuff to offer (hmm, that’s kinda pretty
much in sync with my general view of Ubuntu, coincidence;p)..
I guess that all the different netbooks with the different Mandriva versions was sufficient to catch a lot of attention
from various people to our booth, especially the mips based Gdiums from Emtec running Mandriva G-Linux (which is our mipsel port with special customizations for the Gdium). I got mine powered up at FOSDEM and put it on display and basically everyone else but myself seemed to get to play with it more than I did, which is a good thing since it’s not available for sale quite yet so that way people get to discover it and I got to play with it when I got back home anyways. :D

In addition to the Gdium, Emtec also displayed their new and upcoming G-cube which is a HTPC solution which is also mips based, unfortunately it wasn’t demonstrated so no first impressions there yet, but I’d sure like to get my hands on one later!

For the talks at FOSDEM this year I was a bit disappointed, most of those I attented (ie. the cmake and rpm talks) wasn’t really targeted at developers, but more of the introductionary type for (new) users.. And for most of the talks that I would’ve found interesting I managed to miss, ie. Rob Savoye’s talk about gnash (which I had the pleasure of dining with at Sunday evening, really cool guy!:). :/
I did attend Peter Pöml’s talk about MirrorBrain though which I had interest in since I did the initial implementation of the geolocalized metalinks stuff for urpmi a while back and I exchanged ideas with him on the metalink mailing lists regarding these things, you’ll even find me talking about these things in Mandriva in the video stream of the talk. (Watching it now I think that I with my dry mouth picked up Peter’s german accent in there;p)

Other good things regarding Mandriva was that Anne managed to calm my scepticism towards the Community Steering Committee and the Mandriva Linux Assembly stuff, it seems like we’re mostly on the same page about stuff, aware of the same things with ideas and all that should be quite compatible. :)
I kinda regret that I left FOSDEM early on Saturday to go with Jeff to dine with the CentOS people in Leuvre though as I didn’t really get the chance to discuss such things in dept and interact with all the cool Mandriva d00dz as I hoped for. :/

In summary, FOSDEM was as always great and I’m most definitively planning on attending it next year as well! :D


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

My new Gdium

I just returned to my hotel room from the FOSDEM Beer Event with my new Gdium which Patrick brought me, it looks very sweet and all, but when after spending a couple of minutes trying to plug it in the eletrical outlet I realised it was for US outlets. :(

D’oh! I hope I’ll get the chance to test it tomorrow at least, if not I’m gonna cry. :p

G’nite :)


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Leaving for FOSDEM

I’ll be arriving in Brussels as early as 9:55 in the morning, if anyone wants to help me kill time before the Beer Fest, feel free to give me a call at +47 41681061.
:D


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

pyliblzma 0.5.0 released & FOSDEM Mandriva stand

I’ve finally gotten around to spend some time on updating pyliblzma with xz support
and some other improvements and a lot of fixes and cleanups.

I ended up spending way more time on this than I was expecting since it was quite
a while since I last time messed around with the code or even the python C api at all.
While I’ve implemented the most critical parts for xz support, there’s still a lot of
interesting stuff in the liblzma api that I should get around to implement support
for later (ie. support for selecting several different filters)..

Now that I’ve gotten the release done and it’s status is no longer broken with
latest xz release, I’ll hopefully spend my time on some school stuff and also
game coding again, although I expect that I’ll have to do a 0.5.1 bugfix release
sometime soon. :p

I was also asked by Anne to help out at the Mandriva stand at FOSDEM the
other day, so for anyone who want to say hi, you’ll probably find me there
sometime where I’ll be answering all your questions and what not related
to Mandriva Linux. :)


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

FOSDEM attendance & some Doon Lunacy

Despite not really having any money to afford it, I finally got around to buying a plane ticket for Brussels a couple days ago, so I’ll be attending FOSDEM this year as well. My new years resolution for this year is to get out more, so I figured that I could charge the whole thing to my credit card with good conscience (I just love to make up excuses that I can even make myself find valid;). :D

There also showed someone up on irc with the interest contributing to my totally free and improved clone of the Dune 2 engine (which in contrast to all the other clones out there is totally free of copyright violations as well!) Doon Lunacy yesterday, so I got around to doing some work on it again after not having touched it since the summer. First thing I started with now was to migrate our libeastwood library (which does the reading of the native game data) and doonlunacy from scons to cmake to make it easier to deal with for myself and others, this turned out to take more time than I expected, but it also was a very nice occation to actually get to really learn cmake, now I’m growing more fond of it than I used to be. :)

Most parts of the game should be in place (ie. here’s a screenshot of the menu gui, notice that’s it’s drawn in memory from the original game data, no modified graphics shipped at all! :D), although the most fun and important part is left though – gameplay!

Maybe 2009 will be the year where I’ll finally get a playable release of the new branch done, when it does it’ll be sure to hit cooker before any places else!

I’ll look forward to met all you sexy cooker people again at FOSDEM and also those other sexy, non-cooker people out there as well!

Cya at FOSDEM soon!


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 35

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/functions.php on line 43

xz (formerly known as lzma utils) has gone beta!

As Lasse Collin, the author of xz & liblzma promised, xz went beta before the end of the year and he release the first beta a few hours before midnight.

This means that the API is now final and that the format is stable and ready for use!

This is great news as this new format, library and tool adds a lot of neat functionality and is sure to become an extremely important format over the years and should most definitively replace bzip2 in most cases by any sane person!

I’ve started on updating support for it in various tools, beggining with rpm5 which now supports both the legacy lzma_alone format as well as xz for payload now. I should get around to update the kde lzma filter patch as well for this now and this time it should also be ready for submitting upstream. :)

PylibLZMA will then also of course be a priority, but since this python module implements the whole liblzma api it may take some longer, but I did promise Lasse to get around to it soon to review the API, so I guess I shouldn’t delay it for too long..

I’ve also now switched completely to using the new xz tool in cooker now which has backwards compatibility for old lzma format, keeping the old behaviour when using the old command names, so the old 4.32.7 C++ version is gone now, this will also eliminate the dependency on c++ in our basesystem which is also very nice!

Congrats to Lasse, I know he’s put tons of work, efforts and stress in this and it’s great to see him finally get the beta released making it fully ready for adoption!

PS: The new release can be found here.


Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/http.php on line 1653

Warning: strtotime() [function.strtotime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /var/www/wordpress/wp-includes/http.php on line 1653