Lintian Fixes - foremancli

• QA Page
• Maintainer email: pkg-ruby-extras-maintainers@lists.alioth.debian.org
• Automatic publish policy: main: push-derived , pristine-tar: push-derived , upstream: push-derived
• Last processed: 2024-01-31T16:33 (took 4s)
• Branch URL: https://salsa.debian.org/ruby-team/foremancli.git -b master (taken from version 1.0-3)
• Tags that might be fixable: debian-watch-does-not-check-openpgp-signature package-uses-old-debhelper-compat-version upstream-metadata-file-is-missing silent-on-rules-requiring-root older-debian-watch-file-standard adopted-extended-field uses-debhelper-compat-file
• Queue position: 52385 (a 25w6d wait)

Schedule a new run

Run locally

More details

Full run details

Historical runs

• worker-resume-branch-missing: Branch does not exist: Not a branch: "https://janitor.debian.net/git/foremancli,branch=lintian-fixes/main/".
• nothing-new-to-do: No changes made
• success:
• nothing-to-do: No changes made
• worker-failure: AttributeError: 'RemoteGitRepository' object has no attribute '_serializer'
• success:
• worker-timeout: No keepalives received in 1:00:16.450057.
• run-disappeared: Worker started processing new run rather than 0adaa0b0-19a4-4c96-b688-10dff4effb5b
• result-push-failed: Failed to push result branch: Connection closed: Connection closed early The remote server unexpectedly closed the connection.
• success:
• run-disappeared: Worker started processing new run rather than acc9ecc6-d851-44e6-8714-b713c8f6e44a
• success:
• 502-bad-gateway: Unexpected HTTP status 502 for https://salsa.debian.org/ruby-team/foremancli.git/info/refs?service=git-upload-pack: Unable to handle http code: Bad Gateway
• build-failed-stage-explain-bd-uninstallable: build failed stage explain-bd-uninstallable