Your message dated Fri, 29 Jun 2007 14:32:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430903: fixed in git-core 1:1.5.2.2-3
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-cvs
Version: 1:1.5.2.2-2
Severity: normal


After completing the import process with this command:

git-cvsimport -k -v -m -d :pserver:[EMAIL PROTECTED]:/cvsroot bittornado

it ended with this last fetch/commit, and then the checkout below:

Fetching BitTornado/BT1/track.py   v 1.68
Update BitTornado/BT1/track.py: 49062 bytes
Tree ID 654007d16cbc2340eedeb49a638406704361c8c4
Parent ID 71ae8bf955593db335a796d119622d9a949bb37d
Committed patch 775 (origin +0000 2007-02-21 17:13:23)
Commit ID 94a462230ffffc8beac77dc4a17f87254cfd292f
Generating pack...
Done counting 3956 objects.
Deltifying 3956 objects...
 100% (3956/3956) done
Writing 3956 objects...
 100% (3956/3956) done
Total 3956 (delta 2977), reused 0 (delta 0)
Pack pack-31812d7cdaf8218768a33f892311489335157496 created.
Removing unused objects 100%...
Done.
DONE; creating master branch
D       .cvsignore
D       BitTornado/.cvsignore
D       BitTornado/BT1/.cvsignore
D       BitTornado/BT1/BadDataGuard.py
D       BitTornado/BT1/Choker.py
D       BitTornado/BT1/Connecter.py
D       BitTornado/BT1/Downloader.py
D       BitTornado/BT1/DownloaderFeedback.py
D       BitTornado/BT1/Encrypter.py
... and so on until all files were deleted

So it deleted every file in the checkout, my working directory now has only 
a .git directory in it. git-status shows that all files have been deleted 
(though the changes have not been added to the commit). Switching to the
origin branch has no effect. I had to a "git-reset --hard HEAD" to get the 
files back.

I also noticed a "connect error: Network is unreachable" message early on 
in the import (like in the first few lines) similar to #426617, but since 
it didn't affect the import I don't think it's related. (I'd post it, but 
that part of the import scrolled past the buffer on Konsole.)

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-4-vserver-amd64 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages git-cvs depends on:
ii  cvsps                        2.1-3       Tool to generate CVS patch set inf
ii  git-core                     1:1.5.2.2-2 fast, scalable, distributed revisi
ii  libdbd-sqlite3-perl          1.13-2      Perl DBI driver with a self-contai

Versions of packages git-cvs recommends:
ii  git-doc                      1:1.5.2.2-2 fast, scalable, distributed revisi

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: git-core
Source-Version: 1:1.5.2.2-3

We believe that the bug you reported is fixed in the latest version of
git-core, which is due to be installed in the Debian FTP archive:

git-arch_1.5.2.2-3_all.deb
  to pool/main/g/git-core/git-arch_1.5.2.2-3_all.deb
git-core_1.5.2.2-3.diff.gz
  to pool/main/g/git-core/git-core_1.5.2.2-3.diff.gz
git-core_1.5.2.2-3.dsc
  to pool/main/g/git-core/git-core_1.5.2.2-3.dsc
git-cvs_1.5.2.2-3_all.deb
  to pool/main/g/git-core/git-cvs_1.5.2.2-3_all.deb
git-daemon-run_1.5.2.2-3_all.deb
  to pool/main/g/git-core/git-daemon-run_1.5.2.2-3_all.deb
git-doc_1.5.2.2-3_all.deb
  to pool/main/g/git-core/git-doc_1.5.2.2-3_all.deb
git-email_1.5.2.2-3_all.deb
  to pool/main/g/git-core/git-email_1.5.2.2-3_all.deb
git-gui_1.5.2.2-3_all.deb
  to pool/main/g/git-core/git-gui_1.5.2.2-3_all.deb
git-p4_1.5.2.2-3_all.deb
  to pool/contrib/g/git-core/git-p4_1.5.2.2-3_all.deb
git-svn_1.5.2.2-3_all.deb
  to pool/main/g/git-core/git-svn_1.5.2.2-3_all.deb
gitk_1.5.2.2-3_all.deb
  to pool/main/g/git-core/gitk_1.5.2.2-3_all.deb
gitweb_1.5.2.2-3_all.deb
  to pool/main/g/git-core/gitweb_1.5.2.2-3_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gerrit Pape <[EMAIL PROTECTED]> (supplier of updated git-core package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 29 Jun 2007 12:54:39 +0000
Source: git-core
Binary: git-email git-core git-daemon-run git-doc git-cvs git-svn gitk gitweb 
git-p4 git-arch git-gui
Architecture: all source
Version: 1:1.5.2.2-3
Distribution: unstable
Urgency: low
Maintainer: Gerrit Pape <[EMAIL PROTECTED]>
Changed-By: Gerrit Pape <[EMAIL PROTECTED]>
Description: 
 git-arch   - fast, scalable, distributed revision control system (arch interop
 git-core   - fast, scalable, distributed revision control system
 git-cvs    - fast, scalable, distributed revision control system (cvs interope
 git-daemon-run - fast, scalable, distributed revision control system 
(git-daemon s
 git-doc    - fast, scalable, distributed revision control system (documentatio
 git-email  - fast, scalable, distributed revision control system (email add-on
 git-gui    - fast, scalable, distributed revision control system (GUI)
 git-p4     - fast, scalable, distributed revision control system (p4 interoper
 git-svn    - fast, scalable, distributed revision control system (svn interope
 gitk       - fast, scalable, distributed revision control system (revision tre
 gitweb     - fast, scalable, distributed revision control system (web interfac
Closes: 429810 430530 430903
Changes: 
 git-core (1:1.5.2.2-3) unstable; urgency=low
 .
   * debian/rules: move /usr/share/git-gui/ from git-core package into
     git-gui package (thx Ansgar Burchardt, closes: #430530).
   * debian/diff/0004-git-cvsimport-force-checkout-of-working-tree-after-i.diff:
     new; git-cvsimport: force checkout of working tree after initial import
     (closes: #430903).
   * debian/diff/0005-git-gui-properly-popup-error-if-gitk-should-be-start.diff:
     new; git-gui: properly popup error if gitk should be started but is not
     installed (#429810).
   * debian/control: git-gui: Recommends: gitk (closes: #429810).
   * debian/rules: workaround #427907: compile with -O0 instead of -O2 on hppa
     (#429389).
Files: 
 9f190550def098d44885bd572d0bf859 798 devel optional git-core_1.5.2.2-3.dsc
 e4d2c3663795aee3d5e75616bda94482 138413 devel optional 
git-core_1.5.2.2-3.diff.gz
 7a63dafddcbf852646317d85117137ce 781518 doc optional git-doc_1.5.2.2-3_all.deb
 61f7c72d2eab270f14a30230a0deb26a 144718 devel optional 
git-arch_1.5.2.2-3_all.deb
 c6757959796eaca3420b81aa81c3ff73 173166 devel optional 
git-cvs_1.5.2.2-3_all.deb
 e0a2cda3f7905374967373d78c0be355 182412 devel optional 
git-svn_1.5.2.2-3_all.deb
 425b495cb5e8eea0d86a1938010626a5 136102 contrib/devel optional 
git-p4_1.5.2.2-3_all.deb
 491749b1cb01cba75b9f196731529f8e 131192 devel optional 
git-daemon-run_1.5.2.2-3_all.deb
 211311346d9a6de3b040f0dc5b702f84 139032 devel optional 
git-email_1.5.2.2-3_all.deb
 1ad8d3c7e01c0f33498ba9717569d5ac 185454 devel optional 
git-gui_1.5.2.2-3_all.deb
 6de53f8ad4093fef07cb8274e411d69f 175342 devel optional gitk_1.5.2.2-3_all.deb
 8101c52e59c3fb2f34586f63c2318d82 171096 devel optional gitweb_1.5.2.2-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGhRahGJoyQbxwpv8RAstEAKCYpHS2yAf8QrQsqPOxmNaSdn26gQCdED47
qGK/nJMg9Rgl3ZUR6qAcniU=
=/asf
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to