Re: [Trac] How does the non-local GIT repository be added to the source browser

[Jun Omae]

On Tue, Aug 8, 2017 at 11:52 AM, Mingxing Tian  wrote:
> This is the log information I see:
>
> 2017-08-08 10:49:17,339 Trac[PyGIT] ERROR: GIT control files missing in 
> '/home/git/repositories/testing.git'
> 2017-08-08 10:49:17,339 Trac[git_fs] ERROR: GitError: GIT control files not 
> found, maybe wrong directory?

Please make sure that your web server can access the git repository.

e.g.

$ (cd / && sudo -u www-data git
--git-dir=/home/git/repositories/testing.git fsck)

-- 
Jun Omae  (大前 潤)

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at https://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Re: [Trac] How does the non-local GIT repository be added to the source browser

[Mingxing Tian]

在 2017年8月8日星期二 UTC+8上午4:05:01，RjOllos写道：
>
>
>
> On Monday, August 7, 2017 at 1:29:48 AM UTC-7, Mingxing Tian wrote:
>>
>>
>>
>> 在 2017年8月4日星期五 UTC+8下午3:16:19，RjOllos写道：
>>>
>>>
>>>
>>> On Thursday, August 3, 2017 at 8:32:40 PM UTC-7, Mingxing Tian wrote:



 在 2017年8月4日星期五 UTC+8上午10:24:47，RjOllos写道：
>
>
> On Thu, Aug 3, 2017 at 7:15 PM, Mingxing Tian  wrote:
>
>>
>>
>> 在 2017年8月4日星期五 UTC+8上午4:25:25，RjOllos写道：
>>
>>>
>>>
>>> On Thursday, August 3, 2017 at 2:58:01 AM UTC-7, Mingxing Tian wrote:



 在 2017年8月3日星期四 UTC+8下午3:34:00，RjOllos写道：
>
>
>
> On Wednesday, August 2, 2017 at 7:13:36 PM UTC-7, Mingxing Tian 
> wrote:
>>
>>
>>
>> 在 2017年8月3日星期四 UTC+8上午12:15:10，RjOllos写道：
>>>
>>>
>>>
>>> On Wed, Aug 2, 2017 at 1:31 AM, Mingxing Tian  
>>> wrote:
>>>
 I use gitolite to manage the Git repository, which 
 automatically creates the results as follows:

 [root@host105 testing.git]# ll
 总用量 32
 drwx--  2 git git 4096 8月   2 11:47 branches
 -rw---  1 git git   66 8月   2 11:47 config
 -rw---  1 git git0 8月   2 15:31 git-daemon-export-ok
 -rw---  1 git git  120 8月   2 15:31 gl-conf
 -rw---  1 git git   23 8月   2 11:47 HEAD
 drwx--  2 git git 4096 8月   2 11:47 hooks
 drwx--  2 git git 4096 8月   2 11:47 info
 drwx-- 14 git git 4096 8月   2 15:52 objects
 drwx--  4 git git 4096 8月   2 11:47 refs

 I added it to the repository and could not find it, it did not 
 work properly.

 And then I see such a sentence in the document, we must convert 
 into a warehouse can be identified.

 Note that the repository should be made accessible as a local 
 repository. Thanks to the distributed nature of Git, that's always 
 possible. If the repository is not already local, simply git 
 clone it.

 I tried to find this method is feasible, but this way need to 
 keep the manual check whether the warehouse update, even if you 
 can write a 
 script to do, I think it is troublesome.

>>>
>>> If your Git repositories are on a different computer than your 
>>> Trac instance, then you must create a clone that is local to your 
>>> Trac 
>>> instance. Is GitoLite running on a different computer?
>>>
>>> To update the clone that is local to your Trac instance you must 
>>> use a notification mechanism. For example, trac-github uses 
>>> GitHub's 
>>> webhook to notify Trac to update the local clone.
>>> https://github.com/trac-hacks/trac-github
>>>
>>> - Ryan 
>>>
>>>
>> I use gitolite to build Git server, it and Trac service in the 
>> same machine above. Is it appropriate to use the trac-github plugin 
>> in this 
>> case?
>>
>
> If Trac and Gitolite are on the same server, you don't need to do 
> anything special to make the repositories available to Trac. Just use 
> an 
> absolute path in the repository path argument. The repositories don't 
> need 
> to be inside the Environment.
>
> - Ryan 
>
>>  
>>
>

 But Trac does not recognize a purely storage type of warehouse, it 
 can only identify the code structure of the warehouse.

>>>
>>> That's incorrect, as noted in my other reply. Trac can read a bare 
>>> repository or one with a working tree.
>>>  
>>>
 Since the repository is created automatically, the conversion to 
 the command line operation should be "git init --bare". 

>>>
>> The deployment on the server has been completed, I successfully 
>> cloned on my computer, so the deployment of Git service is successful.
>>
>> [root@host105 git]# pwd
>> /home/git
>> [root@host105 git]# ll
>> 总用量 20
>> drwxrwxr-x 2 git git 4096 8月   2 11:47 bin
>> drwxrwxr-x 6 git git 4096 8月   2 11:47 gitolite
>> -rw-rw-r-- 1 git git  151 8月   1 18:04 node.txt
>> -rw--- 1 git git   12 8月   2 15:31 projects.list
>> drwx-- 4 git git 4096 8月   2 11:47 repositories
>>
>> The full path to the Trac repository management 
>> is:/home/git/repositories/testing.git
>>
>> [root@host105 git]# ll repositories/
>> 总用量 8
>> drwx-- 8 git git 4096 8月   2 15:31 gitolite-admin.git
>> drwx-- 7 git 

Re: [Trac] How does the non-local GIT repository be added to the source browser

[RjOllos]

On Monday, August 7, 2017 at 1:29:48 AM UTC-7, Mingxing Tian wrote:
>
>
>
> 在 2017年8月4日星期五 UTC+8下午3:16:19，RjOllos写道：
>>
>>
>>
>> On Thursday, August 3, 2017 at 8:32:40 PM UTC-7, Mingxing Tian wrote:
>>>
>>>
>>>
>>> 在 2017年8月4日星期五 UTC+8上午10:24:47，RjOllos写道：


 On Thu, Aug 3, 2017 at 7:15 PM, Mingxing Tian  wrote:

>
>
> 在 2017年8月4日星期五 UTC+8上午4:25:25，RjOllos写道：
>
>>
>>
>> On Thursday, August 3, 2017 at 2:58:01 AM UTC-7, Mingxing Tian wrote:
>>>
>>>
>>>
>>> 在 2017年8月3日星期四 UTC+8下午3:34:00，RjOllos写道：



 On Wednesday, August 2, 2017 at 7:13:36 PM UTC-7, Mingxing Tian 
 wrote:
>
>
>
> 在 2017年8月3日星期四 UTC+8上午12:15:10，RjOllos写道：
>>
>>
>>
>> On Wed, Aug 2, 2017 at 1:31 AM, Mingxing Tian  
>> wrote:
>>
>>> I use gitolite to manage the Git repository, which automatically 
>>> creates the results as follows:
>>>
>>> [root@host105 testing.git]# ll
>>> 总用量 32
>>> drwx--  2 git git 4096 8月   2 11:47 branches
>>> -rw---  1 git git   66 8月   2 11:47 config
>>> -rw---  1 git git0 8月   2 15:31 git-daemon-export-ok
>>> -rw---  1 git git  120 8月   2 15:31 gl-conf
>>> -rw---  1 git git   23 8月   2 11:47 HEAD
>>> drwx--  2 git git 4096 8月   2 11:47 hooks
>>> drwx--  2 git git 4096 8月   2 11:47 info
>>> drwx-- 14 git git 4096 8月   2 15:52 objects
>>> drwx--  4 git git 4096 8月   2 11:47 refs
>>>
>>> I added it to the repository and could not find it, it did not 
>>> work properly.
>>>
>>> And then I see such a sentence in the document, we must convert 
>>> into a warehouse can be identified.
>>>
>>> Note that the repository should be made accessible as a local 
>>> repository. Thanks to the distributed nature of Git, that's always 
>>> possible. If the repository is not already local, simply git 
>>> clone it.
>>>
>>> I tried to find this method is feasible, but this way need to 
>>> keep the manual check whether the warehouse update, even if you can 
>>> write a 
>>> script to do, I think it is troublesome.
>>>
>>
>> If your Git repositories are on a different computer than your 
>> Trac instance, then you must create a clone that is local to your 
>> Trac 
>> instance. Is GitoLite running on a different computer?
>>
>> To update the clone that is local to your Trac instance you must 
>> use a notification mechanism. For example, trac-github uses GitHub's 
>> webhook to notify Trac to update the local clone.
>> https://github.com/trac-hacks/trac-github
>>
>> - Ryan 
>>
>>
> I use gitolite to build Git server, it and Trac service in the 
> same machine above. Is it appropriate to use the trac-github plugin 
> in this 
> case?
>

 If Trac and Gitolite are on the same server, you don't need to do 
 anything special to make the repositories available to Trac. Just use 
 an 
 absolute path in the repository path argument. The repositories don't 
 need 
 to be inside the Environment.

 - Ryan 

>  
>

>>>
>>> But Trac does not recognize a purely storage type of warehouse, it 
>>> can only identify the code structure of the warehouse.
>>>
>>
>> That's incorrect, as noted in my other reply. Trac can read a bare 
>> repository or one with a working tree.
>>  
>>
>>> Since the repository is created automatically, the conversion to the 
>>> command line operation should be "git init --bare". 
>>>
>>
> The deployment on the server has been completed, I successfully cloned 
> on my computer, so the deployment of Git service is successful.
>
> [root@host105 git]# pwd
> /home/git
> [root@host105 git]# ll
> 总用量 20
> drwxrwxr-x 2 git git 4096 8月   2 11:47 bin
> drwxrwxr-x 6 git git 4096 8月   2 11:47 gitolite
> -rw-rw-r-- 1 git git  151 8月   1 18:04 node.txt
> -rw--- 1 git git   12 8月   2 15:31 projects.list
> drwx-- 4 git git 4096 8月   2 11:47 repositories
>
> The full path to the Trac repository management 
> is:/home/git/repositories/testing.git
>
> [root@host105 git]# ll repositories/
> 总用量 8
> drwx-- 8 git git 4096 8月   2 15:31 gitolite-admin.git
> drwx-- 7 git git 4096 8月   2 15:52 testing.git
>
> But I get an error message: InvalidRepository: 
> /home/git/repositories/testing.git does not appear to be a Git repository.
>
>
> 

Re: [Trac] How does the non-local GIT repository be added to the source browser

[Mingxing Tian]

在 2017年8月4日星期五 UTC+8下午3:16:19，RjOllos写道：
>
>
>
> On Thursday, August 3, 2017 at 8:32:40 PM UTC-7, Mingxing Tian wrote:
>>
>>
>>
>> 在 2017年8月4日星期五 UTC+8上午10:24:47，RjOllos写道：
>>>
>>>
>>> On Thu, Aug 3, 2017 at 7:15 PM, Mingxing Tian  wrote:
>>>


 在 2017年8月4日星期五 UTC+8上午4:25:25，RjOllos写道：

>
>
> On Thursday, August 3, 2017 at 2:58:01 AM UTC-7, Mingxing Tian wrote:
>>
>>
>>
>> 在 2017年8月3日星期四 UTC+8下午3:34:00，RjOllos写道：
>>>
>>>
>>>
>>> On Wednesday, August 2, 2017 at 7:13:36 PM UTC-7, Mingxing Tian 
>>> wrote:



 在 2017年8月3日星期四 UTC+8上午12:15:10，RjOllos写道：
>
>
>
> On Wed, Aug 2, 2017 at 1:31 AM, Mingxing Tian  
> wrote:
>
>> I use gitolite to manage the Git repository, which automatically 
>> creates the results as follows:
>>
>> [root@host105 testing.git]# ll
>> 总用量 32
>> drwx--  2 git git 4096 8月   2 11:47 branches
>> -rw---  1 git git   66 8月   2 11:47 config
>> -rw---  1 git git0 8月   2 15:31 git-daemon-export-ok
>> -rw---  1 git git  120 8月   2 15:31 gl-conf
>> -rw---  1 git git   23 8月   2 11:47 HEAD
>> drwx--  2 git git 4096 8月   2 11:47 hooks
>> drwx--  2 git git 4096 8月   2 11:47 info
>> drwx-- 14 git git 4096 8月   2 15:52 objects
>> drwx--  4 git git 4096 8月   2 11:47 refs
>>
>> I added it to the repository and could not find it, it did not 
>> work properly.
>>
>> And then I see such a sentence in the document, we must convert 
>> into a warehouse can be identified.
>>
>> Note that the repository should be made accessible as a local 
>> repository. Thanks to the distributed nature of Git, that's always 
>> possible. If the repository is not already local, simply git 
>> clone it.
>>
>> I tried to find this method is feasible, but this way need to 
>> keep the manual check whether the warehouse update, even if you can 
>> write a 
>> script to do, I think it is troublesome.
>>
>
> If your Git repositories are on a different computer than your 
> Trac instance, then you must create a clone that is local to your 
> Trac 
> instance. Is GitoLite running on a different computer?
>
> To update the clone that is local to your Trac instance you must 
> use a notification mechanism. For example, trac-github uses GitHub's 
> webhook to notify Trac to update the local clone.
> https://github.com/trac-hacks/trac-github
>
> - Ryan 
>
>
 I use gitolite to build Git server, it and Trac service in the same 
 machine above. Is it appropriate to use the trac-github plugin in this 
 case?

>>>
>>> If Trac and Gitolite are on the same server, you don't need to do 
>>> anything special to make the repositories available to Trac. Just use 
>>> an 
>>> absolute path in the repository path argument. The repositories don't 
>>> need 
>>> to be inside the Environment.
>>>
>>> - Ryan 
>>>
  

>>>
>>
>> But Trac does not recognize a purely storage type of warehouse, it 
>> can only identify the code structure of the warehouse.
>>
>
> That's incorrect, as noted in my other reply. Trac can read a bare 
> repository or one with a working tree.
>  
>
>> Since the repository is created automatically, the conversion to the 
>> command line operation should be "git init --bare". 
>>
>
 The deployment on the server has been completed, I successfully cloned 
 on my computer, so the deployment of Git service is successful.

 [root@host105 git]# pwd
 /home/git
 [root@host105 git]# ll
 总用量 20
 drwxrwxr-x 2 git git 4096 8月   2 11:47 bin
 drwxrwxr-x 6 git git 4096 8月   2 11:47 gitolite
 -rw-rw-r-- 1 git git  151 8月   1 18:04 node.txt
 -rw--- 1 git git   12 8月   2 15:31 projects.list
 drwx-- 4 git git 4096 8月   2 11:47 repositories

 The full path to the Trac repository management 
 is:/home/git/repositories/testing.git

 [root@host105 git]# ll repositories/
 总用量 8
 drwx-- 8 git git 4096 8月   2 15:31 gitolite-admin.git
 drwx-- 7 git git 4096 8月   2 15:52 testing.git

 But I get an error message: InvalidRepository: 
 /home/git/repositories/testing.git does not appear to be a Git repository.