You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2022. It is now read-only.
I'm trying to get a new repo setup with a package built via FPM and when pushing into a fresh s3 bucket I'm seeing the below error. This error is from the tip of master, and I see the same issue from the most recent gem.
Ubuntu 12.04
Ruby 1.9.3
Is there something I need to do to get an initial repo setup? Are there any debug flags I can set to see what it is doing further?
root@f3ed34bc5efa:/deb-s3# bundle exec deb-s3 upload --bucket=charliek-apt --access-key-id=XXXXX --secret-access-key=XXXX jre1.7.0-45_1.0_amd64.deb
>> Retrieving existing manifests
>> Examining package file jre1.7.0-45_1.0_amd64.deb
/usr/bin/dpkg
/usr/lib/ruby/1.9.1/openssl/buffering.rb:174:in `sysread_nonblock': end of file reached (EOFError)
from /usr/lib/ruby/1.9.1/openssl/buffering.rb:174:in `read_nonblock'
from /usr/lib/ruby/1.9.1/net/protocol.rb:141:in `rbuf_fill'
from /usr/lib/ruby/1.9.1/net/protocol.rb:122:in `readuntil'
from /usr/lib/ruby/1.9.1/net/protocol.rb:132:in `readline'
from /usr/lib/ruby/1.9.1/net/http.rb:2562:in `read_status_line'
from /usr/lib/ruby/1.9.1/net/http.rb:2551:in `read_new'
from /usr/lib/ruby/1.9.1/net/http.rb:1319:in `block in transport_request'
from /usr/lib/ruby/1.9.1/net/http.rb:1316:in `catch'
from /usr/lib/ruby/1.9.1/net/http.rb:1316:in `transport_request'
from /usr/lib/ruby/1.9.1/net/http.rb:1293:in `request'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/http/connection_pool.rb:330:in `request'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/http/net_http_handler.rb:61:in `block in handle'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/http/connection_pool.rb:129:in `session_for'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/http/net_http_handler.rb:55:in `handle'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:244:in `block in make_sync_request'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:280:in `retry_server_errors'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:240:in `make_sync_request'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:502:in `block (2 levels) in client_request'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:382:in `log_client_request'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:468:in `block in client_request'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:364:in `return_or_raise'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/core/client.rb:467:in `client_request'
from (eval):3:in `head_object'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/s3/s3_object.rb:293:in `head'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.23.0/lib/aws/s3/s3_object.rb:270:in `exists?'
from /deb-s3/lib/deb/s3/utils.rb:55:in `s3_exists?'
from /deb-s3/lib/deb/s3/utils.rb:59:in `s3_read'
from /deb-s3/lib/deb/s3/manifest.rb:22:in `retrieve'
from /deb-s3/lib/deb/s3/cli.rb:123:in `block in upload'
from /deb-s3/lib/deb/s3/cli.rb:111:in `each'
from /deb-s3/lib/deb/s3/cli.rb:111:in `upload'
from /var/lib/gems/1.9.1/gems/thor-0.18.1/lib/thor/command.rb:27:in `run'
from /var/lib/gems/1.9.1/gems/thor-0.18.1/lib/thor/invocation.rb:120:in `invoke_command'
from /var/lib/gems/1.9.1/gems/thor-0.18.1/lib/thor.rb:363:in `dispatch'
from /var/lib/gems/1.9.1/gems/thor-0.18.1/lib/thor/base.rb:439:in `start'
from /deb-s3/bin/deb-s3:8:in `<top (required)>'
from /var/lib/gems/1.9.1/bin/deb-s3:19:in `load'
from /var/lib/gems/1.9.1/bin/deb-s3:19:in `<main>'
The text was updated successfully, but these errors were encountered:
This error went away when I added --endpoint=s3-us-west-2.amazonaws.com to the command line options. I'll close this ticket since this seems to fix it. Sorry for the noise.
I'm trying to get a new repo setup with a package built via FPM and when pushing into a fresh s3 bucket I'm seeing the below error. This error is from the tip of master, and I see the same issue from the most recent gem.
Ubuntu 12.04
Ruby 1.9.3
Is there something I need to do to get an initial repo setup? Are there any debug flags I can set to see what it is doing further?
The text was updated successfully, but these errors were encountered: