Run of fresh-snapshots for pyexploitdb
Merge these changes:
git pull https://janitor.kali.org/git/pyexploitdb fresh-snapshots/pristine-tar
git pull https://janitor.kali.org/git/pyexploitdb fresh-snapshots/upstream
Summary
Merged new upstream version: 0.2.0+20190604+git20200625.a4cd37e (was: 0.2.0+20190604).
Diff
Branch: pristine-tar
diff --git a/pyexploitdb_0.2.0+20190604+git20200625.a4cd37e.orig.tar.gz.delta b/pyexploitdb_0.2.0+20190604+git20200625.a4cd37e.orig.tar.gz.delta
new file mode 100644
index 0000000..97d17d1
Binary files /dev/null and b/pyexploitdb_0.2.0+20190604+git20200625.a4cd37e.orig.tar.gz.delta differ
diff --git a/pyexploitdb_0.2.0+20190604+git20200625.a4cd37e.orig.tar.gz.id b/pyexploitdb_0.2.0+20190604+git20200625.a4cd37e.orig.tar.gz.id
new file mode 100644
index 0000000..486af7b
--- /dev/null
+++ b/pyexploitdb_0.2.0+20190604+git20200625.a4cd37e.orig.tar.gz.id
@@ -0,0 +1 @@
+c9fa3c1e925c185d2a5ef5297c9ab0e805d24ee4
Branch: upstream
Tag: upstream/0.2.0+20190604+git20200625.a4cd37eDiff is too long (more than 200 lines). Download the raw diff.
Publish Blockers
- ☑ run was successful
- ☑ package has not been removed from the archive
- ☒ command changed from
new-upstream --snapshot --import-only
todeb-new-upstream --snapshot --debian-revision=0kali1 --refresh-patches --skip-empty
- ☑ review not required
- ☑ 0 publish attempts so far.not currently attempting to back off
- ☑ proposals not currently being rate-limited for maintainer None
- ☑ change set c15a0a36-9e42-47f4-916e-024b7f4d0197 is ready
- ☑ merge proposals for previous run were not rejected: status.