I have problem with the automatic udev rule. Back In Time created the following rule in /etc/udev/rules.d but whenever I plug in my device, I am not prompted for any password, nor is the backup process started automatically:
99-backintime-orschiro.rules:
ACTION=="add", ENV{ID_FS_UUID}=="2aac80d3-3f44-41dc-9f99-18f251d518dd", RUN+="/usr/bin/su - 'orschiro' -c 'test -x /usr/bin/anacron && test -e /root/.config/backintime/anacrontab-2aac80d3-3f44-41dc-9f99-18f251d518dd && /usr/bin/anacron -s -t /root/.config/backintime/anacrontab-2aac80d3-3f44-41dc-9f99-18f251d518dd -S /root/.local/share/backintime/anacron' &"
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.48 |
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 .. 33 34 35 36 37 38 39 40 41 42 43 .. 73 Next › Last »
orschiro commented on 2014-03-01 07:50 (UTC)
orschiro commented on 2014-02-26 15:23 (UTC)
@Germar
Thanks! I was so free to add this information to the wiki page:
https://wiki.archlinux.org/index.php/Back_In_Time
Germar commented on 2014-02-26 13:50 (UTC)
@orschiro you can use backintime-gnome as normal user even if you want to use udev schedule. BIT will ask for your sudo password to create udev rules.
You only need to run 'gksu backintime-gnome' if you want to backup/restore files which are only rw by root.
orschiro commented on 2014-02-26 10:53 (UTC)
Since the disabling of the keyring I am a bit confused how to launch backintime. For instance for some settings (such as creating the auto-backup udev rule) I need root permissions.What do you run?
~ backintime
~ backintime-gnome
~ gksudo backintime-gnome
~ gksu backintime-gnome
Thanks for shedding light!
orschiro commented on 2014-02-21 11:46 (UTC)
@zapataz
Then build the package manually and only install backintime-gtk/gnome
zapataz commented on 2014-02-21 11:39 (UTC)
@Orschiro
With Yaourt
orschiro commented on 2014-02-21 08:14 (UTC)
@zapataz
How did you build and try to install backintime?
Using an AUR helper?
zapataz commented on 2014-02-21 07:58 (UTC)
Hi,
Got package conflict error during build (below). I removed backintime-gnome references in PKGBUILD and it worked.
loading packages...
resolving dependencies...
looking for inter-conflicts...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: backintime-gnome and backintime-gtk are in conflict
graysky commented on 2014-02-17 20:17 (UTC)
@qqqq - Extra dependencies suck is the point. Germar mentioned that the next major release will drop the gtk/gnome flavor in favor of a qt GUI only. See his comment from 2013-12-19 20:20.
qqqqqqqqq9 commented on 2014-02-17 10:58 (UTC)
Hi,
what's the point of the backintime-gnome version (beside making it uninstallable by aur-helpers)? The only difference between backintime-gnome and backintime-gtk is gnome-session, which is not even installed during the build.
Couldn't you just make gnome-session an optdepend of backintime-gtk and drop backintime-gnome?
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.