Package Details: backintime-cli 1.5.3-2

Git Clone URL: https://aur.archlinux.org/backintime.git (read-only, click to copy)
Package Base: backintime
Description: Simple backup system inspired from the Flyback Project and TimeVault. CLI version.
Upstream URL: https://github.com/bit-team/backintime
Licenses: GPL
Submitter: None
Maintainer: graysky
Last Packager: graysky
Votes: 299
Popularity: 2.20
First Submitted: 2009-01-09 20:46 (UTC)
Last Updated: 2024-11-13 15:34 (UTC)

Pinned Comments

graysky commented on 2023-10-07 12:15 (UTC)

Using an AUR helper such as yay to build packages including backintime is HIGHLY discouraged. The recommended build method is to use a clean chroot. See: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

I wrote a script that automates much of that called clean-chroot-manager offered here in the AUR.

Please stop posting build failures because you insist on building with yay or other AUR helpers.

Latest Comments

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 73 Next › Last »

catalin.hritcu commented on 2015-12-13 17:29 (UTC)

These are the 2 patches I applied *by hand*: https://github.com/bit-team/backintime/commit/d7b28fa8f1f124e2e13ad9345b60c61110841485 https://github.com/bit-team/backintime/commit/9ae4960f4dca6092d3b636a3b6def68220b50a7e

graysky commented on 2015-12-13 17:25 (UTC)

@cat - Which patches did you apply and were they to 1.1.8? The two I found do not cleanly apply.

catalin.hritcu commented on 2015-12-13 16:39 (UTC) (edited on 2015-12-13 17:35 (UTC) by catalin.hritcu)

Was getting following error on starting up as user: [hritcu@detained ~]$ Traceback (most recent call last): File "/usr/share/backintime/common/backintime.py", line 23, in <module> import config File "/usr/share/backintime/common/config.py", line 31, in <module> import configfile File "/usr/share/backintime/common/configfile.py", line 19, in <module> import logger File "/usr/share/backintime/common/logger.py", line 23, in <module> import tools File "/usr/share/backintime/common/tools.py", line 1173, in <module> logger.warning('import keyring failed') AttributeError: module 'logger' has no attribute 'warning' Locally applying the 2 patches from issue #473 fixed it for me. https://github.com/bit-team/backintime/issues/473 Wondering whether you can include those patches in your package until v1.1.10 comes out. Tool not starting at all seems like a big enough problem for regular users.

graysky commented on 2015-09-29 19:01 (UTC)

Bump to v1.1.8-1

<deleted-account> commented on 2015-09-13 10:44 (UTC)

Solides Programm, nutze es schon sehr lange und läuft sauber- Weiter so!

graysky commented on 2015-09-12 11:09 (UTC)

@tahayassen - validpgpkeys= is the Arch standard not just for the AUR but for all packages. Suggest you read the wiki: https://wiki.archlinux.org/index.php/Makepkg#Signature_checking

Germar commented on 2015-09-12 00:24 (UTC)

@tahayassen AFAIK this is a new directive for AUR Packages to make sure you won't install packages which where manipulated by a man in the middle. Maybe the Arch folks can explain this better. I'm just the Dev of BackInTime and have only little experience with Arch...

tahayassen commented on 2015-09-11 23:40 (UTC)

@Germar Why does this package require a separate key? If everyone did this, using the AUR would be quite inconvenient since we'd have to add keys for each package we want to install.

Germar commented on 2015-09-08 17:17 (UTC)

@nielsvd this was answered several times below. You need to run gpg --keyserver pgp.mit.edu --recv-keys 615F366D944B4826 once to add my key.

nielsvd commented on 2015-09-07 20:22 (UTC)

Installer is not working: ==> Verifying source file signatures with gpg... backintime-1.1.6.tar.gz ... FAILED (unknown public key 615F366D944B4826) ==> ERROR: One or more PGP signatures could not be verified!