zope.viewlet 3.4.1 release broken
Hi, the release of zope.viewlet 3.4.1 on pypi is missing the data files (like .txt and .zcml), hence it is unusable. Also the date in the CHANGES is wrong (2007 should be 2008) Roger, it is good that you do releases, but could to please take take of making them proper? Unfortunately I cannot fix it since I don't have access to zope.viewlet, so somebody else please fix it (or give me access). BTW Roger, z3c.menu.simple has the same problem of missing data files. Regards, -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
Christian Zagrodnick schrieb:
Hi,
the release of zope.viewlet 3.4.1 on pypi is missing the data files (like .txt and .zcml), hence it is unusable. Also the date in the CHANGES is wrong (2007 should be 2008)
Roger, it is good that you do releases, but could to please take take of making them proper?
Unfortunately I cannot fix it since I don't have access to zope.viewlet, so somebody else please fix it (or give me access).
You have now. BTW: I think I saw a tool for giving out rights on pypi to the zope.* set of packages for individuals in one operation. Is it supposed to work/be used? What's its name again? Christian -- gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany www.gocept.com - ct@gocept.com - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development
On 2008-01-24 14:21:44 +0100, Christian Theune <ct@gocept.com> said:
Christian Zagrodnick schrieb:
Hi,
the release of zope.viewlet 3.4.1 on pypi is missing the data files (like .txt and .zcml), hence it is unusable. Also the date in the CHANGES is wrong (2007 should be 2008)
Roger, it is good that you do releases, but could to please take take of making them proper?
Unfortunately I cannot fix it since I don't have access to zope.viewlet, so somebody else please fix it (or give me access).
You have now.
Thanks, I just uploaded zope.viewlet 3.4.2. -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
On Jan 24, 2008 8:21 AM, Christian Theune <ct@gocept.com> wrote:
BTW: I think I saw a tool for giving out rights on pypi to the zope.* set of packages for individuals in one operation. Is it supposed to work/be used? What's its name again?
Argh! This is scary, evil, and dangerous. If there is indeed such a tool, I suspect I'm a victim already. There was a point a few months ago (IIRC) at which many, many Zope-related packages appeared on the list of packages I could manage. Most I've never touched and a number I'd not even heard of. And I can't drop my own privileges on those packages due to a PyPI bug (http://sourceforge.net/tracker/index.php?func=detail&aid=1855548&group_id=66...). Nobody should be added to a package they haven't asked to be on on PyPI, and it's reasonable they should have to list each package they want separately. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller
On Thursday 24 January 2008, Fred Drake wrote:
Nobody should be added to a package they haven't asked to be on on PyPI, and it's reasonable they should have to list each package they want separately.
I disagree, but I am more than happy to take you off the packages again. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Jan 24, 2008 11:46 AM, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
I disagree, but I am more than happy to take you off the packages again.
I made two assertions; I certainly hope you agree that people shouldn't be slammed on packages they've nothing to do with without their consent. Please do take me off packages I've listed below: jquery.javascript jquery.jsonform jquery.layer jquery.widget RestrictedPython z3c.breadcrumb z3c.coverage z3c.csvvocabulary z3c.currency z3c.etestbrowser z3c.form z3c.formdemo z3c.formui z3c.i18n z3c.layer z3c.macro z3c.macroviewlet z3c.menu z3c.optionstorage z3c.pagelet z3c.recipe.runscript z3c.referercredentials z3c.rml z3c.skin.pagelet z3c.template z3c.testing z3c.traverser z3c.viewlet z3c.viewtemplate z3c.zrtresource Zope zope.app.boston zope.app.dav zope.app.debug zope.app.debugskin zope.app.dependable zope.app.dtmlpage zope.app.error zope.app.exception zope.app.externaleditor zope.app.ftp zope.app.homefolder zope.app.http zope.app.i18nfile zope.app.layers zope.app.preference zope.app.preview zope.app.principalannotation zope.app.pythonpage zope.app.rotterdam zope.app.sqlscript zope.app.tree zope.app.twisted zope.app.undo zope.app.wfmc zope.app.workflow zope.app.xmlrpcintrospection zope.contentprovider zope.contenttype zope.dependencytool zope.documenttemplate zope.testrecorder zope.viewlet zope.wfmc -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller
On Thursday 24 January 2008, Christian Theune wrote:
BTW: I think I saw a tool for giving out rights on pypi to the zope.* set of packages for individuals in one operation. Is it supposed to work/be used? What's its name again?
zope.pypisupport Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
Hi Christian
Betreff: [Zope-dev] zope.viewlet 3.4.1 release broken
Hi,
the release of zope.viewlet 3.4.1 on pypi is missing the data files (like .txt and .zcml), hence it is unusable. Also the date in the CHANGES is wrong (2007 should be 2008)
No it doesn't miss the data. Your linux is just not able to extract them. It works on windows box.
Roger, it is good that you do releases, but could to please take take of making them proper?
Probably you know already. That's a (linux) bug in the python tar library. I did nothing wrong. It's just broken if you extract the files from the egg. on linux. Everything is build correct. btw, Stephan told me to fix the other eggs. Regards Roger Ineichen
On 2008-01-24 17:11:32 +0100, "Roger Ineichen" <dev@projekt01.ch> said:
Hi Christian
Betreff: [Zope-dev] zope.viewlet 3.4.1 release broken
Hi,
the release of zope.viewlet 3.4.1 on pypi is missing the data files (like .txt and .zcml), hence it is unusable. Also the date in the CHANGES is wrong (2007 should be 2008)
No it doesn't miss the data. Your linux is just not able to extract them. It works on windows box.
Interesting. So still the package would be broken for most users. I'm using Mac OS btw.
Roger, it is good that you do releases, but could to please take take of making them proper?
Probably you know already. That's a (linux) bug in the python tar library. I did nothing wrong. It's just broken if you extract the files from the egg. on linux. Everything is build correct.
Could you clearify why the package I built works then? That's the great mystery I suppose ;) -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
On Thursday 24 January 2008, Christian Zagrodnick wrote:
Probably you know already. That's a (linux) bug in the python tar library. I did nothing wrong. It's just broken if you extract the files from the egg. on linux. Everything is build correct.
Could you clearify why the package I built works then? That's the great mystery I suppose ;)
Because UNIX built packages work on UNIX and Windows. But Windows built packages only work on Windows. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Thu, Jan 24, 2008 at 12:06:16PM -0500, Stephan Richter wrote:
On Thursday 24 January 2008, Christian Zagrodnick wrote:
Probably you know already. That's a (linux) bug in the python tar library. I did nothing wrong. It's just broken if you extract the files from the egg. on linux. Everything is build correct.
Could you clearify why the package I built works then? That's the great mystery I suppose ;)
Because UNIX built packages work on UNIX and Windows. But Windows built packages only work on Windows.
This email contains the explanation -- it's a bug in distutils/setuptools: http://mail.python.org/pipermail/distutils-sig/2007-September/008296.html Note that the latest setuptools release (setuptools 0.6c7) does NOT contain the fix. Marius Gedminas -- For vi emulation of emacs, just type ":sh emacs" (without the quotes).
Hi Marius
Betreff: Re: [Zope-dev] Re: AW: zope.viewlet 3.4.1 release broken
[...]
Because UNIX built packages work on UNIX and Windows. But Windows built packages only work on Windows.
This email contains the explanation -- it's a bug in distutils/setuptools: http://mail.python.org/pipermail/distutils-sig/2007-September/ 008296.html
Note that the latest setuptools release (setuptools 0.6c7) does NOT contain the fix.
Thanks, that helps a lot to understand what's going on. Regards Roger Ineichen
Marius Gedminas -- For vi emulation of emacs, just type ":sh emacs" (without the quotes).
On 2008-01-24 22:28:19 +0100, Marius Gedminas <mgedmin@b4net.lt> said:
On Thu, Jan 24, 2008 at 12:06:16PM -0500, Stephan Richter wrote:
On Thursday 24 January 2008, Christian Zagrodnick wrote:
Probably you know already. That's a (linux) bug in the python tar library. I did nothing wrong. It's just broken if you extract the files from the egg. on linux. Everything is build correct.
Could you clearify why the package I built works then? That's the great mystery I suppose ;) =20 Because UNIX built packages work on UNIX and Windows. But Windows built= =20 packages only work on Windows.
This email contains the explanation -- it's a bug in distutils/setuptools: http://mail.python.org/pipermail/distutils-sig/2007-September/008296.html
Note that the latest setuptools release (setuptools 0.6c7) does NOT contain the fix.
So let's hope there will be a release which fixes this soon. This is very disturbing. And meanwhile we should not make releases on windows, should we. -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
On Thursday 24 January 2008, Christian Zagrodnick wrote:
the release of zope.viewlet 3.4.1 on pypi is missing the data files (like .txt and .zcml), hence it is unusable. Also the date in the CHANGES is wrong (2007 should be 2008)
The fact that you noticed this problem this quickly tells me you are not using the KGS. I tend to reply to this "tough luck". I will update the KGS as soon as I have re-released the packages. Jim has also given me already a new "zope-dev" directory already, so we can evolve a new, experimental KGS there. BTW, if you want to use a newer package than the KGS provides, you can always use the find-links option and point to the package in PyPI or PPIX directly.
Roger, it is good that you do releases, but could to please take take of making them proper?
He did take the care. The problem is a Python bug as Martijn pointed out later.
BTW Roger, z3c.menu.simple has the same problem of missing data files.
Yes, there are a bunch of packages that have this problem. I am going to re-release them all. (In fact, I have already started.) Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On 2008-01-24 18:04:44 +0100, Stephan Richter <srichter@cosmos.phy.tufts.edu> said:
On Thursday 24 January 2008, Christian Zagrodnick wrote:
the release of zope.viewlet 3.4.1 on pypi is missing the data files (like .txt and .zcml), hence it is unusable. Also the date in the CHANGES is wrong (2007 should be 2008)
The fact that you noticed this problem this quickly tells me you are not using the KGS. I tend to reply to this "tough luck". I will update the KGS as soon as I have re-released the packages. Jim has also given me already a new "zope-dev" directory already, so we can evolve a new, experimental KGS there.
BTW, if you want to use a newer package than the KGS provides, you can always use the find-links option and point to the package in PyPI or PPIX directly.
Most component packages do not use the KGS in their buildout, so I wasn't either. For production use we pin exact versions actually.
Roger, it is good that you do releases, but could to please take take of making them proper?
He did take the care. The problem is a Python bug as Martijn pointed out later.
Yeah, actually I wondered how it would be possible to do it wrong ;)
BTW Roger, z3c.menu.simple has the same problem of missing data files.
Yes, there are a bunch of packages that have this problem. I am going to re-release them all. (In fact, I have already started.)
Good. Thanks! -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
On Friday 25 January 2008, Christian Zagrodnick wrote:
BTW, if you want to use a newer package than the KGS provides, you can always use the find-links option and point to the package in PyPI or PPIX directly.
Most component packages do not use the KGS in their buildout, so I wasn't either. For production use we pin exact versions actually.
Right, I should probably start adding the KGS index to the package's buildout to make clear what the expected working set is for a particular package. Well, pinning versions for production is okay, but what are you doing during development? If everyone keeps their own working set of versions, we will soon have a support nightmare, since reproducing someone else's setup will become almost impossible. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"
On Jan 25, 2008 6:13 AM, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
Well, pinning versions for production is okay, but what are you doing during development? If everyone keeps their own working set of versions, we will soon have a support nightmare, since reproducing someone else's setup will become almost impossible.
No, zc.buildout does the work there. At least at ZC, the versions specifications are stored in Subversion right alongside the project code, and is essential build information. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller
On Jan 25, 2008 4:19 PM, Fred Drake <fdrake@gmail.com> wrote:
On Jan 25, 2008 6:13 AM, Stephan Richter <srichter@cosmos.phy.tufts.edu> wrote:
Well, pinning versions for production is okay, but what are you doing during development? If everyone keeps their own working set of versions, we will soon have a support nightmare, since reproducing someone else's setup will become almost impossible.
No, zc.buildout does the work there. At least at ZC, the versions specifications are stored in Subversion right alongside the project code, and is essential build information.
So you are effectively maintaining your own personal KGS configuration, which is fine if there are enough resources to do that properly, but I personally like delegating whenever I can ;) and i trust Stephan to do the task for me. And I don't think there are that many developers that are better than Stephan at keeping a good KGS. I understand that Zope corp is employing a lot of programmers that have the expertise to maintain such a config, I just don't think everyone should do it. Ignas
participants (7)
-
Christian Theune -
Christian Zagrodnick -
Fred Drake -
Ignas Mikalajunas -
Marius Gedminas -
Roger Ineichen -
Stephan Richter