Run of fresh-releases for py3status

Try this locally (using silver-platter):

debian-svp new-upstream py3status 
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
Opening branch at https://salsa.debian.org/debian/py3status.git/,branch=debian%2Fmaster
Using cached branch file:///home/janitor/vcs/git/py3status/,branch=master
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
upstream/3.22 does not point to a valid object
Using upstream branch https://github.com/ultrabug/py3status.git (guessed)
Total 19991 (delta 1277), reused 1276 (delta 1260), pack-reused 18692
Using version string 3.22.
No upstream upstream-revision format specified, trying tag:3.22
Using uscan to look for the upstream tarball.
Searching for revision importing py3status version 3.22 on packaging branch.
Upstream import of 3.22 lacks a tag. Set one by running: brz tag -rrevid:git-v1:c0554f51f46fcbe82d5ebeddc3ef543742dc0d60 upstream/3.22
Total 19539 (delta 1032), reused 1032 (delta 1032), pack-reused 18507
3.23 does not point to a valid object
3.24 does not point to a valid object
3.25 does not point to a valid object
3.26 does not point to a valid object
3.27 does not point to a valid object
3.28 does not point to a valid object
3.29 does not point to a valid object
3.30 does not point to a valid object
Not storing pristine-tar metadata, since there is no pristine-tar branch.
Text conflict in debian
Text conflict in debian/changelog.THIS
Text conflict in debian/control.THIS
3 conflicts encountered.
Worker failed (missing-changelog): Could not find changelog at /home/janitor/tmp/tmp1u0hfnuf/py3status/debian/changelog in tree.
Elapsed time: 0:04:47.877855

Full worker log