Search Results: "lucas"

25 January 2010

Lucas Nussbaum: How free is the Nokia N900?

Dear readers, So, I ve been looking into buying a Nokia N900. However, what it provides regarding freedom is still not completely clear to me. And given that it is significantly more expensive than other smartphones, I d like to make sure that it s not a loss of money :-) - Can I download the full source, recompile it, build a firmware from it and re-install my Nokia N900 from scratch? Is the process documented? It seems that you need to accept a EULA to download updated firmwares, and I couldn t find the source for them. What exactly is available from firmware that is not available through normal repositories? (Are normal repositories only for extras apps, or is the base system also installable / upgradable from them? - What s the content of /etc/apt/sources.list? What exactly is http://repository.maemo.org/pool/maemo5.0/nokia-binaries/? What does Nokia need to hide? :-) - Would it be possible to develop a Centos-like distribution, installing the Maemo firmware, but then upgrading everything to rebuilt versions using an unofficial repository? Are there some applications that are not packaged, or that would break if re-installed that way? - Could I install Debian or Ubuntu on the N900? Is the process documented? Is it possible to dual-boot between, say, Maemo5 and Debian? (I m not talking about setting up a chroot, of course) - Besides the non-free telephony stack, are there any other antifeatures I should be aware of? Thanks.

22 January 2010

Lucas Nussbaum: Simpler GnuPG-encrypted password store

Roland blogs about his GPG-encrypted password store. When I read the title of his blog post, I thought he would be writing about the gnupg.vim Vim plugin. But he didn t, so I ll take care of that: The gnupg.vim plugin provides transparent editing of GPG-encrypted files. It s as simple as vim foo.gpg, enter your GPG key if you are creating the file, and you are done.

16 January 2010

Stefano Zacchiroli: Kuhn on Debian, Ubuntu, and the culture of freedom

The culture of freedom lies in the details Here is an interesting blog post by Bradley Kuhn about Ubuntu, Debian, and (warning: my interpretation ahead) the culture of freedom. While reading it, I had kinda moment of truth, because just yesterday I was musing with Mehdi and Lucas on the fact that Debian is basically the only remaining distribution among the mainstream ones (if that means something) that is free from the ground up, including its infrastructure. We "just" seek hardware via donations and then we run, thanks to the amazing work of DSA, our own free infrastructure on top of it. Let's cherish this value! Thanks to Roberto Di Cosmo for the pointer to Bradley's post. Update: there's a thread on the ubuntu-devel mailing list about Bradley's post.

Stefano Zacchiroli: RCBW strike - BSP in Moenchengladbach

RC squashing news In the last two weeks I didn't progress as usual with RC bug squashing, even if I've some squashes to share: The reason for my under-activity are that for a week I'd relatively scarce network connectivity, which is a badly needed good for RCBW. Then, this week, I got swamped by various tasks at the university (including co-authoring a paper with Lucas, more on this (hopefully) in the future). My residual RCBW time has been devoted to write a page about RCBW where I've tried to summarize my initial motivations and the main points of the initiative, which I consider established by the first 18 weeks of activity. Starting from next week I'll be back with daily squashes. In the week-end ... drum roll ... I'll be attending the BSP in M nchengladbach, hosted by Credativ; I'll personally be kindly hosted by bzed which I thank already for that and for the BSP organization. See you there (!?)

25 December 2009

Christian Perrier: My Christmas gift to Debian

Being stuck at home because of my stepfather's health condition becoming worse and therefore family meeting plans being changed, I just made the Debian project a small Christmas gift by fixing an RC bug on December 25th for the first time in my Debian life. Apparently, after TeXLive packages changes, this one will not be the only one discovered by Lucas automated archive rebuilds. Anyway, Merry Christmas to those of you who celebrate it.

22 December 2009

Lucas Nussbaum: Doctor Capello!

He might too shy to tell everybody, but the world must know. Luca Capello successfully defended his PhD thesis today at Universit de Gen ve, getting a Tr s Bien mention. I must admit that my last biology lesson was 13 years ago, so I m not sure I can really comment on his work on Vomeronasal Receptors: from Monogenic Expression to Axon Guidance. But I was very impressed by the quality of the experimental process, especially compared to what we do in computer science. Debian was well represented at the defense, since Axel Beckert, Didier Raboud and the Debian kilt were also there. Welcome to the list of Debian Developers holding PhD degrees, Luca!

Luca waiting at the door (again).
luca1
Luca ready to start.

21 December 2009

Lucas Nussbaum: Debian s KVM + Ubuntu karmic => bug?

I ve been playing with virtualization, and KVM in particular. However, I m running into an interesting problem. Below is how Ubuntu Netbook Remix look inside my KVM (either using virt-viewer, virt-manager or directly KVM to display the VM). Note how the top panel is fine. I m using KVM 88 from experimental (but I had the same problem with KVM 85 from unstable), the cirrus video driver inside the VM, and an up-to-date karmic VM.
Has someone ran into that problem already? If yes, where is it tracked? I m been failing to find the correct search keywords so far. kvm-unr

20 December 2009

Stefano Zacchiroli: RC bugs of the week - week 15

RCBW - week #15 Here are last weektoday squashes, by yours truly: Some highlights:

9 December 2009

Asheesh Laroia: A big machine that nothing can stop

A couple of weeks ago, Lucas Nussbaum wrote about his experience at the Ubuntu Developer Summit. Two things stuck out at me: In the summer of 2004, my laptop (an iBook G4) ran Debian GNU/Linux on PowerPC. I tried out Ubuntu that autumn, and was very impressed. It's been five years since then. My desktop still runs Debian, and I'm proud to be a "two-distro" community member. At the same time, this juggernaut nature raises concern. When Ubuntu releases ship with significant flaws, I quietly sigh and wonder, Are we doing good service to the people coming to GNU/Linux for the first time and seeing Ubuntu? This bugginess has bit me a few times (even for upgrades between one release and the next), and it pushed a friend of mine to switch a lot of his computing to DragonflyBSD. Lucas points out that Ubuntu's done a fantastic job of becoming visible. A look at Google Trends shows that people search for "Ubuntu" about as much as they search for "Linux" at all. Richard Stallman complains when people refer to GNU/Linux as just "Linux." But today, the most popular name for an operating system based on GNU is probably "Ubuntu." For Stallman, having his hard work associated with someone else's "Linux" project must be frustrating. As a Debian contributor, it would be easy to succumb to the same feeling with regard to Ubuntu. Lucas is well aware of that. He asks, Debian does have users! I was feeling a bit disheartened about my maintenance work on alpine lately, when out of the blue I received an email from a fellow at MIT asking me if I would accept some help with maintenance from him. Just seeing the note was a relief; it's very nice to be reminded that I have users to take care of. Debian is not as popular as Ubuntu on the desktop (or laptop), it's true. But technically sharp people do frequently still choose it. For example, the FreeNAS project recently announced a switch from FreeBSD to Debian (and a new name as coreNAS). But we could end up a "package supermarket". To stave this off, we must do good releases and make sure people know about them. Doing all that work takes us all time. We must recruit new contributors, help them find things to work on, and make sure they feel welcome. And sometimes-sloppy maintainers like me ought to fix our packages, and get help from others where necessary. I promise to work toward that.

2 December 2009

Margarita Manterola: Life after DebConf8

Finally, after more than a year of preparation, and six months of very very hard work, DebConf8 has come and gone. Even if I'm not yet completely recovered from all that stress, I'm good enough to feel really happy about how things turned out. DebConf8 was a great success. We had great talks, many opportunities for developing interesting ideas, a lot of social interaction, an awesome video team that allowed more than 200 people from all around the world to be part of the conference even if they weren't in Argentina, and in general almost everyone had a very good time. It was really nice to have so many people from Debian over here, and it was specially nice to see them working and enjoying themselves so much. This was all possible thanks to our sponsors, thanks to the many hours spent during the previous months both by the DebConf orga-team (the usual suspects) and specially by the local team, which includes Tincho, Dami n, Romanella, Maxy, Sebas, Zero, Mendieta, Dererk, Melisa, Angasule, Lisandro, Nueces, and also thanks to the all help of the volunteers that came to work with us during DebCamp and DebConf, which include Tom s, Tinchito, M nica, Lucas, Germ n, Diego, Fefu, Nicol s, Mart n, Marcos, Hern n, Alejandro, Mat as, Rodrigo, Alberto and Joaqu n, and finally, DebConf wouldn't have been the great event it was without all the people that managed to travel thousands of kilometers to get here. To all of them, thanks, for making DebConf8 such a great conference Now, at last, DebConf8 is over (although there is some stuff that we still need to do before we can really forget all about it), and life goes on. Today, I did my first NMU after a long time. I'm particularly glad to have time for fixing bugs again, but I won't lie, I'm also extremely satisfied with how DebConf8 turned out. See you in Extremadura!

26 November 2009

Michal Čihař: Ubuntu bugs for second time

It looks like my post about bugs in Ubuntu has received a bit more attention than I expected for few lines of ranting :-). Most interesting reactions came to Lucas Nussbaum's blog. There were nice explanations how it is supposed to work, but the problem is that people out there can not manage that amount of bugs. It is possible, that for some core packages, they manage to do the job. However most bug reports will probably go to some leaf packages, which are not that important, but lot of people use them. I started to interest in bugs in Ubuntu when I noticed that there is some huge number of bugs linked on phpMyAdmin's PTS page. There was something like 50 too much bugs. After quick look I could see that most of them are duplicates. After little fight with ajaxy interface, I even managed to mark most of them as duplicates and fix it in Debian package. But as somebody with no knowledge of Ubuntu (and not willing to learn internals of yet another distribution, I think Debian and OpenSUSE is enough), I really have no idea what could be done to push some bug fix to existing release. So once some Ubuntu release (The Lucid Lynx in this case) got new version, I marked the bug as fixed. This is probably not that nice to users, but somebody from Ubuntu community should take care of them. Off-topic PS: If anybody is interested in Google Wave invitations, just write me an email, I currently have 15 without any use.

25 November 2009

Lucas Nussbaum: Re: Ubuntu Bugs

(Context: Michal iha complains about bugs filed in Ubuntu not being looked at nor forwarded to Debian or upstream) Michal, I think that your complaint is caused by a misunderstanding of how package maintenance happens in Ubuntu. I ll try to clarify it, based on what I understand (if you know better than me, don t hesitate to comment). The part of Canonical maintaining the distribution is organized into teams (full list here), like Kernel, Foundations, Desktop, Mobile, Server, etc. Most of those teams have mirror-teams in the community, like the Ubuntu Desktop team. Those teams take care of subsets of packages in Ubuntu, of relevance to the respective teams. (This is orthogonal to package upload rights, which are managed with the Ubuntu Core Development Team, and the Ubuntu Development Team ; there s a proposal to change that so that package upload rights are based on the first set of teams). However, there are some packages (probably more than 70% of the packages in Ubuntu, including main+universe) that are of no interest to any particular team. Those packages are maintained on a best-effort basis by all the Ubuntu developers (inside the loosely defined MOTU team), and focus is usually on not diverging from Debian, to make their work as easy as possible. It s very similar to what we do in Debian with orphaned packages: sometimes, important bugs get fixed, because someone complained loudly enough or a developer ran into the bug and did a QA upload ; but usually, we don t really do any bug triaging. Of course, there are some packages in Ubuntu that are not maintained by any core team, but still have someone that cares about them. They are more the exception than the rule. So, yes, obviously, you will run into packages with lots of untriaged bugs, sometimes even with patches. And those bugs and patches are rarely being forwarded manually to Debian, simply because nobody cares about those packages in Ubuntu. In an ideal world, with infinite resources, this would not happen, of course. But realistically, this is not going to change anytime soon. There s a link on the PTS to the bugs of your packages in Ubuntu. The idea is to allow an easy access to the bugs reported in Ubuntu, which are likely to be also relevant to the Debian package. You should probably feel welcomed to triage the bugs against your package in ubuntu, if it makes it easier for you to monitor them. There s some noise in the Ubuntu bugs, of course, but more and more often, by looking at the Ubuntu bugs, I find important bugs in my Debian packages that are not even reported in Debian yet.

24 November 2009

Lucas Nussbaum: UDS Lucid

I m back from Dallas, where I was invited at the Ubuntu Developer Summit for Lucid. I spent a great week there ; the event was extremely well organized (by organizing them every 6 months, you are probably able to gather a lot of experience!). Of course, after all I had heard about people hugging each other all the time in the Ubuntu community, I was a bit worried, especially with the flu spreading! But there are lots of fantastic people around Ubuntu, and it was a very nice opportunity to be able to meet them all. Since it was my first UDS (I was at FOSSCAMP in Prague a few years ago, but didn t stay for UDS back then), I was not really sure of what to expect. I was very pleasantly surprised. UDS vs Debconf UDS is very different from Debconf. In Debconf, we do three different kind of things: In UDS, the main focus is on the third point: most of the sessions are about discussing what will be implemented for the next release. All of the relevant developers are in the same room to discuss possible problems, and the outcome of each session is usually a detailed plan, with a list of action items. It s a very nice way to ensure that changes are well thought, and allows making large-scale changes in Ubuntu very easily (you don t spend weeks arguing about them on mailing lists). Of course, it s probably also helped by the fact that there s a company behind Ubuntu, with a set of large teams (kernel, foundations, desktop, etc), which helps transfering trust (not everybody feel like they have to participate in each discussion, even when they affect the whole distribution: the team in charge is trusted by the rest of the project). On the other hand (yeah, let s be negative for a while) it doesn t really help spreading information between Ubuntu developers: it s often a bit difficult to get the global view of what is happening inside Ubuntu, especially since lots of things are discussed on IRC. Collaboration between Debian and Ubuntu During the week, I mainly was interested on collaboration between Debian and Ubuntu. There s a strong focus on doing the right thing wrt Debian (and also other upstreams). Then, of course, Ubuntu also has an agenda, which sometimes requires moving very fast on some things, or making compromises between technical purity and pragmatism. But the willingness to have common foundations between Debian Squeeze and Ubuntu Lucid will surely benefit both distros. Quality Assurance On the QA front, I am planning to do archive rebuilds for Ubuntu as well (fixing FTBFS is an easy way to start contributing to Ubuntu or Debian, and having those bugs fixed in Lucid would benefit Debian as well, by having patches already prepared). I also had a session with the QA team, where I gave an overview of what we are doing in the Debian QA group, to discuss opportunities for collaboration. The Ubuntu QA team focuses more on testing (with automated or manual testing) and bug triaging than archive quality that part is left to the MOTUs and the release managers. (About MOTUs, I liked how what they do was described as long-tail maintenance, landscape gardening or terraforming. That gives a good idea of what it s about). Ultimate Debian Database On the Ultimate Debian Database front, I did a plenary talk to try to demonstrate how UDD could be useful to Ubuntu as well, and, with Jorge Castro, we examined some metrics of Ubuntu s giving back to Debian. I also talked with the Launchpad team to try to resolve my long standing pretty please provide an export of Ubuntu bugs, so I can easily import them in UDD! issue. Ubuntu and ARM ARM netbooks and smartbooks (mix between netbooks and smartphones) are coming, and Ubuntu is clearly very well positioned to play an important role on that market. There was a whole track about ARM support, with lots of changes that will be done for Lucid. Let s all hope that Ubuntu-powered ARM netbooks win that market, so we don t reproduce the failures of the non-ARM netbooks. Distributed Development James Westby has been working on a set of tools to be able to work on Ubuntu packaging using bzr. The point is not to store the canonical source for Ubuntu packages in bzr (well, at least it s not the plan yet), but to provide a set of branches to make it easier to merge or cherry-pick from Debian. The resulting workflow looks extremely nice, with lots of syntaxic sugar. And even better, he assured me that his code is portable to Git ;)
Using his work, merging Ubuntu-specific changes in a new version of a Debian package basically means pulling from lp:ubuntu/foopkg, merging from lp:debian/sid/foopkg, and you are done!
As a bonus, we (Debian) would get bzr branches with the history of packages (kind of bzr-powered snapshots.debian.org).
James project is not completely ready yet, but should be very soon. It s already basically usable, apparently. Conclusion Ubuntu has clearly gone a very long way since 2004. Everything looks very well organized and polished, and gives the impression of a big machine that nothing can stop. With Cloud Computing and now ARM netbooks, Ubuntu has proven to be able to adapt to the current trends and attract a lot of visibility. It is great news for Free Software, but also proposes an interesting challenge to Debian: of course, it s nice that a Debian-based distro is in that position, but will Debian manage to stay relevant, or are we just going to be the technically-pure distro without many users that serves as a package supermarket for Ubuntu?

6 November 2009

Stefano Zacchiroli: DPKG source v3 stats

graphing DPKG source v3 adoption Given that now we can upload DPKG source v3 packages to the archive, prodded by Lucas and Martin, I've added yet another page to my Debian graph/stats collection: namely stats about DPKG source v3 usage in the archive. This time, I've done even less work than the other pages: Lucas was already providing the actual data via a UDD CGI. So thank him, I'm basically just aggregating/mirroring the graphs for bandwidth reasons. Of course, I've also added the new page to the stats index on wiki.d.o.

27 October 2009

Lucas Nussbaum: Patches welcome

When you merge a patch, especially a patch that has been waiting to be merged for more than 6 months, it is polite not to publicly mention that the patch required changes to the way it originally looked (a lot of patches do, especially when you didn t provide much feedback during the 6 months waiting period), or that merging the patch required cleaning up, and introduced bugs. Also, crediting the patch author in public communications doesn t hurt. If you fail to do that, people might feel that patches are not so welcome after all.

10 October 2009

Stefano Zacchiroli: RC bugs of the week - week 6

RCBW - week #6 RC bugs squashed this week by yours truly: This week I've cheated for at least two reasons:
  1. the first 4 entries in the list above are bugs of "mine", since within the Debian OCaml Maintainers team we migrated to a new package toolchain called dh_ocaml (with a lot of advantages I've anticipated before my summer break). The migration to that triggered (thanks, Lucas! :-) ) more than 30 FTBFSs which had to be dealt with. So, even if not cheating, it is at least breaking the NMU tradition of RCBW, but they were still RC bugs looking for a fix! All in all, I'm impressed by the fact that in about a week we dealt with most of them.
  2. the lxml fix above is severity "important" and as such, not RC. I attacked that because I intended to help out with the Python 2.6 transition which is still, at the time of writing, 41 bugs away from hitting unstable. I confess I did not find the task particularly fun (which is a requirement for me when I work on packages which are not mine) yet, we'll see next week ...
The feeling of the week I've to share is that I'm more and more impressed to not have received any complaint about my NMU activity, and I'm approaching the 50 NMUs. Actually I've received several "thank you" replies (you rock guys and you know who you are). On one hand this is probably a good indication that I haven't (yet) done any serious mistake; I do love peer-review! On the other hand, and more importantly, this is dispelling inside me the folklore / cultural block we have in Debian that "NMU is bad", while NMUing should become a way to help each other routinely. Really.

18 September 2009

Jaldhar Vyas: RHAT Chroots For Jackasses

A jackass mach package page. IM SOOOOO SORRY TO LUCAS AND HIS FANS AND HIS MOM.

17 September 2009

Lucas Nussbaum: Free software improvements

Two things that have been annoying me for a long time have been fixed recently, and I discovered those two new features the same day (rainy week-ends are good for you). OK, both changes have been there for a long time, but I m sure I m not the only one who didn t notice them at the time. Big Thank You to both groups of developers (especially to the ati/radeon developers, who have been very helpful on IRC to troubleshoot my setup).

Lucas Nussbaum: Bootstrapping Centos or Fedora from Debian or Ubuntu

Here are some notes about bootstrapping a Centos or Fedora chroot from Debian. It should also work from Ubuntu with minor changes, but I haven t checked. The following should really be done in a chroot, since some commands will install files in your /etc or elsewhere, ignoring the --installroot passed to yum. The following instructions are for Centos, but replacing all occurences of centos with fedora should work. Update: Jaldhar Vyas pointed me to mach, and Paul Wise to mock. Both packages are available in Debian, but use config files for each release shipped in the package. Unfortunately, both packages are out of date, and don t include Fedora 9 or newer. Also, mock doesn t support Centos.

Anyway, both packages could use a new maintainer. Don t hesitate to jump in!

16 September 2009

Lucas Nussbaum: Managing your PTS subscriptions

Subscribing to packages on the PTS is really useful to stay informed of everything happening with those packages. Unfortunately, managing your PTS subscriptions is really a challenge. Here is how I proceed to subscribe to packages I forgot to subscribe after uploading them: Some more info:
  • The PTS lives on master, in /org/packages.qa.debian.org.
  • The script that handles emails send to pts@ is bin/control.pl.
  • The spool dir for pending requests is spool/. The files are simple text files.
  • You can send multiple commands per email. Sending them in the subject might be broken. (at least it failed for me)
  • You don't need to take special care of the From for your emails. It's ignored (unless you subscribe without specifying an email address).

Next.

Previous.