Search Results: "lucas"

5 November 2007

Lucas Nussbaum: NEW processing

NEW is currently nearly empty (only 3 packages), and there are only 2 NMs waiting for DAM approval. Some people deserve beers (… or milk ;) )!

4 November 2007

Lucas Nussbaum: Some numbers about Debian s history

There’s an interesting article on LWN.net about Gentoo: Who made Gentoo Linux, and when? A commit analysis I was wondering how Debian compared, so I made some stats using the debian-devel-changes archives. First, the number of source uploads per quarter:
It’s interesting to note that, while the number of packages in Debian increased a lot, the number of uploads basically stayed the same since 2001. Then, I wondered about the number of active developers in Debian. So I counted: I can provide the raw data on demand, if someone else want to work on this. There’s probably a lot of other interesting things to do!

27 October 2007

Christian Perrier: See you in BLR

The talks I proposed for FOSS.in, the major FLOSS conference in India, have been accepted for the Project Days, in the Debian-Ubuntu sessions. Thanks to the event organizers who will sponsor my travel to Bangalore, I'll probably leave as of Sunday Dec. 2nd and attend the entire conference from Dec. 4th to Dec. 8th. During earlier weeks, Sam Hocevar, the Debian Project Leader, also agreed to come to the conference and give two talks there. And, this morning, I had the nice surprise to discover that Lucas Nussbaum, one of our most tireless QA animators in Debian, will also come and give a talk about QA in Debian. So, that should make three French DD attending and, therefore, bring a strong Debian representation in this conference, which is something I definitely find interesting as I invested quite a lot of time and energy last years to increase the Debian presence in South Asia. This will certainly be a great occasion for us to give credit to the few people who contribute to Debian (and related projects) in India, and of course meet them in person. Please check the list of talks to get an idea of talks. Now for the challenge: the organizers expect our slides....by 7 days as of now. I don't know for Sam and Lucas but I have just begun working on one of my two talks (the i18n one, of course...you know: the one with the cute maps....). Would someone have a ready "How to contribute to Debian" talk somewhere? :-)

24 October 2007

Lucas Nussbaum: Better mentors.debian.net/REVU to improve our sponsorship workflow?

I recently sponsored several uploads, and was asked to sponsor even more uploads, and that got me thinking about our sponsorship workflow. It’s a clear bottleneck in Debian, and discourages many new contributors, which obviously sucks. It’s important to note that the same problems exist in Ubuntu (their equivalent to mentors.debian.net is named REVU). The best way to improve the process would be to have packages of better quality when a DD first look at them. They would be more likely to be uploaded right away, which frees time for other packages. I think that there’s a lot of room for improvement in the current mentors.debian.net implementation. Here is a small list of features I would like to see. The good thing with this whole list of features is that everybody can help. So, if you are looking for a sponsor and want to help solve this problem, start coding now ;) And if you need me to create nicenameforyourservice.debian.net, just ping me. There’s probably some code to steal from svnbuildstat.debian.net, so contacting its developers would be a good idea.

19 October 2007

Stefano Zacchiroli: debian on ubuntu com just a bug

No "debian" on ubuntu.com: undoubtfully a bug! The mention that the word "Debian" does not appear in the recent announce about Gutsy on the ubuntu.com website by Lucas reminded me something. Indeed, though I'm yet another DD that so far has never played the ubuntu bashing game, I remember having in the past tried to find the word "debian" on the ubuntu website. At the time of writing, using the site search on ubuntu.com, results in just a few hits, all of them are marginal: OpenOffice.org maintenance, the fact that Canonical employees are part of Debian, and an announcement as old as Ubuntu 5.04. What I want to see there is just a tiny teeny sentence that explain where a huge deal of Ubuntu packages come from and a mention of all the wonderful collaborative maintenance projects in which DDs and Canonical employees (or even MOTUs) work together to build great packages. So I wondered that it was probably a fault of mine: I wasn't looking in the right place of the website. Let's try with http://www.ubuntu.com/debian, since the ubuntu website is CMS/Wiki based it seems like a good attempt, doesn't it? But no luck: "Sorry, the page you are looking for was not found". But then, down in the page, I saw the root of the problem: "please consider reporting this problem as a bug". It is obvious now: it's simply a bug in the website! Let's point the maintainers to it ... As a careful bug reporter I first searched to check whether the bug was already reported, according to this search it hasn't (though now that you're clicking on it you're probably seeing something, when I did I got "No results for search debian"). So let's report the bug, the result is bug #154274 on launchpad. Let's see what will happen to it. Update: the reply on launchpad was really fast. I've followed up with what I think should be mentioned on the ubuntu website regarding Debian. Feel free to help out with your comments in the launchpad entry.

18 October 2007

Lucas Nussbaum: Re: Giving credit where due?

Christian Perrier is wondering why the official announcement about the Gutsy release does not even contain the word “Debian”. It’s not new: Debian is virtually nonexistent in Ubuntu’s communication. It seems that the last Ubuntu release to acknowledge its Debian origins was Dapper (June 2006), maybe because that was the “Long Term Support” release. The fact that there’s no “Ubuntu is based on Debian” paragraph on www.ubuntu.com was raised during Debconf, and it was supposed to get fixed, but it seems that it didn’t happen for some reason (there was such a paragraph before the website redesign). In other news, I’ve been trying to install Ubuntu Gutsy inside qemu, but it fails miserably while booting the installer. I removed the “quiet” and “splash” options from the kernel cmdline, and discovered that after trying to “mount the root filesystem”, I get dropped into busybox with no error message to google for. Feisty fails as well, but Dapper boots fine. So much for the Ubuntu is an ancient African word, meaning “I can’t install Debian” joke!

Lucas Nussbaum: Who made Debian GNU/Linux, and when?

Donnie Berkholz wrote an interesting article on Who made Gentoo Linux, and when?. Has someone already done something similar for Debian? It would probably be possible (and easy) to use the debian-devel-changes archives (available since 1998) for that.

4 October 2007

Lucas Nussbaum: Selling Debian tasks

In a lot of talks or blog posts (like Sam’s talk at RMLL, or Rapha l’s blog posts - both in french), people have been talking about what people could do inside Debian, and how it would help Debian. That doesn’t sound like the best approach to me. When describing tasks with the objective of getting potential contributors to pick them up, we should try to make them sexy, to tell users what is exciting about them, what they will learn doing those tasks, where satisfaction will come from. We really need to sell them better. Of course, some Debian tasks are mainly grunt work. And for some of them, people just do them because someone has to do them. But I believe that most tasks inside Debian are actually more interesting than outsiders would expect. For example, I would be very interested in reading why an i18n expert (hint: Christian!) finds i18n sexy … and I should probably try to write about QA myself. (As you might have noticed now, the subject of this blog post was misleading on purpose — chosen so that a lot of people would read the post :P)

28 September 2007

Lucas Nussbaum: ZFS as LVM killer really?

From the ZFS FAQ:
Can devices be removed from a ZFS pool? You can remove a device from a mirrored ZFS configuration by using the zpool detach command. Removal of a top-level vdev, such as an entire RAID-Z group or a disk in an unmirrored configuration, is not currently supported. This feature is planned for a future release.
buzz, buzz, buzz…

26 September 2007

Lucas Nussbaum: Compiz interest

From time to time, I try Compiz, to see if how it has evolved. The last time was yesterday (I also switched to the xserver-xorg-driver-ati from experimental). But as usual, after using it for a few minutes, I can’t help switching back to metacity. I don’t think that Compiz’s visual effects bring anything on the usability POV, and I just find them annoying after the initial “WOW”. Of course, it’s nice to show off, but to do actual work? Are there people really using it all the time?

22 September 2007

Lucas Nussbaum: creating a Distributions Developers Forum : follow-up

After that blog post, I decided to write a mail asking a first set of questions. I sent it to developers’ mailing lists of Fedora, Gentoo, Mandriva, openSUSE, and of course Debian and Ubuntu. I got really interesting answers from everyone, except …. Debian and Ubuntu.

18 September 2007

Lucas Nussbaum: Better Debian RC bugs graphs

if you like to monitor the number of RC bugs, you are probably annoyed by the graph on http://bugs.debian.org/release-critical/. The graph starts in 2003, making it impossible to read short-time changes. There’s a bug about that: #431299: RC bug status graph timescale is too long. And I provided a patch a few months ago, but it hasn’t been included yet. So, in the meantime, you can use my private copy (generated daily): Also, if you like graphs, Yves-Alexis Perez (aka Corsac) generates cool graphs about Debian: And if you want to have all the interesting graphs on the same page, you can use this page.

14 September 2007

Lucas Nussbaum: Idea: creating a Distributions Developers Forum ?

Scientific papers always have a “related works” section, where the authors describe how the work they are presenting compares with what others did. In the Free Software world, this is nearly non-existent: in a way, it seems that many of us are thinking of their projects as competing products, fighting for market share. On a project web page, I would love to read something like:
This project is particularly well suited if you want XX. But if YY is more important to you, you might want to have a look at ZZ.
Or simply links to similar projects for other environments, etc. All in all, I think that the goal is to improve the global satisfaction. Not to win a few users, who won’t be totally happy, because the project doesn’t really suit their needs. While some projects cooperate and share ideas, like I think desktop environments do inside freedesktop.org, most just ignore each other. I am both a Debian and an Ubuntu developer, and I’m sometimes amazed that Ubuntu discusses technical choices that were discussed (and solved) a few weeks earlier in Debian. And it’s even worse with the other big distros out there. Couldn’t we try to improve this ? We could just create a mailing list, where developers from various distributions could present the way they do things. This would allow to discuss future developments (”We are planning to improve this, what are you doing about that ?“) or simply to improve people’s knowledge of the various distributions. Of course, this could easily turn into flamefests, but they are technical ways to avoid that, like moderating posts from trollers… Does something like that already exist ? Do you think that it would be interesting ? Would you like to contribute to such a forum ? Some examples of things that could be discussed:

13 September 2007

Lucas Nussbaum: Which distribution on Thinkpads: really the good question to ask?

After Dell, Lenovo decided to ask users which Linux distribution they should put on Thinkpads. Seriously, who cares? If I buy a laptop that comes with Linux pre-installed, my first step would be to reinstall it from scratch, exactly like with a laptop with Windows pre-installed. Because the choices that were made wouldn’t match mine (think of partitioning, etc). Or simply because I wouldn’t totally trust the hardware manufacturer. So, what would make me happier about a laptop? I couldn’t care less about which distribution comes preinstalled. If Lenovo wants to make me happy, there are two ways: It’s not _that_ hard: some manufacturers got it right, at least for some of their products. There are many manufacturers contributing code directly to the Linux kernel, for network drivers for example. But maybe this is just about marketing and communication, not about results? Because after all, Dell and Lenovo will look nice to the random user. While playing-by-the-rules manufacturers are hidden deep in the Linux changelog.

22 August 2007

Lucas Nussbaum: Opening mutt s HTML attachments with epiphany?

I just ran into a rather funny problem. I’d like to use epiphany to open text/html attachments or mail parts. Mutt uses mailcap, so I added an entry in ~/.mailcap:
text/html; epiphany-browser '%s'; description=HTML Text; nametemplate=%s.html This should work fine, but the problem is that mutt creates a temporary file (/tmp/mutt.html) and removes it when the command terminates, which is nearly immediately with epiphany. And epiphany has a really nice feature: it monitors local files for changes and reload them when they change. Which results in seeing the page briefly, then a File "/tmp/mutt.html" not found. error page. Anyone using mutt and epiphany together successfully?

14 July 2007

Gunnar Wolf: On collaborative maintenance

Following Zack's and Lucas' posts regarding group maintenance of packages: Do I have to AOL with you guys? Yes, I also agree with Zack's both 1 and 2. And I also want to share the bit of experience we have got in this regard in the pkg-perl group. In our case, group maintainership has often saved our collective butts. We have also debated somewhat which way should our packages' maintainership be handled. In the end, our packages' maintainer will (most usually) be the pkg-perl group itself, subscribed through an alias that reaches all of us. Then, every group member that feels identified with the package lists himself as an uploader (note that this does not necessarily have a relation with the last uploads, at least not as strongly as in what the KDE and Gnome groups do, according to Lucas' post - it's closer to the pkg-ruby-extras handling). Of course, there are some packages which I have NMUed in the group's pool - packages I prefer not to have listed in my maintainer page, as I don't usually care too much about them, but I happened to be able to fix a bug with them.
Now, what about the roles of the different group members? Each of us has some skills that make him better for part of the task - i.e., we have an amazingly knowledgeable member, Niko Tyni. He just fixes all the bugs that baffle us. Honest, my best kudos to Niko, he is a good part of our team's success. And then, we have hard-working people as Gregor Hermann, who not only fixes also nice amounts of bugs, but also writes and runs general QA tests throughout our over 300 modules. Neither of them is a DD yet. And of course, many other hard-working folks. Some of us are DDs and try to upload promptly - and, of course, also try fixing bugs. So far, we are in good shape, and we tend not to lag too much. I have taken some vacation periods (both announced and unannounced - sorry :) ), but to my surprise and amazement, my packages tend not to be buggy - Why? Because there is a real team looking after them, and in the end, we keep an eye on each other.
For the pkg-perl group, group maintenance has really worked. We collectively maintain more packages than it would be reasonable for all of us added together as individuals, and they are in a better shape. There are several things we can make better, and we do try to address them - it is not yet heaven, but... :) I'll elaborate later, when I finish a text I'm preparing for presenting at YAPC (it's not that long, of course - During Debconf, I showed advances of it to several people... I just have left it aside). Right now... Well, I have 3hr of sleep left before we leave for a daytrip to the beautiful (but hot and humid!) Veracruz Huasteca. See you on Sunday/Monday!

12 July 2007

Lucas Nussbaum: Collaborative Maintenance

Stefano Zacchiroli blogs his thoughts about collaborative maintenance. He identifies two arguments/religions about it:
  1. it is good because duties are shared among co-maintainers
  2. it is bad because no one feels responsible for the co-maintained packages
And he says he stand for the first one. I’m not sure that those two positions really contradict. Sure, collaborative maintenance is a good thing, because it allows to share the load between co-maintainers, which often results in bugs being fixed faster. But collaborative maintenance creates the problem of the dilution of responsabilities, and the dilution of knowledge. In many cases, a single maintainer will have a better knowledge of a package than the sum of the knowledge of all co-maintainers. Also, sometimes, teams don’t work very well, and everybody start thinking that a specific bug is another co-maintainer’s problem. In the pkg-ruby-extras team, we have been trying different organizations over the past two years. We have now settled with the following: Stefano also raises the point of infrastructure issues caused by the switch to the team model. I ran into one recently. My “Automated mails to maintainers of packages with serious problems” are currently only sent to the maintainers of the packages with problems, unless someone has problems in both maintained and co-maintained packages (in that case, all problems are mentioned). I thought for a while about sending mails to co-maintainers as well, but that would mean sending more mails… I might try that and see if I get flamed :-)

11 July 2007

Stefano Zacchiroli: uploaders vs maintainers

More Uploaders, Less Maintainers: Infrastructure Issues When yet another discussion about "is collaborative maintenance good or not?" starts on debian- lists, the average lurker can easily identify two arguments / religions:
  1. it is good because duties are shared among co-maintainers
  2. it is bad because no one feels responsible for the co-maintained packages
Of the two religions, I stand for the first one. More generally I share the long term aim of decreasing as much as possible the "ownership" of Debian packages; collaborative maintenance is just a tool to achieve the goal. In the meantime, I believe the second religion is supported also by technical deficiencies in some pieces of our infrastructure. In particular some of our developer tools artificially enforce a distinction among Maintainers and Uploaders where it wouldn't be necessarily needed. In the last few days I thought about some of them: Think about such deficiencies, I'm pretty sure we can spot and fix easily a lot of them in our tools. Update: Lucas: I agree that the two arguments do not necessarily contradict, that's why I (initially) called them arguments. Then I moved to "religions", it was an oversimplification: there are of course pros and cons of collab maint. My main argument holds nevertheless: several perceived cons of collab maint are due to artificial distinctions maintainer/uploader in our tools, thanks for providing yet another example ... I want more! :)

9 July 2007

Lucas Nussbaum: Easy migration of a service to another, totally different host with iptables

I’m tired of googling for this every time I need it, so I’m blogging about it. Q: How can one redirect all connections to hostA:portA to hostB:portB, where hostA and hostB and in totally different parts of the Internet? A:
echo 1 > /proc/sys/net/ipv4/ip_forward
$IPT -t nat -A PREROUTING -p tcp --dport portA -j DNAT --to hostB:portB
$IPT -A FORWARD -i eth0 -o eth0 -d hostB -p tcp --dport portB -j ACCEPT
$IPT -A FORWARD -i eth0 -o eth0 -s hostB -p tcp --sport portB -j ACCEPT
$IPT -t nat -A POSTROUTING -p tcp -d hostB --dport portB -j SNAT --to-source hostA
Connections are masqueraded, that means that, for hostB, all connections are coming from hostA. So be careful.

5 July 2007

Lucas Nussbaum: How do archive rebuilds and piuparts tests on Grid 5000 work?

With the development of rebuildd and the fact that several people are interested in re-using my scripts, I feel the need to explain how this stuff works. Grid’5000 First, Grid’5000 is a research platform used to study computer grids. It’s not really a grid (it doesn’t use all the classic grid middleware such as Globus). Grid’5000 is composed of 9 sites, each hosting from 1 to 3 clusters. Inside clusters, nodes are usually connected using gigabit ethernet, and sometimes another high speed network (Myrinet, Infiniband, etc). Clusters are connected using a dedicated 1OG ethernet network. Grid’5000 is in a big private network (you access it through special gateways), and one can access each node from any other node directly (no need for complex tunnelling). Using Grid’5000 nodes When you want to use some nodes on Grid’5000, you have to use a resource manager to say “I’d like to use 50 nodes for 10 hours”. Then your job starts. At that point, you can use a tool called KaDeploy to install your own system on all the nodes (think of it as “FAI for large clusters”). When KaDeploy finishes, the nodes are rebooted in your environment, and you can connect as root. At that point, you can basically break the nodes the way you want, since they will be restored at the end of your job. Running Debian QA tasks on Grid’5000 None of that was Debian-specific. I will now try to explain how QA tasks are run on Grid’5000. The scripts mentioned below are in the debcluster directory of the collab-qa SVN repository. When the nodes are ready, the first node is chosen to play a special role (it’s called the master node from now on). A script is run on the master node to prepare it. This consists in mounting a shared NFS directory, and run another script located on this shared NFS directory to install a few packages, configure some stuff, and start a script (masternode.rb) that will schedule the tasks on all the other nodes. masternode.rb is also responsible for preparing the other nodes. Which consists in mounting the same shared NFS directory, and executing a script (preparenode.rb) that installs a few packages and configures some stuff. After the nodes have been prepared, they are ready to execute tasks. To execute a task, masternode.rb connects to the node using ssh and executes a script in the shared directory. Those scripts are basically wrappers around lower-level tools. Examples are buildpackage.rb, and piuparts.rb. Now, some specific details: Comments and questions welcomed :)

Next.

Previous.