Package Details: backintime-cli-git 1.4.3.r54.g50c74444-1

Git Clone URL: https://aur.archlinux.org/backintime-git.git (read-only, click to copy)
Package Base: backintime-git
Description: Simple backup/snapshot system inspired by Flyback and TimeVault. CLI version
Upstream URL: https://github.com/bit-team/backintime
Licenses: GPL
Conflicts: backintime-cli
Provides: backintime-cli
Submitter: willemw
Maintainer: willemw
Last Packager: willemw
Votes: 28
Popularity: 0.000001
First Submitted: 2015-10-15 03:28 (UTC)
Last Updated: 2024-06-05 08:48 (UTC)

Required by (2)

Sources (1)

Latest Comments

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

willemw commented on 2024-09-29 16:52 (UTC)

In the PKGBUILD file, the main source url in source= becomes git+https://github.com/bit-team/backintime.git after variable expansion, which results in a git clone https://github.com/bit-team/backintime.git call.

So yes, whenever you install or reinstall a -git package with such a default URL, it will install the latest commit on the default branch.

https://wiki.archlinux.org/title/VCS_package_guidelines#VCS_sources explains how to change the URL to select another git repo, another branch or select a commit. It can be changed to install, for example, a specific pull request.

buhtz commented on 2024-09-29 14:47 (UTC)

Hi, is it your PKGBUILD pinned to a specific commit in the upstreams default branch or does it really always use the latest commit by its own?

buhtz commented on 2024-07-07 07:44 (UTC)

Hello willemw, my apologize. The script is really called via the make system. This gives me a headache. It is time we migrate to modern Python Packaging Standards to prevent workarounds like this.

willemw commented on 2024-07-06 16:54 (UTC)

@buhtz: please have a look at the build script (see the "View PKGBUILD" link on this page). It basically just follows the install instructions: "configure; make; make install". It's not calling any backintime scripts. I think I'll wait for the https://github.com/bit-team/backintime/pull/1782 fix.

buhtz commented on 2024-07-06 14:55 (UTC) (edited on 2024-07-06 15:08 (UTC) by buhtz)

The error is related to your packaging not to upstream. The folder "debian" was removed from upstream because it is not relevant and is especially not relevant to Arch.

EDIT: Ah... You use "updateversion.sh". That is prohibited for distro package maintainers. Just don't use it. It is a helper script for upstream maintainers only.

EDIT2: Please see this PR for a fix https://github.com/bit-team/backintime/pull/1782 . But again, I don't see a reason why you would use that script on your side.

willemw commented on 2024-07-06 12:54 (UTC)

@buhtz: *-git packages update themselves when you, the user, (re)install the package(s).

willemw commented on 2024-07-06 12:46 (UTC)

@buhtz: fails to builld (this also already happened before the fix):

# Inject version string into source files
(cd .. && ./updateversion.sh)
VERSION: 1.4.4-dev.ba50bf9c
Update 'common/version.py'
Update 'common/man/C/backintime.1'
Update 'common/man/C/backintime-config.1'
Update 'common/man/C/backintime-askpass.1'
Update 'qt/man/C/backintime-qt.1'
Update 'debian/changelog'
./updateversion.sh: line 81: debian/changelog: No such file or directory
./updateversion.sh: line 86: debian/changelog: No such file or directory
cat: debian/changelog: No such file or directory
./updateversion.sh: line 90: debian/changelog: No such file or directory
make: *** [Makefile:17: install] Error 1
make: Leaving directory '/build/backintime-git/src/backintime-git/qt'
==> ERROR: A failure occurred in package_backintime-git().

buhtz commented on 2024-07-06 12:32 (UTC)

Upstream fixed and merged the issues with global file lock. Would be nice if you could upgrade your *-git packages to give it a shot.

We do prepare a new release (1.5.0) in the end of this month.

buhtz commented on 2024-06-07 11:38 (UTC)

At upstream there is a pending PR fixing the latest permission problem in context of the global file lock if the option "Run only one snapshot at a time" is enabled. I did some tests on Manjaro but would be glad if someone could give it a test before merging it. See https://github.com/bit-team/backintime/pull/1756

buhtz commented on 2024-06-03 12:19 (UTC)

But "these dependencies" are listed as "Build and testing dependencies" not for regular user packages. You need this if you want to build BIT as a developer. Users don't need it.