Your message dated Wed, 9 Jul 2014 14:23:13 -0700
with message-id <20140709212313.GL2924@siren>
and subject line resolved issues with git-remote-bzr
has caused the Debian Bug report #703286,
regarding git-remote-bzr: fetch fails with "fatal: bad object
0000000000000000000000000000000000000000"
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 [email protected]
immediately.)
--
703286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703286
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git
Version: 1:1.8.2~rc3-1
Severity: wishlist
Hi!
Another issue with git-remote-bzr, it chokes on a bad object with a 0*
hash. I've found this on at least two repos:
$ git remote -v
origin bzr::lp:upstart (fetch)
origin bzr::lp:upstart (push)
$ git remote -v
origin bzr://bzr.savannah.nongnu.org/libpipeline/trunk/ (fetch)
origin bzr://bzr.savannah.nongnu.org/libpipeline/trunk/ (push)
$ git fetch
[... some "WARNING: TODO: fetch tag" omitted ...]
fatal: bad object 0000000000000000000000000000000000000000
error: bzr://bzr.savannah.nongnu.org/libpipeline/trunk/ did not send all
necessary objects
Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Control: reassign 703285 git-remote-bzr
Control: reassign 703286 git-remote-bzr
Version: git-remote-bzr/0.2+20140705-1
These were marked as fixed in the git-remote-bzr plugin shipped with git,
and should be resolved in the git-remote-bzr source package as well.
live well,
vagrant
signature.asc
Description: Digital signature
--- End Message ---
