Arch Linux User Repository

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.

Because the software is only written with KDE (qt) and Gnome (gtk) bindings; hence you have to have one and/or the other for things to work since the author hasn't written an E17, Xfce etc only version. You can mod the PKGBUILD to force the KDE version if you prefer KDE/QT bindings.

just tryig to understand a little of this all. If I use E17, why do I need gnome-python?

Updated: https://github.com/fukawi2/aur-packages/commit/ea3eff8cc32724bd295ffd21ca8c6467cf56c80e

I guess gnome-session is only needed for GnomePlugin which can give you an optional tray icon while a snapshot is working. So, gnome-session should be a suggestion, no hard dependency.

Request for out of date: There's version 1.0.10 tagged in bzr, though no offical tarball available. The configure script for the gnome GUI does not work for --no-check, meaning gnome-session is always enforced. Not good for Xfce, Enlightenment etc. Here my proposal for the PKGBUILd part: # Build a custom array of depends based on what DE is installed GUI_ENFORCE=1 # set to 0 if you don't want a GUI at all if [ -e '/usr/lib/libkonq.so' ]; then # KDE is installed depends=( ${depends[@]} xorg-utils python2-pyqt kdebindings-python) _type=( ${_type[@]} kde4 ) fi if [ -n "`which gnome-session 2> /dev/null`" ]; then # GNOME really depends=( ${depends[@]} pygtk python-notify gnome-python meld gksu gnome-session ) _type=( ${_type[@]} gnome ) fi if [ ${GUI_ENFORCE} == 1 -a ${#_type[@]} == 0 ]; then # other DE like Xfce, Enlightenment etc. depends=( ${depends[@]} pygtk python-notify gnome-python meld gksu ) _type=( ${_type[@]} gnome ) fi Replace the line "./configure" with "cp Makefile.template Makefile" as a work around for the gnome section. The check for gnome-session is useless here. http://bazaar.launchpad.net/~bit-team/backintime/trunk/view/head:/gnome/configure

is it neccessary that gvfs runs proccesses the whole time? I'm not using gnome

Very weird... Makes me think even more it's an issue further down the dep chain (ie, somewhere in python) rather than backintime itself. Still keen to fix in the PKGBUILD if possible though :)

Odd thing is that this is only happening on one machine. I have your PKG running just fine on 3 other x86_64 boxes... of course the machine that's causing a problem resides at my parent's house. Gotta coordinate a time with them to ssh in... they power down EVERYTHING including the modem and router when the machine is not in use :p

Hmm, same... Appears to have last been updated 6+ months ago: $ grep lib32-gnutls /var/log/pacman.log [2010-04-27 20:04] installed lib32-gnutls (2.8.6-1) [2010-09-05 09:40] upgraded lib32-gnutls (2.8.6-1 -> 2.8.6-3) [2010-10-10 17:40] upgraded lib32-gnutls (2.8.6-3 -> 2.8.6-4) [2011-01-18 18:16] upgraded lib32-gnutls (2.8.6-4 -> 2.10.4-1) [2011-05-08 11:45] upgraded lib32-gnutls (2.10.4-1 -> 2.12.2-1) I wonder if it's a python version issue; I see you're running it with 2.7.. There is python-gnutls in the repos, and it depends on python26. Could you try downgrading to 2.6 and see if it works?

@fukaw - wish I knew. # pacman -S lib32-gnutls error: target not found: lib32-gnutls I have multilib enabled. Really odd! :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date