Activity log for bug #1785268

Date Who What changed Old value New value Message
2018-08-03 15:19:26 Chris Siebenmann bug added bug
2018-08-03 15:24:00 Chris Siebenmann description If you have an Amanda client machine, you have probably only installed the amanda-client package (and then amanda-common, which it depends on). If you try to run 'amrecover' on such a machine, you will get a failure: # amrecover -s <server> -t <server> -C <s_config> AMRECOVER Version 3.5.1. Contacting server on <server> ... [request failed: amrecover: error [exec /usr/lib/amanda/ambind: No such file or directory]] If you have an Ubuntu 18.04 Amanda client machine, you have probably only installed the amanda-client package (and then amanda-common, which it depends on). If you try to run 'amrecover' on such a machine, you will get a failure: # amrecover -s <server> -t <server> -C <s_config> AMRECOVER Version 3.5.1. Contacting server on <server> ... [request failed: amrecover: error [exec /usr/lib/amanda/ambind: No such file or directory]] This happens because the ambind program is packaged in the amanda-server package, which is not installed by default when you install amanda-client. The current Debian testing packages for Amanda also appear to have this issue, so Ubuntu's packages may have inherited it from upstream. The Amanda package version is '1:3.5.1-1build2'. This is on Ubuntu 18.04 ('bionic'); amrecover works fine in 16.04, but then 16.04 has Amanda 3.3.6, which is before Amanda introduced the ambind program. (My apologies for an initial incomplete submission of this report; bugs.launchpad.net decided to submit it when I was adding tags.)