``` [root@ipfire ~] # /etc/rc.d/init.d/netatalk start Starting Netatalk AFP File Server... /usr/sbin/netatalk: error while loading shared libraries: liblber-2.4.so.2: cannot open shared object file: No such file or directory [ FAIL ] [root@ipfire ~] # ``` I removed and then reinstalled netatalk but it did not correct the shared libraries: liblber-2.4.so.2 error. https://community.ipfire.org/t/core-168-netatalk-error-after-upgrade/8094/2 this may be similar to: https://community.ipfire.org/t/update-to-core-168-and-samba-not-working/8057/2?u=jon
these are the only liblber files I could find ``` [root@ipfire ~] # find / -iname "liblber*" /usr/lib/liblber.so.2 /usr/lib/liblber.so.2.0.200 [root@ipfire ~] # ```
It looks like liblber-2.4.so.2 was removed in the core 168 update. https://github.com/ipfire/ipfire-2.x/blob/master/config/rootfiles/core/168/update.sh#L41-L66
liblber-2.4.so.2 was removed in CU168 from the update of openldap. The liblber libs in openldap were changed from liblber-2.4.so.2 to liblber.so.2 and liblber-2.4.so.2.10.12 to liblber.so.2.0.200 It looks like netatalk has a dependency on openldap's liblber library and this was missed when openldap was updated. netatalk should have been shipped with CU168 but it wasn't. I will do a patch for netatalk that upgrades the PAK_VER so that it will be shipped with CU169
(In reply to Adolf Belka from comment #3) > I will do a patch for netatalk that upgrades the PAK_VER so that it will be > shipped with CU169 Yes, that is the solution. In the meantime, uninstalling and reinstalling the package might fix the problem.
(In reply to Michael Tremer from comment #4) > In the meantime, uninstalling and reinstalling the package might fix the > problem. I tried that but it did not help. Same error as in the 1st post.
Patch to ship netatalk with CU 169 submitted to list and patchwork https://patchwork.ipfire.org/project/ipfire/patch/20220616211636.2812067-1-adolf.belka@ipfire.org/
(In reply to Jon from comment #5) > (In reply to Michael Tremer from comment #4) > > In the meantime, uninstalling and reinstalling the package might fix the > > problem. > > I tried that but it did not help. Same error as in the 1st post. You have to remove the old netatalk file in your cache as it will use that to re-install. If the cache version is removed or renamed then IPFire will download the same version from the IPFire server but that one will have the updated library links. 1 - Uninstall netatalk 2 - In /var/cache/pakfire/ you should find a file named netatalk-3.1.12-2.ipfire Rename or delete that file. 3 - Install netatalk again. This time, as the file is not in your cache, IPFire will download it from the server. 4 - netatalk should now start. You should now find the netatalk-3.1.12-2.ipfire in the cache again, so if you renamed the old one then you can now delete it.
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=a5cdf05acc0e638ff544e1b31f6a0cda5c043985
(In reply to Adolf Belka from comment #7) > You have to remove the old netatalk file That worked! Thank you!
https://blog.ipfire.org/post/ipfire-2-27-core-update-169-is-available-for-testing
Bumping this to VERIFIED due to comment #9.
https://blog.ipfire.org/post/ipfire-2-27-core-update-169-released
All looks A-OK in CU 169. Yay! Thank you to all! Jon