Run of fresh-snapshots for pyexploitdb

• Worker: atlas.kali.org
• Package: pyexploitdb
• Change set: 7d02047f-40b6-474c-8700-82a813eb325f
• Branch URL: https://gitlab.com/kalilinux/packages/pyexploitdb.git
• Upstream Branch URL: https://github.com/GoVanguard/pyExploitDb.git/,branch=master
• Start time: 2022-04-12T15:25
• Duration: 24m40s
• Success probability: 0.07 (based on 36 previous runs)
• Status: success ( schedule control run )
• Description: Merged new upstream version 0.2.0+20190604+git20211018.1.792c369
• Review Status: unreviewed
• Diff: raw diff, binary diffs are not available (missing control run - schedule control run )
• Command: DEB_UPDATE_CHANGELOG=auto deb-new-upstream --snapshot --debian-revision=0kali1 --refresh-patches
• Build Version: 0.2.0+20190604+git20211018.1.792c369-0kali1~jan+nus1

Reschedule Reschedule (from scratch) Publish now Reprocess logs

Merge these changes:

git pull https://janitor.kali.org/git/pyexploitdb fresh-snapshots/main

git pull https://janitor.kali.org/git/pyexploitdb fresh-snapshots/pristine-tar

git pull https://janitor.kali.org/git/pyexploitdb fresh-snapshots/upstream

Full worker log

• Full build log

Summary

Merged new upstream version: 0.2.0+20190604+git20211018.1.792c369 (was: 0.2.0+20190604).

Diff

Branch: main

Diff is too long (more than 200 lines). Download the raw diff.

Branch: pristine-tar

diff --git a/pyexploitdb_0.2.0+20190604+git20211018.1.792c369.orig.tar.gz.delta b/pyexploitdb_0.2.0+20190604+git20211018.1.792c369.orig.tar.gz.delta
new file mode 100644
index 0000000..18db547
Binary files /dev/null and b/pyexploitdb_0.2.0+20190604+git20211018.1.792c369.orig.tar.gz.delta differ
diff --git a/pyexploitdb_0.2.0+20190604+git20211018.1.792c369.orig.tar.gz.id b/pyexploitdb_0.2.0+20190604+git20211018.1.792c369.orig.tar.gz.id
new file mode 100644
index 0000000..6876c2f
--- /dev/null
+++ b/pyexploitdb_0.2.0+20190604+git20211018.1.792c369.orig.tar.gz.id
@@ -0,0 +1 @@
+87d920a59effab5fda31b20095e2faa7de1f5e60

Branch: upstream

Tag: upstream/0.2.0+20190604+git20211018.1.792c369

Diff 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 DEB_UPDATE_CHANGELOG=auto deb-new-upstream --snapshot --debian-revision=0kali1 --refresh-patches to deb-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 7d02047f-40b6-474c-8700-82a813eb325f is ready
• ☑ merge proposals for previous run were not rejected: status.

Resulting package

The resulting binary packages can be installed (if you have the apt repository enabled) by running one of:

apt install -t kali-bleeding-edge python3-pyexploitdb

Lintian Result

• pyexploitdb_0.2.0+20190604+git20211018.1.792c369-0kali1~jan+nus1.dsc
• pyexploitdb_0.2.0+20190604+git20211018.1.792c369-0kali1~jan+nus1_amd64+jan.buildinfo
• w package-has-long-file-name 80 (84) > 80
• pyexploitdb_0.2.0+20190604+git20211018.1.792c369-0kali1~jan+nus1_amd64+jan.changes
• w package-has-long-file-name 80 (84) > 80
• python3-pyexploitdb_0.2.0+20190604+git20211018.1.792c369-0kali1~jan+nus1_all.deb