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.

fail to install:

Current thread 0x00007fbc267d9740 (most recent call first):
  File "/home/mz/.cache/yay/backintime/src/backintime-1.4.1/common/diagnostics.py", line 214 in _get_qt_information
  File "/home/mz/.cache/yay/backintime/src/backintime-1.4.1/common/diagnostics.py", line 134 in collect_diagnostics
  File "/home/mz/.cache/yay/backintime/src/backintime-1.4.1/common/test/test_diagnostics.py", line 60 in test_no_ressource_warning
  File "/usr/lib/python3.11/unittest/case.py", line 579 in _callTestMethod
  File "/usr/lib/python3.11/unittest/case.py", line 623 in run
  File "/usr/lib/python3.11/unittest/case.py", line 678 in __call__
  File "/usr/lib/python3.11/site-packages/_pytest/unittest.py", line 333 in runtest
  File "/usr/lib/python3.11/site-packages/_pytest/runner.py", line 169 in pytest_runtest_call
  File "/usr/lib/python3.11/site-packages/pluggy/_callers.py", line 77 in _multicall
  File "/usr/lib/python3.11/site-packages/pluggy/_manager.py", line 115 in _hookexec
  File "/usr/lib/python3.11/site-packages/pluggy/_hooks.py", line 493 in __call__
  File "/usr/lib/python3.11/site-packages/_pytest/runner.py", line 262 in <lambda>
  File "/usr/lib/python3.11/site-packages/_pytest/runner.py", line 341 in from_call
  File "/usr/lib/python3.11/site-packages/_pytest/runner.py", line 261 in call_runtest_hook
  File "/usr/lib/python3.11/site-packages/_pytest/runner.py", line 222 in call_and_report
  File "/usr/lib/python3.11/site-packages/_pytest/runner.py", line 133 in runtestprotocol
  File "/usr/lib/python3.11/site-packages/_pytest/runner.py", line 114 in pytest_runtest_protocol
  File "/usr/lib/python3.11/site-packages/pluggy/_callers.py", line 77 in _multicall
  File "/usr/lib/python3.11/site-packages/pluggy/_manager.py", line 115 in _hookexec
  File "/usr/lib/python3.11/site-packages/pluggy/_hooks.py", line 493 in __call__
  File "/usr/lib/python3.11/site-packages/_pytest/main.py", line 350 in pytest_runtestloop
  File "/usr/lib/python3.11/site-packages/pluggy/_callers.py", line 77 in _multicall
  File "/usr/lib/python3.11/site-packages/pluggy/_manager.py", line 115 in _hookexec
  File "/usr/lib/python3.11/site-packages/pluggy/_hooks.py", line 493 in __call__
  File "/usr/lib/python3.11/site-packages/_pytest/main.py", line 325 in _main
  File "/usr/lib/python3.11/site-packages/_pytest/main.py", line 271 in wrap_session
  File "/usr/lib/python3.11/site-packages/_pytest/main.py", line 318 in pytest_cmdline_main
  File "/usr/lib/python3.11/site-packages/pluggy/_callers.py", line 77 in _multicall
  File "/usr/lib/python3.11/site-packages/pluggy/_manager.py", line 115 in _hookexec
  File "/usr/lib/python3.11/site-packages/pluggy/_hooks.py", line 493 in __call__
  File "/usr/lib/python3.11/site-packages/_pytest/config/__init__.py", line 169 in main
  File "/usr/lib/python3.11/site-packages/_pytest/config/__init__.py", line 192 in console_main
  File "/usr/bin/pytest", line 8 in <module>

Extension modules: _dbus_bindings, _dbus_glib_bindings, _cffi_backend, gi._gi, cairo._cairo, gi._gi_cairo, PyQt5.QtCore, PyQt5.QtGui, PyQt5.QtWidgets (total: 9)
make: *** [Makefile:562: unittest] Segmentation fault (core dumped)
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: backintime-exit status 4

I was unable to get 1.4.0-5 to build. Checking the install logs, it looks like it failed because I didn't have sshfs installed when it got to running the test code to verify it built correctly. Installing sshfs first allowed me to install 1.4.0-5 without issues. I don't know if it'd be better to not require that set of tests, or to mark that package as required for the test cases, after which it can be automatically uninstalled.

@hollunder

WARNING: PyQt was not able to install a translator for language code "C". Deactivate translation and falling back to the source language (English).

THX for the full output, the failing unit test must be fixed on our (BiT developer) side.

I think the warning depends on some language settings of the target system.

A fix is already in the PR pipeline to be merged into BiT v1.4.1:

https://github.com/bit-team/backintime/pull/1537

Same as @hollunder here. Not using any helper.

The whole output is a bit lengthy, so I put it up there: https://paste.rs/TNkXL.txt Also note that a lot of tests are getting skipped for some reason.

And yes, I am using aurman as AUR helper, but it has never interfered with unit tests so far. I also get the same unit test failure with plain makepkg -scfi.

@hollunder I just tried again and it builds fine, no errors with makepkg... Are you using any aurhelper?

@hollunder

FAILED test/test_backintime.py::TestBackInTime::test_local_snapshot_is_successful - AssertionError: Regex didn't match: 'INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nI... 1 failed, 313 passed, 45 skipped in 14.30s

Could you please show us (here or better in a new issue at https://github.com/bit-team/backintime/issues) the full output of the failing unit test (the above snippet is incomplete and the important part is missing)?

THX a lot :-)

I would recommend to open an issue/ticket about it and provide more details to us. To me it is not clear what the problem is.

Unit test still fails when I try to install 1.4.0-5, I wonder why you don't get that test failure?

FAILED test/test_backintime.py::TestBackInTime::test_local_snapshot_is_successful - AssertionError: Regex didn't match: 'INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nI... 1 failed, 313 passed, 45 skipped in 14.30s

test/test_backintime.py:178: AssertionError

@graysky, no problem, thanks for keeping this package up to date!