Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - attic

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: attic 0.16-1

Git Clone URL: https://aur-dev.archlinux.org/attic.git (read-only)
Package Base: attic
Description: A deduplicating backup program for efficient and secure backups.
Upstream URL: https://attic-backup.org/
Licenses: BSD
Submitter: Beneldr
Maintainer: gim
Last Packager: gim
Votes: 30
Popularity: 0.687814
First Submitted: 2013-12-21 23:16
Last Updated: 2015-12-04 11:34

Latest Comments

1 2 3 4 Next › Last »

rpodgorny commented on 2016-05-23 16:06

arneko: not sure, really. but! just in case you don't know already, be sure to check borg - the actively maintained attic fork...

arneko commented on 2016-05-23 13:49

Is it just me or is both the "mount" and "extract" function broken? I tried on both my client and my server without results, also the self tests seem fo fail (fakeroot -u python -m attic.testsuite.run). Since both extract and mount don't work it's kinda hard to tell if backups works at all, but certainly seems to. Tried reinstalling the package with no effect.

Clouseau commented on 2015-11-14 20:38

All good, didn't upgrade the system for 2 months :D

Clouseau commented on 2015-11-13 19:46

Tried fresh install today and there is an error in build

Traceback (most recent call last):
File "/usr/bin/sphinx-build", line 5, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 3084, in <module>
File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 3070, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 3097, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 651, in _build_master
File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 952, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 839, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'Sphinx==1.3.1' distribution was not found and is required by the application
Makefile:113: recipe for target 'man' failed
make: *** [man] Error 1
==> ERROR: A failure occurred in build().
The build failed.

The package python-sphinx-1.3.1-10 is installed. Any idea?

noplomplom commented on 2015-10-17 09:21

Error again, re-installing does not help:

Traceback (most recent call last):
File "/usr/bin/attic", line 2, in <module>
from attic.archiver import main
ImportError: No module named 'attic'
attic: Error: Connection closed by remote host

Any ideas?

EDIT: I found where the problem was. I simply forgot to re-install attic on my remote server too...

JasonP commented on 2015-10-10 14:05

@Beneldr Also reinstalled here and everything goes fine :)


Beneldr commented on 2015-10-10 13:38

@JasonP: I just reinstalled the package. Also, note that vlad is now the maintainer.

JasonP commented on 2015-10-05 14:38

@Beneldr After the recent change to Python3.5 as the default Python 3 in Arch, attic stopped working because it's not installed in this version. Should I simply reinstall it or is there an automated way for library migrations when Python upgrades?


wsha commented on 2015-05-14 04:18

Just to add some information to the recent comments: development of the original Attic project has slowed down due to other commitments in the main developer's personal life. However, he is still working on Attic and does not plan to merge all of the changes that some other community members have been making in downstream forks of the project. The original Attic developer favors stability, whereas the forked projects are tolerant of backwards incompatible changes for the sake of adding new features (at least at the outset of a new fork but perhaps remaining stable after some initial changes). It is up to the users to decide which project is a better fit for their needs (if one of the new features is needed, one of the forks should probably be used; if not, the original project might provide more stability), but keep in mind that the forked versions will produce repos that can no longer work with the attic command from the original project.

You can read more here:


Beneldr commented on 2015-04-16 05:51

Package updated for newly released bugfix version 0.15. Also, for those of you interested in a more active branch, attic-merge-all-git has been uploaded to the AUR.