Jonathan Nieder wrote:
reassign 654422 src:git 1.7.7.3-1
tags 654422 + moreinfo
quit

Hi Peter,

peter green wrote:

package: git
severity: important

What version?
1:1.7.7.3-1 which afaict was the current version in sid as of a couple of hours ago.
[...]
During a rebuild after importing (after importing a new architecture
debian rebuilds the packages that were imported) git failed to build on
the armhf and s390x buildds with failures in the same tests. Namely "11
among 13 tests" in t9161-git-svn-mergeinfo-push.sh

Could you send a log from

        cd t
        sh t9161-git-svn-mergeinfo-push.sh -v -i
Unfortunately afaict the files left in the build-dir by a build on an autobuilder aren't saved. I could try to reproduce locally on armhf but since a new version of git has been uploaded in the meantime there doesn't seem much point. Lets see what happens with the new version first.
https://buildd.debian.org/status/package.php?p=git&suite=sid

Based on [1] it seems to pass tests on s390x.
Indeed it seems that in the time between when I wrote my mail and when you replied a new version has just been accepted in sid (though the changes file is dated as several days ago....), was built successfully on s390x and has not yet failed on any architecture. Lets wait and see what happens on the rest of the architectures and close this bug if there are no failures.
When something fails in the same way on both armhf and s390x it's
generally indicative of a wider problem (since the architectures are
very different). So I tried building on amd64 and being lazy I did the
build as root. When I did this I got test failures relating to mktemp
(unfortunately I didn't save details of these.

Interesting.  Running the test suite as (real) root did not work in
past, but it is supposed to work now.

Thanks and hope that helps,
Jonathan

[1] 
https://buildd.debian.org/status/fetch.php?pkg=git&arch=s390x&ver=1%3A1.7.8.2-1&stamp=1325608572





--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to