diff options
| author | cos <cos> | 2024-04-20 09:15:12 +0200 |
|---|---|---|
| committer | cos <cos> | 2024-04-20 09:44:47 +0200 |
| commit | bbed591285e1882d05198e518f75873af58939f5 (patch) | |
| tree | c25b33652187f7070d0c2467663c11d6cd4e2326 /requirements.txt | |
| parent | c4f015da4ac75017b97c24ef6601bdd98872e60f (diff) | |
| download | debian-ansible-core-upstream/failed-recreation-attempt.zip | |
Attempt to recreate upstream branch state from tar filesupstream/failed-recreation-attempt
Unfortunately this was a too naive approach, and the result fails to
build.
Work around that version control is behind the actual package version in
trixie. As is obvious from the lacking commits in the salsa repository
and also visible on https://tracker.debian.org/pkg/ansible-core with the
report from vcswatch stating: VCS repository is not up to date.
This commit contains all changes from ansible-core_2.14.13.orig.tar.gz
to ansible-core_2.16.5.orig.tar.gz, which should hopefully be a squashed
representation on the same set of changes on the uploader's unpushed git
tree.
Diffstat (limited to 'requirements.txt')
| -rw-r--r-- | requirements.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/requirements.txt b/requirements.txt index 20562c3e..5eaf9f2c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -12,4 +12,4 @@ packaging # NOTE: Ref: https://github.com/sarugaku/resolvelib/issues/69 # NOTE: When updating the upper bound, also update the latest version used # NOTE: in the ansible-galaxy-collection test suite. -resolvelib >= 0.5.3, < 0.9.0 # dependency resolver used by ansible-galaxy +resolvelib >= 0.5.3, < 1.1.0 # dependency resolver used by ansible-galaxy |