On 8/22/05, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> James Y Knight wrote:
> > It seems a waste to use SVN's webdav support just for anon access.
> > The svnserve method works well for anon access. The only reason to
> > use svn webdav IMO is if you want to use that for authenticated
> > acce
Barry Warsaw wrote:
>>Not sure what "the right place" would be: [EMAIL PROTECTED]
>>I think the email could look any way we want it to look.
>
>
> I think it should be @python.org where is the
> firstname.lastname (with some exceptions) scheme that we've agreed on.
> I actually /don't/ want all
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
> > It worked. I made a trivial change to Misc/NEWS and checked it in. I then
> > ran "svn blame NEWS" to see what it showed. This took approximately
> > forever. Can I assume this is one thing svn is always going to be p
[EMAIL PROTECTED] wrote:
> It worked. I made a trivial change to Misc/NEWS and checked it in. I then
> ran "svn blame NEWS" to see what it showed. This took approximately
> forever. Can I assume this is one thing svn is always going to be pretty
> slow at?
Yes. Somebody commented that this is
Phillip J. Eby wrote:
> You can do that with viewcvs, too. Viewcvs can also create tarballs for
> easy downloading, and has a lot of browsing and viewing options that the
> SVN webdav mode doesn't.
True. I had some issues with viewcvs, though: you cannot provide access
control easily, as you cann
>> I think until this experiment is over and we have really and truly
>> migrated to svn I will simply let other people fuss with things.
Martin> Well, you are not required to understand it, but you should try
Martin> to use it.
Good point.
Martin> Just check out
Martin
At 06:23 PM 8/22/2005 +0200, Martin v. Löwis wrote:
>James Y Knight wrote:
> > It seems a waste to use SVN's webdav support just for anon access.
> > The svnserve method works well for anon access. The only reason to
> > use svn webdav IMO is if you want to use that for authenticated
> > access. Bu
On Mon, 2005-08-22 at 12:16, "Martin v. Löwis" wrote:
> Barry Warsaw wrote:
> > I think technically, the answer to that is "yes", you will automatically
> > get access to the source repo.
>
> At the moment, the answer actually is "no". For the projects repository,
> there is no group write permiss
James Y Knight wrote:
> It seems a waste to use SVN's webdav support just for anon access.
> The svnserve method works well for anon access. The only reason to
> use svn webdav IMO is if you want to use that for authenticated
> access. But since you're talking about using svn+ssh for that..
[EMAIL PROTECTED] wrote:
> More confusion here. If I use some sort of shared access how will the
> system ascribe changes I make to me and not, for example, Martin?
In pythondev's authorized_keys2, we have a line
command="/usr/bin/svnserve --root=/data/repos/projects -t
--tunnel-user 'Skip Monta
Barry Warsaw wrote:
> I think technically, the answer to that is "yes", you will automatically
> get access to the source repo.
At the moment, the answer actually is "no". For the projects repository,
there is no group write permission - you must be pythondev in order to
write.
> The question I h
Aahz wrote:
> Yes, I know -- but it looks like a mistake to me. Are you saying that
> all shell access will be done through a single account? Isn't that a
> huge security risk? My understanding was that it was SVN access that
> would be going through a single account, not shell access.
Only few
[EMAIL PROTECTED] wrote:
> I'm completely confused about what, if anything, I need to send to you. I
> can already access the python.org website repository via svn.
Yes, but you do so using username/password, right? pythondev will be
using svn+ssh.
> Will I
> automatically get access to the new
On Aug 22, 2005, at 11:32 AM, Barry Warsaw wrote:
> They are the same machine, with different IP addresses. Anonymous
> webdav will require two Apache processes, since different user/groups
> are needed and to support different certs for svn.python.org and
> (eventually) www.python.org.
>
It see
>> Will I automatically get access to the new Python source repository
>> or do I need to send you pub key(s)?
Barry> I think technically, the answer to that is "yes", you will
Barry> automatically get access to the source repo.
Okay...
Barry> The question I have is whether
On Mon, 2005-08-22 at 11:18, [EMAIL PROTECTED] wrote:
> I'm completely confused about what, if anything, I need to send to you. I
> can already access the python.org website repository via svn. Will I
> automatically get access to the new Python source repository or do I need to
> send you pub k
On Mon, Aug 22, 2005, "Martin v. L?wis" wrote:
> Aahz wrote:
>>Barry:
>>>Martin:
Host pythondev
Hostname dinsdale.python.org
User pythondev
IdentityFile ~/.ssh/pythondev
>>>I'm confused again; are you saying that we should have a host named
>>>pythondev.python.org?
Martin,
I'm completely confused about what, if anything, I need to send to you. I
can already access the python.org website repository via svn. Will I
automatically get access to the new Python source repository or do I need to
send you pub key(s)? Are dinsdale.python.org and svn.python.org th
Barry Warsaw wrote:
>>You could do that (or use the root account); I can't: I don't have
>>a ssh account on dinsdale. An even if I had, I couldn't write to
>>pythondev's authorized_keys2.
>
>
> That's easily rectified! :) We should give you an account and sudo
> access. Should I just use your k
Aahz wrote:
>>>Host pythondev
>>> Hostname dinsdale.python.org
>>> User pythondev
>>> IdentityFile ~/.ssh/pythondev
>>>
>>I'm confused again; are you saying that we should have a host named
>>pythondev.python.org? I'm not sure that's necessary.
>
>
> No, pythondev is simply an SSH alias for d
Barry Warsaw wrote:
> I may be totally misunderstanding, but to get shell access wouldn't I
> avoid using the pythondev account and just use my own account?
You could do that (or use the root account); I can't: I don't have
a ssh account on dinsdale. An even if I had, I couldn't write to
pythondev
On Sun, Aug 21, 2005, Barry Warsaw wrote:
> On Sun, 2005-08-21 at 09:12, "Martin v. L?wis" wrote:
>>
>> I would suggest that the default key is used for regular commits,
>> and a separate key is created for shell access. I described this
>> a bit in the PEP, essentially, in .ssh/config, I have
>>
On Sun, 2005-08-21 at 09:12, "Martin v. Löwis" wrote:
> It turns out that svn+ssh with a single account has limitations:
> you can only set the tunnel user when you are using a restricted
> key. In PEP 347, the plan is that the current SF project admins
> get shell access to the pythondev account,
23 matches
Mail list logo
