@graysky: Is it possible that backintime with KDE requires kdebindings-python2 instead of kdebindings-python? Because as far as I know, backintime uses python2, and I needed to install kdebindings-python2 in order to avoid this error on startup:
$ backintime-kde4 Traceback (most recent call last):
File "/usr/share/backintime/kde4/app.py", line 44, in <module>
from PyKDE4.kdecore import *
ImportError: No module named kdecore
Thanks a lot for checking :-)
Search Criteria
Package Details: backintime-cli 1.5.3-2
Package Actions
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.16 |
First Submitted: | 2009-01-09 20:46 (UTC) |
Last Updated: | 2024-11-13 15:34 (UTC) |
Dependencies (8)
- cron (scron-gitAUR, vixie-cronAUR, busybox-crondAUR, mcronAUR, dcronAUR, dcron-gitAUR, cronie-selinuxAUR, systemd-cron-next-gitAUR, systemd-cronAUR, cronie, fcron)
- openssh (openssh-gitAUR, openssh-dotconfigAUR, openssh-dotconfig-binAUR, openssh-selinuxAUR, openssh-hpn-shimAUR, openssh-gssapiAUR)
- python-dbus
- python-keyring
- python-packaging
- rsync (rsync-gitAUR, rsync-reflinkAUR, rsync-reflink-gitAUR)
- python (python37AUR, python311AUR, python310AUR) (make)
- backintimeAUR (backintime-gitAUR) (optional) – Qt6 GUI version
Required by (1)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 48 49 50 51 52 53 54 55 56 57 58 .. 73 Next › Last »
firun commented on 2013-10-06 10:11 (UTC)
graysky commented on 2013-10-05 19:57 (UTC)
Bump to v1.0.26-4
Changelog: Added a versioned requirement to python2-keyring to keep users from updating to 3.0.5 which FUBR's backintime. A bug report is active upstream concerning this issue.[1]
Commit: http://pkgbuild.com/git/aur-mirror.git/commit/backintime?id=0f8175e5181ead95137030a7d26fe00c5ec6062d
1. https://bugs.launchpad.net/backintime/+bug/1234024
graysky commented on 2013-10-05 14:51 (UTC)
Yes, the update of python2-keyring from 1.6.1-1 -> 3.0.5-1 has fubr'ed backintime. I can repeat this on my gtk setup after updated that package.
There is an open bug report against this upstream.[1]
1. https://bugs.launchpad.net/backintime/+bug/1234024
% backintime-gnome
Back In Time
Version: 1.0.26
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.
Traceback (most recent call last):
File "/usr/share/backintime/gnome/app.py", line 1280, in <module>
main_window = MainWindow( cfg, app_instance )
File "/usr/share/backintime/gnome/app.py", line 333, in __init__
mnt = mount.Mount(cfg = self.config, profile_id = profile_id, parent = self.window)
File "/usr/share/backintime/common/mount.py", line 52, in __init__
pw_cache = password.Password_Cache(self.config)
File "/usr/share/backintime/common/password.py", line 265, in __init__
self.keyring_supported = tools.set_keyring(backend)
File "/usr/share/backintime/common/tools.py", line 505, in set_keyring
backends = (keyring.backend.GnomeKeyring(), keyring.backend.KDEKWallet())
AttributeError: 'module' object has no attribute 'GnomeKeyring'
ArchGiac commented on 2013-10-05 13:43 (UTC)
@orschiro
Thanks, but it did not work!
Gnome Keyring is started:
###> ps ax | grep gnome
660 ? Sl 0:00 /usr/bin/gnome-keyring-daemon --start --components=pkcs11
1351 pts/1 S+ 0:00 grep gnome
orschiro commented on 2013-10-05 11:31 (UTC)
@ArchGiac
Could it be that also on KDE you need the Gnome Keyring?
Does that help?
http://www.jfdesignnet.com/?p=2731
ArchGiac commented on 2013-10-05 11:28 (UTC)
After last update, I have this bug:
backintime -b
Back In Time
Version: 1.0.26
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.
INFO: Lock
Traceback (most recent call last):
File "/usr/share/backintime/common/backintime.py", line 388, in <module>
start_app()
File "/usr/share/backintime/common/backintime.py", line 171, in start_app
take_snapshot( cfg, True )
File "/usr/share/backintime/common/backintime.py", line 53, in take_snapshot
snapshots.Snapshots( cfg ).take_snapshot( force )
File "/usr/share/backintime/common/snapshots.py", line 887, in take_snapshot
hash_id = mount.Mount(cfg = self.config).mount()
File "/usr/share/backintime/common/mount.py", line 52, in __init__
pw_cache = password.Password_Cache(self.config)
File "/usr/share/backintime/common/password.py", line 265, in __init__
self.keyring_supported = tools.set_keyring(backend)
File "/usr/share/backintime/common/tools.py", line 505, in set_keyring
backends = (keyring.backend.GnomeKeyring(), keyring.backend.KDEKWallet())
AttributeError: 'module' object has no attribute 'GnomeKeyring'
Info:
Arch i686
Kernel 3.11.3
Kde 4.11.2
Danyright commented on 2013-10-03 14:05 (UTC)
Thanks for fixing the issue :-)
Works fine for me too (kde4).
graysky commented on 2013-10-02 23:17 (UTC)
Bump to v1.0.26-3
Changelog: Added kde4 fix.
Commit: http://pkgbuild.com/git/aur-mirror.git/commit/backintime?id=bead457945e3ad95bfd6a334f3178375fa1678bd
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.