That doesn't generate any error messages, but it also doesn't clean up the files in the object directory. Mark Post -----Original Message----- From: spearce@xxxxxxxxxxx [mailto:spearce@xxxxxxxxxxx] Sent: Sunday, July 16, 2006 9:52 PM To: Post, Mark K Cc: git@xxxxxxxxxxxxxxx Subject: Re: git-repack not removing files from $GIT_DIR/objects/[00-ff] So try: GIT_DIR=/home/git/pub/scm/linux-2.6.git git-prune-packed On a bare repository you should always set the GIT_DIR environment variable to the directory of the repository before running the command. "Post, Mark K" <mark.post@xxxxxxx> wrote: > Thanks for the suggestion, but it didn't help. One reason is that this > is a bare repository. When I ran the command, it aborted with "fatal: > Not a git repository." Most likely because bare repositories don't have > a .git directory in them. > > > Mark Post > > -----Original Message----- > From: spearce@xxxxxxxxxxx [mailto:spearce@xxxxxxxxxxx] > Sent: Sunday, July 16, 2006 9:22 PM > To: Post, Mark K > Cc: git@xxxxxxxxxxxxxxx > Subject: Re: git-repack not removing files from $GIT_DIR/objects/[00-ff] > > "Post, Mark K" <mark.post@xxxxxxx> wrote: > > I'm having a problem that just started occurring with git-repack not > > removing the files from $GIT_DIR/objects/*, and therefore not removing > > the directories, since they're not empty. The command I'm using (as > the > > git user) is this: > > GIT_DIR=/home/git/pub/scm/linux-2.6.git git-repack -a -d -l > > > > This used to work, but then suddenly stopped working. I ran an strace > > -f -F with this same command, and I don't see any attempt being made > to > > unlink the files in $GIT_DIR/objects/*/, but I do see the rmdir > commands > > failing because the directories are not empty. All of the files in > > those directories are owned by git:git. > > Try running `git-prune-packed` after git-repack. git-repack doesn't > delete the loose objects. > > I don't remember git-repack ever doing it either. -- Shawn. - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html