Binary package hint: netatalk
The upgrade from Karmic to Lucid leaves behind the .AppleDB metadata store in the shares, used by afpd for metadata. The bdb version for this metadata has changed again, and the new version of netatalk can not read the old data, and will return error messages on attempts to access shares with old metadata caches.
The work-around is to delete these caches manually.
But it would be preferable for the install package to either
* Scan for shares, and upgrade the metadata stores,
* Scan for shares, and delete the metadata stores.
* Notify the user of the need to upgrade/manually delete metadata stores.
This is an old bug (http://lists.apple.com/archives/macosx-interop/2007/Jul/msg00002.html) that keeps coming up every time netatalk is compiled against a different version of bdb.
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:/
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://