Your message dated Sun, 31 Jan 2021 22:43:00 +0100
with message-id <20210131214259.ga25...@debian.org>
and subject line Re: git: FTBFS: test failed
has caused the Debian Bug report #975173,
regarding git: FTBFS: test failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git
Version: 1:2.29.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> *** t3100-ls-tree-restrict.sh ***
> Initialized empty Git repository in /<<PKGBUILDDIR>>/t/trash
> directory.t3100-ls-tree-restrict/.git/
> expecting success of 3100.1 'setup': mkdir path2 path2/baz &&
> echo Hi >path0 &&
> test_ln_s_add path0 path1 &&
> test_ln_s_add ../path1 path2/bazbo &&
> echo Lo >path2/foo &&
> echo Mi >path2/baz/b &&
> find path? \( -type f -o -type l \) -print |
> xargs git update-index --add &&
> tree=$(git write-tree) &&
> echo $tree
> checking prerequisite: SYMLINKS
>
> mkdir -p "$TRASH_DIRECTORY/prereq-test-dir" &&
> (
> cd "$TRASH_DIRECTORY/prereq-test-dir" &&
> # test whether the filesystem supports symbolic links
> ln -s x y && test -h y
>
> )
> prerequisite SYMLINKS ok
> a384d4f8dd786f29d6da4705dee4c2c0bc6b5049
> ok 1 - setup
>
> expecting success of 3100.2 'ls-tree plain': git ls-tree $tree >current &&
> cat >expected <<\EOF &&
> 100644 blob X path0
> 120000 blob X path1
> 040000 tree X path2
> EOF
> test_output
> ok 2 - ls-tree plain
>
> expecting success of 3100.3 'ls-tree recursive': git ls-tree -r $tree
> >current &&
> cat >expected <<\EOF &&
> 100644 blob X path0
> 120000 blob X path1
> 100644 blob X path2/baz/b
> 120000 blob X path2/bazbo
> 100644 blob X path2/foo
> EOF
> test_output
> ok 3 - ls-tree recursive
>
> expecting success of 3100.4 'ls-tree recursive with -t': git ls-tree -r -t
> $tree >current &&
> cat >expected <<\EOF &&
> 100644 blob X path0
> 120000 blob X path1
> 040000 tree X path2
> 040000 tree X path2/baz
> 100644 blob X path2/baz/b
> 120000 blob X path2/bazbo
> 100644 blob X path2/foo
> EOF
> test_output
> ok 4 - ls-tree recursive with -t
>
> expecting success of 3100.5 'ls-tree recursive with -d': git ls-tree -r -d
> $tree >current &&
> cat >expected <<\EOF &&
> 040000 tree X path2
> 040000 tree X path2/baz
> EOF
> test_output
> ok 5 - ls-tree recursive with -d
>
> expecting success of 3100.6 'ls-tree filtered with path': git ls-tree $tree
> path >current &&
> cat >expected <<\EOF &&
> EOF
> test_output
> ok 6 - ls-tree filtered with path
>
> expecting success of 3100.7 'ls-tree filtered with path1 path0': git ls-tree
> $tree path1 path0 >current &&
> cat >expected <<\EOF &&
> 100644 blob X path0
> 120000 blob X path1
> EOF
> test_output
> ok 7 - ls-tree filtered with path1 path0
>
> expecting success of 3100.8 'ls-tree filtered with path0/': git ls-tree $tree
> path0/ >current &&
> cat >expected <<\EOF &&
> EOF
> test_output
> --- expected 2020-11-19 07:29:11.106032902 +0000
> +++ check 2020-11-19 07:29:11.106032902 +0000
> @@ -0,0 +1 @@
> +100644 blob X path0
> not ok 8 - ls-tree filtered with path0/
> # git ls-tree $tree path0/ >current &&
> # cat >expected <<\EOF &&
> # EOF
> # test_output
>
> expecting success of 3100.9 'ls-tree filtered with path2': git ls-tree $tree
> path2 >current &&
> cat >expected <<\EOF &&
> 040000 tree X path2
> EOF
> test_output
> ok 9 - ls-tree filtered with path2
>
> expecting success of 3100.10 'ls-tree filtered with path2/': git ls-tree
> $tree path2/ >current &&
> cat >expected <<\EOF &&
> 040000 tree X path2/baz
> 120000 blob X path2/bazbo
> 100644 blob X path2/foo
> EOF
> test_output
> ok 10 - ls-tree filtered with path2/
>
> expecting success of 3100.11 'ls-tree filtered with path2/baz': git ls-tree
> $tree path2/baz >current &&
> cat >expected <<\EOF &&
> 040000 tree X path2/baz
> EOF
> test_output
> ok 11 - ls-tree filtered with path2/baz
>
> expecting success of 3100.12 'ls-tree filtered with path2/bak': git ls-tree
> $tree path2/bak >current &&
> cat >expected <<\EOF &&
> EOF
> test_output
> ok 12 - ls-tree filtered with path2/bak
>
> expecting success of 3100.13 'ls-tree -t filtered with path2/bak': git
> ls-tree -t $tree path2/bak >current &&
> cat >expected <<\EOF &&
> 040000 tree X path2
> EOF
> test_output
> ok 13 - ls-tree -t filtered with path2/bak
>
> expecting success of 3100.14 'ls-tree with one path a prefix of the other':
> git ls-tree $tree path2/baz path2/bazbo >current &&
> cat >expected <<\EOF &&
> 040000 tree X path2/baz
> 120000 blob X path2/bazbo
> EOF
> test_output
> ok 14 - ls-tree with one path a prefix of the other
>
> # failed 1 among 14 test(s)
> 1..14
> make[4]: *** [Makefile:56: t3100-ls-tree-restrict.sh] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/11/19/git_2.29.2-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!
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.
--- End Message ---
--- Begin Message ---
Version: 1:2.30.0~rc1-1
Hi,
On Thu, Nov 19, 2020 at 10:45:05AM +0100, Lucas Nussbaum wrote:
> Source: git
> Version: 1:2.29.2-1
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
The upload of 1:2.30.0~rc1-1 was done after that, and seems to build fine (as
did later uploads). Closing this bug.
Cheers,
Ivo
--- End Message ---
