summaryrefslogtreecommitdiff
path: root/debian/watch
diff options
context:
space:
mode:
authorcos <cos>2024-04-20 09:18:16 +0200
committercos <cos>2024-04-20 09:47:09 +0200
commit3280e8181e83872988933ea71b89ae891749a872 (patch)
treec3b125a337eef8d05844a3ba252b32e3323a7a81 /debian/watch
parent581ee0d45f9e54ddf9f02a43c128b5f0d14688f6 (diff)
downloaddebian-ansible-core-3280e8181e83872988933ea71b89ae891749a872.zip
Attempt to recreate debian branch state from tar files
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 changes from ansible-core_2.14.13-1.debian.tar.xz to ansible-core_2.16.5-1.debian.tar.xz, which should hopefully be a squashed representation on the same set of changes on the uploader's unpushed git tree.
Diffstat (limited to 'debian/watch')
-rw-r--r--debian/watch2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/watch b/debian/watch
index e98fc57c..ae1cc690 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,4 +1,4 @@
version=4
opts=dversionmangle=s/\+dfsg//,repacksuffix=+dfsg \
-https://pypi.debian.net/ansible-core/ ansible-core-(2\.14\.[0-9]+).tar.gz
+https://pypi.debian.net/ansible-core/ ansible-core-([0-9]+\.[0-9]+\.[0-9]+).tar.gz