Netatalk 2.0.3-2

I just released Netatalk 2.0.3-2. This version solved the conflict with yudit by renaming /usr/bin/uniconv to /usr/sbin/netatalk-uniconv. As this is a tool that is only required very occasionally (i.e. when updating a volume from one character set to unicode, which hopefully you will only have to do once per volume), this change should be fairly unobstrusive.

Resolving the conflict with bigloo is more bothersome. Bigloo also contains a binary called afile, just like Netatalk. But since this is a tool that is possibly used regularily by some users and may even be used in scripts, I fear that simply renaming it may break things. I think I will just try to rename afile (and a few other similar commands) to apple_file, add a note to NEWS.Debian, and upload this to unstable. If too many users complain, I will probably use a transitional strategy: Rename the tools, add the note to README.Debian, but leave symlinks hanging around until after the release with etch. This would mean that the conflict with bigloo can’t be resolved until then.

Other opinions or suggestions on that matter are welcome.

New Netatalk Packages

Yesterday saw a new Netatalk package (2.0.2-2), since I forgot to include heimdal-dev in the build dependencies. Today another fix is needed (2.0.2-3), since it doesn’t build on amd64. I don’t expect this to be the last build failure. Let’s wait and see …

Of course I would prefer to check in the build fixes into upstream CVS, but due to my current problems with Sourceforge CVS I can’t.

Sourceforge CVS Broken?

Is it just me or is the CVS on Sourceforge really broken? When I tried to update, I got the error message that the host key had changed. So I deleted all known host keys for Sourceforge sites and tried again. After I accepted the new host key, I got the following error message:

Cannot access /cvsroot/netatalk/CVSROOT
No such file or directory

Trying it again, I instead got the well-known “host key changed” message. Whenever I try I get one of these two error messages. I know that I had similar problems two days ago, but after about five tries it worked at least a bit. This really sucks, Sourceforge!