I'm not sure. It could be some permission thing as a result of how the script works that syncs with the Github repo. Github uses ssh key authentication to identify the user, so we set up a keyfile that should be used by everyone with push access to darcs.h.o. Apparently, Git creates some files with the user's permissions which leads to problems if the umask is too restrictive. The push was successful nevertheless, which is a bit confusing. Ian and I will look into this.
On Wed, Sep 10, 2008 at 9:40 AM, Simon Peyton-Jones <[EMAIL PROTECTED]> wrote: > I got the following message re the Git repo when pushing a darcs patch. I > don't know what it means. > > Simon > > dpush -av > darcs push -av --no-set-default [EMAIL PROTECTED]:/home/darcs/ghc > scp: /home/darcs/ghc/_darcs/format: No such file or directory > scp: /home/darcs/ghc/_darcs/prefs/sources: No such file or directory > We have the following patches to push: > Wed Sep 10 08:35:29 BST 2008 [EMAIL PROTECTED] > * Simplify the type signature for tcPolyBinds > Syncing Git repo. > Finished applying... > Counting objects: 11, done. > Compressing objects: 100% (6/6), done. > Writing objects: 100% (6/6), 991 bytes, done. > Total 6 (delta 5), reused 0 (delta 0) > To [EMAIL PROTECTED]:ghc-hq/ghc.git > fadb176..93e57e1 master -> master > fatal: unable to create '.git/refs/remotes/github/master.lock': Permission > denied > Push successful. > (By the way, the remote repository has 15 patches to pull.) > bash-3.2$ > > _______________________________________________ > Cvs-ghc mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/cvs-ghc > _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
