gsutil-discuss Google Group

Re: gsutil distribution files are broken for all versions above 3.18

danylo.dra...@rolympus.com (Danylo Dragan) — Tue, 18 Dec 2012 16:52:04 UT

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
On Tuesday, December 18, 2012 6:34:05 PM UTC+2, Mike Schwartz (Google

the gs-discuss forum is going away, being consolidated into gs-discussion

gs-t...@google.com (Mike Schwartz (Google Storage Team)) — Tue, 18 Dec 2012 16:40:57 UT

Hi,

We are de-commissioning the
gsutil-discuss<[link]>
forum. From now on, any discussions/questions about gsutil can take place
on gs-discussion <[link]>, where
other discussions related to Google Cloud Storage take place. You can also

Re: gsutil distribution files are broken for all versions above 3.18

gs-t...@google.com (Mike Schwartz (Google Storage Team)) — Tue, 18 Dec 2012 16:34:05 UT

Hi Danylo,

Thanks for the suggestion about announcing new gsutil releases. From now on
we will announce new gsutil releases on
gs-announce<[link]>
.

Mike

On Mon, Dec 17, 2012 at 5:20 AM, Danylo Dragan

Re: gsutil distribution files are broken for all versions above 3.18

danylo.dra...@rolympus.com (Danylo Dragan) — Mon, 17 Dec 2012 12:20:53 UT

Hi Mike,
I was able to successfully build RPM from fixed distribution file gsutil_3.22_PRE_REMOVE_BOTO_MI SINCLUDES.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

Re: gsutil distribution files are broken for all versions above 3.18

gs-t...@google.com (Mike Schwartz (Google Storage Team)) — Sun, 16 Dec 2012 23:15:16 UT

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

Re: gsutil distribution files are broken for all versions above 3.18

danylo.dra...@rolympus.com (Danylo Dragan) — Sun, 16 Dec 2012 20:38:17 UT

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

Re: gsutil distribution files are broken for all versions above 3.18

gs-t...@google.com (Mike Schwartz (Google Storage Team)) — Sun, 16 Dec 2012 19:51:13 UT

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 distribution files are broken for all versions above 3.18

danylo.dra...@rolympus.com (Danylo Dragan) — Sun, 16 Dec 2012 18:15:48 UT

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

Re: Failure: 'ascii' codec can't encode character u'\xe8' in position 165: ordinal not in range(128)

gs-t...@google.com (Mike Schwartz (Google Storage Team)) — Fri, 30 Nov 2012 17:01:04 UT

Hi,

Yes, object names can't be longer than 1024 bytes when UTF-8 encoded.

gsutil does not currently support synchronization. There are other tools
available that will let you synchronize between the local disk and the
cloud - for example, I have used CloudBerry Pro for doing that.

Mike

Re: Failure: 'ascii' codec can't encode character u'\xe8' in position 165: ordinal not in range(128)

nt...@gimasys.com (Nguyễn Trí Lưu) — Fri, 30 Nov 2012 06:02:15 UT

Dear Google Storage team,

I think this issue by my file name is too long ( larger than 1024 bytes).
with gsutil tool, we cannot synchronized folders exist on my server and
cloud storage, Do you know any other tools support synchronized. We backup
70 GB data daily.

Thanks
Nguyễn Trí Lưu

new gsutil version supporting Object Versioning and Durable Reduced Availability Storage

gs-t...@google.com (Mike Schwartz (Google Storage Team)) — Tue, 27 Nov 2012 16:04:20 UT

Hi,

You may have seen our blog
posting<[link]>
yesterday,
announcing a number of new features, including Object
Versioning<[link]>and
Durable
Reduced Availability

Re: Can't locate LWP/UserAgent.pm in @INC

gs-t...@google.com (Mike Schwartz (Google Storage Team)) — Tue, 27 Nov 2012 15:50:02 UT

Hi,

Please instead install gsutil using the instructions at
[link]

Thanks,

Mike

Can't locate LWP/UserAgent.pm in @INC

anjan...@gmail.com (Anjanesh) — Tue, 27 Nov 2012 11:30:05 UT

Today I tried running gsutil on a newly formatted computer, and I got :
The program 'gsutil' is currently not installed. You can install it by
typing:
sudo apt-get install gsutil
After installing through aptitude and running it I get the following :
Can't locate LWP/UserAgent.pm in @INC (@INC contains: /etc/perl

Re: Failure: 'ascii' codec can't encode character u'\xe8' in position 165: ordinal not in range(128)

gs-t...@google.com (Google Storage Team) — Mon, 26 Nov 2012 18:12:21 UT

Hi,

Can you please send the output of running the command using gsutil -D. For
example:

gsutil -D getacl gs://yourbucket/yourobject

When you do, please strip out the Authorization: header.

If you'd prefer not to post this on the public list, you can send it to
gs-t...@google.com.

Thanks,

Re: Failure: 'ascii' codec can't encode character u'\xe8' in position 165: ordinal not in range(128)

nt...@gimasys.com — Tue, 20 Nov 2012 07:25:58 UT

I used gsutil version 3.18, but the error occur too, how to resolve it.

On Tuesday, June 19, 2012 10:11:24 PM UTC+7, Mike Schwartz (Google Storage