Note 1: .AppleDB is NOT a cache, but instead it's the place where a consistent filename/dirname <-> CNID mapping is stored. Delete it, every file/dir will be assigned a new and different CNID, such that a) Aliases will loose their ability to maintain reference to the original in case the original is moved and b) linked documents (eg. InDesign/Quark) loose the same coupling leaving only the path relationship to resolve the link.
Note 2: The internal metadata format is a term that only makes sense in relation to the data in the .AppleDouble directories, and this too has NOT changed. What probably has changed is that Netatalk in lucid links against a newer version of BerkeleyDB then the one in Karmic. Unfortunately solving this upgrade problem is difficult with Netatalk 2.0.x. Some instructions can be found in the Netatalk Wiki: <https://sourceforge.net/apps/mediawiki/netatalk/index.php?title=Upgrading_BerkeleyDB> Starting with the upcoming version 2.1 Netatalk will be able to upgrade its databases without manual intervention. HTH, Frank Netatalk Developer, Consulting and Services <http://www.netafp.com/> -- Upgrade from Karmic to Lucid leaves broken netatalk caches https://bugs.launchpad.net/bugs/555917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
