Re: [Zope] attribute/name error after server migration… please advise?

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 01:51 PM, Dan Gaibel wrote: in the debugger I get type 'ImplicitAcquirerWrapper' for app.asian.courses.be type. Same as other folder objects on the site, even those that are fully funtional. I should have figured. Try:

Re: [Zope] attribute/name error after server migration… please advise?

2013-01-10 Thread Dan Gaibel
type(courses.aq_self) yields: class 'OFS.Folder.Folder' print app.asian.courses._objects gives me: ({'meta_type': 'Folder', 'id': 'falcon'}, {'meta_type': 'ProgramPage', 'id': 'japanese'}, {'meta_type': 'ProgramPage', 'id': 'burmese'}, {'meta_type': 'ProgramPage', 'id': 'korean'},

Re: [Zope] attribute/name error after server migration… please advise?

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 02:57 PM, Dan Gaibel wrote: 2013-01-10 14:23:12 WARNING ZODB Could not import class 'GroupUserFolder' from module 'Products.GroupUserFolder.GroupUserFolder' That is the smoking gun: your new instance is missing the

Re: [Zope] attribute/name error after server migration… please advise?

2013-01-10 Thread Dan Gaibel
That's it! Fixed! Many, many thanks, Tres. You saved me. Cheers! On Jan 10, 2013, at 2:58 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 02:57 PM, Dan Gaibel wrote: 2013-01-10 14:23:12 WARNING ZODB Could not import class

Re: [Zope] attribute/name error after server migration… please advise?

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 03:58 PM, Dan Gaibel wrote: That's it! Fixed! Many, many thanks, Tres. You saved me. Cheers! Glad that helped. Tres. - -- === Tres Seaver +1 540-429-0999

[Zope-dev] Status of github migration

2013-01-10 Thread Patrick Gerken
Hi, I wanted to fix some logging in Products.SiteErrorLog, but I am confused where to go to. zopefoundation on github has a small number of repos but not Products.SiteErrorLog. http://svn.zope.org shows me a web view of our old cvs server. There is something wrong. Can I help with something?

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Alexandre Garel
Le 10/01/2013 11:23, Patrick Gerken a écrit : Hi, I wanted to fix some logging in Products.SiteErrorLog, but I am confused where to go to. here it is, part of Zope module : http://svn.zope.org/Zope/trunk/src/Products/SiteErrorLog/ ___ Zope-Dev

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jens Vagelpohl
On Jan 10, 2013, at 11:23 , Patrick Gerken do3cc...@googlemail.com wrote: I wanted to fix some logging in Products.SiteErrorLog, but I am confused where to go to. zopefoundation on github has a small number of repos but not Products.SiteErrorLog. http://svn.zope.org shows me a web view

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Patrick Gerken
Following your link it works for me too. Turned out I use a firefox plugin that if I enter a url without specifying a protocol, it tries https first. https://svn.zope.org redirects to the cvs. Regarding repos, I once did a full git mirror of the full svn.zope.org. I try to see if I can recreate

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Sebastien Douche
On Thu, Jan 10, 2013 at 11:48 AM, Jens Vagelpohl j...@dataflake.org wrote: The GitHub migration happens on an as-needed basis. Don't see the point, why not migrate all active packages (aka the ZTK + ZopeApp)? -- Sebastien Douche sdou...@gmail.com Twitter: @sdouche / G+: +sdouche

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jim Fulton
On Thu, Jan 10, 2013 at 5:48 AM, Jens Vagelpohl j...@dataflake.org wrote: On Jan 10, 2013, at 11:23 , Patrick Gerken do3cc...@googlemail.com wrote: I wanted to fix some logging in Products.SiteErrorLog, but I am confused where to go to. zopefoundation on github has a small number of repos

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jens Vagelpohl
On Jan 10, 2013, at 14:37 , Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 5:48 AM, Jens Vagelpohl j...@dataflake.org wrote: For those packages that are fully migrated you will have obvious markers on the package in svn.zope.org, such as the package being read-only. I don't think

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jens Vagelpohl
On Jan 10, 2013, at 14:45 , Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 8:39 AM, Jens Vagelpohl j...@dataflake.org wrote: On Jan 10, 2013, at 14:37 , Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 5:48 AM, Jens Vagelpohl j...@dataflake.org wrote: For those packages

[Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Jim Fulton
I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in github - Copy above file to root of project. - Make project read

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Brian Sutherland
On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Leonardo Rochael Almeida
Hi Jens, On Thu, Jan 10, 2013 at 11:47 AM, Jens Vagelpohl j...@dataflake.org wrote: [...] All other repositories (Zope, Products.*) were test migrations where I asked for feedback and never got any. They are throw-away and not final. The only finished migrations are yours and Tres'. I've

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jens Vagelpohl
On Jan 10, 2013, at 15:40 , Leonardo Rochael Almeida leoroch...@gmail.com wrote: I took a quick look at the Zope migration now and I think it's excellent. The only thing I'd add is that I'd also migrate branches 2.12 and 2.13 branches since they're all active, even if just for bug/security

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jim Fulton
On Thu, Jan 10, 2013 at 9:50 AM, Jens Vagelpohl j...@dataflake.org wrote: On Jan 10, 2013, at 15:40 , Leonardo Rochael Almeida leoroch...@gmail.com wrote: I took a quick look at the Zope migration now and I think it's excellent. The only thing I'd add is that I'd also migrate branches 2.12

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Patrick Gerken
I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a specific revision. I run a CI tool and it is broken already because apparently a trunk has been deleted already. Thats not a bug, thats why I run the CI Tool. Would be stupid if I

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Hanno Schlichting
On Thu, Jan 10, 2013 at 3:59 PM, Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 9:50 AM, Jens Vagelpohl j...@dataflake.org wrote: I did not choose to include or exclude any branch. The test migration uses the package used to migrate most Plone packages from SVN to GitHub, which

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 07:02 AM, Sebastien Douche wrote: On Thu, Jan 10, 2013 at 11:48 AM, Jens Vagelpohl j...@dataflake.org wrote: The GitHub migration happens on an as-needed basis. Don't see the point, why not migrate all active packages (aka the

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 09:15 AM, Jim Fulton wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 10:42 AM, Patrick Gerken wrote: I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a specific revision. I run a CI tool and it is broken already because apparently a

Re: [Zope-dev] zope-tests - FAILED: 14, OK: 15

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/09/2013 08:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 135 https://mail.zope.org/pipermail/zope-tests/2013-January/071231.html [2]FAILED Still Failing - zopetoolkit_trunk_app -

Re: [Zope-dev] zope-tests - FAILED: 14, OK: 15

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 12:15 PM, Tres Seaver wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 135 https://mail.zope.org/pipermail/zope-tests/2013-January/071231.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build #

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jim Fulton
On Thu, Jan 10, 2013 at 10:54 AM, Hanno Schlichting ha...@hannosch.eu wrote: On Thu, Jan 10, 2013 at 3:59 PM, Jim Fulton j...@zope.com wrote: On Thu, Jan 10, 2013 at 9:50 AM, Jens Vagelpohl j...@dataflake.org wrote: I did not choose to include or exclude any branch. The test migration uses

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Matthew Wilkes
Tres Seaver wrote: Because it is a helluva lot of work, which can't be trivially scripted (things can go wrong: each project needs a person who knows it well to review the migrated repo). When Plone did this the people involved wrote some scripts https://github.com/plone/svn-migrate I'm

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Jens Vagelpohl
On Jan 10, 2013, at 21:02, Matthew Wilkes matt...@matthewwilkes.co.uk wrote: When Plone did this the people involved wrote some scripts https://github.com/plone/svn-migrate That stuff works only partially. It uses a GitHub API that has been removed months ago. I migrated the Zope package

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Marius Gedminas
On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Jim Fulton
On Thu, Jan 10, 2013 at 12:02 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 10:42 AM, Patrick Gerken wrote: I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 03:02 PM, Matthew Wilkes wrote: Tres Seaver wrote: Because it is a helluva lot of work, which can't be trivially scripted (things can go wrong: each project needs a person who knows it well to review the migrated repo). When

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 03:16 PM, Marius Gedminas wrote: On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? +1

Re: [Zope-dev] Status of github migration

2013-01-10 Thread Matthew Wilkes
Tres Seaver wrote: What is needed is not scripts, but eyeballs: we need people who know the various packages and*care* about getting them migrated to github to step up. Softwward which doesn't have a champion willing to do the work should stay behind on SVN. The community as a whole cares

[Zope-dev] zope-tests - FAILED: 24, OK: 15

2013-01-10 Thread Zope tests summarizer
This is the summary for test reports received on the zope-tests list between 2013-01-09 00:00:00 UTC and 2013-01-10 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: