[Zope-dev] Status of github migration
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? Best regards, Patrick ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 of our old cvs server. There is something wrong. Can I help with something? Going to http://svn.zope.org works fine for me. I see the expected SVN repositories. The GitHub migration happens on an as-needed basis. Package maintainers may request to have packages migrated or, like Jim and Tres are already doing, migrate packages themselves. There is no full migration of all svn.zope.org content. 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. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 single repos from it by moving stuff around and modifying the history. git svn clone is dog slow with svn.zope.org. On Thu, Jan 10, 2013 at 11: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 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? Going to http://svn.zope.org works fine for me. I see the expected SVN repositories. The GitHub migration happens on an as-needed basis. Package maintainers may request to have packages migrated or, like Jim and Tres are already doing, migrate packages themselves. There is no full migration of all svn.zope.org content. 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. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 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? Going to http://svn.zope.org works fine for me. I see the expected SVN repositories. The GitHub migration happens on an as-needed basis. Package maintainers may request to have packages migrated or, like Jim and Tres are already doing, migrate packages themselves. There is no full migration of all svn.zope.org content. 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 being read only is enough. Are people supposed to attempt commits to find out if a project is read-only? We should at least leave something like a MOVED_TO_GITHUB file in the project, in addition to making it read only. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 being read only is enough. Are people supposed to attempt commits to find out if a project is read-only? We should at least leave something like a MOVED_TO_GITHUB file in the project, in addition to making it read only. That's what I meant by obvious marker, such as I did not imply making a package read-only is the only marker. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 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 being read only is enough. Are people supposed to attempt commits to find out if a project is read-only? We should at least leave something like a MOVED_TO_GITHUB file in the project, in addition to making it read only. That's what I meant by obvious marker, such as I did not imply making a package read-only is the only marker. But that's all that has been done for some projects. (Sorry, I don't mean to be critical and I didn't raise the issue when it happened.) OTOH, it's been argued (I disagree :) that I did too much for the ZODB projects. I think it would be helpful if we agreed on what should done, so we have a standard play book. Please get in touch with Tres if you think his migrations should be improved. 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'. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] How to signal that projects have moved to github
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 only An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? There are a lot of other details of the migration that need to be worked out, like how folks should request migration and automating the conversion further. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
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 github - Copy above file to root of project. - Make project read only +1 An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Maybe a bit draconian at this stage? This could perhaps be done much later in the migration by scripting the removal of all trunks with a MOVED_TO_GITHUB file. Thoughts? There are a lot of other details of the migration that need to be worked out, like how folks should request migration and automating the conversion further. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) -- Brian Sutherland ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 been overly busy with these last couple of monks with job change/country relocation/new year, so I couldn't review those migrations before. 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 fixes. Having those branches means that back/forward-porting fixes is easier. Although we could always recreate the branches based on the tags, which were also nicely migrated. I think you mentioned this before, but I couldn't find it in a quick archive search, but which script did you use for those migrations? Thanks for all the work! And thanks also for the very nice mirror at: git.zope.org Cheers, Leo jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 fixes.
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 uses
svn2git underneath. If there's whole branches missing the migration has
obviously failed.
If you want to help you could try a migration with the attached Python script
that Jim wrote as a result of finding bugs in svn2git. I can provide you with a
suitable authors mapping file.
jens
##
#
# Copyright (c) 2012 Zope Foundation and Contributors.
# All Rights Reserved.
#
# This software is subject to the provisions of the Zope Public License,
# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution.
# THIS SOFTWARE IS PROVIDED AS IS AND ANY AND ALL EXPRESS OR IMPLIED
# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
# FOR A PARTICULAR PURPOSE.
#
##
%prog [options] subversion_url
svn to git conversion helper
Based loosely on the svn2git ruby tool.
You must have git and the svn git plugin installed.
A repository directory will be created with a name derived from the
subversion URL.
The subversion URL must point to a subversion project with a standard
layout, with trunk, branches, and tags.
import optparse
parser = optparse.OptionParser(__doc__)
githelp=
Create a github repository. The argument is a string of the form
DEST/token. where DEST is either 'users/USERNAME' or 'orgs/ORGNAME' and
token is a github OAuth token:
https://help.github.com/articles/creating-an-oauth-token-for-command-line-use
curl must be installed if you use this.
parser.add_option('--github', '-g', help=githelp)
parser.add_option('--restart', '-r', action='store_true',
help=Restart after fetch times out)
parser.add_option(
'--authors', '-a',
help = 'Path to authors.txt file (required)')
import os
import sys
import xml.etree.ElementTree
def s(command):
print 'Running command:', command
if os.system(command):
raise SystemError
def r(command):
f = os.popen(command)
result = f.read()
f.close()
return result
def main(args=None):
if args is None:
args = sys.argv[1:]
options, args = parser.parse_args(args)
url, = args
if url.endswith('/'):
url = url[:-1]
name = url.rsplit('/', 1)[1]
if not options.restart:
os.mkdir(name)
os.chdir(name)
if not options.restart:
s('git svn init --no-metadata -s %s' % url)
assert options.authors
s('git config svn.authorsfile %s' % options.authors)
s('git svn fetch')
for tag in r('svn ls %s/tags' % url).strip().split():
if tag[-1] == '/':
tag = tag[:-1]
f = os.popen('svn log --xml -l1 %s/tags/%s' % (url, tag))
date = xml.etree.ElementTree.ElementTree(
file=f).find('logentry').find('date').text
f.close()
s(GIT_COMMITTER_DATE=%r git tag %r 'tags/%s' % (
date.replace('T', ' ').replace('Z', ' +'),
tag, tag,
))
for branch in r('svn ls %s/branches' % url).strip().split():
if branch[-1] == '/':
branch = branch[:-1]
s('git checkout %s' % branch)
s('git checkout -b %s' % branch)
# Not sure if this is necessary, or sufficient. The Ruby
# version ran into trouble when git left files around between
# branche checkouts. I haven't had the problem, with this
# script, which unlike the Ruby version, doesn't process
# deleted branches.
s('git reset --hard HEAD')
s('git checkout trunk')
s('git branch -D master')
s('git checkout -f -b master')
s('git branch -d -r trunk')
s('git gc')
if options.github:
github_dest, github_token = options.github.rsplit('/', 1)
if github_dest.startswith('users/'):
github_user = github_dest[6:]
github_dest = 'user'
else:
assert github_dest.startswith('orgs/')
github_user = github_dest.split('/')[1]
s('curl -v -XPOST -H Authorization: token %s'
' https://api.github.com/%s/repos -d '
'{name: '%s'}'
% (github_token, github_dest, name))
s('git remote add origin ssh://g...@github.com/%s/%s.git'
% (github_user, name))
s(git push -u origin '*' --tags)
if __name__ == '__main__':
main()
smime.p7s
Description: S/MIME cryptographic signature
Re: [Zope-dev] Status of github migration
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 and 2.13 branches since they're all active, even if just for bug/security fixes. 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 uses svn2git underneath. If there's whole branches missing the migration has obviously failed. I had a bunch of problems with ZODB and the ruby svn2git. That's why I wrote my own based on seeing what the ruby version was trying to do. Note that most of the heavy lifting is actually done by the git svn plugin. If you want to help you could try a migration with the attached Python script that Jim wrote as a result of finding bugs in svn2git. I can provide you with a suitable authors mapping file. I've been waiting to make the script more publicly available in a saner fashion until I've worked with it some more. I should just make it a gist. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
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 continue to test a trunk not in use. Best regards, Patrick On Thu, Jan 10, 2013 at 3:15 PM, Jim Fulton j...@zope.com 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 github - Copy above file to root of project. - Make project read only An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? There are a lot of other details of the migration that need to be worked out, like how folks should request migration and automating the conversion further. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 uses svn2git underneath. If there's whole branches missing the migration has obviously failed. I had a bunch of problems with ZODB and the ruby svn2git. If you used a ruby tool, then you didn't use the same one as the Plone migrations. Unfortunately there's at least two different tools named svn2git. The one used by the Plone migrations is from the KDE community and written in Qt. Some of the more useful info is at http://techbase.kde.org/Projects/MoveToGit/UsingSvn2Git That tool doesn't really use git-svn. Instead it scan through all SVN revisions, looks at the changed paths and matches those against a ruleset. So you can tell it that both /foo/bar/trunk and /bar/trunk contain code that goes into the final bar.git repo. Since you can manually influence these rules, this tool tends to work better on projects which have moved their location in SVN a lot. It also does a single scan through the entire SVN repo and is able to generate many resulting git projects at once. Which made it perfect for a mass-migration. git-svn or tools based on it, tend to work well on small projects that always stayed in the same place, with the same structure. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
-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 ZTK + ZopeApp)? 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). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDu86MACgkQ+gerLs4ltQ5jMQCfShe7ev+ti+PAS66pXOPVLRZ6 Qy4AoNu3SxntlWgSfMfc7UbkHJ5fQRUo =maE3 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
-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 the URL if the project page in github - Copy above file to root of project. - Make project read only An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? There are a lot of other details of the migration that need to be worked out, like how folks should request migration and automating the conversion further. I would be happy to add the 'MOVED-TO-GITHUB.txt' files to the SVN projects for the 'zope.*' packages I have already migrated. I need to have the readonly restriction relaxed, first/ Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDu8+UACgkQ+gerLs4ltQ78tACg0RqCvxRd269YKdcT+shih/5s y/EAn1aO1PUQamqH4sJaMVgBKH2xK2LP =YRxy -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
-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 trunk has been deleted already. Thats not a bug, thats why I run the CI Tool. Would be stupid if I continue to test a trunk not in use. It isn't just CI: people may have projects running from SVN checkouts, which we break without warning (the Plone devs have been notorious for causing such breakage for years). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDu9DUACgkQ+gerLs4ltQ4vpACeP5Tt0m8MkbK/cAOPynlHMerf N4gAnA2ULgxdeGwq81jvlGYuV59NGmdc =FiLH -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 14, OK: 15
-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 - Build # 118 https://mail.zope.org/pipermail/zope-tests/2013-January/071232.html These failures are both due to failures to check out 'transaction', which is now moved to Github. [3]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071249.html [4]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071250.html [5]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071251.html [6]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071252.html These failures are in tests of now-out-of-date BTrees. We should just remove such tests from the ZODB suite, now that BTrees have their own CI. [11] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071259.html [12] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071258.html [13] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071256.html [14] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071257.html These failures are due to an oddity in the ZCML-based class protections granted by zope.app.security to the (non-API) tree iterators in the C BTrees code. I assume from the fact that these tests fail, that they are running against a BTrees package which does *not* have the C extensions compiled. Those iterator classes are not APIs: they are implementation details of the BTrees C extensions. I speculate somebody added protections for them to zope.app.security to work around an issue with walking space-suit-wrapped BTrees in untrusted code (note that somehow the corresponding TreeSets aren't protected: go figure). I pushed a branch of BTrees which restores the iterators *in name only* in the pure-Python case: https://github.com/zopefoundation/BTrees/tree/expose_tree_iterator Im my branch, trying to actually *use* the XXTreeITerator class in that branch (assuming no C extensions) will raise an exception, but the ZCML class declarations which name the classes should no longer raise. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDu9yAACgkQ+gerLs4ltQ6LGQCdFWY+ol5kZiF7j+MaQlpSo302 4UQAoKOt/TZqWxN9eGMkCZXRJKqx8rhv =8dk5 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 14, OK: 15
-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 # 118 https://mail.zope.org/pipermail/zope-tests/2013-January/071232.html These failures are both due to failures to check out 'transaction', which is now moved to Github. I think I have just fixed these failures by updating the 'ztk-sources.cfg' file to point to the github locations.'bin/develop co '.*' workds, and all tests pass. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDu/FgACgkQ+gerLs4ltQ5BXQCgmtqqTs/zmZTpGe14KOyFgdo4 i34AnA2/mvomHm0IlH2ZnaOLSWo3f8Sm =sPeY -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 the package used to migrate most Plone packages from SVN to GitHub, which uses svn2git underneath. If there's whole branches missing the migration has obviously failed. I had a bunch of problems with ZODB and the ruby svn2git. If you used a ruby tool, then you didn't use the same one as the Plone migrations. Unfortunately there's at least two different tools named svn2git. The one used by the Plone migrations is from the KDE community and written in Qt. Some of the more useful info is at http://techbase.kde.org/Projects/MoveToGit/UsingSvn2Git That tool doesn't really use git-svn. Instead it scan through all SVN revisions, looks at the changed paths and matches those against a ruleset. So you can tell it that both /foo/bar/trunk and /bar/trunk contain code that goes into the final bar.git repo. Since you can manually influence these rules, this tool tends to work better on projects which have moved their location in SVN a lot. It also does a single scan through the entire SVN repo and is able to generate many resulting git projects at once. Which made it perfect for a mass-migration. git-svn or tools based on it, tend to work well on small projects that always stayed in the same place, with the same structure. That's interesting. Not sure what I think about it (now that I have something mostly working and don't want to figure out something else :), but definitely worth thinking about. Thanks. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 sure they'd be willing to help move all of Zope across, too. Should I have a word? Matt ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 based on that software and apparently there are issues with missing branches, too. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
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 github - Copy above file to root of project. - Make project read only An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? +1 Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
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 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 continue to test a trunk not in use. It isn't just CI: people may have projects running from SVN checkouts, which we break without warning (the Plone devs have been notorious for causing such breakage for years). I still think breakage is better. If they're using trunk, without pinning a revision, it must be because they want the latest code. They won't get that from svn. This is a case where I think it's better to fail in an obvious way. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
-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 Plone did this the people involved wrote some scripts 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. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDvQiMACgkQ+gerLs4ltQ5dAwCgwtWbn9IRnpjsD3AxYlgkLmZs PT0AoKd/cY6c0cJ8z4DzMZ+w0qcXtTLv =S8Qf -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] How to signal that projects have moved to github
-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 Feeling ambiguoous today, or maybe not? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDvQpUACgkQ+gerLs4ltQ5GCACdHHdDouYMufXolF2yNPfsgA6d b90An29nE88UOeLO3RXIoYEULp2C1Qge =Mffi -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Status of github migration
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 about having them all migrated to github. I'm sure this will happen the next time there's a sprint, just like lots of them got migrated (and subsequently deleted) at the zope4 sprint in San Francisco a few years back. We need man-hours, sure, but not champions. Being blocked on working on the code because you're the first one to care about a package and subsequently have to learn how to do the migration is a crazy way of doing things. Matthew ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 24, OK: 15
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: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received [1]Still Failing - zopetoolkit_trunk - Build # 136 [2]Still Failing - zopetoolkit_trunk_app - Build # 119 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux [3]winbot / ZODB_dev py_265_win32 [4]winbot / ZODB_dev py_265_win64 [5]winbot / ZODB_dev py_270_win32 [6]winbot / ZODB_dev py_270_win64 [7]winbot / z3c.configurator_py_265_32 [8]winbot / z3c.contents_py_265_32 [9]winbot / z3c.ptcompat_py_265_32 [10] winbot / z3c.recipe.paster_py_265_32 [11] winbot / z3c.sampledata_py_265_32 [12] winbot / zc.sourcefactory_py_265_32 [13] winbot / zope.app.applicationcontrol_py_265_32 [14] winbot / zope.app.authentication_py_265_32 [15] winbot / zope.app.component_py_265_32 [16] winbot / zope.app.container_py_265_32 [17] winbot / zope.app.exception_py_265_32 [18] winbot / zope.app.generations_py_265_32 [19] winbot / zope.app.publisher_py_265_32 [20] winbot / zope.app.rotterdam_py_265_32 [21] winbot / zope.app.security_py_265_32 [22] winbot / zope.app.session_py_265_32 [23] winbot / zope.app.testing_py_265_32 [24] winbot / zope.app.zcmlfiles_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 136 https://mail.zope.org/pipermail/zope-tests/2013-January/071271.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 119 https://mail.zope.org/pipermail/zope-tests/2013-January/071272.html [3]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071288.html [4]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071289.html [5]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071290.html [6]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071291.html [7]FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071268.html [8]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071292.html [9]FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071265.html [10] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071293.html [11] FAILED winbot / z3c.sampledata_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071294.html [12] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071267.html [13] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071266.html [14] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071262.html [15] FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071270.html [16] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071298.html [17] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071297.html [18] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071263.html [19] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071260.html [20] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071269.html [21] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071264.html [22] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071261.html [23] FAILED winbot / zope.app.testing_py_265_32
