Search Results: "ag"

4 February 2008

Matthew Garrett: Notes for the day

MESSAGE ENDS

Julian Andres Klode: Experiences with git and pristine-tar


In the last days, I used git very often. It was almost the first time I really used it, but I quickly understand the basic commands. As some of you may know, the readahead-list package is now maintained in a git repo in the collab-maint project. I decided to use git instead of bzr (which I used for everything before), because of its speed and because I wanted to learn more about git, how it works. I used git-import-dsc to import the first revision, and used debdiffs from 1 to 2 and from 2 to 3 to import the next revisions. Afterwards, I run git-import-orig on the new upstream tarball, which I downloaded and recompressed. Then, I did the packaging changes, added them using ‘git add changed-file‘ and committed them using git commit. After I had done this, I read Planet Debian and saw Joey Hess’s post about the new features of pristine-tar 0.5, i.e. the integration with git. Running Ubuntu at the moment, I fetched the source package, built it and installed it. I then opened a shell in my git repo and ran pristine-tar commit path-to-orig upstream/0.20050517.0220 to import the delta for the first tarball. Afterwards I did it for the second tarball. Because I use git-buildpackage to build the package and Joey said he would like to see support for pristine-tar in git-buildpackage, I then wrote a patch for the programs in git-buildpackage to import and export the orig.tar.gz when needed. The patch can be seen in gitweb, and the maintainer responded in Bug#463580 will integrate the patch with some minor modifications.
Both git and pristine-tar are great works, and it makes it so easy to maintain the readahead-list package. The combination of git, git-buildpackage and pristine-tar is the most powerful I ever used to maintain a Debian package, especially when you are not upstream.

Julian Andres Klode: uploads and machine-readable copyright


Two days ago, zobel uploaded some of my package updates for me. One of them was ndisgtk 0.8.1, which adds more translations and fixes some problems. I intent to create a 0.9 release soon, with support for PolicyKit. I will upload the release candidate of this version to Debian experimental and Ubuntu Hardy. The other upload was readahead-list 1:1.20060421.1016-1, which I found on the Gentoo mirrors, but not where previous releases were located. This is OK, because the upstream author is a Gentoo developer and uploaded this tarball himself. I already requested to sync this release into Ubuntu Hardy, to reduce the diff between both distributions. In both uploads, I changed the format of debian/copyright to match http://wiki.debian.org/Proposals/CopyrightFormat. I will also change my other packages in their next uploads, and hope that other maintainers also use the new format, especially for NEW packages. I some cases (especially when you are upstream + packager), this format is also shorter.

Julian Andres Klode: Debian Maintainer


Since yesterday, I am a Debian maintainer. This will help me and my sponsors, which have to do less now. I can now upload new versions of my packages if the version in unstable contains the “Dm-Upload-Allowed” field in the dsc (and only if the package is not NEW). For more information about the Concept of Debian Maintainers, see http://wiki.debian.org/Maintainers I’m very happy about this, as it makes my life easier. But this does not mean that I don’t want to be a DD anymore. A DD is able to vote, to sponsor packages, to upload NEW packages, and many more things. (BTW: I’m currently at T&S step)

Sune Vuorela: libqt3-compat-headers

libqt3-compat-headers is a debian package containing headers from qt3 to help migrating from qt2 to qt3.
This is long ago. Qt people laughed at me when I asked about how long ago that would have been. Apparantly, this package is still build-depended upon by 66 different debian packages. A big bunch of them are probably just leftovers from the past. The rest is probably a 5 minute job (+build time) pr package. For me, it kind of makes the packages look kind of unmaintained. grep-dctrl -sPackage -FBuild-Depends libqt3-compat-headers /var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_main_source_Sources to see the full list. I just filed bugs with patches on 3 random of them.

Jonathan McDowell: Sennheiser PXC 250 headphones

I was bought a pair of these for Christmas. For the past few years I've been using a pair of Hitachi TMP028s - cheap clip on headphones that I've found far better than the popular ear bud style, but nothing special. The Sennheisers are much better again. They have a neat little padded cup that means they make a good fit with your ears, the headband is reasonably adjustable (I've had issues with my glasses with other headphones) and they come with a carry case and fold flat which means throwing them in my bag for my train commute much easier. All in all I've been very impressed in my use over the past month. And then today I finally put some batteries in to power the noise cancellation function. Wow. Much more effective than I expected. I was able to knock the volume on my iAudio down a fair bit and still hear the music better than usual. The noise of the train was still present, but reduced significantly to the point where it wasn't an issue at all. Definitely recommended.

Wouter Verhelst: Movie: The prince and me, plus sequel

First of all: no, I'm not a huge fan of the genre. In fact, when I don't feel too good, I tend to avoid them, since they can depress me at times. But once in a while, a romantic comedy doesn't hurt, and I do kindof like them at times. Early last week, I picked up a DVD of the first movie at a low-price DVD shop nearby, and watched it. The prince and me isn't my favourite movie in the genre; the plot surely is interesting, but I can't shake the feeling that things work out too easily in the end. Compare with Notting Hill, for example, where the two protagonists need to go through (I believe) three cycles of relationship/no relationship before the end of the movie; this, in my opinion, makes for far more interesting cinema. But, all in all, it certainly was an interesting watch. I might think the plot could've used some improvement; but that doesn't mean it's bad. The entire visual aura of the movie is great; they went through quite some effort to make it look well. For instance, in a number of scenes it's obvious that they made the clothing of the characters blend in with the background; and yet they still managed to create diversity in those colors during scenes, by making the clothing differ just that tiny bit, and different parts of the background as well; the entire scene would be built up of one painting-like shot after another, yet all of them slightly different. Impressive. And then I haven't even mentioned the casting, which was magnificent. Anyway. Since I kindof liked the movie, and since the sequel DVD wasn't expensive, either, I got that DVD as well. Boy. I've never quite seen a movie's sequel be so completely and utterly out of touch with its original. What horror. Except for the male protagonist, not a single actor of the original cast returned for the sequel. They had good reason, so it seems. The plot is utterly stupid. It revolves around an ancient law that made it somehow illegal for the couple to get married. Hello? Do you really think a king wouldn't have the influence to convince parliament to get rid of that law? Of course not, but then you wouldn't have a plot anymore. Now if the rest of the movie would make up for this silliness, then it wouldn't be so bad. Except it doesn't. This movie is bad in... let me count the ways.
  1. The plot error, as explained above. Also, the plot was quite incoherent, for the most part.
  2. The casting is terrible. The original King Haraald, father of the male protagonist, managed to create a believable king, with that somewhat eccentric and strange flair that most European royals seem to have these days. The queen had a bit of an iciness over her, warming up to an interesting character once she started to like Paige. Even the minor roles were so well played. In the sequel, none of this returned. The queen was just tight; an empty shell. The new Paige had a problem with overacting in some of the scenes. In fact, that was a common issue; I don't think I've ever quite seen this much overacting in one movie. Also, King Haraald didn't even remotely look like the original; not physically, and not in his acting.
  3. Speaking of the King, and given the plot of the original movie, he shouldn't even have returned for the sequel; he abdicated because he was terribly ill; he should've been dead, for crying out loud!
  4. The CGI was horrible. In the original movie, there were a few scenes where I'll bet CGI was used; not because it showed, but because I don't think it were possible to create that scene otherwise. In the sequel, you could tell when CGI was used due to the utter lack of natural feeling. Ever heard of a randomizer? It's what you use to avoid having a full room of butterflies all shake their wings at the exact same speed. Shudder.
  5. The "painting" feeling and attention to detail of the original movie was nowhere to be found. In fact, at some point they show a castle which supposedly is in Denmark somewhere, but it shows the Czech flag, instead. Ugh.
  6. Some of the gags were funny, but not as intended; because they were so silly. I've seen 3-year-olds make better jokes.
... I guess I could go on forever, but then there isn't much point in boring my audience. The short version: the original "The prince and me" is an interesting watch, but please forget about the horrible sequel... ... I guess there's a reason why they put it directly on DVD and skipped the theatres.

Pierre Habouzit: New git and CLI

Yes Junichi, this new release explicitely deprecates dashed form of git commands, as they will probably go away from the $PATH for many good reasons: So we gave our users a pretty good timeframe to adapt their scripts, hence the deprecation notice. Also note that best practices about scripting are now documented in the gitcli(5) man page I wrote.

Alexander Sack: mozilla/firefox 2.0.0.12 (RC3) security backports to 1.8.0 branch

... finally I got my blog up again and I start with yet another lame post :-) My latest security backports to the upstream abandoned mozilla 1.8.0 branch are now available at http://people.ubuntu.com/~asac/mozilla-security/moz-1.8.1.12a-backports.tar.gz. Those patches should cover all security related fixes that landed on the 1.8 branch (firefox 2) as of 2.0.0.12 RC3. I noticed that I didn’t really release any of the post-mortem security patches released in debian and ubuntu. So, here the patchsets for the 1.8.0 branch that contains them all: Those tarballs ship quilt patch directories. This means that the sequence to apply them cleanly can be found in the contained series file. To apply them to MOZILLA_1_8_0_BRANCH checkout, just copy the directory contained to your checkout (name the directory patches if you like) and run
CODE:
quilt push -a
Have fun!

Daniel Baumann: My misc developement news (Januar 2008)

In the past I was not blogging small things if they were not worth a full blog entry on their own (or if I did not have the time to make up a full entry of it :). Inspired by the example of Raphaël Hertzog <hertzog@debian.org> with "News for Debian developers" for <debian-devel-announce@lists.debian.org>, I am intending to do the same on a monthly basis about my own Debian related work. This first entry about January 2008 also covers a few things from the last month of 2007. General News Package News Team News

3 February 2008

Jonathan McDowell: Inaugural all-Island Conference on Free and Open Source Software, Belfast

My. That's a mouthful of a title. I went to this event on Friday, which was run by OpenIsland. I don't really think I was the target audience; I'm already a convert and aware of the opportunities which Free Software offers. However, there were a few bits of interest to me. Brian Doran, director of the Southern Regional College talked about including discussion of Open Source in their computer related courses. He didn't commit to more use in the colleges' IT infrastructure (and indeed Netcraft reports the website as being hosted by a Win2k3/IIS combo), but it's still a significant step forward IMO - rather than just being spoon fed MS based product people will hopefully be encouraged to think about the options available and evaluate them on their merits. We'll see if it pans out in practice. Also notable was Reg Empey, NI Minister for Employment and Learning, giving a speech involving Open Source. It got hijacked into discussion about how they were going to invest in higher education in NI and fund more PHDs in a targeted manor, but I still think the fact that a member of the NI Assembly got up and used the words Open Source (or possibly Free and Open Source Software; I can't remember exactly which speaker used that once a sentence) is quite incredible. Whether or not he's fully aware of it, someone on his staff must have done some research, and decided that it was something government was prepared to think about, or at the very least not boycott. During the day I realised that I'm prejudiced towards Free Software. I'm not sure if this is a good thing or not. I will, in general, accept slightly less functionality as long as the Free option fulfils my primary needs. And I've got used to hanging around with people who also work this way, or at the very least consider Free Software on a level playing field with proprietary stuff. I was reminded that a lot of people work the other way; either they're not aware of the Free alternatives, or they view them with a natural suspicion. So it was really good to see people standing up and talking about how they'd built their businesses on Free Software, and even better, about how they were pushing back upstream fixes/features they'd needed as part of their business. I don't know if anyone in the audience was converted, but it's certainly the sort of thing I like to see - it's important to appreciate that as well as Free Software being a great resource, it's also often beneficial to share any changes you make from a business point of view, as it tends to make things easier for you in the long run. Hopefully the conference did some good in terms of making people aware of Free Software (well, mostly Open Source was talked about, but both got mentioned). I wasn't convinced that there was a need, but having talked to various people I think it's just that I have got used to being surrounded by converts and perhaps lost sight of the fact that there are still plenty of people out there who aren't yet giving Free Software a chance. There are plans for this to be an annual event, so I look forward to the next one (and I think there will be various more targeted meetings over the next year too; I know there was considerable interest in covering the use of Free Software in health).

Matthew Garrett

Hello! I am in San Francisco. Offers of beer, entertainment and marriage will be given appropriate consideration. Interestingly, moving from Melbourne to here seems to have left me back on GMT, which I'm sure isn't quite what I want.

My LCA presentation isn't up yet. I seem to have this effect on technology.

David Welton: Rails and Hype

Yoav Shapira wonders about the "rails backlash": http://yoavs.blogspot.com/2008/02/railsshudder.html I'm a big fan of Rails, and of course I realize that it has some flaws and is certainly not the optimal choice for all situations, but I don't buy into the bashing. Sure, Rails was hyped, but there is no way that it could have possible reached the level of popularity it has on hype alone. We're not talking about multi-million dollar marketing budgets commanded by the likes of Sun or Microsoft, but about a video and some nice dressings by DHH and 37signals. A small group like that just doesn't have the resources to push something like Rails as far as it's gone without some substance to back it up. Look at all the imitation. People realize that the basic idea is good, and even though the basic idea is nothing phenomenal, it hadn't really been done before. What is this idea? Take a bunch of components, and good (if not always the absolute best) practices, and integrate them nicely. Database, templating, testing, a clean application structure, ajax/javascript integration, with some code generation, all done with a language that's flexible enough to do all of the above pretty well. All those things existed, but Rails did a great job of tying them all together. And that's been imitated far and wide. That seems to indicate that, even though the imitators may change and improve bits and pieces, they're quite smitten with the idea itself. So much that they've dedicated a lot of time and effort to reproduce it. That's quite a tribute. Look at the adoption. Moving to a new language/platform is a big step, not one to be taken lightly, and for people with lots of existing code in some other language, perhaps simply not possible. Hype will take things only so far, but Rails has been taken up by a large number of people who certainly didn't do so because it was the safe, easy path to take. Perhaps some of those people have found that Rails really wasn't for them, but that's pretty normal. No one said it was perfect. However, when you look at what it takes to make people jump ship from what they know, and are comfortable with, you realize that it really must have been that much better to make people go out on a limb. Furthermore, it's easy to point out the failings and drawbacks of something after the fact, but much more difficult to do creative, innovative work of your own. Compounding that is the fact that criticizing others' work is often an easy and effective way of looking smart; there's an interesting study referenced here http://bobsutton.typepad.com/my_weblog/2006/08/brilliant_but_c.html that talks about this effect. It's something I've come to dislike over the years. Our field is so new, so dynamic, and so immature, that it's usually pretty easy to take a look at something and say that it "sucks". It is much harder to write something of your own and put it out there, knowing full well that lots of people who have never done much of anything will jump on it and bemoan its "copious failings". That's not to say that it's impolite to criticize, but - do it constructively please. Imagine that you were there in the same room, talking to the person who wrote the code in question. You would still say you don't like it, but you'd probably be much more polite and helpful in your commentary. I hope so, at least.

Steve Kemp: Shout it out

Well I've had a busy weekend, but I'm sober now. I made a new release of xen-tools, which has a couple of minor bugfixes and not much else. I also released a new update for Debian of the xen-shell which fixes a couple of bashisms. Finally I've managed to sign up two new users to my anti-spam proxy. Hopefully they're very happy. In real news I painted about 1 square meter of my flat, (we're now into week three of painting a single room...), and replaced five light bulbs:
My eyes! The goggles do nothing!
Now I need to install a request tracking system (otrs2) and catch up on significantly outstanding RT status updates. I'm getting hopeless again. Maybe I should just give it all up and become a plumber. Plumbing is easy: Water goes downhill. The rest is just regulations and a willingness to get dirty...

Christian Perrier: No more badly encoded debian/control

In today's annoucement of the release update, Marc Brockschmidt mentioned the release goal to make UTF-8-clean control and changelog files. I was also working on Pootle for i18n.debian.net and such non clean files for linux-doc-html-pt and linux-doc-text-pt were annoying me. So, I just decided to NMU these packages and fix the 20th century ISO-8859-1 encoding they use in debian/control. As this was easy, I decided to NMU (0-day....all these packages had longstanding bug reports while the fix is trivial) all other packages with badly encoded debian/control files and, as of tonight, there should not be such files anymore in unstable. Maintainers with badly encoded debian/changelog, watch out for your asses, I could decide for such a campaign for your stuff. So, please fix this: this is as easy as using "iconv".

Adam Rosi-Kessel: Recycle Your PACER Documents

Brilliant and legal. Technorati Tags: , , , ,

2 February 2008

Christian Perrier: Preparing lenny D-I beta 1: l10n status 2nd day

(no, I won't make a daily post) After one day only, and a general call for updates, we went up to 22 complete languages for D-I level 1. +4

Junichi Uekawa: git new release deprecates git-xxx.

git new release deprecates git-xxx. I learned that git 1.5.4 now deprecates the 'git-xxx' format of commands and recommends people to switch over to 'git xxx'. Due to the confusion with GNU Interactive Tools, as a Debian user I avoided the 'git xxx' format and all my scripts are written in 'git-xxx'. In fact, all the manpages are in the 'git-xxx' format as of 1.5.3.8 (the previous release done in December). So... erm... yeah.

Joerg Jaspert: DebConf8 Call for papers and registration opened

Finally I was able to open the registration for DebConf8 and send the Call for Papers. For the full details please read the whole mail. We had a lot of work in the last few weeks to make this possible, as we set us the goal “We will keep all data entered last year, people won’t have to enter that again”. And we made it! It wasn’t all that easy to do, as we switched from the old 0.2.10 version of Pentabarf to the more recent, completly rewritten 0.3.9 release of it. Which had a completly new database schema, making the database upgrade a fun task, having had a lot of changes for our own data… After Mark and Stephen finished the database it was my task to get all the changes to the interface back which we had done. Which took about a week longer than I expected it, unfortunately delaying the CfP about 4 days. But hey, the new code is way better now. The actual difference between us and plain upstream is about 30% of that with 0.2.10. Which is nice. Of course we still miss a few things, but those aren’t important for the CfP and will be readded soon. Some of those features also will be sent (and most possibly merged) upstream. A big thanks go to Mark (mhy) Hymers and Stephen (sgran) Gran who did the database upgrade (keeping all our own data in it!) and to upstream who did help me out multiple times to get this running. (Yes, this stuff is also the reason why NEW got that huge again. No worries, I will fix that this weekend, shouldn’t take more than one or two “NEW-sessions”).

Miriam Ruiz: is Yahoo! Answers rejecting Open-Source options in their forums?

Guess what happens if you recommend free software in Yahoo! forums? Your message might just be deleted for violating their Community Guidelines or Terms of Service. Someone got a computer from a friend that had some serious problems with Windows. They had none of the disks (XP or restore) and were asking for recommendations. Amanda Kerik’s suggestion was to install Ubuntu or Kubuntu instead. It seems that they didn’t like that suggestion in Yahoo! Answers, as they simply deleted it. Might it be that Yahoo! simply loves Microsoft too much?

Next.

Previous.