Michal Čihař - Blog Archives for Debian

No sponsors found?

Hmm it looks like I'm doing something wrong when trying to find sponsor for some package which I want to put into Debian. I already gave up with wmmp as I lost interest in using it meanwhile, but I'd love to see Czech-English dictionary in distribution as there are quite a lot of users here.

I hope that this time I will manage it earlier than in half year as it took for Gammu, because I'd like to have in in next stable…

Maybe it's time to start new maintainer process to avoid begging for each upload.

Comments on Blog

Russell Coker, if you have enabled comments for blog, make sure that they can be used. And no, I do not think creating blog on blogger.com is appropriate way to post a comment.

Hmm all I wated to say to your spam blocking is that you can do SMTP time bayes (using spamassasin) using sa-exim, but I'm pretty sure there exist more alternatives.

Backing up using duplicity

I used quite long time rdiff-backup for creating server backups. But I had to move away from it because it requires same program to run on the other end where backups are stored. And there was no chance that I can get it into 4Mib memory of my Asus router with OpenWrt which will now act as bacup server.

So I googled a bit and after reading several articles I decided to try duplicity. This decision was heavily inspired by article on Debian Administration website.

The setup with encryption and signing was very quickly and even restoring seems to work :-).

Packaging delay

Yes I know there is gammu 1.07.00 which should be packaged, yes I know there is python transition ongoing which needs changes on my python packages, yes I know that there is new libbluetooth2 in archives which need gammu rebuild. Please be patient I will return back to packaging work as soon as I will have internet connection at home.

By that time you can also expect new python-gammu release which will be just minor update to fix some urgent things.

Python policy craziness

I have no clue whether python-support or python-central is better solution as new python packaging helper. I follow debian-python list too shortly to know all backgrouds between their authors. Despite of those current situation is really bad.

There were filed many bugs and tools and policy still change every day. Will it use Python-Standards-Version or debian/pycompat? Will there be XS-Python-Version or debian/pyversions? Now it looks that both. I thought that new policy shoud simplify things and not making them even more complex. Calm down people and try to find one solution.