Source: d-shlibs
Version: 0.82
Severity: serious
Tags: buster sid
User: [email protected]
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> bash -n d-shlibmove
> bash -n d-devlibdeps
> shellcheck d-shlibmove
>
> In d-shlibmove line 243:
> sed -i -e "/^.*\.la usr\/lib || true$/d" "$INSTALLFILE_DEVPKG"
> ^-- SC1117: Backslash is literal in "\.". Prefer
> explicit escaping: "\\.".
> ^-- SC1117: Backslash is literal in "\/".
> Prefer explicit escaping: "\\/".
>
>
> In d-shlibmove line 251:
> sed -i -e "s/usr\/lib\( || true\)\?$/usr\/lib\/$DEB_HOST_MULTIARCH\1/"
> "$execscript"
> ^-- SC1117: Backslash is literal in "\/". Prefer
> explicit escaping: "\\/".
> ^-- SC1117: Backslash is literal in "\(". Prefer
> explicit escaping: "\\(".
> ^-- SC1117: Backslash is literal in
> "\)". Prefer explicit escaping: "\\)".
> ^-- SC1117: Backslash is literal in
> "\?". Prefer explicit escaping: "\\?".
> ^-- SC1117: Backslash is
> literal in "\/". Prefer explicit escaping: "\\/".
> ^-- SC1117: Backslash is
> literal in "\/". Prefer explicit escaping: "\\/".
> ^--
> SC1117: Backslash is literal in "\1". Prefer explicit escaping: "\\1".
>
>
> In d-shlibmove line 270:
> check_line "$PKGDEV" "Section: \(devel\|libdevel\)"
> ^-- SC1117: Backslash is literal in "\(".
> Prefer explicit escaping: "\\(".
> ^-- SC1117: Backslash is literal in
> "\|". Prefer explicit escaping: "\\|".
> ^-- SC1117: Backslash is
> literal in "\)". Prefer explicit escaping: "\\)".
>
> make[1]: *** [Makefile:10: check] Error 1
The full build log is available from:
http://aws-logs.debian.net/2018/05/02/d-shlibs_0.82_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
