You are not logged in.
Hello,
I originally added this as a comment on the bacula package group itself but I'm not sure if that was an appropriate place for this.
https://aur.archlinux.org/pkgbase/bacula/?comments=all
Anyway, if I try to install aur/bacula-common I get this:
error: failed to commit transaction (conflicting files)
/usr/lib/libbaccats-7.0.3.so exists in both 'bacula-dir-mariadb' and 'bacula-dir-postgresql'
/usr/lib/libbaccats-7.0.3.so exists in both 'bacula-dir-mariadb' and 'bacula-dir-sqlite3'
/usr/lib/libbaccats-7.0.3.so exists in both 'bacula-dir-postgresql' and 'bacula-dir-sqlite3'
Errors occurred, no packages were upgraded.
No /usr/lib/libbac* exists on my computer and querying pacman shows that I have no bacula components installed. This seems to be an issue with the package itself.
I'm also getting a failing PGP signature for aur/bacula-client.
Suggestions? Thanks.
Last edited by khouli (2015-01-10 14:16:29)
Offline
Not a Pacman issue, moving to AUR Issues...
Offline
The package splits to multiple packages; it seems you would be fine if you choose from -postgresql, mariadb and sqlite3 to install; the message indicates you are currently installing all of them. Are you using some sort of helper?
Offline
I'm using yaourt. I get this error even if I try installing exactly one package and even if it isn't one of the bacula-dir-dbms packages.
E.g.
$ yaourt bacula
1 aur/bacula-bat 7.0.5-1 (29)
Bacula - A Network Backup Tool (management GUI)
2 aur/bacula-client 7.0.5-1 (31)
A network backup tool for Linux, Unix, Mac and Windows. This is the client edition.
3 aur/bacula-client-compat 5.2.13-1 (0)
A network backup tool for Linux, Unix, Mac and Windows. This is the client edition for users experiencing incompatibilities with older Bacula Directors.
4 aur/bacula-common 7.0.5-1 (29)
Bacula - A Network Backup Tool (common files)
5 aur/bacula-console 7.0.5-1 (29)
Bacula - A Network Backup Tool (management CLI)
6 aur/bacula-dir 7.0.5-1 (29)
Bacula - A Network Backup Tool (Director)
7 aur/bacula-dir-mariadb 7.0.5-1 (29)
Bacula - A Network Backup Tool (Director - MariaDB support)
8 aur/bacula-dir-mysql 7.0.5-1 (29)
Bacula - A Network Backup Tool (transition package)
9 aur/bacula-dir-postgresql 7.0.5-1 (29)
Bacula - A Network Backup Tool (Director - PostgreSQL support)
10 aur/bacula-dir-sqlite3 7.0.5-1 (29)
Bacula - A Network Backup Tool (Director - SQLite3 support)
11 aur/bacula-fd 7.0.5-1 (29)
Bacula - A Network Backup Tool (file daemon)
12 aur/bacula-postgresql 5.2.13-4 (12)
An advanced backup tool with network and tape changer support (PostgreSQL backend)
13 aur/bacula-sd 7.0.5-1 (29)
Bacula - A Network Backup Tool (Storage Daemon)
==> Enter n° of packages to be installed (ex: 1 2 3 or 1-3)
==> -------------------------------------------------------
==> 4[ lots of output ]
==> Edit PKGBUILD ? [Y/n] ("A" to abort)
==> ------------------------------------
==> n
==> WARNING: This PKGBUILD describes a splitted package.
==> Specific package options are unknown
==> bacula dependencies:
- tcp_wrappers (already installed)
- sqlite (already installed)
- libmariadbclient (already installed)
- postgresql-libs (already installed)
- qt4 (already installed)
==> Continue building bacula-common ? [Y/n]
==> ---------------------------------------
==> y[ tons more output ]
==> Continue installing bacula ? [Y/n]
==> [v]iew package contents [c]heck package with namcap
==> ---------------------------------------------------
==> y
loading packages...
resolving dependencies...
looking for conflicting packages...
Packages (10) bacula-bat-7.0.5-1 bacula-common-7.0.5-1 bacula-console-7.0.5-1 bacula-dir-7.0.5-1 bacula-dir-mariadb-7.0.5-1 bacula-dir-mysql-7.0.5-1
bacula-dir-postgresql-7.0.5-1 bacula-dir-sqlite3-7.0.5-1 bacula-fd-7.0.5-1 bacula-sd-7.0.5-1
Total Installed Size: 5.24 MiB
:: Proceed with installation? [Y/n] y
(10/10) checking keys in keyring [#################################################################] 100%
(10/10) checking package integrity [#################################################################] 100%
(10/10) loading package files [#################################################################] 100%
(10/10) checking for file conflicts [#################################################################] 100%
error: failed to commit transaction (conflicting files)
/usr/lib/libbaccats-7.0.3.so exists in both 'bacula-dir-mariadb' and 'bacula-dir-postgresql'
/usr/lib/libbaccats-7.0.3.so exists in both 'bacula-dir-mariadb' and 'bacula-dir-sqlite3'
/usr/lib/libbaccats-7.0.3.so exists in both 'bacula-dir-postgresql' and 'bacula-dir-sqlite3'
Errors occurred, no packages were upgraded.In the last portion you can see that multiple bacula backends are being installed. I don't know why.
Last edited by khouli (2015-01-04 15:00:44)
Offline
Stop using yaourt to build it. Multiple backends are being installed because yaourt is really stupid when dealing with split packages.
Offline
I installed the bacula backend components by hand and that went fine but I still get a PGP error for the bacula client. I tried a pacman-key --refresh-keys but it didn't help.
Last edited by khouli (2015-01-04 18:51:34)
Offline
Offline
After reading that over and locally signing the bacula key I still get the same error.
$ makepkg -s
==> Making package: bacula-client 7.0.5-1 (Sun Jan 4 15:37:21 EST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found bacula-7.0.5.tar.gz
-> Found bacula-7.0.5.tar.gz.sig
-> Found bacula-fd.service
==> Validating source files with sha256sums...
bacula-7.0.5.tar.gz ... Passed
bacula-7.0.5.tar.gz.sig ... Skipped
bacula-fd.service ... Passed
==> Verifying source file signatures with gpg...
bacula-7.0.5.tar.gz ... FAILED (unknown public key 9E98BF3210A792AD)
==> ERROR: One or more PGP signatures could not be verified!I'm not sure how to determine what PGP keys I need to sign for an AUR package. I just tried what was in the error message.
$ sudo pacman-key -f 9E98BF3210A792AD
pub dsa1024/10A792AD 2003-06-08
Key fingerprint = 2CA9 F510 CA5C CAF6 1AB5 29F5 9E98 BF32 10A7 92AD
uid [ full ] Bacula Distribution Verification Key (www.bacula.org)
sub elg2048/E7ADEDF1 2003-06-08Looks legit.
$ sudo pacman-key --recv-key 9E98BF3210A792AD
gpg: key 10A792AD: "Bacula Distribution Verification Key (www.bacula.org)" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
==> Updating trust database...
gpg: next trustdb check due at 2016-01-22The blog post link gave the flag in this step as "--lsign" while the arch wiki and pacman-key manpage have "--lsign-key". Both seem to do the same thing.
$ sudo pacman-key --lsign-key 9E98BF3210A792AD
-> Locally signing key 9E98BF3210A792AD...
==> Updating trust database...
gpg: next trustdb check due at 2016-01-22$ makepkg -s
[same PGP error as above]Offline
No. Don't add random keys to pacman's keychain: that was the whole point of Allan's post.
Offline
Oh, I get it now. I set up a user gpg, added the bacula key to it, and removed the bacula key from pacman. makepkg then completed.
pacman won't install the bacula-client because it has file conflicts with files owned by the bacula server components. Looking at the PKGBUILD for bacula-client, there is a line that reads
conflicts=("bacula")I think this means that there's no need to install bacula-client on a machine that has the bacula server on it (which are in split package "bacula") because bacula-client is a subset. If someone could verify that this sounds reasonable then that solves all my issues.
Offline