Skip to content

[pull] master from restic:master#240

Open
pull[bot] wants to merge 4071 commits intofakegit:masterfrom
restic:master
Open

[pull] master from restic:master#240
pull[bot] wants to merge 4071 commits intofakegit:masterfrom
restic:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented Apr 27, 2021

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Apr 27, 2021
MichaelEischer and others added 29 commits October 3, 2025 19:34
CI: group dependency updates for golang.org/x/*
Bumps [github.com/peterbourgon/unixtransport](https://github.com/peterbourgon/unixtransport) from 0.0.6 to 0.0.7.
- [Release notes](https://github.com/peterbourgon/unixtransport/releases)
- [Commits](peterbourgon/unixtransport@v0.0.6...v0.0.7)

---
updated-dependencies:
- dependency-name: github.com/peterbourgon/unixtransport
  dependency-version: 0.0.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…/peterbourgon/unixtransport-0.0.7

build(deps): bump github.com/peterbourgon/unixtransport from 0.0.6 to 0.0.7
s3: drop manual credentials loading from environment
Replace Repository.SetIndex with internal helper
The group always needs execute access for the directories. In addition,
files should be always set to read-only for everyone as restic never
modifies files.
Just tell the user what to do instead of explaining too many details.
I've dropped the read-only variant as it actually has no representation
in the local and sftp backends. Instead it relied on both backends
initially creating all directories, which can't actually be guaranteed.

Based on a suggestion by @brad2014 in significant parts.
docs: fix permission setup for group-accessible repo
Drop the `packs` map from the internal state of the checker. Instead the
Packs(...) method now calls a filter callback that can select the
packs intended for checking.
Co-authored-by: Michael Eischer <michael.eischer@fau.de>
to make the exit code behaviour consistent with files inaccessible during the backup phase, making this change to exit with code 3 if not all target files/folders are accessible for backup

---------

Co-authored-by: Michael Eischer <michael.eischer@fau.de>
This prevents mangling the output due to delayed messages.
No complaints in the past.
MichaelEischer and others added 30 commits February 1, 2026 11:56
…/Azure/azure-sdk-for-go/sdk/storage/azblob-1.6.4
Bumps [github.com/minio/minio-go/v7](https://github.com/minio/minio-go) from 7.0.97 to 7.0.98.
- [Release notes](https://github.com/minio/minio-go/releases)
- [Commits](minio/minio-go@v7.0.97...v7.0.98)

---
updated-dependencies:
- dependency-name: github.com/minio/minio-go/v7
  dependency-version: 7.0.98
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Michael Eischer <michael.eischer@fau.de>
pack ID is included in full. In addition, the error message now says
that it is a pack file.
ui: mention compressed size of added files in `backup -vv`

This is already shown for modified files, but the added files message
wasn't updated when compression was implemented in restic.

Co-authored-by: Ilya Grigoriev <ilyagr@users.noreply.github.com>
docs: add warning for capability-based non-root backups
---

Co-authored-by: udf2457 <udf2457@users.noreply.github.com>
* mount: check for more requisite mountpoint conditions

In order to be able to mount a repository over a mountpoint target
directory via FUSE, that target directory needs to be both writeable and
executable for the UID performing the mount.

Without this patch, `restic mount` only checks for the target pathname's
existence, which can lead to a lot of data transfer and/or computation
for large repos to be performed before eventually croaking with a fatal
"fusermount: failed to chdir to mountpoint: Permission denied" (or
similar) error.

FUSE does allow for mounting over a target path that refers to a regular
(writeable) file, but the result is not accessible via chdir(), so we
prevent that as well, and accept only directory inodes as the intended
target mountpoint path.

* Don't use snake_case identifiers

* Add changelog entry

* tweak changelog summary

---------

Co-authored-by: Michael Eischer <michael.eischer@fau.de>
…stallation-docs

docs: remove outdated CentOS 6/7 installation instructions
…o-20260401

Fix a typo in the contributing docs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.