On Saturday 25 May 2019 03:44:12 am 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. > > So when do we get a link to something we can build, test, and use, and > so that we are all "on the same page" again?
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!!! ============================================= root@coyote:~$ su backup backup@coyote:/root$ /usr/sbin/amcheck Daily amcheck: critical (fatal): Cannot create debug file "/var/log/amanda/server/amcheck.20190525035437.debug": Permission denied amcheck: Cannot create debug file "/var/log/amanda/server/amcheck.20190525035437.debug": Permission denied /usr/lib/x86_64-linux-gnu/amanda/libamanda-3.3.9.so(+0x2a367) [0x7fca9fdf7367] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x1e4)[0x7fca9ea945c4] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f)[0x7fca9ea947cf] /usr/lib/x86_64-linux-gnu/amanda/libamanda-3.3.9.so(debug_open+0x1d3) [0x7fca9fdf7893] /usr/sbin/amcheck(main+0xa1)[0x56283f254451] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fca9de0c2e1] /usr/sbin/amcheck(_start+0x2a)[0x56283f25568a] backup@coyote:/root$ cd backup@coyote:~$ ls alternatives.tar.0 alternatives.tar.6.gz apt.extended_states.5.gz dpkg.diversions.3.gz dpkg.statoverride.2.gz dpkg.status.1.gz group.bak alternatives.tar.1.gz apt.extended_states.0 apt.extended_states.6.gz dpkg.diversions.4.gz dpkg.statoverride.3.gz dpkg.status.2.gz gshadow.bak alternatives.tar.2.gz apt.extended_states.1.gz aptitude.pkgstates.0 dpkg.diversions.5.gz dpkg.statoverride.4.gz dpkg.status.3.gz passwd.bak alternatives.tar.3.gz apt.extended_states.2.gz dpkg.diversions.0 dpkg.diversions.6.gz dpkg.statoverride.5.gz dpkg.status.4.gz shadow.bak alternatives.tar.4.gz apt.extended_states.3.gz dpkg.diversions.1.gz dpkg.statoverride.0 dpkg.statoverride.6.gz dpkg.status.5.gz alternatives.tar.5.gz apt.extended_states.4.gz dpkg.diversions.2.gz dpkg.statoverride.1.gz dpkg.status.0 dpkg.status.6.gz backup@coyote:~$ pwd /var/backups ============================================ I have no clue what all that is about, let alone why is backup's home directory in /var/backups, but that is what I got from the last build attempt of the last tarball I could find. If you've a 3.5.1 ready to test, where is it? Copyright 2019 by Maurice E. Heskett Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
