|
»
« Return to Thread: libpng.git hosting via sourceforge
Re: libpng.git hosting via sourceforge
by Brandon Casey-3
::
Rate this Message:
On Sat, Mar 7, 2009 at 11:50 PM, Bob Friesenhahn
<bfriesen@...> wrote:
> On Sat, 7 Mar 2009, Bob Friesenhahn wrote:
>>
>> What I can say is that 'git.simplesystems.org' responds on port 9418 to GIT
>> requests and that there is a 'libpng.git' available with libpng files of some
>> vintage. Maybe it will work for someone who knows the correct incantation.
>
> Ok, I tried
>
> % git clone git://git.simplesystems.org/libpng.git
> Initialized empty Git repository in /home/bfriesen/tmp/libpng/.git/
> fatal: The remote end hung up unexpectedly
> fetch-pack from 'git://git.simplesystems.org/libpng.git' failed.
>
> And checked the system log and see this error message:
>
> '/serve/git/libpng.git/.git': repository not exported.
>
> So apparently some extra magical step needs to be taken to prepare the
> files for use. The files are just a straight copy of Glenn's
> repository.
Possibly the 'git-daemon-export-ok' file does not exist. This is
indeed a magic file
which indicates to git-daemon that the repository should be exported.
Usually, this would do the trick (but see below first):
touch /serve/git/libpng.git/git-daemon-export-ok
BUT, it looks like the repository above is not a bare repository. A
bare repository is a
repository without a working directory. Basically, it is _just_ the
'.git' directory, but usually
named <proj_name>.git. The reason I think so is because of the path in
your error message above which ends with '.git'. This is how a
regular repository would
look, like the one you would get after a clone, which is ready for
developing in. You can tell
the difference by looking in the libpng.git directory. If the libpng
source files are there,
then it is not a bare repository.
So, maybe the export-ok file needs to be created one directory down,
in the .git directory, like:
touch /serve/git/libpng.git/.git/git-daemon-export-ok
Or, you can create a bare repository, which I think is the better thing to do.
It's easy to make a bare repository. Just move the existing
repository out of the
way, and create a bare clone. Like:
cd /serve/git/
mv libpng.git <somewhere>
git clone --bare <somewhere>/libpng.git libpng.git
Then, create the git-daemon-export-ok file
touch libpng.git/git-daemon-export-ok
-brandon
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement
<bfriesen@...> wrote:
> On Sat, 7 Mar 2009, Bob Friesenhahn wrote:
>>
>> What I can say is that 'git.simplesystems.org' responds on port 9418 to GIT
>> requests and that there is a 'libpng.git' available with libpng files of some
>> vintage. Maybe it will work for someone who knows the correct incantation.
>
> Ok, I tried
>
> % git clone git://git.simplesystems.org/libpng.git
> Initialized empty Git repository in /home/bfriesen/tmp/libpng/.git/
> fatal: The remote end hung up unexpectedly
> fetch-pack from 'git://git.simplesystems.org/libpng.git' failed.
>
> And checked the system log and see this error message:
>
> '/serve/git/libpng.git/.git': repository not exported.
>
> So apparently some extra magical step needs to be taken to prepare the
> files for use. The files are just a straight copy of Glenn's
> repository.
Possibly the 'git-daemon-export-ok' file does not exist. This is
indeed a magic file
which indicates to git-daemon that the repository should be exported.
Usually, this would do the trick (but see below first):
touch /serve/git/libpng.git/git-daemon-export-ok
BUT, it looks like the repository above is not a bare repository. A
bare repository is a
repository without a working directory. Basically, it is _just_ the
'.git' directory, but usually
named <proj_name>.git. The reason I think so is because of the path in
your error message above which ends with '.git'. This is how a
regular repository would
look, like the one you would get after a clone, which is ready for
developing in. You can tell
the difference by looking in the libpng.git directory. If the libpng
source files are there,
then it is not a bare repository.
So, maybe the export-ok file needs to be created one directory down,
in the .git directory, like:
touch /serve/git/libpng.git/.git/git-daemon-export-ok
Or, you can create a bare repository, which I think is the better thing to do.
It's easy to make a bare repository. Just move the existing
repository out of the
way, and create a bare clone. Like:
cd /serve/git/
mv libpng.git <somewhere>
git clone --bare <somewhere>/libpng.git libpng.git
Then, create the git-daemon-export-ok file
touch libpng.git/git-daemon-export-ok
-brandon
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
png-mng-implement mailing list
png-mng-implement@...
https://lists.sourceforge.net/lists/listinfo/png-mng-implement
« Return to Thread: libpng.git hosting via sourceforge
| Free embeddable forum powered by Nabble | Forum Help |
