Search Results: "ed"

5 March 2011

Mike Hommey: More graphs for the Debian Bug Tracking System

I have been maintaining Debian Bug Tracking System graphs for a few years, now, though not very actively. They initially were available on people.debian.org/~glandium/bts/, but there have been some recent changes. A while ago, I started experimenting with brand new graphs on merkel.debian.org/~glandium/bts/, and when merkel was announced to be dying a few months ago, I got in touch with the QA team to know what to do with them, and it was decided we d put them on qa.debian.org. I unfortunately didn t follow up much on this and only recently actually worked on the migration, which took place 2 weeks ago. The result is that the graphs have officially moved to qa.debian.org/data/bts/graphs/, and links on the Package Tracking System have been updated accordingly. There is now also an additional graph tracking all open bugs in the BTS, across all packages: Today, I added a new feature, allowing to consolidate data for multiple arbitrary packages in a single graph. Such graphs can be generated with the following URL scheme (please don t over-abuse of it):
http://qa.debian.org/data/bts/graphs/multi/name0,name1,name2,etc.png
As an example, here is a graph for all the bugs on the packages I (co-)maintain:
http://qa.debian.org/data/bts/graphs/multi/dehydra,diggler,iceape,iceweasel,libxml2,libxslt,livehttpheaders,mozilla-dom-inspector,nspr,nss,pyxpcom,venkman,vmfs-tools,webkit,xulrunner,zfs-fuse.png
And here are the bugs affecting Mozilla-related packages:
http://qa.debian.org/data/bts/graphs/multi/iceape,icedove,iceowl,iceweasel,nspr,nss,xulrunner.png
I guess the next step is to allow per-maintainer consolidation through URLs such as
http://qa.debian.org/data/bts/graphs/by-maint/address.png
Update: per-maintainer consolidation has been added. (Hidden message here: please help triaging these bugs)

Lars Wirzenius: DPL nomination period for 2011

The nominations for Debian Project Leader elections for 2011 are open. As always, I'm tempted to nominate myself, but after thinking about it, I again conclude that I shouldn't. If I did nominate myself, there's a couple of things I'd like to push for. The DPL position is inherently a political one, which is why nothing in the list above is technical. On the other hand, I want to concentrate my Debian time on doing stuff that is fun, and right now that means writing code. I want to write code for Debian.

4 March 2011

Alexander Reichle-Schmehl: Picture could be titled: Me and my new best friend

Karsten Gerloff and Alexander Reichle-Schmehl I guess it's time to renew my Fellowship now :) Picture taken by Andre McMillan licensed CC by 2.0.

Steve Kemp: A final update on redisfs

I think I'm done with the redis filesystem for the moment. It does everything I need it to do, although I am curious to see how much faster it could go if it were to use non-blocking writes that isn't a major concern. There is only one missing feature I'm planning to play with - and that is the ability to implement snapshots. As a refresher redis is a key+value store, which mostly uses system memory. I've built a simple FUSE filesystem on top of that (now with symlink support!) and so all the file contents, meta-data, and similar is stored in memory. Implementing snapshots could be done by two different routes:
Copying all keys and their values, under a new name.
For example right now, by default, all the filesystem entries in the root directory are stored beneath the key "SKX:/" - where "SKX" is the key prefix. Assume I copy each existing key, and the associated value(s), giving them a new prefix such as "SKX2:" I can mount the filesystem against that prefix - and we've got a point-in-time snapshot.
Serialising all keys & values
Redis has a primitive which allows you to determine the names of keys at runtime. Given that all my filesystem keys have a prefix ("SKX:" by default) it wouldn't be difficult to find them, and serialise them. This would require more effort to re-import and re-mount, but it should be portable across hosts.
Anyway assuming I get this right we'll have a filesystem which is replication-friendly and snapshot-able. A fun combination. ObQuote: "We had been everywhere. We had really seen nothing. " - Lolita

Jo Shields: Protip: parallel-installing Mono versions in an APT-happy way

If you ve ever gotten tired of waiting for a new Mono release to appear, and taken matters into your own hands by compiling your own copy of Mono, you ve likely faced the problem of missing libraries. That s weird, it says it can t find gtk-sharp, but I have that package! This happens because every version of Mono on your system has what s called a Global Assembly Cache a location where all system-wide assemblies lives. So when you run an app like Tomboy, it loads its libraries such as GTK# from the GAC belonging to the Mono runtime being used. Ordinarily, this is in /usr/lib/mono/gac on a Debian/Ubuntu system. When you have your parallel Mono, it doesn t share a GAC as a result, libraries in your main distro GAC are not available in your DIY GAC, as they were never registered in there. Typically, the advice is to either start compiling every lib you need into a non-standard place too however, here s a better idea. Why not make Apt take care of not only your system s GAC but additional GACs too? We actually have structures in place to handle this, so it s not as hard as you think (merely relatively unknown). This guide does NOT take startup scripts into account it s your problem to ensure you re using the correct mono command to run your copy of MonoDevelop or Tomboy or whatever. You should probably learn about update-alternatives and $PATH for this. Oh, and this guide will BREAK HORRIBLY if you try to uninstall system mono completely. Don t try it. Setup step 1: preparation Don t install parallel Mono into /usr/local. I don t care what happens to you if you do. Use some random folder in /opt, usually a per-build prefix like /opt/mono-2.10 Setup step 2: duplicating existing magic Open a terminal, and copy /usr/share/cli-common/runtimes.d/mono to a new filename, e.g. /usr/share/cli-common/runtimes.d/mono-2.10 Setup step 3: tweak duplicate magic Open your copied file in an editor, and change the name value on line 27ish (e.g. from Mono\n to Mono (parallel 2.10 install)\n ). Then change the two places in the file, on lines 64ish and 120ish, from /usr/bin/gacutil to /opt/mono-2.8.2/bin/gacutil or equivalent. Setup step 4: apply magic to existing packages Run /usr/share/cli-common/gac-install mono-2.10 (or whatever filename you picked for your runtimes.d entry) as root. This will instantiate your parallel GAC(s). From now on, every GAC library you install or uninstall will happen to every single runtime in runtimes.d. To go back to how things were before, with only a single Mono runtime: Uninstall step 1: empty out parallel GAC Run /usr/share/cli-common/gac-remove mono-2.10 (or whatever filename you picked for your runtimes.d entry) as root. This will remove all packaged entried from your parallel GAC(s). Uninstall step 2: remove magic Delete your file from runtimes.d

Dirk Eddelbuettel: RcppArmadillo 0.2.14 and 0.2.15

A few days ago Conrad Sanderson released version 1.1.6 of his Armadillo templated C++ library for linear algebra. Accordingly, I made a new release 0.2.14 of RcppArmadillo, our Rcpp-based integration into R which included a few local fixes. However, while I updated SVN at the R-Forge project I didn't update the final tarball so Armadillo 1.1.6 wasn't in it. That is corrected in the 0.2.15 upload which is now on CRAN and its mirrors. The short NEWS file extract for both releases follows, also containing Conrad's entry for 1.1.6. A few minor tweaks were added but no user-visible changes:
0.2.15  2011-03-04
    o   Upgraded to Armadillo Version 1.1.6    Baby Carpet Shark 
         * fixed size matrices and vectors can use auxiliary (external) memory
         * .in_range() can use span() arguments
         * subfields can use span() arguments
0.2.14  2011-03-02
    o   Support Run-Time Type Information (RTTI) on matrices by setting the
        state variable vec_state in Row and Col instantiation, with thanks to
        Conrad Sanderson for the hint
    o   fastLm code simplified further by instantiating the Armadillo matrix
        and vector directly from the SEXP coming from R
    o   inst/doc/Makefile now respects $R_HOME environment variable
And courtesy of CRANberries, here are the diffs to.2.14
 ChangeLog                                                   14 -
 DESCRIPTION                                                  8 
 inst/NEWS                                                   10 
 inst/doc/RcppArmadillo-unitTests.pdf                     binary
 inst/doc/unitTests-results/RcppArmadillo-unitTests.html     10 
 inst/doc/unitTests-results/RcppArmadillo-unitTests.txt      39 +-
 inst/include/armadillo_bits/Col_meat.hpp                    51 +++
 inst/include/armadillo_bits/Col_proto.hpp                    3 
 inst/include/armadillo_bits/Cube_meat.hpp                   52 +++
 inst/include/armadillo_bits/Cube_proto.hpp                   7 
 inst/include/armadillo_bits/Mat_meat.hpp                    51 +++
 inst/include/armadillo_bits/Mat_proto.hpp                   12 
 inst/include/armadillo_bits/Row_meat.hpp                    51 +++
 inst/include/armadillo_bits/Row_proto.hpp                    3 
 inst/include/armadillo_bits/arma_version.hpp                 6 
 inst/include/armadillo_bits/config.hpp                       9 
 inst/include/armadillo_bits/field_meat.hpp                 220 ++++++++++++++--
 inst/include/armadillo_bits/field_proto.hpp                 20 +
 inst/unitTests/runit.RcppArmadillo.R                        16 +
 19 files changed, 521 insertions(+), 61 deletions(-)
and to the previous release 0.2.13, respectivel
 ChangeLog                                                   14 ++++++
 DESCRIPTION                                                  6 +-
 inst/NEWS                                                   11 +++++
 inst/doc/Makefile                                           15 +++++--
 inst/doc/RcppArmadillo-unitTests.pdf                     binary
 inst/doc/unitTests-results/RcppArmadillo-unitTests.html     18 ++++----
 inst/doc/unitTests-results/RcppArmadillo-unitTests.txt      34 ++++++++--------
 inst/include/RcppArmadillo/Col_meat.h                       24 ++++++-----
 inst/include/RcppArmadillo/Row_meat.h                       19 ++++----
 src/fastLm.cpp                                              15 ++-----
 10 files changed, 94 insertions(+), 62 deletions(-)
More information is on the RcppArmadillo page. Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page.

David Paleino: Optional argument with \newcommand in LaTeX

In LaTeX, it seems like you can't define a command with a really optional argument, using \newcommand. You can make commands with arguments having a default value though. Now, I found myself in need of having such a functionality. I had to google a while, but finally found it, so I'm posting it here, both to share knowledge and to remember it in future :) Suppose you want to do something like \mycmd foo and \mycmd foo bla , doing different things (in my case, I needed to add the second argument enclosed by parenthesis in the TOC and other places, but only if it was present) Here's the code:
\def\mycmd#1 \def\tempa #1 \futurelet\next\mycmd@i % Save first argument
\def\mycmd@i \ifx\next\bgroup\expandafter\mycmd@ii\else\expandafter\mycmd@end\fi %Check brace
\def\mycmd@ii#1 ... %Two args
\def\mycmd@end ... %Single args
In the last two lines of the code, use \tempa for your first argument, and #1 for your second optional argument. If you need spaces there (maybe as part of some text), be sure to escape them with a backslash \. I think it's expandable for additional arguments, but I haven't tried, and I don't feel like getting my hands dirty with TeX yet ;)

Wouter Verhelst: Dear lazyweb,

I'm a complete font n00b. How does one install Type1 fonts as part of a Debian package in such a way that: PMW, which I'm packaging for Debian, includes Type1 postscript fonts that it absolutely cannot live without; and while it's possible to create a .ps file from pmw that includes those fonts, by default it does not, so it's generally useful to put those fonts somewhere that ghostscript can find them. Only I know squat about how ghostscript finds fonts, and just adding a symlink /usr/share/fonts/type1/gsfonts/pmw -> ../../../pmw/psfonts (as was suggested to me on IRC) does not seem to do the trick. Thanks,

Michal Čihař: Fun with MinGW64 and ODBC

The test suite for recently added ODBC support in Gammu was consistently failing on Win64 platform (all others were just fine). It took me some time to figure out why. The reason is SQLLEN type, which is in some sort special, that generated code for it is broken. All started with pretty much standard retrieving value from ODBC result:
SQLLEN size;
SQLRETURN ret;
/* Figure out string length */
ret = SQLGetData(res->odbc, 1, SQL_C_CHAR, NULL, 0, &size);
if (!SQL_SUCCEEDED(ret))  
    return NULL;
 
/* Did not we get NULL? */
if (size == SQL_NULL_DATA)  
    return NULL;
 
/* Allocate buffer for string */
out = reallocate(out, size + 1);
The first problem was comparing of size against SQL_NULL_DATA. It simply always failed even if size did contain -1 (what is actually value of SQL_NULL_DATA). Yesterday, I've come out with typecasting magic that worked fine for this case. However what I've missed is that even reallocate is failing with this parameter. No matter what the size would be, it would return NULL. Typecasting again did help here. Hey, should not be compiler clever enough to typecast this for me? It turns out that in case of MinGW64 it is not. Anybody has suggestion why? At the end I ended up with pretty ugly duplicating of the variable just to avoid mixing it up in future changes (as would happen with typecasting everywhere). I'd really like to know why my assumptions are wrong in this case.

Filed under: English Gammu 0 comments Flattr this!

Craig Small: Apache and incomplete redirection messages

As part of moving my site around, I needed a bunch of redirects so that http://enc.com.au/docs/linuxload.html now becomes http://enc.com.au/2010/07/manually_calculating_process_times/ because its now controlled by WordPress. so I used the RedirectPermanent feature of mod_alias to do it with lines like:
RedirectPermanent /docs/linuxload.html /2010/07/manually_calculating_process_times/
So you come in on /docs/linuxload.html and redirect to the blog entry, simple really! It actually works, kinda, but the log files fill with things like:
[Fri Mar 04 14:40:17 2011] [warn] [client 172.16.242.1] incomplete redirection target of '/2010/07/manually_calculating_process_times/' for URI '/docs/linuxload.html' modified to 'http://enc.com.au/2010/07/manually_calculating_process_times/
What is going on? Why won t Apache just be quiet and be happy? The reason is in the Redirect Directive documentation on the 2.0 mod_alias page:
Also, URL-path must be a fully qualified URL, not a relative path, even when used with .htaccess files or inside of <directory> sections.
But I m running Apache 2.2 and the 2.2 mod_alias page says:
The new URL should be an absolute URL beginning with a scheme and hostname, but a URL-path beginning with a slash may also be used, in which case the scheme and hostname of the current server will be added.
That s it, you two choices: Changing the above config snippet to use absolute paths fixed it.
RedirectPermanent /docs/linuxload.html http://enc.com.au/2010/07/manually_calculating_process_times/

Cyril Brulebois: Debian XSF News #7

Time for a seventh Debian XSF News issue!

3 March 2011

Adrian von Bidder: Btrfs data deduplication

Apparently, it's coming. Haven't tested these patches, though (and why yet another btrfs-foo command rather than something integrated with the btrfs command?), but together with my hacked up dirvish (added support to create btrfs snapshots instead of hardlinked trees) this will save me a couple of gigabytes for all those backups of various servers (which I pretty much keep at the same releases.) The discussion on the btrfs mailing list got quite heated on the online vs. offline dedup issue (and also very silly IMO since nobody said online dedup shouldn't be supported. It's just not written yet...); What nobody mentioned was: how much memory is the hash index of an online dedup daemon going to consume, and how much CPU cache will it burn? This would be my main concern since my NAS only has 512M memory, and also needs to do NAT, VPN and DNS (yes, I'm a home user. I'd like to get the public IP off the NAS, but I'll have to buy some box to do this first...)

Russ Allbery: Personal Debian archive updated

This probably won't affect many people, but I wanted to note it here just in case. I've now finished the (long-delayed) work of updating my personal archive for the squeeze release. There is now a new wheezy distribution and squeeze is now treated as stable. lenny has become oldstable. For my future reference and for anyone else for whom it might be helpful, the changes required in reprepro:
  1. Update the distributions config file to add the wheezy distribution with a suite of testing and a pull policy of everything. Change the suite of squeeze to stable and the pull policy to arch-all. (These are pull policies defined elsewhere in my configuration that do what they say.) Change the suite of lenny to oldstable.
  2. Update the incoming config file to map the suites to new release code names.
  3. Pull all packages from sid into the new wheezy distribution:
        env GNUPGHOME=/srv/debian/keyring reprepro -b /srv/debian pull
  4. Update the archive symlinks:
        reprepro -b /srv/debian --delete createsymlinks
        reprepro -b /srv/debian createsymlinks
    
That's all there was to it. Easier than I was expecting it to be.

Thorsten Glaser: (Free)BSD vs. Linux

Warning: this is a rant against BSD (specifically FreeBSD , but don t let me get started on DragonFly, who think it s wise to drop all shells except ash from the base system and rely on pkgsrc yay let s compile a dozen packages just to get a shell with tab completion, not to mention boxen with no network access for the task although others seem to go into that direction too ; you know, there s BSD, and then there s FreeBSD ) don t like, don t read. If you want to change something in the BSD world, you gotta fork your own BSD no other way around the thickheads. Ok, back then, I ran into a particularily thick one, but others tend to not be much better. Users share the thickness. If you want to change something in the GNU/Linux world, just make a package, have someone upload it, prod (or pay, Hanno got a Radler) people to do it, or just upload it yourself. At the BSD booth at FOSDEM, despite me bringing the Windows Mobile 6 Professional devive, strictly for Geocaching mind you, Macintosh boxen had a share of more than 50% I didn t manage to tip the scale. At the Debian booth, almost everyone had a I want to buy a new laptop some day, but it just keeps on working and doesn t break pre-Lenovo IBM laptop. No hyping of Google either. (Last year s CLT saw BSD people advocating pro-Schily the guy with the broken encoding in his name shockingly.) Honestly, tcsh, FreeBSD people? Sorry. While I agree that there is merit on having the same script and interactive shell, as someone has pointed out (copy-paste examples into the command line), there s those zsh users who use mksh or GNU bash for scripting. Or just POSIX shell. And that s with an interactive shell which can be used for scripting. On the other hand, the C shell (both csh and tcsh) cannot. And what s with pretending the accent gravis is non-combining, called backtick (such a thing does not exist); and advocating it? Sorry, if your csh/tcsh doesn t handle the POSIX $( ) you should just drop it. (By the way, there is a convention that example command lines are prefixed with % for csh and $ for sh (or # but we write $ sudo instead, these days). Use it. Or leave it. If you have examples that substitute another process output, be specific.) It s funny to see how one person tries to defuse my arguments against csh by telling me it s just an interactive shell , while the other argues that people copy-paste between them, to which that was my response. Read the thread! And please, get your facts right. I would prefer that the standard shell be at least Bourne-compatible. You don t want Bourne ( ^ instead of for pipes), you want POSIX. That GNU bash is called the Bourne-Again Shell in one of their usual semi-bad puns doesn t help the global perception of such things any. Also, the root shell and /bin/sh are disjunct. (Plus, why change the root shell, use sudo(8), plain and simple.) ObNote: in jupp (should I package that for Debian, btw? rather upload, packages are ready ) the key is used as pr fix for Ctrl-X ( X) or to directly enter numerical (decimal, octal, sedecimal/hexadecadic) ASCII, 8-bit or Unicode codepoints. Yay!
And even the FSF has seen the light; for a few releases already, GCC uses ' ' instead of ' for quoting in messages, even without locales. Great job there! (LC_MESSAGES=en_GB.UTF-8 usually works, too, though.) ObDisclaimer: I have an (yes, Google ) Alert on the word mksh , so I know when it s being discussed. This obviously includes certain fora. Also, I m a shell implementer and bound to know a certain amount of details. Plus, mksh s build script runs with pretty much any Bourne/POSIX/Z Shell which has functions and not too many bugs. I wrote it. Go figure. No lowly trolling. FWIW, mksh(1) has the cat(1) builtin both because Android has no cat(1), and as speed hack. Almost all other shells have worse speed hacks, like a printf(1) builtin. And recently, builtins have become direct-callable, so this actually reduces the overall system footprint. (Its inclusion also provides for some other possibilities, internally.) And as two final side notes, if you haven t seen this: determine which shell we are run under (CVS) and I still offer a prompt conversion service (send me any GNU bash or oksh $PS1 and I ll send that to you in mksh(1) syntax optionally with adjustments/improvements, like cwd uses only up to 1/3 of screen width).

Kumar Appaiah: A new book on shell scripting

Over the next month or so, I've decided to read an interesting book which covers one of my favourite topics, shell scripting. The book is Linux Shell Scripting Cookbook. It has been quite a while since I have actually read a book on a programming topic (other than K&R or the like), but I guess it does feel "complete" to gain knowledge from a book and feel as though we have gained at least some mastery over the topic!Updates on this will follow.

Russell Coker: How Not to Park a Mercedes

Why is that Mercedes blocking so much of the road through the station car park?It s because it s the second car in a 1 car parking spot!Here s a front view.These were taken in the Coburg Station car park on Wednesday. The car park was about half empty, so the alternative to blocking part of the road and blocking in someone who was legally parked was to just park about 10 meters further away from the station.Some people just shouldn t be driving.

Michal &#268;iha&#345;: Gammu has ODBC support

One of features for Gammu SMSD which was for quite a long time in my head was ODBC support. With unified SQL backend we have right now it should be pretty easy to add support for it so I gave it a try. It really did not take to long and the ODBC driver is committed to git and will be part of next release. The great benefit of this is that we get native database support on Windows without need to linking against database libraries, which is always painful. The ODBC driver behaves like any other SQL based driver for SMSD, so if you are familiar with it, the configuration won't surprise you:
[smsd]
service = sql
driver = odbc
host = dsn_of_your_database
user = username
password = password
All important information about the driver should be available in the manual.

Filed under: English Gammu 0 comments Flattr this!

Kai Wasserb ch: Extending Chronicle

This little blog is created/compiled with Chronicle, coded by Steve Kemp, and one of the cool features is that you can specify a command run before/after your blog gets compiled from the input files. This presents us with one problem and a lot of opportunities. First to the problem: the singular "a command" (from the manual page) might not be enough. Maybe you want to run more than one command. This can be achieved by creating a directory for the commands you want to run before the compilation and one for the commands you want to run after the chronicle run. Then you create a small shell script one directory above and call that from chronicle, the script for the post-run might look like:
#!/bin/sh
set -e
WORKDIR=" dirname $ 0  /post"
find $ WORKDIR  -name "*.sh" -exec " " ";"
This script makes the assumption, that the scripts to run have a .sh suffix and are in a subdirectory named "post". But you can surely adapt this to your needs. Now to one of the oppurtunities this offers: you can now, for example, create static pages, which share the general visual appearance with your blog entries but don't show up in the tags or archive system. I'm using this to generate an imprint for this blog. The script to generate the imprint looks like:
#!/bin/sh
set -e
OUTPUT_PATH= grep output $ HOME /.chroniclerc   cut -d= -f2   tr -d [:blank:] 
sed -ne'/<\?xml version/,/blosxomFirstDayDiv/  /blosxomFirstDayDiv/b;p ' \
        $ OUTPUT_PATH /index.html > $ HOME /tmp/imprint.html
cat  dirname $ 0  /imprint.data >> $ HOME /tmp/imprint.html
echo -e "\n" >> $ HOME /tmp/imprint.html
sed -ne'/imprint_match/,$p' $ OUTPUT_PATH /index.html >> $ HOME /tmp/imprint.html
mv $ HOME /tmp/imprint.html $ OUTPUT_PATH /imprint.html
There are again some assumptions made here, which you'd need to adopt to your setup: Now you have a very powerful system to modify/extend your chronicle-generated blog. I hope you enjoy it as much as I do! A little P.S.: you might want to use version 4.5, as 4.4 had a nasty encoding bug.

Kai Wasserb ch: Extending Chronicle (Updated)

This little blog is created/compiled with Chronicle, coded by Steve Kemp, and one of the cool features is that you can specify a command run before/after your blog gets compiled from the input files. This presents us with one problem and a lot of opportunities. First to the problem: the singular "a command" (from the manual page) might not be enough. Maybe you want to run more than one command. This can be achieved by creating a directory for the commands you want to run before the compilation and one for the commands you want to run after the chronicle run. [UPDATE]Then just add run-parts /path/to/ before,post .d to your .chroniclerc for the pre,post -build configuration entries.[/UPDATE] (Thanks to Steve for pointing the obvious out to me, don't know why I didn't think of run-parts myself.) Now to one of the oppurtunities this offers: you can now, for example, create static pages, which share the general visual appearance with your blog entries but don't show up in the tags or archive system. I'm using this to generate an imprint for this blog. The script to generate the imprint looks like:
#!/bin/sh
set -e
OUTPUT_PATH= grep output $ HOME /.chroniclerc   cut -d= -f2   tr -d [:blank:] 
sed -nre'/<\?xml version/,/blosxomFirstDayDiv/  /blosxomFirstDayDiv/b;p ' \
        $ OUTPUT_PATH /index.html > $ HOME /tmp/imprint.html
cat  dirname $ 0  /imprint.data >> $ HOME /tmp/imprint.html
echo -e "\n" >> $ HOME /tmp/imprint.html
sed -ne'/imprint_match/,$p' $ OUTPUT_PATH /index.html >> $ HOME /tmp/imprint.html
mv $ HOME /tmp/imprint.html $ OUTPUT_PATH /imprint.html
There are again some assumptions made here, which you'd need to adopt to your setup: Now you have a very powerful system to modify/extend your chronicle-generated blog. I hope you enjoy it as much as I do! A little P.S.: you might want to use version 4.5, as 4.4 had a nasty encoding bug.

Rapha&#235;l Hertzog: People behind Debian: Christian Perrier, translation coordinator

Christian is a figure of Debian, not only because of the tremendous coordination work that he does within the translation project, but also because he s very involved at the social level. He s probably in the top 5 of the persons who attended most often the Debian conference. Christian is a friend (thanks for hosting me so many times when I come to Paris for Debian related events) and I m glad that he accepted to be interviewed. He likes to speak and that shows in the length of his answers :-) but you ll be traveling the world while reading him. My questions are in bold, the rest is by Christian. Who are you? I am a French citizen (which is easy to guess unless you correct my usual mistakes in what follows). I m immensely proud of being married for nearly 26 years with Elizabeth (who deserves a statue from Debian for being so patient with my passion and my dedication to the project). I m also the proud father of 3 wonderful kids , aged 19 to 23. I work as team manager in the Networks and Computers Division of Onera the French Aerospace lab , a public research institute about Aeronautics, Space and Defense. My team provides computer management services for research divisions of Onera, with a specific focus put on individual computing. I entered the world of free software as one of the very first users of Linux in France. Back in the early 1990 s, I happened (though the BBS users communities) to be a friend of several early adopters of Linux and/or BSD386/FreeBSD/NetBSD in France. More specifically, I discovered Linux thanks with my friend Ren Cougnenc (all my free software talks are dedicated to Ren , who passed away in 1996). You re not a programmer, not even a packager. How did you come to Debian? I m definitely not a programmer and I never studied computing (I graduated in Materials Science and worked in that area for a few years after my PhD). However, my daily work always involved computing (I redesigned the creep testing laboratory and its acquisition system all by myself during my thesis research work). An my hobbies often involved playing with home computers, always trying to learn about something new. So, first learning about a new operating system then trying to figure out how to become involved in its development was quite a logical choice. Debian is my distro of choice since it exists. I used Slackware on work machines for a while, but my home server, kheops, first ran Debian 1.1 when I stopped running a BBS on an MS-DOS machine to host a news server. That was back in October 1996. I then happened to be a user, and more specifically a user of genealogy software, also participating very actively in Usenet from this home computer and server, that was running this Debian thing. So, progressively, I joined mailing lists and, being a passionate person, I tried to figure out how I could bring my own little contribution to all this. This is why I became a packager (yes, I am one!) by taking over the geneweb package, which I was using to publish my genealogy research. I applied as DD in January 2001, then got my account in July 2001. My first upload to the Debian archive occurred on August 22nd 2001: that was of course geneweb, which I still maintain. Quite quickly, I became involved in the work on French localization. I have always been a strong supporter of localized software (I even translated a few BBS software back in the early 90 s) as one of the way to bring the power and richness of free software to more users. Localization work lead me to work on the early version of Debian Installer, during those 2003-2005 years where the development of D-I was an incredibly motivating and challenging task, lead by Joey Hess and his inspiring ideas. From user to contributor to leader, I suddenly discovered, around 2004, that I became the coordinator of D-I i18n (internationalization) without even noticing :-) You re the main translation coordinator in Debian. What plans and goals have you set for Debian Wheezy? As always: paint the world in red. Indeed, this is my goal for years. I would like our favorite distro to be able to be used by anyone in the world, whether she speaks English, Northern Sami, Wolof, Uyghur or Secwepemcts n. As a matter of symbol, I use the installer for this. My stance is that one should be able to even install Debian in one s own language. So, for about 7 years, I use D-I as a way to attract new localization contributors. This progress is represented on this page where the world is gradually painted in red as long as the installer supports more languages release after release. The map above tries to illustrate this by painting in red countries when the most spoken language in the country is supported in Debian Installer. However, that map does not give enough reward to many great efforts made to support very different kind of languages. Not only various national languages, but also very different ones: all regional languages of Spain, many of the most spoken languages in India, minority languages such as Uyghur for which an effort is starting, Northern Sami because it is taught in a few schools in Norway, etc., etc. Still, the map gives a good idea of what I would like to see better supported: languages from Africa, several languages in Central Asia. And, as a very very personal goal, I m eagerly waiting for support of Tibetan in Debian Installer, the same way we support its sister language, Dzongkha from Bhutan. For this to happen, we have to make contribution to localization as easy as possible. The very distributed nature of Debian development makes this a challenge, as material to translate (D-I components, debconf screens, native packages, packages descriptions, website, documentation) is very widely spread. A goal, for years, is to set a centralized place where translators could work easily without even knowing about SVN/GIT/BZR or having to report bugs to send their work. The point, however, would be to have this without making compromises on translation quality. So, with peer review, use of thesaurus and translation memory and all such techniques. Tools for this exist: we, for instance, worked with the developers of Pootle to help making it able to cope with the huge amount of material in Debian (think about packages descriptions translations). However, as of now, the glue between such tools and the raw material (that often lies in packages) didn t come. So, currently, translation work in Debian requires a great knowledge of how things are organized, where is the material, how it can be possible to make contribution reach packages, etc. And, as I m technically unable to fulfill the goal of building the infrastructure, I m fulfilling that role of spreading out the knowledge. This is how I can define my coordinator role. Ubuntu uses a web-based tool to make it easy to contribute translations directly in Launchpad. At some point you asked Canonical to make it free software. Launchpad has been freed in the mean time. Have you (re)considered using it? Why not? After all, it more or less fills in the needs I just described. I still don t really figure out how we could have all Debian material gathered in Rosetta/Launchpad .and also how Debian packagers could easily get localized material back from the framework without changing their development processes. I have always tried to stay neutral wrt Ubuntu. As many people now in Debian, I feel like we have reached a good way to achieve our mutual development. When it comes at localization work, the early days where the everything in Rosetta and translates who wants stanza did a lot of harm to several upstream localization projects is, I think, way over. Many people who currently contribute to D-I localization were indeed sent to me by Ubuntu contributors .and by localizing D-I, apt, debconf, package descriptions, etc., they re doing translation work for Ubuntu as well as for Debian. Let s say I m a Debian user and I want to help translate Debian in my language. I can spend 1 hour per week on this activity. What should I do to start? Several language teams use Debian mailing lists to coordinate their work. If you re lucky enough to be a speaker of one of these languages, try joining debian-l10n-<yourlanguage> and follow what s happening there. Don t try to immediately jump in some translation work. First, participate to peer reviews: comment on others translations. Learn about the team s processes, jargon and habits. Then, progressively, start working on a few translations: you may want to start with translations of debconf templates: they are short, often easy to do. That s perfect if you have few time. If no language team exists for your language, try joining debian-i18n and ask about existing effort for your language. I may be able to point you to individuals working on Debian translations (very often along with other free software translation efforts). If I am not, then you have just been named coordinator for your language :-) I may even ask you if you want to work on translating the Debian Installer. What s the biggest problem of Debian? We have no problems, we only have solutions :-) We are maybe facing a growth problem for a few years. Despite the increased welcoming aspects of our processes (Debian Maintainers), Debian is having hard times in growing. The overall number of active contributors is probably stagnating for quite a while. I m still amazed, however, to see how we can cope with that and still be able to release over the years. So, after all, this is maybe not a problem :-) Many people would point communication problems here. I don t. I think that communication inside the Debian project is working fairly well now. Our famous flame wars do of course still happen from time to time, but what large free software project doesn t have flame wars? In many areas, we indeed improved communication very significantly. I want to take as an example the way the release of squeeze has been managed. I think that the release team did, even more this time, a very significant and visible effort to communicate with the entire project. And the release of squeeze has been a great success in that matter. So, there s nearly nothing that frustrates me in Debian. Even when a random developer breaks my beloved 100% completeness of French translations, I m not frustrated for more than 2 minutes. You re known in the Debian community as the organizer of the Cheese & Wine Party during DebConf. Can you tell us what this is about? This is an interesting story about how things build themselves in Debian. It all started in July 2005, before DebConf 5 in Helsinki. Denis Barbier, Nicolas Fran ois and myself agreed to bring at Debconf a few pieces of French cheese as well as 1 or 2 bottles of French wine and share them with some friends. Thus, we settled an informal meeting in the French room where we invited some fellows: from memory, Benjamin Mako Hill, Hannah Wallach, Matt Zimmermann and Moray Allan. All of us fond of smelly cheese, great wine plus some extra p t home-made by Denis in Toulouse. It finally happened that, by word of mouth, a few dozens of other people slowly joined in that French room and turned the whole thing into an improvized party that more or less lasted for the entire night. The tradition was later firmly settled in 2006, first in Debconf 6 in Mexico where I challenged the French DDs to bring as many great cheese as possible, then during the Debian i18n meeting in Extremadura (Sept 2006) where we reached the highest amount of cheese per participant ever. I think that the Creofonte building in Casar de C ceres hasn t fully recovered from it and is still smelling cheese 5 years after. This party later became a real tradition for DebConf, growing over and over each year. I see it as a wonderful way to illustrate the diversity we have in Debian, as well as the mutual enrichment we always felt during DebConfs. My only regret about it is that it became so big over the years that organizing it is always a challenge and I more and more feel pressure to make it successful. However, over the years, I always found incredible help by DebConf participants (including my own son, last year a moment of sharing which we will both remember for years, i think). And, really, in 2010, standing up on a chair, shouting (because the microphone wasn t working) to thank everybody, was the most emotional moment I had at Debconf 10. Is there someone in Debian that you admire for their contributions? So many people. So, just like it happens in many awards ceremonies, I will be very verbose to thank people, sorry in advance for this. The name that comes first is Joey Hess. Joey is someone who has a unique way to perceive what improvements are good for Debian and a very precise and meticulous way to design these improvements. Think about debconf. It is designed for so long now and still reaching its very specific goal. So well designed that it is the entire basis for Joey s other achievement: designing D-I. Moreover, I not only admire Joey for his technical work, but also for his interaction with others. He is not he loudest person around, he doesn t have to .just giving his point in discussion and, guess what? Most of the time, he s right. Someone I would like to name here, also, is Colin Watson. Colin is also someone I worked with for years (the D-I effect, again ) and, here again, the very clever way he works on technical improvements as well as his very friendly way to interact with others just make it. And, how about you, Rapha l? :-) I m really admirative of the way you work on promoting technical work on Debian. Your natural ability to explain things (as good in English as it is in French) and your motivation to share your knowledge are a great benefit for the project. Not to mention the technical achievements you made with Guillem on dpkg of course! Another person I d like to name here is Steve Langasek. We both maintain samba packages for years and collaboration with him has always been a pleasure. Just like Colin, Steve is IMHO a model to follow when it comes at people who work for Canonical while continuing their involvment in Debian. And, indeed, Steve is so patient with my mistakes and stupid questions in samba packaging that he deserves a statue. We re now reaching the end of the year where Stefano Zacchiroli was the Debian Project Leader. And, no offense intended to people who were DPL before him (all of them being people I consider to be friends of mine), I think he did the best term ever. Zack is wonderful in sharing his enthusiasm about Debian and has a unique way to do it. Up to the very end of his term, he has always been working on various aspects of the project and my only hope is that he ll run again (however, I would very well understand that he wants to go back to his hacking activities!). Hat off, Zack!I again have several other people to name in this Bubulle hall of Fame : Don Armstrong, for his constant work on improving Debian BTS, Margarita Manterola as one of the best successes of Debian Women (and the most geeky honeymoon ever), Denis Barbier and Nicolas Fran ois because i18n need really skilled people, Cyril Brulebois and Julien Cristau who kept X.org packaging alive in lenny and squeeze, Otavio Salvador who never gave up on D-I even when we were so few to care about it. I would like to make a special mention for Frans Pop. His loss in 2010 has been a shock for many of us, and particularly me. Frans and I had a similar history in Debian, both mostly working on so-called non technical duties. Frans has been the best release manager for D-I (no offense intended, at all, to Joey or Otavio .I know that both of them share this feeling with me). His very high involvment in his work and the very meticulous way he was doing it lead to great achievements in the installer. The Installation Guide work was also a model and indeed a great example of non technical work that requires as many skills as more classical technical work. So, and even though he was sometimes so picky and, I have to admit, annoying, that explains why I m still feeling sad and, in some way, guilty about Frans loss. One of my goals for wheezy is indeed to complete some things Frans left unachieved. I just found one in bug #564441: I will make this work reach the archive, benefit our users and I know that Frans would have liked that.
Thank you to Christian for the time spent answering my questions. I hope you enjoyed reading his answers as I did. Subscribe to my newsletter to get my monthly summary of the Debian/Ubuntu news and to not miss further interviews. You can also follow along on Identi.ca, Twitter and Facebook.

7 comments Liked this article? Click here. My blog is Flattr-enabled.

Next.

Previous.