Package Details: rdiff-backup 2.2.6-2

Git Clone URL: https://aur.archlinux.org/rdiff-backup.git (read-only, click to copy)
Package Base: rdiff-backup
Description: Reverse differential backup tool, over a network or locally
Upstream URL: https://github.com/rdiff-backup/rdiff-backup
Licenses: GPL-2.0-only
Submitter: arojas
Maintainer: carsme
Last Packager: carsme
Votes: 18
Popularity: 0.64
First Submitted: 2023-04-01 17:24 (UTC)
Last Updated: 2024-01-28 22:56 (UTC)

Latest Comments

1 2 3 4 Next › Last »

crean commented on 2024-07-11 18:56 (UTC)

Would you please consider removing the .gitignore file? If git can see untracked files, they are easy to clean up with a git clean -fd.

rwd2 commented on 2024-05-07 17:00 (UTC)

@exuvo Thanks, that was the solution indeed.

exuvo commented on 2024-05-07 09:35 (UTC)

You should just need to rebuild the package and it should be fixed.

rwd2 commented on 2024-05-06 18:16 (UTC) (edited on 2024-05-06 18:37 (UTC) by rwd2)

After a system upgrade of all the packages last week I get this error when starting rdiff-backup:

Traceback (most recent call last):
  File "/usr/bin/rdiff-backup", line 5, in <module>
    from rdiffbackup.run import main
ModuleNotFoundError: No module named 'rdiffbackup'

I see that rdiff-backup has files in /usr/lib/python3.11/site-packages/ while the current python version is 3.12.3-1.

I tried just copying /usr/lib/python3.11/site-packages/rdiff* to /usr/lib/python3.12/site-packages/ but then I get different errors.

carsme commented on 2023-10-08 16:12 (UTC) (edited on 2023-10-08 16:13 (UTC) by carsme)

As far as I can tell, upstream deleted that tag as it never was not a proper release, according to them. See https://github.com/rdiff-backup/rdiff-backup/commit/105122b142a45e57f35fb9e5e8cc08c435021528.

I've pushed a change so the version is now 2.2.6, which is their last release: https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.2.6.

This will require a manual downgrade for those who have 2.4.0 installed. Either that or I can bump the epoch.

hayfever commented on 2023-10-07 01:03 (UTC)

tarball is down, looks like wherever it was has been removed from the git... ? just getting a 404

ultdev commented on 2023-08-18 21:07 (UTC)

I ran into bug #892 filed upstream (ActionListTest.test_action_listincrements fails in sufficiently-negative-from-UTC timezones https://github.com/rdiff-backup/rdiff-backup/issues/892) and have created a patch based on the fix listed in task 893 (https://github.com/rdiff-backup/rdiff-backup/pull/893). Please add the following patch to this package, which can be removed once commit d8c2f68 is included in a release tag upstream: https://termbin.com/r0jl

rwd2 commented on 2023-08-13 10:26 (UTC)

@carsme currently there seems to be a bit of a mess with python 3.11 related packages on Arch32. So downgraded them all to the python 3.10 versions. After that I was able to build and run rdiff-backup 2.2.5-3 on my pentum4 (not i686 like I wrote earlier) Arch32 system.

carsme commented on 2023-08-10 16:23 (UTC) (edited on 2023-08-10 16:24 (UTC) by carsme)

@rwd2 I'm fairly certain you won't be able to cross-compile this, so I would focus on getting the PKGBUILD to work on your Arch Linux 32 system.

The wiki article is about packaging 32-bit software for other architectures, what you're trying to do is the opposite - packaging (potentially) 64-bit software for a 32-bit system. So you should avoid any of the instructions in it.

arch=(any) means that the built package is architecture independent, which is not the case for this package as it contains the shared library /usr/lib/python3.11/site-packages/rdiff_backup/C.cpython-311-x86_64-linux-gnu.so.

Try adding i686 to the arch array instead:

arch=(x86_64 i686)

Not sure this will fix your build issues though.

The log you posted seems to indicate something is wrong with the build process for Python. Could you check the versions of the components involved?

$ pacman -Q python-setuptools python-wheel python-build
python-setuptools 1:68.0.0-1
python-wheel 0.40.0-3
python-build 0.10.0-4

My suspicion is that this is unrelated to rdiff-backup and has to do with the Python packaging on Arch Linux 32. I've never packaged on a 32-bit system though so this is just a guess.

Let me know how it goes!

rwd2 commented on 2023-08-10 15:49 (UTC) (edited on 2023-08-10 16:04 (UTC) by rwd2)

@carsme: I tried compiling on my arch32 system. I changed the value of arch in PKGBUILD to 'any', and then did a 'makepkg -rs'. I get errors, but they seem to be about the build environment rather than rdiff-backup : https://pastebin.com/A1Cc3u04. I will ask on the arch32 forums.

Would cross compiling on a x86_64 arch system be possible? I know 32 bit support was dropped in Ach so I can imagine the tools/libraries to do that are no longer there.