Search Results: "ag"

9 December 2008

Peter Eisentraut: When non ASCII names will finally work? (part 2)

no comment

Bastian Venthur: Lenny s release date III

Two months since my last status update of my initial guess for Lenny s release date, time for an update: My guess for Lenny's release III I don t know what the current official release target for Lenny is, but I still think we re heading towards Spring/Summer 2009. The last related mail on -devel-announce is from October 2008 from Alexander who hopes that we ll release Lenny at least by the end of 2008. I ve read an article with an interview with Steve McIntyre somewhere on The Register where he said:
Bastian s being a little bit pessimistic based on the data he s looking at, but as far as I know, he hasn t spoken to any of the release team. As far as Lenny goes, we re almost there, he told The Register.
That interview was in the beginning of October. It doesn t bother me too much, that we release late. What bothers me is that we don t correct our estimated release dates even when it s obvious that there is no way we will release in time. It s really sad that we keep our users in the dark about the fact that we can t release in time until it s already too late. I believe many users would appreciate if we d honestly say: We don t know when we release, but currently we have x RC bugs open and looking at the last releases we think it will take roughly n months to fix them and release, instead of the good old We release when it s ready . Another important point: Unstable is frozen for almost five months now. If you buy a current laptop, chances are hight that it might not fully work with Debian bleeding edge unstable, since it s horrible outdated. Some of the newer stuff can be obtained from experimental if you re brave enough, but if you re not, unstable is getting more and more unattractive compared to other distribution s current versions. This is really something we should try to fix after we released Lenny.

Lucas Nussbaum: The Project membership procedures GR

So, the call for vote on the “Project membership procedures” GR was sent. Since I took part in the discussions that lead to that GR, I feel obliged to explain my point of view. What this GR isn’t about
This GR isn’t about the merits of Joerg Jaspert’s proposal. I personally don’t think that the changes he wants to implement are what we need in Debian, but even if I fully agreed with those changes, I would still disagree with the process that led to those changes. Also, this GR isn’t about Joerg Jaspert himself. I deeply respect him and his awesome work for Debian. And I’m sure that this vote could have been triggered by decisions announced by someone else. What this GR is about
I think that the question we are asked to vote on is:
Some people in Debian have a special role, and special privileges. Does it allow them to change important aspects of our project, without the approval of all the other developers?
Or, put differently:
Where is our limit between Doocracy and Democracy?
I’m all for listening to developers who contribute(d) a lot. I think that most people, when skimming through posts in a big thread on -devel@, will look for posts from people who did a lot of work for Debian, or who usually post interesting ideas. However, that doesn’t mean that those people should feel empowered to decide changes to important parts of our project, without first discussing those changes with all other developers, and making sure that those changes are consensual. So, I hope that we will send a clear message that says: you are very welcome to propose changes, but please make sure that they are properly discussed within the developers before they are implemented. Joerg’s initial mail on d-d-a, with a few s/decision/proposal/, and a final question phrased like “Any comments? Suggestions? Other ideas?”, could have been the start of an interesting discussion about how we can integrate non-developing contributors in Debian. And if too many developers disagreed, we could have had an opinion poll (it would be great to have an infrastructure for running polls inside Debian, like what Jeroen did three times a long time ago), or even a GR, like we did for Debian Maintainers. For this actual vote, there are two similar options on the ballot (choices 1 and 2, respectively “amendment text A” and the original text on the vote page). I proposed this amendement (choice 1) because the original text is unclear, and mixes several different questions, forcing voters to answer several (secondary) questions at once, like: The amendment aims at going straight to the point. And yes, it is only asking the DAMs, but if the developers ask the DAMs not to do something, and the DAMs do it anyway, we clearly have a bigger problem. I believe that the way those decisions were announced was a mistake (that unfortunately none of the people involved have been willing to admit), not that the DAMs are trying to take-over Debian, so there’s no need for a stronger wording.

Wouter Verhelst: The advantages of a home-grown comment system

A while ago, I was investigating the possibility to move blog backend to something else; something like, say, drupal, so that I wouldn't have to maintain it too much myself. For those who care, this blog is a very strange contraption based on subversion, blosxom, php, and a postres backend for the comments. I've now dropped that migration thought, for a very simple reason: comment spam. A while back, the spammers had found my blog, and started placing comments using a bot. They might think that these comments will eventually show up on my website, but that's wrong; I always moderate away spam. First, they posted a few comments. I changed a few details about the form, and the bots (who only went to the POST URL, never checking whether the form they requested was unchanged) failed miserably. Then, they posted loads and loads of comments, in a weird attempt to overrun me with comments. One psql run and one DELETE statement later, those comments were gone -- and one minor form change later, the bots failed miserably, again. This went on for a few months, until the stupid spammer finally understood that he was wasting loads of his time in trying to post something on a website that wasn't ever going to enable his comments, anyway. Or so I thought. You see, the thing they're really after is my pagerank. In itself, grep.be is nothing special -- but planet.grep.be is, and apparently some of that pagerank score trickles to the other grep.be subdomains. Or, at least, that's what the spammers seem to think, in case it isn't (I wouldn't know). When the comment spam on my blog had been silent for a few weeks, I found that the spammers had found my gallery installation, and had posted some several thousand comments there. One DELETE statement later they were gone, but a few hours later some of them were back. I don't know the gallery source code well enough to pull the same trick here (disable comments until manual moderation), and unless I want to do something like using a CAPTCHA on my gallery site (I don't) or disabling comments altogether (I don't, either), I'll just have to resort to removing these comments from the database. At least by doing that, I can remove them all in one go. And at least the spammers are easily recognizable. For now. Perhaps I'll have to look into changing gallery's source code after all... or, perhaps, just use something else. Sigh. Stupid spammers

Josselin Mouette: RubyGem is from Mars, apt-get is from Earth

There is again some ongoing debate about Ruy gems and how to integrate them cleanly into the operating system. Let s put aside the fact such tools are useful on Windows and MacOS which don t have decent packaging systems. This is not a reason to dictate stupid requirements for other operating systems. Still, even without that, gems, eggs and the like are great tools for development; tools that developers can t work without today. They allow to easily setup a development environment with everything needed, at the latest versions. However they were not meant for integration and production environments, and will never be suitable for them. We re living in another world indeed: a world where servers must be up 24/7, where security issues flood your inbox every day, where you need dozens of servers running the very same software. This world is the Earth. Python eggs and Ruby gems were designed for the same target audience and with similar requirements; as such, they share the same deficiencies when it comes to other audiences:
  1. They replace the operating system s packaging tool. This is very nice to not wait for the packagers when you want the latest development version, but you lose track of what is actually installed. In production, you need to know exactly what s installed and at what version. You also need to know what you will need to update in case of a security issue.
  2. They install packages automatically on the system. This is really the biggest WTF; there are some reasons to do that to begin with, but they are all wrong.
  3. They use a specific file format. This requirement comes mostly from the Windows world, and it really makes no sense on Unix. It makes it much harder to integrate complex applications using components in different languages.
  4. They ship all files at the same place, happily violating the FHS and making it even harder to integrate with other things.
Python tools (setuptools and easy_install) have shifted their philosophy and brought a few small improvements which allow us to easily work around issues 1-3. These tools now include all you need to build a development environment in any directory that will not have an impact on the system packaging, making a clear distinction between the two targets. Furthermore, the metadata is shipped separately and can safely be included in a distribution package. Similarly, modules will not be installed automatically on your system. I have yet to see such a move from Ruby developers. However, what we are still missing is something along the lines of dh_make_perl: starting from a CPAN module, it will generate a clean and working Debian package in a few minutes. There have been some similar attempts for Python, but nothing as efficient. And I am certainly guilty of not having done something in this area, as one of the most knowledgeable of issues we encounter while packaging Python modules. As a note, I should add the underlying issue behind all of this is still the same: the NIH syndrome. Developers are reinventing the wheel, engine and transmission. Which is not that bad per se, but by not looking at existing solutions for the problem of making a car move, they are inventing a square wheel, a steam-powered engine and a superconductor-powered magnetic transmission. For example, while trying to fix the 4th of items listed earlier and they are really willing to fix it and several more general issues, setuptools developers forgot to look at the existing solutions: Certainly, the existing tools are everything but perfect, and not necessarily suitable for Ruby and Python, but some of the design ideas behind them are clearly the good solutions to some of the issues of software development and integration. Adapting these ideas to radically different languages is going to take more time than just throwing other layers of symlink farms.

Wouter Verhelst: Rails: followup

I received quite some comments on my rant about Ruby on Rails a few days ago; I guess I must have received some inbound link on a ruby-fanboy-website or some such. Most of it is just bashing me since, I'll admit, my post wasn't very constructive (and which according to my policy of only blocking spammers I've not moderated away), some of it just posits another opinion about packaging (which is valid), and one Eric Anderson gave a good and constructive set of arguments that I just have to reply to. First of all, yes, I hate RubyGems more than I hate Ruby on Rails. However, Ruby on Rails is the major success story in the Ruby community, and the main reason why people use that language; it's not unfair to say that I won't use RoR because of RubyGems. But perhaps I should've been clearer. Anyway. Eric mentions that RubyGems "solves two problems that other packaging systems are not addressing": the ability to install two versions of the same library, and the ability to install a single package on multiple operating systems. Well, first of all, the latter one simply is not true. There's CPAN.pm, which does much the same thing as RubyGems; but much of CPAN can be easily turned into a Debian (or RPM, or whatnot) package. The few cases where it can't, you're usually dealing with a broken CPAN package, anyway. There are similar things for Python (egg), and, heck, even TeX (CTAN). The fact that other scripting languages have proper and working packaging systems only outlines that there really isn't an excuse for the horrors of RubyGems. Second, the fact that you even need to be able to install multiple versions of a library really shows that there's a problem with your development ecosystem. C, Perl, and Python programmers are used to stable APIs, and prefer not to change their APIs all that much. Most packaging systems reflect that preference, and deal with incompatible API changes the way they should: as the exception, rather than the rule. The people in the Ruby ecosystem clearly have a different opinion on that, which probably results in the difference in packaging system requirements. Personally, I prefer the non-Ruby way—I'll leave the discussion about "what happens when you need to do an urgent security update of one of your libraries but the API has changed three times since you last looked at it and now the library update breaks your application" as an excercise to the reader. In closing, I'd like to reply to this one sentence that Eric put in his comment:
And of course there is no reason software cannot start as a gem (for people close to the ruby community) but as it's popularity increases packages can be created that are more tightly integrated into the native package manager.
Well, in an ideal world, he'd be right: there would be no reason. Unfortunately, in the RubyGems world—which is far, far away from an ideal world—the fact is that packaging RubyGems in a sane way so that they'll integrate with the rest of a Debian system is simply impossible. You simply cannot currently go from a gem and create a package out of that, because of how gems are done. That, more than anything, was what I was objecting to. I can understand that many Ruby developers do not care about this much; that they are used to RubyGems, and that they can geet anything they need using that system. However, they should understand that different people have different preferences, and that packages for systems other than RubyGems is going to be necessary if their software is to become popular beyond the select set of people who care enough about Ruby. I personally know of plenty of people (myself included) who prefer things to be installed as operating-system level packages on the Linux systems they install; and even if it's not your personal preference to do things that way, you should at the very least not stand in the way of those who do.

Wouter Verhelst: "Going to FOSDEM"

Planet Debian is currently plastered with this "I'm going to FOSDEM" banner that the FOSDEM people have created. That's great; it means I'll be seeing lots of people there the first weekend of February. I'd put it here, too, but I'm lazy, and people know I'll be there—I'm doing th Debian devroom. So just assume a blue banner here. What I'm not seeing, however, is talk submissions. So far 5 people have expressed interest in giving a talk, and two have made a definite commitment. That's not enough! I'll probably be sending out second a Call for Talks if I don't get enough submissions by next weekend, but for now, let me give people a list of talk titles I'd like to see in the DevRoom but that haven't been submitted yet: People, above all, please remember that FOSDEM is less than two months from now. Usually I can (and do) send the CfT about four months before the actual event, but circumstances have forced us in this position now. If you want to have an interesting Devroom, I need talks, and I need them sooner rather than later. See my CfT for details.

8 December 2008

Gunnar Wolf: Apt-get and gems: Different planets, right. But it must not be the war of the worlds!

Thanks to some unexplained comments on some oldish entries on my blog, I found -with a couple of days of delay- Rubigem is from Mars, Apt-get is from Venus, in Pelle's weblog. And no, I have not yet read the huge amount of comments generated from it... Still, I replied with the following text - And I am leaving this blog post in place to remind me to further extend my opinions later on.
Wow... Quite a bit of comments. And yes, given that the author wrote a (very well phrased and balanced) post, I feel obliged to reply. But given that he refered to me first, I'll just skip the chatter for later - I'm tired this time of day ;-)
Pelle, I agree with you - This problem is because we are from two very different mindsets. I have already said so - http://www.gwolf.org/soft/debian+rails is a witness to that point.
But I do not think the divide is between sysadmins and developers. I am a developer that grew from the sysadmin stance, but that's not AFAICT that much the fact in Debian.
Thing is, in a distribution, we try to cater for common users. I have a couple of Rails apps under development that I expect to be able to package for Debian, and I think can be very useful for the general public.
Now, how is the user experience when you install a desktop application, in whatever language/framework it is written? You don't care what the platform is - you care that it integrates nicely with your environment. Yes, the webapp arena is a bit more difficult - but we have achieved quite a bit of advance in that way. Feel like using a PHP webapp? Just install it, and it's there. A Python webapp? Same thing. A Perl webapp? As long as you don't do some black magic (and that's one of the main factors that motivated me away from mod_perl), the same: Just ask apt-get to install it and you are set.
But... What about installing a Rails application? From a package manager? For a user who does not really care about what design philosophy you followed, who might not even know what a MVC pattern is?
Thing is, distributions aim at _users_. And yes, I have gradually adopted a user's point of view. I very seldom install anything not available as a .deb - and if I do, I try to keep it clean enough so I can package it for my personal use later on.
Anyway... I will post a copy of this message in my blog (http://gwolf.org/), partly as a reminder to come back here and read the rest of the buzz. And to go to the other post referenced here. And, of course, I invite other people involved in Ruby and Debian to continue sharing this - I am sure I am not the only person (or, in more fairness, that Debian's pkg-ruby-extras team is not the only team) interested in bridging this huge divide and get to a point we can interact better - And I am sure that among the Rubyists many people will also value having their code usable by non-developers as well.

Tiago Bortoletto Vaz: gnome-subtitles 0.8 almost there


I ve finished the first working package for gnome-subtitles 0.8 in Debian, since it adopted SubLib as a separated project: http://svn.debian.org/wsvn/pkg-cli-libs/packages/sublib/
http://svn.debian.org/wsvn/pkg-cli-apps/packages/gnome-subtitles/ The main question for me now is about waiting a signing key from upstream or suggesting him to adopt mine in order to get the assembly strongnamed for Debian. Actually I need some reviewing, considering I m totally ignorant about mono stuff and it s my first library in Debian. ps: thanks guys from #debian-mono for teaching me that Chicken has nothing to do with us even currently providing the csc binary :) Posted in english Tagged: debian gnu linux

Biella Coleman: dino-anon (or how to end your hacker class on a lulzy note)



dino-anon, originally uploaded by the biella.
As I mentioned in my last entry, the end of the semester is one of overwhelming, seemingly unstoppable entropy. People and Professors are tired and to help move us through this thickness, I try to pick fun readings. Today I also had the opportunity to have a group of NYC-based Anonymous come to class today to give us a window into the politics of protesting Scientology and this of course worked magnificently against the end-of-semester-entropy. In a nutshell: they did not fail or in their own lingo, it was an Epic Win. They provided a really nice set of presentations (and then also proceeded to collectively draw the lulzy image featured above) about their origins, their purpose and some of the tensions within the group. Then we had a class discussion about a number of topics, including their argot and “offensive” (offensive) [I am not sure whether to put " " or not] online language. While I am still ambivalent about their use of “fag” and “nigger”, I greatly admire Anonymous for their politics of pleasure and aesthetic audacity (not to mention creativity). They insist that protest must be fun, must be wild, must go beyond simply rational discourse. If you are interested in this topic, check out Stephen Duncombe’s excellent (and very readable) book Dream, which I happened to be (somewhat randomly) reading right now and it helped give me a new fresh perspective about the politics driving Anon.
Duncombe is a professor at NYU Passionate (with a Capital P) about politics with a lot of real world political experience who examines the importance of desire, fantasy, and pleasure for progressives and leftists who tend to shy away or even denigrate such impulses. And it is certainly the case that Anonymous is experimenting, consciously and unconsciously, with these very questions and impulses which helps explain why many people jumped on board. I hope to post the audio from the class a little later on.

Jonathan McDowell: We need a STFU option

The Debian Project recognises that on occasion the General Resolution process is dominated by a vocal minority of the project members, while the majority are uninterested in the topic under discussion. Without wishing to curtail the democratic process it is felt that it should be possible for the silent majority to indicate its desire to move on from the topic of a GR rather than continuing to rehash the same arguments ad infinitum. In order to facilitate this the project resolves to add a further option to all ballets, "No Further Discussion". It is hoped that in the event of the "No Further Discussion" option being the winner of any vote that the project as a whole will accept that discussion of the subject of the vote is not considered to be a worthwhile use of project time or resources, and that we should therefore concentrate on more important matters. (I thought about signing this post, but decided against it)

Anand Kumria: Coughing up blood

Normally, those would not be the search terms I would plug into Google, first thing in the morning. But they were appropriate, today. Because that was what was happening. When I was younger, I used to have asthma and, as part of that, I would invariably contract bronchitis periodicially. Over the past years, even though my asthma has receeded, I would still get bronchitis at the interface between seasons. It did not matter if the season change was hot to cool, or cool to hot. Whatever the change, I would get it. I've been used to this. It is, in it's own way, comforting. I can watch the seasons change, and notice that are changing earlier. It's like I have an in-built global warming detector! This latest bout came on about 3 weeks ago. So, as usual, I thought nothing of it, bought my normal supply of strepsils and went about my life. It was not until I was doing some training, and was left exhausted and wondering why that I decided to head to the doctor. He could not hear anything wrong with my lungs. We did a few peak flow tests; my best of 3 being 250. Typical values for a health person are 600+. His conclusion: Your asthma has recurred. . A week later and I am still short of breath, but also coughing up blood. So after some searching on the interwebs, it appears that this can be normal with excessive coughing. And that the best ways to control excessive coughing are: codine1 (paracetamol / panadol) and chocolate 2 So, I've been indulging myself in both. I'm off to get a chest X-Ray just in case this is more serious and the blood re-appears tomorrow. But now you know that chocolate is good for you (and your cough).

Phil Hands: HTTPS VirtualHosts

Until a couple of weeks ago, I was under the impression that one could only have a single HTTPS site per IP address, but it seems I was wrong. The procedure is described here on the CACert wiki. In short, you need multiple SubjectAltName fields on your server's certificate, such that all the VirtualHost names that you want to work are either directly mentioned, or will match via wildcards. The page above includes a link to a nice script that generates a key and CSR (Certificate Signing Request) ready to be pasted into CAcert's Server Certificate page. Note: the CN is pretty much ignored by some browsers, so you'll want to put the machine's main name as one of the SubjectAltNames as well. BTW if you get a warning like:
  [warn] _default_ VirtualHost overlap on port 443, the first has precedence
you probably need to add
  NameVirtualHost *:443
to your /etc/apache2/sites-enabled/ssl before the <VirtualHost *:443> line. Of course, this glosses over the details of doing things like setting your name and address in the certificate, but since CAcert will strip all that out anyway, it only matters if you wanted to get it signed by someone else. Even so, this should get you started -- you can always edit those details into the csr script.

David Welton: OpenSSL::SSL::SSLError (hostname was not match with the server certificate)

I got this error in one of my Rails apps that I migrated to 2.2. It occurs when you try and send mail with ActionMailer, which makes it especially annoying because the exception notifications I normally receive when there is a problem weren't being sent! I wasn't able to track down the root cause of the problem - apparently something about an SSL certificate not being there or not being right, but here's the change that causes ActionMailer to fool around with SSL mail: http://github.com/rails/rails/commit/732c724df61bc8b780dc42817625b25a321908e4 I was able to "correct" the problem (or at least get things working again) by commenting out this line of code:
smtp.enable_starttls_auto if smtp.respond_to?(:enable_starttls_auto)
Perhaps it should be a configuration option, or there should be better error detection with regards to the certificate. If anyone comes up with a nicer answer, leave a comment, but in the meantime, I thought I'd post my quick and dirty fix.

Alastair McKinstry: Storm World: Hurricanes, Politics and the Battle over Global Warming

Storm World, by Chris Mooney is an account of the development of the science of Hurricanes and their links to Global warming, against the background of Katrina and the politics of global warming.

read more »

Tags , , ,

Francois Marier: Setting the default git branch in a bare repository

A bare repository in git does not include a checkout. So in order to set the default branch that users will get after they clone, you cannot use git-checkout mybranch.

Instead, if you want the default branch to be something other than master, you need to do this:
git symbolic-ref HEAD refs/heads/mybranch
Which will update the HEAD file in your repository so that it contains:
ref: refs/heads/mybranch
This is well documented in the git-symbolic-ref manpage but it's not necessarily the first place you'd think of looking.

Andrew Pollock: [tech] RHEL doesn't have sysfsutils?

I'm reading the Red Hat I/O Performance Tuning Guide, because hey, it's all Linux, and I might just learn something. So far, I've learned that RHEL doesn't have sysfsutils. How very weird.
Unlike the /proc/sys/ file system, the /sys/ file system does not have a utility similar to sysctl that can make such changes persistent thoughout (sic) system reboots.
and
However, as mentioned in Section 4, Selecting a Scheduler , any tuning made though echo commands to the /sys/ file system is not persistent throughout system reboots. As such, to make any scheduler selection/request queue settings persistent throughout system reboots, use /etc/rc.d/rc.local.
Of course, for all I know, this information may be out of date with respect to the current release, but Debian's had sysfsutils since November 2003.

MJ Ray: 95% of British Residential ISPs Censor - but I think I m OK

The Internet Watch Foundation has objected to the cover of a 1976 Scorpions album (which is, as far as I know, still legally on sale here, with that cover) and their collaborator ISPs have blocked access to Wikipedia. They claim that it covers 95% of British Residential ISPs but I could get through. Can you? Read more formal reports from AP via Google (claims 95% of users, which I think might be an error), BBC, Wikimedia Foundation News Release or The Guardian report (which chickens out of showing the whole cover image). Inspired by a short message from the owner of Cockspiracy, I’ve asked the Phone Coop election candidates for their views on it (note: I expect the question URL to change soon, so beware if you link to it), comparing it to our phorm promise. Did this affect you? Do you care? Have IWF just scuttled their ship?

7 December 2008

Joey Hess: haskell and xmonad

I came back from Thanksgiving in California to find my copy of Real World Haskell had arrived. I've spent the last several days making my way through it up through chapter 10. I'd read a few of the first chapters last year when I was struggling to learn Haskell, and posted enough comments that I'm amoung the (many many) people credited in the Preface. Amusing, since I still don't consider myself proficient in the language. Reading back through those and on through Chapter Nine has swapped back in the basics I learned last year, and built on them. I was able to get all the way to Chapter Ten before hitting real brain-melting stumbling blocks. That's progess! I can't help but feel that Chapter Ten should come later, perhaps after monads are covered. Only other quibbles so far are some typographical problems introduced in typesetting the book, and a few bugs and problems that were pointed out in comments on the web site, but not fixed in time for the first edition.
Anyway, I know more than enough Haskell now to configure xmonad. While I'm still perfectly happy with awesome, xmonad has some cool things going for it. Playing with it this evening, I especially like: My current set of gripes with xmonad is small:

Chris Lamb: Taking Liberties

On Saturday I went to the British Library's Taking Liberties exhibition on "the 900-year struggle for Britain's freedoms and rights". The majority of the items on display were truly iconic, including a copy of the Magna Carta, Ms Davidson's return ticket from Epsom as well as Charles I's death warrant - with Cromwell's signature easily identifiable in third position. In contrast, the video interviews that were scattered around were rather distracting at best (isn't it a library?) and embarrasingly biased at worst. I wonder how many visitors need convicing that detaining suspects without charge for forty-two days isn't a good idea. Near the exit was a wonderfully lo-fi anonymous commenting system based on a wall of bulldog clips and postcard-sized bits of paper. Fascinating in itself.

Next.

Previous.