Search Results: "ag"

27 November 2007

Neil Williams: GPE in Emdebian

These are all just 'first-builds' so problems could well lie ahead but I have now built a set of cross built packages for Emdebian (ARM) that edos-debcheck says is installable for a basic GPE installation. Only one package remains as a problem - gpe-filemanager builds fine but the current dependencies of libgnomevfs mean that gconf is required which doesn't give an option to disable ldap which is something I would rather do without. Certainly, existing GPE installations do without ldap but that could just be because these tend to use older versions of the particular libraries.
The GPE team status report covers the rest of the package set with links to the Debian and Emdebian packages.
I've got a few ITP's to close and a few more to open and close before the full GPE toolset is available (and I need to work out what has happened to the source package for gpe-terminal) but things are looking good.
All the cross building problems were in the base packages and a few of the lower level system libraries - the X libraries and GPE applications cross build very easily, thanks mainly to CDBS support in emdebian-tools.
The hard task lies ahead - configuring the packages so that Emdebian can support pre-built installation images for specific devices with their specific hardware configuration (and nothing else).
I'm expecting a 70% reduction in the amount of space required for the same package set relative to Debian.
When browsing the Emdebian package set you may think that 1,736 packages (or so) is a lot but this is mainly down to the Emdebian Tdeb implementation which splits out each translation for each package into a package of its own.
The next stage of the Tdeb process is to migrate those packages into a separate repository and finish the development of langupdate. Then, each user can choose to install only the .mo files required for their specific needs instead of getting 250Mb of translations for languages that are unsupported on their machine anyway.
The main deviation from the existing tdeb proposal is that Emdebian needs finer granularity so that gettext translations are separate from translated manpages - because Emdebian doesn't include any manpages.

Christian Perrier: Update your sarge and etch samba servers with care

Information is currently not completely tripled checked but I would advice all readers of this blog entry to think twice before upgrading their Etch-based samba file servers to 3.0.24-etch6 (and maybe also 3.0.24-etch7). Same for 3.0.14a-sarge8 (and -sarge9). According to bug #453050, a quite major regression was introduced in these versions and may affect most file servers with Windows clients (which is most often the purpose of samba...). So, unless you want to screw out tons of Windows users, you really should consider upgrading to 3.0.24-etch5 or 3.0.14a-sarge7 (to fix recently unveiled security issues) which do not experience that regression. Or, if your servers are less security-challenged, stick with -etch4 and -sarge7. There might me some delay sorting this out as finding the cause of the regression requires expertise I don't have and Steve Langasek (who did most of the very hard work on last updates) may not be available immediately to work on this with upstream. It is not really clear to me whether the issue is coming from upstream or bad regression fixes in Debian packages, but you've been warned. Of course, we need to find a better way to dispatch that information than a simple blog entry. I don't have it right now so better this than nothing. Again, I'm not 150% sure of all that information but heavy users of samba servers should really be careful. Update: Steve (who never sleeps) found out that one upstream commit may have been ommitted while merging their changes. More investigation is still needed, though, as that patch does not cleanly apply on -etch7.

Bastian Venthur: Time-lapse-video-with-your-webcam mini HOWTO

I bought me a cheapo webcam the other day and the first thing (meh… actually the second. The first thing I had to do was obviously getting this little piece of plastic working…) I wanted to do was making a time-lapse video of me working on my diploma thesis or something. With a little help from google and the friendly folks at debian-user-german I finally got it working. snapshot.jpg What you need: camserv, wget and mencoder. Assuming you have your webcam working with v4l, camserv will provide snapshots of your cam via http://localhost:9192, so the following script will make a snapshot every second until you kill it:

#!/bin/sh
while [ 1 ]; do
    wget http://localhost:9192 -O  date +%s .jpg -q
    sleep 1s
done

Let it run for several hours and then create the movie with the following script:

#!/bin/sh
mencoder "mf://*.jpg" -mf fps=25 -o output.avi -ovc lavc -lavcopts vcodec=mpeg4:mbd=2:trell=yes:v4mv=yes

Hint: coding, juggling and even sleeping at your desk looks cool in time-lapse - eating or singing your favorite songs while listening to them does not :P I recorded myself for ca 12 hours and the resulting video was like 130 megs large. The result looks pretty funny, but since there was a lot of the not-so-cool-looking eating and singing stuff in there, I’m afraid I can’t even show it to my closest friends ;) Hint for users having problems getting proper images from camserv: I had to change max_frames value to 1 in the [socket] section of /etc/camserv/camserv.cfg to get proper single images via wget. I find the camserv solution to get the images from the webcam rather suboptimal, has anyone a smarter solution? NP: Gianna Nannini - Bello e impossibile

Ingo Juergensmann: The data retention law in Germany

The german parliament has passed a law for retention of all communication data for a period of at least 6 months lately - despite all protests from various groups, organizations and experts.
Only the opposition (the Greens and the FDP/Liberals) voted against the law (and some single persons of the other parties). Some, who voted for the law, said later that they consider the law being against the constitution (Grundgesetz) and that the Federal Constitutional Court (Bundesverfassungsgericht) will bring the law (or parts of it) to fall.

When you wonder what this is all about, you may want to read the article "Personal Data Is Now on the Record in Germany" by Rose-Anne Clermont.

There will be a complaint of unconstitutionality (Verfassungsklage) against that law. It's going to be the biggest complaint so far with about 20.000 petitioners. The protests are still going on.

Anyway, data rentention is happing all the time whenever you communicate, but it's a new change that every communication data has to be recorded for at least 6 months. Prior to the new law, data retention was only allowed for billing purposes. Now it's the default and not only Police and Courts are allowed to access the collected data, but organizations like RIAA or MPAA are aiming at getting access as well.
Basically there is no communication privacy anymore.

Given the other "security laws" lately, like the new biometric passport, the Passenger Name Records (PNR), it's really threatening our privacy and democracy. And yet it's still unproven that this will cause less terror.

Michal Čihař: Binary packages for Gammu, Wammu and python-gammu

When Ubuntu announced public availability of Personal Package Archives, I thought it might be good to use it to provide up to date Gammu related packages. After successful registration I uploaded Gammu package and no reaction so far, so I'll wait. However this memorised me that I wanted to use OpenSUSE Build Service for same purpose some time ago. I filled in registration and as I didn't receive any email about being accepted, I absolutely forgot about that. Now just tried to log in and it works. So you can now have access to latest Gammu, python-gammu and Wammu packages for most recent RPM distributions (Fedora 7, Fedora 8, Mandriva 2006, Mandriva 2007, openSUSE 10.2, openSUSE 10.3, openSUSE Factory, SLES 9 and SLE 10). I could not test them so any feedback is welcome :-). You can find all packages on overview page or directly in download folders. Playing with spec files after long time was quite painful, but I got to it after I managed the hardest thing - how to make build dependencies which will work on all these distros. I hope I will be able to announce similar service for Ubuntu users using PPA, but now I have to wait for some reaction on my source uploads.

Daniel Leidert: LDFLAGS = -Wl, as-needed

Now that I discovered this nice flag I checked a few of my packages. It works nice for the gnome-chemistry-utils application packages. Unfortunately libgcu0 does not benefit from the flag because of libtool bug #347650. However there is an appreciably difference in the dependencies for the plugin and application packages, where the amount of dependencies decreased. For example compare the old
Depends: iceweasel   iceape-browser   xulrunner, libart-2.0-2 (>= 2.3.18),
libatk1.0-0 (>= 1.20.0), libc6 (>= 2.6.1-1), libcairo2 (>= 1.4.0), libgcc1 (>= 1:4.2.1), libgconf2-4 (>= 2.13.5),
libgcu0 (<< 0.9), libgcu0 (>= 0.8), libgl1-mesa-glx   libgl1, libglade2-0 (>= 1:2.6.1), libglib2.0-0 (>= 2.14.0),
libglu1-mesa   libglu1, libgnomecanvas2-0 (>= 2.11.1), libgnomeprint2.2-0 (>= 2.17.0),
libgnomeprintui2.2-0 (>= 2.17.0), libgnomevfs2-0 (>= 1:2.17.90), libgoffice-0-4 (>= 0.4.2),
libgsf-1-114 (>= 1.14.7), libgtk2.0-0 (>= 2.12.0), libgtkglext1, libice6 (>= 1:1.0.0), libnspr4-0d (>= 1.8.0.10),
libopenbabel2, liborbit2 (>= 1:2.14.1), libpango1.0-0 (>= 1.18.3), libsm6, libstdc++6 (>= 4.2.1), libx11-6,
libxml2 (>= 2.6.27), libxmu6, libxt6, zlib1g (>= 1:1.2.3.3.dfsg-1)
and the new Depends field for gcu-plugin:
Depends: libc6 (>= 2.6.1-1), libgcc1 (>= 1:4.2.1), libgcu0 (<< 0.9),
libgcu0 (>= 0.8), libglib2.0-0 (>= 2.14.0), libgnomevfs2-0 (>= 1:2.17.90), libgtk2.0-0 (>= 2.12.0),
libnspr4-0d (>= 1.8.0.10), libstdc++6 (>= 4.2.1), libx11-6, libxml2 (>= 2.6.29), iceweasel   iceape-browser  
xulrunner
As another example bluefish now (the next upload) really only shows the necessary dependencies. Compare the current:
Depends: libart-2.0-2 (>= 2.3.18), libaspell15 (>= 0.60),
libatk1.0-0 (>= 1.20.0), libbonobo2-0 (>= 2.15.0), libbonoboui2-0 (>= 2.15.1), libc6 (>= 2.6.1-1),
libcairo2 (>= 1.4.0), libfontconfig1 (>= 2.4.0), libgconf2-4 (>= 2.13.5), libglib2.0-0 (>= 2.14.0),
libgnome2-0 (>= 2.17.3), libgnomecanvas2-0 (>= 2.11.1), libgnomeui-0 (>= 2.17.1),
libgnomevfs2-0 (>= 1:2.17.90), libgtk2.0-0 (>= 2.12.0), libice6 (>= 1:1.0.0), liborbit2 (>= 1:2.14.1),
libpango1.0-0 (>= 1.18.2), libpcre3 (>= 6.0), libpopt0 (>= 1.10), libsm6, libx11-6, libxcomposite1 (>= 1:0.3-1),
libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 1:4.0.1), libxi6, libxinerama1,
libxrandr2 (>= 2:1.2.0), libxrender1
to the “upcoming” Depends field:
Depends: libaspell15 (>= 0.60), libc6 (>= 2.7-1), libglib2.0-0 (>= 2.14.0),
libgnomeui-0 (>= 2.17.1), libgnomevfs2-0 (>= 1:2.17.90), libgtk2.0-0 (>= 2.12.0), libpango1.0-0 (>= 1.18.3),
libpcre3 (>= 6.0)
Nice result. I should check (my) other packages too :) Maybe that’s also something for debichems TODO list.

Clint Adams: Return of the Back Bay Backbiters

I was running down Boylston to avoid smelling ICF guy, and, much to my surprise, I accidentally kidnapped a young girl. Look well, I said, after distracting her from the lotion store. Up there, by the rainbow mezuzot, what do you see? She squinted, bit her lip, and squeaked Is that Coldplay they're listening to? I'm afraid so, I replied, and waited as she drew me this: [happy family]

Evan Prodromou: 5 Frimaire CCXVI

We had a nice trip the rest of the way home from our Thanksgiving in New Jersey today. This morning we had breakfast in the Holiday Inn Express that we stayed in (very nice, new, clean, good pool and exercise room -- a good value for $109/night dual queens). We then spent the rest of our morning shopping at the Whole Foods Market. It's the closest Whole Foods to our house in Montreal -- hold it, no, it looks like the one in Portland (Maine) is closer. Who knew? We picked up a lot of hippy-dippy personal hygiene items that we can't seem to find in Montreal, and I also got a few bottles of wine to take across the border. I got a bottle of 2003 Andrew Will Cellars Champoux Vineyard -- an interesting Columbia Valley red blend, mostly Cabernet Sauvignon that I think will cellar nicely for a couple of years, but not too urgent. And I also picked up a 2004 Hanzell Vineyards Chardonnay, Sonoma Valley, which I also think will sit nicely for a year or so. We'll see -- I'm not really big on cellaring yet, but I'd like to give a few wines a try. We stopped in Amherst (Massachusetts) for lunch at the Amherst Brewing Company, which has good pub grub, generous portions, and really nice house brews available. We also dropped into a few bookstores. Books are a great cross-border purchase for Canadian residents, since their cover price is usually ridiculously skewed. For example: I got a Paul Auster hardback that was labeled at $22 US, $28 Canada. That's with the loonie trading at US$1.01! Our drive up to Montreal was pretty decent, although we had a ton of rain and snow that made the actual driving kind of sucky. We stopped in a cruddy gas station in Sharon, Vermont that didn't have a bathroom (doh!) and didn't stop much afterwards until Burlington. We got dinner at a great place in downtown Burlington, Burlington Hearth (AKA American Flatbread). Great oven-fired pizza, organic ingredients, nice atmosphere, more microbrew. Fabulous. We got across the border all right, although I needed some time to get my new work permit for 2008. Then a long snowy drive back home, where my friend Damien from Austin is staying with us for this week during MIGS. Should be a fun week -- we have lots to catch up on. tags:

26 November 2007

Steve Kemp: You're making me live

Is there an existing system which will allow me to query Apache logfiles via an SQL string? (Without importing into a database first). I've found the perl library SQL::YASL - but that has a couple of omissions which mean it isn't ideal for my task: Still it did allow me to write a simple shell which works nicely for simple cases:
SQL>LOAD /home/skx/hg/engaging/logs/access.log;
SQL>select path,size from requests where size > 10000;
path size 
/css/default.css 13813 
/js/prototype.js 71261 
/js/effects.js 37872 
/js/dragdrop.js 30645 
/js/controls.js 28980 
/js/slider.js 10403 
/view/messages 15447 
/view/messages 15447 
/recent/messages 25378 
It does mandate the use of a "WHERE" clause, but that was easily fixed with "WHERE 1=1". If I could just have support for count I could do near realtime interesting things... Then again maybe I should just log directly and not worry about it. I certainly don't want to create my own SQL engine .. it just seems that Perl doesn't have a suitable library already made which is a bit of a shocker!

Maximilian Attems: Sony VGC Ubuntu Install

This Sony 22' display is fun to watch movies or tv. Installed Ubuntu on such a all in one desktop for a friend. As much as Debian improved visually thanks to newer Gnome and good upstream tango icons. I'm much less impressed by the visual appearance of Ubuntu 7.10. The compiz stuff is fun of course, but the replaced icon sets seem like a regression nowadays.
The logout buttons seem uglier and more misplaced then the usual Gnome ones, same story with the orange openoffice.org or the gnome menu icons. Restricted-manager failed in strange loops due to no initial network availability. Network-manager seemed to write settings to the correct file for static ip setup, but didn't actually set up the network. Also the "play Dvd" usecase seemed not much easier then in Debian. Only bonus is the python apt sugar "Add Remove Applications".

Russell Coker: Pentium-3 vs Pentium-4

I recently was giving away some old P3 and P4 machines and was surprised by the level of interest in P4 machines. As you can see from my page on computer power use [1] the power use from a P4 system is significantly greater than that of a P3. The conventional wisdom is that the P4 takes 1.5 times as many clock cycles to perform an instruction as a P3, the old SPEC CPU2000 results [2] seem to indicate that a 1.5GHz P4 will be about 20% faster than a 1GHz P3, but as the P4 has significantly higher memory bandwidth the benefit may be significantly greater for memory intensive applications. But generally as a rule of thumb I would not expect a low-end P4 desktop system (EG 1.5GHz) to give much benefit over a high-end P3 desktop system (1GHz for a desktop), and a 2GHz P4 server system probably won’t give any real benefit over a 1.4GHz P3 server system. So in terms of CPU use a P4 doesn’t really offer much. One significant limitation of many P3 systems (and most name-brand P3 desktop systems) is the fact that the Intel chipsets limited the system to 512M of RAM. This really causes problems when you want to run Xen or similar technologies. I have a few P4 1.5GHz systems that have three PC-133 DIMM sockets allowing up to 768M of RAM (it seems that PC-133 DIMMs only go up to 256M in size - at least the ones that cost less than the value of the machine). Another issue is USB 2.0 which seems to be supported on most of the early P4 systems but none of the P3 systems. 512M of RAM is plenty for light desktop use and small servers, my Thinkpad (my main machine) had only 768M of RAM until very recently and it was only Xen that compelled me to upgrade. The extra power use of a P4 is significant, my 1.5GHz P4 desktop systems use significantly more power than a Celeron 2.4GHz (which is a much faster machine and supports more RAM etc). Low-end P4 systems have little going for them except for 50% more RAM (maybe - depends on how many sockets are on the motherboard) and USB 2.0. So it seems strange that people want to upgrade from a P3 system to a P4.

Miriam Ruiz: gkismet

Gkismet is a GTK GUI fontend for Kismet wireless sniffer. It is helpful because it allows you to display more data to the screen at once than the curses client shipped with kismet itself, and is conveniently useful to connect to multiple instances of kismet. There are however additional system requirements and a graphical environment in order to run it. I needed gkismet for myself, so I decided to properly package it. I’m not sure if I want to put it into Debian, as it seems to be unmaintained upstream (“Rather than trying to fix the problem with unbalanced quotes in Kismet data I am going to wait and see if I can re-write the whole thing in Java.”). In any case, I thought it might be useful for someone else, so there it goes.

Pierre Habouzit: git-commit(1) vim ftplugin update

Dear vim-ers, yes I know my git.vim ftplugin was kind of a dirty hack, and that it didn't worked that well. Since a few days, git.git next branch shows relative paths in git-status(1) and that was the last hit to my already not that stable hack. So I raised the question on the git mailing list on how to do that plug-in properly, and it happens there is a perfect solution, that was here from day 1 So here is a new release of the plugin that uses the special index[1] git-commit(1) builds for the occasion, hence can use git-diff(1) directly instead of parsing clumsily the commit buffer. Direct benefits:
Notes [1] or commit staging area ;D

Andrew Pollock: [life/americania] Thanksgiving below zero

We got home from our week in Arizona late last night. We decided to drive non-stop yesterday, and get home in a day, rather than split it over two days like we did getting there. It ended up taking around 15 hours (we had an unexpected delay at Lost Hills because we found a stray dog (we initially thought it to be injured to boot) and Sarah was trying to get hold of some local animal control people to do something about it), otherwise it'd have taken closer to 14 hours. The drive to Phoenix was pretty uneventful. We took our time leaving Mountain View on Sunday (we had an early Thanksgiving dinner with all of our neighbours on Saturday night), and decided to call it a night at Cabazon. For about the same price that we stayed in a crappy motel last time we went this way, we stayed at the Morongo Casino, which was really nice. We were in a "Canyon View" room, and, well this is what the view looked like... We arrived at Craig and Sarah's place at about 5pm on Monday afternoon. Their new place is really nice. It's huge, with a huge yard, and a nice view of the hills. I've found suburban Phoenix (well Peoria to be precise) to be the closest looking thing to what I consider "normal Australian suburbia" that I've seen so far in the US. Granted, Peoria's a bit upmarket (at least the part that Craig and Sarah live in). So we spent a day and a half vegging out at Craig and Sarah's place, then on Wednesday afternoon, we headed off to Woods Canyon Lake, in the Sitgreaves National Forests. I rode most of the way with Craig in their new motor home, and then swapped to drive our car after we got close to our destination. It turns out that the headlights in RVs are universally crap, so it was better for the Prius to be out front lighting the way on the gravel road. I'd always associated Arizona with cacti and sand, but as it turns out, the majority of the state is forest. We arrived at the campsite after nightfall, and set up shop. We met some of Craig and Sarah's friends that night, who were all very friendly towards us. It was ridiculously cold that night. We went to bed rather under-dressed for the temperature, and absolutely froze. The next day (Thursday), we all drove from the campsite (Craig towed their Jeep behind the RV) to Woods Canyon Lake itself, and went fishing. Arizona fishing licences for non-Arizona residents were a bit on the expensive side, so Sarah and I just hung out on the rocks and chatted to people and took photos. The collective haul of trout from about 5 hours fishing was pretty impressive. I'm not quite sure why, but Friday was the group Thanksgiving dinner. Everyone pitched in, and cooked up a storm. They deep-fried three turkeys (which came out very nice and looking much less like KFC than I expected), and we had way more food than we needed. We all ate outdoors at around 3:30pm, and it was about 33°F (0.55°C). The only downside of this (aside from it being bloody cold) was the leftovers went cold almost instantly, so going back for seconds was a bit of a disappointment. Everyone gravitated back to the fire pretty quickly afterwards. It got pretty cold that night. I think it was down around -4°C when we went to bed that night. We left a bit before 8am the next morning, and the car thought it was -7°C outside. One of the other campers told Sarah his thermometer was reading something closer to -14°C. I'm not sure how cold it was when we were in New York in January, but I didn't think it was that cold. It was a good week away. The mix of camping and not camping was about just right. Now it's back to work for two weeks before we head off to Australia. Photos from the trip are here.

Joey Hess: thoughts on replacing autofoo

The idea of replacing the auto tools with GNU make code could be a good thing. I tend to just write simple Makefiles, and avoid using autofoo in new projects at all. That's not good for portability, but it's excellent for sanity. But, what caused the auto tools to become such a mess in the first place? Part of it was the design, which from 30,000 feet is to write a code generator for some not ideal, but lowest common denominator language, and ship a copy of the (generated) code with every project. The new design is to write an include file in some not ideal, but almost lowest common denominator language, and ship a copy of that with every project. This avoids many of the pitfalls in the original design, such as having to deal with, and avoid editing, thousands of lines of nasty generated code when a build fails. I'm afraid it doesn't avoid other pitfalls we've seen with the auto tools. One being that all these copies of code need to be kept up to date. Another being that the interfaces between such an include file and the Makefile that would use it tend to be very broad, and, if not very well defined, can make upgrading the include file break things. As happens when you try to use the wrong version of the auto tools on a project that was written for an earlier version. Maybe smarter people than I can get around these problems. And there's probably, sadly, truth to the idea that to get a system like this really widely adopted, it needs to distribute build code that uses only lowest common denominator tools. (I was going to talk about how I started off using a similar include file but redesigned and sidestepped these problems while still getting wide acceptance for a build tool in the Debian community, but I see I already blogged about that earlier, in debhelper autoconf grudge match.)

Evan Prodromou: 4 Frimaire CCXVI

Long weekend of travel and family, and now we're back on our way to Montreal. I spent most of Thanksgiving weekend with my father's family in New Jersey, where he and my mom both grew up and where 4 of his brothers and sisters still live (and their kids, and so on). We left Montreal on Tuesday afternoon, had dinner in Albany, and got down to Newburg (New York) in the early evening. The next morning we spent several hours at the nearby Woodbury Common Premium Outlets, which was about as crass and consumeristic as it sounds. But the loonie is still strong, and it's nice to buy some clothes. I especially like buying things a few sizes smaller than what I had to get a few months ago. Wednesday night we got into Hillsborough, NJ, where my Aunt Barbara lives, and visited with her and her family. Barb has four great kids -- Phillip (16?), Maddy and Vicky (14?), and Nick (13?), who are all my cousins despite being at least 20 years younger than me. When Amita June was too tired to move we hit the hay for the night, and in the morning we all hung around playing Wii sports (even AJ!), and had a hearty dinner in the early afternoon. Then we went to my Uncle Paul's for dessert, coffee, and a nice 2003 Ramos Pinto Vintage Port that we brought along. Friday and Saturday we spent at my Aunt Helen and Uncle Marty's house in Highland Park (New Jersey). They have a great 100-year-old house right by the Raritan River, and it was really nice seeing them. We had dinner with Paul and his wife Eileen on Friday night, and we saw the lighting of the Christmas tree in Princeton. Today we started the two-day trip home. It's not really that long a drive -- about 6-10 hours, depending on the route and kind of weather -- but we like to split it up into two days, since we have a 2-year-old aboard. We stopped in New York (city)/Queens to see our friend Jen for brunch at a nice place called Quaint, where I got a good house-cured salmon and Maj had an excellent bowl of granola. Amita got some nice challah french toast, which she wolfed down with the help of her kind parents. Tonight we stopped in the Pioneer Valley in Massachusetts to sleep over. I like this part of MA, and the New York Times had a recent article about its bookish culture, called In the Valley of the Literate. We had a nice quick dinner at Bueno Y Sano in Northampton, and we'll stick around tomorrow for more shopping (books! Whole Foods!) and a little site-seeing before we head home. It'll be good to be back in MTL, though. I miss my bed, and we only have a few weeks there before we're off again to California for Christmas time. tags:

Montreal SantaCon Speaking of Christmas, one of the things we'll be shopping for tomorrow is santa costumes. Friday, November 30th is SantaCon Montreal 2007. SantaCon is a world-wide anarchic cluster-together of goofballs and lunatics who go rampaging around their town from bar to mall to bar in full Santa costume (or Mrs. Santa, or elves, or reindeer, or something similar). Everyone's invited, nobody's in charge, and a fun time is had by all. SantaCon started in the 90s in San Francisco (like everything), but I never managed to go. I finally went to SantaCon in Austin in 2001, and had an amazingly good time. My pals at The Ministry of Truth have photo evidence here and here and here. There's nothing like overflowing a bar with 100 of your new best friends, all dressed like Santa, dancing and goofing off and having a good time. It brightens up everyone's day. Anyways, we'll be picking up Maj the beginnings of an outfit here on the US side of the border, so she'll be able to accessorize with her own bits and pieces. I'll probably pick up a couple of spares for friends in Montreal, too. I'm really looking forward to the event -- it should be a good time. There's a Facebook event for people who go for that kind of thing. tags:

le Sans Fil to go municipal I was excited to read (via Steve Faguy) that our beloved local community wireless group, le Sans Fil will be providing wireless to many parks and open spaces around Montreal. This is great news for Montrealers -- the city had previous vowed up the street and back that it would never have a municipal wireless program of any sort. So good deal. It sounds like it's going to be a tough job -- I don't think wiring up outdoor spaces for wireless is anywhere near as easy as doing caf s or homes. And I think it's going to be tough to show value -- after all, people are only outdoors in parks in great numbers during the few warm months of the year here. And when people are out in parks, they're not usually checking their email -- they tend to do more outdoorsy things. But my guess is that park culture will adapt to the new resource pretty well. Congrats to SF -- I think they're a great organization that's up to this new challenge. tags:

Rob Taylor: In Critique of Git

Now as anyone who knows me knows, I love Git. I find it gives a very productive and comfortable workflow. One of my favourite new(ish) features is git rebase --interactive, which along with cheap’n'fast branching gives a great way to hack and commit as you go and then later on refactor your work into sets of nice orthogonal patches. However, there I do still find a good few things wrong with git, so I’d like to discuss these problems and possible solutions:
  1. Error Messages In general git has some terrible cryptic error messages. My favourite example is if you modify a file and then pull a change that modifies that file before you commit it: Updating beb8c37..b953e6f
    test: needs update
    fatal: Entry 'test' not uptodate. Cannot merge.
    WTF? what does uptodate mean? why isn’t it up to date? whats gone wrong? what should i do?
    Surely something like: Cancelling pull as 'test' has changes that would be overwritten by this pull. Please commit your changes or force an overwrite using the '--force' flag would be a lot better? I leave it as a reader excercise to repeat this process for most error messages…
  2. The index Why oh why oh why is it called the index? It does no indexing as far as the user is concerned. Its name gives you no clue to what it is, you don’t know when or how you’re supposed to use it. git add and git rm modify it and it’s used all over the place by the obscure low-level git helpers that you stumble over. How about commit staging area, that being what it actually is. You could have nice commands like git stage and git unstage and git stage --interactive. That’d make more sense, right? Then git add and git rm would be a lot more meaningful, being only used when you actually want add or remove a file.
  3. Remotes With git remote this is a lot better than it used to be - having to use cryptic refspecs (see git-pull manpage for the gory details). Unfortunately refspecs are still scattered all over the documentation just to confuse you… That should almost certainly be moved out to less user-visible documentation. The main issues I have now are:
    • Remote branches don’t always behave like local branches when they should. In particular git pull . <remote branch name> doesn’t work (and gives an obscure error) but git merge <remote branch name> does. remote branches should act just like local branches you can’t modify.
    • I’m not sure I like git branch -r to list remote branches, maybe git remote branches would be nicer and more obvious, or even git branch --remote
  4. Lots of git-* commands that confuse people This is a common complaint, and I have to say that I agree. Why not put all the low-level commands in libexec? People who really use them often (which can’t be many!) can always add it to their path.
  5. No bug tracker! For such a user-facing tool, a bug tracker would be very useful for users who lack the experience or time to get their hands dirty in the codebase. It certainly seems that just taking bugs to the mailinglist without a patch isn’t generally useful.
So, what do people think? What other bugbears do beginners and experienced git users see? Are these useful ideas? After some discussion, I’ll happily take these to the git mailing list and come up with some patches! Update:
Looks like people had some problems with my OpenID based login. Comments are now open.

25 November 2007

Jeff Licquia: Another Long Hiatus

Wow. Has it really been that long since my last post? It occurred to me today, as I upgraded to the latest WordPress and watched the ongoing security nightmares, that going through this effort is only useful if I actually use the darned thing. And I’ve been busy; yes I have. I’m now the webmaster for my son’s Boy Scout troop, using MediaWiki as a CMS with an eye to encouraging more parent and Scout participation in the site. I’ve been to Montreal and Salt Lake City, among other places. And I’m preparing to upload a Debian package for virtualenv, a cool alternative to OS virtualization in the Python space. More later.

Brandon Holtsclaw: Hello Planet Debian

It seems there is a long standing tradition to post a “Hello Planet” entry when being added to a new planet. Well Hello http://planet.debian.org , My name is Brandon Holtsclaw, and have done a bit of Debian and Ubuntu work over the last few years ( and hopefully will continue to do-so ). Only my posts taged with “planet-debian” are fed here so hopefully I wont spam totaly “unrealated to debian” things. Thanks Mako for getting me all setup. If you would like to see all my posts or know a little bit more about me you can follow these few links ( or drop me an email ):
http://www.imbrandon.com/
http://qa.debian.org/developer.php?login=brandon@imbrandon.com
https://launchpad.net/~imbrandon Nothing more to see here … move along.

Manoj Srivastava: Manoj: Filtering Accuracy: Brown paper bag time

After posting about filtering accuracy I got to thinking about the test I was using. It appeared to me that there should be no errors in the mails that crm114 had already been trained upon but here I was, coming up with errors when I trained the css files until there were no errors, and then used a reg exp that tried to find the accuracy of classification for all the files, not just new ones. This did not make sense. The only explanation was that my css files were not properly created and I thought to try an experiment where isntead of trying to throw my whole corpus as one chunk at a blank css file, I would feed the corpus in chunks. I cam up with an initialization script to feed my corpus to a blank css file in 200 mail chunks; and, while it was at it, renumber the corpus mails (over the years, as I cleaned the corpus, gaps had appeared in the numbering). I have also updated the retraining script Voila. I am getting a new set of css files which do not appear to show any errors for mails crm114 has already learned about in other words, for mails it has seen, the accuracy is now 100%, not 99.5% as it was a couple of days ago. While it is good news in that my classification accuracy is better than it was last week; the bad news is that I no longer have concrete number on accuracy for crm114 anymore the mechanism used now gives 100% accuracy all the time. The funny thing is, I recall going through this analysis a couple of years ago, where I predicted that one could only check for accuracy with a test corpus that had the same characteristics as real mail inflow, and which had not been used for learning. That wold mean I would have classified testing corpus that could improve the efficiency of my filter, but was not being used to provide accuracy numbers I have gone for improving the filter, at the cost of knowing how accurate they actually are.

Next.

Previous.