Today is last day when I'll be more or less online, so if you wanted something to me this year, it's probably already too late :-). I will somehow follow emails, but do not expect much.
Tomorrow I'll spend by traveling back to Czechia (NGO - FRA - PRG), then I will just enjoy time being home and not being pushed to deliver tons of papers to somebody.
This is also most likely last blog post this year, so I can not skip the merry Christmas and happy new year phrases ;-).
I wanted to make 1.16.0 last release this year, but unfortunately one bug preventing reading of all SMS messages from some AT phones sneaked in, so I decided to make another quick release. Changelog is really short:
Other change is that I started to produce additional binary build for Windows - it does not use any external libraries (so no MySQL, PostgreSQL or Gettext support) and links statically. So you can just copy single binary and it should work anywhere.
You can download from usual place: http://cihar.com/gammu/
After half day of playing with Wine, MinGW and friends, I managed to be able to automatically build Windows versions of both python-gammu and Wammu. However I do not have environment to actually test these versions (except for Wine), so I would really welcome if some Windows users could do some testing. I expect some strange crashes at beginning, but hopefully we will be able fix it to produce working Wammu version for Windows in future.
You can get the installer here: http://tmp.cihar.com/wammu-0.26-setup.exe
It's NOT final or stable version, but as the only changes which happened since last release were either minor or related to cross compilation, it should be equal to combination of Gammu 1.16.0, python-gammu 0.24 and Wammu 0.25, so don't be confused by versions.
PS: Okay, when application works in Wine, it does not mean it will work in Windows, see bug report for details.
I just released version 0.25 of Wammu. This release brings new icon set thatnks to David Corrales and fixes various crashes. Full list of changes:
There is still no binary for Windows. I don't have time and environment for maintaining them. Volunteers are welcome!
Working on the project here at Japan is sometimes really fun. Tomorrow we have important delivery and this afternoon out Japanese colleagues decided that 2000 pages describing our software solution is not enough. They need at least 500 extra pages. Fortunately it could be any existing documentation, so we randomly choose POSIX standard Part 1 (535 pages) and the Eclipse basic tutorial (592 pages). Japanese guys were really happy that they have 1100 more pages and we're happy that we don't have to produce more documents. Now I only wonder why the hell customer is interested in quantity of paper and not in quality of work.
I just noticed, that Python Jabber transports have been migrated this weekend to Google Code and first people started to contribute. I especially like the fact, that first contributors are Czech guys and they're fixing encoding problems :-).
Let's hope that this activity will also help to improve Debian package which is not really in good state, but I promised not to hijack it till the end of year ;-) (so for now I temporarily hack it in my repository).
PS: I know ICQ is evil, but I don't have enough power to force all my contacts to start using Jabber.
Continuing in Christmas release series, the next in a row is python-gammu. It only brings usual bunch of upgrades to be in sync with Gammu and improved MinGW support:
Download from usual place: http://cihar.com/gammu/python/
Last Gammu release in this year is out. There are no major changes compared to 1.15.91, but it brings lot of bug fixes to stable series.
Full list of changes since 1.15.0:
You can download from usual place: http://cihar.com/gammu/
I somehow expected that this will never happen, but todays update contained debian-keyring version 2007.12.04, which includes changes from last two years or so. So finally who-uploads and other tools work reasonably good for mine stuff.
Anyway I think with more than 6000 lines in last changelog entry, it is good candidate to be the longest changelog entry ever been in Debian :-).
After more than year and half of blogging with Nanoblogger, I'm still more and more thinking about trying something else. With almost 500 entries I currently have, generating blog takes more and more time. Otherwise there is not anything I'd miss, but something with comments might be also better.
I didn't yet find time to investigate currently available blog engines, but from what I remember in past, it was hard to choose something. What is thing which many engines fail to fulfill is ability to use text editor instead of writing text in browser. The other thing I'd like to see is to have more than category (or tag) per post. Maybe ikiwiki would be good candidate for this...
However what to do with old content? Should it be migrated to new system? I doubt it will be able to keep old URLs what is something I'd like...