Search Results: "ag"

20 December 2006

Jonathan McDowell: Wedding writeup

I've been sitting on this for a while, gradually adding more bits as I think of them. So it's a bit long and rambly, but if I don't post it now I'll never get round to it. First, the details, for anyone who cares. I got married to my partner of 11 years, Katherine, on 1st December. This was actually our 11 year anniversary. We had a civil ceremony in The Assembly House, Norwich with a wine reception afterwards, then moved on to Wolterton Hall for the main reception, with a magnificant feast provided by Brasteds. Afterwards there was a chocolate fountain courtesy of Digby's and Nero thanks to Milton. The wedding cars were provided by American Dream (we had the Excalibur Sedan and the Lincoln Town Car). The bus to/from the reception was from Dolphin Autos. Robin Phillips brought the band. Wonderful purple jacket + the other suits were from John Field Formal Hire. Next, some photos. Burly Dave Ganesh Paddy Steve Tim (Ceremony) Tim (Reception) Finally, some things I've learned. For guests (I wish someone had told me these - Katherine says I sound stroppy but I don't mean to): For couples getting married:

Jesus Climent: I could not agree more

More here

Josselin Mouette: Erich Schubert should read constitution 2.1.1

Erich Schubert's pastime seems to be accusing others of trolling and FUDing (a politically correct buzzword that actually means lying) while contributing to these trolls and spreading lies himself. I had warned I would reduce my involvement in the project if dunc-tank was started. I reduced it much less than I could, probably much less than I should. I had warned that maintaining libpng required a high profile developer with time and motivation, and I had lost the latter. Basically, the dunc-tank cabal chose to ignore such warnings - as well as similar warnings given by other developers - and thought they could do better without us. Fine. I didn't do anything to prevent libpng from being maintained, and yet you see the result. Trying to put the blame on me for this disaster is simply outrageous. Sure, I have my share in this disaster. Just like you, Erich. You and all others who didn't work on libpng for this time. You let a junior maintainer try to deal with a complicated package, and you let him fail, like every one of us would have failed when we were new in this project. Now, if you really think that: was being childish, there's nothing I can do to help you, as the kind of help you need has nothing to do with computing. What I have learnt in the meantime, though, is that most people in the project are really able to appreciate any kind of help, which is why now, I won't let myself be hurt by those few who spend time insulting other developers rather than maintaining packages.

MJ Ray: SPI gives away opensource.org and opensource.net

For various reasons, Software in the Public Interest (SPI) owned the domains opensource.org and opensource.net, which have been managed by the Open Source Initiative (OSI) for most of their life. This supported various SPI goals and also gave a possibility of community control of opensource.org/net just in case it was ever needed. OSI does not offer much opportunity for community control, as it is a self-appointing board. (Regular readers may remember that the principles of democratic member control, autonomy and concern for community are important to me.) I was watching as the SPI board voted in favour of giving away the opensource domains, proposal 2006-11-18.dbg.mjs.1 on the agenda. The vote happened without any discussion in the meeting. From memory (I guess logs will appear on the SPI site eventually):- David Graham ("SPI must also be involved in the promotion of and education about open source") proposed and voted for this action that stops SPI being involved in this promotion and education about open source; Michael Schultheiss ("I look forward to SPI's future expansion") (amended and?) voted for this action that reduces SPI; Neil McGovern ("achieve a greater degree of involvement [...] from the community in general") voted for this action that lessens SPI's involvement; Jimmy Kaplowitz ("It is important that it continue holding in trust the money and other legal assets belonging to its member projects [...] fulfill some more of its stated corporate purposes, involving education of the general public about free software and about computers in general") voted for this action that drops these assets and reduces involvement in education of the general public; Bdale Garbee ("would like to close this issue one way or another, once and for all") seemed willing to vote for anything which prevented further discussion - of course, only surrendering the domains could close it once and for all, as this is a one-way trapdoor topic - but had apologised for absence from the meeting; Martin "Joey" Schulze had apologised for absence from the meeting; Josh Berkus (nothing obviously relevant in his platform) abstained - consistent but disappointing; I think Branden Robinson was missing. Ian Jackson ("SPI's role is to provide a stable legal entity which can hold assets") voted against this action so that SPI would keep holding these assets. Bravo! Sources: The quotes above are the board's own promises in their election platforms, as listed on the SPI site in 2003 2006 apart from Bdale Garbee's platform which wasn't at the link given in 2004 so that quote is from the minutes of the previous meeting If some board members are willing to give away assets for no good reason, that strikes at one of SPI's core methods: holding assets for the community. What can we trust about this board? Their platforms are full of fine sentiments, but how do their actions reflect their platforms? This may be a mostly-dormant issue until the next election. If you want any of SPI's assets, just ask. If your request is rejected (as SPI rejected the opensource domain give-away before), just keep asking new sets of voters until they agree.

Stefano Zacchiroli: ls2rss

ls2rss AFAIK amule is missing notification of completed downloads. In addition to that, me and Godog are sharing the same amule instance and it's cool to be notified of what the other downloaded, it's a bit like the for:someone tag on del.icio.us. As an issue of my hack of the day series I hence implemented ls2rss.py. The name is telling: given a directory it generates a corresponding RSS feed. It's written in python, it's meant to be run as a cron job, and takes care of minor details like remembering files that have been deleted since the last invocation and enforcing a threshold to the feed size. I was unable to find anything like that already available on the net (the one available here is not available for download any longer). In case of need, try mine. Download

Evan Prodromou: 28 Frimaire CCXV

Big week for me in and around the media. Huzzah for fame and fortune!

Web 2.0 APIs I'm really happy that an article I wrote for Linux World on Web APIs for software development was published. Called Ten Web 2.0 APIs you can really use, it covers the APIs available today that are really useful for more than just gee-whiz mashups. I'd covered a few of the services when I did a story for LW on the Web 2.0 Summit, so Don Marti asked me to follow up with a full rundown on the world of Web APIs right now. tags:

Wikitravel on the AP wire On the other side of the media lens, Wikitravel is one of the sites featured in an article on the API wire by Anick Jesdanun called Travelers contribute to online guides. Although the article covers a lot of other travel sites, and even has some sour grumpiness by proprietary travel guide publishers, I think it's very favorable to Wikitravel. tags:

Thanks, Tom Also, it was nice of Tom Brown from Stuffopolis in talking about his OpenID Podcast to say that the OpenID extension for MediaWiki is "excellent". Gawrsh! tags:

Felipe Augusto van de Wiel: 20 Dec 2006

Just for the record!

[*.cloud.*]
Alive. Birthday. Happy. Sad. Changes. Freeze. Packages. i18n. Ideas. Plans. University. Life. Family. Mother. Notebook. Frieds. DebConf. DebConf7. Edinburgh. OLS2007. LI. OpenBeach. Work. Free. Freedom. Debian. Brasil. Sorry. Smooth. Standards. Ideas. Core. Philosophy. Beliefs. World. Creed. 24. Translations. Organization. pt_BR. NMU. l10n. Past. Present. Future. Notes. Messages. Kind. Patience. Friendship. Fellowship. Party. Meeting. Food. Discussion. Debate. Cry. Try. Fix. Solve. Together. Alone. Team. Workgroup. Fast. Again. Just. Me.
Thanks: peretto and enerv.

Gunnar Wolf: Comments in blogs

Many people have recently posted in Planet Debian regarding the use, usability and usefulness of having comments enabled in blogs, of using comments as the right way for following discussions, of dealing with spam, and so on.
I'm sorry I'm not linking to more of them, but I'm too lazy to look them up. This is one of the down-sides of not using comments - Ideally, if I were interested on commenting on a topic, I would just leave the comment on the blog that started it. It goes somewhat against Joey's logic of posting both the comment and the posting itself - Of course, we all want everybody and their dogs to read our comments, don't we? And, given we know that (most of) our target readers regularly follow Planet Debian, we continue ranting on our personal blogs (as I'm doing now). Besides, that will rank our page higher. We all want Google to love us, right? Of course, following discussions on a bunch of blogs is not optimal, as it's easier to miss parts of it (hey, would somebody volunteer on writing threading support for Planet? It'd have to be multidimensional, as postings often refer to different threads... Bah :) ). Besides, many of us are syndicated on different planets (and many people read our blogs as individuals as well), so many of my postings start with a stupid amount of background information so the martians understand the terrans. But still, here I am, writing a post that provides nothing but a braindump, serves no purpose, and links to your posting. So there, the world is not ideal. QED.
As always, MJR rants against captchas (and yes, thank you, you have commented on my blog that most captchas are trivially crackable by automated means). They do reduce spam, but they are REALLY not a strong barrier against it. I have thought of some ideas, or thought about implementations for other ideas I've read here and there, but I'm too lazy to implement them on my blogging software. I could switch, but I happen to like Jaws. I would like to contribute to making it better, but have had a permanent lack of time for a long time already :-/ I do get swamped by spam comments, and every now and then mass-delete whatever looks like spam (hundreds to thousands of comments, for crap's sake!), but anyway... It's not too important for me. I like having comments on my entries, but sometimes a long time must pass until I even read them (I read my own blog syndicated via the Planets, on a RSS reader).
BTW, Lucas: I used to have trackbacks enabled. The amount of spam, and the control I have over spam in my blog, makes me favor comments against trackbacks. My trackbacks used to be so wildly abused that it almost made me cry. I hope it is not your case :)

Ian Murdock: Software installation on Linux: Tomorrow, it won t (with some cooperation) (part 2)

In part 1, I described the problem of software installation on Linux; in part 2, I’ll describe the solution we came up with at the recent LSB Packaging Summit. After reading through the comments to part 1, let me first point out that our goal is to create a vibrant third party software ecosystem around Linux—you know, like the one Microsoft has built around Windows. No, it’s not about imitating Microsoft. It’s about being competitive. A platform is only as good as the applications that run on it. Bottom line: Many third parties have built their businesses around proprietary software, and we can’t just ignore them. And “ecosystem” implies decentralized, which I argued in part 1 was a key tenet of open source development anyway, i.e., this should be playing to one of our core strengths. So, if your “solution” is to tell ISVs (independent software vendors) to give us their source code so the distributions can include it because that’s just how we do things, you can safely skip the rest of the post below. You’re simply not going to agree that any of this is a problem. Ok. Assuming our goal is to create a vibrant third party software ecosystem (and everyone still reading agrees that’s a good goal, right?), we have the following challenges. First of all, the distribution vendors are hugely invested in their existing package systems, and for the most part, those package systems work extremely well. As I said in part 1, “if [an application] is in your distro of choice, you re only an apt-get or a yum install away from running it.” (I’m saying it again here because some of the commenters apparently didn’t see that. The tricky bit is “in your distro of choice”, which by definition is not the case with third party software.) Furthermore, a variety of highly sophisticated systems management solutions are built above those package systems, such as Red Hat Network and Novell ZENworks. This is a pretty important consideration, because these days, the “software management problem” largely involves managing software across the entire infrastructure, not just a single system. What problem then? This: ISVs have thus far been reluctant to use the native package systems. Why? THEY’RE hugely invested in “package systems” for other platforms, and every Linux specific thing they have to support costs money. In a world where decisions are ruled by cost vs. benefit, this is a pretty important consideration too. How do ISVs handle this today? For the most part, they ignore the package systems on Linux and do their own thing. Trouble is, while doing their own thing gives ISVs the flexibility to work cross platform, it ultimately makes their products integrate poorly in the broader systems management context because the package systems know nothing about them. What is needed is a way to bridge the gap between what the distros provide and what the ISVs want. But how? First off, we have to understand what ISVs want. The answer is simple: ISVs want to treat Linux as a single platform, which means they want to offer a single package for Linux, much as they do for Windows. So, if one commenter is right that “[t]he problem is that people (including software distributors) believe there s such [a] thing as ‘Linux’ as a target platform” and that “[i]f you re distributing software for ‘Linux’ then it won t be simple to install it, ever”, well, then Linux is destined to suffer the fate of UNIX. I’m not ready to give up so easily. Several commenters suggested that what we need is a brand new package system. That’s a non-starter—for one thing, the distros aren’t going to be too keen on replacing something they’re hugely invested in, and if ISVs aren’t going for RPM today, why would they go for something different tomorrow? No, to find a way forward, we need an evolutionary step from where we are today. From there, perhaps we can do more, but even the first steps can be quite valuable in their own right. To help find those first steps, we put some of the leading minds in Linux packaging in the same room (including the maintainers of RPM at Red Hat and Novell and the authors/maintainers of APT, yum, alien, and klik) along with ISVs large and small, server and desktop. The discussion pretty quickly converged on constructing a single API that could be implemented across the various package systems, because APIs make for nice evolutionary steps and can, done right, mask underlying implementation differences. Question is, what do ISVs need in such an API? Limiting the scope is key here, because providing an API that spans all the functionality of, say, RPM and dpkg is overwhelming to the point of being unworkable, not to mention more work to implement, which in turn makes it less likely to get into the distros so that ISVs can count on it being there, the whole point of this exercise in the first place. Fortunately, the ISVs don’t really need much. At the most basic level, an installer just needs to be able to query the system to see if it’s LSB compliant, and if it is, what version of the LSB it’s compliant with; and it needs to be able to “register” with the package system, so the package system knows about it, including what files it has installed. And that’s really about it. Importantly, because we assume an environment that’s LSB compliant, we don’t have to worry about dependencies, because everything is covered by the single LSB dependency, and dependency management is 95% of the package systems right there. We still need minimal dependency support—components can extend the LSB, and applications can depend on those other components being installed—but we’re talking on the order of a handful of components, not the tens of thousands of components typical package systems have to deal with. We only had a day, so we obviously don’t have a complete solution yet. For one thing, we barely touched on the issue of uninstallation (should we allow applications to register GUI uninstallers?), and the issue of how applications go about changing the system configuration still needs discussion (in a lot of cases, the assumption of LSB compliance means the installer is going to be well behaved, but there’s undoubtedly corner cases to be explored). And it’s going to take time for the API to be implemented and put into widespread enough use that ISVs can depend on it. However, everyone in the room did come to consensus pretty quickly that this was an important problem, and that providing a simple API that provides the minimum necessary functionality was the way to go. Perhaps most exciting, the very people whose support are needed to put the API into widespread use were in that room, and active participants in the discussion too. Everyone is certainly motivated: The distros get more applications, which makes the shared platform more attractive; and ISVs get lower cost, which tilts the cost vs. benefit equation in their favor, making Linux versions more economically attractive and potentially opening new markets. Because this is just a start, the FSG is launching a Packaging workgroup to continue the discussion we started at the Packaging Summit. If you’re interested in this topic, I’d encourage you to join the mailing list and get involved. There’s still plenty to be done. Update: One more thing: In addition to making it easier for ISVs to better support Linux by simply extending their existing installation scripts, the API approach really comes into its own when you imagine it implemented in things like Autopackage and InstallAnywhere. Let the market decide!

NOKUBI Takatsugu: Binary 2.0 Conference again

Last year, Binary 2.0 Conference had held, and it also held again. There is a book named Binary Hacks (Japanese) that contains many things focused for low-level stuff. Unfortunately, it is a Japanese book, but the English TOC is available. Anyway, Takeshi Yaegashi's presentation is spreading over the world. Engadget's article is a good brief summary.

19 December 2006

Erich Schubert: Dunc wars are back

Joey and Josselin are trying to bring dunc wars back. Please ignore the trolls. They're talking more FUD than ever. And yes, I consider this behaviour childish, too. Basically they claim that dunc tank is to blame for the etch release delay. Sure, blame AJ for the attr breakage. And the libpng disaster. And the FransPop and others vs. Sven Luther issue. And the installer delays. Especially the latter. The installer has never ever before delayed a Debian release, so obviously AJ and his dunc tank are to blame. (Well, actually I think that this kind of infighting done wrt Sven Luthers access to the debian-installer repository or the anti-dunc-tank-evangelists that really harms the project: this can really take a lot of fun out of Debian, more than dunc-tank ever could. But pointing at the installer is more fun, you know...) So Joey, Josselin: please, grow up. Stop trying to harm the project just because you disagree with a decision some months ago. Thank you, aba, for working e.g. on helping sorting out the libpng issues and doing a quick NMU for the attr breakage. And all the other release work you've been doing before, during and after dunc-tank funding. Your work is heavily appreciated because it's constructive.

Russell Coker: interesting things

/tmp /mnt/bind bind bind 0 0

Today I discovered that the above syntax works in the /etc/fstab file. This enables a bind mount of /tmp to /mnt/bind which effectively makes /mnt/bind a hard link to /tmp. The same result can be achieved by the following command, but last time I tried (quite some time ago) it didn't seem to work in /etc/fstab - but now it works in both SUSE and Debian.

mount --bind /tmp /mnt/bind

Also I recently discovered that 0.0.0.0 is an alias to 127.0.0.1. So for almost any command that takes an IP address you can use either address with equal results (apart from commands which interpret the string and consider 0.0.0.0 to be invalid). I can't think of any benefit to using this, and challenge the readers to post a comment (or make their own blog post if they so wish) demonstrating it's utility.

Gerfried Fuchs: ESA Plays Funny

When you are on some abuse list from an ISP you propably know these kind of things: you get copyright/intelectual property/whatever infringement alerts from various institutions every now and then. I won't try to guess if they themself are actually downloading all the data to verify the content, or maybe even put it into the peer to peer networks to see who is going to download it. Nevertheless, sometimes there are quite funny companies with their alerts out there. One of those is the ESA—the Entertainment Software Association. The following is an excerpt of one of their mails stripped down to the relevant parts:
From: esa-no-reply@copyright-compliance.com
Reply-To: esa-no-reply@copyright-compliance.com
-----BEGIN PGP SIGNED MESSAGE-----
[key 0x9E9658B85A10FEEC unavailable]
[...]
ESA believes that its members' rights in such entertainment software products
are entitled to the full protection of the intellectual property law as well as
other relevant laws of your country.
[...]
Please inform us whether you will remove or disable access to the Infringing
Material as requested.
[...]
Given that they say in their headers that they don't want reply, both in the From and Reply-To, they still request information about the actions taken in their mail body. Yes, there is a different mail address listed in the body too, though that's not how mail programs work, do they...
Then for added authentity they pgp signed their message. Though, I wasn't able to find a server on which this key is available, and there is no hint in the mail where to get it from. Quite trustworthy, isn't it. It adds that the whole mail says that it's a template, though states that they are "entitled to the full protection of [...] relevant laws of your country". One starts to wonder if they are at least remotely aware to which countries they are mailing... P.S.: On a side note, their second listed MX record doesn't seem to feel responsible for the domain—it simply sends you a 551 5.7.1 relaying denied when one would try to deliver there. Adds to the impression that the ESA is nothing but entertaining...

Manoj Srivastava: Mail Filtering With CRM114: Introduction

I have a fairly sophisticated Spam filtering mechanism setup, using MIMeDefang for SMTP level rejection of Spam, grey-listing for mails not obviously ham or Spam, and using both crm114 and spamassassin for discrimination, since they compensate for each other when one of them can't tell what it is looking at. People have often asked me to write up the details of my setup, and the support infrastructure, and I have decided to oblige. What follows is a series of blog posts detailing how I set about redoing my crm114 setup, with enough detail that interested parties can tag along. I noticed that the new crm114 packages have a new facility called mailtrainer, which can be used to setup initial css database files. I liked the fact that it can run over the training data several times, it can keep back portions of the training data as a control group, and you can tell it to keep on going until it gets a certain number of mails discriminated correctly. This is cool, since I have a corpus of about 15K Spam and 16K ham messages, mostly stored on my previous train-on-error practice (whenever crm114 classified a message incorrectly, I train it, and store all training emails). I train whenever crm114 and spamassassin disagree with each other. This would also be a good time to switch from crm114's mailfilter to the new mailreaver, which is the new, 3rd Generation mail filter script for crm114. It is easier to maintain, and since it flags mails for which it is unsure, and you ought to train all such mails anyway, it learns faster. Also, since the new packages come with a brand new discrimination algorithms which are supposed to be as accurate but also faster, but may store data in incompatible ways, I figured that it might be time to redo my CRM mail filter from the ground up. The default now is "osb unique microgroom". This change requires me to empty out the css files. I also decided to change my learning scripts to not send command via email to a 'testcrm' user, instead, now I train the filter using a command line mode. Apart from saving mails incorrectly classified into folders ham and junk (Spam was already taken), I have a script that grabs and saves mails which are classified differently by crm114 and spamassassin from my incoming mail spool and saves it into a grey.mbox file, which I can manually separate out into ham and junk. Then I have a processing script, that takes the ham and junk folders and trains spamassassin, or crm114, or both; and stashes the training files away into my cached corpus for the future. In subsequent blog postings, I'll walk people through how I setup and initialized my filter, and provide examples of the scripts I used, along with various and sundry missteps and lessons learned and all.

Wouter Verhelst: Dunc-Tank, Debian, and crises in general

For those who've been hiding under a rock for the last few months: dunc-tank is the (controversion) project that was founded by the current DPL, Anthony 'aj' Towns. Controversial, because a lot of people feel that this goes against the spirit of Debian; and that by paying some Debian people and not paying others, we're creating a two-class system that we'd best avoid. And probably a bunch of other arguments, too, but that's not what this blog post is about. Me, I've been staying rather quiet in the whole debate. It's not that I don't have an opinion; rather, I haven't been voicing it, mostly because my thoughts on the matter are rather convoluted, and I'm not sure I can put them in words pretty well. But since the debate seems to be going in circles, and since I think that I might be able to help it out, I'll try anyway. If that doesn't bring the debate any further, well—can't blame me for trying. Do I think that paying people to do work on Debian is necessarily a bad idea? No, not at all. Quite to the contrary; by paying people to work full-time on Debian for a while, we will increase the amount of work that's being put into Debian, which can only be a good thing; and I can only applaud aj for trying to get this done, since it should be obvious to anyone involved that by proposing this, he only had Debian's best interests (i.e., improve our distribution) in mind. The obvious question, however, is who we'll be paying. After all, while I don't think it's necessarily bad to pay people, I do think that with money, you introduce the possibility for corruption; so at the very least, it should be strictly checked what exactly happens with the money that's being spent. Accordingly, the way in which you pay people—your whole set-up and procedures—should have a number of safeguards. Which brings me to my next point. Do I think that dunc-tank, as a project, is a good idea? No, not at all. Quite to the contrary; and I have a number of reasons for that. First, I don't think that deciding by committee who can get paid and who can't is the way to go forward. A committee will always be biased, no matter how diverse its membership. Even if you could find a committee that would not be biased—an impossibility by definition—then there will still be people who will not agree with the committee's decision. Are they right not to agree? Not necessarily. Is it bad to create such controversy if it could be avoided? Sure as hell. Moreover, by creating a project which populated by Debian people and which has the sole purpose of paying Debian people, it's fairly possible to create the impression as if all other ways to get paid to do Debian work would be unsound; that if a developer accepts money for Debian work without going through the committee, he's somehow doing something morally wrong. This would be very bad indeed; I know for a fact that there are cases of people paying Debian Developers to work a few days on a certain package so that a certain bug which impedes their business is fixed, or so that a certain version of a random package which this company is using, is uploaded into the archive. I've done this myself in the past (although I can't disclose more, since the person who paid me requested to remain anonymous); I know of at least two other Debian Developers who've done so as well. So what's the alternative? Not paying people is one, but it would not necessarily be the best. One alternative, which the FreeBSD people have been doing, is just "no organization at all". People who want to get paid just put up a web page with the amount of money they would like to have, and it's up to the community to decide whether their request is valuable enough for it to actually be paid. To some extent, this is also what the Dunc-Tank committee is doing, except that as FreeBSD does it, there is no committee in between. The problem with this approach, however, is that if we all go ahead and ask for money at the same time, it'll not only make us look like a bunch of beggars; it's also very likely that nobody will actually be getting any money, because there's so many "good causes" to choose from that there might not be enough donations to fund them all. Another proposal was one made by Manoj Srivastava, before word got out that dunc-tank would be started (or about at that time). As it was made on the debian-private mailinglist, I can't say much about that; suffice to say that I feel his proposal was overly bureaucratic, and had problems that were similar in nature to the problems I feel exist with dunc-tank. So do I have any answers which might get us a way out of the current status quo? Nope, afraid not. But allow me to make this final observation: In early 2005, a bunch of people decided that Vancouver was a nice place, and travelled there. As it happened, they were all Debian people. What a coincidence. Since they were all there anyway, they decided to talk a bit about Debian, and as a result, came up with some plan for its future. This plan, too, was rather controversial. When I initially read the first few paragraphs, I suddenly fell upon this paragraph which seemed to say that "we suspect we won't be releasing with anything but i386, amd64, and powerpc for etch". Things suddenly turned kinda red from then on. And it wasn't the wine that I hadn't been drinking. I could imagine that what I felt back then is somewhat similar to what some other people felt when they first heard about the suggestion to pay people for Debian work; and this realization is the reason why I haven't been dismissing their arguments or thoughts, much like I've seen other people do. However, I cannot say that I feel the current crisis to have many parallels with the Vancouver one; this is mostly because in the current case, people on both side of the argument seem to be building up walls around themselves, to help them ignore whatever the other side was saying. In contrast, when someone suggested something which had the potential effect of throwing most of the hard work I'd been putting in for Debian during the last five years now down the drain, I went to talk with them—after the heat had cooled down, anyway. Unfortunately for me, the result is exactly the same; for all my effort, I haven't been able to prevent m68k to be kicked out of the release; and to say I'm not happy about this would be an understatement. But at least this way the port has been given a fair chance; if I hadn't been talking to the people on the other side of the argument, I would still be talking about Steve Langasek as if he were the devil himself, and m68k would probably have been kicked out of Debian—along with a bunch of other architectures. At least I got that bit fixed. I guess what I'm saying is that people, rather than farting in eachother's general direction, should be working together in finding a compromise. Sure, that means making concessions, and agreeing to something you'd rather not agree to. But at least this way, the thing you have to agree to isn't as bad as what it could be. And trust me, people will do the stuff you don't want them to do, with or without your agreement. Hell, they've already started. Whoa, long post. I'll stop preaching now.

Luciano Bello: Dear Santa Pyro

Dear Santa Pyro,
I've been a really good maintainer this year and I hope not to get coal. Don't let my not-updated-lintian-page fool you. My packages hasn't got any RC bug in unstable or testing and they are all updated.
What I really want for Christmas is Task and Skill step finished. That will look great under Christmas tree :)
Thanks in advance.

Your eternal applicant, luciano

Pierre Habouzit: Let stop FUDing, or let's kill the "dunc-bank delayed etch" troll

Given the recent articles or blog posts that may lead some people to think that dunc bank made people work against Debian, maybe some explanations are needed. Dunc-bank is a single web page that some humourless people may find unfunny, YMMV, but that is nothing else than satirical. There was no conspiracy, undermining work, or power games. People claiming the contrary are just making complete fools of themselves. Really. The people that contributed to dunc-bank, meaning that did report most of the RC bugs in the last month are for some, even disgruntled when it comes to dunc-bank (I'm thinking e.g. of Lucas Nussbaum that did a full archive rebuild and reported many bugs). No, dunc-bank is not the evil masonery club that some depict. The sole thing I think really happened, is that people are nowadays really concerned about QA, and that there is a whole lot of issues that can be tracked automatically, at home (a good ADSL line and a GHz grade CPU is largely enough to do an archive rebuild in a week nowadays). What is really a shame in fact, is that those checks are not performed by Debian for any package, and on a regular basis. The other factor is that I think many people had concerns with etch quality, as many discussions in the past month may have let think that its quality could suffer from the announced release date. Now that this bad joke is now officially a dead-line, I think this is less and less a concern. That said, Yes, I do think some people that usually did good work in debian diminished their work considerably, and that it hurt the release. We lost some developpers (our locales + X-keyboard expert and that's a huge loss), some orphaned a lot of packages, and recent events do show that you can't improvise beeing the libpng maintainer a month before the release, and so on. Yes it's true that recent events and surroundings in Debian[1] have led people to feel they are strangers to what Debian is becoming. And blaming them for not beeing supportive is very distateful and shocking. When you do pursue actions, that will lead to big changes in the community, then blaming the community members for those changes is a shame. So no, you can't blame the people behaviours (that have been reduced to dunc-bank supporters because that's so easy) for etch beeing late, because you can't blame the direct consequences of an action for beeing the cause of its failure.
Notes [1] and not only dunc-tank, even if that's IMHO one of the biggest.

Mario Iseli: Package for pokerth

Good morning… :-) today I saw the RFP for “pokerth” on WNPP, had a look at upstreams website and just retitled to an ITP. Now my package is ready (and in the queue of my AM to upload ;-) )
For those who are bored or like to play poker games I already have a little preview: http://www.marioiseli.com/debian/sid/main/source/games/asciijump_0.0.6-3.dsc
http://www.marioiseli.com/debian/sid/main/binary-i386/games/pokerth_0.3-1_i386.deb Yeah I know, please don’t flame me because I write a blog article just due to one single Debian package, but I really like this game and hope you have fun with it too… Regards… (I’m not responsible when you arrive late at work tomorrow…)

Daniel Baumann: Mozilla Locales Packaging

Mozilla Firefox Locales In 2004, we had for every individual localization a dedicated source package in the Debian archive, such as: mozilla-firefox-locale-ar, mozila-firefox-locale-ca, etc. This is a mess from every point of view. First, it creates much overhead on the archive infrastructure side as well as on the maintainers one, and second, since it often results in localization packages out of sync with the browser, it is a major pain in the ass for the users. Mozilla Firefox Locales All In January 2005, Cesar Martinez Izquierdo introduced the common source package mozilla-firefox-locale-all which included most of the available localizations. That was the inital step to clean up the mess. Later, David Moreno Garza and Luk Claes took the package over and accompanied it through the Mozilla Firefox to Firefox transition. Iceweasel l10n In September 2006, I jumped in as the new maintainer. Since then, the package did continue to evolve: Additionally, iceweasel-l10n as of 2.0+debian.1-1 supports 43 languages in total. That is more than any other distribution (yes, including Ubuntu :) contains. Icelizard Currently, the locale packages for iceape and icedove are not unified. This September, I was writing to the some of the maintainers but they seemed not interested to fix it for Etch. I will try it again in 2007, my aim is to have proper unified localization packages for all icelizard applications in Lenny. Update: iceweasel-l10n 2.0.0.1+debian-1 adds Valencian localization, so supporting 44 languages now.

Steve Kemp: How long? Not long

In the finest tradition it is Christmas-time and my computer is dead. OK slight exaguration. I have two computers I regularly use:
desktop.my.flat
This is my main development machine, which I sit in front of and work at most days.
itchy.my.flat
This has several roles:
  • xen
    • So that I can run Sarge for building security updates.
  • caching name server
  • backup server
(Both of these machines run Sid.) The backup server is the important use for this machine. Every four hours I do a full database dump + rsync of d-a.org, my personal server, and my desktop system.
The backup machine, itchy, is currently down because of a failing hard drive. I’ve ordered a replacement computer (a bit extravogent considering I could have got by with just a new disk drive). This will be my first 64-bit machine, and also my first machine with hardware support for virtualisation. The new machine should arrive on Saturday. Once it does I’ll rotate it in. The new machine will become my desktop. My desktop will become the backup, and the old machine with the failing drive will be donated to my Sister. (Who I was due to give a machine to already. I will need to get a new disk but that will be done shortly.) I think I’ll try sticking with Etch on the new machine, and possibly make the backup machine run it too. I guess I don’t need sid yet… Besides Xen makes new installations easy :)

Next.

Previous.