Search Results: "gismo"

18 July 2011

Stefano Zacchiroli: arrived at debconf11

debconf riding is again After ~1650 km of motorbike riding from Paris, yesterday evening I've arrived at DebConf11, after having shared the part of the trip from Geneva to Banja Luka with my good friend gismo. DebConf11 motorbike trip DebConf11 motorbike trip DebConf11 motorbike trip DebConf11 motorbike trip DebConf11 motorbike trip The venue looks great. It's full of nice spots for impromptu chats, beers, and the like, which I love. I had a good lengthy recovery sleep and I'm ready for the usual DebConf fun to begin. Plan for today is simple: dismantle DPL backlog accumulated during the trip and in the frantic 10-15 days before it. If you are at the conference and willing to discuss, chat, or simply share a beer: do not hesitate! For something less informal, Neil is also organizing an in person "ask the leader" session here; feel free to propose questions to him and make me have a hard time answering them. See you around.

28 March 2010

Stefano Zacchiroli: RC bugs of the week - issue 25

RCBW - #25 Last (long) week has finally passed: first in Geneve visiting Gismo, then in Sierre/Crans-Montana to present a paper at SAC 2010, then back in Paris for half a day before a day in Bruxelles for the 2nd year Mancoosi project review. (And of course campaigning has always been going on ...) All went fine and I can finally relax a bit for a week-end back "home" (i.e. Paris). Regarding RCBW, it looks like that in the past 2 months I've stabilized around 3 issues per month, which makes me happy nevertheless. Without any further ado, here are this weekissue's squashes: Random points:

31 January 2010

Axel Beckert:

On Wednesday I got DAM approval and since Saturday late evening I m officially a Debian Developer. Yay! :-) My thanks go to As Bernd cited in his AM report, my earliest activity within the Debian community I can remember was organising the Debian booth at 2003, where I installed Debian 3.0 Woody on my Hamilton Hamstation hy (a Sun SparcStation 4 clone). I wrote my first bugreport in November 2004 (#283365), probably during the Sarge BSP in Frankfurt. And my first Debian package was wikipedia2text, starting to package it August 2005 (ITP #325417). My only earlier documented interest in the Debian community is subscribing to the lists debian-apache@l.d.o and debian-emacsen@l.d.o in June 2002. I though remember that I started playing around with Debian 2.0 Hamm, skipping 2.1 (for whatever reasons, I can t remember), using 2.2 quite regularily and started to dive into with Woody which also ran on my first ThinkPad bijou . I installed it over WLAN with just a boot floppy at the Chemnitzer Linux-Tage. :-) Anyway, this has led to what it had to lead to a new Debian Developer. :-) The first package I uploaded with my newly granted rights was a new conkeror snapshot. This version should work out of the box on Ubuntu again, so that conkeror in Ubuntu should not lag that much behind Debian Sid anymore. In other News Since Wednesday I own a Nokia N900 and use it as my primary mobile phone now. Although it s not as free as the OpenMoko (see two other recent posts by Lucas Nussbaum and by Tollef Fog Heen on Planet Debian) it s definitely what I hoped the OpenMoko will once become. And even if I can t run Debian natively on the N900 (yet), it at least has a Debian chroot on it. :-) I'm going to FOSDEM, the Free and Open Source Software Developers' European Meeting A few weeks ago, I took over the organisation of this year s Debian booth at FOSDEM from Wouter Verhelst who s busy enough with FOSDEM organisation itself. Last Monday the organiser of the BSD DevRoom at FOSDEM asked on #mirbsd for talk suggestions and they somehow talked me into giving a talk about Debian GNU/kFreeBSD. The slides should show up during the next days on my Debian GNU/kFreeBSD talks page. I hope, I ll survive that talk despite giving more or less a talk saying Jehova! . ;-) What a week.

16 April 2009

Stefano Zacchiroli: happy term Steve

DPL candidacy woes Well, time to face it publicly: I lost and Steve/Luk won, it is as simple as that :-) This post is to: All in all, standing for DPL has been worth and interesting no matter the result. Time to get back to my usual Debian duties now ...

23 October 2008

Stefano Zacchiroli: from Vim to Emacs - part 1

One month with Emacs and counting - Part 1 Straight to the point: since mid September I've been using Emacs, trying to evaluate whether I was willing to switch from Vim to it. Yup, that's true, me (user of Vim since the day I've started using GNU/Linux 10 years ago, (not so) active maintainer in Debian of vim and related packages, author of some popular Vim extensions and of vim-addon-manager) it's considering switching to Emacs. What is worse is that I've de facto already switched. May jamessan forgive me. OK, that was the hardest part to write, now ... This choice will have an impact on me: partly because I'm quite sure several fellow DDs will start making fun of this story :-) , and partly because as many geeks I've always had strong opinions on the editor war. Switching side ain't easy. Hence, I've decided to write a small (2-3) series of blog posts on the issue, to future memory. The post you are reading is about why, since a few months ago, I wasn't willing to give Emacs a try, and how I've changed my mind. Why I wasn't willing to give Emacs a try, but then changed my mind I love knowing tools which can improve my workflow, no matter the task. Editors happen to be at the intersection of many tasks, hence knowing well his own editor and feeling satisfied about it is quite important. This is even more so for free software hackers which, for a reason or another, happen to use the very same editor for a lot of different tasks; in my case: programming, conf file hacking (i.e., playing the sysadm role), mail writing, and everything in between. I've started using vi on Solaris around 1998, then switched to Vim starting from version 4.0, and then followed all its releases up to 7.0. I consider my "Vim karma" to be quite hight and I've delivered several talks about using Vim for LUGs and other free software-related events. Still, I've always been hit bit several minor nuisances and glitches of Vim which couldn't be fixed by simple configuration tuning or add-on implementations (more on this in a future post). In the quest for the perfect workflow, those glitches have made me try several times other editors hoping for more satisfying work environments. Of course Emacs was one of them, which I've tried repeatedly during the years; the last time was circa 2006. For one reason or another, after a few days of experiments, I've always decided to give up with it. Why? Various reasons, listed below, together with an explanation of what (I think) has changed since then.
  1. Poor Unicode/multibyte support. Support for whatever Unicode encoding was close to null. It was not available in the legacy editor, and you had to use something called MULE, to be specifically enabled. That was so 60's, and rather hard to use. Now (apparently starting from Emacs 22.1, June 2007) finally you have built-in Unicode support and the needed two variables for setting the input encoding and the file encoding, which is basically all you need. Looks easy once you have it ...
  2. Lack of "modern" UI toolkit support. Yes, I do live in a console and invoke my editor from it, but nevertheless for long coding sessions I do also love having a nice GTK+ window containing my editor using settings which smoothly integrated with the graphical settings of my desktop environment. Maybe I'm getting old, maybe GNOME has changed my perceptions, but why the heck I had to tolerate different monospace fonts in my gnome-terminal wrt my GUI editor I never understood. Firing up Emacs was like getting back in time of 15 years, and if a geek having a maximized terminal on most of its workspaces had this feeling, then something was really wrong. This has changed: starting again from Emacs 22.1, the editor has frown support for that "bleeding edge" technology called GTK+. Finally you can use Pango font faces and avoid the time travel feeling when switching from a terminal to your GUI.
  3. "Dead upstream" syndrome. As we all know by experience, choosing a free software product is not only a matter of evaluating bugs and features, there are other environmental factors. A notable example is how active upstream is. A few of us will use a product affected by the "dead upstream" syndrome. That's exactly what I was feeling about Emacs. The first argument I can offer to back that feeling is again the Emacs release history (noted that "small" hole between 2001 and 2007? Rest In Peace release early, release often ...). The second argument is the bug tracking system: there was none, bug discussions happened only on the development mailing list and the bug tracker was a text file on CVS! (Yes, Vim doesn't have a proper BTS either, but I was looking for reasons to switch from it and hence looking for something better in several respects.) That has changed completely, as I discovered only at this year DebConf thanks to gismo. 2007 has enjoyed 1 Emacs release and 2008 already two. They do have a BTS now and guess what? is dear old debbugs. According to my first experiences as Emacs bug reported the maintainers are very reactive and also friendly in dealing with bug reporters. Finally, also keeping up with snapshot releases in Debian is entirely trivial, thanks to Romain's repository.
  4. Poor performances & memory consumption. This goes in the direction of probably the most popular joke used by Vim zealots in the editor war: Emacs is a nice operating system, but lacks a good editor, or something such. In the past I had the impression that starting Emacs was really slow and that generally the memory footprint was too high to be acceptable. You know what: starting a full-blown gvim with a good deals of add-ons (and I used quite a lot of them, that's why vim-addon-manager was born) is not that faster. And on the contrary, firing up an emacsclient is way faster than starting up a new gvim instance. Regarding memory consumption Emacs is still "gaining" the battle. Still, one has to keep in mind the different workflow: with Vim you are encouraged to enter and exit the editor (not without drawbacks, as I'll discuss in a future post), while with Emacs you always use the same one. It turns out that via emacsclient the resulting feeling is the same as having multiple editors (as you can fire them up as separate windows or in separate consoles), still sharing all user memory. A final comment on memory consumption while looking at my top sorted by decreasing RSS memory: the top process is xulrunner (from the browser) with 356Mb, then Xorg (159M), pidgin (128Mb !!!!), trackerd, gnome-terminal, gnome-panel, ..., Emacs shows up with 51 Mb at the 7th position. Yes, it is not the thinnest editor in the world, but on average machine it doesn't really matter at all.
In the next post: how to switch from Vim to Emacs, without loosing your mental sanity. (Whether I did succeed wrt sanity is up to the reader to judge.)

26 September 2008

Martin F. Krafft: Ubuntu giving back

OpenExpo ended last night with a lovely dinner at Roter Turm, and I ought to thank Matthias St rmer and his team for their efforts. I especially would like to thank Myriam Schweingruber of the Ubuntu team! could not assemble enough manpower for a booth, and so Myriam took care of selling our new t-shirts at the Ubuntu booth 29 of them. That s Ubuntu giving back to Debian! :) NP: AC/DC: Stiff Upper Lip

23 June 2007

Stefano Zacchiroli: vim changelog Closes completion

Automatic completion for Closes: entry in Vim DebConf is always cool: it's the place where 2 minute chats with people can turn into cool hacks. It just happened to me: 2 minutes with Dancer and Gismo chatting about apt-listbugs and kaboom: in the next upload of Vim you will get for free (as in the free drinks Sun offered us a couple of days ago) completion of Closes: entry in your debian/changelog. Just start typing Closes: # and after the # execute CTRL-X CTRL-O (the key to invoke "omni completion", see ":help omni-completion" in the Vim online help). At that point apt-listbugs will be invoked by Vim, it will contact the BTS using the SOAP interface to retrieve outstanding bugs, and will offer you a list of bugs to choose from. A brief description of the bug report will be shown as well in a preview window (see ":help preview"). Once you've made your choice, the appropriate "#XXXX" entry will be input where your cursor was. Super-cool! Here are a couple of screenshot to wet your appetite: screenshot-1.png, screenshot-2.png. If you can't wait for the next Vim upload take my current debchangelog.vim and put it in /usr/share/vim/vimcurrent/ftplugin/.

6 February 2007

Stefano Zacchiroli: do you want my debconf7 ticket

SPAM: do you want my DebConf7 plane ticket? This is (arguably) SPAM. Yes: I've already bought a plane ticket for DebConf7. But, unfortunately, yes: Gismo's proposal is terrific. So, again, yes: I would like to go to Edinburgh by motorbike traveling as few as 2200 km on my ass just to meet you, bunch of geeks, at the next DebConf7. Hence, to conclude this unsolicited blog post, here it comes the dangerous monetary proposal: are you traveling from Italy to DebConf7, Edinburgh airport? maybe from Milan Malpensa on June 14th 2006 (12:50), going back there on June 24th 2006 (14:45 from Edinburgh airport)? Then buy my plane ticket, it's cheap! Only 50 !!

13 April 2006

Wouter Verhelst: X.Org 7

If you're using Debian unstable on powerpc and haven't done your update today yet, might I suggest you hold off on that for a few days?
apr 13 09:14:28 <Yoe>	xorg 7 also seriuosly messed up fonts
apr 13 09:14:48 <Yoe>	"display" from imagemagick doesn't work anymore, and neither does rxvt-unicode
apr 13 09:15:02 <Yoe>	so how am I supposed to do *anything* useful, now? ;)
apr 13 09:15:04 <simonrvn>	i've been using 7 from experimental, so i had to change my fontpath in xorg.conf
apr 13 09:15:10 <simonrvn>	was
apr 13 09:15:19 <Yoe>	oh?
apr 13 09:15:36 <simonrvn>	/usr/share/fonts/X11
apr 13 09:15:39 <Yoe>	is that documented somewhere?
apr 13 09:15:42 <Yoe>	ah
apr 13 09:15:55 <simonrvn>	might be, not sure
apr 13 09:16:16 <Yoe>	hmm
apr 13 09:16:16 <simonrvn>	though don't remove the old ones, add those, since some of the packages still use the old path
apr 13 09:16:26 <Yoe>	well, not here, aparently
apr 13 09:16:36 <Yoe>	my FontPaths all point to /usr/lib/X11/fonts/misc,
apr 13 09:16:37 <simonrvn>	if it is, either BTS or one of the READMEs
apr 13 09:16:44 <Yoe>	s/misc//
apr 13 09:17:06 <Yoe>	and /usr/lib/X11/fonts is a symlink to '../../share/fonts/X11'
apr 13 09:17:11 <Yoe>	which does not exist.
apr 13 09:17:27 <ejka>	Yoe: dpkg -l xfonts-base
apr 13 09:17:41 <Yoe>	that's installed
apr 13 09:17:53 <Yoe>	... but still the 6.9.0 version
apr 13 09:17:53 <ejka>	Yoe: version
apr 13 09:18:04 <simonrvn>	l /usr/share/fonts/X11/75dpi: -rw-r--r-- 1 root root 4.1K 2006-04-11 00:32 charB08.pcf.gz ....
apr 13 09:18:41 <Yoe>	ah
apr 13 09:18:51 <Yoe>	xfonts-base depends on xfonts-utils, which isn't available (yet)
apr 13 09:18:59 <Yoe>	so I s'ppose I'll need to wait another day
apr 13 09:19:02 <Yoe>	(powerpc here)
apr 13 09:20:25 <ejka>	Yoe: for now you can add fontpaths /usr/X11R6/lib/X11/fonts/ misc,... 
apr 13 09:20:49 <simonrvn>	xfonts-utils *just came in to ppc today (sid)
apr 13 09:20:55 <simonrvn>	*just*
apr 13 09:21:10 -->	gismo (i=luca@ has joined #debian-devel
apr 13 09:21:37 <Yoe>	right
apr 13 09:21:42 <Yoe>	brb, restart X server
apr 13 09:21:43 Tcl interface unloaded
apr 13 09:21:43 Python interface unloaded
**** LOGGEN GESTOPT OM Thu Apr 13 09:21:43 2006
wouter@country:~$ startx
bash: startx: command not found
wouter@country:~$ X
X: cannot stat /etc/X11/X (No such file or directory), aborting.
wouter@country:~$ su -
country:~# apt-get install xserver-xorg
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
  xserver-xorg: Depends: xserver-xorg-core but it is not installable
                Depends: xserver-xorg-video-all but it is not going to be installed or
                         xserver-xorg-video but it is not installable
                Depends: xserver-xorg-input-all but it is not going to be installed or
                         xserver-xorg-input but it is not installable
E: Broken packages
country:~# apt-get install xserver-xorg-core
Reading package lists... Done
Building dependency tree... Done
Package xserver-xorg-core is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package xserver-xorg-core has no installation candidate
country:~# apt-get build-dep xserver-xorg-core
Reading package lists... Done
Building dependency tree... Done
E: Build-Depends dependency for xserver-xorg-core cannot be satisfied because no available versions of package libxmuu-dev can satisfy version requirements
Believe me, it's painful to have no X server available. Update: okay, by getting packages from experimental I've been able to get myself a somewhat working X again. Except that xkb doesn't load my modified keymap, which is horrible, and setxkbmap refuses to do anything when I say "setxkbmap wouter" and, on top of that, quits by segfault for good measure. I'm hoping that's fixed in the version that's been uploaded to unstable, but I can't check that—at the time of writing, doesn't even have a log file for some of the xorg stuff yet. Though some parts are in the building state at this very moment...