backport #5969
Closed
backport #5969
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
update llfuse requirements, llfuse 1.3.8 is out!
enable using libxxhash (1.1-maint only)
fix small typo in quickstart docs
fix small typo in quickstart docs
…-1.1 fix --dry-run and --stats coexistence, fixes #5415
Python 3.8 changed the default format to PAX, but GNU format is documented for Borg.
export-tar: set tar format to GNU_FORMAT explicitly
create: backport implementation --stdin-mode, --stdin-user and --stdin-group, #5462
- kill the macOS builds, way too expensive (and problematic anyway) - kill the builds on python development versions, can't afford any more
reduce testing on travis, no macOS, no py3x-dev, see #5467 (1.1-maint)
docs: clarify borg create's '--one-file-system' option, #4009 The documentation now explicitly mentions btrfs subvolumes and explains how --one-file-system works. Co-authored-by: Eike <e.fokken+git@posteo.de>
Clarify '--one-file-system' for btrfs (1.1 backport)
Fix spurious failure in test_cache_files (1.1 backport)
github ci workflow (1.1-maint backport)
Use --timestamp in placeholders if given (1.1 backport)
Using "package" ansible module make the ansible playbook able to run against most unix OSes. Pacman module only works with Arch and derivatives. Also : changing state from "latest" to "present". Ansible should not be a way to keep your system up-to-date : it's a configuration management system and, as such, should not change anything if neither the playbook nor the machine changed its state (idempotency). Reference : https://github.com/ansible/ansible-lint/blob/master/lib/ansiblelint/rules/PackageIsNotLatestRule.py#L24
Doc / Deployment with ansible: pacman -> package
update CHANGES (1.1-maint)
vagrant: use generic/netbsd9 box, copied from master branch
same code as in master now.
vagrant: fix install_pyenv
update CHANGES
we test on py310-dev on github CI since a while and now also on the vagrant machines, so it should work ok.
more vagrant updates
it just hangs (swaps?) if there is too little RAM.
more vagrant updates
release 1.1.17
docs: remove duplicate faq entries
docs: fix sphinx warnings
we require >= 1.3 now anyway, see setup.py.
…k-1.1 fuse: remove unneeded version check and compat code
When exclude files are used, this can trigger a stack trace if the file does not exist. Instead exit nicely without the stacktrace.
Use an exception catching to avoid a stack trace
ghost
closed this
ghost
deleted the
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ignore this, major fail from automatically creating PR from command line