Skip to content

migrate: Report why an migration cannot be applied#3913

Merged
MichaelEischer merged 1 commit intorestic:masterfrom
MichaelEischer:better-migrate-error-message
Sep 9, 2022
Merged

migrate: Report why an migration cannot be applied#3913
MichaelEischer merged 1 commit intorestic:masterfrom
MichaelEischer:better-migrate-error-message

Conversation

@MichaelEischer
Copy link
Copy Markdown
Member

What does this PR change? What problem does it solve?

Just returning that Migration upgrade cannot be applied: check failed
is not too useful when running migrate upgrade_repo_v2.

Was the change previously discussed in an issue or on the forum?

Fixes https://forum.restic.net/t/migration-upgrade-repo-v2-cannot-be-applied-check-failed/5407
Fixes https://forum.restic.net/t/restic-0-14-0-released/5359/19

Checklist

  • I have read the contribution guidelines.
  • I have enabled maintainer edits.
  • I have added tests for all code changes.
  • [ ] I have added documentation for relevant changes (in the manual).
  • There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
  • I have run gofmt on the code in all commits.
  • All commit messages are formatted in the same style as the other commits in the repo.
  • I'm done! This pull request is ready for review.

Just returning that `Migration upgrade cannot be applied: check failed`
is not too useful when running `migrate upgrade_repo_v2`.
@MichaelEischer MichaelEischer merged commit 2363e5c into restic:master Sep 9, 2022
@MichaelEischer MichaelEischer deleted the better-migrate-error-message branch September 9, 2022 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant