bruno1505 / pyetv

Automatically exported from code.google.com/p/pyetv
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

svn checkout requires frontpython authentication #15

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Attempt anonymous SVN checkout

What is the expected output? What do you see instead?
Successful checkout is expected; however, checkout fails because of the 
external SVN 
dependency on frontpython requiring authentication:

$ svn checkout http://pyetv.googlecode.com/svn/trunk pyetv
Fetching external item into 'pyetv/PyFR'
Authentication realm: <https://frontpython.googlecode.com:443> Google Code 
Subversion 
Repository
[...]
svn: PROPFIND request failed on '/svn/trunk/SDK/PyFR'
svn: PROPFIND of '/svn/trunk/SDK/PyFR': authorization failed 
(https://frontpython.googlecode.com)

What version of the product are you using? On what operating system?
N/A

Please provide any additional information below.
If you change the frontpython SVN URL to 
http://frontpython.googlecode.com/svn/trunk/SDK/PyFR (instead of https) a 
successful 
anonymous checkout should be possible.

Original issue reported on code.google.com by shin...@gmail.com on 27 Dec 2008 at 11:21

GoogleCodeExporter commented 8 years ago
Just change /svn/trunk/.svn/dir-prop-base so it reads

V 58
PyFR http://frontpython.googlecode.com/svn/trunk/SDK/PyFR

rather than 

V 59
PyFR https://frontpython.googlecode.com/svn/trunk/SDK/PyFR

Fixed here [locally], but to do so,  you must use 'svn checkout 
--ignore-externals http://pyetv.googlecode.com/svn/trunk pyetv', edit the file, 
then .svn up'. This should be fixed on the server.

Original comment by d235...@gmail.com on 22 Mar 2009 at 6:28

GoogleCodeExporter commented 8 years ago
I personally have write access to the frontpython repo, and so my dev 
environment
has PyFR checked out via https so that I can commit changes.

Of course that breaks it for the rest of the world.  Great.

If anyone has a better svn-foo than I do and can tell me how to set 
this up so that I:

1) don't have to maintain a separate tree
2) can commit to both PyeTV and PyFR from the same source tree.
3) can set up the PyeTV dependency on PyFR in svn.

I'd appreciate it.

Original comment by jon.chri...@gmail.com on 26 Mar 2009 at 1:20

GoogleCodeExporter commented 8 years ago
Why make it so complicated???  It doesn't seem so smart.
I just want to download some files, but now I have already wasted hours on 
trying to 
download, install and run some kind of rediculous SVN client. Who is 
responsible for 
all this? Probably some "smart" Linux hacker who hates userfriendly software.
Einstein said: Keep it simple!

Original comment by nilsthor...@gmail.com on 31 Mar 2009 at 5:30

GoogleCodeExporter commented 8 years ago
nilsthorell,

I think you meant to say "Thank you for using your limited free time to provide 
me
useful software free of cost".

If you want simple, download the binary which I, personally, have no use for, 
but go
out of my way to provide as a public service.

If you want to hack on the source, then I'm afraid you'll have to learn the
development tools, which google has selected and hosted as a public service.

And finally, for your information, there are many user friendly svn clients out
there.  A google search for "mac svn" turns up many.

Original comment by jon.chri...@gmail.com on 1 Apr 2009 at 4:56

GoogleCodeExporter commented 8 years ago
If you modify the svn to use http, perhaps you could  check out PyFR seperately 
and symlink the required 
directory into your build tree, in place of the one you checked out as the 
external for PyeTV.  Then it would check 
out right for others.

Just a thought. Thanks for doing this.

Bill

Original comment by w.northc...@unsw.edu.au on 27 Dec 2009 at 2:20