Use log codes for common backend errors

[Michael Terry]

Most/all backends currently just raise BackendExceptions when an error occurs. It would be nice to include more information, including log codes for wrapper consumption.

I'm working on the patch.

[Michael Terry (mterry)]

Ken, this doesn't seem to have been applied to the 0.6.11 tarball after all?

[Kenneth Loafman (kenneth-loafman)]

I've reversed out the LP status. Will get it into the next release, soon.

Looks like it was merged into the 0.7 series, not 0.6.

...Ken

On Sun, Nov 21, 2010 at 5:50 PM, Michael Terry
<email address hidden>wrote:

> Ken, this doesn't seem to have been applied to the 0.6.11 tarball after
> all?
>
> --
> Use log codes for common backend errors
> https://bugs.launchpad.net/bugs/578663
> You received this bug notification because you are subscribed to
> Duplicity.
>
> Status in Déjà Dup: Fix Released
> Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Released
>
> Bug description:
> Most/all backends currently just raise BackendExceptions when an error
> occurs. It would be nice to include more information, including log codes
> for wrapper consumption.
>
> I'm working on the patch.
>
>
>

[Kenneth Loafman (kenneth-loafman)]

I just tried to merge the two branches above and got 'nothing to do' from bzr. Are you sure about this?

[Kenneth Loafman (kenneth-loafman)]

Either bazaar is screwed up, or there's something else going on here. A 'bzr diff' yields nothing...

ken@stealth:~/workspace/duplicity-0.6-series$ bzr diff https://code.launchpad.net/~mterry/duplicity/backend-log-codes
ken@stealth:~/workspace/duplicity-0.6-series$ bzr diff https://code.launchpad.net/~mterry/duplicity/backend-log-codes2

[Michael Terry (mterry)]

I'm not a bzr expert, but I'm not sure if diff can be used between divergent branches like that. I think you have to use --old or --new to specify which branch is to be treated as the newer one.

I've filed a new branch here against 0.6: https://code.launchpad.net/~mterry/duplicity/backend-log-codes3/+merge/42759

[Kenneth Loafman (kenneth-loafman)]

Will get it in ASAP.

...Ken

On Sat, Dec 4, 2010 at 4:16 PM, Michael Terry
<email address hidden>wrote:

> I'm not a bzr expert, but I'm not sure if diff can be used between
> divergent branches like that. I think you have to use --old or --new to
> specify which branch is to be treated as the newer one.
>
> I've filed a new branch here against 0.6:
> https://code.launchpad.net/~mterry/duplicity/backend-log-<https://code.launchpad.net/%7Emterry/duplicity/backend-log->
> codes3/+merge/42759
>
> ** Changed in: duplicity
> Status: Fix Released => Triaged
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/578663
>
> Title:
> Use log codes for common backend errors
>
> Status in Déjà Dup:
> Fix Released
> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
> Triaged
>
> Bug description:
> Most/all backends currently just raise BackendExceptions when an error
> occurs. It would be nice to include more information, including log codes
> for wrapper consumption.
>
> I'm working on the patch.
>
>
>