Package Base Details: backintime

Git Clone URL: (read-only, click to copy)
Submitter: None
Maintainer: graysky
Last Packager: graysky
Votes: 272
Popularity: 0.78
First Submitted: 2009-01-09 20:46
Last Updated: 2019-08-25 17:21

Packages (2)

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 11 12 13 14 ... Next › Last »

Germar commented on 2015-09-12 00:24

@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

@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

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

nielsvd commented on 2015-09-07 20:22

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!

graysky commented on 2015-09-02 18:10

gksu is no longer required for root access; the preferred method is using pkexec.

coderkun commented on 2015-09-02 12:05

Running backintime as root works under Gnome running
$ export QT_X11_NO_MITSHM=1
$ gksu backintime-qt4


graysky commented on 2015-08-22 17:11

@willemw - So it has, thanks. Updated.

willemw commented on 2015-08-22 16:39

Package 'kdesdk-kompare' has been renamed to 'kompare'.

finswimmer commented on 2015-08-19 12:12

I have the same problem. Running backintime-qt4 as root only shows empty windows.

arm1e commented on 2015-08-06 08:27

I am also having these errors when trying to start the root version. Blank windows if done from terminal and nothing starts at all when using the menu icon in gnome. Are there any known fixes yet?