(updating the Subject line in an attempt to keep the discussion subthreads separate...)
On Sat, May 25, 2019 at 03:44:12 -0400, Gene Heskett wrote: > On Friday 24 May 2019 10:37:15 am Chris Hassell wrote: > > > On 5/22/19 11:47 AM, Nathan Stratton Treadway wrote: > > > You can find the full set of patches in the source repo on Salsa, > > > i.e. in your web broswer at: > > > https://salsa.debian.org/debian/amanda/tree/master/debian/patches > > > > I just pushed a branch up (3_5-deb-patches or something) that includes > > their latest work against their "master". > > > > Some things seem quite reasonable. > > I wandered around on salsa, without finding an obviously ready to > download tarball that wasn't prehistoric. Or a src deb. The Salsa repo is for the official Debian packages. I don't believe there is any reason for you to download from it -- you should use the Zmanda release tar files (or for bleeding edge, the Zmanda github repo) directly. (I only posted that link here in order for Chris to take a look at the patches found over there.) On Sat, May 25, 2019 at 04:14:29 -0400, Gene Heskett wrote: > I just tried to rub what I do have and it makes zero difference whether I > am amanda or backup (theres no amandabackup user in the pw file so I > can't even become amandabackup. And as amanda or as backup I get thrown > out of running amcheck, with no permissions exits. > > Go back to the amanda:disk or amanda:backup model for starters. This is > insane!!! Gene, The choice of which user (and group) is used depends on the binaries you have installed. The problems you are currently running into result from switching back and fourth between package sources -- something which will always cause all kinds of trouble. The official Debian Amanda packages have always[*] used user=backup, group=backup. The Zmanda Debian packages have always[*] used user=amandabackup, group=disk for the Amanda programs (as documented on http://wiki.zmanda.com/index.php/Amanda_packages_from_Zmanda_downloads_page ). If you are trying to have user=amanda, then that must come from building your own binaries from source... So the question is what are you trying to accomplish now? I think you are only causing yourself trouble switching back and fourth from self-built to either sort of Debian packages. Have you decided to give up using your gh.cf build script, in favor of using one or the other flavor of Debian packages from now on? If not, you should de-install any amanda*.deb files currently installed, and make sure you don't try to use (at least on this particular server) any .deb files going forward (and avoid following any .deb-related build instructions as well). Then we can focus here on what's needed to get you back to some working system with your self-built, non-packaged binaries... Nathan [*] "always" meaning: definitely for the past decade or two, and probably since the very first version of each flavor of packages... ---------------------------------------------------------------------------- Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
