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:
<snip>
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<pid>" 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
