It occurred to me the other day that while it's very obvious what one of the major improvements that came with the release of 1.0 to those of us actively participating and following bazaar's development (a new storage format with performance as a priority), so obvious, it might not be for the average user.
This new storage format also brought many long awaited bug fixes, so I think it was not stressed enough how important it is to upgrade any branches you created (or started using) with any version before 1.0.
First of all, make sure you're running the latest bzr version (head to http://bazaar-vcs.org/Download, Ubuntu users can download the very latest from PPA)
To find out what storage format you are currently using, just go the the branch's folder and type in:
beuno@beuno-laptop:~/test_branch$ bzr info -v | grep 'repository'
That should give you an output similar to this:
beuno@beuno-laptop:~/test_branch$ repository: Knit repository format 1
(Warning: if you're using bzr-svn, you might see different formats, this probably doesn't apply)
If it's reporting Knit repository format (or anything different than Packs containing knits...) then you're still using the old storage format. How to upgrade is documented in the bzr documentation, including preparation and upgrading, but for you lazy fellows, here's how it goes:
Make sure you backup the whole directory first, the run:
beuno@beuno-laptop:~/test_branch$ bzr upgrade
(if you're using shared repositories, make sure you specify where the root repository is with bzr upgrade root-repo-dir)
Once that's done, you should reconcile:
beuno@beuno-laptop:~/test_branch$ bzr reconcile
If the operation doesn't report any problems, run a quick bzr info to make sure the repository has been updated correctly and you should be able to delete the backup of the old storage format dir renamed to .bzr.backup/ (WARNING: make sure everything is working correctly before you do this).
If you have branches in Launchpad, you have to do the upgrades via SFTP instead of bzr+ssh (and I do recommend having all branches with the same storage format) like so:
beuno@beuno-laptop:~/test_branch$ bzr upgrade sftp://<username>@bazaar.launchpad.net/~username/project/branchname
And then of course:
beuno@beuno-laptop:~/test_branch$ bzr reconcile sftp://<username>@bazaar.launchpad.net/~username/project/branchname
If you run into any problems, feel free to drop by #bzr in freenode.
As the advertised on their homepage, Nokia seems to have bought Trolltech, in an attempt to "to accelerate software strategy".
They have a FAQ placed on their webpage trying to address the common concerns of customers and the community in general.
Seems like it's "Buy successful Open Source companies" season.
Congratulations to the Trolltech guys.
After my previous post on an Ubuntu ad in Slashdot (and I've since seen them in google adwords too), I actually spotted it again and clicked it to satisfy my curiosity. I got sent to a Canonical page, which seemed normal enough.
One small bit did catch my eye, and after all the back and forth about Ubuntu not recognizing enough it is based on Debian, I thought it would be nice to air it out in public:

(no, I don't think this settles anything, just nice, ain't it?)
I've always thought that the Debian Release Cycle was a mystery to me because I involved enough in it. After poking around a bit more I realized that it has much more randomness to it then what I expected.
While that doesn't have to be a bad thing, it does make it a bit harder for regular users to get excited about it (and consequently, more involved in it).
So that led me to start a release cycle page, based on the email announcement back when Etch was released: http://debian-community.org/LennyReleaseSchedule/
Now that the basics are layed down, I would like to add as much interesting information as possible to it, ranging from what versions of the different desktops are going to be added (gnome, kde, xfce, etc), what has been accomplished and what not, to major kernel improvements.
If can think of anything to add, please, feel encouraged to do so directly on the wiki, and if you can think of anything else that might make this release cycle more interesting, comments or direct email to me is the a great way to keep this moving forward.
After updating the kernel today to 2.6.22-2, everything but my wireless card seems to work! (sound didn't work properly before)
It turns out I need some proprietary firmware to get it running in Lenny (aka Testing), so here's a quick step by step:
- Fire up a terminal
- Go into superuser mode: su -
- Then: gedit /etc/apt/sources.list (or "kate /etc/apt/sources.list" if you're under KDE)
- There you should add the following line at the end: deb http://ftp.debian.org/debian/ lenny non-free contrib
- Save, then run: aptitude update
- Then we need to install the firmware and the module: aptitude install firmware-ipw3945 ipw3945d ipw3945-modules-`uname -r`
- You should have wireless now
You don't?
Take a look in: http://forums.debian.net/
HowToForge.com has a great step-by-step on how to install Debian Etch from Windows with the "Debian-Installer Loader".
Seems like a good place to point people wanting to give Debian a try, so this one is going to my bookmarks.
It finally seems we have a working Debian Community planet, so thanks to Holger for putting in all that work!