Your message dated Tue, 5 Feb 2008 14:02:06 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#459487: Update
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: git-core
Version: 1:1.5.4~rc2-1
Severity: serious
Tags: experimental

> *** t7201-co.sh ***
> *   ok 1: setup
> *   ok 2: checkout from non-existing branch
> *   ok 3: checkout with dirty tree without -m
> *   ok 4: checkout with unrelated dirty tree without -m
> *   ok 5: checkout -m with dirty tree
> *   ok 6: checkout -m with dirty tree, renamed
> *   ok 7: checkout -m with merge conflict
> * FAIL 8: checkout to detach HEAD
>       
>       
>               git checkout -f renamer && git clean -f &&
>               git checkout renamer^ 2>messages &&
>               (cat >messages.expect <<EOF
>       Note: moving to "renamer^" which isn't a local branch
>       If you want to create a new branch from this checkout, you may do so
>       (now or later) by using -b with the checkout command again. Example:
>         git checkout -b <new_branch_name>
>       HEAD is now at 7329388... Initial A one, A two
>       EOF
>       ) &&
>               git diff messages.expect messages &&
>               H=$(git rev-parse --verify HEAD) &&
>               M=$(git show-ref -s --verify refs/heads/master) &&
>               test "z$H" = "z$M" &&
>               if git symbolic-ref HEAD >/dev/null 2>&1
>               then
>                       echo "OOPS, HEAD is still symbolic???"
>                       false
>               else
>                       : happy
>               fi
>       
> *   ok 9: checkout to detach HEAD with branchname^
> *   ok 10: checkout to detach HEAD with HEAD^0
> *   ok 11: checkout with ambiguous tag/branch names
> *   ok 12: checkout with ambiguous tag/branch names
> * failed 1 among 12 test(s)
> make[2]: *** [t7201-co.sh] Error 1
> make[2]: Leaving directory `/build/buildd/git-core-1.5.4~rc2/t'
> make[1]: *** [test] Error 2
> make[1]: Leaving directory `/build/buildd/git-core-1.5.4~rc2'
> make: *** [build-arch-stamp] Error 2



--- End Message ---
--- Begin Message ---
On Tue, Feb 05, 2008 at 02:36:48PM +0100, Frank Lichtenheld wrote:
> On Fri, Feb 01, 2008 at 02:13:53PM +0000, Gerrit Pape wrote:
> > On Tue, Jan 29, 2008 at 02:48:08PM +0100, Frank Lichtenheld wrote:
> > > Oddly enough it built fine for me on my own hppa when I built it
> > > manually.
> > 
> > I strongly guess this is due to a problem with subversion on this hppa
> > buildd.  We could see more details when running the selftests with
> > GIT_TEST_OPTS='--verbose --debug' set in the environment or through
> > make.
> 
> After upgrading the kernel from etch's version to 2.6.22 git-core builds
> fine.

The final 1.5.4 built fine on hppa/unstable too, I'm closing this bug
now.

 
http://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1%3A1.5.4-1&arch=hppa&stamp=1202123633&file=log

Thanks, Gerrit.


--- End Message ---

Reply via email to