My understanding (and the way we use it when monkey patching for
instance) is that whenevery you apply new security to a class, you
create a new ClassSecurityInfo on it. It only defines new stuff
to do. The real synthesized security is still stored in
__ac_permissions__.
Yes, your
Dieter Maurer wrote:
You could use part of the old style initialization, the methods
declaration to be precise.
You see an example in .../Products/ZSQLMethods/__init__.py.
Be warned, however: the old style initialization puts
the declared methods on the OFS.Folder class.
Yeah, I thought
I'm trying to fix a bug assigned to me, and for some reason
I can use svn to make and check out my branch but it fails when fetching
externals. Anybody else seen this?
[EMAIL PROTECTED] tmp]$ svn co
svn+ssh://[EMAIL PROTECTED]/repos/main/Zope/branches/slinkp-collector_1895
A
btw, I'm in #zope-dev right now if anybody wants to chat about this.
-PW
Paul Winkler said:
I'm trying to fix a bug assigned to me, and for some reason
I can use svn to make and check out my branch but it fails when fetching
externals. Anybody else seen this?
(snip)
--
Paul Winkler
Update: I *can* fetch the externals from a different box
(my windows laptop, on which i can't successfully build zope
because cygwin's python is known-broken and I don't have a C
compiler other than cygwin's.)
But when I ssh to a linux box (on which building works fine),
I get the problem
On 9/30/05, Paul Winkler [EMAIL PROTECTED] wrote:
One thing Tino suggested: it might be a firewall issue.
Does svn's externals-fetching look somehow different to a firewall
than does a regular (non-external) checkout?
When I tried checking out on my laptop, I noticed that ZoneAlarm asked 'me
Hypothesis:
Is it possible that svn.zope.org is configured such that when you get
the externals, it uses plain svn (i.e. an anonymous checkout)
rather than svn+ssh?
If so, I bet that's the answer: our firewall is blocking svn
but allowing svn+ssh.
Can anybody confirm that this is a likely
On 9/30/05, Paul Winkler [EMAIL PROTECTED] wrote:
Hypothesis:
Is it possible that svn.zope.org is configured such that when you get
the externals, it uses plain svn (i.e. an anonymous checkout)
rather than svn+ssh?
As noted, very likely. The default port for SVN w/out SSH is 3690:
On Fri, Sep 30, 2005 at 04:27:47PM -0400, Fred Drake wrote:
| On 9/30/05, Paul Winkler [EMAIL PROTECTED] wrote:
| Hypothesis:
| Is it possible that svn.zope.org is configured such that when you get
| the externals, it uses plain svn (i.e. an anonymous checkout)
| rather than svn+ssh?
|
| As
Aha! Thanks very much Fred, this arrived just after I sent a message
asking for confirmation of exactly that :-)
Looks like it's the standard 3690 port, I'll go talk to our poor
beleaguered admins... thanks again!
-PW
Fred Drake said:
On 9/30/05, Paul Winkler [EMAIL PROTECTED] wrote:
One
Paul Winkler wrote:
Update: I *can* fetch the externals from a different box
(my windows laptop, on which i can't successfully build zope
because cygwin's python is known-broken and I don't have a C
compiler other than cygwin's.)
That's no excuse ;)
You can build Zope on Windows easily with
11 matches
Mail list logo
