Search Criteria
Package Details: btrbk 0.32.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/btrbk.git (read-only, click to copy) |
---|---|
Package Base: | btrbk |
Description: | Backup tool for btrfs subvolumes, taking advantage of btrfs specific capabilities to create atomic snapshots and transfer them incrementally to your backup locations |
Upstream URL: | https://digint.ch/btrbk |
Licenses: | GPL3 |
Conflicts: | btrbk-git |
Submitter: | myles |
Maintainer: | akurei |
Last Packager: | akurei |
Votes: | 53 |
Popularity: | 0.140789 |
First Submitted: | 2015-03-29 11:35 (UTC) |
Last Updated: | 2022-03-01 11:23 (UTC) |
Dependencies (5)
- btrfs-progs (btrfs-progs-git)
- perl (perl-git)
- asciidoctor (make)
- mbuffer (optional) – --progress support and add buffering to send-stream
- openssh (openssh-hpn-git, openssh-git, openssh-gssapi, openssh-xdg-git, openssh-dotconfig, openssh-selinux, openssh-hpn-shim) (optional) – remote backup support,
Latest Comments
Omar007 commented on 2022-03-13 12:08 (UTC) (edited on 2022-03-13 12:09 (UTC) by Omar007)
The
conflicts=('btrbk-git')
line should be removed (if putting a conflict anywhere it should be on the VCS version of a package instead, with a conflict on the non-VCS variant).Also, maybe add
optdepends=('sudo: support for the btrfs-progs-sudo backend')
?akurei commented on 2021-10-04 11:31 (UTC)
@willemw Thank you, removed.
willemw commented on 2021-10-02 08:47 (UTC)
Please remove "conflicts=('btrbk-git')" according to the guidelines ("... you do not need to specify that conflicting package in your conflicts array").
akurei commented on 2021-09-14 07:53 (UTC)
@MountainX No, sorry. Don't know if they exist. It would be great if those landed upstream. If not, another AUR package would probably the better solution (btrbk-pacman-hooks) or something akin.
willemw commented on 2021-08-07 20:44 (UTC)
conflicts=('btrbk-git') is not necessary.
MountainX commented on 2020-12-11 20:32 (UTC)
@akurei thank you for maintaining this package. Do you know if any pacman hooks exist for btrbk that could replace Arch Linux - snap-pac 2.3.1-2 (any)? If they don't exist, I volunteer to help someone create & test them.
akurei commented on 2020-09-30 08:14 (UTC)
Fixed here. As soon as upstream releases a fix I will adapt the PKGBUILD again. Thanks @xiretza @Kr1ss
simon04 commented on 2020-09-28 19:03 (UTC)
The package should therefore specify
otions=(!makeflags)
. Citing from PKGBUILD(5), "More useful in its negative form !makeflags with select packages that have problems building with custom makeflags such as -j2 (or higher)."Kr1ss commented on 2020-09-28 14:55 (UTC)
Thank you for the quick response !
xiretza commented on 2020-09-28 14:54 (UTC)
Submitted an upstream patch for the problem mentioned by @Kr1ss at https://github.com/digint/btrbk/pull/341, but until a new patch release comes out,
make -j1
inpackage()
is probably the best solution.Kr1ss commented on 2020-09-28 14:31 (UTC) (edited on 2020-09-28 14:38 (UTC) by Kr1ss)
Hey @akurei, thx a lot for maintaining the package, and for the recent update !
While building, I noticed there is a race condition occuring occasionally when
make
is configured to use multithreading, leading to an errorThis points to the symlink being attempted before the
$pkgdir/usr/bin
folder has been created.So, would you consider either
options=('!makeflags')
, ormake install
command withMAKEFLAGS+=' -j1'
TIA, Cheers !
PS By the way, the
BINDIR="/usr/bin"
is no longer necessary, since the application will now be installed to that location by default. :)akurei commented on 2019-07-29 06:28 (UTC)
Updated to 0.28.3
getzze commented on 2018-06-26 15:07 (UTC)
I could not make it work without the
mbuffer
dependency, which is optional since version 0.25.1 (https://github.com/digint/btrbk/issues/154). Can you maybe add it in 'optdepends': 'mbuffer: add buffering to send-stream'akurei commented on 2017-10-29 16:36 (UTC)
kbabioch commented on 2017-10-28 18:55 (UTC)
akurei commented on 2017-07-30 20:42 (UTC)
akurei commented on 2017-04-03 10:18 (UTC)
akurei commented on 2016-11-21 18:02 (UTC)
akurei commented on 2016-06-04 00:32 (UTC)
puithove commented on 2016-05-02 11:55 (UTC)
derhamster commented on 2015-09-07 08:08 (UTC)
TH3L0N3W0LF commented on 2015-09-06 16:22 (UTC)
derhamster commented on 2015-09-06 08:41 (UTC)
TH3L0N3W0LF commented on 2015-09-05 20:13 (UTC)
derhamster commented on 2015-09-05 20:00 (UTC)