[Bug 1347814] Re: git-gc can damage a repository

[Sworddragon]

> How do you know that your repository was damaged?

> Can you give instructions to reproduce the problem from scratch?

I wanted now to make a testcase but while doing so I have noticed that
the repository doesn't got damaged but I got still errors (like seeing
no commits anymore) because the permissions were still missing. My user
uses a default umask of 077 which is propably causing this behavior if
combined with sudo.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to git in Ubuntu.
https://bugs.launchpad.net/bugs/1347814

Title:
  git-gc can damage a repository

Status in “git” package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 14.10 dev with git 1:2.0.1-1 and if git-gc hasn't
  full write-access to a repository it can damage it. Getting such a
  permission state for a git repository isn't even unlikely if it was
  optimized in a sudo environment before. Here is an example output:

  sworddragon at ubuntu:~/.git/tvoip$ sudo git gc --aggressive --prune=now
  Counting objects: 1250, done.
  Delta compression using up to 6 threads.
  Compressing objects: 100% (1220/1220), done.
  Writing objects: 100% (1250/1250), done.
  Total 1250 (delta 944), reused 295 (delta 0)
  sworddragon at ubuntu:~/.git/tvoip$ git gc --aggressive --prune=now
  fatal: internal error: packed-ref cache cleared while locked
  error: failed to run pack-refs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1347814/+subscriptions