Run of fresh-releases for exploitdb

Try this locally package):

debcheckout exploitdb
cd exploitdb
new-upstream
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
Opening branch at https://gitlab.com/kalilinux/packages/exploitdb.git/,branch=kali%2Fmaster
Using cached branch file:///home/janitor/vcs/git/exploitdb/,branch=master
Resuming from branch file:///home/janitor/vcs/git/exploitdb/,branch=new-upstream
/opt/debian-janitor/dulwich/dulwich/repo.py:490: UserWarning: ref refs/tags/upstream/20201121 points at non-present sha 16ab1d6e3b5cdc4fab121688aa7953ac30bdc0fe
  UserWarning,
/opt/debian-janitor/dulwich/dulwich/repo.py:490: UserWarning: ref refs/tags/upstream/20201225 points at non-present sha 8d980e540439b5126a0325917cabd5b32cd6f9a6
  UserWarning,
/opt/debian-janitor/dulwich/dulwich/repo.py:490: UserWarning: ref refs/tags/upstream/20201205 points at non-present sha a6fde9ab41c0ce9376fd6c68e78d7da755d37ae7
  UserWarning,
/opt/debian-janitor/dulwich/dulwich/repo.py:490: UserWarning: ref refs/tags/upstream/20210126 points at non-present sha 49a8af4d298f968f7fce4bb99720688ce50b1ae6
  UserWarning,
/opt/debian-janitor/dulwich/dulwich/repo.py:490: UserWarning: ref refs/tags/kali/20201225-0kali1 points at non-present sha 5bd60673e2b6e9120e113dfc59ccd231e40aa228
  UserWarning,
/opt/debian-janitor/dulwich/dulwich/repo.py:490: UserWarning: ref refs/tags/upstream/20201212 points at non-present sha b6513cf902299398bf91cdab841177a141f2f558
  UserWarning,
/opt/debian-janitor/dulwich/dulwich/repo.py:490: UserWarning: ref refs/tags/upstream/20201128 points at non-present sha 615b4cf66d93c4410e890432c60a8230eca583e4
  UserWarning,
upstream/20201121 does not point to a valid object
upstream/20201225 does not point to a valid object
upstream/20201205 does not point to a valid object
upstream/20210126 does not point to a valid object
kali/20201225-0kali1 does not point to a valid object
upstream/20201212 does not point to a valid object
upstream/20201128 does not point to a valid object
upstream/20201121 does not point to a valid object
upstream/20201225 does not point to a valid object
upstream/20201205 does not point to a valid object
upstream/20210126 does not point to a valid object
kali/20201225-0kali1 does not point to a valid object
upstream/20201212 does not point to a valid object
upstream/20201128 does not point to a valid object
upstream/20201121 does not point to a valid object
upstream/20201225 does not point to a valid object
upstream/20201205 does not point to a valid object
upstream/20210126 does not point to a valid object
kali/20201225-0kali1 does not point to a valid object
upstream/20201212 does not point to a valid object
upstream/20201128 does not point to a valid object
upstream/20201121 does not point to a valid object
upstream/20201225 does not point to a valid object
upstream/20201205 does not point to a valid object
upstream/20210126 does not point to a valid object
kali/20201225-0kali1 does not point to a valid object
upstream/20201212 does not point to a valid object
upstream/20201128 does not point to a valid object
Total 1340 (delta 157), reused 287 (delta 150), pack-reused 981

All changes applied successfully.
Total 1093 (delta 102), reused 107 (delta 102), pack-reused 981
Total 1085 (delta 101), reused 102 (delta 101), pack-reused 981

Workspace ready - starting.
Using upstream branch https://github.com/offensive-security/exploit-database.git (guessed)
Total 135878 (delta 86), reused 117 (delta 40), pack-reused 135704
Using version string 20210320.
No upstream upstream-revision format specified, trying tag:20210316
No upstream upstream-revision format specified, trying tag:exploitdb-20210316
No upstream upstream-revision format specified, trying tag:v20210316
No upstream upstream-revision format specified, trying tag:v.20210316
Old upstream version '20210316' is not present in upstream branch <UpstreamBranchSource for 'https://github.com/offensive-security/exploit-database.git/'>. Unable to determine whether upstream history is normally included. Assuming no.
Using uscan to look for the upstream tarball.

Full worker log