Search Results: "ag"

1 January 2007

Russell Coker: free software liason?

In my previous work as a sys-admin I have worked for a number of companies that depend heavily on free software. If you use a commercially supported distribution such as Red Hat Enterprise Linux then you get high quality technical support (much higher than you expect from closed-source companies), but this still doesn't provide as much as you might desire as it is reactive support (once you notice a problem you report it). Red Hat has a Technical Account Manager offering that provides a higher level of support and there is also a Professional Services organization that can provide customised versions of the software. But the TAM and GPS offerings are mostly aimed at the larger customers (they are quite expensive).

It seems to me that a viable option for companies with smaller budgets is to have an employee dedicated to enhancing free software and getting changes accepted upstream. For a company that has a team of 5+ sys-admins the cost of a developer dedicated to such software development tasks should be saved many times over by the greater productivity of the sys-admins and the greater reliability of the servers.

This is not to criticise commercial offerings such as Red Hat's TAM and GPS services, a dedicated free software developer could work with the Red Hat TAM and GPS people thus allowing the company to get the most value for money from the Red Hat consultants.

If using a free distribution such as Debian the case for a dedicated liason with the free software community is even stronger, as there is no formal support organization that compares to the Red Hat support (there are a variety of small companies that provide commercial support, but I am not aware of a 24*7 help desk or anything similar). If you have someone employed full-time as a free software developer then they can provide most of your support. It would probably make sense for a company that has mission critical servers running Debian to employ a Debian developer, a large number of Debian developers already work as sys-admins and finding one who is looking for a new job should not be difficult. There are more companies that would benefit from having DDs as employees than there are DDs, this isn't an obstacle to hiring them as most hiring managers don't realise the technical issues involved.

This is not to say that a company which can't hire a DD should use a different distribution, merely that their operations will not be as efficient as they might be.

Jaldhar Vyas: Should Auld Acquaintence Be Forgot?

I am the psychotherapist. Please, describe your problems. Each time
you are finished talking, type RET twice. I am worried about Debian. Are you worried often? Yes! I see... Well, why do you say this is so? The Debian project seems to be quite dysfunctional. What makes you believe the debian project seems to be quite dysfunctional? We keep having these massive flame wars. Earlier you said you felt worried? What causes you to be worried? It doesn't seem right that a group of people who ostensibly have the same goal should bicker so much. And its the same topics over and over again. Is it because a group of people who ostensibly have the same goal should bicker so much that you came to me? Yes. You are a very cheap^wgood therapist. It has been suggested that Debian could profit from therapy. Does it bother you that debian could profit from therapy? I would hope that a group of mature, intelligent, professionals could settle their differences on their own. Maybe your plans have something to do with this? I have no plans really. I just want to work on a great Linux distribution. How does it feel to want? What we have built is so great but sometimes it seems that Debian doesn't get taken seriously when outsiders see all this infighting. What happens when outsiders see all this infighting? They think we are just amateurs and they wonder why they should make their future endeavors dependant on a bunch of flighty narcissists. Do you really think that?

No of course I don't. Debian is just as good if not better than most "serious" operating systems and most of the time Debian developers do work together well and settle their differences amicably. But there are a few people who can't and they really hurt our image. I see... Tell me more.

There are some people who just can't work with each other and our current way of dealing with such conflicts is at a dead end. As long as issues are left unresolved and they are forced together, these negative people will just keep bickering and bringing the rest of us down. What are your feelings towards bickering and bringing the rest of us down? I feel that at this point only answer is for the people who can't alter their behavior to be asked to leave or to remove themselves. What do you think? Speaking as a trained psychiatrist I think you are all bonkers and I'm switching to gNewSense.

Andrew Pollock: [life] How do you put the genie back in the bottle?

The simple answer is, you can't. I didn't want cats while we were here in the US. And yet, we have three of them. We made the decision not to take our current cat with us from Australia, because of the length of the journey, and the fact that we were planning on being away a lot travelling, and because of the length of time she'd have to stay in quarantine when we returned to Australia. Then along came Stumpy, a cat we were supposed to be temporarily fostering, because she was hit by a car, had a broken pelvis and lost her tail. She was all sweet while she was convalescing, and Sarah really wanted to adopt her, so I caved in. Stumpy was probably less than a year old, so still at the boisterous kitten age, and sure enough, she recovered, and became a boisterous kitten again. To the point where she was so energetic, she needed a little friend to wear her out, and I was asked if we could get a second cat, and since I seem to have problems saying no to anything (but heck, I was getting attacked in bed by her in the middle of the night as well), along came Lily (wow, Sarah really needs to spot breaking all the image links in her blog posts). Sarah was taking Lily back to the shelter we adopted her from, for her shots, and was asked if she'd foster a tiny 4 week old kitten, that was going to have to be euthanized if a foster home wasn't found for her. We still have Smudge today, months later, technically still as a foster, but we intend to adopt her as well, because she's such a sweet little kitten, and of the three, she's the most affectionate towards me. Call this one "my" cat. Then I look at the destruction these cats have caused. I look at the damage to the really nice dining suite we bought shortly before moving over here. The leather chairs are scratched terribly. The nice wooden table top has scratches in it as well, because they liked to use it as a playground. I was setting the table tonight because we've got people coming round for dinner (it's been a while), and I saw first hand the extent of the damage. I was so pissed off I could have cried. After our last trip away, the cats got sufficiently bored that Stumpy thought chewing on laptop power adapter cables would be fun. My laptop no longer charges. (I'd just had said power adapter replaced under warranty not two weeks previously). Don't get me wrong, I love cats, I just so didn't want them right now, and especially right now, I'm wishing I'd stuck to my guns on that one. I think I'd have rather brought LC over from Australia, and not have her become obese by the new owner we found for her, than have so much of our stuff be destroyed by three kittens in a small townhouse that we're away from too often to give them the attention they need as kittens. Sigh.

31 December 2006

Simon Richter: All good things...

This year I have a weird new year celebration before me. My girlfriend is hosting a party, but I just left it (with her permission :-) ) because today is also the last night the Pulverturm is open. In the old days, before I had to think about things like getting up the next morning, I managed to be there every Tuesday, Friday and some of the Sundays, I met a number of people who are now my friends there, so it was an important bit of my life. Well, I better hurry up to get there before midnight.

Paul van Tilburg: What Etch Will Bring

With 2006 almost finished, I can look back at a succesful year for the Debian/Ruby Extras team. The infrastructure was set up and we gained 12 new team members and a lot of packages. With Etch frozen, I can now almost certainly say what Etch will bring Ruby-wise: I am proud of what we have accomplished, good work everyone! Not team related is the change that the whole Ruby stdlib is now bundled in libruby(1.8) and is no longer split up! So you all can remove those Debian-specific messages about having to “do extras things when using Debian”. ;) Future plans for Lenny Future plans for Lenny include updating and extending the Ruby Policy. Focus points will be package versioning, improving documentation. Also we intend to package even more Ruby libraries and applications and ask current Ruby lib/app developers to join us. A third matter I’d like to address is Gem support.

Russell Coker: memes that damage debian

The Debian project is afflicted with several damaging memes. One that is causing problems at the moment is the idea that life should be fair. Unfortunately life is inherently unfair, it's not fair that those of us who were born in first-world countries (the majority of Debian developers) have so many more opportunities than most people who are born in "developing" countries, and things just continue to be unfair as you go through life. Unfair things will happen to you, deal with it and do what is necessary to have a productive life!

When one developer has regular long-term disputes with many other developers the conclusion is that the one person who can't get along is at fault. We can debate about whether one or two significant disputes are a criteria for this or whether having a dozen developers disagreeing with them is the final point. But the fact is that if there is a large group of people who work together well and an individual who can't work with any of them then there is only one realistic option, the individual needs to go find some people that they can work with - they can resign or be expelled. The fact that something slightly unfair might have happened a year ago is no reason for pandering to an anti-social developer. The fact that expelling a developer for being anti-social is unfair to them is no reason for damaging the productivity of all Debian developers.

Another problemmatic meme is the idea that we have to tolerate everyone - even those who are intolerant (known as the Limp Liberal meme). When someone has no tolerance for others (EG being racist or practicing sexual discrimination) then they have no place in a community such as Debian. They need to be removed sooner rather than later. All Debian developers know the problems caused by deferring such expulsion.

The final damaging meme that I have observed is you can't force a volunteer to do any work. On it's own that statement is OK, but the interpretation commonly used in Debian is you can't take their job away from them either. The most common example of this is when a developer is not maintaining a package and someone else does an NMU (non-maintainer upload) to fix a bug, the developer then flames the person who did this (usually to fix a severe bug). It seems to be believed that a Debian developer owns their packages and has a right to prevent other people from working on them. This attitude also extends to all other aspects of Debian, there are many positions of responsibility in Debian that are not being adequately performed and for which volunteers are offering to help out but being refused.

The idea of the GPL is that when a program is not being developed adequately it can be taken over by another person. However when that program is in a Debian package the developer who owns it can refuse to allow this.

Evan Prodromou: 9 Niv se CCXV

My brother Nate and his girlfriend Kristen live in the Laurel Heights area of San Francisco, just north of Presidio Heights, across the street from Laurel Village on California Street. They invited us up for dinner at their house last night, and since my Mom and Dad hadn't seen their apartment yet, they decided to join us, too. Maj, Amita June and I went up early yesterday afternoon, right after naptime. (That's our main measure of time -- before naptime, after naptime, before bedtime, after the baby goes to sleep.) We initially planned to go downtown and do some post-Christmas shopping, but we hit gruesome traffic getting off North 280 into China Basin. Friday afternoon traffic in San Francisco is pretty crappy any day of the month, but yesterday was Critical Mass, which really tangles things up downtown. So we juked west and headed out to Ocean Beach instead. I parked at the end of Golden Gate Park by the giant windmills. We all walked out onto the beach -- Amita at 0.5 mph, of course, and rarely in the correct direction -- just at sunset, which was great. It was our second beach day in a row, but it was great being out there. The baby chased dogs and waves, and we got to watch the sun go down. There were kites everywhere -- I explained to Amita how people had to hold their strings so that they could keep flying. It's so counterintuitive. We dropped into the Beach Chalet on the Great Highway for a late afternoon snack. Amita June had her trademark grilled cheese sandwich, Maj and I split a plate of calamari. The chalet does its own beers, so Maj had a Christmas ale and I tried the more than decent stout. We got to Nate's place just after 6, and they ordered Indian food from Rotee in the Lower Haight. It was excellent -- we got some tandoori fish and about 12 different curries. Maj's brother Brian came too, and we stayed up pretty late talking. Maj and I stayed over at Nate and Kristen's last night, then shared coffees this morning from Peet's. There's a really nice Cuban place, Caf Lo Cubano right up the street, but we wanted bagels from Noah's, so it's just natural to get Peet's, too. We had a long ride home, though -- Maj and I are both feeling sick, and the baby's not too happy about long car rides anymore. But we got home for a good nap and a radio interview. tags:

Get Connected Radio I did an interview today on Get Connected Radio about Wikitravel. It was pretty fun -- the interviewers were pretty clued-in about wikis, so we got to talk a bit more about the interesting travel aspects. Also cool that they emphasized the "open source" aspect, which is something a lot of media don't cover. tags:

Erich Schubert: Freeze progress

... is pretty bad. So far, only four applications (i.e. much less than 1% of all packages) have been renamed to ice* (i.e. frozen!): Iceweasel, Icedove, Iceape and Icedax. Or did I miss something? P.S. All your freeze are belong to us. P.P.S. Stupid SUV drivers delaying our freeze. Your CO2 production causes the climate to change, which makes freezing much harder!

Randall Donald: Now with wfb!!

9746 packaages now come (just uploaded) with libnvidia-wfb flavouring for 8800 peeps.

30 December 2006

David Nusinow: Communities

I spent some time playing with haskell over the past month or so. One of the most incredible things about it is the wonderful community that has sprung up around the language. The haskell homepage is a treasure trove of information, excited users throw all sorts of new articles at reddit every day, and the #haskell channel is exactly what you want out of an irc channel. A nice bonus for Debian types is the incredibly close ties the haskell community has with our distro.

Comparing this to Debian is instructive. The haskell community seems to be having a ton of fun using their language. The sense in #debian, or from whatever Debian tutorials I read, is that people aren't using their system to have fun any more. The air of joy and occasional whimsy that traces its way through #haskell (and also very strongly through the ruby community) seems to be somewhat surpressed in Debian, as though we're so big and cool and technically competent that we don't have time for frivolity. It's hard to have fun and create a warm and inviting community with this kind of attitude. Turf wars, protocol, and politics only compound the problem.

Doing something fun for its own sake should be a part of the Debian experience the same way that it's inherently part of the free software experience. It's way too easy to lose that in the mountain of packages, emails, and bug reports. Using Debian makes me happy, and I want to try and let that spirit out to play a little more.

Tollef Fog Heen: A moderately complicated OpenWRT setup

At home, I have had a setup with a wireless router for quite a while. It's more or less a stock OpenWRT setup, but I have split the joined all the wired ports into one virtual interface (actually, I think they're just on one VLAN) and split off the wireless. The wireless is open to the world, but I have a fair amount of packet filters there so it doesn't get too annoying. Some people have no shame and run bittorrent and other file sharing utilities on other people's open wireless. Anyway, my setup is no longer so simple. I bought a WRT54GL to provide better reception in other parts of the flat and wanted to join those two. After a little bit of reading, I found what I wanted: WDS. Due to a previous misconfiguration of the WRT54GS, the WDS connection was joined onto the br0/LAN segment and not the wireless segment. That was easily enough fixed, but it's always a bit scary to change network settings on headless devices. (I did manage to lock myself out, but I could ssh through in from the wireless network, so I just used the WRT54GL to bounce through.) Once that bit was up, I could set up WDS, I did as the documentation told me and did it with lazywds (anyone can do WDS with you) enabled. It worked, so I turned it off and rebooted both routers (again..), and it still worked. Yay!

Russell Coker: more about vista security

While reading the discussion of Vista security on Bruce Schneier's blog it occurred to me that comparing the issues of DRM that face MS with the issues faced by SE Linux developers provides some benefits.

SE Linux is designed to enable the owner of a computer to effectively enforce security policies to protect their system integrity and the confidentiality of their data. Some of the SE Linux users (military users) use all the available features, but most people only use the targeted policy which provides a sub-set of the system integrity and data confidentiality protections that are available to give a greater ease of use.

Fedora and Red Hat Enterprise Linux ship with the SE Linux targeted policy enabled by default. This policy is not something that most users notice. The main program that is commonly used which might have an issue with the default SE Linux policy is Apache. Fedora and RHEL systems that do not run Apache (which is most of them) can run SE Linux with almost no costs.
setsebool -P httpd_disable_trans 1
/etc/init.d/httpd restart
It seems clear to me that there is no good reason for disabling SE Linux by default. There are reasons for running a particular daemon in the unconfined_t domain via the FOO_disable_trans boolean. EG to run Apache without restrictions you would type the above commands.

In spite of the SE Linux targeted policy being so easy to use, the fact that it prevents certain daemon compromises from allowing immediate control of the system, and also prevents some kernel exploits from working, there are still some people who turn it off when installing Fedora and RHEL systems and advise others to do so.

Given this great fear of some people to use a technology that is specifically designed for their own benefit I find it difficult to imagine that any users will be inclined to accept the MS DRM technology that is specifically designed to go against their interests.

ESR claims that the 64bit transition is the critical period for Linux to move on the desktop. While he makes many interesting observations I don't find his argument convincing. Firstly current P4 CPUs with PAE can handle significantly more than 4G of RAM (64G is possible now). Secondly it's quite possible to run a 64bit kernel with 32bit applications, this means that you can use a 64bit kernel to access >64G of RAM with each 32bit application getting direct access to something slightly less than 4G of virtual memory. As ESR's point seems based on total system memory the 4G per application doesn't seem to be an issue. As an aside the only applications I've used which could benefit from >4G are database servers (in the broadest interpretation - consider an LDAP server as a database) and JVM environments. Again it would not be difficult to ship an OS with mostly 32bit code that has a 64bit kernel, JVM, and database servers.

I hope that Vista will be a good opportunity for mass transition to Linux. Vista offers little that users desire, many things that will hurt them, and is expensive too!

With Vista you pay more for the OS and more for the hardware (Vista has the usual excessive Windows hardware requirements plus the extra hardware for TPM encryption) without providing anything substantial in return.

What I want to see next is support for Security Enhanced X to protect desktop environments against hostile X clients. This will make a significant difference to the security of Linux desktop environments and provide another significant benefit for choosing Linux over Windows. While MS is spending their effort in making their OS act against the best interests of the users we will keep making Linux enforce the access controls that users need to protect their systems. Hopefully Linux users will choose to use SE-X, but if they don't they are given the freedom to make that choice - unlike the poor sods who use Windows.

Jordi Mallach: Tunisia

Yesterday Bel n and I got confirmation from the travel agency: it's now official! We'll be going to Barcelona (third time this month for me) tomorrow, spend New Year's Eve with my cousin and early during the morning of January 1st we'll be taking a flight to Tunisia, to end up in Hammamet for a one week long trip around the country. Before this very late confirmation, the agency was only assuring one of us could come back; the other return ticket was missing, and I wasn't planning on staying there alone. :) This is pretty exciting because I've never been anywhere in Africa, despite it's very close from where I live, so I'm really looking forward to discovering the cultures of the Islam in Northern Africa. We plan going to way too many places, but I think I'll most enjoy the different Roman buildings in a few of the important cities, specially in Dougga. If you have any suggestions of things I can't miss in Tunisia, feel free to comment here. Have in mind I'll probably be moving around in louages (shared taxis) so maybe going to places too far away from Hammamet isn't that easy -yeah, I'm thinking about Matmata and the Skywalker's village ;)- and we don't want to spend lots of money. Hopefully things will be normal at El Prat airport tomorrow, after the distressing news coming from Madrid this morning... More when I come back on January 8th!

Wouter Verhelst: f-spot vs digiKam

Since I have been having a digital camera since a few weeks now, I've had a need for an application to manage my pictures. The two applications that people have pointed me to are f-spot and digiKam, which also seem to be the most popular applications in this category for Linux. Since I use neither KDE nor GNOME as my user interface, it doesn't matter much to me which I install; so I've tried them both. Their feature set is quite different; unfortunately, though, they both have some features which the other doesn't, which makes choosing for one or the other rather hard. Since their on-disk format is rather different, it's impossible to use them both at the same time—at least not if I don't want to enter commentary and tags each and every time; so I'll have to choose one or the other based on their features. Since that requires me to actually compare them, I thought I might as well make a blog post out of that. Note, though, that this comparison is in no way intended to be complete; it only compares those features which I really care about. Features digiKam F-spot My opinion After having used f-spot for a few weeks before I tried digiKam, I have to be honest and say that I don't like the concept of albums. They do not add value; everything they allow you to express can equally well be expressed with tags. Additionally, one can categorize a picture in only one album, whereas it's possible to categorize pictures in as many tags as you would want. Just creating one album which contains all my pictures, with tagging used for categorizing, doesn't help either; that way, digiKam would store all my pictures in a single flat directory, which would become problematic when the number in the picture filenames wraps around. I do love the scoring thing in digiKam. A favourites tag just doesn't cut it; and creating five tags for scoring would make things like find all pictures that have a score of three or above rather cumbersome, and sort by score outright impossible. However, the fact that it's not possible to filter by score makes it all rather useless. The export to gallery function in digiKam is horrible. I have to select my pictures blindly; none of the metadata which I tack on them can be used to help select which pictures I want. Workaround: use whatever filtering is available to select the right pictures and add them to a temporary album from which I then upload all pictures, but that's silly (and requires disk space for no good reason). Additionally, there seems to be a bug in the interface, which means that I have to babysit an upload (with no workaround). And I can't even view my pictures to spend the time waiting. Bah. F-spot isn't without problems of its own. Due to a bug in mono, it crashes rather often on my PowerPC laptop. When that happens, it can't be restarted until the X server is restarted. Workaround: use Xnest, but that makes it impossible to view pictures in full-screen mode. Also, since f-spot is a GNOME application, its options dialog is as helpful as a pair of soccer shoes when you're out swimming. No surprises there. Conclusion Which one do I prefer? I'm not sure. The digiKam upload interface is positively annoying, especially the bug which requires me to click continue after every picture. For that alone, I might ditch it. On the other hand, it has a slew of interesting features (the scoring, to name one) that f-spot lacks, and that pull me more towards digiKam. I guess I'll have to give it a few days of thought. But hey, at least I know where I stand now.

Stefano Zacchiroli: trac.cs.unibo.it

Experiences with a Trac Server In the last few days after Xmas I set up http://trac.cs.unibo.it, a server for my CS department which will host a bunch of Trac instances, initially for academic projects only then it will be opened to student projects as well. The server set-up has been "powered-by" the following technologies:
  1. Debian Etch
  2. Apache 2.2 with FastCGI, SuExec, and WebDAV over TLS (for accessing SVN repositories without forcibly passing through Trac)
  3. Trac instances backed by Sqlite databases and Subversion repositories
  4. Some bits of Genshi templating for generating the projects index
  5. Some shell scripts for automating creation and removal of projects
I'm quite happy with the result. From the overall experience I drew some observations though: Happy new year birthday trac.cs.unibo.it.

Ian Murdock: What s in a name? Quite a bit

Geir Magnusson: “What exactly is the result when the distros compile and package the OpenJDK source? I’ll argue it’s by definition not “JavaTM” (or “Java compatible”) because it hasn’t passed the TCK [the Technology Compatibility Kit, the Java compatibility test suite from Sun].” Very good question. I agree with Geir—it shouldn’t be called Java unless it has passed the test suite. If it’s cost prohibitive to run the test suite against third party versions, that should be remedied now that the reference implementation is open source. (Via James Governor.)

David Welton: Stuff To Do

Regarding my previous posting, the first thing that I wanted to release is called "Stuff To Do", and is a simple, elegant priority queue for getting things done. It lets you reprioritize, track time spent on tasks, generate reports on time spent, and most importantly, share with other users. You can create groups of people who can view one another's tasks, and give tasks to other users, all via a very intuitive interface (javascript is, however, required). It's all meant to stay out of your way as much as possible, even the time tracking requires only that you visit the browser window every so often to let it know you're there, rather than fiddling with (and sooner or later forgetting about) start and stop buttons. Perhaps it's not accurate down to the second, but the idea is to give you a general idea of what you've been up to, rather than something you have to slavishly click on all the time. The group interface is also meant to be easy to use to get a quick idea of what other people are working on, or share tasks with other people. For instance, if you're a project manager, you could create a bunch of tasks, and then just drag and drop them to other people in the system. You can't change other people's priorities (yet), because I think it's better if you simply ask them yourself - technology isn't a substitute for communication! While I work on the paypal interface (I looked into Google Checkout, but it's still got some limitations), I'm going to let people sign up for the group-enabled version with six months for free. It won't cost too much per user when I roll it out in any case, probably somewhere south of $20. The basic version is likely to remain free as long as I can cover hosting costs. I've been using it myself at work and home for the past month or so, along with a few of my colleagues, and it seems to fill a nice niche in between more heavyweight issue tracking tools like JIRA, and the index cards/bulletin board we'd been using. Check it out - I hope you like it! In any case, let me know what you think.

Benjamin Mako Hill: Digital Disobedience Videos

The Digital Disobedience event that I helped organize on December 1st went (IMHO) very well. If you missed it, you can check out this video (MP4) that the Berkman Center has recently posted. I was particularly impressed with Stanford's Fred Turner whose work I was not familiar with before. I haven't had a chance to check out From Counterculture to Cyberculture but I am looking forward to doing so soon.

29 December 2006

Randall Donald: Ack! We need 9631!


Ok. Since I have uploaded 1.0.9746 I need to make a packaging change regarding the 1.0.9631 drivers which are now another legacy version, but not as legacy as 7184 if that makes sense. 7184 might become something like -ancient if it still be kept around.

If you need 1.0.9631 you can find it here http://snapshot.debian.net/archive/2006/12/08/debian/pool/non-free/n/nvidia-graphics-drivers/
for now.

Martin-Éric Racine: RFA: utf8-migration-tool -- Debian UTF-8 migration wizard

From the Debian Bug #374997 department:
* Package name    : utf8-migration-tool
  Version         : 0.4
  Upstream Authors: Tollef Fog Heen, Martin- ric Racine
* URL             : http://q-funk.iki.fi/debian/pool/u/utf8-migration-tool/
* License         : GPL
  Programming Lang: Python, GTK2+
  Description     : Debian UTF-8 migration wizard
This wizard upgrades legacy system locales to their UTF-8 
equivalent. It also informs users whenever files in their 
home directory still utilize legacy encodings.
This started as an Ubuntu tool to enable easy migration to UTF-8 for both locale settings and user file encodings. Tollef says that since Ubuntu has been UTF-8 by default for a few releases already, they are not likely to further develop it and invited me to take over development, so I have. I have found this tool very useful to help me locate remaining files in my home directory that are still in a legacy encoding and to check system files for UTF-8 locales utilization. Given how Etch is going to be the first Debian release with UTF-8 locales by default, I figure that it could be a useful migration tool for others as well.
Since I'm currently paring down my involvement in Free Software, I never got around fixing the GTK annoyance reported by Denis Barbier in response to the ITP and thus never uploaded the package to the NEW queue so, if anybody is interested in picking up this package's maintenance, please do so by responding to the above bug.

Next.

Previous.