@fukawi2 - Are you running gnome as your DE? I tried this under several users and I get the same error in each case. I just tried it on another machine running just lxde and it ends in the same error.
Opened a bug report with upstream since it seems to be more than just my single machine: https://bugs.launchpad.net/backintime/+bug/814271
Search Criteria
Package Details: backintime 1.5.2-1
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. Qt5 GUI version. |
Upstream URL: | https://github.com/bit-team/backintime |
Licenses: | GPL |
Submitter: | None |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 296 |
Popularity: | 0.47 |
First Submitted: | 2009-01-09 20:46 (UTC) |
Last Updated: | 2024-08-07 19:55 (UTC) |
Dependencies (11)
- backintime-cliAUR (backintime-cli-gitAUR)
- libnotify (libnotify-gitAUR)
- polkit (polkit-gitAUR, polkit-consolekitAUR)
- python-dbus
- python-pyqt6
- sshfs
- xorg-xdpyinfo
- python (python37AUR, python311AUR, python310AUR) (make)
- kompare (kompare-gitAUR) (optional) – diff/patch frontend
- meld (meld-gitAUR) (optional) – diff/patch frontend
- qt6-translations (optional) – translate BIT dialogs into native language
Required by (1)
- backintime-cli (optional)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 63 64 65 66 67 68 69 70 71 72 73 Next › Last »
graysky commented on 2011-07-21 20:30 (UTC)
altkrall commented on 2011-07-21 18:51 (UTC)
I also get the error of graysky. How can I repair this?
fukawi2 commented on 2011-07-21 10:31 (UTC)
Nope, WFM:
$ gksu backintime-gnomeINFO: Update to config version 4: other snapshot locations
INFO: Random tag for profile 1: 506
INFO: Update to config version 5: other snapshot locations
Back In Time
Version: 1.0.7
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.
which: no gloobus-preview in (/usr/lib/cw:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/java/bin:/opt/java/db/bin:/opt/java/jre/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/lib/perl5/vendor_perl/bin:/usr/bin/core_perl:~/bin/:/usr/local/bin:/usr/local/sbin:/usr/local/usr/bin/)
graysky commented on 2011-07-21 08:31 (UTC)
fukawi2 - seems broken for me, can you confirm:
$ gksu backintime-gnome
Traceback (most recent call last):
File "/usr/share/backintime/gnome/app.py", line 33, in <module>
import gnome
File "/usr/lib/python2.7/site-packages/gtk-2.0/gnome/__init__.py", line 13, in <module>
from _gnome import *
ImportError: /usr/lib/libgnomevfs-2.so.0: undefined symbol: gcry_control
fukawi2 commented on 2011-07-11 03:39 (UTC)
Whoops, you are correct. My apologies, and fixed in pkgrel 2:
https://github.com/fukawi2/aur-packages/commit/a6be1e3d086a019a260de37d796bd315360489f2
leonardof commented on 2011-07-11 03:08 (UTC)
@fukawi2: Indeed, having the dep set tp 'cron' would allow us to use any cron package, but it is set to 'dcron'. Would you please set it to 'cron' instead? Thanks!
fukawi2 commented on 2011-06-26 23:12 (UTC)
Bump to 1.0.8
* Fix bug: https://bugs.launchpad.net/backintime/+bug/723545
* Fix bug: https://bugs.launchpad.net/backintime/+bug/705237
* Fix bug: https://bugs.launchpad.net/backintime/+bug/696663
* Fix bug: https://bugs.launchpad.net/backintime/+bug/671946
fukawi2 commented on 2011-05-16 22:59 (UTC)
'cronie' provides 'cron' so having the dep set to 'cron' allows you to use any cron packages (assuming the packager has correctly set the 'provides' array to include 'cron')
<deleted-account> commented on 2011-05-16 14:13 (UTC)
Could you change the dependencies to:
depends=( 'python2' 'rsync' 'cron' )
because cronie is now in core and i wouldn't like to install dcron. Or is there any reason why backintime won't work with cronie?
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.