Run of fresh-releases for sparsebitset

1
2
3
4
5
6
7
8
9
10
11
[2022-09-12 11:50:53] Opening branch at https://gitlab.com/kalilinux/packages/sparsebitset.git/,branch=kali%2Fmaster
[2022-09-12 11:50:53] Using cached branch file:///home/janitor/vcs/git/sparsebitset/,branch=kali%2Flatest
[2022-09-12 11:51:06] Workspace ready - starting.
[2022-09-12 11:51:08] Running ['deb-new-upstream', '--debian-revision=0kali1', '--require-uscan', '--refresh-patches']
[2022-09-12 11:51:09] Assuming changelog does not need to be updated, since there is a [dch] section in gbp.conf.
Using upstream branch https://github.com/brettwooldridge/SparseBitSet.git (from configuration)
Upstream branch https://github.com/brettwooldridge/SparseBitSet.git inaccessible; ignoring. ('https://github.com/brettwooldridge/SparseBitSet.git', 'Connection error: while sending GET /brettwooldridge/SparseBitSet.git/info/refs?service=git-upload-pack: [Errno 111] Connection refused')
uscan warn: In watchfile /home/janitor/tmp/tmpgqkcia_g/debian/watch, reading webpage
  https://github.com/brettwooldridge/SparseBitSet/tags failed: 500 Can't connect to github.com:443 (Connection refused)
UScan failed to run: In watchfile /home/janitor/tmp/tmpgqkcia_g/debian/watch, reading webpage
  https://github.com/brettwooldridge/SparseBitSet/tags failed: 500 Can't connect to github.com:443 (Connection refused).
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 --debian-revision=0kali1 --require-uscan --refresh-patches to deb-new-upstream --debian-revision=0kali1 --require-uscan --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 477ded50-24ea-4c1b-a7e8-d2e0f35b272f is ready
  • ☑ no relevant previous merge proposals