apt-get install debian-wizard

Insider infos, master your Debian/Ubuntu distribution

  • About
    • About this blog
    • About me
    • My free software history
  • Support my work
  • Get the newsletter
  • More stuff
    • Support Debian Contributors
    • Other sites
      • My company
      • French Blog about Free Software
      • Personal Website (French)
  • Mastering Debian
  • Contributing 101
  • Packaging Tutorials

People behind Debian: Christian Perrier, translation coordinator

March 3, 2011 by Raphaël Hertzog

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.

5 Free Software To Support With Flattr

March 1, 2011 by Raphaël Hertzog

Flattr FOSS LogoAnother month and thus another issue of Flattr FOSS. Time flies but Flattr’s usage seems to remain relatively strong.

I was fearing that people get bored after some time but that does not seem be to the case, my Flattr income does not really drop (it doesn’t take off either ;-)). I get a bit less for dpkg than at the start but a bit more for my blog.

Enough babbling, let’s go straight to the 5 projects to flattr this month:

  1. Linux Mint (Flattr link) is a Linux distribution based on Debian and Ubuntu that targets home desktop users. I have never tried it (I’m too much of an hardcore Debianer) but I’ve read several good reviews saying that it works well out of the box with good multimedia support. If you try it out, be sure to pick Linux Mint Debian Edition (LMDE). 🙂
  2. Network Block Device (NBD) user-space support tools (Flattr link) is the set of tools to setup a block device whose content is really on a remote server. It requires support of NBD in the kernel of course. The user space tools are maintained by Debian developer Wouter Verhelst.
  3. Tahoe LAFS (Flattr link) is a filesystem that implements a cloud storage. The data are distributed across multiple servers in such a way that it can continue to work even if one of the servers fails.
  4. Gajim (Flattr link) is a full featured and easy to use Jabber client. If you don’t need support of multiple instant messaging protocols, this Jabber client might be a good fit for you.
  5. Aurélien Gateau (Flattr link) is a KDE developer who takes one day per week off his work to work on KDE. He seeks support from the community to compensate for the loss of revenue. Much like me, he has a support page with a complete history of the amount of donations received. I can only sympathize with people who try to live true to their passion… good luck Aurélien!

This article is part of the Flattr FOSS project.

Debian Cleanup Tip #5: identify cruft that can be removed from your Debian system

February 28, 2011 by Raphaël Hertzog

Last week we learned how to identify and restore packages whose files have been corrupted. This time we’ll concentrate ourselves on the non-packaged files…

Non-packaged files

They are files which are not provided by a Debian package, or in other words, files where dpkg --search finds no associated package:

$ dpkg --search /srv/cvs
dpkg-query: no path found matching pattern /srv/cvs

You always have such files on your system, at least all your own files in /home. But many daemons also create files as part of their work (and they are usually stored in /var): internal files for a database server, mail spool for a mail server, etc. Those are normal and you want to leave them alone.

But you might have non-packaged files in /usr and that should not be the case if you install everything from packages. It would thus be useful to be able to list those files in order to detect a software that has been manually installed.

Manually installed software is not a good idea

Such an installation might cause troubles for example by taking precedence over the same software provided in a Debian package. Over time the local installation will not be upgraded while the packaged one will.

The other packages which depend on this software will believe they have the latest version since their dependency is satisfied but in fact they are using the older version since it takes precedence.

So you want to get rid of those? Let’s see how we can find them.

Use cruft to identify non-packaged files

As I explained above, there are many non-packaged files that are legitimate and that you don’t want to remove. That’s why cruft does something more elaborated than a scan of the filesystem and a check of dpkg’s database.

It provides a way for packages to say which files they might legitimately create during run-time and that cruft should not report. And it knows of many such files. But it’s far from exhaustive and definitely not up-to-date.

So you should always take its output with suspicion and consider twice where the file came from. Do not trust it blindly to remove the files… you have been warned.

How to use cruft

You should give it a list of directories to ignore to reduce the noise in the output, for example like this:

$ sudo cruft -d / -r report --ignore /home --ignore /var --ignore /tmp
$ less report
cruft report: mercredi 23 février 2011, 15:45:34 (UTC+0100)

---- missing: ALTERNATIVES ----
        /etc/alternatives/cli-csc.1.gz
        /usr/share/man/man1/cli-csc.1.gz
---- missing: dpkg ----
        /etc/xdg/autostart/gnome-power-manager.desktop
        /usr/lib/libpython2.6_d.so.1.0-gdb.py
        /usr/share/fonts/X11/100dpi
        /usr/share/fonts/X11/75dpi
---- unexplained: / ----
        /boot
        /dev
        /etc/.java
        /etc/.java/.systemPrefs
[...]
        /usr/lib/pymodules/python2.6
        /usr/lib/pymodules/python2.6/.path
        /usr/lib/pymodules/python2.6/Brlapi-0.5.5.egg-info
[...]

Note that it doesn’t traverse filesystems so if your /usr is on another partition than /, you will need to use the option -d "/ /usr" to have it scan both.

Analyze the report

Now you can quietly go through the report that has been generated and decide which files need to be removed or not. The report also contains missing files (files which should exist according to the dpkg database but which are not there) but the bulk of the listing will be in the “unexplained” section: files which are not part of any package (and whose presence is not explained by any other explain script that packages can ship).

Again take this with great suspicion, and you should rather not delete a file if you don’t know it got there in the first place. For instance, on my system it lists many files below /usr/lib/pymodules/ and those are legitimate: they come from Debian packages but they are copied there dynamically from /usr/{lib,share}/pyshared in order to support multiple python versions. If you remove those files, you effectively break your system.

You will also find many .pyc files created by python packages, they are a byte-compiled version of the corresponding .py file. Removing them breaks nothing but you loose a bit of performance.

On the opposite, most of the files below /usr/local/ are likely the result of some manual software installation and those should be safe to remove (if you know that you are not using the corresponding software).

Conclusion: useful but needs work

In summary, you can use cruft to identify non-packaged files and maybe learn a bit more about what got manually installed on the system, but it requires some patience to go through the report as many of the files reported are false positives.

Yes, cruft badly needs supplementary volunteers to cope with the many ways packages legitimately generate non-packaged files. It’s not even complicated work: the package is mostly in shell and in Perl, and /usr/share/doc/cruft/README.gz explains how it all works.

Do you want to read more tutorials like this one? Click here to subscribe to my free newsletter, you can opt to receive future articles by email.

February 2011 wrap up

February 26, 2011 by Raphaël Hertzog

February has been again a busy month for me. Here’s a quick summary of what I did:

Multi-Arch work

I have spent many days implementing and refining dpkg’s Multi-Arch support with Guillem Jover (dpkg co-maintainer) and Steve Langasek (beta-tester of my code ;-)). Early testers can try what’s in my latest pu/multiarch/snapshot/* branch in my personal git repository.

A Debian DVD shop

I’m always exploring new options to fund my Debian work (besides direct donations) and this month—with the Debian Squeeze release—I saw an opportunity in selling Debian DVD. Nobody provides DVD with included firmwares and quite a few people would like to avoid the SpaceFun theme. So I built unofficial Debian DVDs that integrate firmware and that install a system with the old theme (MoreBlue Orbit). Click here to learn more about my unofficial DVDs.

On my blog

In my “People behind Debian” series, I interviewed Mike Hommey (Iceweasel maintainer) and Maximiliam Attems (member of the kernel team).

I started a “Debian Cleanup Tip” series and already published 4 installments:

  • Debian Cleanup Tip #1: Get rid of useless configuration files
  • Debian Cleanup Tip #2: Get rid of obsolete packages
  • Debian Cleanup Tip #3: Get rid of third-party packages
  • Debian Cleanup Tip #4: Find broken packages and reinstall them

For contributors, I wrote two articles: the first gives a set of (suggested) best practices for sponsoring Debian packages and adapted my article as a patch for the Developers Reference. In the second article, I shared some personal advice for people who are considering participating on Debian mailing list: 7 mistakes to avoid when participating to Debian mailing lists.

Click here to subscribe to my free newsletter and get my monthly analysis on what’s going on in Debian and Ubuntu. Or just follow along via the RSS feed, Identi.ca, Twitter or Facebook.

  • « Previous Page
  • 1
  • …
  • 68
  • 69
  • 70
  • 71
  • 72
  • …
  • 102
  • Next Page »

Get the Debian Handbook

Available as paperback and as ebook.
Book cover

Email newsletter

Get updates and exclusive content by email, join the Debian Supporters Guild:

Follow me

  • Email
  • Facebook
  • GitHub
  • RSS
  • Twitter

Discover my French books

Planets

  • Planet Debian

Archives

I write software, books and documentation. I'm a Debian developer since 1998 and run my own company. I want to share my passion and knowledge of the Debian ecosystem. Read More…

Tags

3.0 (quilt) Activity summary APT aptitude Blog Book Cleanup conffile Contributing CUT d-i Debconf Debian Debian France Debian Handbook Debian Live Distro Tracker dpkg dpkg-source Flattr Flattr FOSS Freexian Funding Git GNOME GSOC HOWTO Interview LTS Me Multiarch nautilus-dropbox News Packaging pkg-security Programming PTS publican python-django Reference release rolling synaptic Ubuntu WordPress

Recent Posts

  • Freexian is looking to expand its team with more Debian contributors
  • Freexian’s report about Debian Long Term Support, July 2022
  • Freexian’s report about Debian Long Term Support, June 2022
  • Freexian’s report about Debian Long Term Support, May 2022
  • Freexian’s report about Debian Long Term Support, April 2022

Copyright © 2005-2021 Raphaël Hertzog