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.

@dev_aryoda: Yeah, I just realized you meant from master, not 1.3.2. Thanks for the heads up either way.

@yochananmarqos THX for the details!

Yes, python-pyfakefs is only used in test_tools.py (which is skipped) and in the upcoming release 1.3.3 in test_diagnostics.py

I have checked why the missing python-packaging is not causing any run-time errors: It was introduced after v1.3.2 so you do not yet have this dependency but it will "hit" you with the next BiT release.

@dev_aryoda: I can confirm it neither requires python-packaging nor python-pyfakefs. However, since one test fails, I skip it just like Fedora does:

check() {
  cd "$_pkgname-$pkgver"

  # Skip test_tools.py unit test
  sed -i '/test_tools.py/d' common/Makefile

  make -C common test-v
}

This package does not need qt5-wayland as an optional dependency as it's already an optional dependency of qt5-base. Any Qt 5 application might need it. It would be ridiculous to add it as an optional dependency for all of them.

@graysky

python-pyfakefs is only required for unit tests (= make test). Are you able to distinguish between build-only and run-time dependencies in PKGBUILD?

python-packaging is imported in three files and required to check the python package version number of Qt (in backintime-qt) and rsync + encfs in backintime (CLI). I would expect an python import error if this package is not installed.

qt5wayland was my mistake, it is named "qtwayland5" in Ubuntu and contains eg. libwayland-egl.so and libdrm-egl-server.so.

@dev_aryoda - I can add these deps but are certain they are required? For example, I have neither python-packaging nor python-pyfakefs on my system and backintime seems fully functional. Perhaps it is just my limited use case?

EDIT: is the unit test to which you refer needed only for make test not for runtime?

Re: qt5wayland, can you call out one of the binaries or libraries provided by this package? It will help me to identify the Arch package.

@gravsky

I am one of the developers of the new forming team to maintain backintime.

Could you please check our updated documentation of the dependencies (there were some undocumented dependencies until recently) and update your PKGBUILD?

https://github.com/bit-team/backintime#from-sources

Thanks for your support!

PS: Possibly missing dependencies:

sudo pacman -Sy python-packaging  # required by BiT
sudo pacman -Sy python-pyfakefs   # required for a unit test
possibly also <qt5wayland> for wayland support by Qt5 (I don't know the AUR pkg name)

I've recently been getting failed --user systemd jobs, including one for app-backintime@autostart.service - Backintime Password Cache. I'm not entirely sure what this is. I think perhaps a newer version of systemd is initiating /etc/xdg/autostart/backintime.desktop? The problem is that not all users use backintime, so those that have not configured it are getting this failure. I tried stopping and disable-ing the service, but neither worked. I don't even entirely understand what backintime pw-cache is for. Should it really be autostarted anyway?

$systemctl --user status app-backintime@autostart.service
× app-backintime@autostart.service - Backintime Password Cache
     Loaded: loaded (/etc/xdg/autostart/backintime.desktop; generated)
     Active: failed (Result: exit-code) since Sat 2022-06-25 15:28:04 AEST; 2h 47min ago
   Duration: 590ms
       Docs: man:systemd-xdg-autostart-generator(8)
   Main PID: 1108 (code=exited, status=2)
        CPU: 354ms

Jun 25 15:28:04 hostname systemd[877]: Starting Backintime Password Cache...
Jun 25 15:28:04 hostname systemd[877]: Started Backintime Password Cache.
Jun 25 15:28:04 hostname systemd[877]: app-backintime@autostart.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun 25 15:28:04 hostname systemd[877]: app-backintime@autostart.service: Failed with result 'exit-code'.

It probably is this issue: https://github.com/bit-team/backintime/issues/1181

Not sure why you're building in docker... build in a clean chroot[1] and report back.

1. https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

I have tested the build inside of a docker and it does not work for me:

dockerfile: FROM archlinux RUN pacman --noconfirm -Sy archlinux-keyring && pacman --noconfirm -Suy RUN pacman --noconfirm -Suy base-devel RUN pacman --noconfirm -Suy git RUN pacman --noconfirm -Suy cron fuse2 openssh python-dbus python-keyring rsync USER nobody WORKDIR /tmp/

RUN git clone https://aur.archlinux.org/backintime.git WORKDIR /tmp/backintime/ RUN makepkg