TOP NOTES: Make a build and the .deb files.
1. Maybe remove the 'amanda' or 'amandabackup' user and its home directories (any). Remove it from the /etc/passwd as well. The /var/lib/amanda is the *normal* home directory but has no config in there.. so it should go too. 2. Don't add it back ... or if you must add it (if you know its UID was set to 63998 as is the necessary default) use: $ sudo useradd -c "Amanda" -g <amanda_group> -u 63998 -d /var/lib/amanda -s /bin/bash amanda 3. Try installing the packages *then*. If that doesn't work, remove the packages again and then run this separately (if something failed and you're not sure why): % bash -xv ./packaging/deb/preinst Not sure. But that's what *should* succeed and make the user on its own. You may need to check everything *everywhere* in /etc/amanda and /var/log/amanda and /var/lib/amanda etc.. etc... is changed over to the new user (because the uid# is the *real* presence of a user... not the stringy name). Use "dpkg -V amanda-backup-server" and I think it'll check the ownership/validity of the install. Remember .. the server has both server and client binaries .. so its what you want. On 5/11/19 9:32 AM, Gene Heskett wrote: Despite changing the name in the rules file, its hard coded to be amanda-backup in the .dsc files. GRRRRRRR The .dsc file is (I believe) from the Debian build process. Whatever user you have, it will find one name to describe the file owners. If you have amandabackup and amanda both in your /etc/passwd ... it can pick either one as a valid choice.\ I don't run Debian-based at home so I can't tell right now what it looks like. I know that if it's changed within every file in packaging/deb/... then it's changed for all new builds. Make sure to run a "git clean -d -f" before a build to start clean. Nothing works if you have the last-used-user spread all hither and yon and change it upstream in one place. Without fixing this, how the hell do we get rid of the older version trash when updateing it? Seems like a heck of a good question to me. Do we expect the users to wear out find in cleaning house file by file? I think not. The only files (in the repo) that mention amandabackup ... are entirely within packaging/... This was amanda for 2 decades before some marketing type decreed a name change. What was this person thinking? Confusion. I've no idea but many names all identical are kind confusing. Some folks *may* even have a young or old lady using a machine named 'amanda'? Changes are the norm. Static stuff is rare... except bugs live there too Anyway, I blew that whole /home/amanda/amanda directory away an started with becoming amanda, then a fresh git clone from github. Then did exactly as said. It builds 5 packages. so I attempt to install the amanda-backup-server since this machine is the server. I still don't get that *anything* is good about having the amanda user or building-with-amanda. I'm worried its your problem there? Take it or leave it .. but things haven't worked smoothly yet. And its stuck, just like the previous attempt. No cpu used, no progress. pstree does show but one process, but htop shows 5, with the highest pid being from gnupg getting a no-permissions from /var/lib/amanda. An ls -l of that dir is: What process was it? (May need to use pstree -phul to see everything). amanda@coyote:..$<mailto:amanda@coyote:..$> ls -l /var/lib/amanda total 16 -rw-r--r-- 1 root root 34 May 11 09:59 amanda-release -rw-r--r-- 1 backup backup 0 May 6 10:51 amandates drwxr-xr-x 3 amandabackup disk 4096 May 11 11:01 example drwxrwx--- 2 amandabackup disk 4096 May 11 09:59 gnutar-lists drwxr-xr-x 2 amandabackup disk 4096 May 11 11:01 template.d That's amanda's home directory, by default. One should try running the build with no packages installed and no amanda user in place. And that directory is owned by backup. And I'm lost, and I need to go convince a winders 10 home edition that I am indeed boss. I can't even get it online. Need a manpage for netfs. Thanks Chris, but its Your turn. That's all I have for right now. Some of these pre-post install scripts could be more clear and block an install (with a reason why) to help everyone get success sometime without guesswork. Cheers, Gene Heskett
