Free Software · I still don't have a title

Weird VirtIO errors on a jessie KVM host: Fixed!

Fri, 08 Jan 2016 10:57:00 +0000

Yesterday I posted a desperate plea for help as I had no idea where else to look for clues on what was causing random I/O errors on the guests of our jessie KVM host.

Thanks to Michael Herold, who was kind enough to mail me after identifying our problem, now we know os-prober is to blame, triggering the problem on every kernel update on the host, and we have quickly uninstalled it from all our systems.

Thanks Michael! If you by any chance going to attend FOSDEM, I am so happily going to buy you beers!

Let’s hope anyone else wondering what’s going on with their filesystems will find the trail to these blog posts to find a quick solution!

Weird VirtIO errors on a jessie KVM host running Debian guests

Thu, 07 Jan 2016 16:20:00 +0000

Hi Interwebs! I’m facing a weird issue with one of our server’s at work, involving Debian jessie, libvirt and Debian guests using VirtIO drivers. This is a plea for help. :)

Basically, we are getting random VirtIO errors inside our guests, resulting in stuff like this:

[4735406.568235] blk_update_request: I/O error, dev vda, sector 142339584
[4735406.572008] EXT4-fs warning (device dm-0): ext4_end_bio:317: I/O error -5 writing to inode 1184437 (offset 0 size 208896 starting block 17729472)
[4735406.572008] Buffer I/O error on device dm-0, logical block 17729472
[ ... ]
[4735406.572008] Buffer I/O error on device dm-0, logical block 17729481
[4735406.643486] blk_update_request: I/O error, dev vda, sector 142356480
[ ... ]
[4735406.748456] blk_update_request: I/O error, dev vda, sector 38587480
[4735411.020309] Buffer I/O error on dev dm-0, logical block 12640808, lost sync page write
[4735411.055184] Aborting journal on device dm-0-8.
[4735411.056148] Buffer I/O error on dev dm-0, logical block 12615680, lost sync page write
[4735411.057626] JBD2: Error -5 detected when updating journal superblock for dm-0-8.
[4735411.057936] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
[4735411.057946] EXT4-fs error (device dm-0): ext4_journal_check_start:56: Detected aborted journal
[4735411.057948] EXT4-fs (dm-0): Remounting filesystem read-only
[4735411.057949] EXT4-fs (dm-0): previous I/O error to superblock detected

(From an Ubuntu 15.04 guest, EXT4 on LVM2)

Or,

Jan 06 03:39:11 titanium kernel: end_request: I/O error, dev vda, sector 1592467904
Jan 06 03:39:11 titanium kernel: EXT4-fs warning (device vda3): ext4_end_bio:317: I/O error -5 writing to inode 31169653 (offset 0 size 0 starting block 199058492)
Jan 06 03:39:11 titanium kernel: Buffer I/O error on device vda3, logical block 198899256
[ ... ]
Jan 06 03:39:12 titanium kernel: Aborting journal on device vda3-8.
Jan 06 03:39:12 titanium kernel: Buffer I/O error on device vda3, logical block 99647488

(From a Debian jessie guest, EXT4 directly on a VirtIO-based block device)

When this happens, it affects multiple guests on the hosts at the same time. Normally they are severe enough that they end up with a r/o file system, but we’ve seen a few hosts survive with a non-fatal I/O error. The host’s dmesg has nothing interesting to see.

We’ve seen this happen with quite heterogeneous guests:

Debian 6, 7 and 8 (Debian kernels 2.6.32, 3.2 and 3.16)
Ubuntu 14.09 and 15.04 (Ubuntu kernels)
32 bit and 64 bit installs.

In short, we haven’t seen a clear characteristic in any guest, other than the affected hosts being the ones with some sustained I/O load (build machines, cgit servers, PostgreSQL RDBMs…). Most of the times, hosts that just sit there doing nothing with their disks are not affected.

The host is a stock Debian jessie install that manages libvirt-based QEMU guests. All the guests have their block devices using virtio drivers, some of them on spinning media based on LSI RAID (was a 3ware card before, got replaced as we were very suspicious about it, but are getting the same results), and some of them based on PCIe SSD storage. We have some other 3 hosts, similar setup except they run Debian wheezy (and honestly we’re not too keen on upgrading them yet, just in case), none of them has ever shown this kind of problem.

We’ve been seeing this since last summer, and haven’t found a pattern that tells us where these I/O error bugs are coming from. Google isn’t revealing other people with a similar problem, and we’re finding that quite surprising as our setup is quite basic.

So, dear Interwebs, have you seen this? We could use any comment (on the blog, or in Debian bug #810121, or kernel bug 110441) that clues us on what’s to blame here. Thanks in advance!

Update: We finally know what’s going on! The problem is gone at long last!

A pile of reasons why GNOME should be Debian jessie’s default desktop environment

Thu, 07 Aug 2014 23:58:00 +0000

GNOME has, for some reason or another, always been the default desktop environment in Debian since the installer is able to install a full desktop environment by default. Release after release, Debian has been shipping different versions of GNOME, first based on the venerable 1.2/1.4 series, then moving to the time-based GNOME 2.x series, and finally to the newly designed 3.4 series for the last stable release, Debian 7 ‘wheezy’.

During the final stages of wheezy’s development, it was pointed out that the first install CD image would not longer hold all of the required packages to install a full GNOME desktop environment. There was lots of discussion surrounding this bug or fact, and there were two major reactions to it. The Debian GNOME team rebuilt some key packages so they would be compressed using xz instead of gzip, saving the few megabytes that were needed to squeeze everything in the first CD. In parallel, the tasksel maintainer decided switching to Xfce as default desktop was another obvious fix. This change, unannounced and two days before the freeze, was very contested and spurred the usual massive debian-devel threads. In the end, and after a few default desktop flip flops, it was agreed that GNOME would remain as the default for the already frozen wheezy release, and this issue would be revisited later on during jessie’s development.

And indeed, some months ago, Xfce was again reinstated as Debian’s default desktop for jessie as announced:

Change default desktop to xfce.

This will be re-evaluated before jessie is frozen. The evaluation will
start around the point of DebConf (August 2014). If at that point gnome
looks like a better choice, it’ll go back as the default.

Some criteria for that choice will include:

* Popcon numbers for gnome on jessie. If gnome installations continue to
 rise fast enough despite xfce being the default (compared with, say
 kde installations), then we’ll know that users prefer gnome.
 Currently we have no data about how many users would choose gnome when
 it’s not the default. Part of the reason for switching to xfce now
 is to get such data.

* The state of accessability support, particularly for the blind.

* How well the UI works for both new and existing users. Gnome 3
 seems to be adding back many gnome 2 features that existing users
 expect, as well as making some available via addons. If it feels
 comfortable to gnome 2 (and xfce) users, that would go a long way
 toward switching back to it as the default. Meanwhile, Gnome 3 is also
 breaking new ground in its interface; if the interface seems more
 welcoming to new users, or works better on mobile devices, etc, that
 would again point toward switching back.

* Whatever size constraints exist for CD or other images at the time.

--

Hello to all the tech journalists out there. This is pretty boring.
Why don’t you write a story about monads instead?

― Joey Hess in dfca406eb694e0ac00ea04b12fc912237e01c9b5.

Suffice to say that the Debian GNOME team participants have never been thrilled about how the whole issue is being handled, and we’ve been wondering if we should be doing anything about it, or just move along and enjoy the smaller amount of bug reports against GNOME packages that this change would bring us, if it finally made it through to the final release. During our real life meet-ups in FOSDEM and the systemd+GNOME sprint in Antwerp, most members of the team did feel Debian would not be delivering a graphical environment with the polish we think our users deserve, and decided we at least should try to convince the rest of the Debian project and our users that Debian will be best suited by shipping GNOME 3.12 by default. Power users, of course, can and know how to get around this default and install KDE, Xfce, Cinnamon, MATE or whatever other choice they have. For the average user, though, we think we should be shipping GNOME by default, and tasksel should revert the above commit again. Some of our reasons are:

Accessibility: GNOME continues to be the only free desktop environment that provides full accessibility coverage, right from login screen. While it’s true GNOME 3.0 was lacking in many areas, and GNOME 3.4 (which we shipped in wheezy) was just barely acceptable thanks to some last minute GDM fixes, GNOME 3.12 should have ironed out all of the issues and our non-expert understanding is that a11y support is now on par with what GNOME 2.30 from squeeze offered.
Downstream health: The number of active members in the team taking care of GNOME in Debian is around 5-10 persons, while it is 1-2 in the case of Xfce. Being the default desktop draws a lot of attention (and bug reports) that only a bigger team might have the resources to handle.
Upstream health: While GNOME is still committed to its time-based release schedule and ships new versions every 6 months, Xfce upstream is, unfortunately, struggling a bit more to keep up with new plumbing technology. Only very recently it has regained support to suspend/hibernate via logind, or support for Bluez 5.x, for example.
Community: GNOME is one of the biggest free software projects, and is lucky to have created an ecosystem of developers, documenters, translators and users that interact regularly in a live social community. Users and developers gather in hackfests and big, annual conferences like GUADEC, the Boston Summit, or GNOME.Asia. Only KDE has a comparable community, the rest of the free desktop projects don’t have the userbase or humanpower to sustain communities like this.
Localization: Localization is more extensive and complete in GNOME. Xfce has 18 languages above 95% of coverage, and 2 at 100% (excluding English). GNOME has 28 languages above 95%, 9 of them being complete (excluding English).
Documentation: Documentation coverage is extensive in GNOME, with most of the core applications providing localized, up to date and complete manuals, available in an accessible format via the Help reader.
Integration: The level of integration between components is very high in GNOME. For example, instant messaging, agenda and accessibility components are an integral part of the desktop. GNOME is closely integrated to NetworkManager, PulseAudio, udisks and upower so that the user has access to all the plumbing in a single place. GNOME also integrates easily with online accounts and services (ownCloud, Google, MS Exchange…).
Hardware: GNOME 3.12 will be one of the few desktop environments to support HiDPI displays, now very common on some laptop models. Lack of support for HiDPI means non-technical users will get an unreadable desktop by default, and no hints on how to fix that.
Security: GNOME is more secure. There are no processes launched with root permissions on the user’s session. All everyday operations (package management, disk partitioning and formatting, date/time configuration…) are accomplished through PolicyKit wrappers.
Privacy: One of the latest focuses of GNOME development is improving privacy, and work is being done to make it easy to run GNOME applications in isolated containers, integrate Tor seamlessly in the desktop experience, better disk encryption support and other features that should make GNOME a more secure desktop environment for end users.
Popularity: One of the metrics discussed by the tasksel change proponents mentioned popcon numbers. 8 months after the desktop change, Xfce does not seem to have made a dent on install numbers. The Debian GNOME team doesn’t feel popcon’s data is any better than a random online poll though, as it’s an opt-in service which the vast majority of users don’t enable.
systemd embracing: One of the reasons to switch to Xfce was that it didn’t depend on systemd. But now that systemd is the default, that shouldn’t be a problem. Also given ConsoleKit is deprecated and dead upstream, KDE and Xfce are switching or are planning to switch to systemd/logind.
Adaptation: Debian forced a big desktop change with the wheezy release, switching from the traditional GNOME 2.x to the new GNOME Shell environment. Switching again would mean more adaptation for uses when they’ve had two years to experience GNOME 3.4. Furthermore, GNOME 3.12 means two years of improvements and polishing to GNOME 3.4, which should help with some of the rough edges found in the GNOME release shipped with wheezy.
Administration: GNOME is easy to administrate. All the default settings can be defined by administrators, and mandatory settings can be forced to users, which is required in some companies and administrations; Xfce cannot do that. The close integration with freedesktop components (systemd, NM, PulseAudio…) also gives access to specific and useful administration tools.

In short, we think defaulting to GNOME is the best option for the Debian release, and in contrast, shipping Xfce as the default desktop could mean delivering a desktop experience that has some incomplete or rough edges, and not on par with Debian quality standards for a stable release. We believe tasksel should again revert the change and be uploaded as soon as possible, in order to get people testing images with GNOME the sooner the better, with the freeze only two months away.

We would also like that in the future, changes of this nature will not be announced in a git commit log, but widely discussed in debian-project and the other usual development/decision channels, like the change of init system happened recently. We will, whichever the final decision is, continue to package GNOME with great care to ensure our users get the best possible desktop experience Debian can offer.

GUADEC 2012

Sun, 29 Jul 2012 16:31:00 +0000

I’ve been in A Coruña for this year’s GUADEC since Tuesday night, and it rocked. I did a late registration after my first week at Collabora, which is sponsoring my stay here.

I came one day early to participate, as Debian’s representative, at the yearly GNOME Advisory Board meeting, for the first time. It was a positive experience, which helped me get a grasp of the “big picture” of what the GNOME Foundation does. I also had the pleasure of visiting Igalia’s awesome offices in the city, and puting faces to many names during the meeting.

I presented an overview of Debian’s relation to GNOME, how our packaging team works and what are our goals and biggest problems as a GNOME downstream. We stirred some good debate as some other Advisory Board members share part of our problems. I should be posting a summary of what happened there for debian-project@ldo as soon as I have the time to scribble it.

I’ve met with GNOME Hispano people I hadn’t seen since 2004 or 2006 in the best case, and catched up with many of them. I’ve also met many GPUL members I had know for over a decade via IRC, but never had met in person, and it was about time. And of course, I’ve got to known a good number of my new workmates at Collabora, and had fun with them around the conference, the beach and the numerous post-conference events.

Last, but not least, I ended up participating in the GNOME Olympics, substituting Rodrigo in Team B “Core Dumped”, along with Stefano, John, Bastien, Chema and Adam. WE WON, not thanks to me, but the statistics shine: I’ve won all FreeFA World Cups I’ve played :P so here’s a PROtip: if you want to win next year, be sure to be my team mate, and more importantly, be sure Adam is not your rival. :)

Unfortunately, I’m only attending the core days so tonight I’ll be flying back to Madrid on my way home in València. See you next year! A Coruña is a city that has impressed me quite a bit, and I’m looking forward to coming back for some more standard vacation at some point. :)

GNOME 3.4 in wheezy

Sun, 03 Jun 2012 09:47:00 +0000

Users of Debian sid will have noticed: the final (and interesting) bits of GNOME 3.4 have landed and if all looks as good as it does now, they should migrate to wheezy in about a week.

3.2 → 3.4 hasn’t been as complicated as the previous horrible transition, but still had some complications due to Cogl/Clutter incompatibilities. Other than that, our major problem has been manpower, but this isn’t new for many other Debian teams. We’ve also seen new incarnations of “Linux-only technology is now mandatory” which makes our lives a bit more miserable due to kfreebsd-* and hurd-i386, but for now we’ve still been able to dodge it. It seems wheezy+1 will be fun in that regard though, and we might need to take drastic approaches.

If all goes well and the current lot (GNOME Shell, Control Center, Settings daemon, Mutter…) transitions without additional problems, we should be wrapping up our transitions for wheezy with Evolution and friends (currently sitting in experimental), and hopefully GDM 3.4.

As we get many questions regarding the status of GDM in Debian, let’s add a short note on this. Packaging GDM, at least in its current upstream form, is not a matter of unpacking a new tarball and editing debian/changelog. When Joss works on a new major version, the amount of tweaking to break away from stuff that works on other distros but is not so simple in Debian is outstanding (see, for example, the current unfinished work for GDM 3.2 in our SVN repo). In our case, to handle our GDM defaults, we even need changes to the underlying configuration system, dconf. This evidently takes some effort to do, and unfortunately our GDM expert has had little time for Debian lately, but we’re confident we’ll end up with a GDM in wheezy that is on par with Debian standards.

We are, as always, reachable at #debian-gnome in the OFTC IRC network. Have fun!

GNOME 3.4

Thu, 29 Mar 2012 23:50:00 +0000

The GNOME project released today GNOME 3.4, the second major update to the GNOME 3 platform. Congrats!

I know there’s lots of polish and improvements to some of the major rough edges in GNOME 3.2, but I think that of all changes in this release, Epiphany really stands out, as you can see in blog posts by Xan and Diego.

Work to bring GNOME 3.4 to Debian wheezy users has been underway for a few weeks already, and some bits and pieces have been hitting unstable since the tarballs were released a pair of days ago. We still need more base work to be done before some exciting components like GNOME Shell can hit our archive, and we want to fix as many FTBFS with GLib 2.32 bugs as possible before pushing it to unstable, but all in all, hopefully this time, shepherding a major GNOME release to Debian testing won’t be as painful as it was not so long ago. However, we have already identified some fun bits involving clutter, cogl and mutter in our initial analysis, but nothing that hopefully can’t be dealt with in a civilised way.

As always, if you think you can help us, we’re reachable at #debian-gnome at OFTC!

alsaconf

Thu, 23 Feb 2012 23:53:00 +0000

Removing alsaconf was one of the very few rewarding moments of these ten years of taking care of ALSA in Debian.

Not everyone agreed back then, and we still get some retaliation. :)

Date: Thu, 23 Feb 2012 02:59:31 +0100
From: <CENSORED>
To: jordi@debian.org
Subject: sabotage!

the removing of alsaconf without working(!) alternatives was (AND IS!) an
act of sabotage against millions of debian/alsa - users who needs stable
productive systems

you and all those proponents of removing this still needed alsaconf - program
will have to take the responsibility in front of an (us-) court for damages in
millions of dollars - amounts (lost man hours) all over the world

only a short while and we will have enough sponsors and witnesses around the
globe (and a very specialised, international labouring bureau of advocates) to
go to the court for prosecution.

we will not tolerate such an betray ("stable"? - do you believe, we're
fools??!!) against broad sections of the population and against the spirit of
free software!

it will be intresting to investigate, in whoms interests you've done so and
who the beneficiaries are ...

L.B.
conductor, publicist, whistleblower

FOSDEM 2012

Fri, 03 Feb 2012 13:05:00 +0000

In a few hours, I’ll be flying to Brussels with Ivan, for a new edition of FOSDEM, undoubtedly the best Free Software conference in Europe.

I’m looking forward to hang out with Debian, GNOME and #dudes people, as well as to explore some other quiet and cool spots in the city with our hosts Raül and Vir.

I’ll probably be around the CrossDistro and CrossDesktop rooms most of the time, but before that I’ll be at the Delirium café not long after landing in Brussels.

For someone who doesn’t enjoy cold weather that much, this is going to be a special edition… oh dear, -10℃, this is fucking crazy!

GNOME Shell 3.2 in wheezy: a retrospective

Tue, 31 Jan 2012 01:23:00 +0000

When you read this, GNOME Shell 3.2 will (hopefully!) have finally transitioned to Debian’s testing suite.

Planet GNOME readers might think Debian now has outdated versions of software even in their development versions, or the distribution’s development marches at glacial pace. Wheezy GNOME users will finally have a Shell that matches the rest of their GNOME components, something that works with the Shell extensions website and much less problems and limitations compared to 3.0.2.

The reality is that GNOME 3.2’s packaging was quite ready back when it was released in late September, but a number of not-so-desirable situations held GNOME Shell from transitioning to testing until today, four months later. So, what happened?

TL;DR: transitioning from GNOME 2 → GNOME 3 is not so easy if you want to keep testing in a sane state, and when you need to deal with dozens of indirectly related packages, for more than 10 architectures… but it shouldn’t take nearly a full year*, either…*

Let’s go back to the last months of 2010. Debian squeeze is in very deep freeze, and the release team and many Debian developers are focusing on squashing as many release critical bugs as they can, in order to make Debian 6.0 the great release it ended up being. The GNOME project has recently delayed the big launch of GNOME 3.0 again, until March 2011; Debian has already settled on GNOME 2.28 for its release, although it will end up cherry-picking many updates from the 2.30 release modules.

With most of the stabilization work being done, many Debian GNOME team members were at that time working on packaging very early versions of what would end up being GNOME 3.0 technology: GTK+3.0, GNOME Shell, Mutter… and some brave users even tried to use it via the experimental archive.

On February 6th, Debian 6.0 was released, and soon after, on April 6th, GNOME made a huge step forward with the much anticipated release of GNOME 3.0. At that time, Debian developers were busy breaking unstable as much as they could, as it’s tradition on the weeks following a major release, and the Debian GNOME team was able to start moving some GNOME 3.0 libraries (those which were parallel-installable with their GTK+2.0 versions) to unstable.

However, moving the bulk of GNOME 3.0 to unstable wasn’t so easy. When you start doing that, you need to be sure you’re ready to have all affected packages in a “transitionable” state as soon as possible, to minimise the chances of blocking transitions of unrelated packages via the dependencies they pick up with rebuilds. All the packages involved in a transition need to be ready to go in the same “testing run”, for all supported architectures. When you’re dealing with dozens of GNOME source packages at the same time, many of which introduce new libraries, or worse, introduce incompatible APIs that affect many more unrelated packages, things get hairy, and you need a plan.

So, Joss outlined what a sane approach to this monster transition could look like. The amount of work to do was what we call “fun” on #debian-gnome. In a nutshell, we had to deal with quite a few transitions, starting with having a newer version of libnotify in unstable, and a pre-requisite for that was making sure all the packages using libnotify1 were ready to use the source-incompatible libnotify4, and this meant preparing patches and NMUs for many of our packages, as well as many others not under our control.

Before starting a controlled transition like this one, we had to get an ACK from the release team, who was busy enough handling other huge transitions like Perl 5.12, so by the time we got our own slot, we were well into Summer.

With libnotify done in August, it was time to get our hands dirty with more exciting stuff, like getting Nautilus in testing. This meant bumping a soname and requiring all packages providing Nautilus extensions to migrate to GTK+3.0, or drop the extension entirely, as you can’t mix GTK+2.0 and GTK+3.0 symbols in the same process. However, in GNOME 3.0, automounting code had moved from Nautilus to gnome-settings-daemon, so in order to not break filesystem automounting in testing for an unreasonable amount of time, both Nautilus and g-s-d needed to go in at the same time. The fun thing is that g-s-d dragged glib2.0, gvfs, gnome-control-center, gdm3, gnome-media, gnome-session and gnome-panel into the equation, so this transition needed extra planning and a lot more work than initially expected: migrating all nautilus extensions, plus ensuring all Panel applets had migrated to GTK+3.0 and the new libpanel-applet-4 interface. In short, this was the monster transition we were trying to avoid.

By the time all this mess was sorted out, GNOME 3.2 had been released, and for what users said, it was a lot better than 3.0. We still had no more than a few bits and pieces of 3.0 in testing, and we were working hard to get 3.0 in wheezy. With all the excitement around 3.2, at times it was difficult to explain outsiders why we were beating a dead 3.0 horse… Going back to our huge transition, it was just a matter of time before all the packages would be built and be ready to enter, on the same run, in testing.

A few weeks later, in early November and after several rounds of mass-bug-filings, fixing unrelated FTBFS, many NMUs, package removal requests and dealing with any possible problem that could block our transition, everything seemed to be set, and our release team magicians had everything in place for the big magic to happen. However, our first clash with the rest of Debian happened a few hours before our victory, in the form of an unannounced ruby-gnome2 upload which resetted the count for everyone. It was fun to see the release team trying all sorts of black magic in an attempt to mitigate the damage. Fortunately, after a few tries they managed to fool britney (the script that handles package transitions from unstable to testing) somehow, and the hardest part of the job was done with just one day of delay.

At last, the core of GNOME 3 was in testing, and testing users found soon after. The rest of the week saw a cascade of hate posts against GNOME 3 in Planet Debian, and personally I didn’t find that especially motivating to keep on working on the rest of GNOME bits. With experimental clear of GNOME 3.0 stuff, we finally were able to focus on packaging whatever GNOME 3.2 components were not already done, and preparing for what should be a plain simple transition of GNOME 3.0 to 3.2.

After our share of wait for a transition slot, as Perl 5.14, ICU and OpenSSL were in the line before us, and after dealing with a minor tracker 0.12 transition, we were ready for our next episode: evolution-data-server.

At first sight, we thought this would be a lot easier, but it still got a bit hairy due to evo-data-server massive soname bumps. We were given our slot just before Christmas, after a few weeks of wait for others to finish their migration rounds, and most of the pack entered wheezy a few days before the new year.

No rejoicing, though, as GNOME Shell 3.2 didn’t make it. First, we discovered it was FTBFS on kFreeBSD architectures, as NetworkManager had been promoted from optional to required, for apparently no good reason, leaving the BSD world in the cold, including our exotic GNU/kFreeBSD architectures. Now, let’s clarify that I’m a supporter of the Debian kFreeBSD architectures and was really happy to see it accepted as a technology preview in squeeze. However, as you know, GNOME Shell currently requires hardware acceleration to run, a requirement hardly met in kFreeBSD, unless you’re using a DRI1 X driver. We seriously doubted anyone had ever ran a GNOME 3 session on kfreebsd-*. However, if it didn’t build, it was a blocker bug for GNOME Shell. We considered creating different meta-packages for kFreeBSD architectures, to conclude it’d be a mess, so our awesome Michael Biebl ended up cooking up a patch that restored the ability to build the Shell without NetworkManager support.

With this out of our way, we just needed to upload Michael’s fix and watch the buildds do their part of the job. Or maybe not?

Enter Iceweasel 9.

In parallel, and with incredible bad timing, Iceweasel 9.0 was uploaded to Debian the very same day it was released by Mozilla. Again, it greeted us with a nasty surprise: yet another mozjs API change, which made gjs FTBFS, which meant our kFreeBSD fixes would be unusable until someone who knew Gjs’ internals well enough bit the bullet and worked around the new API changes. Again, Michael Biebl tried to be our saviour, but unfortunately wasn’t able to fix all the problems, so we tried to focus on plan B.

Mozilla had released a fork of the mozjs that is included in Firefox, so that embedders would have a bit less of a hard time with these recurrent API changes. This was based on Firefox 4, and was already being packaged by Ubuntu. Gjs would build using this older version just fine, so we just needed to get it in Debian as soon as possible. We just needed to find a sucke^Wvolunteer that would be inclined to maintain the beast. Only after a few weeks we managed to get Chris Coulson, the Ubuntu packager, to maintain the package directly through the Debian archive via package syncs. However, his package had only been auto-compiled in the three Ubuntu architectures, that is amd64, armel and i386. It’s late January 2012, and we’ve been fighting this war for 10 months.

After getting some help from Michael to get the new package in shape for Debian standards, we were excited to sponsor it for Chris. Duh, after a few days in the NEW fridge, it was rejected by the ftp-masters. The license statement was missing quite a few details, so I went ahead and sacrificed a few hours of my copious free time to get this sorted out. A few days later, mozjs was accepted, but the result was horrible. It was very red. mozjs didn’t build on half of our targets.

Mike Hommey was quick to file a bug and point us to the most obvious fuckups. As he had dealt with this in the past as the Iceweasel maintainer, all of these issues were fixed and patches were ready to be applied verbatim or with minimal changes to our sources. With mozjs finally built successfully (although with severe problems on ia64), we were finally able to rebuild Gjs against it, upload GNOME Shell with our kFreeBSD fixes and wait until today for this mess to be over. Whew.

I can’t say I’ve enjoyed all the stages of this ride. Some bumps on the road were clearly there to test our patience, but it has helped me get back in touch with non-leaf GNOME packaging, which was all I was doing for a while due to being super-busy lately with studies. It also reminds me of the privilege of working side by side with some awesome people, not only Joss, Michael, Sjoerd, Laurent or Gustavo, to name just a few Debian GNOME team members, but also the receptive release team members like Julien or Cyril, and NEW-processing record-breaking ftp-master Luca. Without them, we might be trying to figure out the Nautilus transition since last Summer.

We really hope GNOME 3.4 will be a piece of cake compared to this. ;)

Installing GNOME 3 in Debian

Thu, 29 Sep 2011 01:46:00 +0000

The following is a quick HOWTO for the brave Debian users who want to upgrade to GNOME 3. Assuming you have an up to date system running sid, and experimental listed in your APT sources, perform the following complicated steps to end up having a functional GNOME 3 desktop:

apt-get install -t experimental gnome

Thanks go to Joss for putting together new GNOME 3 meta-packages, and the rest of the Debian GNOME people for months of hard planning and packaging work, and painful testing transition handling.

Before you ask, yeah, not all of GNOME 3.x is in unstable yet, but will soon be, as precedent transitions start clearing the way. And yeah, GNOME 3.2 will come just after the two remaining package sets enter testing. To compensate, you’ll find that you have some GNOME leaf packages pending an upgrade to 3.2.0-1 while you read this.

Not going to DebConf 11

Wed, 13 Jul 2011 13:47:00 +0000

3 months ago, I was positive I would be attending DebConf 11 in Banja Luka, but as the time to buy tickets and plan the trip came closer, I began to realise I don’t have lots and lots of vacation, and I probably prefer spending them doing something that absolutely rocks my world. I’ve always enjoyed the Debian conferences when I’ve been lucky to be there, but last year’s experience in the Pyrenees was nothing a DebConf can compare to, and I’ve decided to spend time seeking similar experiences this summer.

With much regret, because I love meeting the wonderful people that make up Debian and DebConfs, I have to say that after all and once again, I won’t make it.

GNOME 3.0

Thu, 07 Apr 2011 23:14:00 +0000

Yesterday one of my free software halves was very, very happy, because after a lot of work, GNOME 3 was released!

I’ve been following GNOME 3.0’s development since Debian got the first GNOME Shell snapshots uploaded to experimental. While my first experience, on an old, 2 or 3 generations behind Athlon 800MHz with 512MB of RAM was horrid due to the lack of features (it wasn’t even an alpha!) and the incredible slowness due to the crappy Radeon 9200, I’ve seen it evolve to the gem that was released yesterday.

I haven’t been so excited about GNOME since GTK+ and GNOME 2.0 were released after their eternal development cycle, and was happy to see how positive the atmosphere in #gnome-hackers was last night when vuntz sent the email and everyone was able to relax after a very long sprint of hard work.

Congratulations everyone, because not only this a great, solid release, but it’s also a brave one. Change does not come without resistance, but I am very sure the path GNOME opened last night has a bright and innovative future. I will be delighted to walk this path to enjoy it!

FOSDEM 2011

Thu, 03 Feb 2011 22:45:00 +0000

When I returned from the first FOSDEM edition I attended, I wrote that I had liked and enjoyed that weekend in Brussels so much, that this conference had probably become a “must”.

It seems I was right. Five years later, I’m delighted to say

I’m happy to meet so many friends from the Debian, GNOME or GNU projects, and enjoy the kindness of our hosts in Brussels, Raül and Virginia. And I’m looking forward to the awesome beer, the excellent talks and discussions, and that unique FOSDEM atmosphere that makes this so special. This year, FOSDEM has the bonus of being able to enjoy the Debian “squeeze” 6.0 release as it happens, with many of the people who made it possible, and celebrate this on Saturday night. See you there!

New project to discuss

Fri, 14 Jan 2011 20:19:00 +0000

Reading Scott’s recent announcement on his move to Google was both surprising and a pleasure. Surprising, because it’ll take time to stop associating his name to Ubuntu, Canonical, and the nice experiences I had while I worked with them. A pleasure, because his blog post was full of reminiscences of the very early days of a project that ended up being way more successful in just a few years than probably anyone in the Oxford conference could imagine. Scott, best of luck for this new adventure!

Scott’s write-up includes a sentence that made me remember I had been wanting to write a blog post related to all of this, but was pending Mark Shuttleworth’s permission for posting:

Ok, Mark wasn’t really a Nigerian 419 scammer, but some people did discard his e-mail as spam!

― Scott James Remnant

Many know the story of how I ended not being part of the “Super-Secret-Debian-Startup” Scott mentions. I even wrote about it in a blog post, 3 years ago:

[…] nothing beats the next email which sat for some dramatic 6 months in my messy inbox until I found out in the worst of the possible scenarios. Let’s go back to late February, 2004, when I had no job, and I didn’t have a clue on what to do with my life.
From: Mark Shuttleworth <mark@hbd.com>
Subject: New project to discuss
To: Jordi Mallach <jordi@debian.org>
Date: Sun, 29 Feb 2004 18:33:51 +0000

[...]
I'm hiring a team of debian developers to work full time on a new
distribution based on Debian. We're making internationalisation a prime
focus, together with Python and regular release management. I've discussed
it with a number of Debian leaders and they're all very positive about it.
[...]
I’m not sure if I totally missed it as it came in, or I skimmed through it and thought “WTF?! Dude on crack” or I just forgot “I need to reply to this email”, but I’d swear it was the former. Not long after, no-name-yet.com popped up, the rumours started spreading around Debian channels. Luckily, I got a job at LliureX two months later, where I worked during the following 2½ years, but that’s another story. I guess it was July or so when Ubuntu was made public, and Mark and his secret team organised a conference (blog entries [1] [2] [3] [4] [5]), just before the Warty release, and I was invited to it, for the same reasons I got that email.

During that conference, probably because Mark sent me some email and I applied a filter to get to it, I found the lost email, and felt like digging a hole to hide for a LONG while. I couldn’t believe the incredible opportunity I had missed. I went to Mark and said “hey, you’re not going to believe this”, and he did look quite surprised about someone being such an idiot.

I wonder if I should reply to his email today…

When the usual suspects in the secret Spanish Debian Cabal channel read this blog post, they decided Mark deserved a reply, even if it would hit his inbox more than three and a half years late. :)

With great care, we crafted an email that would look genuinely stupid in late 2007, but just arrogant and idiotic in 2004, when “Ubuntu” was just an African word, and the GNU/Linux distribution landscape was quickly evolving ―at the time, Gentoo Linux had the “posh distribution” crown, that Debian had held for quite a few years. I even took enough care to forge the X-Operating-System and User-Agent headers so they matched whatever was current in Debian in February 2004, and of course, top-posting seemed most appropriate.

So Mark woke up that Monday, fired up his email client, and got… this:

Date: Mon, 1 Mar 2004 09:47:55 +0100
From: Jordi Mallach <jordi@sindominio.net>
To: Mark Shuttleworth <mark@hbd.com>
Subject: Re: New project to discuss
Organization: SinDominio
X-Operating-System: Debian GNU/Linux sid (Linux 2.6.3 i686)
User-Agent: Mutt/1.5.5.1+cvs20040105i

Hi Mark,

Thanks for your email. I nearly deleted this e-mail because for some
reason I thought it was targetted spam.

Your project looks very interesting, almost like a dream come true.
However, I feel a bit uneasy about your proposal. Something just doesn't
fit.

Why would someone start a company to work on /yet another/ Debian
derivative? Have you heard about Progeny's sad story? I think it's a
great example to show that Debian users don't want Debian-based distros,
they want people to work on the "real thing". Besides, I don't think
there's much more place for successful commercial distros, with Red Hat
and SuSE having well-established niches in the US and Europe.

Also, why focus on Debian specifically, Why not, for example, Gentoo,
which has a lot of buzz these days, and looks poised to be the next big
distribution?

To be honest, I think only a few people have the stamina or financial
stability to undertake a project like this, so I'd like to know
a bit more about you, and details on how you plan to sustain the
expenses.

Those are the main issues that worry me about your project. Other than
that, I would be interested in taking part in it, as I'm currently
unemployed and working on something Debian-based would be just too good
to miss.

You can reach me at +34 123 45 67 89, or if you feel like flying people
around Europe, I probably can be in the UK whenever it fits you.

Thanks, and hoping to hear from you again,
Jordi

On Sun, Feb 29, 2004 at 06:33:51PM +0000, Mark Shuttleworth wrote:
> Hi Jordi
>
> We haven't met, but both Jeff Waugh and Martin Michelmayr recommended that
> I get in touch with you in connection with a new project that I'm starting.
>
> I'm hiring a team of debian developers to work full time on a new
> distribution based on Debian. We're making internationalisation a prime
> focus, together with Python and regular release management. I've discussed
> it with a number of Debian leaders and they're all very positive about it.
>
> Would you be available to discuss it by telephone? I'm in the UK, so we
> could probably find a good timezoine easily enough ;-) Let me knof if
> you're keen to discuss it, when and what number to call.
>
> Cheers,
> Mark
>
> --
> Try Debian GNU/Linux. Software freedom for the bold, at www.debian.org
> http://www.markshuttleworth.com/

As you can imagine, his reaction was immediate:

Date: Mon, 22 Oct 2007 11:13:54 +0100
From: Mark Shuttleworth <mark@hbd.com>
To: Jordi Mallach <jordi@sindominio.net>
Subject: Re: New project to discuss

Jordi! I just got this now! Did you recently flush an old mail queue?

With thanks to all the Spanish Cabal members who were involved!

Recipe Manager meets arròs a banda

Mon, 25 Oct 2010 00:12:00 +0000

Two weeks ago, nekohayo posted a blog entry on Recipe Manager, a (you guessed it) cooking recipe manager for GNOME. Looking good, I fetched the bzr tree from Launchpad and played a bit with it, and soon discovered it had no internationalisation support.

I’ve tried to add i18n properly, but I’ve not had enough time to do it. Before tackling that, the authors need to give it some bootstrapping love so the app can actually install, look for its files in /usr/share, etc.

My fugly, unpostable current patch does allow for a preview of how Recipe Manager will teach the world about the best rice dish ever, arròs a banda. Yum!

Recipe Manager, showing off the zenith of Valencian culture

GNOME 2.32

Thu, 30 Sep 2010 23:49:00 +0000

Once again, the GNOME project has released a major release on time, to the day. Congrats! While it doesn’t feel like a major release, due to the pushing back of GNOME 3.0 another 6 months in the middle of the cycle and the limited changes included, I believe it’ll be a good one because it just adds on top of the really solid GNOME 2.30.

GNOME 2.32 is out a bit too late for Debian squeeze, but the Debian GNOME team has a plan™ to incorporate new 2.32 versions for modules which don’t include big, intrussive changes like migrations to dconf, or any other dependency on the new versions of GTK or GLib. The result is that Debian 6.0 will ship with most of GNOME 2.30, plus some cherrypicked new versions of 2.32 modules.

GNOME 2.30

Wed, 31 Mar 2010 23:53:00 +0000

Congratulations to everyone involved in what looks like a very good GNOME release!

Interesting times are now ahead for the GNOME project, as on the plate is now a big release like 3.0. That will mean a lot of changes to the desktop we’ve got used to in the last decade, and I hope it ends up being successful, innovative and useful.

Debian has packages for GNOME Shell, and a special gnome3-session which starts Mutter + Shell. I experimented with it last week at my work place, and had mixed feelings with the current status.

I’m not a big fan of hard dependencies on Direct Rendering. My main computer is an Athlon 800MHz. Compiz crawls on it, and sadly Mutter is basically unusable on it. At the office, I have P4-based system with 1GB of RAM, which runs GNOME 2.28 OK. When I switched to the GNOME 3 session, it showed that it’s getting old. I also experienced X crashes and kernel oopses, apparently a classic for ATI users using a composited window manager. This being said, I consider myself lucky because both systems have ATI cards and can do DRI using free software. If I was forced to use nVidia non-free drivers, it’d probably mean I’d stick with the Panel until that wasn’t an option at all.

I am aware we’ll see improvements both in Xorg/kernel and GNOME before GNOME 3.0 is released next Autumn, and have high hopes for a release that is accepted by our users really fast (avoiding a KDE 4.0 situation). GNOME hackers have done good stuff for ages, and 3.0 will be a new example!

Tinyproxy 1.8

Sun, 28 Feb 2010 23:44:00 +0000

A while ago, I was asked to recompile Tinyproxy to enable transparent proxying support, which was not being compiled in etch’s Debian package. As it tends to happen, once I got the source and looked into doing a quick rebuild with --enable-transparent-proxy, I noticed the package was in such a bad shape, that I couldn’t just leave it like that, so I found myself doing a few more changes, which mostly involved updating the packaging so it didn’t suck a lot, and splitting the Debian patches so things could be sent upstream or dropped when new versions appeared.

However, even if Ed had asked me to go ahead and take over the package, this was meant to be a one-day effort, and soon I had forgotten about Tinyproxy, except for the ocassional bug mail getting through the PTS. It also didn’t help that Tinyproxy had been pretty much dead upstream for years.

So lately, a few bug reports were reporting a ∗gasp∗ new major Tinyproxy release, after 7 years of basically nothing. OMG, what do I see, there’s a Git repo! And an upstream Bugzilla! Somehow, feeling I owed Ed a reply to his unanswered request, I went ahead and tagged tinyproxy 1.6.3-3.2 in collab-maint, and started working on the new version. Adding myself to Uploaders, and getting rid of the “make no unnecessary changes” vetto, I rewrote most of the packaging. And for a change, I looked for and found a #tinyproxy channel on IRC and told muks and obnox that the days of Tinyproxy’s stay in the Debian/Ubuntu limbo were over.

They were happy to get a few bugs and patches forwareded upstream, and asked me why all of this hadn’t happened before. Pitty is that a few longstanding issues were well known in Debian but not so obvious for the new upstream maintainers, and are present in 1.8.0. Hopefully all will be dealt with in 1.8.1 or the next major version. The lesson is: if you work on an apparently abandoned package, after cleaning the mess in your NMU, try to spend 15 more minutes trying to contact upstream (if available), pointing them at the patch tracker and our list of bugs: chances are many are still useful. Also, contact the Debian maintainer, and if they ask you to take over, at least post a RFA so someone else can.

If you’re a Tinyproxy user, I’d be happy to hear if the current package in Debian unstable works for you. If you were having weird issues with 1.6.x, chances are 1.8 will fix them. The package can be installed on stable with no extra dependencies, so if you’re feeling adventurous, go ahead and upgrade.

Ten years as a Debian Maintainer

Tue, 24 Nov 2009 23:47:00 +0000

On the 24th of November of 1999, the Debian ftpmasters processed the NEW package wmbiff, which got installed in the potato distribution. This sponsored upload by Fernando Sánchez was the first of my packages to hit the official Debian archive, thus officially making me a Debian maintainer. So, in short, today is my tenth anniversary as a Debian contributor!

I actually started a few days before, and soon after that upload, many other ITPs and uploads followed. I will always be thankful to fer for his patience with my upload sponsoring until I became a Debian developer with full rights and was able to upload myself.

During these years, I’ve been involved in many teams and different tasks, with my activity and dedication probably peaking around 2001 or 2002, when I apparently was doing a crazy amount of different stuff. I started doing plain packaging work of software packages, some of which also have come a long way (thanks for that, Chris!), but soon started to contribute in other Debian tasks. I think it’s safe to say that the task that has ended up having more impact in the people that surround me was bootstrapping the Debian Catalan community and starting the Catalan translation of Debian’s website, which soon after triggered the creation of a formal Debian Catalan translation project.

I’ve also spent a lot of time giving back to the NM team which helped me get a Debian account through the still experimental new New Maintainer process, and the QA team helping as I could with the never ending release cycles of potato and woody.

At some point I got engaged in the GNOME packaging tasks and the creation of the Debian GNOME team, and picked up the Catalan translation of GNOME 1.5.x releases, which eventually opened me the doors of Softcatalà, a Catalan non-profit devoted to the promotion of the Catalan language in technology.

I’ve believed in Debian’s values since my classmate Ulisses Alonso prodded me to install Debian on my desktop back in 1997. Even if getting X up and running on bo was a real pain in the ass, knowing that the system I was running had all been written by people driven by altruism was enlightening; months later it was time to give back.

Of course, I’ve not been able to keep my motivation or output as high as I’d like. Debian as a collective has sometimes taken some decisions which were not so easy to understand from my point of view. The outcome of the non-free votes was a bit appalling, and having debian-devel becoming more and more a battleground instead of a civilised mailing list certainly did not help at some point (unsubscribing from it made my life a lot simpler!). Joining a triathlon club, having a girlfriend and suddenly rediscovering my neglected social life didn’t help either. The result is that my dedication has been wanning noticeably since 2005 or so, but I still do my best to keep up with most of duties, even if I’m aware I’m clearly neglecting a few of them.

I am very proud of having been a part of an incredible project like Debian, and hope to be around for at least ten more years. Not only because I love and believe in Free Software; thanks to my involvement, I’ve been able to work on Debian-related jobs for all of my professional career, but above all I’ve been very lucky to make lots of real friends.

Today’s has been a nice day full of remembering and mailbox digging. Thank you, Debian!

DebConf 9

Thu, 23 Jul 2009 09:13:00 +0000

It’s taken me way too long to scribble these few lines, but I’m happy to say that in about one hour, I’ll be driving to Cáceres with Sergio. After seven hours or so, we should appear somewhere in Extremadura.

My priorities for this week are 1) having lots of fun with people I haven’t seen in ages, 2) catching up with all the Debian work I have neglected lately, be it packaging or l10n, 3) enjoying Cáceres and Extremadura’s culture, as it’s the first time I go past Madrid, and this is pretty much uncharted territory for me, and 4) doing some kind of exercise, which means letting bubulle kick my ass, and finding a decent swimming pool around the venue.

See you tonight!

An update on GRUB2

Sat, 28 Mar 2009 14:54:00 +0000

Some time ago I wrote about the the state of GRUB2 and a milestone on getting it boot my Apple PowerBook G4 without manual intervention. More than a year later, GRUB2 has changed and improved a lot, as the community keeps growing and patches and ideas are continously being posted.

Some months and commits after my previous post, GRUB broke again on Apple OpenFirmware and I’d get dropped to OF console, the amount of commits since the last known working version and the current SVN was quite big, and although I was able to narrow it to a few suspicious changes, I had no time to bisect it properly, and sadly I had to go back to yaboot for a while.

But procrastinating sometimes helps, and when I should have been writing and studying, on December I gave GRUB a new try on my laptop to see if a few important changes to memory allocation would have changed anything. And it did! So after fighting quite a few problems, I was able to report partial success to grub-devel.

Again, getting GRUB installed correctly was a bit challenging and needed some hackery, due to incorrectly generated device.map, and the linux module mysteriously not getting loaded. Luckily, Michel Dänzer found out that this was due to a bug in sort ordering in the HFS module, which broke the lookup of files with underscores like _linux.mod, and for which he posted a possible fix by taking Linux’s table of character ordering, which is a blob of hex values.

GRUB developers didn’t seem too happy about applying the patch: they argument that a blob like that should be well documented or written in some other more readable way, and there’s a possible problem with the mix of Linux GPLv2 and GRUB GPLv3+ codebases, if a table of data like what Michel posted is actually copyrightable. The discussion ended up dying and nothing was done… until Pavel Roskin picked it up weeks later and posted a new patch, based on hfsutils GPLv2+ code, which addressed these issues. The new patch seems to have a few issues, which makes it fail as before, but hopefully it’ll be fixed soon.

Additionally, I wasn’t able to boot using UUIDs as the search commands fails to detect the correct boot device on my system (but not on Michel’s), so I had to disable that in /etc/default/grub.

To workaround the linux module loading bug while the patch is fixed, I just added this ugly hack to /etc/grub.d/09_local_prelinux:

#! /bin/sh -e

# Work-around for bugs in the hfs module which makes the load of
# linux.mod fail.

cat << EOF
insmod (hd,3)/usr/lib/grub/powerpc-ieee1275/_linux.mod
insmod linux
EOF

This is enough to get the initrd and linux commands available. However, update-grub will still add search commands to your menu entries even if you disabled UUID support; I can’t understand why, but I know it breaks on my PowerBook due to some OF rarety. Just removing the line from the menu entry will leave me with a working config that boots without any manual editing at GRUB prompt.

The latest GRUB snapshot in Debian fixes the device.map issue, but adds one last issue: update-grub will fail due to some gfxterm detection code, a workaround is to replace an exit 1 with exit 0 when this happens in /etc/grub.d/00_header.

On the “weird architectures” front, it’s worth noting that this month Dave Miller popped up on the list and started posting patches to fix the rotten SPARC port, and I think it’s safe to assume that it’ll be on an usable state really soon. Impressive!

GNOME 2.24 in Debian unstable, and the road ahead

Wed, 25 Mar 2009 00:32:00 +0000

GNOME 2.26 was released last week, and I couldn’t help adding myself to the long list of celebrating posts in Planet GNOME. Looking at the release notes, it looks like this release adds a good number of very visible features, and also keeps improving on ongoing transitions like gvfs.

The Debian GNOME team is obviously not ignoring this fact and started to work very hard on updating GNOME for squeeze as soon as the lenny freeze was over.

First, the new versions of GLib and GTK+ were uploaded to unstable, and managed to transition to testing very easily. The rest of GNOME 2.24 bits, which had been patiently waiting on experimental for months, has been uploaded with care not to disrupt any of the many transitions the Debian release team is currently dealing with. You can have a quick glance at how things are going in our 2.24 status page, but the summary is that most of GNOME 2.24 is in unstable, with a few notable exceptions which are held back by ongoing testing transitions. Namedly, evolution-data-server is trying to trickle into testing, which is in turn holding the final bits: gnome-panel, nautilus and related packages, but we think this will be over soon.

As soon as GNOME 2.24 is safe in squeeze, we’ll immediately turn our focus to the new GNOME 2.26 release. Our initial plan is to package the trivial bits and leaf packages which can’t break stuff for unstable, and herd the more complex modules via experimental, to avoid breaking unstable at all. There are some exceptions; we plan to keep gnome-session 2.22 in unstable/testing until 2.26.1 is released to avoid getting a broken session saving in Debian.

People might wonder why we insist on hitting what would seem a dead horse by first dealing with 2.24 and not 2.26 directly. The main reason is that these packages had been ready for a long time, and were in good shape to transition to testing quickly and with little pain. Preparing 2.26 directly would mean throwing away a lot of hours of packaging and polishing effort, and it’s not like we’re releasing squeeze any time soon anyway.

Enjoy the hopefully not too bumpy road to 2.26!

Stepping down as the GNOME Catalan translations coordinator

Tue, 24 Mar 2009 19:21:00 +0000

As of this morning, Damned Lies finally reflects what has been the de-facto reality for at least four major GNOME releases. I started to invest a lot of time on translating GNOME to Catalan in the middle of the long 1.5 journey towards GNOME 2.0. That was a long time ago, and somehow was the way I ended being abduced by Softcatalà to eventually work with them on the localisation of some other projects.

However, I’ve been watching how my free time and motivation has been slowly shrinking, until the point I was no longer doing some of the stuff I was expected to do, or was doing it badly and late. Luckily, Softcatalà’s GNOME team, a model for our organisation, has been able to smoothly replace heavily contributing members with a constant stream of new blood. In my case, I first stopped having that many modules assigned, then focused on coordination and finally stopped doing even that.

Gil Forcada has filled the gap perfectly and has been the main lead of effort for a pair of years. Passing the baton was long overdue; I think GNOME is lucky to count on Gil’s amazing drive and motivation. Gil, congrats on earning yet another marronet! ;)

FOSDEM 2009

Sun, 18 Jan 2009 16:07:00 +0000

I’m glad to announce that I’ll be again in Brussels for this year’s FOSDEM. Ivan and I will fly from Zaragoza (!) on Friday, just on time for the beer event, and come back on Monday evening. I know azeem would have not been happy otherwise!

jabberd2 2.2.4 packages for etch

Fri, 31 Oct 2008 19:43:00 +0000

Last weekend I created a set of backports of jabberd and its unfulfilled dependencies for etch, for use in my jabber server which has been suffering s2s problems for way too long.

The packages are a bit quick and dirty, but good enough for my personal use (a known issue is the lack of shlibs bump in gsasl) and are available from this non-apt-get enabled repository. If I can help the XMPP team in any way to help these packages get into unstable or experimental, I’m totally willing to help.

GNOME-Mud 0.11

Fri, 25 Jul 2008 20:38:00 +0000

GNOME-Mud 0.11 was released yesterday. This was probably something unexpected to those who follow the mailing list, as it’s the first release in over three years.

Back in 2006, Les Harris started contributing to the project and started a major rewrite of the program. Things looked very promising, with the program being ported to newer GNOME technologies and standards and being basically rewritten from ground up. However, Les got hit by Real Life™ and being the project’s only real hacker, development basically stopped for nearly two years. On June, I was tempted to remove my irssi subscription to #gnome-mud; all I did was idling or telling people who popped by that nothing was being done and that wouldn’t change unless someone rolled up their sleeves and finished up the nearly ready 0.11 release.

A few days after considering declaring GNOME-Mud dead, Les joined IRC after more than a year of no contact, recovered his GNOME account password and started to commit the missing bits at an awesome pace.

A few weeks later, 0.11 was done, with even more features than originally planned (support for more advanced MUD protocols like MSP or ZMP, for example) and I finally found the time to make a tarball and publish it. Les has lots of plans for the next release, and I hope my old wish of seeing GNOME-Mud becoming a MUD client that is comparable to the classic zMud will soon be a lot closer. The foundation set by this release certainly will make it easier to accomplish.

As always, if you want to contribute, we’ll be happy to help you out on #gnome-mud at GIMPnet, or in gnome-mud-list@gnome.org.

Interview in El País on Debian's OpenSSL incident

Tue, 03 Jun 2008 17:11:00 +0000

Last week’s edition of Ciberpaís included a lengthy article which tried to explain Debian’s and Ubuntu’s OpenSSL problem to unexperienced computer users, it’s impact, what should people do and what happens next.

Mercè Molist sent in a few questions for me to answer, a small part of which were used in the article. While I don’t like a few bits of the article that much, I tried my best to make it clear that Debian is not a bunch of clueless and careless Free Software enthusiasts. The treatment that the incident had in some well known Spanish security-related websites was in my opinion deplorable, so I want to thank Mercè for the opportunity to clarify some of the Debian bashing.

I expect the full interview will be published either here or at Mercè’s website in the following days.

Filtering Planet Debian authors

Thu, 24 Apr 2008 16:03:00 +0000

Several people have been discussing what material is appropriate or not for feeds syndicated by Planet Debian. It’s basically the same discussion that also pops up every now and then in any big planet like GNOME’s, KDE’s, Ubuntu’s or ours, with some people advocating for Free Software or techie stuff content only, and an apparent majority liking and defending that people write about their latest Debian hack, but also how wonderful their vacation in Paris were, or how their favourite politician did this or that.

For some time now, Planet Debian has a small new feature that might have gone unnoticed by many, and could help some readers get rid of undesired content from the post listings.

Steve Kemp added a cookie-based per-author filtering system to Planet a few weeks ago. Next to each author name you’ll see a “−” link which can be used to collapse all entries by the author. This setting will be saved in a browser cookie, and can be reverted by clicking on the “+” link next to the collapsed author. To expand all hidden posts, use the “Show all” link in the Planet’s right column above the subscription list.

So, if reading about baby Jesus annoys you, just click on “−” and be happy.

Interview in El País

Thu, 27 Mar 2008 17:00:00 +0000

Today’s edition of El País, the most read Spanish newspaper, celebrates the 10^th anniversary of it’s weekly technology section Ciberpaís with a special edition which takes a look back at the last 10 years of computing, and also looks forward to what the future will bring us.

Mercè Molist interviewed Carlos Atarés, my mate at Softcatalà Jordi Mas and myself, on what happened during the last 10 years of Free Software and where we are heading. The paper edition features a *gasp* half page picture of me laying on the grass, but is otherwise identical to the online version.

I need to add, this feels a bit strange. :) It’s the first time I see myself refered to as just “Mallach”, but I realise I’m getting old…

Time for GRUB2?

Sat, 09 Feb 2008 17:53:00 +0000

My Apple Powerbook 5,4 just booted for the first time using GRUB, with no manual intervention, from Apple chime to GDM prompt. This is a great milestone for GRUB2 on powerpc-ieee1275 and OpenFirmware, as until now, multiple problems in the loader would drop you to OF console straight away, although other PowerPC hardware with other firmware implementations did manage to work.

Recent fixes by Pavel in the core and some other minor fixes for the userland utils have taken grub2 to the point where it is usable on most PowerPC hardware. On Apple, the only minor issue remaining is grub-probe insisting on (hd) not being a valid device name, so for now I have to trick it into believing it’s really (hd1).

In parallel, many other GRUB2 improvements haven’t stopped hitting CVS in the last months, which have seen how new contributors joined grub-devel and helped GRUB2 get the great momentum it’s enjoying right now. Vesa, Robert and Bean have been really active lately, and have fixed long standing issues or written a lot of new code. One of the features GRUB2 acquired recently was image loading for background images. Much more powerful than the implementation in GRUB Legacy, GRUB2 can now read images in multiple formats, can handle up to 24bit colour and render a menu in arbitrary resolutions. The menu can now show UTF-8, and the Debian package will configure a pretty theme that matches the rest of the system if desktop-base is installed:

GRUB2 speaking UTF-8 Catalan

Although I’m not sure if GRUB2 is completely up-to-par with GRUB Legacy on i386/amd64, it seems the tricky bits, like video, LVM, RAID and the standard filesystems are supported and working. What GRUB2 needs now, in order to finally replace the aging and upstream-lacking GRUB Legacy you probably have installed, is massive testing. Debian has traditionally been a testbed for GRUB Legacy patches, and is also the platform where GRUB2 is being more widely tested. Having GRUB2 included in lenny’s debian-installer would be a great step forward, and by the looks, I think we’re well on time to manage this.

Replacing GRUB Legacy with GRUB2 is trivial. On PCs, just install the grub-pc package. You’ll be offered to keep GRUB Legacy, but with an added menu entry to chainload GRUB2. If you’re worried that GRUB2 might fail on your hardware, accept this, and try to load GRUB2 from GRUB. If it works, you then know you can get rid of GRUB Legacy completely and keep GRUB2 in the MBR.

On PowerPC-based Macs, you’ll have to work around the small issue I mentioned above. Install the grub-ieee1275 package. You also need a very recent powerpc-ibm-utils package, which was just uploaded to unstable.

Mount your bootstrap partition, probably /dev/hda2 in /boot/grub, and generate a device.map file with grub-mkdevicemap. Check the contents. If your first device name lacks a drive number such as (hd), it’s probably correct, although this will make things fail later. Change it to (hd0) for now. As grub-install relies on grub-probe, you’ll have to generate your grub image by hand.

Copy all .mod files in /usr/lib/grub/powerpc-ieee1275 to your bootstrap partition, and generate a core.img:

root@powerpc:/boot/grub# grub-mkimage -d . -o /boot/grub/core.img *.mod
root@powerpc:/boot/grub# update-grub
root@powerpc:/boot/grub# nvsetenv boot-device hd:2,core.img

The generated grub.cfg will have references to (hd0,X), which you’ll have to correct back to (hd,X) if necessary for your OpenFirmware. After this, you are probably ready to reboot, cross two fingers and get a warm “Welcome to GNU GRUB!” message at boot, which will then be followed by a standard GRUB menu, but on your nice PowerPC box. Unfortunately, the eye candy in the screenshot above isn’t available yet in this platform, as it lacks VESA. Does someone in the audience want to contribute a video driver for powerpc? :)

FOSDEM 2008

Thu, 10 Jan 2008 14:52:00 +0000

As part of a sad trend that pulls me away from my healthy travel habits, I just booked plane tickets to Brussels for February 22nd. Note this is 1.5 months of planning ahead. madduck, your turn!

Additionally, two weeks ago I got tickets for a one week long trip around parts of Germany at the end of the month. The travel plan is totally undefined, so I don’t know what cities I’ll be visiting yet. Fun!

GNOME 2.20 for Debian

Mon, 24 Sep 2007 23:23:00 +0000

My lack of posts lately left Planet readers without yet another “yay, GNOME 2.20 released” post. I’m sure nobody missed it. However, I can report what’s going on in Debian regarding its packaging.

The executive summary is: the GNOME team rocks, and having much of GNOME 2.20 available in sid on the very same day it was officially announced was possible thanks to the incredible work done by lool, Np237, slomo and other restless team members, who spent the summer tracking GNOME 2.19 releases and packaging them in experimental.

To get a better view on what’s left to do, you can use the 2.20 status page, which you’ll see shows lots of green at this point. Some of the outstanding blockers are gtksourceview and the new epiphany-webkit binary stuck in NEW, which block gedit and epiphany, and of course, the initial mess that the buildds need to sort out to get the dependencies installed. The rest of “red bits” will continue trickling in unstable in the next few days.

Beware of the new behaviour in control-center, which will by default use the DPI value provided by X. Some X drivers are still buggy and can provide bad values, which will cause bad font displays. If you’re hit by this, you can force a DPI value in control-center, which should fix the issue. Also, you can read the relevant thread in our mailing list.

Enjoy 2.20!

Update: yeah, ftpmasters rock too, and epiphany hit incoming just a few hours after posting this entry. Yay ephy-webkit!

Ten years of GNOME

Wed, 15 Aug 2007 23:07:00 +0000

Ten years ago, Miguel de Icaza announced the “GNU Network Object Model Environment” project, an attempt to fix a dependency on a non-free library for free desktops.

Today, GNOME is a large, healthy and fun project with a very steady mission and personality. Congratulations to everyone who made it possible!

I feel bad

Mon, 11 Jun 2007 15:56:00 +0000

I’ve cursed myself quite a bit during the last two or three weeks, because there probably are no good excuses for not attending DebConf this year, it’s just that I didn’t plan it at all. Sorry to everyone who expected me there, and thanks to those who have insisted me lately to book tickets, and even planned my arrival by sea. :) Unfortunately, last minute plans won’t work this time, as my new job doesn’t permit. I hope you all have a great time, and unlike me, will POP THE TRUNK, all week.

Oil delivery will resume… maybe in Argentina? Or Birmingham, why not!

Google shuts down the Google Translation program

Thu, 17 May 2007 19:59:00 +0000

Via Quico Llach’s blog, I just learned about Google no longer hiring independent translators to work on their many web applications. Since Quico was hired by them to do their Catalan translators, a few millions of users have been benefitting from his very professional work in Google’s most used services: mail, maps, search…

Like Quico, I really hope they already have deals with translation companies to take care of minorised and minority language translations. When Catalan translations were made by random volunteers, I remember the results were quite… unsatisfying, as each one of them used their own glossary and style. When Quico took over, the interfaces were normalised using the Guia d’estil and everything improved dramatically (this problem is something people involved in Rosetta as a developer, translator and team leader know well, and is tricky to solve). Having Google suddenly drop Catalan as a “supported” language would be a huge step back for Catalan on technology. Either way, we’ll find out soon.

Congratulations to the Catalan Ubuntu LoCo team

Tue, 15 May 2007 18:38:00 +0000

On this happy day, there’s some big news coming from the Ubuntu Catalan Community. Today’s Community Council meeting approved the Catalan LoCo team, with lots of praise from the council members.

<mako> this is a fantastic application
<mako> the ultimate sign of a great team is that makes people want to
 move to their community to participate, +1 from me :)
<jono> this team is setting a standard for approval applications

Ubuntaires, my apologies for not being able to attend the meeting to offer my support. It clearly wasn’t needed at all, though, thanks to the amazing work you’re been doing during the last months. What I like most about the Catalan LoCo is that it’s the first culture-based team, as opposed to the traditional model of state, country or territory LoCo’s. Quoting the wiki,

[The] Ubuntu Catalan User community gathers Catalan-speaking users of Ubuntu in all its varieties. The scope of the Catalan LoCo Team is mainly the Catalan Countries, that is, the territories where Catalan is traditionally spoken, where members and volunteers are spread practically all over their geography.

Endavant!

Data disaster on pusa

Mon, 14 May 2007 21:15:00 +0000

pusa, a server I administer at uni, suffered a massive data accident on Wednesday. When I went to see why it didn’t come up from a reboot on Friday, I found out the initrd hadn’t been able to mount /. Weird…

Luckily, the two new disks were already installed in the host and waiting for me to finish the migration to the RAID1 and the new Linux-VServer setup, but unfortunately I’ve been way too busy and it was too late for some of our data. A fsck of /dev/hda1 resulted on large portions of the data going to /lost+found. Discovering this made me feel like a great fool after not having dd’d the device before doing this (a dry-run of fsck had not reported anything useful). I found out some of the lost data in random directories, but in general lots were missing, and others made no sense:

/oldpusa/etc: gzip compressed data, was "libpng.txt", from Unix, last modified: Wed Dec 20 00:58:51 2006, max compression

I hoped for my PostgreSQL stuff being intact, so after dd’ing /dev/hda5, I fsck’d the image. The result was an empty filesystem, and a lost+found full of stuff. I can’t find a directory with stuff that resembles postgresql data at all. I did find a directory with a PG_VERSION file in it, but the rest of the files in it (around 100) had numeric names and little more. If anyone thinks I might be able to rebuild my /var/lib/postgresql from this, I’ll be infinitely grateful.

Anyway, I haven’t written to the corrupted after I fucked up the root partition. I’m very interested in knowing what could cause corruption on all partitions, making them unmountable, but still recognisable by fsck, even if the result is not good at all. Maybe a corrupted partition table? If so, what does the Dear Lazyweb recommend me to try out? I suspect the first portion of all partitions were damaged, but maybe just that. Some “partition table shift”, which makes the filesystems lose the first superblock (trying other superblocks didn’t work either)? Suggestions is very welcome by comment or email, and detail on what tools and how to use to try out things, better. My backup of PostgreSQL is not so recent, and recovering some SmartList data would also be great.

As for the mandatory “where are your backups”, the answer is basically we had no resources to store them until very recently, and when we finally got the disks I’ve had no time until now to set it up entirely, so some bits (db, lists, web) were still not running off the new drives. The luckiest people have been the MUD owners, who have had no data loss at all, as they were living entirely on /dev/md0. Losing MUD data probably means getting angry calls at 4AM or so. :)

Debian's GNOME 2.18: are we there yet?

Wed, 18 Apr 2007 16:50:00 +0000

The short answer is no, but as our status page easily reflects, there has been lots of work going on during the last two weeks, once etch’s release unblocked the way to upload new versions to unstable. This post intends to resume the trend of updating on the status of GNOME in Debian, after we ended up deciding we’d ship etch with 2.14 for a number of reasons, most notably some complications with the GTK 2.10 transition at that time. You’ll be able to find other related news items in Debian GNOME team’s website.

What has the Debian GNOME team up to during the last 6 months? Our first priority was to focus on unstable’s GNOME 2.14 packages again, in an attempt to fix any outstanding remaining bugs from our packaging, and get them in the best shape possible to deliver a polished GNOME desktop for etch. I think the result is really good, and Debian’s default GNOME desktop is both very usable and attractive. In parallel, the preparations for a complete set of GNOME 2.16 packages continued in our Subversion repository and kept appearing, little by little, in experimental. The most visible consequence of our 2.16 efforts translated into nobse’s backport of 2.16 for etch, which can be found in the corresponding repository.

And then, with etch deep frozen and nearly ready to be released, GNOME 2.18 was released, and of course the GNOME team didn’t wait too much to start working on it.

Our current status is looking good: the Developer Platform is already available in unstable, although buildd’s are fighting the builds on various architectures. When the dust settles (GTK 2.10’s landing has generated quite a big cloud; we have a list of packages that still haven’t completed the GTK+ 2.10 transition), we’ll be able to prepare and upload the more complex Desktop components like the panel, nautilus, evolution or control-center. Unstable users should probably be seeing daily progress on this front, so keep an eye on your package managers!

Although Debian 4.0 released with an old version of GNOME, vast amounts of time and work have been invested to release it with the necessary backported fixes and enhancements. The newer GNOME versions have been available in Debian official ftp archives in very reasonable timeframes; this has only been possible thanks to the restless efforts of the (fortunately) growing Debian GNOME team members: giskard, feedback, HE, lool, np237, slomo, shaka, sjoerd, xaiki and not forgetting our incredible bug triager, svena. Thanks!

On the behind the scenes department, it’s a pleasure to report that Loïc Minier and Jordi Mallach very recently joined the GNOME Foundation’s board of advisors in representation of the Debian Project, replacing Matthew Garrett, who has been representing us for the last few years until he left the project. Thanks, Matthew!

The big Debian news I missed last weekend

Wed, 11 Apr 2007 20:46:00 +0000

I’ve been a bit offline during the last two weeks due to being in the middle of a ISP switch at home, which took me offline for a longer time than expected. Additionally, when I finally got the connection up, it was Easter time, and I ended up going to Vall, after cancelling a cycling trip with some friends down the Via Verda Ojos Negros (but this time, not during the night and spending a few days to complete the route) in the last minute, due to the horrid weather forecast. It apparently was a good idea: the river that goes along Vall overflowed, and for some reason the mobile phone service went down for more than 3 days.

On Monday night I came back to València, and I figured that the DPL election results would be out by the time. When I opened Debian’s webpage, I found out some other big news: Debian 4.0 was released the day before! Soon after, I looked for the vote results, to find Sam, my candidate of choice, was the winner, very closely followed by uncle Steve. Congrats Sam, no nos falles! And congratulations to the rest of the Debian project for yet another successful, well done release. Reading comments on news sites gives a fuzzy warm feeling. Even though we were slightly delayed, people show how etch is going to make their lives easier, or how trustable Debian is at work and at home. That’s the kind of stuff that keeps me and many Debian people going.

I’m pondering improvising some Etch Release Party (as the release managers deprived me of a IRC party by secretly releasing while I wasn’t looking) this weekend in Barcelona, where I will be visiting, after giving up on being able to be in A Coruña for DudesConf. Anyone up for it?

Tasques, però en català

Wed, 28 Feb 2007 23:26:00 +0000

So Ross was offering fame and glory to whoever would add i18n support to his nice little Tasks program. Tasks seems like something I’ve been looking for (there’s gToDo, but Tasks is simple and clean), and I haven’t done much for GNOME in a looong time, and I was bored, and hey, I can use some fame and glory, so…

Tasks, in a language Jose María Aznar can read

I need to note that it took quite a lot more time to create this screenshot than writing the patch. Go my GIMP skillz!

And by the way, Ross, what does Paris Hilton say about applications with their main function in a file named test.c?

Debian etch will ship with GNOME 2.14

Fri, 06 Oct 2006 21:45:00 +0000

This is already old news, but I haven’t commented here yet. We already hinted this possibility in my previous blog entry on this topic, but sometime last week, we made it official.

After speaking to some people upstream, we got the impression that the GTK situation was way too risky to do a GTK 2.10 migration, with no hints on when the file selector problems would be solved. As of today, and two GTK 2.10 releases later, not all of the issues appear to have been resolved in this branch, so we may have chosen the right path.

So, with this information in our hands, we described the whole situation to the release managers, explaining what the options were, and they, of course, had no doubt on what was better for etch.

The last two months before the release, we’ll try to polish the last few bits that we’d like to improve in the current 2.14 packages. For example, Joss just made a change to the session manager, to make it possible to save the user’s session easily, a feature which was present until GNOME 2.12, then removed in 2.14 with apparently no sane replacement of saving sessions available for the user.

I must admit I’m a bit disappointed about not being to ship all the work we’ve been doing with GNOME 2.16 in experimental, although I believe it was the right choice. If the etch release is delayed for some major reason, and let’s hope it’s not, that might open a window to see a transition going on, if the fixes are finally in and we consider our packages release quality. If not, we’re sorry, but we won’t be able to sell the “latest GNOME version” argument in our release PR. ;)

The Debian GNOME team has already been talking about doing a “semi-official” 2.16 backport for etch though, so people can use stable with the current GNOME, at least for a few months. We’ll see how it goes…

What about GNOME 2.16 and Debian?

Sat, 23 Sep 2006 12:08:00 +0000

I haven’t heard too many people asking if GNOME 2.16 will make etch. Maybe everyone just assumes it will, because the latest transitions have been pretty good, or maybe everyone just assumes it won’t because nobody would expect Debian to ship with a current GNOME release, right? Or maybe Debian is immerse in what looks like the beginnings of a civil war, and that is more interesting.

The Debian GNOME team has been preemtively working on GNOME 2.16, though, as the release clock is ticking. Loïc has spent a big amount of time revamping the packaging of GTK+ and Pango, finally resulting in sane source packages people can look at. Joss, Guilherme, Loïc and others have worked on the rest of the Developer Platform packages, which is now ready for testing in experimental. The evolution team has also been rocking and all the associated packages are ready to go in experimental as well.

The GNOME 2.16 status page still shows quite some red for Desktop packages, which are now being worked on, with GTK+ 2.10 in place.

But we still haven’t decided if we can go ahead and attempt a 2.14 -> 2.16 transition in time for etch. Our biggest concern are the known problems of GTK 2.10’s file chooser regarding cancelling of operations. Apparently, other distributions are getting bad bug reports due to these, so we need to be very careful about it. We know there are people working on an upstream fix as I write, but we don’t know when there’ll be a patch for GTK+ and libgnomeui available. If we learn it’s due soon, we might start speaking to our release managers about the possibility of starting a transition. If we have no news, it’ll probably be too late.

GNOME 2.16

Fri, 08 Sep 2006 10:14:00 +0000

GNOME 2.16 was released this week, delivering, once again to the day, the usual catalogue of improvements and polishing. Congratulations, everyone!

Catalan is, once again, very well covered in this release (99.87% completed as of this writing) thanks to the fantastic GNOME group at Softcatalà. I have only been able to contribute an update to Sound Juicer and little more, due to lack of time and, admittedly, motivation, so I’m very glad to see the group continues to be healthy and active thanks to Xavi, Jordi, Maria (from WSOP fame!), Gil (awesome GUADEC organiser) and others, under the leadership of Josep. Moltes gràcies, equip!

GTetrinet 0.7.10 released

Sat, 02 Sep 2006 18:19:00 +0000

GTetrinet 0.7.10 is out. This release fixes a security hole (CVE-2006-3125), so you’re advised to update ASAP.

The last release was assembled during UbuntuDownUnder, back in April 2005, which is a good indication about GTetrinet’s development health. If you’re interested in writing new features or fixing the many bugs in GTetrinet, please consider joining the mailing list. GTetrinet really needs your help!

Debian binaries are on the way to unstable; Ubuntu will hopefully suck them up soonish. Get the hot tarball from the GNOME FTP mirrors.

Thank you for the problem report you have sent regarding Debian.

Mon, 28 Aug 2006 23:51:00 +0000

Our user manuals encourage all newcomers to the Free Software community to file bugs when they find incorrections and bugs in a package. Of course, there’s always some people who take it too far (!).

Get prepared, DeFuBu challengers!

XFS nightmares

Tue, 22 Aug 2006 11:11:00 +0000

Following up to madduck’s and gwolf’s recent horror stories on XFS, last Thursday, my desktop greeted me after the fantastic week around Asturies with a series of I/O errors whenever I tried to execute something. I rebooted, and then the kernel wasn’t happy.

I/O error in filesystem ("hda1") meta-data dev hda1 block 0x4a9778 ("xlog_iodone") error 5 buf count 1024

/dev/hda1 is my / partition, and the machine would not boot at all. To make things more interesting, the box refused to boot from any of my old CD and DVD drives.

Yesterday, with my mail piling up already at Sindominio’s mailserver, I managed to find a spare CD writer, which would not open its tray, and a DVD reader which managed to boot a Breezy Live CD I had around.

The good guys at #xfs were helpful as always and helped me in the process of not fucking up my valuable root filesystem while trying to fix it. The filesystem ended up having quite some corruption here and there, but after xfs_repair, nubol was able to boot again. Only it was missing libldap.so.2, libX11.so.6, debconf programs and other minor details like those. Some reinstall rounds later, GNOME was able to startup without errors and now the box is up and running.

Does anyone know of some script that compares dpkg’s contents database with that the filesystem has, so I can easily find the rest of damaged packages to reinstall them?

The price of naked swimming in the Mediterranean

Tue, 27 Jun 2006 13:45:00 +0000

So to make a long story short, last night at GUADEC featured a great Fluendo party at one of Vilanova’s great beaches. At some point, people had drunk enough to finally consider getting a good swim in the warm waters of the Mediterranean. David Reveman, from the Novell crowd, was one of them.

I learned from Anna that in the US it is illegal to show your nipples (ie, go top-less) or any “reproductive organs” in public. WTF!? The GNOME Hispano crowd did have no problems at all, and went in completely naked, reminding me of the great nights at Helsinki during Debconf 5.

I thought it was a good opportunity to POP THE TRUNK, if only a little bit, so I swam to the buoy and came back, in complete darkness, and acs watching out for me from the distance. When we were back, most people were getting dressed already, and I managed to lose my micro suimming suit, which is a PITA as I need it to train.

The phone had more sand than silicon, I guess.

Anyway, I wasn’t the only one leaving stuff behind. David, if you mind your valuable wallet and mobile phone, find me around the conference. :)

Other GUADEC stories will need to wait for another entry…

Get prepared for Vilanova

Thu, 27 Apr 2006 20:02:00 +0000

Everyone knows IRC is a very useful resource. Today, #gnome-hackers had the basic tips to survive GUADEC moment.

16:23 <@davyd> you can then teach us how to order drinks
16:23 <@davyd> because I can't speak spanish
16:23 < miguel> They dont speak spanish in that down Davyd
16:23 < miguel> They speak Catalan
16:24 < miguel> Which is sort of Spanish - arabic words + a little bit of
 french thrown in
16:24 < jdub> estic cercant els meus pantalons!
16:24 < Ankh> I always thought catalan was a network file access thing
16:24 < hadess> davyd: they seem to prefer somebody speaking english than
 somebody speaking castillan ;)
16:24 < miguel> I know how to order coffee
16:24 < miguel> cafe am llet

GNOME 2.14 visits unstable

Sat, 01 Apr 2006 21:33:00 +0000

And after a long and boring week and a half of ordered Development Platform uploads, today the first few Desktop packages have started to hit unstable. I expect that the entire 2.14 release will be ready for your apt-get’ing in just a few days more.

Of course, that doesn’t include Ekiga, as their dependencies seem to be in a debian-legal trap…

The most exciting bit of this round of uploads is the participation of at least 3 new Debian GNOME maintainers, including… new people looking after the evolution packages!

Evolution and the new GLib in Debian testing

Thu, 30 Mar 2006 19:11:00 +0000

Last night, glib 2.8 and pango 1.12 entered testing, as a first step on the GNOME 2.14 quest. The bad news is that the fixed evolution & friends were not ready to go in as well, so now many etch users will be wondering why their evolution doesn’t start up, or doesn’t show any mail.

Until we manage to get a fixed evolution in testing, and it looks like it won’t be trivial to get this done in the immediate future, Erich’s recipe comes handy again:

My personal hero of the day is Gustavo Franco, for this email to debian-devel. He writes how to get your Gnome/Pango/Glib applications that don’t work since yesterday’s upgrade like evolution (#358071) working again:
$ G_SLICE=always-malloc evolution
And you should be able to read your email again.

Just FYI, and in case you missed it. :)