Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Saturday 11 May 2019 03:40:46 am Gene Heskett wrote:

> On Friday 10 May 2019 05:06:25 pm Gene Heskett wrote:
> > On Friday 10 May 2019 12:05:32 pm Chris Hassell wrote:
> > > I think you just need to attack some debian-package-creation
> > > goodness and cd down into "packaging/deb".
> > >
> > > From there ... outside of documentation and examples ... you have
> > > these only to change:
> > >
> > > ~/.../packaging/deb #1$0 [..local:3_5]@BSL$ grep -n amandabackup *
> > >
> > > buildpkg:11:amanda_user=amandabackup
> > > postinst.src:12:amanda_user=amandabackup
> > > postrm.src:9:amanda_user=amandabackup
> > > postrm.src:56:# only call deluser when amandabackup is
> > > in $group preinst.src:10:amanda_user=amandabackup
> > > preinst.src:19:# We require amandabackup to have a specific uid
> > > because buildtime uid is rules:37:AMANDAUSER=amandabackup
> > >
> > > And you can even use the handy-dandy sed command line if you like:
> > >
> > > % sed -i -e 's/amandabackup/amanda/g' packaging/deb/*
> > >
> > > That's for the old issue... but for the new one (the prefix being
> > > /usr/local).. you can just change the variable there in the
> > > "rules" file (a package's make-and-package script).
> > >
> > >
> > >  14 # These are variables that the user can override.  They get
> > > used in various 15 # places during configure, build, and install.
> > > 16 PREFIX=/usr
> > >  17 BINDIR=$(PREFIX)/bin
> > >  18 triplet := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
> > >  19 ifeq ($(triplet),x86_64-linux-gnu)
> > >  20 LIBDIR=$(PREFIX)/lib/$(triplet)
> > >
> > > Again that's packaging/deb/rules ... line #16 changed to wherever
> > > you like your root-install to start.  I guess PREFIX=/usr/local
> > > should do it.
> > >
> > > -- CH
> > >
> > > On 5/10/19 8:14 AM, Gene Heskett wrote:
> > >
> > > On Friday 10 May 2019 10:13:30 am Chris Hassell wrote:
> > >
> > >
> > >
> > > On 5/9/19 11:31 PM, wrote:
> > >
> > >
> > > 
> > > but scanimage -L locks up tight useing zero cpu and is unkillable,
> > > I'll have to reboot to get rid of it.  This kernel is a preempt-rt
> > > kernel, and doesn't have some of a normal kernels bells and
> > > whistles, like usbhid-ups is missing, and that speaks to my ups.
> > >
> > >
> > >
> > > I have a kernel like that too with Manjaro/Arch... non custom.
> > > They're nice but boy they do take their time if something else is
> > > competing for resources.  Do a "dmesg" and see if something has
> > > bit down hard on your kernel's locks and crashed/paniced some
> > > thread.
> > >
> > >
> > >
> > > dmesg is rather non-commital, as I'd expect for a kernel that cam
> > > make sub 10 microsecond latencies in an old phenom. Normal kernels
> > > on an amd phenom are several hundred milliseconds.
> > > As for dmesg, no unusual other than it doesn't find a scanner at
> > > the same usb address as the Brother MFC-J6920DW printer. So I am
> > > going to shut down, swap sata1 and sata0 cables and boot back to
> > > wheezy where all this works, and see if the detection during dmesg
> > > is different.
> > >
> > >
> > >
> > > Maybe using "ps l" will show the symbol/wait-channel that
> > > it's stuck in.That's definitely one way to see why a process
> > > (if you can find the one) is sitting at zero cpu. "Pstree" is fun
> > > to use because it can show the 'leaf' ... the latest and lowest
> > > child that was created that all the rest of the process group are
> > > waiting on. That's usually the one in the spotlight... or the
> > > do-nothing-spotlight in this case.
> > >
> > >
> > >
> > > Unforch, no pstree seems to be available, ISTR i looked yesterday.
> > > Ahh, found it, its in psmisc.deb.  And its not reporting some
> > > things, I have a bash script that tells tde-kmail to go get the
> > > mail when a mail comes in and is written to /var/mail/$name. htop
> > > sees it. but pstree doesn't.
> > >
> > > pstree spits out 100 lines of hits, while htop says there are 111
> > > tasks ATM. But on a 5th run of pstree, mailwatcher is there. A
> > > Head scratcher.
> > >
> > > But I think I need to get sane, or scanimage -L working next as
> > > thats screw up several other things, like gimp and the *office*
> > > stuffs. I can kill the ups stuff thats spamming the logs. I've
> > > also posted to the emc-dev list about this kernel lack of a couple
> > > modules. So I'll expect things will eventually get fixed.
> >
> > [...]
> > One diff though, I
> >
> > > have never hand installed with a null prefix, always been
> > > /usr/local. Using your procedure, how would I make it work to
> > > build and install in /usr/local?
> >
> > Needs two more $varnames in the rules file, $USERNAME and $GROUPNAME
> > so that one does not have to troll all the way thru the rules file
> > to change all the names of the debs from amanda-backup-client to
> > amanda-client yadda yadda.
> >
> > But this needs to be in the git clone as downloaded or possibly as a
> > patch to be applied by autogen autoge

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Friday 10 May 2019 05:06:25 pm Gene Heskett wrote:

> On Friday 10 May 2019 12:05:32 pm Chris Hassell wrote:
> > I think you just need to attack some debian-package-creation
> > goodness and cd down into "packaging/deb".
> >
> > From there ... outside of documentation and examples ... you have
> > these only to change:
> >
> > ~/.../packaging/deb #1$0 [..local:3_5]@BSL$ grep -n amandabackup *
> >
> > buildpkg:11:amanda_user=amandabackup
> > postinst.src:12:amanda_user=amandabackup
> > postrm.src:9:amanda_user=amandabackup
> > postrm.src:56:# only call deluser when amandabackup is
> > in $group preinst.src:10:amanda_user=amandabackup
> > preinst.src:19:# We require amandabackup to have a specific uid
> > because buildtime uid is rules:37:AMANDAUSER=amandabackup
> >
> > And you can even use the handy-dandy sed command line if you like:
> >
> > % sed -i -e 's/amandabackup/amanda/g' packaging/deb/*
> >
> > That's for the old issue... but for the new one (the prefix being
> > /usr/local).. you can just change the variable there in the "rules"
> > file (a package's make-and-package script).
> >
> >
> >  14 # These are variables that the user can override.  They get used
> > in various 15 # places during configure, build, and install.
> >  16 PREFIX=/usr
> >  17 BINDIR=$(PREFIX)/bin
> >  18 triplet := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
> >  19 ifeq ($(triplet),x86_64-linux-gnu)
> >  20 LIBDIR=$(PREFIX)/lib/$(triplet)
> >
> > Again that's packaging/deb/rules ... line #16 changed to wherever
> > you like your root-install to start.  I guess PREFIX=/usr/local
> > should do it.
> >
> > -- CH
> >
> > On 5/10/19 8:14 AM, Gene Heskett wrote:
> >
> > On Friday 10 May 2019 10:13:30 am Chris Hassell wrote:
> >
> >
> >
> > On 5/9/19 11:31 PM, wrote:
> >
> >
> > 
> > but scanimage -L locks up tight useing zero cpu and is unkillable,
> > I'll have to reboot to get rid of it.  This kernel is a preempt-rt
> > kernel, and doesn't have some of a normal kernels bells and
> > whistles, like usbhid-ups is missing, and that speaks to my ups.
> >
> >
> >
> > I have a kernel like that too with Manjaro/Arch... non custom.
> > They're nice but boy they do take their time if something else is
> > competing for resources.  Do a "dmesg" and see if something has bit
> > down hard on your kernel's locks and crashed/paniced some thread.
> >
> >
> >
> > dmesg is rather non-commital, as I'd expect for a kernel that cam
> > make sub 10 microsecond latencies in an old phenom. Normal kernels
> > on an amd phenom are several hundred milliseconds.
> > As for dmesg, no unusual other than it doesn't find a scanner at the
> > same usb address as the Brother MFC-J6920DW printer. So I am going
> > to shut down, swap sata1 and sata0 cables and boot back to wheezy
> > where all this works, and see if the detection during dmesg is
> > different.
> >
> >
> >
> > Maybe using "ps l" will show the symbol/wait-channel that it's
> > stuck in.That's definitely one way to see why a process (if you
> > can find the one) is sitting at zero cpu. "Pstree" is fun to use
> > because it can show the 'leaf' ... the latest and lowest child that
> > was created that all the rest of the process group are waiting on.
> > That's usually the one in the spotlight... or the
> > do-nothing-spotlight in this case.
> >
> >
> >
> > Unforch, no pstree seems to be available, ISTR i looked yesterday.
> > Ahh, found it, its in psmisc.deb.  And its not reporting some
> > things, I have a bash script that tells tde-kmail to go get the mail
> > when a mail comes in and is written to /var/mail/$name. htop sees
> > it. but pstree doesn't.
> >
> > pstree spits out 100 lines of hits, while htop says there are 111
> > tasks ATM. But on a 5th run of pstree, mailwatcher is there. A Head
> > scratcher.
> >
> > But I think I need to get sane, or scanimage -L working next as
> > thats screw up several other things, like gimp and the *office*
> > stuffs. I can kill the ups stuff thats spamming the logs. I've also
> > posted to the emc-dev list about this kernel lack of a couple
> > modules. So I'll expect things will eventually get fixed.
>
> [...]
> One diff though, I
>
> > have never hand installed with a null prefix, always been
> > /usr/local. Using your procedure, how would I make it work to build
> > and install in /usr/local?
>
> Needs two more $varnames in the rules file, $USERNAME and $GROUPNAME
> so that one does not have to troll all the way thru the rules file to
> change all the names of the debs from amanda-backup-client to
> amanda-client yadda yadda.
>
> But this needs to be in the git clone as downloaded or possibly as a
> patch to be applied by autogen autogen or thereabouts.  Otherwise its
> a lot of work, only to be rewritten back to the original by the fresh
> git clone.  Or can I just do a make clean and rerun the packaging
> command to change both the prefix and the packaging names?
>
>
> I've done the rules edits, now lets see what I get st

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Friday 10 May 2019 12:05:32 pm Chris Hassell wrote:

> I think you just need to attack some debian-package-creation goodness
> and cd down into "packaging/deb".
>
> From there ... outside of documentation and examples ... you have
> these only to change:
>
> ~/.../packaging/deb #1$0 [..local:3_5]@BSL$ grep -n amandabackup *
>
> buildpkg:11:amanda_user=amandabackup
> postinst.src:12:amanda_user=amandabackup
> postrm.src:9:amanda_user=amandabackup
> postrm.src:56:# only call deluser when amandabackup is in
> $group preinst.src:10:amanda_user=amandabackup
> preinst.src:19:# We require amandabackup to have a specific uid
> because buildtime uid is rules:37:AMANDAUSER=amandabackup
>
> And you can even use the handy-dandy sed command line if you like:
>
> % sed -i -e 's/amandabackup/amanda/g' packaging/deb/*
>
> That's for the old issue... but for the new one (the prefix being
> /usr/local).. you can just change the variable there in the "rules"
> file (a package's make-and-package script).
>
>
>  14 # These are variables that the user can override.  They get used
> in various 15 # places during configure, build, and install.
>  16 PREFIX=/usr
>  17 BINDIR=$(PREFIX)/bin
>  18 triplet := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
>  19 ifeq ($(triplet),x86_64-linux-gnu)
>  20 LIBDIR=$(PREFIX)/lib/$(triplet)
>
> Again that's packaging/deb/rules ... line #16 changed to wherever you
> like your root-install to start.  I guess PREFIX=/usr/local should do
> it.
>
> -- CH
>
> On 5/10/19 8:14 AM, Gene Heskett wrote:
>
> On Friday 10 May 2019 10:13:30 am Chris Hassell wrote:
>
>
>
> On 5/9/19 11:31 PM, wrote:
>
>
> 
> but scanimage -L locks up tight useing zero cpu and is unkillable,
> I'll have to reboot to get rid of it.  This kernel is a preempt-rt
> kernel, and doesn't have some of a normal kernels bells and
> whistles, like usbhid-ups is missing, and that speaks to my ups.
>
>
>
> I have a kernel like that too with Manjaro/Arch... non custom. They're
> nice but boy they do take their time if something else is competing
> for resources.  Do a "dmesg" and see if something has bit down hard on
> your kernel's locks and crashed/paniced some thread.
>
>
>
> dmesg is rather non-commital, as I'd expect for a kernel that cam make
> sub 10 microsecond latencies in an old phenom. Normal kernels on an
> amd phenom are several hundred milliseconds.
> As for dmesg, no unusual other than it doesn't find a scanner at the
> same usb address as the Brother MFC-J6920DW printer. So I am going to
> shut down, swap sata1 and sata0 cables and boot back to wheezy where
> all this works, and see if the detection during dmesg is different.
>
>
>
> Maybe using "ps l" will show the symbol/wait-channel that it's
> stuck in.That's definitely one way to see why a process (if you
> can find the one) is sitting at zero cpu. "Pstree" is fun to use
> because it can show the 'leaf' ... the latest and lowest child that
> was created that all the rest of the process group are waiting on.
> That's usually the one in the spotlight... or the do-nothing-spotlight
> in this case.
>
>
>
> Unforch, no pstree seems to be available, ISTR i looked yesterday.
> Ahh, found it, its in psmisc.deb.  And its not reporting some things,
> I have a bash script that tells tde-kmail to go get the mail when a
> mail comes in and is written to /var/mail/$name. htop sees it. but
> pstree doesn't.
>
> pstree spits out 100 lines of hits, while htop says there are 111
> tasks ATM. But on a 5th run of pstree, mailwatcher is there. A Head
> scratcher.
>
> But I think I need to get sane, or scanimage -L working next as thats
> screw up several other things, like gimp and the *office* stuffs. I
> can kill the ups stuff thats spamming the logs. I've also posted to
> the emc-dev list about this kernel lack of a couple modules. So I'll
> expect things will eventually get fixed.
[...]
One diff though, I
> have never hand installed with a null prefix, always been /usr/local. 
> Using your procedure, how would I make it work to build and install in
> /usr/local?

>
Needs two more $varnames in the rules file, $USERNAME and $GROUPNAME so 
that one does not have to troll all the way thru the rules file to 
change all the names of the debs from amanda-backup-client to 
amanda-client yadda yadda.

But this needs to be in the git clone as downloaded or possibly as a 
patch to be applied by autogen autogen or thereabouts.  Otherwise its a 
lot of work, only to be rewritten back to the original by the fresh git 
clone.  Or can I just do a make clean and rerun the packaging command to 
change both the prefix and the packaging names?


I've done the rules edits, now lets see what I get starting with "bash 
autogen".

But that blew up, and I don't see why, so rules 
and /var/log/amanda.install.log from yesterday's fail is attached.
And I can't find the build.log if there is one.

One other comment, I only tried dump once, 20 years ago, such a disaster 
I've used tar e

Re: Debian-based Amanda Build ... (revised)...

[Chris Hassell]

I think you just need to attack some debian-package-creation goodness and cd 
down into "packaging/deb".

From there ... outside of documentation and examples ... you have these only to 
change:

~/.../packaging/deb #1$0 [..local:3_5]@BSL$ grep -n amandabackup *

buildpkg:11:amanda_user=amandabackup
postinst.src:12:amanda_user=amandabackup
postrm.src:9:amanda_user=amandabackup
postrm.src:56:# only call deluser when amandabackup is in $group
preinst.src:10:amanda_user=amandabackup
preinst.src:19:# We require amandabackup to have a specific uid because 
buildtime uid is
rules:37:AMANDAUSER=amandabackup

And you can even use the handy-dandy sed command line if you like:

% sed -i -e 's/amandabackup/amanda/g' packaging/deb/*

That's for the old issue... but for the new one (the prefix being /usr/local).. 
you can just change the variable there in the "rules" file (a package's 
make-and-package script).


 14 # These are variables that the user can override.  They get used in various
 15 # places during configure, build, and install.
 16 PREFIX=/usr
 17 BINDIR=$(PREFIX)/bin
 18 triplet := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 19 ifeq ($(triplet),x86_64-linux-gnu)
 20 LIBDIR=$(PREFIX)/lib/$(triplet)

Again that's packaging/deb/rules ... line #16 changed to wherever you like your 
root-install to start.  I guess PREFIX=/usr/local should do it.

-- CH

On 5/10/19 8:14 AM, Gene Heskett wrote:

On Friday 10 May 2019 10:13:30 am Chris Hassell wrote:



On 5/9/19 11:31 PM, wrote:



but scanimage -L locks up tight useing zero cpu and is unkillable,
I'll have to reboot to get rid of it.  This kernel is a preempt-rt
kernel, and doesn't have some of a normal kernels bells and
whistles, like usbhid-ups is missing, and that speaks to my ups.



I have a kernel like that too with Manjaro/Arch... non custom. They're
nice but boy they do take their time if something else is competing
for resources.  Do a "dmesg" and see if something has bit down hard on
your kernel's locks and crashed/paniced some thread.



dmesg is rather non-commital, as I'd expect for a kernel that cam make
sub 10 microsecond latencies in an old phenom. Normal kernels on an amd
phenom are several hundred milliseconds.
As for dmesg, no unusual other than it doesn't find a scanner at the same
usb address as the Brother MFC-J6920DW printer. So I am going to shut
down, swap sata1 and sata0 cables and boot back to wheezy where all this
works, and see if the detection during dmesg is different.



Maybe using "ps l" will show the symbol/wait-channel that it's
stuck in.That's definitely one way to see why a process (if you
can find the one) is sitting at zero cpu. "Pstree" is fun to use
because it can show the 'leaf' ... the latest and lowest child that
was created that all the rest of the process group are waiting on.
That's usually the one in the spotlight... or the do-nothing-spotlight
in this case.



Unforch, no pstree seems to be available, ISTR i looked yesterday. Ahh,
found it, its in psmisc.deb.  And its not reporting some things, I have
a bash script that tells tde-kmail to go get the mail when a mail comes
in and is written to /var/mail/$name. htop sees it. but pstree doesn't.

pstree spits out 100 lines of hits, while htop says there are 111 tasks
ATM. But on a 5th run of pstree, mailwatcher is there. A Head scratcher.

But I think I need to get sane, or scanimage -L working next as thats
screw up several other things, like gimp and the *office* stuffs. I can
kill the ups stuff thats spamming the logs. I've also posted to the
emc-dev list about this kernel lack of a couple modules. So I'll expect
things will eventually get fixed.



And synaptic just asked me to cleanup the cache with a
dpkg --configure -a, which will make me reboot as its now locked up
trying to configure amanda-backup-server.  But I was able to kill it
and run dpkg -r amanda-backup-server, so now syanaptic can run and
its got about a dozen libs to update, so when its done and I have
sent this, reboot time.



It is very common for dpkg / debian, at various times, to get all
console-interactive too.  Maybe something is wanting to chat and is
waiting on a keyboard response in the terminal?   I'm glad you at
least removed it properly.

When all the rest of the packages are installed and behaving correctly
... then maybe try again.   The amanda post-install isn't that
complex that I know of??



Seems like the way forward at this point.  It seems to be getting stuck
in the dpkg configure stage, possibly permissions? IDK.  But with this
kernel, I'd have to claim its a custom install. I might point out
however, that synaptic has not had an similar problems with anything
I've asked it to install from the repo's so far.  That does seem to
point at the deb pkg as being the problem.  One diff though, I have
never hand installed with a null prefix, always been /usr/local.  Using
your procedure, how would I make it work to build and install
in /usr/local?

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Friday 10 May 2019 10:13:30 am Chris Hassell wrote:

> On 5/9/19 11:31 PM, wrote:
> > 
> > but scanimage -L locks up tight useing zero cpu and is unkillable,
> > I'll have to reboot to get rid of it.  This kernel is a preempt-rt
> > kernel, and doesn't have some of a normal kernels bells and
> > whistles, like usbhid-ups is missing, and that speaks to my ups.
>
> I have a kernel like that too with Manjaro/Arch... non custom. They're
> nice but boy they do take their time if something else is competing
> for resources.  Do a "dmesg" and see if something has bit down hard on
> your kernel's locks and crashed/paniced some thread.
>
dmesg is rather non-commital, as I'd expect for a kernel that cam make 
sub 10 microsecond latencies in an old phenom. Normal kernels on an amd 
phenom are several hundred milliseconds.
As for dmesg, no unusual other than it doesn't find a scanner at the same 
usb address as the Brother MFC-J6920DW printer. So I am going to shut 
down, swap sata1 and sata0 cables and boot back to wheezy where all this 
works, and see if the detection during dmesg is different.

> Maybe using "ps l" will show the symbol/wait-channel that it's
> stuck in.    That's definitely one way to see why a process (if you
> can find the one) is sitting at zero cpu. "Pstree" is fun to use
> because it can show the 'leaf' ... the latest and lowest child that
> was created that all the rest of the process group are waiting on. 
> That's usually the one in the spotlight... or the do-nothing-spotlight
> in this case.

Unforch, no pstree seems to be available, ISTR i looked yesterday. Ahh, 
found it, its in psmisc.deb.  And its not reporting some things, I have 
a bash script that tells tde-kmail to go get the mail when a mail comes 
in and is written to /var/mail/$name. htop sees it. but pstree doesn't.
 
pstree spits out 100 lines of hits, while htop says there are 111 tasks 
ATM. But on a 5th run of pstree, mailwatcher is there. A Head scratcher.

But I think I need to get sane, or scanimage -L working next as thats 
screw up several other things, like gimp and the *office* stuffs. I can 
kill the ups stuff thats spamming the logs. I've also posted to the 
emc-dev list about this kernel lack of a couple modules. So I'll expect 
things will eventually get fixed.

> > And synaptic just asked me to cleanup the cache with a
> > dpkg --configure -a, which will make me reboot as its now locked up
> > trying to configure amanda-backup-server.  But I was able to kill it
> > and run dpkg -r amanda-backup-server, so now syanaptic can run and
> > its got about a dozen libs to update, so when its done and I have
> > sent this, reboot time.
>
> It is very common for dpkg / debian, at various times, to get all
> console-interactive too.  Maybe something is wanting to chat and is
> waiting on a keyboard response in the terminal?   I'm glad you at
> least removed it properly.
>
> When all the rest of the packages are installed and behaving correctly
> ... then maybe try again.   The amanda post-install isn't that
> complex that I know of??

Seems like the way forward at this point.  It seems to be getting stuck 
in the dpkg configure stage, possibly permissions? IDK.  But with this 
kernel, I'd have to claim its a custom install. I might point out 
however, that synaptic has not had an similar problems with anything 
I've asked it to install from the repo's so far.  That does seem to 
point at the deb pkg as being the problem.  One diff though, I have 
never hand installed with a null prefix, always been /usr/local.  Using 
your procedure, how would I make it work to build and install 
in /usr/local?


> > Copyright 2019 by Maurice E. Heskett
> > Cheers, Gene 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 

Re: Debian-based Amanda Build ... (revised)...

[Stefan G. Weichinger]

Am 10.05.19 um 02:20 schrieb Chris Hassell:
> That's pretty bonkers.  There's nothing in the setup that I know of 
> that's been changed.   Never happened to me.
> 
> Try a "pstree -phul" to see if you can find wth it was trying to do.   
> Did htop show something spinning ... or a specific process going nuts?

quick side note from a short vacation (maybe slightly off topic then):

I suggest writing an ansible role for example: this could reflect the
various dependencies for OSes and also be used as foundation for
automated tests later.

Basically an ansible role is also kind of a howto as it is
human-readable ...

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Thursday 09 May 2019 08:20:11 pm Chris Hassell wrote:

> That's pretty bonkers.  There's nothing in the setup that I know of
> that's been changed.   Never happened to me.
>
> Try a "pstree -phul" to see if you can find wth it was trying to do.  
> Did htop show something spinning ... or a specific process going nuts?
>
> On 5/9/19 4:50 PM, Gene Heskett wrote:
> > On Thursday 09 May 2019 04:58:20 pm Gene Heskett wrote:
> >> On Thursday 09 May 2019 04:35:40 pm Chris Hassell wrote:
> >>> 
> >>> amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin
> >>>
> >>> That's what I have for amandabackup.  A no-frills-nothing and no
> >>> password user.  Don't get why it can't be a dup of your other one.
> >>> Hrm
> >>>
> >>> Looks like the rest of the build was happy enough from the parts
> >>> you gave.
> >>>
> >>> On 5/9/19 12:26 PM, Gene Heskett wrote:
> >>>
> >>>
> >>> And, I'm looking at 4 debs:
> >>> amanda@coyote:~/amanda$ ls -l *.deb
> >>> -rw-r--r-- 1 amanda amanda 1298594 May  9 14:48
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda  101638 May  9 14:48
> >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda 2085650 May  9 14:48
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda  140310 May  9 14:48
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>>
> >>> Those are a good sign too.
> >>>
> >>> root@coyote:amanda$ dpkg -i *.deb
> >>>
> >>> Selecting previously unselected package amanda-backup-client.
> >>> dpkg: regarding
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> containing amanda-backup-client:
> >>>   amanda-backup-client conflicts with amanda-client
> >>>amanda-client (version 1:3.3.9-5) is present and installed.
> >>>
> >>> dpkg: error processing archive
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install): conflicting packages - not installing
> >>> amanda-backup-client
> >>>
> >>>
> >>> One old package is still installed... and conflicts, so it needs a
> >>> 'dpkg -r amanda-client'.
> >>>
> >>> Selecting previously unselected package
> >>> amanda-backup-client-dbgsym. (Reading database ... 267815 files
> >>> and directories currently installed.) Preparing to unpack
> >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> ... Unpacking amanda-backup-client-dbgsym
> >>> (3.5.1.git.19364c7b-1Debian99) ...
> >>>
> >>> Selecting previously unselected package amanda-backup-server.
> >>> dpkg: regarding
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> containing amanda-backup-server:
> >>>   amanda-backup-server conflicts with amanda-client
> >>>amanda-client (version 1:3.3.9-5) is present and installed.
> >>>
> >>> dpkg: error processing archive
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install): conflicting packages - not installing
> >>> amanda-backup-server
> >>>
> >>> Same problem, different attempt to install the server file instead
> >>> and it refused.
> >>>
> >>> Selecting previously unselected package
> >>> amanda-backup-server-dbgsym. Preparing to unpack
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> ... Unpacking amanda-backup-server-dbgsym
> >>> (3.5.1.git.19364c7b-1Debian99) ... dpkg: error processing archive
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install):
> >>>   trying to
> >>> overwrite
> >>> '/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a
> >>>5. de bug', which is also in package amanda-backup-client-dbgsym
> >>> 3.5.1.git.19364c7b-1Debian99
> >>>
> >>> Ahh... both the server and client packages can't be installed
> >>> together and the same would go for its debug files.
> >>>
> >>> May want to run 'dpkg -l | grep amanda' to see what's on there and
> >>> take off things that are old or that got in without cooperating
> >>> yet.
> >>>
> >>> dpkg-deb: error: subprocess paste was killed by signal (Broken
> >>> pipe) dpkg: dependency problems prevent configuration of
> >>> amanda-backup-client-dbgsym:
> >>>   amanda-backup-client-dbgsym depends on amanda-backup-client (=
> >>> 3.5.1.git.19364c7b-1Debian99); however:
> >>>Package amanda-backup-client is not installed.
> >>>
> >>> dpkg: error processing package amanda-backup-client-dbgsym
> >>> (--install): dependency problems - leaving unconfigured
> >>> Errors were encountered while processing:
> >>>   amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>>   amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>>  
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> amanda-backup-client-dbgsym
> >>>
> >>>
> >>> That seems to be the sum of it:  remove the old and install the
> >>> *backup-server*deb files only.
> >>>
> >>> The only amanda stuff was /usr/local/etc/am

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Thursday 09 May 2019 08:20:11 pm Chris Hassell wrote:

> That's pretty bonkers.  There's nothing in the setup that I know of
> that's been changed.   Never happened to me.
>
> Try a "pstree -phul" to see if you can find wth it was trying to do.  
> Did htop show something spinning ... or a specific process going nuts?
>
I might try the install again tomorrow, and I may be remembering it 
wrong, but I killed what I thought was the parent dpkg install, then had 
to kill a dpkg --configure process to get my prompt back. I had at the 
time another unkillable util running but do not now recall its name, and 
scanning thru whats running now, I don't see a memory triggering name.
And the last two days have about wore the old man out so I've taken my 
evening pills and am headed across the hal to bed.

> On 5/9/19 4:50 PM, Gene Heskett wrote:
> > On Thursday 09 May 2019 04:58:20 pm Gene Heskett wrote:
> >> On Thursday 09 May 2019 04:35:40 pm Chris Hassell wrote:
> >>> 
> >>> amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin
> >>>
> >>> That's what I have for amandabackup.  A no-frills-nothing and no
> >>> password user.  Don't get why it can't be a dup of your other one.
> >>> Hrm
> >>>
> >>> Looks like the rest of the build was happy enough from the parts
> >>> you gave.
> >>>
> >>> On 5/9/19 12:26 PM, Gene Heskett wrote:
> >>>
> >>>
> >>> And, I'm looking at 4 debs:
> >>> amanda@coyote:~/amanda$ ls -l *.deb
> >>> -rw-r--r-- 1 amanda amanda 1298594 May  9 14:48
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda  101638 May  9 14:48
> >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda 2085650 May  9 14:48
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda  140310 May  9 14:48
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>>
> >>> Those are a good sign too.
> >>>
> >>> root@coyote:amanda$ dpkg -i *.deb
> >>>
> >>> Selecting previously unselected package amanda-backup-client.
> >>> dpkg: regarding
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> containing amanda-backup-client:
> >>>   amanda-backup-client conflicts with amanda-client
> >>>amanda-client (version 1:3.3.9-5) is present and installed.
> >>>
> >>> dpkg: error processing archive
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install): conflicting packages - not installing
> >>> amanda-backup-client
> >>>
> >>>
> >>> One old package is still installed... and conflicts, so it needs a
> >>> 'dpkg -r amanda-client'.
> >>>
> >>> Selecting previously unselected package
> >>> amanda-backup-client-dbgsym. (Reading database ... 267815 files
> >>> and directories currently installed.) Preparing to unpack
> >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> ... Unpacking amanda-backup-client-dbgsym
> >>> (3.5.1.git.19364c7b-1Debian99) ...
> >>>
> >>> Selecting previously unselected package amanda-backup-server.
> >>> dpkg: regarding
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> containing amanda-backup-server:
> >>>   amanda-backup-server conflicts with amanda-client
> >>>amanda-client (version 1:3.3.9-5) is present and installed.
> >>>
> >>> dpkg: error processing archive
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install): conflicting packages - not installing
> >>> amanda-backup-server
> >>>
> >>> Same problem, different attempt to install the server file instead
> >>> and it refused.
> >>>
> >>> Selecting previously unselected package
> >>> amanda-backup-server-dbgsym. Preparing to unpack
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> ... Unpacking amanda-backup-server-dbgsym
> >>> (3.5.1.git.19364c7b-1Debian99) ... dpkg: error processing archive
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install):
> >>>   trying to
> >>> overwrite
> >>> '/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a
> >>>5. de bug', which is also in package amanda-backup-client-dbgsym
> >>> 3.5.1.git.19364c7b-1Debian99
> >>>
> >>> Ahh... both the server and client packages can't be installed
> >>> together and the same would go for its debug files.
> >>>
> >>> May want to run 'dpkg -l | grep amanda' to see what's on there and
> >>> take off things that are old or that got in without cooperating
> >>> yet.
> >>>
> >>> dpkg-deb: error: subprocess paste was killed by signal (Broken
> >>> pipe) dpkg: dependency problems prevent configuration of
> >>> amanda-backup-client-dbgsym:
> >>>   amanda-backup-client-dbgsym depends on amanda-backup-client (=
> >>> 3.5.1.git.19364c7b-1Debian99); however:
> >>>Package amanda-backup-client is not installed.
> >>>
> >>> dpkg: error processing package amanda-backup-client-dbgsym
> >>> (--install): dependency problems - leaving un

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Thursday 09 May 2019 08:20:11 pm Chris Hassell wrote:

> That's pretty bonkers.  There's nothing in the setup that I know of
> that's been changed.   Never happened to me.
>
> Try a "pstree -phul" to see if you can find wth it was trying to do.  
> Did htop show something spinning ... or a specific process going nuts?
>
Let me clarify, the processs's were there, doing nothing, and using zero 
cpu.  And took a #9 sigkill to stop them.

> On 5/9/19 4:50 PM, Gene Heskett wrote:
> > On Thursday 09 May 2019 04:58:20 pm Gene Heskett wrote:
> >> On Thursday 09 May 2019 04:35:40 pm Chris Hassell wrote:
> >>> 
> >>> amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin
> >>>
> >>> That's what I have for amandabackup.  A no-frills-nothing and no
> >>> password user.  Don't get why it can't be a dup of your other one.
> >>> Hrm
> >>>
> >>> Looks like the rest of the build was happy enough from the parts
> >>> you gave.
> >>>
> >>> On 5/9/19 12:26 PM, Gene Heskett wrote:
> >>>
> >>>
> >>> And, I'm looking at 4 debs:
> >>> amanda@coyote:~/amanda$ ls -l *.deb
> >>> -rw-r--r-- 1 amanda amanda 1298594 May  9 14:48
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda  101638 May  9 14:48
> >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda 2085650 May  9 14:48
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> -rw-r--r-- 1 amanda amanda  140310 May  9 14:48
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>>
> >>> Those are a good sign too.
> >>>
> >>> root@coyote:amanda$ dpkg -i *.deb
> >>>
> >>> Selecting previously unselected package amanda-backup-client.
> >>> dpkg: regarding
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> containing amanda-backup-client:
> >>>   amanda-backup-client conflicts with amanda-client
> >>>amanda-client (version 1:3.3.9-5) is present and installed.
> >>>
> >>> dpkg: error processing archive
> >>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install): conflicting packages - not installing
> >>> amanda-backup-client
> >>>
> >>>
> >>> One old package is still installed... and conflicts, so it needs a
> >>> 'dpkg -r amanda-client'.
> >>>
> >>> Selecting previously unselected package
> >>> amanda-backup-client-dbgsym. (Reading database ... 267815 files
> >>> and directories currently installed.) Preparing to unpack
> >>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> ... Unpacking amanda-backup-client-dbgsym
> >>> (3.5.1.git.19364c7b-1Debian99) ...
> >>>
> >>> Selecting previously unselected package amanda-backup-server.
> >>> dpkg: regarding
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> containing amanda-backup-server:
> >>>   amanda-backup-server conflicts with amanda-client
> >>>amanda-client (version 1:3.3.9-5) is present and installed.
> >>>
> >>> dpkg: error processing archive
> >>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install): conflicting packages - not installing
> >>> amanda-backup-server
> >>>
> >>> Same problem, different attempt to install the server file instead
> >>> and it refused.
> >>>
> >>> Selecting previously unselected package
> >>> amanda-backup-server-dbgsym. Preparing to unpack
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> ... Unpacking amanda-backup-server-dbgsym
> >>> (3.5.1.git.19364c7b-1Debian99) ... dpkg: error processing archive
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> (--install):
> >>>   trying to
> >>> overwrite
> >>> '/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a
> >>>5. de bug', which is also in package amanda-backup-client-dbgsym
> >>> 3.5.1.git.19364c7b-1Debian99
> >>>
> >>> Ahh... both the server and client packages can't be installed
> >>> together and the same would go for its debug files.
> >>>
> >>> May want to run 'dpkg -l | grep amanda' to see what's on there and
> >>> take off things that are old or that got in without cooperating
> >>> yet.
> >>>
> >>> dpkg-deb: error: subprocess paste was killed by signal (Broken
> >>> pipe) dpkg: dependency problems prevent configuration of
> >>> amanda-backup-client-dbgsym:
> >>>   amanda-backup-client-dbgsym depends on amanda-backup-client (=
> >>> 3.5.1.git.19364c7b-1Debian99); however:
> >>>Package amanda-backup-client is not installed.
> >>>
> >>> dpkg: error processing package amanda-backup-client-dbgsym
> >>> (--install): dependency problems - leaving unconfigured
> >>> Errors were encountered while processing:
> >>>   amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>>   amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>>  
> >>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >>> amanda-backup-client-dbgsym
> >>>
> >>>
> >>> That seems to be the sum of it:  remove

Re: Debian-based Amanda Build ... (revised)...

[Chris Hassell]

That's pretty bonkers.  There's nothing in the setup that I know of 
that's been changed.   Never happened to me.

Try a "pstree -phul" to see if you can find wth it was trying to do.   
Did htop show something spinning ... or a specific process going nuts?

On 5/9/19 4:50 PM, Gene Heskett wrote:
> On Thursday 09 May 2019 04:58:20 pm Gene Heskett wrote:
>
>> On Thursday 09 May 2019 04:35:40 pm Chris Hassell wrote:
>>>  amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin
>>>
>>> That's what I have for amandabackup.  A no-frills-nothing and no
>>> password user.  Don't get why it can't be a dup of your other one.
>>> Hrm
>>>
>>> Looks like the rest of the build was happy enough from the parts you
>>> gave.
>>>
>>> On 5/9/19 12:26 PM, Gene Heskett wrote:
>>>
>>>
>>> And, I'm looking at 4 debs:
>>> amanda@coyote:~/amanda$ ls -l *.deb
>>> -rw-r--r-- 1 amanda amanda 1298594 May  9 14:48
>>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> -rw-r--r-- 1 amanda amanda  101638 May  9 14:48
>>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> -rw-r--r-- 1 amanda amanda 2085650 May  9 14:48
>>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> -rw-r--r-- 1 amanda amanda  140310 May  9 14:48
>>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>>
>>> Those are a good sign too.
>>>
>>> root@coyote:amanda$ dpkg -i *.deb
>>>
>>> Selecting previously unselected package amanda-backup-client.
>>> dpkg: regarding
>>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> containing amanda-backup-client:
>>>   amanda-backup-client conflicts with amanda-client
>>>amanda-client (version 1:3.3.9-5) is present and installed.
>>>
>>> dpkg: error processing archive
>>> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> (--install): conflicting packages - not installing
>>> amanda-backup-client
>>>
>>>
>>> One old package is still installed... and conflicts, so it needs a
>>> 'dpkg -r amanda-client'.
>>>
>>> Selecting previously unselected package amanda-backup-client-dbgsym.
>>> (Reading database ... 267815 files and directories currently
>>> installed.) Preparing to unpack
>>> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> ... Unpacking amanda-backup-client-dbgsym
>>> (3.5.1.git.19364c7b-1Debian99) ...
>>>
>>> Selecting previously unselected package amanda-backup-server.
>>> dpkg: regarding
>>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> containing amanda-backup-server:
>>>   amanda-backup-server conflicts with amanda-client
>>>amanda-client (version 1:3.3.9-5) is present and installed.
>>>
>>> dpkg: error processing archive
>>> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> (--install): conflicting packages - not installing
>>> amanda-backup-server
>>>
>>> Same problem, different attempt to install the server file instead
>>> and it refused.
>>>
>>> Selecting previously unselected package amanda-backup-server-dbgsym.
>>> Preparing to unpack
>>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> ... Unpacking amanda-backup-server-dbgsym
>>> (3.5.1.git.19364c7b-1Debian99) ... dpkg: error processing archive
>>> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>> (--install):
>>>   trying to
>>> overwrite
>>> '/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a5.
>>> de bug', which is also in package amanda-backup-client-dbgsym
>>> 3.5.1.git.19364c7b-1Debian99
>>>
>>> Ahh... both the server and client packages can't be installed
>>> together and the same would go for its debug files.
>>>
>>> May want to run 'dpkg -l | grep amanda' to see what's on there and
>>> take off things that are old or that got in without cooperating yet.
>>>
>>> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>>> dpkg: dependency problems prevent configuration of
>>> amanda-backup-client-dbgsym:
>>>   amanda-backup-client-dbgsym depends on amanda-backup-client (=
>>> 3.5.1.git.19364c7b-1Debian99); however:
>>>Package amanda-backup-client is not installed.
>>>
>>> dpkg: error processing package amanda-backup-client-dbgsym
>>> (--install): dependency problems - leaving unconfigured
>>> Errors were encountered while processing:
>>>   amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>>   amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>>   amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>>>   amanda-backup-client-dbgsym
>>>
>>>
>>> That seems to be the sum of it:  remove the old and install the
>>> *backup-server*deb files only.
>>>
>>> The only amanda stuff was /usr/local/etc/amanda/DAILY copied from
>>> the old disk to preserve my system, and about 20 files of the old
>>> amanda install in /usr/local/lib/amanda, all dated from Jan 2017 so
>>> they aren't precious now.  But all the old installs using amanda's
>>> own Makefile, simply overwrote them instead of having 

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Thursday 09 May 2019 04:58:20 pm Gene Heskett wrote:

> On Thursday 09 May 2019 04:35:40 pm Chris Hassell wrote:
> > amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin
> >
> > That's what I have for amandabackup.  A no-frills-nothing and no
> > password user.  Don't get why it can't be a dup of your other one.
> > Hrm
> >
> > Looks like the rest of the build was happy enough from the parts you
> > gave.
> >
> > On 5/9/19 12:26 PM, Gene Heskett wrote:
> >
> >
> > And, I'm looking at 4 debs:
> > amanda@coyote:~/amanda$ ls -l *.deb
> > -rw-r--r-- 1 amanda amanda 1298594 May  9 14:48
> > amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > -rw-r--r-- 1 amanda amanda  101638 May  9 14:48
> > amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > -rw-r--r-- 1 amanda amanda 2085650 May  9 14:48
> > amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > -rw-r--r-- 1 amanda amanda  140310 May  9 14:48
> > amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >
> > Those are a good sign too.
> >
> > root@coyote:amanda$ dpkg -i *.deb
> >
> > Selecting previously unselected package amanda-backup-client.
> > dpkg: regarding
> > amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > containing amanda-backup-client:
> >  amanda-backup-client conflicts with amanda-client
> >   amanda-client (version 1:3.3.9-5) is present and installed.
> >
> > dpkg: error processing archive
> > amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > (--install): conflicting packages - not installing
> > amanda-backup-client
> >
> >
> > One old package is still installed... and conflicts, so it needs a
> > 'dpkg -r amanda-client'.
> >
> > Selecting previously unselected package amanda-backup-client-dbgsym.
> > (Reading database ... 267815 files and directories currently
> > installed.) Preparing to unpack
> > amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > ... Unpacking amanda-backup-client-dbgsym
> > (3.5.1.git.19364c7b-1Debian99) ...
> >
> > Selecting previously unselected package amanda-backup-server.
> > dpkg: regarding
> > amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > containing amanda-backup-server:
> >  amanda-backup-server conflicts with amanda-client
> >   amanda-client (version 1:3.3.9-5) is present and installed.
> >
> > dpkg: error processing archive
> > amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > (--install): conflicting packages - not installing
> > amanda-backup-server
> >
> > Same problem, different attempt to install the server file instead
> > and it refused.
> >
> > Selecting previously unselected package amanda-backup-server-dbgsym.
> > Preparing to unpack
> > amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > ... Unpacking amanda-backup-server-dbgsym
> > (3.5.1.git.19364c7b-1Debian99) ... dpkg: error processing archive
> > amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> > (--install):
> >  trying to
> > overwrite
> > '/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a5.
> >de bug', which is also in package amanda-backup-client-dbgsym
> > 3.5.1.git.19364c7b-1Debian99
> >
> > Ahh... both the server and client packages can't be installed
> > together and the same would go for its debug files.
> >
> > May want to run 'dpkg -l | grep amanda' to see what's on there and
> > take off things that are old or that got in without cooperating yet.
> >
> > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> > dpkg: dependency problems prevent configuration of
> > amanda-backup-client-dbgsym:
> >  amanda-backup-client-dbgsym depends on amanda-backup-client (=
> > 3.5.1.git.19364c7b-1Debian99); however:
> >   Package amanda-backup-client is not installed.
> >
> > dpkg: error processing package amanda-backup-client-dbgsym
> > (--install): dependency problems - leaving unconfigured
> > Errors were encountered while processing:
> >  amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >  amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >  amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> >  amanda-backup-client-dbgsym
> >
> >
> > That seems to be the sum of it:  remove the old and install the
> > *backup-server*deb files only.
> >
> > The only amanda stuff was /usr/local/etc/amanda/DAILY copied from
> > the old disk to preserve my system, and about 20 files of the old
> > amanda install in /usr/local/lib/amanda, all dated from Jan 2017 so
> > they aren't precious now.  But all the old installs using amanda's
> > own Makefile, simply overwrote them instead of having a litter of
> > calves.
> >
> > Kittens, calves, or piglets ... package systems are more consistent
> > and complain if they leave their room messy.   Much more uptight ...
> > but then they get the job done with less guesswork.
> >
> > So I nuked what I could find of the january 2017 install the at may
> > have b

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Thursday 09 May 2019 04:35:40 pm Chris Hassell wrote:

> amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin
>
> That's what I have for amandabackup.  A no-frills-nothing and no
> password user.  Don't get why it can't be a dup of your other one. 
> Hrm
>
> Looks like the rest of the build was happy enough from the parts you
> gave.
>
> On 5/9/19 12:26 PM, Gene Heskett wrote:
>
>
> And, I'm looking at 4 debs:
> amanda@coyote:~/amanda$ ls -l *.deb
> -rw-r--r-- 1 amanda amanda 1298594 May  9 14:48
> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> -rw-r--r-- 1 amanda amanda  101638 May  9 14:48
> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> -rw-r--r-- 1 amanda amanda 2085650 May  9 14:48
> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> -rw-r--r-- 1 amanda amanda  140310 May  9 14:48
> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>
> Those are a good sign too.
>
> root@coyote:amanda$ dpkg -i *.deb
>
> Selecting previously unselected package amanda-backup-client.
> dpkg: regarding
> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb containing
> amanda-backup-client:
>  amanda-backup-client conflicts with amanda-client
>   amanda-client (version 1:3.3.9-5) is present and installed.
>
> dpkg: error processing archive
> amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
> (--install): conflicting packages - not installing
> amanda-backup-client
>
>
> One old package is still installed... and conflicts, so it needs a
> 'dpkg -r amanda-client'.
>
> Selecting previously unselected package amanda-backup-client-dbgsym.
> (Reading database ... 267815 files and directories currently
> installed.) Preparing to unpack
> amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb ...
> Unpacking amanda-backup-client-dbgsym (3.5.1.git.19364c7b-1Debian99)
> ...
>
> Selecting previously unselected package amanda-backup-server.
> dpkg: regarding
> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb containing
> amanda-backup-server:
>  amanda-backup-server conflicts with amanda-client
>   amanda-client (version 1:3.3.9-5) is present and installed.
>
> dpkg: error processing archive
> amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
> (--install): conflicting packages - not installing
> amanda-backup-server
>
> Same problem, different attempt to install the server file instead and
> it refused.
>
> Selecting previously unselected package amanda-backup-server-dbgsym.
> Preparing to unpack
> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb ...
> Unpacking amanda-backup-server-dbgsym (3.5.1.git.19364c7b-1Debian99)
> ... dpkg: error processing archive
> amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
> (--install):
>  trying to
> overwrite
> '/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a5.de
>bug', which is also in package amanda-backup-client-dbgsym
> 3.5.1.git.19364c7b-1Debian99
>
> Ahh... both the server and client packages can't be installed together
> and the same would go for its debug files.
>
> May want to run 'dpkg -l | grep amanda' to see what's on there and
> take off things that are old or that got in without cooperating yet.
>
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> dpkg: dependency problems prevent configuration of
> amanda-backup-client-dbgsym:
>  amanda-backup-client-dbgsym depends on amanda-backup-client (=
> 3.5.1.git.19364c7b-1Debian99); however:
>   Package amanda-backup-client is not installed.
>
> dpkg: error processing package amanda-backup-client-dbgsym
> (--install): dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
>  amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
>  amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
>  amanda-backup-client-dbgsym
>
>
> That seems to be the sum of it:  remove the old and install the
> *backup-server*deb files only.
>
> The only amanda stuff was /usr/local/etc/amanda/DAILY copied from the
> old disk to preserve my system, and about 20 files of the old amanda
> install in /usr/local/lib/amanda, all dated from Jan 2017 so they
> aren't precious now.  But all the old installs using amanda's own
> Makefile, simply overwrote them instead of having a litter of calves.
>
> Kittens, calves, or piglets ... package systems are more consistent
> and complain if they leave their room messy.   Much more uptight ...
> but then they get the job done with less guesswork.
>
> So I nuked what I could find of the january 2017 install the at may
> have been copied to the new drive.  Getting essentially the same
> message from
>
> dpkg -i *.deb
>
> WTH is wrong now?  Your turn Chris.
>
> That's what it is: cleaning is good but the meta-files (a database of
> what's in your linux system) have conflicts in them.  Clean up the old
> "amanda-cli

Re: Debian-based Amanda Build ... (revised)...

[Chris Hassell]

amandabackup:x:112:65534::/home/amandabackup:/usr/sbin/nologin

That's what I have for amandabackup.  A no-frills-nothing and no password user. 
 Don't get why it can't be a dup of your other one.  Hrm

Looks like the rest of the build was happy enough from the parts you gave.

On 5/9/19 12:26 PM, Gene Heskett wrote:


And, I'm looking at 4 debs:
amanda@coyote:~/amanda$ ls -l *.deb
-rw-r--r-- 1 amanda amanda 1298594 May  9 14:48
amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
-rw-r--r-- 1 amanda amanda  101638 May  9 14:48
amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
-rw-r--r-- 1 amanda amanda 2085650 May  9 14:48
amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
-rw-r--r-- 1 amanda amanda  140310 May  9 14:48
amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb

Those are a good sign too.

root@coyote:amanda$ dpkg -i *.deb

Selecting previously unselected package amanda-backup-client.
dpkg: regarding
amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb containing
amanda-backup-client:
 amanda-backup-client conflicts with amanda-client
  amanda-client (version 1:3.3.9-5) is present and installed.

dpkg: error processing archive
amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb (--install):
 conflicting packages - not installing amanda-backup-client


One old package is still installed... and conflicts, so it needs a 'dpkg -r 
amanda-client'.

Selecting previously unselected package amanda-backup-client-dbgsym.
(Reading database ... 267815 files and directories currently installed.)
Preparing to unpack
amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb ...
Unpacking amanda-backup-client-dbgsym (3.5.1.git.19364c7b-1Debian99) ...

Selecting previously unselected package amanda-backup-server.
dpkg: regarding
amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb containing
amanda-backup-server:
 amanda-backup-server conflicts with amanda-client
  amanda-client (version 1:3.3.9-5) is present and installed.

dpkg: error processing archive
amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb (--install):
 conflicting packages - not installing amanda-backup-server

Same problem, different attempt to install the server file instead and it 
refused.

Selecting previously unselected package amanda-backup-server-dbgsym.
Preparing to unpack
amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb ...
Unpacking amanda-backup-server-dbgsym (3.5.1.git.19364c7b-1Debian99) ...
dpkg: error processing archive
amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
(--install):
 trying to
overwrite 
'/usr/lib/debug/.build-id/06/a6d45701283ff745c5ea6b44c461817e1288a5.debug',
which is also in package amanda-backup-client-dbgsym
3.5.1.git.19364c7b-1Debian99

Ahh... both the server and client packages can't be installed together and the 
same would go for its debug files.

May want to run 'dpkg -l | grep amanda' to see what's on there and take off 
things that are old or that got in without cooperating yet.

dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
dpkg: dependency problems prevent configuration of
amanda-backup-client-dbgsym:
 amanda-backup-client-dbgsym depends on amanda-backup-client (=
3.5.1.git.19364c7b-1Debian99); however:
  Package amanda-backup-client is not installed.

dpkg: error processing package amanda-backup-client-dbgsym (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
 amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
 amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
 amanda-backup-client-dbgsym


That seems to be the sum of it:  remove the old and install the 
*backup-server*deb files only.

The only amanda stuff was /usr/local/etc/amanda/DAILY copied from the old
disk to preserve my system, and about 20 files of the old amanda install
in /usr/local/lib/amanda, all dated from Jan 2017 so they aren't
precious now.  But all the old installs using amanda's own Makefile,
simply overwrote them instead of having a litter of calves.

Kittens, calves, or piglets ... package systems are more consistent and 
complain if they leave their room messy.   Much more uptight ... but then they 
get the job done with less guesswork.

So I nuked what I could find of the january 2017 install the at may have
been copied to the new drive.  Getting essentially the same message from

dpkg -i *.deb

WTH is wrong now?  Your turn Chris.

That's what it is: cleaning is good but the meta-files (a database of what's in 
your linux system) have conflicts in them.  Clean up the old "amanda-client" 
(using dpkg or apt-get remove amanda-client) and you'll probably be in better 
shape to install the new again.

A minimal client-only system is great ... but you need a server system it 
seems.  One or the other, at least.

Copyright 2019 by Maurice E. Hesket

Re: Debian-based Amanda Build ... (revised)...

[Gene Heskett]

On Thursday 09 May 2019 12:50:08 pm Chris Hassell wrote:

> [oop.. left this email unsent yesterday]
>
> For those who were wondering.. I left out libglib2.0-dev and bison and
> flex.   Here's the revised instructions for a Debian-based 3.5 build.
>
> % sudo apt-get install ca-certificates xinetd perl gettext bsd-mailx
> dpkg-dev \ debhelper dump gnuplot-nox libtool mtx smbclient \
> libcurl4-gnutls-dev libncurses5-dev libreadline-dev libssl-dev \
> docbook-xsl swig xsltproc libglib2.0-dev bison flex
>
> % git clone git://github.com/zmanda/amanda.git
>
> % cd amanda
>
> % git checkout -b 3_5mine origin/3_5
>
> % bash autogen && ./packaging/deb/buildpkg
>
> It worked for Debian Stretch and Ubuntu 18.04.  I'm interested what
> older platforms fail, if some know of them?  Thanks.  (Note: this is
> for 3.5.1 only, in effect and I'll submit a pull request for trunk
> soon.)
>
> -- CH
Didn't quite work fore this debian stretch, close though.
Now, I did all the above as amanda, obtained by sudo -i
then su amanda.

I had a good sized tanker full of deprecated_declarations and if its 
still in the scroll-back, unused_functions. And lots of other noise that 
didn't look too serious, but I ended up with this:

# fix perms manually
chown -R amandabackup:disk debian/*/var/lib/*
chown: invalid user: ‘amandabackup:disk’
debian/rules:122: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit 
status 2

And indeed, there is no amandabackup user in this new install.

Took about 45 wall minutes, but next time I won't have to manually check 
all the installed bits.

So I ctl-d'd out of amanda, then adduser amandabackup, doing something I 
never had to do before, give amandabackup both a passwd and I see its 
also got /bin/bash for a shell, so there goes the security model by 
giving anybody who knows the amanda passwd a route into the machine, bad 
dog. without that its just an emasculated username, accessible only to 
root.  So be aware you may have to edit that crap back out 
of /etc/passwd.  But after doing the usreadd, and without that editing, 
I see the second stage of the build, making the deb, looks like its 
starting from scratch. But this time it finished up with this:

echo "Amanda version `cat FULL_VERSION`" 
>  
> /home/amanda/amanda/build/debian/amanda-backup-server//var/lib/amanda/amanda-release
echo "Amanda version `cat FULL_VERSION`" 
>  
> /home/amanda/amanda/build/debian/amanda-backup-client//var/lib/amanda/amanda-release
install -o root -g root -m 0644 debian/amanda-backup-client.lintian \

/home/amanda/amanda/build/debian/amanda-backup-client/usr/share/lintian/overrides/amanda-backup-client
install -o root -g root -m 0644 debian/amanda-backup-server.lintian \

/home/amanda/amanda/build/debian/amanda-backup-server/usr/share/lintian/overrides/amanda-backup-server
dh_makeshlibs  >> /home/amanda/amanda/build/debian/dpkg.log 2>&1
dh_perl >> /home/amanda/amanda/build/debian/dpkg.log 2>&1
dh_shlibdeps 
-l"/home/amanda/amanda/build/debian/tmp/usr/lib/x86_64-linux-gnu:/home/amanda/amanda/build/debian/amanda-backup-client/usr/lib/x86_64-linux-gnu:/home/amanda/amanda/build/debian/amanda-backup-server/usr/lib/x86_64-linux-gnu"
 
>> /home/amanda/amanda/build/debian/dpkg.log 2>&1
dh_installdeb >> /home/amanda/amanda/build/debian/dpkg.log 2>&1
dh_gencontrol >> /home/amanda/amanda/build/debian/dpkg.log 2>&1
dh_md5sums  >> /home/amanda/amanda/build/debian/dpkg.log 2>&1
dh_builddeb  >> /home/amanda/amanda/build/debian/dpkg.log 2>&1
 dpkg-genbuildinfo
 dpkg-genchanges  >../amanda_3.5.1.git.19364c7b-1Debian99_amd64.changes
dpkg-genchanges: info: including full source code in upload
 dpkg-source --after-build build
dpkg-buildpackage: info: full upload; Debian-native package (full source 
is included)

And, I'm looking at 4 debs:
amanda@coyote:~/amanda$ ls -l *.deb
-rw-r--r-- 1 amanda amanda 1298594 May  9 14:48 
amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb
-rw-r--r-- 1 amanda amanda  101638 May  9 14:48 
amanda-backup-client-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb
-rw-r--r-- 1 amanda amanda 2085650 May  9 14:48 
amanda-backup-server_3.5.1.git.19364c7b-1Debian99_amd64.deb
-rw-r--r-- 1 amanda amanda  140310 May  9 14:48 
amanda-backup-server-dbgsym_3.5.1.git.19364c7b-1Debian99_amd64.deb

Now the pen-ultimate test, failed.:

root@coyote:amanda$ dpkg -i *.deb
Selecting previously unselected package amanda-backup-client.
dpkg: regarding 
amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb containing 
amanda-backup-client:
 amanda-backup-client conflicts with amanda-client
  amanda-client (version 1:3.3.9-5) is present and installed.

dpkg: error processing archive 
amanda-backup-client_3.5.1.git.19364c7b-1Debian99_amd64.deb (--install):
 conflicting packages - not installing amanda-backup-client
Selecting previously unselected package amanda-backup-client-dbgsym.
(Reading database ... 267815 file