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 /MANIFEST.in | |
| parent | c4f015da4ac75017b97c24ef6601bdd98872e60f (diff) | |
| download | debian-ansible-core-bbed591285e1882d05198e518f75873af58939f5.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 'MANIFEST.in')
| -rw-r--r-- | MANIFEST.in | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/MANIFEST.in b/MANIFEST.in index 0b41af05..bf7a6a04 100644 --- a/MANIFEST.in +++ b/MANIFEST.in @@ -5,7 +5,6 @@ include changelogs/changelog.yaml include licenses/*.txt include requirements.txt recursive-include packaging *.py *.j2 -recursive-include test/ansible_test *.py Makefile recursive-include test/integration * recursive-include test/sanity *.in *.json *.py *.txt recursive-include test/support *.py *.ps1 *.psm1 *.cs *.md |