[Zope-dev] Re: Zope 2.9.4 broken ? (solved)
Hi, I found the solution for my problem: There was a build folder under lib/python called build/lib/lib-i686-2.4/... Don't know where it comes from. Maybe a wrong setup before current install process. Removing lib/python/build solved my problem. Regards, Dirk -- Feel free – 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
--On 14. Juli 2006 16:01:22 -0400 Tres Seaver [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: If there are no objections, I plan to release Zope 2.9.4 in about one week (likely next Thu or Fri). Note that the 2.9 branch depends at the moment on unreleased ZODB changes (for a fix to issue #2016) and that there is a sizable set of changes on the 3.2 branch after 3.2.1, at least some of which might be important for Zope2. Since nobody replied to my posting about a 3.2.2 release this week I will release 2.9.4 using Zope 3.2.1. Andreas pgpBBW4Szc9s7.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
--On 15. Juli 2006 15:55:42 -0400 Tim Peters [EMAIL PROTECTED] wrote: [Tim] I used tags for ZODB until I gave in to complaints about that, and switched to using revision numbers. The real complaint about using a tagged external is that when the tag changes, SVN isn't smart enough to do an incremental update. Instead, when you update after an external tag changes: [Andreas] What do you mean with when the tag changes? Not what I said: I said [when] an /external/ tag changes. I mean when you change an external tag _in_ project A _referencing_ the external tagged project B. Here A=Zope and B=ZODB, and the external tags in question are the ones referencing ZODB from within the svn:externals properties of various Zope directories. I am still not completely sure about the problem. Yesterday I created a tag for for ZODB 3.6.2 as ../ZODB/tags/3.6.2 and I updated the svn:externals for the ZODB on the Zope 2.9 branch to this new tag. When releasing 2.9.4 2.9.4 will be tagged as Zope/tags/2.9.4so what will be the problem... both tags should never be touched...am I missing a particular usecase? Andreas pgpkq7UXsgJOp.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 2.9.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: --On 15. Juli 2006 15:55:42 -0400 Tim Peters [EMAIL PROTECTED] wrote: [Tim] I used tags for ZODB until I gave in to complaints about that, and switched to using revision numbers. The real complaint about using a tagged external is that when the tag changes, SVN isn't smart enough to do an incremental update. Instead, when you update after an external tag changes: [Andreas] What do you mean with when the tag changes? Not what I said: I said [when] an /external/ tag changes. I mean when you change an external tag _in_ project A _referencing_ the external tagged project B. Here A=Zope and B=ZODB, and the external tags in question are the ones referencing ZODB from within the svn:externals properties of various Zope directories. I am still not completely sure about the problem. Yesterday I created a tag for for ZODB 3.6.2 as ../ZODB/tags/3.6.2 and I updated the svn:externals for the ZODB on the Zope 2.9 branch to this new tag. When releasing 2.9.4 2.9.4 will be tagged as Zope/tags/2.9.4so what will be the problem... both tags should never be touched...am I missing a particular usecase? Tim is talking about the effect on an existing sandbox when the developer (or somebody else) changes the 'svn:external'. He alleges (I have no reason to doubt him, but haven't observed it myself) that changing from one tag to another (e.g., from $ZSVN/ZODB/tags/3.6.3 to $ZSVN/ZODB/tags/3.6.4) is more disruptive to those sandboxes than shifting the revision number, but keeping the branch the same. I think for *development* purposes that we can afford to leave the externals pointing at branch+revision; however, for making releases, I think we need to manage the external dependencies such that we trigger at least the internal checkpoint release of externals. I *really* wish that there SVN supported something like 'svn ln -r 12345 $ZSVN/foobar/branches/3.5 $ZSVN/foobar/tags/3.5.6' (such that the link that got created was equivalent to branch + revision. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEukSe+gerLs4ltQ4RAtrkAKC9DAN2QAi7kLaroVjv7rq+D/tqRACgszEK j6WOf3YGAeYo8F4/nNCQHbw= =lzTZ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
--On 14. Juli 2006 16:01:22 -0400 Tres Seaver [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: If there are no objections, I plan to release Zope 2.9.4 in about one week (likely next Thu or Fri). Even sooner would be fine with me. I plan to release a 2.8.8 this weekend with the changes for the ReST fix (I already released a 2.7.9). Should not be a problem for me..perhaps Monday... Note that the 2.9 branch depends at the moment on unreleased ZODB changes (for a fix to issue #2016) and that there is a sizable set of changes on the 3.2 branch after 3.2.1, at least some of which might be important for Zope2. I think we should make another internal ZODB release. The current svn:externals for the ZODB (and other modules) use a revision number instead of a tag. This reminds me of some former discussion whether to use revision numbers or tags...what was the result of this discussion. I am very much in favor of using tag names...revision number tell you nothing...provide at least a reasonable version information...opinions? -aj pgpVE3mgGygLt.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
Previously Andreas Jung wrote: I think we should make another internal ZODB release. The current svn:externals for the ZODB (and other modules) use a revision number instead of a tag. This reminds me of some former discussion whether to use revision numbers or tags...what was the result of this discussion. I am very much in favor of using tag names...revision number tell you nothing...provide at least a reasonable version information...opinions? +1 on tags Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: --On 14. Juli 2006 16:01:22 -0400 Tres Seaver [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: If there are no objections, I plan to release Zope 2.9.4 in about one week (likely next Thu or Fri). Even sooner would be fine with me. I plan to release a 2.8.8 this weekend with the changes for the ReST fix (I already released a 2.7.9). Should not be a problem for me..perhaps Monday... Note that the 2.9 branch depends at the moment on unreleased ZODB changes (for a fix to issue #2016) and that there is a sizable set of changes on the 3.2 branch after 3.2.1, at least some of which might be important for Zope2. I think we should make another internal ZODB release. The current svn:externals for the ZODB (and other modules) use a revision number instead of a tag. This reminds me of some former discussion whether to use revision numbers or tags...what was the result of this discussion. I am very much in favor of using tag names...revision number tell you nothing...provide at least a reasonable version information...opinions? +1. I tagged 'ZODB-3.4.4' and 'Zope-3.0.2-Zope-2.8' releases yesterday for internal consumption of the Zope 2.8 branch. I don't expect to make actual releases from those tags, but I like having them there. As we move to a more fine-grained package architecture (i.e., egg-based Zope districbutions), we are going to have to do more releases management of the individual pieces which make up Zope. Keeping the changelog current will be a bit of a chore, but is essential in a packageing-driven maodel (just as with RPM / .deb packaging). Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEuNKv+gerLs4ltQ4RAmELAJ4oRjpr7lJU4m+8qzcXv1EL9JwMnwCglwO3 nPLTzxp2s1dtPbTQjuWI6vE= =II/L -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
[Andreas Jung] ... I think we should make another internal ZODB release. The current svn:externals for the ZODB (and other modules) use a revision number instead of a tag. This reminds me of some former discussion whether to use revision numbers or tags...what was the result of this discussion. I am very much in favor of using tag names...revision number tell you nothing...provide at least a reasonable version information...opinions? The things people complain about sometimes astonish me -- just as the things I complain about sometimes astonish others :-) I used tags for ZODB until I gave in to complaints about that, and switched to using revision numbers. The real complaint about using a tagged external is that when the tag changes, SVN isn't smart enough to do an incremental update. Instead, when you update after an external tag changes: - It wholly deletes you current checkout of the external. If non-version-controlled files (like .pyc) happen to be sitting in the directories, this leaves behind useless OLD directories. - It does a complete checkout of the new tag. This generally takes more time. And forces a recompile too even if no C code in the external has actually changed, It's true that changing an external revision number instead suffers none of those drawbacks.Like I cared ;-) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
--On 15. Juli 2006 15:21:20 -0400 Tim Peters [EMAIL PROTECTED] wrote: The things people complain about sometimes astonish me -- just as the things I complain about sometimes astonish others :-) I used tags for ZODB until I gave in to complaints about that, and switched to using revision numbers. The real complaint about using a tagged external is that when the tag changes, SVN isn't smart enough to do an incremental update. Instead, when you update after an external tag changes: What do you mean with when the tag changes? A tag IMO should *never* change. I know that even CVS allows you to modify tagged files however I consider this a misuse of the concept tag. A tag in my understanding is identical with the state for a sequence of files and dirs for a given timestamp where the timestamp should never change. -aj pgp7Ko7Gbgnix.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
Previously Andreas Jung wrote: What do you mean with when the tag changes? A tag IMO should *never* change. What he describes sounds like modifying svn:externals to point to a different tag. Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9.4
[Tim] I used tags for ZODB until I gave in to complaints about that, and switched to using revision numbers. The real complaint about using a tagged external is that when the tag changes, SVN isn't smart enough to do an incremental update. Instead, when you update after an external tag changes: [Andreas] What do you mean with when the tag changes? Not what I said: I said [when] an /external/ tag changes. I mean when you change an external tag _in_ project A _referencing_ the external tagged project B. Here A=Zope and B=ZODB, and the external tags in question are the ones referencing ZODB from within the svn:externals properties of various Zope directories. A tag IMO should *never* change. The revision number associated with a tag within project B indeed shouldn't change. That's not what I'm talking about. I'm talking about how other projects reference project B: they have a choice of: 1. making their own copy of B 2. using svn:externals with a tag for B 3. using svn:externals with a revision number for B Read my msg again with that in mind, and it will make much more sense to you. I was describing the complaints about using choice #2. Zope Corp has tried all of those at various times. They all have different drawbacks, but the only one I found horribly unusable was #1 (because then N different projects have copies of B, and changes to copies of B's code get made from N different projects, and nobody bothers to merge those changes back into B itself -- people changing a copy of B from a different project often don't even _know_ they're changing conceptually external code; in effect, without absurd effort on the part of B's maintainer(s), the world ends up with B plus N forks of B). ... ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 2.9.4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: If there are no objections, I plan to release Zope 2.9.4 in about one week (likely next Thu or Fri). Even sooner would be fine with me. I plan to release a 2.8.8 this weekend with the changes for the ReST fix (I already released a 2.7.9). Note that the 2.9 branch depends at the moment on unreleased ZODB changes (for a fix to issue #2016) and that there is a sizable set of changes on the 3.2 branch after 3.2.1, at least some of which might be important for Zope2. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEt/gS+gerLs4ltQ4RAti/AJ9YTcGB/e3UXvqRn9SW3UxYq30SEwCgoYRY 8/+qvoX+IOAVQPBRqByTwjc= =4tr0 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Zope 2.9.4
Tres Seaver wrote: Andreas Jung wrote: If there are no objections, I plan to release Zope 2.9.4 in about one week (likely next Thu or Fri). Even sooner would be fine with me. I plan to release a 2.8.8 this weekend with the changes for the ReST fix (I already released a 2.7.9). Note that the 2.9 branch depends at the moment on unreleased ZODB changes (for a fix to issue #2016) and that there is a sizable set of changes on the 3.2 branch after 3.2.1, at least some of which might be important for Zope2. Ok. Let's get a Zope 3.2.2 out first, then. It should probably happen anyways because of the docutils thing, right? Also, Alec Mitchell backported the new traversal behaviour (attributes, views, acquired junk) to Five 1.3. So we should probably also include a new Five 1.3.x release as well. I would expect that that would make a few people happy... Philipp ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
