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 My sincere apologies, this was a fresh install of Arch and apparently locale was not generated properly, I should have checked that. Once I fixed the locale issue, everything compiled on first try.

-Joao

@JoaoMachado

Gtk-WARNING **: 20:56:30.052: Locale not supported by C library.\n\tUsing the fallback 'C' locale.

It looks like a different problem that reported by others and is related to a different locale. Which are you using?

May I suggest that you open a new issue at https://github.com/bit-team/backintime/issues so that the BiT dev team can track it better (I am most probably the only one following the discussions here...). THX :-)

I have just merged the fix for the failing unit test into the BiT DEV branch:

The fix is merged into the dev branch now: https://github.com/bit-team/backintime/commit/66d248fe8f2bb7e1c3189a14d1f73eb54949ef2a

Since the PKGBUILD "pins" the released version 1.3.3 (if I interpret it right) the fix will be used only if

1. we create a new BiT release and
2. the PKGBUILD will be updated to pin the new BiT release.

There is currently no fixed release date for the next version, I will discuss this internally with the BiT dev team...

I am trying to build BIT and I keep getting this error: Any ideas?

Ran 21 tests in 1.619s

OK python -m unittest -b test/test_backintime.py WARNING: Failed to connect to Udev serviceHelper daemon via D-Bus: org.freedesktop.DBus.Error.ServiceUnknown WARNING: D-Bus message: The name net.launchpad.backintime.serviceHelper was not provided by any .service files WARNING: Udev-based profiles cannot be changed or checked due to Udev serviceHelper connection failure .Fs ====================================================================== FAIL: test_local_snapshot_is_successful (test.test_backintime.TestBackInTime) end to end test - from BIT initialization through snapshot

Traceback (most recent call last): File "/home/joao/Build/builddir/backintime/src/backintime-1.3.3/common/test/test_backintime.py", line 147, in test_local_snapshot_is_successful self.assertRegex(filtered_log_output, re.compile(r'''INFO: Lock AssertionError: Regex didn't match: 'INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nINFO: Save config file\nINFO: Save permissions\nINFO: Create info file\nINFO: Unlock\n' not found in "INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nINFO: Save config file\nINFO: Save permissions\nINFO: Create info file\n\n(process:118866): Gtk-WARNING **: 20:56:30.052: Locale not supported by C library.\n\tUsing the fallback 'C' locale.\nINFO: Unlock\n"

Ran 3 tests in 2.636s

FAILED (failures=1, skipped=1) make: *** [Makefile:570: unittest] Error 1 ==> ERROR: A failure occurred in check().

Aborting...

I have added two more warnings to the exclusion list of the failing unit test (Qt5 warnings should not make BiT CLI unit tests fail):

https://github.com/bit-team/backintime/issues/1429

The change is based on the DEV branch (NOT the newest released version).

It would be great if someone (who is affected by the failing unit test due to these warnings) could test my modifications (see the commit/branch referenced in above issue).

I will add the warning qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" to the exclusion list of the unit test today as easiest solution since it is irrelevant for the success of this unit test (which is testing the CLI backend only and triggers the system tray icon to be shown - if this plugin of BiT is installed too via the BiT-qt part).

When we (the BiT developers) will have stabilized all major issues in BiT we plan to do a code refactoring to improve e.g. the testability of the Qt5 GUI parts and will hopefully get rid of unwanted side-effects like triggering above plugin...

@topas-rec: qt5-wayland is already an optional dependency for qt5-base. Wayland users that use Qt applications should already have it installed. It could be added as an optional dependency, perhaps. It is of no use to Xorg users.

Please consider adding qt5-wayland to the dependencies as discussed here: https://github.com/bit-team/backintime/issues/1421#issuecomment-1509761121

from my testings i need to start xorg session also in addition to set qt platform theming.. on wayland session it still fails to do the test. Also running the applications GUI is no püroblem under wayland once builded and installed. (all on GNOME)

This application failed to start because no Qt platform plugin could be initialized.

There is a related bug report (at the bottom of this already closed old issue) with the same symptoms.

I (as one of the BiT developers) are working on a fix...

Solution is to setup qt theming to work under gnome

To be totally sure about your steps: All you did to make it work was

• to install qgnomeplatform-qt5[-git]

• and (?) set the env var: QT_QPA_PLATFORMTHEME=gnome

Or are there further steps required?

BTW: A permanent qt5 dependency is unwanted if the user just wants to install BiT CLI (without the Qt5 GUI) so I think we must at least fix the unit test to work without Qt5 interference (better test isolation or ignore the unexpected warning).