gsutil distribution files are broken for all versions above 3.18

101 views
Skip to first unread message

Danylo Dragan

unread,
Dec 16, 2012, 1:15:48 PM12/16/12
to gsutil-...@googlegroups.com
Hi,

gsutil distribution files (both zip and tar.gz) are broken for all versions above 3.18 (i.e. the contents doesn't match respective svn trunk and it's impossible to build RPM package).

Please repack/update broken distribution files. Thanks in advance!

Regards,
Danylo Dragan

Mike Schwartz (Google Storage Team)

unread,
Dec 16, 2012, 2:51:13 PM12/16/12
to gsutil-...@googlegroups.com
Hi Danylo,

Can you please give a specific example of a file in the zip or tar.gz file that doesn't match what's checked in to svn?

Are you referring to the fact that the svn repo no longer includes boto via an svn propset, while the zip and tar.gz files do include boto? If so, we made that switch because the svn-github gateway has become very unreliable. gsutil and boto need to be separately checked out now.

Thanks,

Mike

Danylo Dragan

unread,
Dec 16, 2012, 3:38:17 PM12/16/12
to gsutil-...@googlegroups.com, gs-...@google.com
Hi Mike,

I have run into issues while trying to build RPM as per gsutil/README.pkg and further analysis showed that it's distribution file issue.

Starting with gsutil 3.19 files gsutil/MANIFEST.in and gsutil/setup.py are no longer from gsutil svn but instead from boto git, so gsutil RPM packaging now is clearly broken (I didn't check for other files possibly not matching gsutil svn, I just stepped back to gsutil 3.18 until RPM packaging issues will be resolved).

Also, for Scientific Linux 6.3 (i.e. the same for RHEL 6.3), one has to fix path to Python egg file and include several Python-compiled files to get over "installed but not included into rpm" issue (I attached a quick patch, though you might find a better way to fix this).

Hope this info will help you to sort everything out. Thanks for your help and great product!

Regards,
Danylo
gsutil.spec.in.patch

Mike Schwartz (Google Storage Team)

unread,
Dec 16, 2012, 6:15:16 PM12/16/12
to gsutil-...@googlegroups.com
Hi Danylo,

We fixed the accidental inclusion of the boto manifest and other artifacts in the top-level gsutil dir, but haven't yet put out a new gsutil release with this fix. (We usually assemble a number of bug fixes and new features before puttiing out new gsutil releases.) I put out a pre-release for you to try with this fix at gs://prerelease/gsutil_3.22_PRE_REMOVE_BOTO_MISINCLUDES.tar.gz
and
gs://prerelease/gsutil_3.22_PRE_REMOVE_BOTO_MISINCLUDES.zip
I'd appreciate if you could please try it and let me know whether that fixes the problem for your RPM builds.

(We will probably release gsutil 3.22 within the next couple of weeks.)

Thanks,

Mike

Danylo Dragan

unread,
Dec 17, 2012, 7:20:53 AM12/17/12
to gsutil-...@googlegroups.com, gs-...@google.com
Hi Mike,

I was able to successfully build RPM from fixed distribution file gsutil_3.22_PRE_REMOVE_BOTO_MISINCLUDES.tar.gz you provided (I only had to apply patch I mentioned in my previous post to get over "installed but not included into rpm" issue).

Thank you!

Also, is it possible for Google Storage Team to always announce new gsutil releases to either gs-announce group or some new group other than gsutil-discuss (e.g. something like gsutil-announce)?

Regards,
Danylo

Mike Schwartz (Google Storage Team)

unread,
Dec 18, 2012, 11:34:05 AM12/18/12
to gsutil-...@googlegroups.com, Google Storage Team
Hi Danylo,

Thanks for the suggestion about announcing new gsutil releases. From now on we will announce new gsutil releases on gs-announce.

Mike

Danylo Dragan

unread,
Dec 18, 2012, 11:52:04 AM12/18/12
to gsutil-...@googlegroups.com, Google Storage Team
Hi Mike,

Again, thanks a lot for products/services Google Storage Team provides!

Merry Christmas and a Happy New Year to all of you,
Danylo
Reply all
Reply to author
Forward
0 new messages