Search Results: "sesse"

11 August 2007

Christian Perrier: How to not flash

Sesse pointed the Dell repository with Debian packages of their firmware tools. Out of curiosity, I installed the firmware-tools package, then identified my Latitude X1 BIOS as A03 and noticed that Dell now has a A06 released. So, I attempted to update it:
mykerinos:~# update_firmware --yes
Searching storage directory for available BIOS updates...
Checking system_bios(ven_0x1028_dev_0x01a3) - a03
        Found Update: system_bios(ven_0x1028_dev_0x01a3) - a06
	
	Found out of date packages.
	
	Running updates...
	Installing system_bios(ven_0x1028_dev_0x01a3) - a06
	Traceback (most recent call last):
	  File "/usr/bin/update_firmware", line 226, in ?
	      sys.exit( main() )
	        File "/usr/bin/update_firmware", line 160, in main
		    ret = pkg.install()
		      File "/var/lib/python-support/python2.4/package.py", line 51, in install
    return self.installFunction(self)
      File "/var/lib/python-support/python2.4/package.py", line 24, in defaultInstallStrategy
    raise InternalError("Attempt to install a package with no install function. Name: %s, Version: %s" % (self.nam                e, self.version))
package.InternalError: Attempt to install a package with no install function. Name: system_bios(ven_0x1028_dev_0x0                1a3), Version:
a06
No luck, then..:-) I'll check this more carefully when back from holidays. Anyway, updating my BIOS before leaving is probably not a good idea..:-)

19 July 2007

MJ Ray: zugschlus becomes asuffield

Marc 'Zugschlus' Haber:
"I think I'm going to stop being responsive to users. They're not worth the blood pressure."
Andrew Suffield:
"But realistically, all that is fairly minor compared to the number of idiot users, idiot developers, kooks, luddites, zealots, managers, politicians, and self-obsessed fools that everybody has to deal with in the free software world."
I think I have a new source of blunt put-downs.

21 June 2007

Joey Hess: daytrip pics

I've selected some pics from Sesse of the day trip to Bute island yesterday for those following this from home. Including my first ever gratutously tourist-like pose-against-the-background picture in a foreign country. Now on with DebConf!

19 June 2007

Mark Brown: Debian giving back

Rumors reach me that people from the Forest Cafe next to the night venue are so impressed with what has been done with the organ in the night venue that they’re planning to incorporate some organ music into some of their performances.

28 May 2007

Eric Dorland: The Ghost of Browser Past

Even though Iceweasel has been a reality since November, it seems that there is still some backlash about the rename. Thanks very much to Andrew for jumping to my defense (and also for organizing dinner the last time I was in Mountain View, it was a fun evening). Nothing he said was fundamentally incorrect, but it doesn't paint the full picture.

Once upon a time (somewhere around Firefox 0.9) we happily shipped the fox hugging the globe icon. Then it was pointed out the copyright license on that piece of artwork wasn't DFSG free (and probably wouldn't be free under any reasonable free software or even open content license), so we removed it and used the plain globe icon they shipped in the tarball instead. Eventually the Mozilla Foundation asked us to remove mozilla- from the package name (it was mozilla-firefox at the time) which we did, and the issue of the icon and trademark came up. After explaining why we couldn't ship the icon they gave us permission to continue to use the name. They said they would periodically check up to make sure we weren't shipping crap that would harm the brand. This seemed a fairly good compromise and we accepted.

This situation persisted for a year or so, in both Debian and Ubuntu, but then the Mozilla Corporation (who was now in possession of the trademarks) insisted we couldn't use the name without the non-free logo. They also wanted to approve any changes made before they were uploaded. They are certainly within their rights to do this, but to hear Mr. Fowler tell it we were on a crusade to purge the name from the distro. We were not, we were content with the status quo. I also must take exception with Mr. Fowler stating: "They've persisted, despite the best efforts of the Mozilla project team to engage with the Debian packagers to resolve the situation." I think from the discussion we were trying our best to reach some sort of compromise and the Mozilla side seemed firmly entrenched in their position, not offering us a lot of alternatives. The non-free nature of the logo and the unprecedented "control-freak" review process didn't leave us with a lot of alternatives.

Ubuntu does ship the officially branded version of the Firefox, but they have a weaker set of freedom guidelines than Debian. Whether you think that is good or bad is personal choice, but one of the reasons I like Debian so much is its commitment to free software, even if that means not everything is as easy or expedient as one would like.

With respect to the new name and icon, this is again a matter of personal taste. I do tend to think "Iceweasel" doesn't have that much sex appeal but it was a popular choice and had the benefit of having already been used to refer to a potential name fork of Firefox. And BTW this is really only a name fork, the amount of changes we've actually put in to the tree (beyond renaming ones) are minimal. In fact the last time it was checked, our patches were a strict subset of the patches Ubuntu uses in their Firefox package. So Iceweasel is in fact functionally identical to Firefox with what I like to think are some minor improvements from upstream.

As to your other points, I will admit to being poorly-socialized, but I think most who have met me wouldn't call me self-obsessed, egotistical or a moron.

I think Debian is developing a bit of a bias against it where we're assumed to be a bunch of crazy Free software nuts, and the presumption is anytime we act against the grain we're the ones being unreasonable despite any evidence to the contrary. I don't know how we can fight this perception, but I think we should.

21 May 2007

Stefano Zacchiroli: i had a dream

I'm Going to Play Some Number at the Lotto The Lotto Game is a really popular gambling game in Italy, run by the state itself. As in all good gambling game: you, the player, can win a lot of money while who is running the game (the Italian state in our case) will win a lot of money for sure, no matter what. Anyhow, to the facts, it's a well-known folklore that people win playing Lotto FOR SURE by playing numbers told while dreaming by parents, friends, kitties, whatever, ... As a scientist, I've no reason not to trust this folklore, why should I? As a strange coincidence (another fact that strongly hints I HAVE TO PLAY), this night I had a dream (well, it was more this morning while reading the planet, but it doesn't really matter..., folklore is folklore!). There were a lot, really a lot of people whispering this to my ears:
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

well, ok, they aren't in decimal notation, and they aren't even comprised between 1 and 90, ... but what would you expect from a bunch of geeks??? They are probably trying to exploit some overflow in the hands of the lotto extractor or something like that... But I won't desist, I'll play those number! Open questions: any proficient Lotto player to answer them around?

Wouter Verhelst: Grm(b)l

It's been pointed out to me ages ago that you should not just buzz about some shiny new software and expect people to know what you're rambling about. So, for the benefit of those of us who haven't got a clue: could you please explain what grml is? Thanks,

16 May 2007

Evan Prodromou: 26 Flor al CCXV

It's been a busy week here and I've been lax in updating my blog. It's probably a good thing to put on the chopping block -- of all the possible things going on in my life -- but I'm regretting not keeping up with it. We had a good weekend last weekend. Maj's Mother's Day present request was to clean out all our closets in the house and take extra clothes to the Petits Fr res up the street. It took most of the day Saturday, and we finished with twelve garbage bags full of clothes for the Fr res. Check out Maj's photo of the pile of clothes. Sunday morning Amita June and I made Mama a nice breakfast of waffles and (tofu) sausage. Amita's job was to stir the batter (which she did a good job at) and not to touch anything hot (not so good). That afternoon, Maj went to get a haircut at the salon down the street, and I took the opportunity to give Amita June her first haircut. I think she looks like Twiggy. This week has been a maelstrom of activity. We have RoCoCoCamp coming up on Friday, and we're still tying all the loose ends together. I had most of my tasks done yesterday, so at the organizational meeting last night I saddled myself with more. D'oh! I think my main work this week is going to be encouraging local Montreal tech scenesters to come. I especially want to make sure that important women in the local Internet scene are present, so I'm going to copy Hugh McGuire's invite for BarCampMontreal2 and do some link-baiting: tags:

Interview There's a really good interview with me and Maj on the Internet Brands Developer Blog. It's gotten into the short list of interviews I point press to when they want background about Wikitravel -- along with the Creative Commons interview. I'm really glad that IB has started this blog to give the outside world a peek at what's happening out there in El Segundo. And it's also a great way for IB to highlight some of the Open Source work they're doing, like the neat-o new AJAX tool kit IBDOM. tags:

3 May 2007

Stefano Zacchiroli: i had a dream

I'm Going to Play Some Number at the Lotto The Lotto Game is a really popular gambling game in Italy, run by the state itself. As in all good gambling game: you, the player, can win a lot of money while who is running the game (the Italian state in our case) will win a lot of money for sure, no matter what. Anyhow, to the facts, it's a well-known folklore that people win playing Lotto FOR SURE by playing numbers told while dreaming by parents, friends, kitties, whatever, ... As a scientist, I've no reason not to trust this folklore, why should I? As a strange coincidence (another fact that strongly hints I HAVE TO PLAY), this night I had a dream (well, it was more this morning while reading the planet, but it doesn't really matter..., folklore is folklore!). There were a lot, really a lot of people whispering this to my ears:
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

well, ok, they aren't in decimal notation, and they aren't even comprised between 1 and 90, ... but what would you expect from a bunch of geeks??? They are probably trying to exploit some overflow in the hands of the lotto extractor or something like that... But I won't desist, I'll play those number! Open questions: any proficient Lotto player to answer them around?

Erich Schubert: Magic numbers

When reading this number
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
I thought it was the fingerprint of a GPG key.The first time I came across it, it was encoded in a puzzle; not a particularly difficult one (what key is inbetween of F8 and F10 on your keyboard?).Turns out that this number can be used to decrypt most HD-DVDs produced so far.No, you can't really think you have a copyright on this number? You could have it as a registered trademark, I guess. But I think everybody will be using it to refer to you. :-)From a crypto point of view, it was just a matter of time until this number leaked out. And in fact, the HD-DVD encryption was designed to handle this cases (but it wasn't used correctly). Face it: cryptographers have been telling you right from the beginning that your encryption will be broken by it's very nature (remember: you are shipping decryption keys worldwide in your HD-DVD player devices).[Update: others thought it might be an IPv6 address maybe?][Update #2: Google thinks there are about 300k pages with this number. Maybe we can stop this meme now? :-)][Update #3: it was pointed out to me that nobody claimed to have copyright on this number, but that it is a device to cirumvent encryption and thus violates the DMCA. And that this is similar to distributing magic markers that could be used to 'crack' a famous CD protection used by Sony some time ago...]

1 April 2007

Biella Coleman: The Joy of Weather, Writing, Music, and Software

Spring has arrived in many parts of North America. But in Edmonton, North America’s largest and most northernly city, spring has sort-of-come-but-not-really as it recedes fairly quickly. There will be a day of explosive warmth (you know, a balmy 45-55 F) and of course locals strip down to near nakedness, wearing shorts and, the more flamboyant will don an 80’s inspired cut-off tee. Hot. This sartorial statement says WE are SO ready for the long winter to leave … for good. Despite the collective sentiment, which is probably shared by 99.999999% of Edmonton’s inhabitants, the winter cold, snow, and breeze are indifferent to our deepest pleas and they come right back, making us sport at least a few layers of winter clothes. Within this dance between winter breeze and spring warmth, I have spent most of my time staring at my computer doing everything possible to transform half-baked ideas, hunches, sentiments, and theories into coherent words, sentences, paragraphs, and chapters for my book. I am working on it full-force and am enjoying it more than I have in a year though from time to time I get fed-up, lost, sick of it, and my writing soul descends back, deep into one of Dante’s infernal rings, where I fester with my frustration, convinced that I should have become an organic flower farmer/acupuncturist that I almost became (well not really, but I have always fancied that combination as an ideal and fulfilling career path). Slowly I usually make my way back up, brush off the cobwebs of despair, and proceed anew. Within this highly secluded life of monastic-like repetition, thankfully, I have been enjoying some new things this spring. Once a week I head over to an University of Alberta off-site library facility to pour over archive material for a new project, which I am not going to talk about here (it is super-duper-top-secret) but it has been interesting working at an archive, especially one that is housed in an old Ikea. Since I am one of those right-brained people, I like to listen to music while I work, and lately I have also become pretty obsessed with house & electronic music, mainly thanks to a local DJ, David Stone whose weekly radio show on CJSR, BPM, is simply the bomb. He claims to bring the latest and greatest of electronic dance music from around the world and I think he is totally right. If you like this type of music, do catch his weekly show on Sat nights at 6 PM (MST). I sometimes get a little sad when I listen to some good music or see some stellar performance because it reminds me that what I may one day have to offer to the wider world an academic book and article here and there simply cannot bring the type of joy that musical performance and other creative expressions can bring. While you can listen to songs and over again, a book, if it is really superb, may attract a second or third reading. An academic book or article may at times light an inner light of joy, but let’s face it, it is usually a pretty cerebral light oh’ joy, leaving untouched those part of the brain, soul, heart, where more visceral, mysterious, yet fully self-enveloping feelings of joy reign high (but I am trying my hardest to stick a funny section or two in every chapter to leave a trace of laughter because if I can’t manage that with an ethnography on hackers, I will have failed miserably). Every track David Stone plays is something I want to listen to over and over again and thanks to mplayer stream dump function, I can. And funny enough, is that in the last month software believe it or not has brought me much joy as of late. I have been using free software since 1997 and I used to get A LOT more annoyed no make that a downright frustrated with programs (or lack of programs) than I do now. In fact, now, I am simply stunned whenever I upgrade to a version of a program. For example, Word Press 2.0 is like so much nicer in terms of usability and functionality than 1.5. The same goes for Open Office, the Gimp, and even Firefox, which has some bugs, but is so much better than its predecessors. I once described free software using the well-worn clich as “the gift that keeps on giving. And I think that this is becoming more and more true. And like wine, with the passing of time, these gifts usually get better and better. And like a unexpected present that arrives on your doorstep, these software packages induce some joy, because it is actually pretty neat to see these programs develop and grow into something stronger and more useful; so thanks to those who spend their time hacking away at making and improving this software and thanks to those (you know who you are) who helped with my recent WP upgrade!

21 February 2007

Gunnar Wolf: Dell laptops without Windows? No, not yet

Steinar: You can get some (few) Dell desktop models with no preinstalled Windows, IIRC they are called the L series . I tried, however, to get a OS-free laptop. I had to buy my XPS M1210 (sweet machine, BTW) with Windows XP. Tried on the phone, yes.

8 February 2007

Steinar H. Gunderson: Gngngn

Don't you just hate it when you pick up some software, start using it and immediately crop into three distinct bugs? Today's frustration is brought to you by ESR. Our motto: It's not my design that's broken, it's the equipment. And if you try to add configuration options to adjust better to the equipment, I will refuse your patch.

2 February 2007

Amaya Rodrigo: Sender verify callouts *are* evil

Steinar H. Gunderson wrote:
> Who the heck is uceprotect , and should anyone care?
> At least they obviously don t have much idea how sender verify works,
> as you can see from their page on the issue...


Well, as I can t properly or reliably communicate with the Debian project via email anymore, I was about to allow sender verify probes on my side, but after reading what the Postfix project has to say about it, together with the uceprotect people, who look quite harsh, but otherwise reasonable to me... I say no way. Who the heck is postfix , and should anyone care? At least they obviously have a clue about how sender verify works, as you can see from their page on the issue...

I am sick of changing configuration in my (otherwise) almost perfectly working smtp server, specially if I am opening my postfix server to a potential DoS. From the link above:
The sender/recipient address verification feature described in this document is suitable only for low-traffic sites. It performs poorly under high load and may cause your site to be blacklisted by some providers.

Is Debian a low-traffic site? I am feeling cut out from the project, as I can no longer email certain (not all) developer@debian.org accounts, bug numbers in the BTS (control still works), and Alioth mailing lists. I refuse to misconfigure my email server because of this. This is plain stupid!

Greylisting was a minor nuissance. This is $FILL_IN_WITH_CURSE_OF_CHOICE:
~-root@aenima>mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
A57EB890041 1173 Fri Feb 2 19:52:34 xxxxxx@amayita.com
(host lists.alioth.debian.org[217.196.43.134] said: 451 Could not complete sender verify callout (in reply to RCPT TO command)) xxxxxx-pkg-base-maintainers-request@lists.alioth.debian.org

Spammers have already won. I hereby proclaim email officially dead.

1 February 2007

MJ Ray: Debian: No Mail Today

As far as I can tell, I was not getting any email from debian.org because master cached a bogus MX record for phonecoop.coop. Update 2: superstar DSAs stroked the right widget so email should start flowing again. I think I can't email anyone at debian.org or lists because debian uses sender verify. Update: It seems that debian.org's use of sender verify means debian will get blacklisted. An anonymous commenter posted:
"I'm arguing against Debian admins using Sender Verify because it's evil. Even uceprotect will list them if they caught a mail from them: http://www.uceprotect.net/en/index.php?m=10&s=0"
Update: Steinar H. Gunderson - Sender verify says we shouldn't care.

14 January 2007

Ian Murdock: On the importance of backward compatibility

I’m often asked why I’m so obsessed with backward compatibility and, as a result, why I’ve made the issue such a central part of the LSB over the past year. Yes, it’s hard, particularly in the Linux world, because there are thousands of developers building the components that make up the platform, and it just takes one to break compatibility and make our lives difficult. Even worse, the idea of keeping extraneous stuff around for the long term “just” for the sake of compatibility is anathema to most engineers. Elegance of design is a much higher calling than the pedestrian task of making sure things don’t break. Why is backward compatibility important? Here’s a great example, via Joel Spolsky (note: from 2004):
Raymond Chen is a developer on the Windows team at Microsoft. He’s been there since 1992, and his weblog The Old New Thing is chock-full of detailed technical stories about why certain things are the way they are in Windows, even silly things, which turn out to have very good reasons. The most impressive things to read on Raymond’s weblog are the stories of the incredible efforts the Windows team has made over the years to support backwards compatibility: “Look at the scenario from the customer’s standpoint. You bought programs X, Y and Z. You then upgraded to Windows XP. Your computer now crashes randomly, and program Z doesn’t work at all. You’re going to tell your friends, ‘Don’t upgrade to Windows XP. It crashes randomly, and it’s not compatible with program Z.’ Are you going to debug your system to determine that program X is causing the crashes, and that program Z doesn’t work because it is using undocumented window messages? Of course not. You’re going to return the Windows XP box for a refund. (You bought programs X, Y, and Z some months ago. The 30-day return policy no longer applies to them. The only thing you can return is Windows XP.)” I first heard about this from one of the developers of the hit game SimCity, who told me that there was a critical bug in his application: it used memory right after freeing it, a major no-no that happened to work OK on DOS but would not work under Windows where memory that is freed is likely to be snatched up by another running application right away. The testers on the Windows team were going through various popular applications, testing them to make sure they worked OK, but SimCity kept crashing. They reported this to the Windows developers, who disassembled SimCity, stepped through it in a debugger, found the bug, and added special code that checked if SimCity was running, and if it did, ran the memory allocator in a special mode in which you could still use memory after freeing it. This was not an unusual case. The Windows testing team is huge and one of their most important responsibilities is guaranteeing that everyone can safely upgrade their operating system, no matter what applications they have installed, and those applications will continue to run, even if those applications do bad things or use undocumented functions or rely on buggy behavior that happens to be buggy in Windows n but is no longer buggy in Windows n+1… A lot of developers and engineers don’t agree with this way of working. If the application did something bad, or relied on some undocumented behavior, they think, it should just break when the OS gets upgraded. The developers of the Macintosh OS at Apple have always been in this camp. It’s why so few applications from the early days of the Macintosh still work… To contrast, I’ve got DOS applications that I wrote in 1983 for the very original IBM PC that still run flawlessly, thanks to the Raymond Chen Camp at Microsoft.
I can almost feel the revulsion among my readership right about now. However, next time you’re in Best Buy or CompUSA, look at the shelf of Windows applications, then compare it to the shelf of Mac applications, and perhaps you’ll better understand why it’s important. Beyond the results speaking for themselves, I’ll argue that it takes a better engineer to move a platform forward while at the same time making sure things don’t break. It’s pretty easy to wash your hands of something and declare it to be someone else’s problem.

24 December 2006

Erich Schubert: Website meta langauges

Zack asked for website meta languages for redoing his homepage. Well, I redid my homepage last february, using XML and XSLT. A monster XSLT stylesheet, because I wanted to keep my template outside of the stylesheet. I can not recommend XSLT. Using it for templating is quite messy. XSLT is okay if you want to transform one representation of the data to another; it's not if you want to add a lot of surrounding markup and things like a sitemap and similar navigation tools. This is next to impossible in pure XSLT, it gets better once you have some extensions (dubbed EXSLT, and supported by pretty much any xslt processor) or maybe with XSLT2. String manipulation is also a pain (at least with XSLT1); I gave up on generating a nice "last modified" date from my subversion tag. Supposedly XSLT2 has some functions that could make this easier (i.e. for parsing and printing datetime information), but the common approach with XSLT is to only supply the required minimum of function you need, and I'm not aware of an easy way to add custom functions, not to mention any large standard library that can efficiently be used (which is the true strength of Java, Python and C#, that they bring a huge collection of pre-written ready-to-use code with them). Of course there are some efforts to write XSLT libraries (especially for XSLT2), and this aforementioned EXSLT is some kind of standard library that even might be efficiently implemented in some interpreters - you can't rely on it to be there and to just work. XSLT isn't useless, but when it comes to presenting data to humans or writing clean, compact code it's not satisfactory at all. I'd give you my Makefile and XSLT file, if they weren't that messy... too many features; I'm generating two languages, a partially expanded navigation menu, etc. - my XSLT is 10k, my sitemap currently 4.5k, the template file is 5k. Anyway. Half a year ago, my favourite templating language was KID templating. I used it for some small projects such as my DNSoupdate tool to edit DNS zones via the DNS protocol (requires a nameserver such as bind which has support for DNS update, uses encryption). It was a perfect match for such tiny pages, but I'm no longer that convinced I still like it for larger projects. What's good about Kid: XML templating language, Python based, easy to use in whichever way you want by writing a few lines of python (i.e. easy to write a Makefile to generate a static version of you homepage) What's not good about Kid: only works with a Python interpreter. I'd prefer to have a templating language that can be used from multiple languages. However the Kid syntax relies on Python, which is really bad. Also I'd prefer to have some component-render model for more complex websites. The current setup is IMHO okay if you have one default layout and one content layout; but if you have multiple components that could be combined differently on the pages, it gets too messy. With my turbogears experiments, Kid was also not very performant (but that might as well be Turbogears fault). Right now, I'd probably still go with Kid. But I've been having a look at JSP 2.1, and JSF / Facelets in particular. There are some things about facelets that I really like (for example, that they use a proper XML syntax, instead of this bastardized almost-XML that JSP usually (ab-)uses). There is also some stuff that I don't like (e.g. the massive overengineering of everything surrounding it), and I have no idea how easy it will be to generate static pages in a scripted fashion, i.e. using it without a real webserver. Or I might just write it all in python, which is a nice language for manipulating XML, usually. Please don't just send me an email with your favourite templating engine. Like zack, I'm only interested in XML-based templating engines, which does not apply to most templating solutions out there. Clearsilver for example is another bastardization of XML. I'm aware of TAL/METAL, and find them quite interesting, but they were also not having this kind of componentization that I'm usually thinking in. [Update: some people have pointed me to Genshi, which is mostly Kid compatible. However, it still has mostly the same problems, e.g. the templates being not reusable in other languages than python, and that certain constructs are a pain to do (e.g. the page_specific_css recipe with more than one css file). Others have pointed me to smarty, but it's string-based and doesn't ensure valid XML output. (Which is very useful for e.g. generating atom or rss output) For example this is probably valid in smarty: if 0 <b> /if </b> - allowing errors is bad. Oh, and smarty is PHP, which is broken by design, a no-go. The best match to my ideas so far is XML::Template (for Perl, Python, Ruby, PHP) which is pretty close to what I've been doing manually when not using a templating solution. I don't know yet how well it handles recursion - I need recursive templates for the navigation menu on my homepage.]

18 November 2006

Riku Voipio: cdbs: empathic maybe

I tried to ask our cats if they felt threatened by CDBS. They didn't seem really worried.

I'm not sure if it is entirely fair to blame CDBS for complex packaging issues. If CDBS was not available, more maintainers would just cook up their own spaghetti packaging scripts. The balance needs to be somewhere between "everyone reinventing the wheel" and "frameworks that are harder to use than the raw stuff". Currently I would recommend only using CDBS for simple packages.

Sven Mueller: CBDS and kittens

Steinar H. Gunderson wrote about CDBS once again, and I couldn’t agree more. CDBS introduces a lot of complexity for non-trivial packages, and it especially is basically undocumented. So what is CDBS’s value? For non-trivial packages, it is hard to use, since you basically need to decipher the CDBS code. For trivial packages however, it doesn’t add much value over dh_make. That’s actually sad: I like the general idea behind CDBS, but it is implemented badly IMHO. What it should do, if implemented right is to automate anything you want done on an easy package while providing and documenting (which includes consistently named hooks and options) all the interfaces needed to maintain non-trivial packages. Ideally, this would even include packages which need multiple build runs (like providing two differently configured versions of the same binary in two packages). But as said: It would need consistent names and proper documentation, and CDBS fails both currently. I however hope this improves in the future. Don’t ask me to work on this however, since personally, I’m quite happy using debhelper on my packages, since it is removing complexity (not typing work or lines of code) from debian/rules while keeping it obvious from that file what is done during a build. I would really like to see the reasoning from Erich on why he thinks CDBS is NMU-friendly, since I don’t get why he thinks so from his blog post.

17 November 2006

Steve Langasek: On setting and meeting goals, and statistical fun

While NMUing plays an important part in getting us to a release, as shown by the thousand or so fixed-in-NMU RC bugs that we recently cleaned up the BTS state on, it's evident after doing this whole release-managing thing for a while that there is a very high (non-linear) correlation between the age of an open RC bug and the likelihood that a release manager is going to have to touch it at some point in order to get it fixed. By and large, maintainers really do a good job of fixing their own packages, which is probably something we don't say enough - maybe 75% of all RC bugs, I'd guess, will (or would) get fixed by maintainers in the first week without anyone needing to poke them about it, and of the remainder, probably another 80-90% get taken care of by BSPers and serial-NMUers like bug-a-day mascot Steinar Gunderson. That's why I'm not bothered overly much by the idea of full-archive searches for hidden RC bugs, like Lucas's piuparts tests, affecting the release timeline, because I know that 95-98% of those bugs are going to be gone two weeks after they're filed anyway, especially when they're no-brainer fixes to maintainer scripts or dependencies. But then that leaves the other 2-5%, which are the ones nobody else has fixed. And why hasn't anyone fixed them? Because they're the hard ones, of course... So although I follow the debian-bugs-rc list and occasionally swat a few non-bugs closed to save the maintainers time, and also provide some nudges when it looks like a package is causing RC bugs to be filed on other packages, my goal for the last full week of my Dunc-Tank contract was to get the count of etch RC bugs unfixed in unstable that are 20 days old or older down from around 50 to under 30. This seemed a reasonable goal, since it had been at 80 the week before, and it would go a long way towards helping the real blockers on the release. Initially I was aiming to bring down the count of RC bugs unfixed in testing that are 20 days old or older to this number, but quickly realized that this wasn't going to be realistic because it depended too much on the autobuilders all operating optimally and there wasn't time to both help fix 20 of the hardest RC bugs and handhold 60 RC bugfixes into testing in one week. In the end, we did miss this lesser target by a day or two. Still not a bad week's work, given that I'm pretty sure I fixed about 20 of these bugs myself in that time period (through NMUs, removals, and analysis+downgrades) and they seem to average 3 hours of work for a fix. And we've been holding at or below 30 on this list of bugs since then, so we're successfully keeping up with new bugs aging past the 20-day mark, which is also a good sign. Unfortunately, I seem to have left myself to fix the alpha Xorg 7.1 bugs on my own time. :) By now the announcement has made the rounds that the release team doesn't think we can hit the Dec. 4 target date because more time is needed for a final release candidate of the installer. Does that mean that RC bugs were the wrong thing to be focusing on for the past weeks? Well, no; if you want one place in Debian where Brooks' Law holds, I think you'll find that getting a d-i release out is it, and we still have a hard road ahead to make sure we do get our other RC issues sorted out in the same time frame. The installer just happens to put a lower limit on a release date, we still have an opportunity to screw it up from there. ;) At least the statistics suggest that we're going in the right direction. Only 13% of RC bugs fall into the "20 days or older and unfixed" category. Half of all RC bugs over 10 days old have a fix of some kind in unstable, and 64% of all reported RC bugs are less than 10 days old. We'll see whether this graph backs me up on this in a couple more days.

Next.

Previous.