All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kestenholz <lists@irregular.ch>
To: git@vger.kernel.org
Subject: Bug encountered while comitting
Date: Fri, 24 Mar 2006 19:39:51 +0100	[thread overview]
Message-ID: <20060324183951.GA23193@spinlock.ch> (raw)

Hello list,

I don't know if this is the right place to report a bug, but I'll
just try and see what comes back.

I am trying to build a Wiki [1] using PHP, a hacked version of Markdown,
and git for content tracking. I use the git core plumbing to do the
history work.

The PHP script created directories under .git/objects which were
only writable by www-data. There were other directories which were
owned by user mk and group www-data, and they were group writable.

So, I had write access to only a part of the .git directory.

When I tried to commit, I got a message saying "Unable to write sha1
filename".

The result was, that only part of the commit was recorded and that I
experienced repository corruption. refs/heads/master pointed to a
non-existant object.

The expected behavior would have been an error message telling me I
had insufficient write privileges and surely no repository
corruption.



Thanks,
Matthias


[1]: http://spinlock.ch/cgi-bin/gitweb.pl?p=swisdk2/bugs.git;a=tree
(See Wiki_ctrl.php for source)


-- 
:wq

             reply	other threads:[~2006-03-24 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24 18:39 Matthias Kestenholz [this message]
2006-03-24 19:34 ` Bug encountered while comitting Andreas Ericsson
2006-03-25  1:15   ` Matthias Kestenholz
2006-03-24 22:55 ` Junio C Hamano
2006-03-25  1:15   ` Matthias Kestenholz
2006-03-25  6:17     ` Junio C Hamano
2006-03-25 10:23       ` Matthias Kestenholz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060324183951.GA23193@spinlock.ch \
    --to=lists@irregular.ch \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.