Setting up external on GitHub

[John Huebner]

I have been trying to set up an external repo for my repo on GitHub but getting nowhere but frustrated.

Hoping to get some help or maybe be told this is a bug that will be fixed:

1) Right click my local repo file
2) TortoiseSVN => Properties
3) New => Externals
4) New...
5) Local Path: trunk/external-repo-name
6) URL: https://github.com/user/external-repo-name/trunk
7) Ok => Ok => Ok
8) Right Click Local Repo Folder => SVN Commit... => Ok

I have tried numerous paths for both local and url. I have tried updating before committing. I've done many cleanups, no luck. Every time I get this error:

Commit failed (details follow): Invalid PROPPATCH path

Please help me before I loose my mind :P

~JH

[Lübbe Onken]

Hi John,

I had a similar problem connecting to Git. I'm not trying to use externals as you are, but I'm monitoring several projects using Stefans Commit Monitor.

Are Git externals supposed to work at all in TortoiseSVN?

Monitoring the InnoSetup repository doesn't work with this URL: <https://github.com/jrsoftware/issrc/trunk>. But when I leave out "trunk" it works in commit monitor <https://github.com/jrsoftware/issrc/>

If I check out the InnoSetup repository with TortoiseSVN, I check out from <https://github.com/jrsoftware/issrc/>

To me this looks like "trunk" is only a virtual folder in Git, but the "real" URL is the one without "trunk"

Cheers
- Lübbe

--
Please help me get more space on Dropbox :)
https://www.dropbox.com/referrals/NTIwMzcxNjI5
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB

[John Huebner]

I've tried the remote path both with and without /trunk, I get the same error. The only thing that works on the local path is trunk/name-of-repo

I can update my local copy of the repo and the external. The error happens when I attempt to commit the update that includes the external.

There are only 2 choices for the URL as far as I know 1) https://github.com/user/repo-name 2) https://github.com/user/repo-name/trunk

John Huebner
Web Applications Developer Site-Seeker, Inc.
Your Partner for Online Success
www.site-seeker.com

[Lübbe Onken]

Hi John,

2014-07-04 15:28 GMT+02:00 John Huebner <johnh...@site-seeker.com>:

I've tried the remote path both with and without /trunk, I get the same error. The only thing that works on the local path is trunk/name-of-repo

I can update my local copy of the repo and the external. The error happens when I attempt to commit the update that includes the external.

There are only 2 choices for the URL as far as I know 1) https://github.com/user/repo-name 2) https://github.com/user/repo-name/trunk

I never tried GIT externals in SVN, so I don't know if they are supposed to work and I'm afraid I can't help you any further. If I understand it correctly, Git wraps everything up so that it is SVN compatible.

Since the error happens, when you try to commit, the next thing that comes to mind is: 

* Do you have write access to the git repository?

* Does this GIT->SVN Wrapper allow write access at all or is it always read-only?

[Simon Large]

On 7 July 2014 07:34, Lübbe Onken <luebbe.to...@gmail.com> wrote:
>
> Hi John,
>
> 2014-07-04 15:28 GMT+02:00 John Huebner <johnh...@site-seeker.com>:
>
>> I've tried the remote path both with and without /trunk, I get the same
>> error. The only thing that works on the local path is trunk/name-of-repo
>>
>> I can update my local copy of the repo and the external. The error happens
>> when I attempt to commit the update that includes the external.
>>
>> There are only 2 choices for the URL as far as I know 1)
>> https://github.com/user/repo-name 2) https://github.com/user/repo-name/trunk
>>
>>
> I never tried GIT externals in SVN, so I don't know if they are supposed to
> work and I'm afraid I can't help you any further. If I understand it
> correctly, Git wraps everything up so that it is SVN compatible.
>
> Since the error happens, when you try to commit, the next thing that comes
> to mind is:
> * Do you have write access to the git repository?
> * Does this GIT->SVN Wrapper allow write access at all or is it always
> read-only?

I don't think git has externals as such. This is using github's
git-svn bridge to allow accessing a git repo via a subversion client.
It's a useful feature and it does allow full read/write access, but
the two systems are fundamentally different and I suspect that
svn:externals is an unsupported feature. I'm not even sure that
subversion properties are supported at all - I'm pretty sure
svn:ignore doesn't work either.

Really you need to ask on the github mailing lists to see what
features their bridge layer does and doesn't support.

Simon

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3084672

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].