My buckets all have upper-case in them. So I checked s3cmd out of subversion and ran it. It works! Thanks!
Something separate: I just read your discussion of yum (in today's s3tools mail compendium) and I followed your directions for making a yum repository. First I did "yum erase s3cmd" to remove version 0.9.8.1-3. Then I followed your directions and did "yum install s3cmd". This installed 0.9.8.3-2.1. So if I understand correctly, this means yum will install your latest version rather than Fedora's latest version. Is this right?
Thanks for the quick response! This solves a big problem for me.
----- Original Message ----
From: Michal Ludvig <michal@...>
To: Mike Steele <gurucentral@...>; s3tools-general@...
Sent: Tuesday, September 9, 2008 12:55:26 AM
Subject: Re: [S3tools-general] s3cmd ls s3://SomeBucket gives SignatureDoesNotMatch
Mike Steele wrote:
> Some time ago, I upgraded s3cmd from version 0.9.4 to version 0.9.6
> (Fedora core 4). However, the 'ls' command returned an error:
> Prompt: s3cmd ls s3://SomeBucket
> Bucket 'SomeBucket':
> ERROR: S3 error: 403 (Forbidden): SignatureDoesNotMatch
Does your bucket name have some upper-case letters?
If that's the case give the development version from SVN a try, that one
should be able to work with all your buckets. If you confirm it's all
right there I'll backport the change to 0.9.8-branch.
From: Michal Ludvig <michal@lo...> - 2008-09-10 00:20:47
Mike Steele wrote:
> Something separate: I just read your discussion of yum (in today's
> s3tools mail compendium) and I followed your directions for making a yum
> repository. [...] So if I understand correctly, this means yum
> will install your latest version rather than Fedora's latest version.
> Is this right?
Yes, that's correct. Whenever you do "yum update" it should check for
new versions and if there is one it'll offer it for installation.