deb-s3 seems to hang on upload about deb-s3

[hjrnunes]

Sorry for not being very helpful, but I don't grok Ruby enough...

[hjrnunes]

Tried with a different package, and got a different error! :S

vagrant@precise64:/vagrant$ deb-s3 upload --bucket cbox-pkg-repo-test.s3.amazonaws.com patch_2.6.1-3_amd64.deb --access-key=mykey --secret-key=mysecret
>> Retrieving existing manifests
>> Examining package file patch_2.6.1-3_amd64.deb
>> Uploading packages and new manifests to S3
   -- Transferring pool/p/pa/patch_2.6.1-3_amd64.deb
/home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/aws-s3-0.6.3/lib/aws/s3/error.rb:38:in `raise': The specified bucket does not exist (AWS::S3::NoSuchBucket)
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/aws-s3-0.6.3/lib/aws/s3/base.rb:72:in `request'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/aws-s3-0.6.3/lib/aws/s3/base.rb:88:in `put'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/aws-s3-0.6.3/lib/aws/s3/object.rb:241:in `store'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/utils.rb:58:in `block in s3_store'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/utils.rb:57:in `open'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/utils.rb:57:in `s3_store'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/manifest.rb:69:in `block in write_to_s3'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/manifest.rb:66:in `each'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/manifest.rb:66:in `write_to_s3'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/cli.rb:127:in `block in upload'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/cli.rb:126:in `each_value'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/lib/deb/s3/cli.rb:126:in `upload'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/thor-0.18.1/lib/thor/command.rb:27:in `run'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/thor-0.18.1/lib/thor/base.rb:439:in `start'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/gems/deb-s3-0.5.1/bin/deb-s3:8:in `<top (required)>'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/bin/deb-s3:23:in `load'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/bin/deb-s3:23:in `<main>'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/bin/ruby_noexec_wrapper:14:in `eval'
    from /home/vagrant/.rvm/gems/ruby-1.9.3-p448/bin/ruby_noexec_wrapper:14:in `<main>'

[krobertson]

The command should have been:

deb-s3 upload --bucket cbox-pkg-repo-test patch_2.6.1-3_amd64.deb --access-key=mykey --secret-key=mysecret

The --bucket command should only be the name of the bucket, but it was a hostname (it included .s3.amazonaws.com).