Search Results: "lucas"

7 June 2008

Lucas Nussbaum: Datamining Launchpad bugs

One think that really is annoying with Launchpad is its lack of interfaces with the outside world. No SOAP interface (well, I think that work is being done on this), no easy way to export all bugs. The only way to get all the bug data in a machine-parseable is to first fetch this URL, and then, for each bug number listed there, to make another request for https://launchpad.net/bugs/$bug/+text. I filed a bug a few weeks ago, asking for a simpler way to get all the data. A Launchpad dev suggested to do what I just described (fetch all the number, then fetch the data for each bug). I originally dismissed the idea because it just sounded too dirty/aggressive/whatever, but since I needed to practice python, I gave it a try. And actually, it works: I was able to get all the data in less than an hour (but that probably put some load on Launchpad ;-)). That allows to write cool SQL queries. Bugs with the most subscribers:
select bugs.bug, title, count(*) as subscribers
from bugs, subscribers
where bugs.bug = subscribers.bug
group by bugs.bug, title
order by subscribers desc
limit 10;
bug firefox subscribers
188540 firefox-3.0 crashed with SIGSEGV in g_slice_alloc() 291
154697 package update-manager 1:0.81 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpjP6Bsx/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpjP6Bsx/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpjP6Bsx/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpjP6Bsx/backports/usr/bin/dpkg returned an error code (1) 278
141613 npviewer.bin crashed with SIGSEGV 262
59695 High frequency of load/unload cycles on some hard disks may shorten lifetime 182
215005 jockey-gtk crashed with AttributeError in enables_composite() 171
216043 compiz.real crashed with SIGSEGV 168
121653 [gutsy] fglrx breaks over suspend/resume 144
1 Microsoft has a majority market share 142
145360 compiz.real crashed with SIGSEGV 134
23369 firefox(-gnome-support) should get proxy from gconf 126
Bugs where someone is subscribed twice:
select bug, subscriber_login as cnt
from subscribers
group by bug, subscriber_login
having count(*) > 1;
bug subscriber
33065 mvo
48262 mvo
144628 skyguy
158126 benekal
213741 sandro-grundmann
216043 jotacayul
221630 kami911
(Yes, that forced me to change a primary key) Packages with the most bugs:
select package, count(distinct bug) as cnt
from tasks
group by package
order by cnt desc
limit 10;
package number
ubuntu 5392
linux 1464
linux-source-2.6.20 1034
update-manager 826
linux-source-2.6.22 724
firefox 684
kdebase 673
firefox-3.0 668
ubiquity 590
openoffice.org 566
Bugs with the shortest titles:
select bug, title, length(title) as len
from bugs
order by len asc
limit 5;
bug title length
190560 - 1
160381 uh 2
224350 css 3
133621 gnus 4
138052 pbe5 4
If you want to play too, you can fetch the SQLite3 DB (5.8M, lzma-compressed), the DB creation script, and the script that fetches the bugs and import them into the DB. Comments about my code would be very appreciated (stuff like “oh, there’s a better way to do that in python!”), as I’m not very confident about my pythonic skills. :-) Update: apparently, I’m not really fetching all the bugs. I’m getting the same results as when you just press “Search” on https://launchpad.net/ubuntu/+bugs. But if you click on “Advanced search”, then select all the bug statuses, and click search, you get a lot more bugs (154066 vs 49031). If someone know which bugs are excluded with the default search, I’m interested! Update 2: Got it. Apparently the default search doesn’t list bugs that have all their “tasks” marked “Won’t fix”, “Fix Released”, or “Invalid”.

27 May 2008

Christian Perrier: Reading blog summary

During the last 4 days, I didn't read Planet. So I started an interesting exercise and wanted to comment very briefly on a few entries I just read quickly to catch up. My Planet premium, so to say..

Lucas Nussbaum: Searching for cheap flights?

Dear readers, What are currently the best websites to look for cheap flights? liligo.fr is OK, but doesn’t allow to specify “this date is flexible”, and the listing of the results doesn’t provide a lot of info.

23 May 2008

Lucas Nussbaum: FOSSCAMP

Last week-end, I was in Prague for FOSSCAMP, a Canonical-sponsor event aiming at bringing together people from various Free Software projects. Such an event is a very good idea, especially after the openssl debacle, where we saw how difficult it is to build good relationships with other Free Software projects. The event was organized in a rather interesting way: the attendees make up the schedule as the event happens, by adding sessions to the timetable using marker pens on a whiteboard (see picture, hi Jorge!). If we have a spare BOF room at Debconf, it would be great to do the same thing: I always find it frustrating that many important discussions at Debconf happen outside BOFs/lectures, and are so easy to miss, simply because you submit talk proposals months before Debconf, so you can’t know yet what will be the hot stuff when Debconf finally arrives :-) It was also interesting to see all the different ways people organized BOFs. It might be interesting to write a list of DOes and DON’T about BOFs (not that the sessions weren’t of good quality!). Does anyone know if such a list already exist? And finally, as usual, it was great to meet all those people from this nice community again. If you still believe that some projects are fighting with each other, you need to attend such an event. And special thanks go to Ond ej ert k for guiding me through a visit of Prague!

16 May 2008

Ondřej Čertík: FOSSCamp, Friday

Since I live in Prague, it's basically compulsory to go to FOSSCamp. Yesterday I went with Lucas to some pubs + sightseeing, today we went in a larger group to this pub:

and we had a couple of good Czech meals with Plze beer:




Seems it tasted good:

13 May 2008

Lucas Nussbaum: No, we don t need a new openssl maintainer

DSA-1571 is totally embarrassing. But I disagree with Julien BLACHE: we don’t need a new openssl maintainer. Mistakes sometimes happen to people who do things. That sucks, but it’s unavoidable, no matter how many levels of checking you add. Kurt has done a lot of excellent work on Debian in the past years, and I’m sure he will continue. Of course, it’s a lot easier and less risky to write tons of stupid blog posts. By the way, Julien, there’s an RFH bug for openssl open for more than 2 years. What about getting involved and helping Kurt yourself? On a more constructive side: it’s not the first time that a Debian-specific change broke something (I can think of a recent grep change …). It might be useful to provide a simpler way to review those changes (reading the diff.gz files is not really user-friendly). We could have something like http://patches.ubuntu.com/ (or even something nicer :-).

8 May 2008

Stefano Zacchiroli: vcs distribution stats for packaging

Some more stats: $VCS distribution for Debian packaging I've set up yet another stat page, this time it's about the distribution of $VCS for Debian packaging. It's as trivial as you can imagine: it gets all the Vcs-XXX fields out of unstable Sources and plot how many packages are using a given $VCS. I've got no surprises in the relative popularity of $VCS: subversion is clearly the most widespread (with about 2700 packages on a total of about 13000) and git is growing (700 packages); with the exception of bzr (90 packages), all the other are used by less then 50 packages. Thanks to Lucas I've also included graphs in the page, as I think it would be interesting to monitor the evolution. (Probably as everybody) I'm confident to see an increasing trend for git balanced by a decrease of subversion, we'll see. The total number of packages using some $VCS is encouraging, we are at about 29% of the archive (you know that if your package is not declearing some Vcs- headers in its source stanza I'm not counting it, right? Go add the headers!). Interesting side effect: as I'm now maintaining a handful of these stat pages, I was pondering hey, we should create a wiki page with pointers to all the stat pages about Debian we have . Well, in fact it already exists: Statistics on wiki.d.o.

30 April 2008

Adrian von Bidder: Dear IRC user

Or should I say dear Lucas? Although this is more relevant for the people wanting to talk to Lucas on IRC. I recommend to use the leading edge technology set forth in rfc 2821 and 2822 for this mode of communication. I admit this is extremely experimental technology, but it might be worth looking at nonetheless.

Lucas Nussbaum: Dear IRC user

Please consider switching to screen+irssi, or bip+xchat, or irssi_proxy+irssi or xchat, etc. (This post and its comments has more details). It is very annoying when you ask me something while I’m away, then disconnect, and then when I finally answer you, you are not connected anymore. If I’m away and you are going to disconnect, please send your question by mail or jabber.

25 April 2008

Lucas Nussbaum: Various stuff

New QA website I modified qa.debian.org’s stylesheet/template, using the PTS’s stylesheet as a basis. It looks a bit better. The content was also updated, so we should stop receiving totally outdated answers to the “What does the QA team do?” question in NM. Now, who is going to do the same thing with www.debian.org? :-) Closing bugs in removed packages When packages are removed from unstable and testing, their bugs are not necessarly marked as closed, so they can’t be archived. A few days ago, there was about 3300 open bugs filed against removed packages. Thanks to the work of Barry deFreese, Marco Rodrigues and Raphael Geissert, we are now down to ~2500 bugs. If you want to help, just drop in #debian-qa and ask about our scripts/process. (There are some tricky details) DEP #1: NMUs With Bas Wijnen, we finally announced the DEP about NMUs we have been working on. Please join the (currently very quiet) discussion!

19 April 2008

Chris Lawrence: Principals, agents, and Debian

I’ve noted in the past that Debian has deliberately enshrined in its constitution some rather serious principal-agent problems. By and large this isn’t a bad thing, since there isn’t the consensus within the Debian community to support the “benevolent dictator for life” model of decision-making—if you want that, well that’s what Ubuntu and Daddy Warbucks is for. But it does mean that sometimes the caca hits the fan when a Debian project leader does exercise his powers, as our now-former DPL did earlier this week just before the end of his term of office (by my estimate, just over one hour and 27 minutes before). John Adams would be proud. So we have three related issues in my mind: In any event, congratulations to all the new Debian developers—and I’ll avoid pondering for too long why one person’s appointment to an unrelated group would suddenly break the logjam of developer application approvals.

18 April 2008

Jaldhar Vyas: L'affaire Fucktard

Hi, Julien, I agree that Debian is not dying and it was a bad PR move for Lucas to suggest it is, but what makes you think your response is any better from the PR perspective? I too have represented Debian at trade shows, LUGs etc. and I've had to deal with this topic before. My response is not to berate the holders of misinformation (and while I believe you when you say you were only aiming at Lucas, you used the plural so it would be easy for readers to be misled into thinking you meant multiple people.) but to emphasize that Debian is unique. Noone has conducted a social experiment of this type on this scale before and it is only natural for experiments to occasionally result in explosions and bad smells. Adopting this angle does not make us look bad and steers the questioner away from negative lines of thinking without belittling him. Much better PR don't you think?

Amaya Rodrigo: You people break my heart

Some come, others kind of go.

I warmly welcome the new 19 developers (great female ratio there!) and humbly ask the rest of us to support the new blood carriers. If they made it through this, they are surely worthy of our cause and will probably accomplish a lot more if us, the old farts, make it easier for the ones to come in the future.

Where do I join the Debian elderly club?

Julien Blache: Dear Jaldhar, Debian is alive and kicking asses.

Dear Jaldhar, I wrote the post you’re referring to knowing that only one person had been stupid enough to title his post “Is Debian dying?”, so before you go on writing I’m insulting a group of people (at least I’m reading your post this way), please do your research. Lucas’ post is about the worst PR we can imagine. There’s nothing more stupid to do than what he did. That’s the PR equivalent of committing suicide, mostly. It’s seriously hindering the work some of us are doing, publicizing Debian, going to trade shows, etc. It’s not only stupid, it’s hurting people who do this work. What’s worse, the post comes with comments from random nobodies, who have nothing to do with Debian, don’t have the first clue about how the Project works internally, yet they can tell that Debian is dying and grinding to a halt. Not to mention it’s been publicized yet again by some “journalist”. I’ve known Lucas for a long time now. I know where I stand. And I maintain my previous post in full, like it or not. Kthxbye.

Lucas Nussbaum: 19 new Debian Developers! \o/

I am very happy that 19 contributors who were waiting for their accounts, sometimes for a very long time, became Debian Developers today. This is great news for them, and for the project as a whole. Many thanks to all people involved for making this possible, including Joerg Jaspert, Steve McIntyre and James Troup. And congratulations to (using their account names) kibi, plessy, gregoa, goneri, tincho, akumar, filipe, miriam and the others I haven’t had the chance to work with yet. It also seems that the various pending issues (updating keys that expired, etc.) have been resolved, which is great news for several of our current DDs. But this doesn’t solve the DAM problem on a permanent basis. Something interesting about today’s events is that the account manager asked the system administrators to create the accounts, which is a nice way to offload part of the process. But the keyring maintainance is still a SPOF. A tool has been developed to allow multiple people to collaboratively edit the same keyring (and it’s used to maintain the Debian Maintainers keyring), but I’ve heard that some people weren’t satisfied with it, unfortunately. Let’s hope that this is solved soon, so the next ones to go through NM won’t have to wait that long!

17 April 2008

Jaldhar Vyas: Bitter New Maintainers Cling to Guns and Religion

For the second year in a row, I didn't vote in the DPL election. Not because I have lost interest in Debian affairs but because nothing is really going on that demands my attention. All three of the candidates who ran this year were eminently capable of representing of Debian and its ideals, all three had more or less the same vision for the role of DPL (IMO. See here for platforms,) and all three are, as far as I know, nice people. Organizational and social problems that previously existed have been fixed. The only problem I have with Debian these days is a lack of time but I can hardly expect the DPL to do anything about that. However, a recent post from Lucas reminded me that there is one group for which all is not fine and dandy. Given that this is the same complaint that has been made for atleast five years nows, one has to wonder why it remains singularly unfixable? Well I don't know but this delegation makes me confident that we will finally see the end of this last bottleneck too. Joerg is the one who sped up NEW package processing and I am sure he will have account creation humming along in no time. I sympathize with the frustration people stuck in NM feel, but I would like to remind them that Debian acts the way Winston Churchill observed the United States does:
"Americans can always be depended upon to do the right thing—after they've tried everything else."

MJ Ray: 21 today! MJR around the web...

Not done one of these round-ups for a while and I'm really pushed for time today, so here are some sites that I've written on:
  1. Property of a Lady Wicca on House
  2. Ross Burton: The End Of Homeopathy?
  3. Enough with the dried yoghurt covered raisins Korerorero: Just random ranting and raving
  4. How to host a free software advocacy event Free Software Magazine
  5. Raw Output: AGPL
  6. One for the Morning Glory: Facebook comments
  7. Sam Liddicott GPL3 Questions and Implications
  8. Drugs and an Election etbe
  9. New Tropicana images
  10. robmyers - Support BY-SA/SFDL Compatibility, Not BY-SA/FDL Compatibility
  11. Internet Psychology: Teenagers do not need our help online - we need them to help us oldies by Graham Jones, Internet Psychologist
  12. Wanting Your Opinions about Blog Comments and City Attorneys : David Lee King
  13. Zookoda - I Don't Recommend them Anymore
  14. Solar Water Heating :: ShowBlog
  15. Internet Psychology: Forget email - it's old hat by Graham Jones, Internet Psychologist
  16. Drake.org.uk: That's a wrap! Time to roll the end credits..
  17. Internet Psychology: Internet criminals are going to have a field day by Graham Jones, Internet Psychologist
  18. A Cambridge Co-operator: Rebranded Stores
  19. robmyers - Two Common Errors
  20. Lucas Nussbaum's Blog Blog Archive Where is the NM bottleneck?
  21. NM: FD is fixed - MadBlog

16 April 2008

Kartik Mistry: Fresh blood, Debian and India


* We need fresh blood! Yes. Like Lucas mentioned in his last post, along with Debian itself, many small teams and big teams are highly out-numbered and probably dying slowly. Currently, debian-in team has only two active members (jaldhar and if I count myself). We live on #indlinux at moment, which also leads to confusion about actual focus area of team. So, here are some clear text messages: - Debian-IN is team to work for ‘Indic’ packages as well as bringing new and fresh blood to Debian from India. - Its not true that we only work for fonts, we have many other packages: aspell dictionaries and festival-* packages and so on. Update: QA Page for Debian-In-Workers. Thanks Runa. - We aim to provide platform for upcoming DDs from India. Sadly, all DDs in India are highly isolated at moment. - Hopefully, we will get #debian-in at oftc. Update: Recovered ‘dead’ channel now. Thanks to Ganneff and h0lger for help. Come and join us!! Please note that we are considering developers only right now. We have already good numbers of users of Debian in India. kthnx.

Holger Levsen: 4 months and eleven days

I'm still ill with quite heavy fever, I feel like doing nothing, I'm even to weak to walk the dog properly... but he copes well and is great as usual :-)

Thinking about Debian doesn't make me feel better at all, reading through the comments of lucas post didnt help at all. Since 2000???! Gosh.

Unfortunatly the NM statistics miss two important data points: 1. people who made it thru NM and 2. people waiting for account creation. The second is only "good" to attribute blame, the first would be nice to have, so one could easily see, whether nowadays less people apply for NM or whether there are just less people in NM because the process is faster now.

I don't remember when exactly, but sometime in the past I resolved for myself to only blog positive things here, I'm seriously considering to drop this policy and poste a mean rant every day or so, either til Debian is really dead or those things are fixed or I am kicked.

Ironically it needs people to fix stuff, but yet most people in Debian are overworked. Maybe we should try to get more people in...

Besides fixing stuff and keeping up, there was also this thing called inno- what?

Also ironically I'm also and still very annoyed by whiners.

Guess I will look for a book or a movie now.

MJ Ray: Better Free Software Organisations?

Another zero-day announcement of a Software in the Public Interest online meeting has been posted. The announcement mentions "one motion has been raised" but the agenda doesn't include any motions, so I'm not sure what. Also, the agenda lists "Debian logo licence" as up for discussion but I thought last month's meeting resolved that. I watch SPI fairly closely and I'm confused. How about the rest of you? SPI isn't alone in this: many software organisations seem to suffer from similar problems. For example, I ranted in passing about Free Software Manchester yesterday, who just posted the notes from their own zero-day meeting and I've suggested possible ways of reforming debian's currently-stalled New Maintainer process more than once. Are free software users particularly bad at the basics of running an interest society (like welcoming and expiring members, calling meetings, publishing routine communications, and so on), have I been spoiled by cooperatives with their friendly Member Services departments or secretariats, or what? Is this why so many free software orgs seem to include self-perpetuating leadership groups? Is this a serious problem if, as reported, Software Development is a Team Sport [etbe]? Are there fully-working free software mass participation groups out there? I feel a lot of these problems are caused by attempting to order our inherently entropy-filled world completely and insisting everything follows petty rules, such as refusing to answer a question because the "wrong" member asked it. The world will not become less random just because hackers try to impose arbitrary rules. Sometimes it's good to put down minimum standards (because calling zero-day meetings is a mostly-avoidable way of excluding some members) but it will always be a poor alternative to trying to do the best you can for others. How do we get past this? My pro-cooperation-and-better-business platform for SPI board went pretty badly and I've had some anti-cooperative flames back from someone starting another free software group this month, so I don't think I can fix these existing organisations any time soon. About 1 in 6 people in the UK are members of a cooperative, so even if that is reflected among hackers (and I think it's lower), all of them would not be enough to reform much. One of the most common memes in free software is "show us the code" and the few other free software cooperatives I've seen have mostly failed, with a few surviving but hitting a size limit. As a result, I'm currently negotiating the start of a new free software cooperative. So far, I'm really happy with how that's going. Many cooperators learn at the feet of large consumer cooperatives like the Cooperative Group who run training courses for new members about putting cooperative values and principles into practice, which we smaller groups couldn't run ourselves. As a result, most cooperators already know how to work well together. Should large software societies like SPI try commissioning similar courses?

Next.

Previous.