Run of fresh-snapshots for ruby-maxmind-db

Merge these changes:

git pull https://janitor.kali.org/git/ruby-maxmind-db fresh-snapshots/pristine-tar
git pull https://janitor.kali.org/git/ruby-maxmind-db fresh-snapshots/upstream
Full worker log

Summary

Merged new upstream version: 1.1.1+git20210128.85c5187 (was: 1.1.1).

Diff

Branch: pristine-tar

diff --git a/ruby-maxmind-db_1.1.1+git20210128.85c5187.orig.tar.gz.delta b/ruby-maxmind-db_1.1.1+git20210128.85c5187.orig.tar.gz.delta
new file mode 100644
index 0000000..813d3c1
Binary files /dev/null and b/ruby-maxmind-db_1.1.1+git20210128.85c5187.orig.tar.gz.delta differ
diff --git a/ruby-maxmind-db_1.1.1+git20210128.85c5187.orig.tar.gz.id b/ruby-maxmind-db_1.1.1+git20210128.85c5187.orig.tar.gz.id
new file mode 100644
index 0000000..6463c8c
--- /dev/null
+++ b/ruby-maxmind-db_1.1.1+git20210128.85c5187.orig.tar.gz.id
@@ -0,0 +1 @@
+d45f1a1b004940c40a4040bc8f96c23b5a08c62a

Branch: upstream

Tag: upstream/1.1.1+git20210128.85c5187

Diff is too long (more than 200 lines). Download the raw diff.

Publish Blockers

  • ☑ run was successful
  • ☑ package has not been removed from the archive
  • ☒ command changed from new-upstream --snapshot --import-only to deb-new-upstream --snapshot --debian-revision=0kali1 --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 5b3b9c01-fed6-40a8-abbb-78871751c616 is ready
  • ☑ no relevant previous merge proposals