Do you think it would be problematic to replace gksu with polkit/pkexec? I have written polkit actions and authorization rules for a couple of graphical applications that needed privilege escalation (nautilus, gedit, meld, baobab, bleachbit) mostly to open and edit stuff as root, and it all works great. I did so because I was wary of gksu deprecation, but it is required by BIT installation and now I'm wondering whether I could replace it as well. Any thoughts from the more knowledgeable?
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 .. 31 32 33 34 35 36 37 38 39 40 41 .. 73 Next › Last »
neitsab commented on 2014-04-08 22:03 (UTC)
orschiro commented on 2014-04-04 11:42 (UTC)
@Germar
Because I do not want to shutdown but hibernate. But I don't think this feature needs to be added to BIT. It's just a special use case for me. :)
Germar commented on 2014-04-04 09:03 (UTC)
@orschiro
why don't you use BIT's new shutdown button? It will automatically shutdown your system after new snapshot is done.
orschiro commented on 2014-04-04 05:43 (UTC)
@Germar
Thank you. I deleted the message file and the error disappeard. Can very well be that it was a result of a failed backup (I usually backup and set a hibernation timer which sometimes could have been to short to complete the backup).
Germar commented on 2014-04-03 21:17 (UTC)
@orschiro
I guess this was just some leftovers from a previous failed backup cron job. Status bar will display messages from ~/.local/share/backintime/worker.message. It may happen that BIT failed (e.g. because you shutdown your system during the cron job was starting) and left the old worker.message which will now spam your status bar. Just remove worker.message will solve this.
orschiro commented on 2014-04-03 06:42 (UTC)
@Germar
I encountered an interesting issue.
In the bottom status bar, BIT reports that it cannot find the snapshot folder.
However, in the sidebar all snapshots are correctly displayed.
See this screenshot: http://i.imgur.com/LY4voDm.png
A known bug?
Germar commented on 2014-03-11 21:30 (UTC)
@jeroenMathon python2-secretstorage is in depends in PKGBUILD. But for what ever reason it's not shown on this site. Take a look at grayskys comment from 2014-01-28 20:44.
JeroenMathon commented on 2014-03-11 20:10 (UTC)
@graysky
It seems you forgot to add Python2-secretstorage to the dependencies list.
Heres a url ^_^ https://aur.archlinux.org/packages/python2-secretstorage
orschiro commented on 2014-03-06 07:29 (UTC)
@Germar
Thanks! Renaming the folder did it. Now everything seems to be fine, including the udev rule:
~ cat /etc/udev/rules.d/99-backintime-root.rules
ACTION=="add", ENV{ID_FS_UUID}=="2aac80d3-3f44-41dc-9f99-18f251d518dd", RUN+="/usr/bin/su - 'root' -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' &"
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.