** Changed in: duplicity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904622
Title:
boto3+s3 bucket fails
To manage notifications about this bug go
Apologies for the wild goose chase, you are, expectedly, correct.
I had seen the boto/S3 sections in the man page, however I never
connected the dots that between the boto -> boto3 transition, the
hostname of the s3 url was deprecated in favor of specifying only the
bucket name.
I merely
** Changed in: duplicity
Importance: Medium => Undecided
** Changed in: duplicity
Status: In Progress => Invalid
** Changed in: duplicity
Milestone: 0.8.18 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, it took me a while to grok that you were using the boto3 backend.
The format for a boto3 URL is boto3+s3://bucket_name[/prefix]. It's in
the man page and usage screen.
Make that change and let me know how it went.
--
You received this bug notification because you are a member of Ubuntu
Thanks for the thorough analysis.
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Milestone: None => 0.8.18
** Changed in: duplicity
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Attached output is from a fresh multipass instance of focal, only repro
steps after multipass launch were to create aws creds in
~/.aws/credentials and $ sudo snap install duplicity --classic.
** Attachment added: "duplicity_snap_nonworking.log"
Please upgrade to the current version of duplicity. This will assure
that any bugs fixed since your release are available and may fix your
issue. Current release is 0.8.17.
I would suggest using one of the snap builds if at all possible.
There are multiple options both stable and daily:
-
** Changed in: duplicity (Ubuntu)
Importance: Undecided => Low
** Changed in: duplicity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904622
Title:
** Attachment added: "boto3 credential verification"
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1904622/+attachment/5436048/+files/boto3_demo_working.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For the sake of pointing out the AWS creds which I think is what you are
hinting at with "check permission keys".
As I was in my original bash script, and for testing I am exporting in my shell:
AWS_ACCESS_KEY_ID=$akey
AWS_SECRET_ACCESS_KEY=$sakey
PASSPHRASE=$passphrase
s3cmd seemed to like this
Have you tried reading your files with s3cmd or another tool?
If that works, check permission keys etc..
If that does not work, I'd like a log file, please. This is going big
and I only need a portion. Please run with -v9, redirect to a log file,
then run:
$ head -n 200 < log > log.head
$ tail
11 matches
Mail list logo
