@ottomops and @orschiro
this is because BIT is using 'Auto Host/User/ProfileID' (General Settings below Advanced) by default and 'User' now changed to 'root' (how it should be). But your existing profile was configured with User 'orschiro' or 'ottomops' or whatever your normal user is called.
I'd suggest to keep 'gksudo' but manually deactivate 'Auto Host/User/ProfileID' and change 'User' back to your normal users name. Or alternative rename the snapshot folder '/path/to/backintime/<HOST>/<USER>' into '/path/to/backintime/<HOST>/root' if there are only snapshots for root inside.
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.20 |
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 .. 32 33 34 35 36 37 38 39 40 41 42 .. 73 Next › Last »
Germar commented on 2014-03-04 14:08 (UTC)
orschiro commented on 2014-03-04 12:57 (UTC)
@Germar
I can confirm what ottomops says. My previously made backups are not longer recognised. Though now I can successfully create the udev rule.
So what is the optimal solution? gksu or gksudo?
ottomops commented on 2014-03-04 09:21 (UTC)
Since using gksudo my backup folder is not recognized anymore by backintime. Changing the starter back to gksu fixed it for me. So I would vote for going back to gksu.
graysky commented on 2014-03-03 21:10 (UTC)
Bump to v1.0.34-3
Changelog: Per Garmar's request, modified gnome/gtk .desktop file to use gksudo rather than gksu.
Germar commented on 2014-03-03 13:03 (UTC)
@orschiro
You are already root because of "gksu backintime-gnome". That's why you are not asked for your root pw again.
I just found out that Arch gksu behave different than Debian gksu. "gksu env | grep -e '^USER=\|^LOGNAME='" should print root for both but on Arch it will print orschiro which causes your problems. Using "gksudo backintime-gnome" instead should solve this.
@graysky
Could you please change 'gnome/backintime-gnome-root.desktop' to use 'gksudo'?
orschiro commented on 2014-03-03 05:52 (UTC)
@Germar
When you said that something is wrong with my user, I deleted the udev rule and started from scratch. I launched `gksu backintime-gnome` and tried to recreate the udev rule. I selected Schedule: When drive gets connected.
But then I get the error: `Failed to create udev rules`
The CLI output:
Profile: Arch Linux System
Automatic backup: When drive get connected (udev)
Command "gksudo -m "Please provide your sudo password to install the udev rule." -- cp "/tmp/tmpFn8HNV" "/etc/udev/rules.d/99-backintime-orschiro.rules"" returns 256
That is, I am not asked for my root password.
qqqqqqqqq9 commented on 2014-03-03 00:32 (UTC)
Thanks for clearing it up that it's all about teaching us not to use AUR-Helpers and run makepkg by hand. An Optdepend wouldn't suck at all, the only "harm" it would do is an additional line being printed out during installation.
Germar commented on 2014-03-02 17:04 (UTC)
@orschiro
There is something wrong with the user in that udev rule (/usr/bin/su - 'orschiro' [...] vs. /root/.config[...]). It should be either 'orschiro' OR 'root'. But not mixed.
How did you start BIT? With sudo or gksu?
orschiro commented on 2014-03-02 08:28 (UTC)
@mojtabazn
You have to build the package manually and then selectively install only backintime-gnome or backintime-gtk but not both
mojtabazn commented on 2014-03-02 05:04 (UTC)
i have this problem for install :
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: backintime-gnome and backintime-gtk are in conflict
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.