New Upstream Snapshot - rust-y4m

• QA Page
• Maintainer email: pkg-rust-maintainers@alioth-lists.debian.net
• Automatic publish policy: main: push-derived , pristine-tar: push-derived , upstream: push-derived
• Last processed: 2023-02-26T01:01 (took 4m14s)
• Branch URL: https://salsa.debian.org/rust-team/debcargo-conf.git -b master [src/y4m] (taken from version 0.8.0-1)
• Queue position: 19137 (a 5w4d wait)

Schedule a new run

Ready changes

Publish now

Summary

Merged new upstream version: 0.7.0+git20221123.1.9dc0b01 (was: 0.7.0).

Diff

diff --git a/src/y4m/debian/changelog b/src/y4m/debian/changelog
index d096cc6d3..a834adb30 100644
--- a/src/y4m/debian/changelog
+++ b/src/y4m/debian/changelog
@@ -1,3 +1,9 @@
+rust-y4m (0.7.0+git20221123.1.9dc0b01-1) UNRELEASED; urgency=low
+
+  * New upstream snapshot.
+
+ -- Debian Janitor <janitor@jelmer.uk>  Sun, 26 Feb 2023 00:59:54 -0000
+
 rust-y4m (0.7.0-1) unstable; urgency=medium
 
   * Package y4m 0.7.0 from crates.io using debcargo 2.5.0

More details

Full run details

Historical runs

• source-format-unbuildable: Source format 3.0 (quilt) unusable: no upstream tarball found at ../rust-y4m_0.7.0+git20221123.1.9dc0b01.orig.tar.{bz2,gz,lzma,xz}
• push-failed: Failed to push result branch: EOF occurred in violation of protocol (_ssl.c:2393)
• push-failed: Failed to push result branch: EOF occurred in violation of protocol (_ssl.c:2396)
• bad-gateway: Failed to push result branch: Unexpected HTTP status 502 for https://janitor.debian.net/git/rust-y4m/info/refs?service=git-upload-pack: Unable to handle http code: Bad Gateway
• push-failed: Failed to push result branch: EOF occurred in violation of protocol (_ssl.c:2396)