@graysky by reading the two PKBUILDS indeed I've seen that they are the same so I do not understand how and why two different pages are present in the AUR. Moreover is it not clear to me how to prevent the building of the backintime one if I want only backintime-cli being built, should I use any option?
Search Criteria
Package Details: backintime-cli 1.5.5-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/backintime.git (read-only, click to copy) |
|---|---|
| Package Base: | backintime |
| Description: | Simple backup system inspired from the Flyback Project and TimeVault. CLI version. |
| Upstream URL: | https://github.com/bit-team/backintime |
| Licenses: | GPL |
| Submitter: | None |
| Maintainer: | graysky |
| Last Packager: | graysky |
| Votes: | 301 |
| Popularity: | 0.66 |
| First Submitted: | 2009-01-09 20:46 (UTC) |
| Last Updated: | 2025-08-19 06:34 (UTC) |
Dependencies (8)
- cron (scron-gitAUR, vixie-cronAUR, busybox-crondAUR, mcronAUR, dcronAUR, systemd-cronAUR, dcron-gitAUR, cronie-selinuxAUR, systemd-cron-next-gitAUR, cronie, fcron)
- openssh (openssh-gitAUR, openssh-dnatAUR, openssh-hpn-shimAUR, openssh-selinuxAUR, openssh-gssapiAUR)
- python-dbus
- python-keyring
- python-packaging
- rsync (rsync-gitAUR, rsync-reflink-gitAUR, rsync-reflinkAUR)
- python (python37AUR) (make)
- backintimeAUR (backintime-gitAUR) (optional) – Qt6 GUI version
Required by (1)
Sources (3)
Xwang commented on 2025-08-23 16:25 (UTC)
willemw commented on 2025-08-19 07:46 (UTC)
@buthz: Also, there are no two copies. They both refer to the same package base file in the AUR: https://aur.archlinux.org/pkgbase/backintime. It is all the same file.
graysky commented on 2025-08-19 07:36 (UTC)
buhtz commented on 2025-08-19 07:02 (UTC)
But the PKGBUILD file is identical for both packages.
graysky commented on 2025-08-19 06:57 (UTC)
This package seems identical to the backintime one that depends on it. Why do we have two packages with the same PKGBUILD?
It is a split package to give user the option to have a cli only (backintime-cli) or both the cli and the qt6 GUI (backintime). I highly recommend that you ALWAYS read the PKGBUILD before installing anything from the AUR. https://wiki.archlinux.org/title/Arch_User_Repository#Advisorary_statements
buhtz commented on 2025-08-19 05:41 (UTC)
Hello Graysky, you might have missed the question from Xwang? https://aur.archlinux.org/packages/backintime-cli#comment-1034790 I am also interested in the answer. Regards, Christian
graysky commented on 2025-08-04 19:56 (UTC)
Like any package, some TU needs to adopt it. Why do you care about that exactly? It builds really fast.
Xwang commented on 2025-08-04 16:32 (UTC)
@graysky is there any possibility that this package will ever reach the official repo?
Xwang commented on 2025-08-03 11:17 (UTC)
This package seems identical to the backintime one that depends on it.
Why do we have two packages with the same PKGBUILD?
graysky commented on 2024-10-26 05:55 (UTC)
@buhtz - yes, 1.5.3-rc1 builds cleanly with this PKGBUILD
Pinned Comments
graysky commented on 2023-10-07 12:15 (UTC)
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.