Looking time to time to my QA page, I could not miss huge popularity boost for enca. After looking at reverse deps, I quickly found out that Mplayer from debian-multimediais reason for this:
I just wanted to fix some RC bugs till I'll go home, so I looked at the list of open onesand randomly chosen two bugs about roxen fonts which looked like low hanging fruits. Both were in fact same issue, just copied to two packages.
I worked on the fix, creating some intermediate version and then I finally wanted to upload the package. Unfortunately in this step I somehow managed to use the intermediate version, which did not really fix the issue. As packages were already uploaded, there was not much I could do except yet another NMU, now with full set of changes.
Just as accepted emails arrived I also noticed that I messed up bug numbers in changelog - I used same bug number in both changelogs. Okay, manually closing the bug worked around this.
But now I'm afraid what else did I mess up. Probably it's time to go for a dinner and stop working on computer for now :-).
When finishing series of articles about Debian packagingand writing about dbconfig-common, I just had to ask myself, why it is not used in phpMyAdmin package. I did not find any reason and as Thijs did not have any objections, I hacked it together this evening.
So what you will get? All fancy features where phpMyAdmin requires it's database to manage some additional features. For example you can create PDF pages with structure of your database, add additional comments to databases, notice relations between MyISAM tables, etc. Simply see wikifor more details.
Besides this, phpMyAdmin is now automatically configured to use database you choose using dbconfig-common, so you can also connect to remote MySQL server without manually configuring anything.
The only thing which scares me a bit is that we now increased a lot number of debconf questions user has to reply by this...
Okay, I will again miss DebConf. This time it is not because of time, but because of money. The flight to Buenos Aires is far too expensive to go there just for DebConf and I didn't manage to plan some more travelling around South America...
Hopefully it will get better next year, at least DebConf will be much closer :-).
PS: Just after deadline for confirmation and my decision for not going there, I got an email that my sponsorship for travel was approved. Unfortunately too late to change my decision.
Okay I did thing I considered already for several months - I decided to quit my current job at SYSGO, make one month holidays in summer and find some new job meanwhile. So I'm looking forward to free August, which I will probably spend travelling somewhere :-).
This brought up again question whether to go or not to go to this year DebConf. The only problem with this is distance - flight to Buenos Aires will be something around 2000 USD and it means lot of money for me. I applied for sponsorship for half of the price (well I'm not sure if I can really pay the other half, but I would feel really bad for asking that much money) and let's see how it turns out. On the other side, I'd love to visit Argentina, but that would probably require much more time and money. Let's see how it all turns out, there is still time to decision...
PS: If you have some interesting job offer, just contact me at michal@cihar.com.
Yes Erik,
SourceForge did not do anything. But what is even more "funny" is that changing keys over web interface does not change
~/.ssh/authorized_keys. So even if you are aware of this problem and change keys in interface which should do it, it does not work. I just realized this today when I read your post and wanted to check whether this file is really world readable...
After recent not so funny thing with OpenSSL in Debian, I realized that I will have to regenerate most of keys and certificates, because last big changes I did in networking/vpn/ssh setup which involved generating keys are not older than broken OpenSSL appeared in archives.
First obvious thing was SSH keys and cleanup of
~/.ssh/authorized_keyson all hosts. While doing that, I realized that I still have there several keys, which are more or less gone (not that I'd lost them, but I simply stopped to use them). So it was good opportunity to do cleanup here. While I was at these changes, cleaning up
~/.ssh/known_hostswas also good idea, because I still had there lot of hosts I collected during some of my previous jobs and I definitely won't (and can not) access these machines anymore. So good, big cleanup in SSH configuration was forced :-).
Next and harder step was to found out where else I use certificates generated by vulnerable OpenSSL. Server certificates for sure were also generated by OpenSSL, so let's regenerate web and email certificates and hope I did not miss anything.
All this happened yesterday, but today I realized that I missed other even more important thing - OpenVPN certificates. While regenerating certificates, I also found some machine keys which are not really used anymore, so I again could drop some of them. So that was task for this evening and now I'm hopefully really done with this issue and I really hope that this won't happen again in near future, I don't need to cleanup that often ;-).
Adrian, it looks like you are looking for apt-zeroconf. It looks like great idea, but it does not seem to be really active recently and unfortunately it did not yen find it's way to official archives...
Looking time to time to my QA page, I could not miss huge popularity boost for enca. After looking at reverse deps, I quickly found out that Mplayer from debian-multimediais reason for this:
Long time ago I used FnFXto handle events from ACPI keys on my Toshiba notebook. However when reinstalling notebookbecause of disk crash, I thought there must be a cleaner way to handle these and I found patch for acpid which added handling of these special events.
However I really didn't like patching acpid on every update and there didn't seem to be chance to merge it upstream, so I started to look for better solution. After another amount of googling, I found that HAL already has some support for Toshiba hotkeys. Unfortunately it is now disabled in Debianbecause most key did not emit anything using HAL.
Okay, let's fix the HAL, maybe it will get later enabled. Converting FnFX keymap to C code was quite easy and I made a patch for HALto add support for all keys. Hopefully it get merged soon and I can then file bug on Debian package to reenable Toshiba support in HAL.
Meanwhile I'd like to find some generic way of configuring what happens on these events. For now I hacked simple Python scriptwhich listens to DBUS events and invokes appropriate commands for keys, but I hope that some such tool already exists and I just missed it. If you know something, please let me know at michal@cihar.com.
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 :-).