Run of fresh-snapshots for pyexploitdb

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
[2022-09-20 10:38:42] Opening branch at https://gitlab.com/kalilinux/packages/pyexploitdb.git/,branch=kali%2Fmaster
[2022-09-20 10:38:42] Using cached branch file:///home/janitor/vcs/git/pyexploitdb/,branch=kali%2Flatest
[2022-09-20 10:38:50] reused 0 (delta 0), pack-reused 6
[2022-09-20 10:38:51] All changes applied successfully.
[2022-09-20 10:38:54] Total 7 (delta 0), reused 0 (delta 0), pack-reused 6
[2022-09-20 10:38:57] Total 7 (delta 0), reused 0 (delta 0), pack-reused 6
[2022-09-20 10:38:57] Workspace ready - starting.
[2022-09-20 10:38:57] Running ['deb-new-upstream', '--snapshot', '--debian-revision=0kali1', '--refresh-patches']
[2022-09-20 10:38:57] Assuming changelog does not need to be updated, since there is a [dch] section in gbp.conf.
Using upstream branch https://github.com/GoVanguard/pyExploitDb.git (from configuration)
Using upstream branch https://github.com/GoVanguard/pyExploitDb.git (from configuration)
Total 232 (delta 42), reused 104 (delta 24), pack-reused 104
Total 232 (delta 42), reused 104 (delta 24), pack-reused 104
Using version string 0.2.0+20190604+git20220804.1.ccbc1f2.
No upstream upstream-revision format specified, trying tag:0.2.0+20190604
No upstream upstream-revision format specified, trying tag:0.2.0+20190604
No upstream upstream-revision format specified, trying tag:pyexploitdb-0.2.0+20190604
No upstream upstream-revision format specified, trying tag:pyexploitdb-0.2.0+20190604
No upstream upstream-revision format specified, trying tag:v0.2.0+20190604
No upstream upstream-revision format specified, trying tag:v0.2.0+20190604
No upstream upstream-revision format specified, trying tag:v.0.2.0+20190604
No upstream upstream-revision format specified, trying tag:v.0.2.0+20190604
No upstream upstream-revision format specified, trying tag:release-0.2.0+20190604
No upstream upstream-revision format specified, trying tag:release-0.2.0+20190604
No upstream upstream-revision format specified, trying tag:0_2_0+20190604_release
No upstream upstream-revision format specified, trying tag:0_2_0+20190604_release
No upstream upstream-revision format specified, trying tag:0_2_0+20190604
No upstream upstream-revision format specified, trying tag:0_2_0+20190604
No upstream upstream-revision format specified, trying tag:version-0.2.0+20190604
No upstream upstream-revision format specified, trying tag:version-0.2.0+20190604
No upstream upstream-revision format specified, trying tag:pyexploitdb-0_2_0+20190604-release
No upstream upstream-revision format specified, trying tag:pyexploitdb-0_2_0+20190604-release
No upstream upstream-revision format specified, trying tag:pyexploitdb-v0.2.0+20190604
No upstream upstream-revision format specified, trying tag:pyexploitdb-v0.2.0+20190604
Old upstream version '0.2.0+20190604' is not present in upstream branch <UpstreamBranchSource for 'https://github.com/GoVanguard/pyExploitDb.git/'>. Unable to determine whether upstream history is normally included. Assuming no.
Looking for upstream 0.2.0+20190604+git20220804.1.ccbc1f2 in upstream branch https://github.com/GoVanguard/pyExploitDb.git/.
Looking for upstream 0.2.0+20190604+git20220804.1.ccbc1f2 in upstream branch https://github.com/GoVanguard/pyExploitDb.git/.
Running dist command: SCHROOT=kali-dev-amd64-sbuild PYTHONPATH=/:/opt/janitor/ognibuild:/opt/janitor/buildlog-consultant:/opt/janitor/upstream-ontologist:/opt/janitor:/opt/janitor/lintian-brush:/opt/janitor/breezy:/opt/janitor/silver-platter:/opt/janitor/dulwich:/opt/janitor/python-debian/lib:/opt/janitor/debmutate:/home/janitor:/usr/lib/python37.zip:/usr/lib/python3.7:/usr/lib/python3.7/lib-dynload:/usr/local/lib/python3.7/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.7/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/home/janitor/tmp/janitorkip09_as/pyexploitdb/debian
Running dist command: SCHROOT=kali-dev-amd64-sbuild PYTHONPATH=/:/opt/janitor/ognibuild:/opt/janitor/buildlog-consultant:/opt/janitor/upstream-ontologist:/opt/janitor:/opt/janitor/lintian-brush:/opt/janitor/breezy:/opt/janitor/silver-platter:/opt/janitor/dulwich:/opt/janitor/python-debian/lib:/opt/janitor/debmutate:/home/janitor:/usr/lib/python37.zip:/usr/lib/python3.7:/usr/lib/python3.7/lib-dynload:/usr/local/lib/python3.7/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.7/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/home/janitor/tmp/janitorkip09_as/pyexploitdb/debian
Opened schroot session kali-dev-amd64-sbuild-d81e4d2e-b531-46bf-b116-68d9044d9976 (from kali-dev-amd64-sbuild)
apt: running ['apt', '-y', 'satisfy', 'debhelper-compat (= 12),\n               dh-python,\n               python3-all,\n               python3-git,\n               python3-requests,\n               python3-setuptools']
Creating directory /home/janitor in schroot session.
Using dependency resolver: [apt, cpan, ctan, pypi, npm, go, hackage, cran, bioconductor, octave-forge]
Running ['python3', './setup.py', 'sdist']
Found new tarball pyExploitDb-0.2.8.tar.gz in /var/run/schroot/mount/kali-dev-amd64-sbuild-d81e4d2e-b531-46bf-b116-68d9044d9976/build/tmpxv3h56b0/pyexploitdb/dist.
Found tarball pyExploitDb-0.2.8.tar.gz in parent directory.
Found tarball pyExploitDb-0.2.8.tar.gz in parent directory.
Imported pyexploitdb_0.2.0+20190604+git20220804.1.ccbc1f2.orig.tar.gz with pristine-tar.
Imported pyexploitdb_0.2.0+20190604+git20220804.1.ccbc1f2.orig.tar.gz with pristine-tar.
All changes applied successfully.
All changes applied successfully.
Found tag for topmost changelog version '01f569682aaf6ec23aa58ca7ed5387ea6650534a'
No changes detected from 01f569682aaf6ec23aa58ca7ed5387ea6650534a to HEAD.
Committing to: /home/janitor/tmp/janitorkip09_as/pyexploitdb/
Committing to: /home/janitor/tmp/janitorkip09_as/pyexploitdb/
deleted .gitignore
deleted .gitignore
deleted .travis.yml
deleted .travis.yml
renamed README.md => PKG-INFO
renamed README.md => PKG-INFO
modified README.md
modified README.md
renamed README.md => pyExploitDb.egg-info/PKG-INFO
renamed README.md => pyExploitDb.egg-info/PKG-INFO
modified debian/changelog
modified debian/changelog
deleted dist
deleted dist
deleted dist/pyExploitDb-0.2.0-py3-none-any.whl
deleted dist/pyExploitDb-0.2.0-py3-none-any.whl
deleted dist/pyExploitDb-0.2.0.tar.gz
deleted dist/pyExploitDb-0.2.0.tar.gz
deleted packageIt.sh
deleted packageIt.sh
deleted pushPackage.sh
deleted pushPackage.sh
added pyExploitDb.egg-info
added pyExploitDb.egg-info
added pyExploitDb.egg-info/SOURCES.txt
added pyExploitDb.egg-info/SOURCES.txt
added pyExploitDb.egg-info/dependency_links.txt
added pyExploitDb.egg-info/dependency_links.txt
added pyExploitDb.egg-info/requires.txt
added pyExploitDb.egg-info/requires.txt
added pyExploitDb.egg-info/top_level.txt
added pyExploitDb.egg-info/top_level.txt
modified pyExploitDb/__init__.py
modified pyExploitDb/__init__.py
modified pyExploitDb/cveToEdbid.json
modified pyExploitDb/cveToEdbid.json
modified pyExploitDb/edbidToCve.json
modified pyExploitDb/edbidToCve.json
deleted requirements.txt
deleted requirements.txt
added setup.cfg
added setup.cfg
modified setup.py
modified setup.py
Committed revision 19.
Committed revision 19.
Merged new upstream version 0.2.0+20190604+git20220804.1.ccbc1f2 (previous: 0.2.0+20190604)
Refresh quilt patches.
An error occurred refreshing quilt patch change-data-location.patch: 

Applying patch debian/patches/change-data-location.patch
patching file pyExploitDb/__init__.py
Hunk #4 FAILED at 106.
1 out of 4 hunks FAILED -- rejects in file pyExploitDb/__init__.py
Patch debian/patches/change-data-location.patch does not apply (enforce with -f)

Full worker log

Publish Blockers

  • ☒ run was not 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 f66af0da-e253-46ff-83de-1db6a6d3c839 is ready
  • ☑ merge proposals for previous run were not rejected: status.