Scrub Obsolete - libjdom2-java

• QA Page
• Maintainer email: pkg-java-maintainers@lists.alioth.debian.org
• Automatic publish policy: main: push-derived , pristine-tar: push-derived , upstream: push-derived
• Last processed: 2022-12-21T02:57 (took 44s)
• Branch URL: https://salsa.debian.org/java-team/libjdom2-java.git -b master (taken from version 2.0.6.1-1)
• Queue position: 191635 (a 158w6d wait)

Schedule a new run

No unpublished successful runs for libjdom2-java.

Historical runs

• nothing-to-do: No changes made
• run-disappeared: Worker started processing new run 00a9b528-ca5d-4cd6-a92c-951c39a11714 rather than 00bd3669-66ba-4c12-9d41-fd11ef0ee215
• run-disappeared: Worker started processing new run rather than 803933b7-9121-4aa8-b1fd-10e78914e5fb
• unable-to-find-upstream-tarball: Unable to find the needed upstream tarball for libjdom2-java, version 4.4.0.
• codemod-command-failed: Script ['deb-scrub-obsolete'] failed to run with code 1
• result-push-failed: Failed to push result branch: Connection closed: Connection closed early The remote server unexpectedly closed the connection.
• worker-exception: EOF occurred in violation of protocol (_ssl.c:2396)
• 502-bad-gateway: Unexpected HTTP status 502 for https://salsa.debian.org/java-team/libjdom2-java.git/info/refs?service=git-upload-pack: Unable to handle http code: Bad Gateway