Run of fresh-releases for ruby-vagrant-cloud

Try this locally (using silver-platter):

debian-svp new-upstream ruby-vagrant-cloud 
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
Running ['new-upstream']
Opening branch at https://salsa.debian.org/ruby-team/ruby-vagrant-cloud.git/,branch=master
Using cached branch https://janitor.debian.net/git/ruby-vagrant-cloud/,branch=master
Total 918 (delta 0), reused 0 (delta 0), pack-reused 918
Total 773 (delta 192), reused 192 (delta 192), pack-reused 581
Total 781 (delta 192), reused 192 (delta 192), pack-reused 589

(6/114)
Total 119 (delta 40), reused 4 (delta 0), pack-reused 0
All changes applied successfully.
Workspace ready - starting.
Using upstream branch https://github.com/hashicorp/vagrant_cloud.git (from configuration)
Total 1164 (delta 19), reused 31 (delta 9), pack-reused 1110
Using version string 3.0.4.
No upstream upstream-revision format specified, trying tag:3.0.2
No upstream upstream-revision format specified, trying tag:ruby-vagrant-cloud-3.0.2
No upstream upstream-revision format specified, trying tag:v3.0.2
Not including upstream history, since previous upstream version (3.0.2) is not present in packaging branch history.
Using uscan to look for the upstream tarball.
Searching for revision importing ruby-vagrant-cloud version 3.0.2 on branch upstream, packaging branch, tag debian/3.0.2-1.
Upstream import of 3.0.2 lacks a tag. Set one by running: brz tag -rrevid:git-v1:eeaf0ac704db9683083d5b54fbf73a8ea91416f5 upstream/3.0.2
Imported ruby-vagrant-cloud_3.0.4.orig.tar.gz with pristine-tar.
Text conflict in debian
Text conflict in debian/changelog.THIS
Text conflict in debian/control.THIS
Text conflict in debian/rules.THIS
4 conflicts encountered.

Full worker log