Your message dated Wed, 2 Sep 2009 15:00:06 +0000
with message-id
<20090902150006.11834.qm...@d8ea03923fd0b2.315fe32.mid.smarden.org>
and subject line Re: Bug#544380: git-core: Changing a symlink to a directory
confuses git
has caused the Debian Bug report #544380,
regarding git-core: Changing a symlink to a directory confuses git
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.)
--
544380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544380
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: git-core
Version: 1:1.5.6.5-3+lenny2
Severity: important
I've got a git repository that I own and use regularly.
One entry, "test" is a symlink to another directory (also named test).
For various reasons I decided that it should now be a directory.
Using qgit, I saw that my modifications included the removal of the
"test" symlink, so I "sync'd".
However when I tried to add the directory and it's contents, sync
failed with an error.
I tried
git-rm -r --cached <path-to-test>/test
which seemed to work.
Now I can't commit as the contents of the test directory are visible in
the commit dialog in git even though it lists the directory itself as
one of the "untracked files".
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages git-core depends on:
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libcurl3-gnutls 7.18.2-8lenny3 Multi-protocol file transfer libra
ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith
ii liberror-perl 0.17-1 Perl module for error/exception ha
ii libexpat1 2.0.1-4 XML parsing C library - runtime li
ii perl-modules 5.10.0-19 Core Perl modules
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages git-core recommends:
ii less 418-1 Pager program similar to more
ii openssh-client [ssh-client] 1:5.1p1-5 secure shell client, an rlogin/rsh
ii patch 2.5.9-5 Apply a diff file to an original
ii rsync 3.0.3-2 fast remote file copy program (lik
Versions of packages git-core suggests:
pn git-arch <none> (no description available)
pn git-cvs <none> (no description available)
pn git-daemon-run <none> (no description available)
ii git-doc 1:1.5.6.5-3+lenny2 fast, scalable, distributed revisi
pn git-email <none> (no description available)
pn git-gui <none> (no description available)
pn git-svn <none> (no description available)
pn gitk <none> (no description available)
pn gitweb <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Aug 31, 2009 at 05:56:46AM +0100, Philip Ashmore wrote:
> Just as I finished writing the bug report I noticed that despite the error
> dialog in qgit, the commit seems to have gone through.
>
> Now I have no error message and the test directory is no longer untracked.
>
> It's still worth looking into though, IMHO.
Hi, I do not completely understand your report, e.g. what "sync'd"
means. Since it doesn't look like a problem in git, I close the report.
If you think it's still worth looking into it, please re-open, and
provide instructions on how to reproduce the misbehavior.
Regards, Gerrit.
--- End Message ---
