ruamel.yaml dependency is too restrictive #783
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#783
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
The ruamel.yaml dependency is currently pinned at >0.15.0,<0.18.0.
Fedora now started shipping ruamel.yaml 0.18.2, so we're getting broken dependencies.
Borgmatic seems to work and test fine with ruamel.yaml 0.18.5.
Steps to reproduce
No response
Actual behavior
No response
Expected behavior
No response
Other notes / implementation ideas
No response
borgmatic version
No response
borgmatic installation method
No response
Borg version
No response
Python version
No response
Database version (if applicable)
No response
Operating system and version
No response
Thanks for bringing this to my attention! Newer versions of ruamel.yaml (0.18.x) actually break both config generation and end-to-end tests. So this is unfortunately not as straightforward as relaxing the version requirement. I'll see what can be done though.
This has been implemented in main and will be part of the next release!
Just released with borgmatic 1.8.5!