Search Results: "ag"

17 December 2007

Daniel Jacobowitz: Debian package for uni8 16 font

An anonymous reader asked for a Debian package of the font I recently posted about. One is now available here should you want it. I’m not planning to upload this to the archive, although if anyone wants to add it to an existing fonts package you are more than welcome to. I am considering merging this with GNU Unifont, so that the many missing characters show up looking out-of-place and non-matching instead of completely blank. Also, see xterm bug 456236, which should be fixed in unstable soon. Or mostly fixed, anyway; it still seems to glitch once in a while but it’s harder to reproduce now.

John Goerzen: Everything Update

It's been an interesting week. For those of you that haven't been following along: we lost power Tuesday and have been without ever since.

Yesterday was the annual Christmas party at work. About an hour away, supposed to be there at 6. So at 2:30 I went outside to see if I could get the car out past all the snow. At first, YES! But then, halfway down the driveway... well, no. Our driveway needs help. It's actually lower than the fields around it. Thankfully it's on a hill so it doesn't flood, but it does drift shut when there's snow. So the car got stuck. I dug it out, and it got stuck again. And a third time.

I eventually called my dad to see if he'd be willing to come over with his tractor and open up our driveway. He said yes, and drove the 5 miles in his tractor -- which has no cab, and it was below freezing -- and got the driveway open, and helped me get the car unstuck. We had planned to leave at 4, to give us time to get Jacob to the babysitter. We didn't think a babysitter would enjoy spending the evening at a cold house with only a generator providing power, so we were taking him to their place. Well, we left about 4:30.

We got down our driveway, onto the road, and hey -- more drifts. Yay. Got out onto the highway, over to the road to their place. Which someone, ahem, had assured me was a paved road. But instead we got 5 miles on a very drifty east-west country road. That's the deepest snow I've ever put a car through, and I am still surprised that we didn't get stuck anywhere.

So then we dropped off Jacob, and off to the party, and squeaked in just a few minutes late. Phew. It was nice to be out of the house, too.

When we picked up Jacob later -- taking the non-drifty route -- he was sleeping, of course. I carried him out to the car and put him in his seat. There's nothing quite like carrying a sleeping boy snuggled into you to make you forget the lack of electricity outside.

Today we went to church. Church was canceled last Sunday, and the Wednesday evening activities were too. So I think everybody made an effort to be there today. All sorts of electricity stories were heard. Generators moved around the countryside as those that owned them got power and loaned them out to those that didn't have power. The president of a nearby college called the church and offered two rooms at his personal residence to anyone that needed them. One woman announced during sharing time that her husband was taken to the hospital on Friday. They determined that he needed heart surgery, and that will happen tomorrow... and she added that she'd be with him for a couple of days, so if anyone needed a warm house for a family, theirs was available and had a couple of bedrooms, fridge, and garage that people were welcome to use.

At noon there was a free lunch offered to anyone still without power. We went and enjoyed some warm soup and bread with about 30 others.

After that, we went to my parents' place to do some laundry, then came home.

We ate supper. As Terah got up to give Jacob some more chili, I suggested that she look out the window and see if any yard lights were on yet. I had flipped our master breaker off, just to be extra cautious due to having wired our furnace into the generator temporarily. So this is how we would tell that power was back on somewhere (though we did check it periodically during the day). Terah looked out the window, and said, "I DO see yard lights out there... Do you think?" I got up, went downstairs, flipped the breaker, and light came on! We turned on the lights -- Jacob had missed them -- and plugged in the Christmas tree. The power had come on for people miles in either direction from us at the same time. Dad came over to get our electrical box back to normal state and to help me load up the generator to return tomorrow.

There's nothing quite like this to make us feel fortunate to be a part of such a caring community of friends and family -- people who don't think twice about helping out someone in need, even in the midst of having a husband hospitalized.

Jacob didn't seem to mind the power outage. Except for one thing. He is very excited about lights these days. I can spend 15 to 30 minutes exploring lights with him, especially in the kitchen. He will point at a light and say "da?" ("that"). "Da? Da?" means he wants it turned on or off. We'll go to the light switch, and he'll get to flip it, or watch while I do. "Dooooo!" is his excited response.

Well, when he wants something and it's not happening fast enough for him, "Da? Da?" changes to "Da!... Da!..." and then to "DA!! DA!!" and finally some fussing. That happened several times as we couldn't turn on lights.

Then we got to church this morning and boy was he excited. Lights everywhere! He'd point to one bright light and say "Da!" -- look at the light over there, dad! Point to another place and "Da!" Another one over here! And ceiling fans! Lights everywhere! He was so excited he was trying to jump up and down.

Jacob's favorite new word is "hi." He has just barely figured out how to say it, and it takes effort, and comes out very breathy -- but it's there. He can spend several minutes saying hi to someone over and over if he's in the right mood. He wouldn't say hi to the greeters at church, or anyone that said hi to him. But we were sitting in the back row, and halfway through the sermon, he started saying hi to the ushers that were behind us. I couldn't see them very well, but I imagine they were trying to keep from cracking up.

Frans Pop: aptitude upload not something to be proud of

Sometimes it is extremely tempting to wave a huge, heavy, spiked cluebat around. Today I've decided to give in to this temptation. The case in point is the upload today by their maintainer of first cwidget and later aptitude. The fact that the maintainer blogged about both uploads probably means that he's pretty happy about it. Unfortunately I, and people in the Debian release team, were less than amused. Reason is that the uploads set back a complex transition of apt and related packages by at least a week. This is a transition we'd already been following and trying to get into testing for over a month and which was finally as good as ready to go. So what was so wrong about these uploads and what could (should?) the maintainer have done? First of all he should have realized that aptitude has become a rather central package in Debian with strong ties to apt and thus to a lot of other packages. Second, he should have checked whether his previous uploads had already migrated to testing and, if not, why not. The excellent testing migration page for aptitude (which is linked from its PTS page clearly shows that it is tied in a transition involving about a 100 packages in total. The right thing to do in such a case is to contact the release team (preferably at the debian-release mailing list, or at #debian-release). This would undoubtedly have resulted in a request to delay the uploads a few days until the transition had finished. Unfortunately that did not happen and cwidget was uploaded. Because of an ABI bump it ended up in NEW. Because of the transition I did a quick request to Joerg Jaspert to please delay accepting cwidget until the transition was over. But then a third mistake, and arguably the most serious one of the lot, was made. aptitude was uploaded for i386, built against the cwidget library which had not yet been accepted into unstable. Basically that means that an uninstallable package was uploaded. And of course it meant that at that point all efforts to finalize the transition for apt went down the drain. Some alternatives were discussed on how to deal with the new situation, including a sourcefull upload of the previous version of aptitude, but in the end it was decided to just accept the delay as one of the more annoying facts of life and instead ask Joerg to accept cwidget from NEW. In the end the damage may be a bit less than a week if the buildds cooperate (which they probably won't with cwidget still stuck at the wrong priority) and the RMs decide to force things. I sincerely hope that this story will make all Debian Developers and Debian Maintainers a bit more aware of the broader context and consequences of uploads. Oh, as I'm not an RM myself you may wonder what my interest is in this. We've got this great new feature in Debian Installer that adds support for multiple CDs during an installation (a feature that was lost with the integration of base-installer into D-I). However, we can only upload the relevant D-I component after apt 0.7.9 has reached testing...

Sune Vuorela: EndExtremadura

Ah. Back home. All in all, it was a quite nice trip. I like to get actually to meet the people that I communicate a lot electronically with. Thanks Extremadura for making this happen. The last day, we stayed at the residense instead of going to the local university, as the internet at the residense was much more stable than the one at the university.
But it was still heavily firewalled. Having the svn:// port firewalled doesn’t make it too easy to work with svn - and having ssh connection time out every 5 minutes also makes it difficult to try work on some remote machine. Please. Get the network better for next time. And more bandwidth. And thanks to Nekral for the champagne && cheese ;) Now tired - and times to sleep.

16 December 2007

Steve Kemp: So here it is Merry Christmas

Lars Wirzenius recently released, and packaged for Debian, a simple script to make release tarballs. He calls it Unperish. It makes me wonder how many other people use that kind of system? Of the top of my head the only similar thing I can recall using is Brad Fitzpatrick's ShipIt - another moduler/plugin-based system (Perl rather than Python this time.) For my needs I tend to just write a Makefile which has a "dist" target, and then I have a simple script called "release". This runs:
  1. make dist / make release.
  2. creates a gpg signature of the release.
  3. scp's the resulting files to a remote source.
All this is configurable via a per-project .release file. The configuration files are very simple, the script itself is almost trivial but being able to sit in a random project directory and have a new tarball on my webserver just by typing "release" is enormously useful. There are times when I think I should make it a mini-project of its own, with the ability to auto-build Debian packages, etc. Other times I just think .. well its a hell of a lot better than my previous ad-hoc solution. At the very least I think I will make the cosmetic change of updating the script to run "make test" if there is a test/ or t/ directory inside the generated tarball. In real news - tomorrow I leave for a two week holiday with my partner's parents. Yesterday I got back from a night spent with her in York. The Bytemark staff night out. Lots of fun. Over too soon, but lots of fun.

Mike Hommey: Moving a system off to a usb disk

There are cases where you don’t want to bring a laptop with you, but still want to have your data or, even better, your system and configuration. It is actually not so difficult to do if you are using LVM. With my setup, it was quite straightforward. So, if you happen to have a similar setup (2 partitions : one for /boot, and the other one for the LVM physical volume), here are the steps to do the same (assuming the usb disk is /dev/sda, the laptop disk /dev/hda, the LVM volume group vg, and you’re using grub as a bootloader). At this point (well, you obviously still need to wait for the pvmove to end), you can reboot right now. Your boot loader setup will use your old /boot partition and the kernel will use the root filesystem on the usb disk.
Be aware of a few things, though. You still need to do two things to finish your setup, now: Now you can have any computer run your system, booting off the usb disk. It had the nice side effect that my laptop is much faster now, as the internal disk is an old 4200 rpm disk, vs. 7200 rpm for the usb disk…
You may also want to try to remove the Xorg configuration file (/etc/X11/xorg.conf) so that the video driver and resolution are not hardcoded ; recent enough Xorg do runtime detection, and that worked pretty well on the two laptops I booted with the usb disk.

Michal Čihař: Nice to see PyICQ-t back alive

I just noticed, that Python Jabber transports have been migrated this weekend to Google Code and first people started to contribute. I especially like the fact, that first contributors are Czech guys and they're fixing encoding problems :-). Let's hope that this activity will also help to improve Debian package which is not really in good state, but I promised not to hijack it till the end of year ;-) (so for now I temporarily hack it in my repository). PS: I know ICQ is evil, but I don't have enough power to force all my contacts to start using Jabber.

Kartik Mistry: [VAC] 17 Dec - 27 Dec

* [VAC] I will not able to do any Debian work except answering mails/bug reports during 17th Dec to 27th Dec. Please do NMU if anything is critical in packages. But consult, co-maintainers :) I am heading to Ahmedabad today night around 8 O’ Clock [/VAC]. Well, its for Office work, so no VAC indeed :P * This means, I will miss Kavin. He has 1/2 year birthday today!!

Biella Coleman: From serenity to offense in 5 miles or less

When you live in NYC and have a demanding job, you tend to ignore the city (at least I do), that is until guests descend upon your place. And since a Large Family Clan has recently landed in my apt, I have spent the last few days trekking north, south, east, and west, across bridges, in parks, and memorials, eating, drinking, and passing out at night after the constant flurry of activity. Yesterday we headed pretty much as far north as you can go to pay a visit to the lovely Cloisters sitting high on a cliff. The Cloisters provides stellar views of the Hudson at the same time as it transports you back in time when a lot of energy was put into scribbling religious material on paper in really stunning and ornate ways. I have not paid a visit to the Cloisters since my undergraduate days and after yesterday’s stroll, I am sorry I waited until the frigid winter to do so. It is an *incredibly* serene place, especially the inner courtyard gardens, and if you need serenity (and I think anyone who lives in NYC, needs to counter the low-grade and high-grade exposure to constant noise with some noiseless environments), this is the place to go. We then made our way to the Columbia area to check out the campus, St. John the Divine (currently under renovation), and so I could pick up a book being held for me at the Book Culture bookstore (which I wish was a lot closer to me than it is)… It was nice to escape the blustering winter conditions and browse the rows of books in a warm and well lit environment. But after purchasing Information Please: Culture and Politics in the Digital Age, parts of which I am hoping to teach next semester, and flipping through the book, my new found serenity was replaced by some serious offense when the only index I could find was an author index. There was no subject index in sight, which at the time left me totally surprised!! Anyone who is in the business of using books as research tools knows the index is —-> indispensable. And a well indexed book is much appreciated (never mind what a non-existent index does). In fact, I felt like I stumbled on some rare object because I don’t think I have ever seen an academic book published in the last 30 years not sporting this useful tool and I wonder if 1) I have a bunk copy 2) The editors/authors forgot to include it and just pushed out the book anyway 3) This was a willful choice made for reasons hidden to the reader. I think I may have to contact Duke University Press and let me know they momentarily robbed me of my serenity :-)

Erich Schubert: Keeping the website up in rankings

My personal web site - which actually is not particularly interesting, IMHO - used to get in a lot of traffic via Google. It was highly ranked on several quite interesting search terms. For example, it's still number 1 on the search term "Halbleiterlaser" (semiconductor laser), which is the topic of my secondary school thesis. So I still win against Wikipedia on this one. For "flowers" I sometimes and up at #1 in Google image search (causing lots of people to hot-link certain images from my site... might be with some geo targeting though?) But I've lost other battles to Wikipedia by now, such as the search term "Liebeskummer" ("lovesickness"; I have some old old poetry online that people dig a lot; this still makes up the biggest share of my visitors)My rankings have dropped quite a lot the last year, down about 50% within a year. I don't know if this is because I'm blogging a lot less, because I'm not updating it often enough or because Google doesn't like the redesign as much as it did like the old one. (The redesign was 2 years ago, followed by a drop in visitor numbers but a recovery to like 70% within a month)Algorithmic changes of Googles ranking are just another possible reason; I always felt as if my placement was highly overrated anyway.I added at a Google sitemap some months ago and other things that people expect to help with their site being well included, but it didn't stop the numbers from going further down. For obvious reasons I didn't buy any links or anything; I'm not making my living with that page or anything, it's just a pet project thingy. (So obviously, don't make me any SEO offers for my page!)Still it's a pity: I used to have a couple of really major placements on Google - so much that I've had some inquires if I'd like to sell my personal homepage (nah, I don't want to have to get a new email address!), offers by reputable and huge dating sites to put up ads on my page and surprisingly high offers for including my web page in link farms - but I'd have issues with that (I'd like to keep control of what my page contains; including content that might get Google to ban my page is scary), and it would have required me to run my page on PHP (ugh).I wish there was an easy way to just keep the rankings I mysteriously had acquired the last years. :-) For some time it looked like I had some magic SEO capabilities, and friends suggested I should consider actually going into the SEO business. My page is still overrated by Google, but it seems like it has lost much of it's magic.P.S. A fun story followup: I've just noticed that someone in a french cooking forum hotlinks to a photo of mine, claiming that he had cooked the food I did. Isn't that hilarious? Should I substitute that image with a g*atsee?

Joey Hess: The Man from Earth

I turned this movie off because it became clear in the first few minutes that it was a very low budget movie shot in a hurry[1] with actors who reminded me of ones from not particularly awesome plays[2]. Then for some reason I went back to it. And soon it got interesting. And then I got thuroughly sucked in. And then I was really sad that the storytelling was over. I think it's been a very long time since I was sad that a science fiction movie was over[3]. Maybe 1980? This movie is set all in one room in a cabin, and has no higher technology in it than a cell phone, and yet it's amoung the top two purest peices of science fiction I've seen performed. And the lack of special effects, especially CGI[4], was a very nice change. There's a good chance you'll not enjoy this movie, but I hope you get a chance to see it and find out. You won't find it in theaters, there's a DVD and it's on Netflix, or you can download it and paypal the director and cast a few bucks.
[1] In about a week as it turns out.
[2] Which is probably true of some of them. I only recognised one.
[3] Snip: silly-yet-true-analogy-between-typical-SF-movies-and-bags-of-potato-chips
[4] Snip: hating on most CGI

Jose Luis Rivas Contreras: Updated gkrellm, pgpdump and xscreensaver!

I recently wrote about the new version of xscreensaver and the new hacks but I just forgot to actually install them so now they're installed and thanks to my new co-maintainer Tormod Volden the packaging of xscreensaver is easier ans smooth, yet no in CDBS but easier at least, so the new release is 5.04-2 and right now I'm just waiting for damog to upload it (he's very fast BTW). I updated gkrellm with the new upstream version 2.3.1 fixing some bugs, I cleaned up all the patches and let only one for the gkrellmd.conf file, besides a made a clean up of the BTS of gkrellm, now there're less bugs remaining, the new release is 3.2.1-1 and is waiting for anibal to review it and upload it. Finally but not less important is pgpdump, a package that since a lot of time ago didn't get me any work, new upstream release 0.26 and the release 0.26-1 is waiting for anibal to review it and upload it. This last two were migrated to CDBS, so it's definitely easier to maintain, at least for me!

Matthew Palmer: Camping: CGIs on steroids

There's no way around it: I'm a bit of a Rails fanboy. While it's got it's glitches, it's certainly made the part of my life that involves writing web applications a hell of a lot easier, and introduced me to the wonder that is the Ruby programming language. However, there are plenty of times when Rails just isn't a good fit. It's not particularly simple to deploy, it's quite heavy, and it does have a definite learning curve. So, when I need to write something simple, I've just used Ruby's built-in CGI support. But I will do so no longer. For I have found Camping. The name doesn't make a whole lot of sense, and until you come to grips with Why The Lucky Stiff's weird sense of humour, the docs will probably make you think that acid trip you took several years ago has just kicked in again. However, the purpose of Camping is pretty easy to understand: it allows you to make simple (CGI level) web "applications" using Rails-like (or more properly, MVC) concepts, which are fairly easy to write and deploy. If you're familiar with Rails (or probably most of the other Rails-clones that have sprung up in other languages) then Camping will probably smell at least faintly familiar. You have routes, which map URLs to controller actions, which retrieve models and feed them to a view which sends results back as HTML. From that perspective, Camping is easy to learn -- it's core concepts can piggyback on existing knowledge, and you can get started very quickly. Using your Rails-fu, however, will only get you so far. For one thing, the API is similar-but-different enough that while your first couple of simple experiments will probably Just Work, getting more complex things done will either fall under the "different" or "difficult" headings. That isn't meant to be a slight on Camping, though -- if you want to do horribly complex things, then you're heading into territory best served by Rails anyway. But there is a bit of a middle ground where the utter simplicity of Camping is stretched a little, but it's still more appropriate to write a Camping app than a Rails app, and it's important to remember that you're not using full-blown framework when you thump up against something that's beyond-trivial in Rails, but is not quite so simple in Camping. Camping is a microframework -- it says so right there on the front page. Why's intention is that Camping will always be provided in less than 4kB of code. So you're never going to get, for instance, the broad range of HTML helpers that Rails' ActionView provides to make writing HTML templates so easy, or the Prototype JavaScript framework shipped with the main code. If you don't want to blow a steam pipe, then, when starting out with Camping, you need to think "this is a lot easier than hand-writing CGIs" instead of "this is a lot harder than writing a Rails app". There are a few things that are undeniably a pest in Camping, though. The docs are a little incomplete and hard to follow (even when you account for Why's "unique" style of writing), and some of the coding tricks that are employed in making the framework can make debugging a bit tricky. They're not showstoppers, but it's worth knowing about them in advance so you don't go nuts when you're first using the framework. If you're not the sort of person who needs small, self-contained web scripts, then I'd say you'll probably never get much benefit out of Camping. On the other hand, if you're still writing your CGIs against the "bare(ish) metal", then I would strongly encourage you to take a look at Camping, to make your life just that little bit more delightful.

15 December 2007

Lars Wirzenius: CoverageTestRunner for Python

coverage.py (python-coverage package in Python) is a wonderful little tool for measuring which parts of your program are executed while you run it. It only measures at the statement level, but even that makes it quite useful when developing unit tests. Any code not covered by a unit test is obviously not being tested. I've been using coverage.py since early this year. It's been pretty systematically the case that any code not being tested by my unit tests has at least an order of magnitude more bugs in it when it gets to production. One thing I figured out was that it's even better if you structure you code and unit tests into pairs: the code in foo.py should be fully tested by the tests in foo_tests.py. To make this easier, I wrote a "test runner" which enforces this. It tests such pairs of modules and fails the test unless all statements in the code module are visited during the test. I give you: CoverageTestRunner. I've just uploaded it to Debian, so it should be through the NEW queue after some time.

Jos Parrella: glibc 2.7 in Virtuozzo VPSs

If you’re using a Virtuozzo-based VPS running Debian Testing or Unstable (and probably other modern Linux distributions), you will probably run into problems regarding the patches used in the default kernel and glibc 2.7, which were properly described in the debian-glibc mailing list. Tektonic, my current provider, will upgrade the kernel this weekend but if you’re really in a hurry, you can set your VPS on repair mode, download a 2.6 version of libc6, install it from the repair VPS using dpkg –root=/repair –force-all –install … and restart your VPS. It will boot up, but lots of things that depend on versioned packages of libc6 won’t work correctly, most notably OpenSSH and PAM. The problem is due to non-standard TUX optimization patches implemented over Red Hat’s standard kernels, which seem to be quite popular in Virtuozzo-based VPSs (at least it seems that Strato, Tektonic and Unixshell use them?)

Sune Vuorela: Extremamamamamamamadura day 3

Day three in Extremadura
Yesterday after dinner, we phoned “Telepizza” and got a pizza with cheese and cheese a cheese - and a pizza with barbecue sauce and bacon and bacon.
After a long night of hacking we finally got to sleep. And I almost got my debian working again.
Sleeping until 10 was kind of needed after that - and I got my debian finally working again. No more ubuntu live cd.
We skipped breakfast and found a supermarket. Yay! Best food this trip so far.
A sneak peek on the lunch - and we kind of ate it, but … I feel sorry for the students dining here 3 meals every day. So far we have gotten some discussions about kde3 packaging and kde4 packaging. Lenny will probably ship with a kde3 desktop and with kde4 development platform. - and everytime someone is thirsty, the question arises: “why do they get drinking water from swimming pools?” And tomorrow it is “back home”. Kind of sad, but I miss my bed. And my hardware.

Zak B. Elep: To Australia and Back: OSDC Brisbane 2007

Its been a couple of weeks since the Open Source Developers’ Conference in Brisbane, but it was only now that I’ve got the time to blog about it. :) This is due to some work that got piled in my backlog (I haven’t been lazy enough to have this work all automated yet :(). First off, my trip to Brisbane was a long one, due to the UNDP travel agency giving me a route taking me to Bangkok first, because of my exchange grant’s papers made in short notice. No matter: this being my first ever international trip, this meant that I would be visiting two different countries in just one shot. Bangkok was just an overnight stay though, so I didn’t see much, but their new airport was nevertheless impressive. Arriving there at almost midnight, the only bright places I saw were the big Suvarnabhumi airport and the Novotel where I had my layover. After some sleep, I had a pleasant morning, but only a short one at Bangkok, as my flight to Brisbane followed after: DSC06879.JPG The Brisbane flight was long, and I arrived just an hour before midnight. Now, my next problem was getting a place to stay. I took an airport shuttle to the Royal on the Park, where the conference will be held, first to see if there are any free rooms, or barring that, some recommendation on nearby places to stay, even if only for the night. I was quite anxious because I wasn’t able to arrange for accommodation prior to this trip (short notice, remember?), so I decided to go directly to the venue to be the best way of trying my luck. And try my luck it was! First, I was greeted by a front desk manager who turned out to be a fellow Filipino, and he helped me get a room in the hotel. At the time though, he could not guarantee that I can stay there for the duration of the trip (only for the night) but he would help me to find alternate accommodation instead on the next day. I thought that was good enough, since it was already midnight by the time I reached the hotel, and just a bed to sleep on for the night would do great for me to worry about moving elsewhere later. And the next day: Day 1 of OSDC: DSC06880.JPG I was up rather too early that day; the worrying about moving elsewhere settled in too early as well, and had made me check out very early so I can hopefully look for that alternate accommodation by lunchtime. One by one, the attendees came, and soon enough more than a couple of hundred people were filling the main conference room, waiting for OSDC to begin. And we began with a keynote from Rusty Russell on C, the humbling language and Ian Clatworthy’s talk on distributed version control systems. After the keynote, I was notified by the hotel management that instead of moving elsewhere, I can just remain there for the duration of the conference. I was quite relieved! For the remainder of the day, I listened in on the Perl stream of talks from Kirrily Robert, Josh Heumann, and Jacinta Richardson, on packaging Perl modules, Perl 6, and Perl code optimizations, respectively. Kirrily’s talk was timely since I am writing a couple of Perl modules to be released on the CPAN (one, Tie::Amazon::S3, is now up ;) On the morning Day 2, I listened in on Mark Rees’ talk on testing web applications using twill and a scripting language, like Python. I then followed Adam Kennedy’s talk on the CPAN 1.5, learning about CPAN::Mini, the CPANPLUS (which IIRC will be standard in Perl 5.10) and the Tiny modules in the process. More on the Perl stream continued with another talk from Josh Heumann on intermediate Perl testing, providing a humorous yet informative strategies not really just for testing Perl scripts or modules but for software testing in general: DSC06888.JPG Later in the afternoon was Paul King’s talk on agile developer practices for dynamic languages, covering Groovy and Ruby. That was later followed by Leslie Hawthorn’s talk about the Google Summer of Code and the announcement of the Highly Open Participation contest for the young geeks who are not yet in college or university but would like to work on open source projects just like the SoC-ers. After the day’s schedule of talks, there was a break before the conference dinner, allowing also for a short keysigning session and CACert identity check. Then, we had the conference dinner, sponsored by Google. There was also a game held: every table makes up a team who, given some Play-dohs and imagination, are to make up a bug’; the best bug’ wins a free book. Unfortunately, my table/team didn’t win any books, but that was beside the point anyway, as the bugs that were made up were quite something: DSC06898.JPG DSC06895.JPG On the last day, the morning talks I attended were all about Ruby and Rails. Nic Williams gave an introductory talk on Rails, then Paul King gave another talk, this time on Grails (the Java version of Rails,) and closing the morning session was Keith Pitty’s talk on Ruby for Java shops. For the afternoon, I followed Adam Kennedy’s talk on optimizing projects for wetware. DSC06936.JPG For the closing keynote, Nat Torkington talked about the future of software: DSC06945.JPG And with a day left before returning home, I went to sightseeing mode, bought a couple of books, and the mandatory pasalubong for the relatives. At midnight, my flight took me back to Bangkok, another long trip that touched down at the crack of dawn: DSC07034.JPG After a few hours’ wait, I took the plane back to Manila, returning home just after lunchtime. This being my first international trip, making it alone seemed to be quite an adventure. But I wasn’t really alone in this endeavor: kudos goes to the UNDP International Open Source Network for their exchange grant program, to my relatives for their support, to Free and Open Source Software for really making things rock (and free ;), and to $DEITY for being there. Until the next trip!

Lars Wirzenius: EoC wiki and domain

Enemies of Carlotta, my little mailing list manager, now has a wiki, courtesy of Michael Durgener. It also has its own domain, courtesy of Andreas Barth. See: http://www.e-o-c.org/. There is also now a mailing list for commits to the EoC 2 development branch. To subscribe, e-mail eoc-commits-subscribe@liw.iki.fi .

Lars Wirzenius: Python optparse: what options got set?

While writing some code for EoC 2 to parse the command line, I needed a generic way to find which command line options were set by the user. That is, after I've parsed a command line, and have the return value of the optparse.OptionParser.parse_args method, how do I find which options were set? The return value is an instance of optparse.Values, which does not have a convenient method for that. So what I do is this:
classattrs = dir(optparse.Values)
for name in [_ for _ in dir(options) if _ not in classattrs]:
    print name, getattr(options, name)
Slightly tricky, and it may stop working in a future version if they change things in the in (undocumented, therefore private) interface, but it's nice to be able to work around library design warts like this when the language itself is nicely powerful.

Joerg Jaspert: Using a SSH jumphost

As Tolimar was asking about it and I am using the setup at some places to get past idiotic^Wbroken firewalls, where you always want to kill the clueless people that did set them up - lets write a bit how to ease ssh usage at such locations. Imagine a place where you can’t ssh elsewhere directly, you have to go through at least one, in some cases two or three hosts, to get anywhere sane.[1] So the topic is SSH jumphost. Thats basically what you do manually if you
  ssh some.host
  ssh next.host
where some.host is your jumphost. Add as many some.host as you want into this chain. We are all lazy and don’t want to type that by hand, one ssh is enough for everybody. Hurray, ssh already provides what we need, namely the ProxyCommand directive, it’s just not known as much as it should be. For this example imagine I have to ssh via the following host chain to get out: kosh -> vir -> babylon5 -> sheridan and also want to have my local port 2525 forwarded to sheridans port 25. The following config snippet (.ssh/config) is doing that[2]
 Host yay
 ProxyCommand ssh -q -A -X vir ssh -q -A -X babylon5 'nc -w1 sheridan 22'
 LocalForward 2525 localhost:25
   
 Host vir
 ProxyCommand ssh -q -A -X kosh 'nc -w1 %h %p'
The effect of this is: and I end up having a shell on host sheridan. The LocalForward line also tells ssh to tunnel my port forwarding over that multi-hop session, voila, done. Of course there is a little caveat with this - all hosts do have to know the next one (ie. .ssh/known_hosts should have the right data). You should also think about using ssh keys (maybe including Agent forwarding). You really dont want to see 5 Password: prompts right behind each other for a 5-hop setup - with no clue if its for the next host or for a typo… Update: If you are a Debian Developer and do not have a host “outside” that listens to something else than Port 22 but are behind a firewall that only allows Port 80 and 443 - you are lucky. As long as you aren’t hit by [1] you put the following into your .ssh/config file and have fun:
Host foo.gl bar.gl
ProxyCommand ssh -q -a -p 443 -x gluck.debian.org 'nc -w1 $(basename %h .gl) 22'
Add as many other config options as you want. The effect is: and as such you can get out via gluck. We are using the .gl as an extension here to remember that we go via gluck. Idea stolen from someone on IRC, just can’t remember who atm. [1] For added fun, which I have at one place, add things like a proxy with user authentication done in a way that tools like tor or openvpn can’t get through it and you always wish those admins use Windows, just so they suffer. Anyway, I talk about the first part only, using jumphost, other ways getting around crap admins needs, in my case, an own script to do it, not part of this topic… [2] Yes, one can do it in lots of ways and those here might not be the most optimized/nice/whatever ones. But they work and are just examples here, select your own parameters if you dont like mine!

Next.

Previous.