Bernd Z. posted a photo:
File in original size available on request - flickr doesn't allow files larger than 20MB unfortunately.
Bernd Z. posted a photo:
File in original size available on request - flickr doesn't allow files larger than 20MB unfortunately.
Once there was a project called Debian and a Ganneff.... (unfortunately in German only....)
22:20 < cb> Das ist doch voll die Arbeit Maintainer zu werden :-). Ich geb gewünschte Pakete immer nur weiter an einen der da sowieso schon den Kernel betreut :-) 22:21 < Ganneff> es is nur viel arbeit wenn du keinen schimmer hast 22:22 < cb> ja ich hab nur das seepferdchen *g* 22:22 < Obilan> Knusper: ja sicher ist es das 22:22 < Knusper> kopf -> tisch 22:22 < cb> Knusper, wenn du die verwaisten pakete findest siehst du auf der gleichen seite auch die links wie man maintainer wird 22:22 < Knusper> die hab ich gefunden 22:22 < cb> zumindest hab ich das das letzte mal dort gesehen 22:24 < Ganneff> wnpp? 22:24 < Knusper> aber man brauch dann schon leute, die einen "hoffieren" 22:26 < Ganneff> du brauchst erstmal die ahnung nen paket zu bauen. 22:26 < Ganneff> dazu siehe new maint guide 22:26 < Ganneff> dann brauchste nen sponsor. dazu gehe zur mentors liste 22:26 < Ganneff> dann machste mit dem eh weng rum (also normal so paketuploads via dem) 22:26 < Ganneff> und hast da halt schon dein maintenance krams. 22:27 < Ganneff> irgendwann is der sponsor angekotzt von dir und dem laufenden arbeit generieren 22:27 < Ganneff> der tritt dich dann dass du mal DM anfängst. 22:27 < Ganneff> das machste dann, und jemand anders tritt dir deine pakete als dmua zurecht, nachdem du in nem keyring irgendwo steckst. 22:27 < Ganneff> und dann kannste denn krampf selbst hochladen. aber nix andres. 22:27 < Ganneff> irgendwann willste was andres. und willst das auch noch ohne son doofen sponsor 22:28 < Ganneff> dann versuchste dich an DD 22:28 < Knusper> ahhhhhh 22:28 < Ganneff> dazu musste dir nen advocate suchen 22:28 < Ganneff> der is üblicherweise einer dem du vorher im prozess laufend auf den wecker fielst 22:28 < Ganneff> und er deswegen den nm leutz sagt "oh gott, befreit mich bloss von dem" 22:28 < Ganneff> die machen das dann, aber sie wollen dir mal etwas schmerzen zurückgeben 22:28 < Ganneff> desdewegen wirste viele fragen beantworten müssen 22:29 < Ganneff> und wie beim tüv das auto musste hier deine pakete nochmal vorstellen und checken lassen 22:29 < Ganneff> und dann nochmal fragen beantworten 22:29 < Knusper> thx... 22:29 < Ganneff> irgendwann gehst du dann mit den antworten den nm leuten so auf den geist dass die dem frontdesk sagen "meine kacke, den wolle mehr nit mehr sehen, schickts den dochma zu den DAMs, die hamms verdient" 22:30 < Ganneff> und die machen das dann meist. ausser sie mögen dich nich. dann darfste nochma fragen beantworten 22:30 < Ganneff> bei den dams darfste nur warten. die testen deine geduld 22:30 < Ganneff> irgendwann langweilen die sich aber 22:30 < Ganneff> und dann kriegste plötzlich mail 22:30 < Ganneff> OH MEIN GOTT. EIN NEUER DD. 22:30 < Ganneff> ende 22:30 < Ganneff> kapitel 2: 22:30 < cb> schöne beschreibung 22:30 < Ganneff> du machst ne zeit als dd rum 22:30 < Knusper> LOL 22:30 < Ganneff> votest durch die gegend 22:30 < Ganneff> lädst pakete umher 22:30 < Ganneff> machst bugs in stable 22:30 < Ganneff> gibts dem security team arbeit 22:31 < Ganneff> sprich - du gehst allen auf den sack. denn das is was ein dd macht. muss ja schliesslich auch spass machen. 22:31 < Ganneff> aber irgendwann, also irgendwann, da wird das langweilig 22:31 < Ganneff> und dann verschwindeste mal ne zeit. 22:31 < Ganneff> weil du weisst - da gibts noch son team. das brauch auch arbeit 22:31 < Ganneff> die suchen so leute die weggehen und sich verstecken 22:31 < Ganneff> nennt sich mia. die suchen. 22:31 < Ganneff> vielleicht finden die dich ja auch. 22:32 < Ganneff> dann kommste zurück und machst mal wieder etwas arbeit für security/stable/sonstwen 22:32 < Ganneff> oder nicht, aber das is langweilig, da fliegste einfach. 22:32 < Ganneff> wennde dann gar keinen bock mehr hast und ne längre pause willst 22:32 < Ganneff> dann gehste und machst eien auf emeritus 22:32 < Ganneff> das sind die rentner, die alten säcke, die sich zurücklehnen und über die versuche der neuen lachen die sich grad von den sponsoren quälen lassen 22:33 < Ganneff> ende kap. 2, ich hab keinen bock mehr. (jaja, emeritus)
Cheers to #debian.de on freenode 
Although I'm a really happy cupt user for several weeks now, I have to admit that I didn't read the manpage until a few minutes ago. But after being annoyed by apt-get source again, I thought that chances are good that cupt will help me. And so it was! Now there is a new alias in my zsh config:
alias tget='cupt source --tar-only'
Very useful if you work in teams which keep only the debian directory in their vcs and you need to upload a new revision of a package. Another thing that really rocks is the cupt shell. Give it a try! And don't forget to read cupt(1).
Now there is yet another package with a weird name in Debian - douf00 - a lightweight, slim and straight forward presentation tool. Written by some guys from a hacking and security team, which is mainly based in Vienna - guess that explains the l33t name (if you're scared now, yes, I've reviewed the code...). At the FrOSCon one of the authors asked me if I'd be willing to package it for Debian.I'm sure you'll love it if you're giving presentations and don't like to mess with Openoffice.org and friends. Below I've cited some parts of the README - make sure you read the linked file if you want to know more, or just install the package and give it a try.
Douf00 is a lightweight, slim and straight forward Presentation Tool. It assists novice as well as experienced speakers when giving lectures and business meetings. With its simple presenters Screen that includes current slide - next slide (preview) as well as timers it is designed to assist those of us, that are willing to step up their lectures to the next level.
The main reason why we created douf00 is because we (nice name crew) travel to conferences very often. As a matter of fact i always carried my macbook pro to every event. I always loved keynote and how the presenters screen works. Not having to worry about your beamer configuration and presenters screen is really comforting. However since i love to pack small and play big (on it stuff) i really felt we had to do something about it. Given the current situation presenters using linux have to deal with, we decided to simplify it. Of corse as a geek i would love to travel just with my netback saving valuable space in my backpack. In reality i was always caring my heavy macbook pro 15" everywhere just to lecture. Not only is it bad to give a presentation standing behind your machine because your presenters remote doesn't work. It is also highly annoying to always have to fumble around with your graphics card. Given the large verity of tools for creating your slides. (i.e.: powerpoint, open office impress, apple's keynote, latech-beamer,....) We felt there was no room for yet another slide creation tool. Nonetheless i noticed my desire to jump onstage, give a really good presentation without the usual worries. To be honest i use Keynote from apple on my home computer as i find it the most comforting tool to create slides. But now that we have created doufoo i save up on baggage space, and i finally managed to get rid of all the worries beforehand.
But what is doufoo? - The perfect choice for every presenter that has more important stuff todo than care about beamer configuration more than once. Its fast, simple and lightweight. We think that caring less about your gear and focusing on the presentation itself is the best way to keep your audience enthusiastic and entertained.
After installing the really awesome CyanogenMod on my G1/HTC Dream I was facing the problem that the keyboard layout was switched to qwerty - while I really prefer that on all my computers, it is annoying to use if you have to guess all the Alt keys.
There are several opinions out there about what to do to change the keyboard layout - the following procedure works well for me:
First download the android sdk if you haven't done so yet, you'll need adb from the tools directory. Connect your phone via USB and run
adb devices
to check if adb is able to detect the phone. If not, you probably need to setup the device permissions correctly. If adb is able to detect your devices, use it to remount /system read-write and enter a shell:
adb remount adb shell
Paste the following into the adb shell - please note that the phone will reboot. If you don't want that, don't paste the reboot line.
cp /system/usr/keychars/trout-keypad-qwertz.kcm.bin /system/usr/keychars/trout-keypad-v3.kcm.bin cp /system/usr/keychars/trout-keypad-qwertz.kcm.bin /system/usr/keychars/trout-keypad-v2.kcm.bin cp /system/usr/keychars/trout-keypad-qwertz.kcm.bin /system/usr/keychars/trout-keypad.kcm.bin cp /system/usr/keylayout/trout-keypad-qwertz.kl /system/usr/keylayout/trout-keypad-v3.kl cp /system/usr/keylayout/trout-keypad-qwertz.kl /system/usr/keylayout/trout-keypad-v2.kl cp /system/usr/keylayout/trout-keypad-qwertz.kl /system/usr/keylayout/trout-keypad.kl reboot
Now your keyboard layout should be qwertz again.
Downloading debconf translations from the bts and committing them to my packaging repository was always a task which pretty much annoyed me. Today I spent some time on writing a script which does this job for me. There is still much to improve - it is more like a prove of concept - but it works for me. With some love and probably a rewrite in Perl or Python it is a good candidate for devscripts probably.
#!/bin/bash
set -e
[ -d debian/po ] || exit 255
[ -r debian/control ] || exit 255
function get_ci_message() {
echo "Updating debconf translation: ${2}"
echo ""
echo "Thanks: $(echo ${3} | sed 's, <[^<]*@[^>]*>.*,,')"
echo "Closes: #${1}"
}
pkg_source=$(grep '^Source:' debian/control| awk '{print$2}')
for bug in $(bts select source:${pkg_source} tag:l10n tag:patch status:open); do
#sanety check - stop if there is somethign left to commit.
git status | grep -qE '^nothing.*to commit' || exit 255
#cache bug files
bts cache ${bug}
# po files are gzip or bz2 compressed sometimes
find ~/.devscripts_cache/bts/${bug} -type f -name '*.po.gz' -exec gunzip {} \;
find ~/.devscripts_cache/bts/${bug} -type f -name '*.po.bz2' -exec bunzip2 {} \;
#find the last .po file from the attachments
pofile=$(find ~/.devscripts_cache/bts/${bug} -type f -name '*.po' |\
sort | tail -1)
if [ -z ${pofile} ]; then
echo "Ignoring bug #${bug} - no po file found"
continue
fi
# find the basename of the .po file, some translators use
# packagename.xy.po, we try to work around that
basename=$(basename ${pofile} | sed 's,.*\.\([a-z][a-z].po\),\1,')
# sanety check if we have a filename like xy.po now
if ! echo ${basename} | grep -qE '^[a-z][a-z].po$'; then
echo "Ignoring bug #${bug} - ${basename} not a useful name"
continue
fi
cp ${pofile} debian/po/${basename}
#git add and commit it.
git add debian/po/${basename}
author=$(bts status ${bug} |\
grep '^originator' |\
awk -F '\t' '{print $2}')
get_ci_message ${bug} ${basename} ${author} | git commit -F - --author="${author}"
bts cleancache ${bug}
done
The git commit messages are prepared for usage with git-dch, which is my favourite way to write the Debian changelog.
Update: The script is using the originator information from the bug as author information for the commit now. Thanks to Santi for the comment! I could not test the changes yet, but I assume it will work well
One of my favourite plugins for pidgin is pidgin-blinklight, which blinks my ThinkPad's ThinkLight upon the arrival of new messages. Pretty useful as it is not as annoying (especially for others around you) as playing weird sounds. Unfortunately such a plugin is not available for other messengers like psi - but you're able to specify your own sound player. So I came up with the following script, which is my default sound player in psi now.
#!/bin/bash
IBMLIGHT="/proc/acpi/ibm/light"
function light_is_on() {
[ "on" = "`grep status ${IBMLIGHT} | awk '{print $2}'`" ]
return $?
}
function light_off() {
echo off > ${IBMLIGHT}
}
function light_on() {
echo on > ${IBMLIGHT}
}
if light_is_on; then
light_off
sleep 0.2
light_on
sleep 0.1
light_off
sleep 0.2
light_on
else
light_on
sleep 0.2
light_off
fi
Hint: In case you want a blinking light and sound, just add something like exec /usr/bin/play $@ at the end of the script.
Since a few days a new revision of gpsd is available in Debian/experimental. If you're a gpsd user, please give it a try as it contains various changes to the debconf templates and the config script. Although I don't expect any problems, it is better to test it well. Also there're several updates of the template translations missing and I want to give the translators some more time before uploading the package to unstable.
The other important change in the package was to add a gpsd-dbg package which contains all debug symbols and python-dbg builds of the extensions. Hopefully it will help to debug all gpsd related issues, although until now I did not have a single bug report where they would have been necessary.
Finally my thanks go to Christian Perrier and Justin B Rye for reviewing and fixing all the descriptions and templates.
