Bug 1391253 - git-daemon does not allow shallow clone from read-only repository
Summary: git-daemon does not allow shallow clone from read-only repository
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: git
Version: git19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 2.2
Assignee: Petr Stodulka
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On: 1269138
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-02 21:09 UTC by Frank Ch. Eigler
Modified: 2016-11-28 23:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1269138
Environment:
Last Closed: 2016-11-28 23:21:48 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2016-11-02 21:09:33 UTC
Noticing this on 

git19-git.x86_64   1.9.4-4.el6.1       @rhel-x86_64-server-6-rhscl-1          


+++ This bug was initially created as a clone of Bug #1269138 +++

[dwoodhou@i7 tmp]$ git clone --depth 1 git://git.infradead.org/l2-mtd.git
Cloning into 'l2-mtd'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed


Oct  6 05:31:59 bombadil git-daemon[8837]: fatal: Unable to create temporary file '/srv/git/l2-mtd.git/shallow_2E9NkF': Permission denied
Oct  6 05:31:59 bombadil xinetd[7097]: EXIT: git status=128 pid=8837 duration=1(sec)


Perhaps relevant:
http://git.661346.n2.nabble.com/PATCH-upload-pack-allow-shallow-fetching-from-a-read-only-repository-td7604326.html

--- Additional comment from Fedora Admin XMLRPC Client on 2016-03-16 14:23:52 EDT ---

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

--- Additional comment from  on 2016-07-01 05:44:25 EDT ---

Hi David,
it works for me with current git (was rebased since report of the bug), so I am closing this, but feel free to reopen if You reproduce again.

Comment 1 Petr Stodulka 2016-11-28 23:21:48 UTC
Hi Frank.
As I see, you reported this issue for git19-git that is EOL and will
not be updated anymore. However, the issue is resolved in new rh-git29 collection already.


Note You need to log in before you can comment on or make changes to this bug.