Source: shfmt
Version: 3.4.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> === CONT  TestScripts/flags
>     testscript.go:397: 
>         WORK=$WORK
>         
> PATH=/tmp/testscript-main2353092992/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>         HOME=/no-home
>         TMPDIR=$WORK/.tmp
>         devnull=/dev/null
>         /=/
>         :=:
>         $=$
>         TESTSCRIPT_COVER_DIR=
>         exe=
>         
>         # https://github.com/rogpeppe/go-internal/issues/93
>         # ! shfmt -h
>         # ! stderr 'flag provided but not defined'
>         # stderr 'usage: shfmt'
>         # stderr 'Utilities' # definitely includes our help text
>         # ! stderr 'help requested' # don't duplicate usage output
>         # ! stderr '-test\.' # don't show the test binary's usage func 
> (0.003s)
>         > shfmt -version
>         [stdout]
>         
>         > stdout 'devel|v3'
>         FAIL: testdata/scripts/flags.txt:10: no match for `devel|v3` found in 
> stdout
>         
[...]

> dh_auto_test: error: cd _build && go test -vet=off -v -p 8 
> mvdan.cc/sh/v3/cmd/shfmt mvdan.cc/sh/v3/expand mvdan.cc/sh/v3/fileutil 
> mvdan.cc/sh/v3/interp mvdan.cc/sh/v3/pattern mvdan.cc/sh/v3/shell 
> mvdan.cc/sh/v3/syntax returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/shfmt_3.4.3-1_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to