You are not logged in.
I was a little surprised to find that Holland Backup wasn't already in a repo, so last night I cranked out some packages, today my Arch coworkers peer reviewed them (disclaimer: I work with Holland RPM packagers for EPEL and the coders of Holland) and I've updated the packages with some minor fixes:
https://aur.archlinux.org/packages/holland/
If you're still rolling your own MySQL or PostgreSQL backups as a Sysad, you need to stop and let Holland do it all for you.
If you're unfamiliar with Holland and want to ask some questions about it, please fire away - it's an incredible little piece of python software that solves a ton of DB backup problems we face as sysads. I added a wee blurb about it on the MySQL wiki page as well.
I tested them last night against the mainline MariaDB 10 and PostgreSQL 9.3 pacman installs, and confirm that mysqldump, mysqllvm, mysqldump-lvm, xtrabackup and pgdump child packages are all functioning as expected on vanilla DB setup.
Offline
Not a Sysadmin issue, moving to the AUR board...
Offline
TE,
The package_holland has BSD as license, and you're putting it in the wrong place.
it should be put in /usr/share/licenses/$pkgname , see Arch_packaging_standards#Licenses
(for the GPL2 parts of the code you don't need to copy the license, as the GPL2 license is already present in /usr/share/licenses/common/GPL2/ ).
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Thanks, adjusted - I did not realize BSD wasn't a common license.
Offline
BSD license is a special case, as everything released under it needs a custom copyright line.
I've looked into the holland-1.0.10/LICENSE file and it actually lists 2 licenses .
Both are 3-clause BSD , but they differ in the copyright line.
That means that archlinux needs to regard each BSD license as a unique license.
Last edited by Lone_Wolf (2014-12-14 14:17:36)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online