Fatal error: Start tag expected, '<' not found at :1. about deb-s3

[krobertson]

No, it should create everything for you without the need for something else... otherwise I wouldn't have said that in my post. 😄

Do you have the full command you used and the full output? Did the output have a stack trace, since that would be very useful.

[hjrnunes]

Hi Ken, thanks for getting back at me.

So, here's the command I used:

deb-s3 upload --bucket cbox-pkg-repo-test my-pkg_1.0.5_all.deb --access-key=mykey --secret-key=mysecret

here's the output I got:

>> Retrieving existing manifests
Fatal error: Start tag expected, '<' not found at :1.
/usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/support/faster-xml-simple/lib/faster_xml_simple.rb:179:in `parse': Fatal error: Start tag expected, '<' not found at :1. (LibXML::XML::Error)
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/support/faster-xml-simple/lib/faster_xml_simple.rb:179:in `parse'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/support/faster-xml-simple/lib/faster_xml_simple.rb:58:in `initialize'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/support/faster-xml-simple/lib/faster_xml_simple.rb:53:in `new'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/support/faster-xml-simple/lib/faster_xml_simple.rb:53:in `xml_in'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/parsing.rb:64:in `parse'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/parsing.rb:55:in `initialize'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/response.rb:55:in `new'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/response.rb:55:in `parsed'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/extensions.rb:183:in `block in parsed'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/extensions.rb:152:in `expirable_memoize'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/extensions.rb:182:in `parsed'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/response.rb:45:in `error?'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/base.rb:72:in `request'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/base.rb:88:in `get'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/object.rb:134:in `value'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.3/lib/aws/s3/object.rb:138:in `stream'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/deb-s3-0.5.1/lib/deb/s3/utils.rb:49:in `s3_read'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/deb-s3-0.5.1/lib/deb/s3/release.rb:23:in `retrieve'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/deb-s3-0.5.1/lib/deb/s3/cli.rb:102:in `upload'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/thor-0.18.1/lib/thor/command.rb:27:in `run'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/thor-0.18.1/lib/thor/base.rb:439:in `start'
    from /usr/local/Cellar/ruby/1.9.3-p362/lib/ruby/gems/1.9.1/gems/deb-s3-0.5.1/bin/deb-s3:8:in `<top (required)>'
    from /usr/local/Cellar/ruby/1.9.3-p362/bin/deb-s3:23:in `load'
    from /usr/local/Cellar/ruby/1.9.3-p362/bin/deb-s3:23:in `<main>'

The bucket I'm trying to upload to is an empty just created one.
Thanks!

[hjrnunes]

Found what the problem was.

The bucket name needs to be like this:

mybucket.s3.amazonaws.com

instead of just

mybucket

[krobertson]

You should just have to put the bucket name and not a full hostname. Glad you got it working, but will look into why it wasn't happy with just the bucket name.

[krobertson]

Please try again on the latest release. There are separate --bucket and --endpoint option. Endpoint can be used to specify the AWS region, but I believe in most cases it detects the region.