borgbackup
No description set
- Developed at Archiving:Backup
- Sources inherited from project openSUSE:Factory
-
3
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:15.2:FactoryCandidates/borgbackup && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| borgbackup-1.1.0.tar.gz | 0002912847 2.78 MB | |
| borgbackup.changes | 0000026205 25.6 KB | |
| borgbackup.spec | 0000004247 4.15 KB |
Revision 6 (latest revision is 47)
Dominique Leuenberger (dimstar_suse)
accepted
request 532608
from
Hans-Peter Jansen (frispete)
(revision 6)
- Update to borgbackup 1.1.0
- Changelog:
* Major new features in the 1.1 release series are:
* borg recreate: remove files from existing archives and re-chunk or
re-compress them. This finally allows deduplication between legacy
Attic / Borg 0.xx archives and Borg 1.x archives. This is an
experimental feature.
* borg diff: show differences between two archives.
* borg mount: show all recorded versions of files with the "versions view".
* borg list: more formatting options, including generation of hashes and
per-file chunk statistics.
* borg create: automatic compression mode (-C auto,zlib/lz4/...), faster
handling of many files, experimental support for inclusion patterns
(--patterns, --patterns-from), files cache mode control (mtime/ctime)
* borg export-tar: streaming export of GNU tar compatible archives.
* Archive comments
* BLAKE2b256-based encryption modes, and "authenticated" modes that provide
data integrity without encryption. These provide better performance than
the existing SHA-256-based modes on most hardware, except where the x86
SHA extensions are available (e.g. AMD Ryzen).
* Repository indices and the Borg cache now use checksums to detect bitrot
and other corruption.
* A documented JSON API has been added to the most vital commands
(borg list, borg info and borg create).
* Structured JSON logging is available for all commands.
* --prefix has been supplemented with --glob-archives (-a), --sort-by,
--last and --first options. These can be used for borg list, borg info,
borg mount, borg check, borg delete and borg prune.
* Quality of life improvements:
* options that imply output (--show-rc, --show-version, --list, --stats, (forwarded request 532595 from alarrosa)
Comments 13
There is a problem with the last build of borgbackup because of renamed package python3-msgpack-python to python3-msgpack. It needs older python3-msgpack-python package to work properly. Look here:
https://github.com/borgbackup/borg/issues/3515#issuecomment-368881167
There is a problem with Fuse support in version 1.1.9, it does not work with python3-msgpack >= 0.5.6 (the current python3-msgpack version in Main Repository (OSS) is 0.6.1). Please, see here: https://github.com/borgbackup/borg/issues/4465
With version 1.1.10, the borg mount issue is solved from upstream (by bundling a "good" python3-msgpack).
Assimilation wasn't more serious fun, ever :-)
Sorry for taking so long, though...
Hi! There is Python 3.8 problem with borgbackup-1.1.10-2.2.x86_64 https://github.com/borgbackup/borg/issues/5028
And there is borgbackup 1.1.11 release https://github.com/borgbackup/borg/releases
Could you please upgrade it?
Hi! Is there any solution for unsupported
llfuse?borg mount not available: loading FUSE support failed [ImportError: No module named 'llfuse']
https://github.com/borgbackup/borg/issues/4122
Well, not until upstream releases a version, that supports pyfuse3.
At the time being, only some patches are floating around.
According to the SPEC file borg does not include python-msgpack anymore since version 1.2.0. But borg has very specific (as in limited) and hardcoded requirements for the version of python-msgpack. This could potentially cause borgbackup (and borgmatic) not to function every time there is an update of python310-msgpack in TW.
Currently the versions borgbackup-1.2.0-3.1 and python310-msgpack-1.0.4-1.1 in TW (20220622) do not match because borg 1.2.0 wants python-msgpack v1.0.3 (https://github.com/borgbackup/borg/blob/1.2.0/src/borg/helpers/msgpack.py#L182). The latest release of borg (1.2.1) allows python-msgpack v1.0.4. But again very specifically and hardcoded. Guess with the next update of python310-msgpack it potentially breaks again.
I'm not sure how this situation can be mitigated. In my opinion this is an upstream problem. If borg wants a version of python-msgpack that specific it should bundle it. For now a version bump of the borgbackup package to 1.2.1 will fix it.
There is a specific reason for not including the msgpack dependency in the package: it includes the msgpack since some time.
Do you have any specific reasons that point to problems with borg?
Sorry, I guess my message was not phrased too well.
I'll try to describe the issue again:
In my opinion this very specific version check (instead of maybe allowing all 1.0.x versions of msgpack) has the potential to make borg fail with an error message every time there is an update of python3-msgpack in TW to a version that does not yet match the checked version of borg. Of course there is nothing that the TW package maintainers for the borgbackup package can do about it other than version bump the package often.
I will keep an eye on updates to borgbackup and python310-msgpack on my system from now on and always check the borg changelog online before updating.
My workaround for now was to download the python310-msgpack-1.0.3-1.3 RPM package and downgrade. Now I can make backups.
With https://build.opensuse.org/request/show/985025 zypper will do that for you.
With Ben's change in place, zypper will enforce a resolution for any conflicts that arise and as a consequence will not allow the upgrade of msgpack to an unsupported version with respect to borg.
If you still have issues, let me know.
Great! Thanks for the fast resolution.