Run of fresh-snapshots for armitage

Try this locally package):

debcheckout armitage
cd armitage
DEB_UPDATE_CHANGELOG=auto deb-new-upstream --snapshot --debian-revision=0kali1 --refresh-patches
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
[2022-04-12 11:10:43] Opening branch at https://gitlab.com/kalilinux/packages/armitage.git/,branch=kali%2Fmaster
[2022-04-12 11:10:43] Using cached branch https://janitor.kali.org/git/armitage/,branch=kali%2Flatest
[2022-04-12 11:10:43] Using resume branch: https://janitor.kali.org/git/armitage,branch=fresh-snapshots%2Fmain
[2022-04-12 11:10:45] 5% (558/857)   
[2022-04-12 11:10:54] Total 857 (delta 213), reused 621 (delta 0)
[2022-04-12 11:11:10] Total 176 (delta 88), reused 74 (delta 0)
[2022-04-12 11:11:20] Total 116 (delta 76), reused 28 (delta 0)
[2022-04-12 11:11:38] Text conflict in src/cortana/core
[2022-04-12 11:11:38] Text conflict in src/msf
[2022-04-12 11:11:38] Text conflict in src/tree
[2022-04-12 11:11:38] Text conflict in src/ssl
[2022-04-12 11:11:38] Text conflict in src/table
[2022-04-12 11:11:38] Text conflict in resources
[2022-04-12 11:11:38] Text conflict in src/ui
[2022-04-12 11:11:38] Text conflict in scripts
[2022-04-12 11:11:38] Text conflict in src/console
[2022-04-12 11:11:38] Text conflict in src/armitage
[2022-04-12 11:11:38] Text conflict in scripts-cortana
[2022-04-12 11:11:38] Text conflict in src/graph
[2022-04-12 11:11:38] 12 conflicts encountered.
[2022-04-12 11:11:41] 98)
[2022-04-12 11:11:41] (72/98)
[2022-04-12 11:11:41] Total 176 (delta 55), reused 119 (delta 42), pack-reused 32
[2022-04-12 11:11:41] restarting branch
[2022-04-12 11:11:44] 
Compressing objects:   1% (1/98)
Compressing objects:   2% (2/98)
Compressing objects:   3% (3/98)
Compressing objects:   4% (4
[2022-04-12 11:11:44] Total 176 (delta 55), reused 119 (delta 42), pack-reused 32
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/console
[2022-04-12 11:11:57] Text conflict in armitage/src/main/resources/scripts-cortana
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/cortana/core
[2022-04-12 11:11:57] Text conflict in armitage/src/main/resources/resources
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/ssl
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/msf
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/tree
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/armitage
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/ui
[2022-04-12 11:11:57] Text conflict in armitage/src/main/resources/scripts
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/graph
[2022-04-12 11:11:57] Text conflict in armitage/src/main/java/table
[2022-04-12 11:11:57] 12 conflicts encountered.
[2022-04-12 11:12:00] Total 40 (delta 1), reused 7 (delta 1), pack-reused 32
[2022-04-12 11:12:03] (20/36)
[2022-04-12 11:12:03] (24/36)
[2022-04-12 11:12:03] Total 36 (delta 0), reused 35 (delta 0), pack-reused 0
[2022-04-12 11:12:03] Workspace ready - starting.
[2022-04-12 11:12:03] Running ['deb-new-upstream', '--snapshot', '--debian-revision=0kali1', '--refresh-patches']
[2022-04-12 11:12:03] Assuming changelog does not need to be updated, since there is a [dch] section in gbp.conf.
Using upstream branch https://github.com/r00t0v3rr1d3/armitage.git (guessed)
Total 7689 (delta 24), reused 116 (delta 22), pack-reused 7561
last found upstream version 1.0.0 (1.0.0) is lower than previous packaged upstream version (20220123)
Using version string 20220123+git20220123.1.cf60646.
No upstream upstream-revision format specified, trying tag:20220123
No upstream upstream-revision format specified, trying tag:armitage-20220123
No upstream upstream-revision format specified, trying tag:v20220123
No upstream upstream-revision format specified, trying tag:v.20220123
No upstream upstream-revision format specified, trying tag:release-20220123
No upstream upstream-revision format specified, trying tag:20220123_release
No upstream upstream-revision format specified, trying tag:20220123
No upstream upstream-revision format specified, trying tag:version-20220123
No upstream upstream-revision format specified, trying tag:armitage-20220123-release
No upstream upstream-revision format specified, trying tag:armitage-v20220123
Old upstream version '20220123' is not present in upstream branch <UpstreamBranchSource for 'https://github.com/r00t0v3rr1d3/armitage.git/'>. Unable to determine whether upstream history is normally included. Assuming no.
Looking for upstream 20220123+git20220123.1.cf60646 in upstream branch <RemoteGitBranch('https://github.com/r00t0v3rr1d3/armitage.git/', 'master')>.
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/janitorwx0fs6ce/armitage/debian
Opened schroot session kali-dev-amd64-sbuild-6dc60413-c9e5-4b8a-a86b-9067bb0bc92e (from kali-dev-amd64-sbuild)
apt: running ['apt', '-y', 'satisfy', 'debhelper-compat (= 12), ant, javahelper, default-jdk']
Creating directory /home/janitor in schroot session.
Using dependency resolver: [apt, cpan, ctan, pypi, npm, go, hackage, cran, cran, octave-forge]
No build tools found, falling back to simple export.
Exporting upstream branch revision b'git-v1:cf60646134a20a69bd573b71d967ceaccb227470' to create the tarball
Imported armitage_20220123+git20220123.1.cf60646.orig.tar.gz with pristine-tar.
All changes applied successfully.
Found tag for topmost changelog version '36419b25dd5b92a971e1d11893e138eccc4809f3'
No changes detected from 36419b25dd5b92a971e1d11893e138eccc4809f3 to HEAD.
Committing to: /home/janitor/tmp/janitorwx0fs6ce/armitage/
modified debian/changelog
Committed revision 78.
Merged new upstream version 20220123+git20220123.1.cf60646 (previous: 20220123)
Refresh quilt patches.
Committing to: /home/janitor/tmp/janitorwx0fs6ce/armitage/
modified debian/patches/Remove-mentions-of-old-metasploit-versions.patch
modified debian/patches/Update-postgresql-version-to-support-scram-sha-256.patch
modified debian/patches/Update-the-instructions-for-latest-release-in-Kali.patch
modified debian/patches/fix-launch-script.patch
modified debian/patches/fix-meterpreter.patch
Committed revision 79.
Merge new upstream version 20220123+git20220123.1.cf60646
[2022-04-12 11:34:37] Actual command: ['deb-new-upstream', '--snapshot', '--debian-revision=0kali1', '--refresh-patches']
[2022-04-12 11:34:38] Opened schroot session kali-dev-amd64-sbuild-90628b77-66bf-42e6-942f-0d29da6a2e16 (from kali-dev-amd64-sbuild)
[2022-04-12 11:34:38] Using fixers: [PgBuildExtOutOfDateControlFixer(), SimpleBuildFixer(MissingConfigure, fix_missing_configure), SimpleBuildFixer(MissingAutomakeInput, fix_missing_automake_input), SimpleBuildFixer(MissingConfigStatusInput, fix_missing_config_status_input), SimpleBuildFixer(MissingPerlFile, fix_missing_makefile_pl), SimpleBuildFixer(DebcargoUnacceptablePredicate, coerce_unacceptable_predicate), DependencyBuildFixer(AptFetchFailure, retry_apt_failure), PackageDependencyFixer(AptResolver(<ognibuild.debian.apt.AptManager object at 0x7fdd4a7b8c18>, [functools.partial(<function python_tie_breaker at 0x7fdd57e221e0>, <GitWorkingTree of /home/janitor/tmp/janitorwx0fs6ce/armitage>, ''), BuildDependencyTieBreaker('/var/run/schroot/mount/kali-dev-amd64-sbuild-90628b77-66bf-42e6-942f-0d29da6a2e16'), <function popcon_tie_breaker at 0x7fdd57e3cae8>]))]
[2022-04-12 11:34:38] Building debian packages, running 'sbuild -Asv --dpkg-file-suffix=+jan --force-orig-source --source-only-changes'.
[2022-04-12 11:49:15] Built ['armitage_20220123+git20220123.1.cf60646-0kali1~jan+nus1_amd64+jan.changes', 'armitage_20220123+git20220123.1.cf60646-0kali1~jan+nus1_source.changes'].
[2022-04-12 11:49:16] Running lintian
[2022-04-12 11:49:25] Pushing result branch to {'git': 'https://janitor.kali.org/git', 'bzr': 'https://janitor.kali.org/bzr'}
[2022-04-12 11:49:26] Pushing packaging branch cache to https://janitor.kali.org/git/armitage,branch=kali%2Flatest
[2022-04-12 11:49:31] git: cannot lock ref 'refs/tags/upstream/20220123+git20220123.1.cf60646': reference already exists
Traceback (most recent call last):
  File "/opt/janitor/janitor/worker.py", line 1075, in run_worker
    overwrite=True,
  File "/opt/janitor/janitor/worker.py", line 951, in push_branch
    tag_selector=tag_selector
  File "/opt/janitor/breezy/breezy/git/remote.py", line 705, in push_branch
    dw_result = self.send_pack(get_changed_refs, generate_pack_data)
  File "/opt/janitor/breezy/breezy/git/remote.py", line 511, in send_pack
    m = _LOCK_REF_ERROR_MATCHER.match(error)
TypeError: cannot use a bytes pattern on a string-like object

Full worker log Full build log