PKGBUILD v1.0.28-2 doesn't work on my KDE: the script creates the four packages (backintime, backintime-gnome, backintime-gtk and backintime-qt4) then cannot install anything because they all conflict with each other.
Here's part of my output:
warning: removing 'backintime' from target list because it conflicts with 'backintime-gnome'
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: backintime-gnome and backintime-gtk are in conflict
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 .. 45 46 47 48 49 50 51 52 53 54 55 .. 73 Next › Last »
noplomplom commented on 2013-10-19 18:33 (UTC)
graysky commented on 2013-10-19 18:15 (UTC)
Bump to v1.0.28-2
Changelog: http://backintime.le-web.org/change-log
PKG Changelog: The tricks in the PKBUILD that fukawi created are ingenious but cause the AUR to get confused over the deps and also limit the scope of the package to what is installed on the machine that builds it. I took a stab at a split pkg here that should satisfy all concerned. Please report any problems.
blackshark commented on 2013-10-14 20:24 (UTC)
Ok it's now working ! Thx
Germar commented on 2013-10-14 19:58 (UTC)
@blackshark please run:
'sed -i 1i"PATH=$PATH\nHOME=$HOME\nDISPLAY=$DISPLAY\n\n" /root/.config/backintime/anacrontab; rm /root/.local/share/backintime/anacron/1_Profil_principal'
and watch out if Backintime runs at the next quarter hour. This are modifications I already added for next version.
graysky commented on 2013-10-13 23:45 (UTC)
Not sure what to say about it... suspect something is jacked-up on your system.
blackshark commented on 2013-10-13 21:05 (UTC)
I think the problem is more with cron or anacron in fact... Because if I run the backup manually there is no problem, except an assertion with Python.
$ sudo /usr/bin/backintime --backup-job
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.
/usr/lib/python2.7/site-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed
import gobject._gobject
INFO: Lock
INFO: on process begins
INFO: [GnomePlugin.Systray.run]
INFO: [GnomePlugin.Systray.run] begin loop
INFO: Profile_id: 1
INFO: Call rsync to take the snapshot
graysky commented on 2013-10-13 20:47 (UTC)
It looks sane. Can you manually run that and see anything from the output (omit the >/dev/null redirect to see the output).
Run this as root and post any unusual output: /usr/bin/backintime --backup-job
blackshark commented on 2013-10-13 20:45 (UTC)
sudo cat /root/.config/backintime/anacrontab
1 0 1_Profil_principal nice -n 19 ionice -c2 -n7 /usr/bin/backintime --backup-job >/dev/null 2>&1
graysky commented on 2013-10-13 20:45 (UTC)
Post the output of:
cat /root/.config/backintime/anacrontab
blackshark commented on 2013-10-13 20:45 (UTC)
[[ -x /usr/bin/anacron ]] && echo ok
ok
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.