Package Base Details: backintime

Git Clone URL: (read-only, click to copy)
Submitter: None
Maintainer: graysky
Last Packager: graysky
Votes: 289
Popularity: 0.62
First Submitted: 2009-01-09 20:46 (UTC)
Last Updated: 2023-01-03 20:52 (UTC)

Latest Comments

1 2 3 4 5 6 .. 62 Next › Last »

Rhinoceros commented on 2023-01-21 01:37 (UTC)

Thanks @dev_aryoda. Just to confirm, I'm not 100% sure it's dbus; that's just a wild guess since the tests fails via ssh.

I installed BiT fine locally, and then tried to build/test again over ssh. This again failed, so not sure what's going on there.

If you have trouble reproducing any of this, I'm happy to test for you in the future. If you prefer, happy to continue this conversation at Github.

dev_aryoda commented on 2023-01-21 01:04 (UTC) (edited on 2023-01-21 01:05 (UTC) by dev_aryoda)

I investigated this issue more, and there was the suggestion (by @dev_aryoda?) that dbus permissions might be to blame.

Yes, the DBus chicken-egg bug may be to blame but I thought I have already fixed this.


Some unit tests required that the BiT DBus service is already installed and running to succeed but the BiT DBus service is only installed AFTER running the unit tests.

If you install anyhow (ignoring the failing test) and run the unit tests again they should work. Any further update should also work because the BiT DBus service is still running so this unit test problem occurred only for first time installations.

Your failing unit test is still on my TODO list (pos 5 currently on my dynamic list ;-) to identify and fix the problem (if not already done).

Rhinoceros commented on 2023-01-20 02:27 (UTC)

I didn't think it was a good idea to install backup software that was failing tests, so I wanted to make sure they all passed. I investigated this issue more, and there was the suggestion (by @dev_aryoda?) that dbus permissions might be to blame. I had previously been sshing into the laptop I was attempting to upgrade, but I tried building directly from the machine itself. This solved the problem for me.

yochananmarqos commented on 2023-01-10 23:50 (UTC)

The tests work fine for me skipping the unit test:

  cd "$_pkgname-$_commit/common"

  # Skip unit test
  sed -i '/' Makefile

  # Set HOME to isolate some tests, which accesses files in ~/.ssh/, etc.
  HOME=tmp make test-v

dev_aryoda commented on 2023-01-10 23:44 (UTC)

FYI: I will look into this unit test failure soon and come back...

Rhinoceros commented on 2023-01-10 11:30 (UTC)

The checks fail for me on one system and work on another (with makepkg). Possibly related?

graysky commented on 2023-01-08 12:41 (UTC)

No need to edit the PKGBUILD just run makepkg with the --nocheck flag.

fishr commented on 2023-01-08 12:34 (UTC)

@scaramanga You may edit the PKGBUILD, disable line "make test" for now and build manually.

graysky commented on 2023-01-08 11:16 (UTC)

Builds for me with makepkg or with makechrootpkg

leonardof commented on 2023-01-07 23:52 (UTC)

I have the same error as @scaramanga:

Not using any helper, just git/makepkg/pacman.