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.

here it is again failing caused by check errors ..

======================================================================
FAIL: test_local_snapshot_is_successful (test.test_backintime.TestBackInTime)
end to end test - from BIT initialization through snapshot
----------------------------------------------------------------------
**
This application failed to start because no Qt platform plugin could be initialized.
**

also installing qt5-wayland is not changing this issue.. only when try to build under GNOME no problem in other Desktop Environments. Solution is to setup qt theming to work under gnome like: https://wiki.archlinux.org/title/Uniform_look_for_Qt_and_GTK_applications#QGnomePlatform

@scaramanga Thank you. I had the same problem but I could fix it in that way.

Ah I see what the problem was now, previously this package downloaded a specific commit as the same filename, which was in my sources folder, removing that makes everything work again.

I'm running Xorg and faced the same validation issue. Deleting the backintime-cache of my AUR helper (in my case ~/.cache/paru/clone/backintime) fixed it.

@katt - TLDR: Install qt5-wayland if you're running a Wayland system and see if that helps.

I was having build issues as well- I'm running Sway/Wayland. After running /usr/bin/backintime-qt --debug I found qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" as an error in my console output. I installed qt5-wayland based on this google result.

This allowed for a successful 1.3.3 install.

Checksum appear to be wrong..

==> Making package: backintime 1.3.3-3 (Fri Feb 17 17:20:12 2023)
==> Retrieving sources...
  -> Found backintime-1.3.3.tar.gz
==> Validating source files with b2sums...
    backintime-1.3.3.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Could not download sources.

Even fixing that, it fails right away at

==> Starting build()...
/startdir/PKGBUILD: line 17: cd: backintime-1.3.3/common: No such file or directory
==> ERROR: A failure occurred in build().

@dev_aryoda Aha. Glad we sorted that out!

@Rhinoceros THX a lot for your support! "1" as return code of xdpyinfo explains perfectly why the unit test does not trigger the system tray icon plugin and therefore succeeds.

@dev_aryoda

e.g. if xdpyinfo > /dev/null && echo $? returns a value <> 0 the systray icon is not shown (and the unit test cannot fail therefore)

Yeah okay. It returns 1.

Yep, I don't think there are any icon themes installed.

$ find /usr/share/icons -type f
/usr/share/icons/Adwaita/icon-theme.cache
/usr/share/icons/locolor/16x16/apps/gvim.png
/usr/share/icons/locolor/32x32/apps/gvim.png
/usr/share/icons/hicolor/index.theme
/usr/share/icons/hicolor/64x64/apps/qvidcap.png
/usr/share/icons/hicolor/64x64/apps/qv4l2.png
/usr/share/icons/hicolor/16x16/apps/qvidcap.png
/usr/share/icons/hicolor/16x16/apps/qv4l2.png
/usr/share/icons/hicolor/24x24/apps/qvidcap.png
/usr/share/icons/hicolor/24x24/apps/qv4l2.png
/usr/share/icons/hicolor/scalable/apps/htop.svg
/usr/share/icons/hicolor/scalable/apps/qv4l2.svg
/usr/share/icons/hicolor/scalable/apps/qvidcap.svg
/usr/share/icons/hicolor/48x48/apps/gvim.png
/usr/share/icons/hicolor/icon-theme.cache
/usr/share/icons/hicolor/32x32/apps/qvidcap.png
/usr/share/icons/hicolor/32x32/apps/qv4l2.png
/usr/share/icons/default/index.theme

@Rhinoceros

I just installed xorg-xdpyinfo and it still tests fine. Might be something else preventing the test from running though.

e.g. if xdpyinfo > /dev/null && echo $? returns a value <> 0 the systray icon is not shown (and the unit test cannot fail therefore)

... I am building on a headless system, but I'm just running makepkg, which creates both backintime and backintime-cli. I do only have backintime-cli installed on this system though. I was just building backintime here to test on a system without the icons installed.

Perhaps some icons were installed by another package so that the default theme contains the required icon file.

You can see the names of the installed icon themes with this command:

ls /usr/share/icons