Not only fixes ipconfig regressions due to fixes in 1.5.16, but ipconfig should no longer discard useful packages. We also fixed a long standing klibc sparc specific socket bug (#444087): sparc lists socket system calls, but does not provide all of them natively. So one is better off on sparc to use sys_socketcall.
Thanks to Jan Hauke Rahm the packaging switched to modern Source Format 3.0 (quilt) with debhelper 7 usage reducing cdbs overhead on build. This is a big switch and makes me very happy.
New addition include a $(make help) target in Makefile to ease klibc build. A small losetup got added to klibc-utils.
i386 and sparc build fine against current linux-libc-dev: klibc-1.5.17 released
Yesterday began the central america and caribbean MiniDebconf at Panama. Over 50 people from Mexico, Belice, Nicaragua, Guatemala, Costa Rica, Salvador, Colombia and Venezuela, among others, are here to share experiences around Free Software and Debian contributions. All this is possible to several sponsors from Panama and SPI, and the hard work from many people, specially Anto Recio, Mauro Rosero, Carolina Flores, Gunnar Wolf and the local team.
Open Game Art is a newly started site for
exchanging free Artwork. While one can easily get the impression that
there are loads of such sites around, Open Game Art is one of the very
few that actually is done right.
As a Member of the
Debian Games Team and the
Unknown Horizons Project I was way
too often in the need for good artwork searching around the web. I've also already reported once about my trouble.
There are quite some sites like
Free Sounds around offering free artwork
-- but only free as in beer as the saying goes, not as in speech which
of course is really unhelpfull for FOSS projects. And even most of the
sites that have free content often only tell you the license on some
special pice of arts details page.
Open Game Art is quite different from
that. All the license you may choose as a contributor are free (both
in Debian and in FSF terms) and the license is available through a
search filter so you can find stuff that fits you project's licensing
policy. This list, and that's another thing I really like about that
site, is the availability of choice among common licenses including,
next to the copyleft class of licenses a fair share of more liberal
licenses like my personal favourite, the
zlib License.
And because such a site is just as good as it's amount and quality of
data I've started sharing some
recordings. I'm currently really
new to audio recording so I guess it'll take some time for me to
become really good. I'm considering putting some of my experiences and
stuff I've learned here.
On Wednesday, I went to a meeting of the Business Initiative for North Somerset for Cooperatives-SW (our regional cooperative cooperative). It was the first time anyone from the cooperative and mutual sector was present.

Conference
Bank of England
The first speaker was Geoff Harding from the Bank of England, who talked through topics in their agents summary and related news.
One interesting graph showed a steep rise in the percentage of household income being saved. Answers to questions suggested that more of that goes to mutuals and building societies, but they find it difficult to be competitive while the banks are keen to increase their balances.
There was mention of employment hoarding businesses short-time working, redeploying or shutting down temporarily to keep trained workers under contract, rather than make them redundant and rehire later.
People from both the Federation of Small Businesses and the Hoteliers Association made strong comments about the banks claiming to government that they are willing to lend, but still offering deeply unattractive depth-of-recession rates and terms. If the regional agents get details of such cases, they pass them to the central bank.
South West Regional Development Agency
The second main speaker was Ann O Driscoll, who covers business development for the West of England (what many people call CUBA Councils that Used to Be Avon). She introduced their four strategic priorities:-
Julien's blog post
reminded me that I needed to announce that I'm in the process of
transitioning to a new key myself.
I've been meaning to do something about the whole weak 1024-bit DSA key
thing ever since everyone started freaking out about them, but I liked how
well connected my old key was. Oh well. Time to suck it up and start over.
Here's my transition
document, now that I've figured out how sign
a file with multiple keys
Finally, after almost 6 months of planing, this event is coming and will be start tomorrow, this is really great, There was a first attempt, and an idea to do a local(central-america based) Debian gathering on 2007 IIRC, now it will happen
Some people want Debian 6.0 (codename "squeeze") to be released
sometime this year. Personally I think there is some kitsch
value in releasing it during DebCamp or DebConf, and there is
something to be said for doing it just beforehand so that
everyone can break unstable into insanity while rolling around
on the quad under the hot August sun. Some people want it to
happen sooner, possibly as soon as possible. Irrespective of
your preferences, or if you care at all, we will repeat the
time-honored mantra: it will be released when it's ready.
Readiness is somewhat of a subjective measure, but we typically
do not consider a potential release ready when the
RC bug count is high.
There are a lot of RC bugs right now. Typically these are
fixed at some point by their maintainers. There are also
some self-motivated individuals who enjoy fixing these bugs
themselves, and this practice predates the
RCBW initiative,
though perhaps not to the same level of combined intensity and
endurance. Then there are bug-squashing parties, or BSPs.
A BSP can be held virtually which means that a bunch of people
get together online and say that they are having a party, or it
can be at a designated physical space. I attended one of the
latter type not too long ago.
This BSP was targeted specifically to newbies or people who
might feel that they are unqualified to help squash bugs, but
wished to learn how to contribute. Some group and one-on-one
mentoring occurred, in areas of how packages are put together,
how to patch things, how to submit patches to the BTS, how to
reproduce bugs, and other more problem-specific topics.
I really don't know how successful this endeavor was since
getting metrics on the effectiveness of teaching has been a
historically difficult problem. On the other hand, we did
spend a fair amount of time actually squashing bugs, which
is a bit easier to assess. One problem we had was that
some people liked to be loud and distracting and demand
unreasonable amounts of attention for topics that had nothing
to do with bugs, Debian, or free software, but we made
progress regardless.
Marc Brockschmidt thinks we need more BSPs and more focus
on bug triage. Bug triage can be very demotivating and
many people dislike doing it. BSPs seem to have powers of
motivation through group camaraderie or friendly competition,
so I would agree that it's worth experimenting with.
We had a visitor on #ironruby today asking for help getting IR running on his mac. I gave him the following directions, and they seemed to work aside from one glitch. I tested them on my wife s mac, and it worked for me, too.
Install Mono
You can grab the Mono .dmg from go-mono.com. This will install the framework and put the required programs (mono, xbuild) in your PATH.
Fetch the IronRuby source
Since Jim Deville likes macs, I m sure more recent versions will work, but this is the one we ve recently packaged up for Debian and tested on Ubuntu. If you want to be certain that the IronRuby code you write on Debian works on OS X, then you should probably build from the same version of the source. You should probably also install version 2.4.3 of Mono, but that may be more effort than it s worth ;)
http://github.com/mletterle/ironruby/tarball/20090805+git.e6b28d27
Unpack the tarball
Open up a terminal and unpack the thing you just downloaded:$ mkdir ~/src/ $ cd ~/src/ $ tar xfz ~/Desktop/mletterle-ironruby-e6b28d2.tar.gz $ cd mletterle-ironruby-e6b28d2/Build IronRuby At this point, you should be able to build the IronRuby assemblies using xbuild. I don t recommend using rake, as it has some dependencies, and I m not a fan of dependencies.
$ xbuild /p:TreatWarningsAsErrors=false Merlin/Main/Languages/Ruby/Ruby.sln <snip/> Build succeeded. 2817 Warning(s) 0 Error(s) Time Elapsed 00:00:28.8378230Run the IronRuby interactive interpreter Our guest mentioned that he was using a terminal with a white background. Do note that the font color of the interactive interpreter (aka Read-Eval-Print Loop or REPL) is white, so if you re using a white background, you might want to change it. IIRC, there is a way to change the font color using a configuration setting. Figuring it out is left as an exercise for the reader.
$ mono Merlin/Main/Bin/Debug/ir.exe IronRuby 0.9.0.0 on 2.6.3 (tarball Wed Mar 10 18:18:12 MST 2010) Copyright (c) Microsoft Corporation. All rights reserved. >>> 1+2 => 3 >>> exit()Extra credit: IronPython The tarball you downloaded also included the source to IronPython. The procedure to build/run IronPython is pretty similar to IronRuby. Build IronPython Unlike IronRuby s .sln, this version of IronPython s .sln does not have a default configuration parameter, so we need to specify it with the /p:Configuration=Debug argument.
$ xbuild /p:TreatWarningsAsErrors=false /p:Configuration=Debug Merlin/Main/Languages/IronPython/IronPython.sln <snip/> 69 Warning(s) 0 Error(s) Time Elapsed 00:00:38.8057450Run the IronPython interactive interpreter IronPython has a REPL interface like IronRuby s. Or is it the other way around? Anyway, here s an example.
$ mono .//Merlin/Main/Bin/Debug/ipy.exe IronPython 2.6 Beta 2 DEBUG (2.6.0.20) on .NET 2.0.50727.1433 Type "help", "copyright", "credits" or "license" for more information. >>> 1+2 3 >>> ^D
Crush 2.0 was abandoned last year when the freeze for Debian Squeeze was still scheduled to start at the end of 2009. Even with the expected delays in the timetable for the Debian release, there never was going to be enough time to get Crush 2.0 released with the resources available. Subsequent Crush releases have always been planned, only the release of Crush 2.0 alongside Debian 6.0 (Squeeze) was abandoned.
Well, it's been a month since the initial
demolition started
It's nearly finished.
We had a slight bit of scope creep in that we decided to redo the floor now
as well. This was brought on by the fact that the new cabinets didn't quite
meet up with the footprint of the old ones, on one side, leaving maybe a 5
centimetre gap between the new cabinets and the floor.
I wasn't a fan of having to haul the fridge and stove back into the living
room again at some point in the future (the fridge is too big for the
doorway and needs to have its doors removed) so it seemed like the best
thing was to do it while everything else was being done.
Fortunately, it hasn't blown out the overall time of the work, as we're
still waiting for the counter tops to be cut or manufactured or something.
The ETA for them to be installed is Friday or Monday.
So in the meantime we got just the kitchen floor tiled.
The plan is to replace all of the floating wooden floor with tiles, but just
not right now. To do the rest would involve faffing around with the
downstairs bathroom, and pulling out the washer and dryer, as well as the
hot water heater. Doing that now, on top of having all of the kitchen stuff
in the living room just gives me the heebie jeebies, so the compromise is to
keep the existing flooring for the rest of downstairs, and just buy enough
tiles to cover it later. Maybe at Christmas time, if we go back to
Australia, we'll get it done then while we're not around to be disrupted.
When they ripped up the floor in the kitchen, some huge cracks in the slab
were immediately apparent, so they had to put down some DITRA as a foundation to
prevent the tiles cracking as a result of the slab expanding and
contracting.
The tiling should be finished by tomorrow I hope, and then we have to let
the grout cure for 72 hours before we seal it.
The one small delay we've had was due to a miscommunication with the kitchen
company: we'd never ordered any handles for the cabinets and drawers, so
they only got ordered after the cabinet installation was completed. Had we
had them on hand, we could have started occupying the cabinets and drawers
already, which would have reduced the chaos in the living room a bit. Oh
well.
Blow-by-blow photos of the work so far (I'm lacking photos of the cabinets
with the doors on) are here.
We re coming close to GNOME 2.30 release date, and we are getting ready to branch a stable release off of WebKit s svn trunk in preparation for that. The idea of the stable branch is to try to maintain, and improve stability, with no additional features going in. Speaking of features, though, if you ve been paying attention you will have noticed WebKitGTK+ has come a long way, now.
We came from not having basic features such as download support or openning links in new tabs, a more-or-less working HTML5 media implementation, and very few or missing in action developers to a thriving project, that gets more, and more attention, and contributors every day, with advanced features available, and rocking HTML5 media support that leaves little to be desired. It s been just over one year since we started rolling mostly bi-weekly releases, each adding more awesome features.
There are still many issues, and we are not always equipped as a team to handle all the specifics of the engine ourselves, but I am really happy with the progress we ve made, and really thankful for the support my employer Collabora has given all the way for this to happen, including the early work on plugins, and many other things before my time as a contributor. When I switched to using Epiphany with the WebKit backend as my default browser back in January 2009, that meant having to deal with a whole lot of misbehaviour, and work-around a lot of painful brokeness. These days I enjoy a snappy, functional browser that makes me happy.
If you haven t done so yet, go download, and test the newest Epiphany, with the latest WebKitGTK+, and help us make the GNOME 2.30 s web browser rock even more!
Several months ago, around the Central American Free Software Encounter (ECSL) in Estel , Nicaragua, I started stirring the waters The Central American regions have vibrant, beautiful Free Software communities, but have mostly (with some very notable examples, of course) shied away from being active participants in major development projects. What was I to do about it? Of course, try to get them to become Debian contributors!
During the following weeks, I talked about it with several friends from the region, and the result was an announcement and lots of arguments that followed it. Panam was decided as the host country, and many people have put a lot of work into making the MiniDebConf happen.
Mauro Rosero and Anto Recio came up with what appears to be a wonderful local venue and a set of sponsored amenities, and the Debian project is sponsoring what is needed in terms of transportation for people from the whole region (spanning from Mexico to Ecuador and Venezuela IIRC).
I am very sorry, however, that I cannot attend this meeting. This very same weekend, I will fly three hours, but in the opposite direction: I will go to Tijuana, where fate decided I will present my first round of CENEVAL equivalence exams (Acuerdo 286 Licenciatura). I expect that to be the topic of another post, to come soon.
So, while my friends will be having a good time and talking about Debian and group work, I will sit through three periods of four hours, answering an exam for the first time in a very long time. Fun, hah? Anyway, I will meet Guillermo Amaral (thanks for hosting me! ;-) ), which ensures I will not miss all of the fun ;-)
Every once in a while someone asks how they can use the Debian installer
to access their system on disk to run commands, for example to write
the kernel and ramdisk to flash again. This is particularly useful on
headless NAS devices. So here's how to do it:
mkdir -p /target mount /dev/sda2 /target mount /dev/sda1 /target/boot mount --bind /dev /target/dev mount -t proc none /target/proc mount -t sysfs none /target/sys chroot /target /bin/sh # the prompt will change # make modifications to the system and regenerate the initramfs update-initramfs -u exit # the prompt will change again as you're leaving the chroot umount /target/sys umount /target/proc umount /target/dev umount /target/boot umount /target reboot
Here s the first thing you should know: The general had nothing to do with his chicken. You can banish any stories of him stir-frying over the flames of the cities he burned, or heartbreaking tales of a last supper, prepared with blind courage, under attack from overwhelming hordes. Unlike the amoeba-like mythologies that follow so many traditional dishes, the story of General Tso s chicken is compellingly simple. One man, Peng Chang-kuei very old but still alive invented it. But what s it ? Because while chef Peng is universally credited with inventing a dish called General Tso s chicken, he probably wouldn t recognize the crisp, sweet, red nuggets you get with pork fried rice for $4.95 with a choice of soda or soup. All that happened under his nose. It all got away from himNo related posts.
Here s the first thing you should know: The general had nothing to do with his chicken. You can banish any stories of him stir-frying over the flames of the cities he burned, or heartbreaking tales of a last supper, prepared with blind courage, under attack from overwhelming hordes. Unlike the amoeba-like mythologies that follow so many traditional dishes, the story of General Tso s chicken is compellingly simple. One man, Peng Chang-kuei very old but still alive invented it. But what s it ? Because while chef Peng is universally credited with inventing a dish called General Tso s chicken, he probably wouldn t recognize the crisp, sweet, red nuggets you get with pork fried rice for $4.95 with a choice of soda or soup. All that happened under his nose. It all got away from himNo related posts.
Next.