What should happen if the destination file exists?

I'm leaning to the following implementation:

If the local-path is provided and we are not a confined application:
  2) Throw a DBus exception (e.g. the moral equivalent of EEXIST)
if not confined:
 3) Append a .1 to the file name. (although I'm appending a uuid to make sure we do not have an extra loop)

On Sep 25, 2013, at 11:59 AM, Manuel de la Peña wrote:

>I'm leaning to the following implementation:
>
>If the local-path is provided and we are not a confined application:
> 2) Throw a DBus exception (e.g. the moral equivalent of EEXIST)
>if not confined:
> 3) Append a .1 to the file name. (although I'm appending a uuid to make sure we do not have an extra loop)

I'm a bit confused. Do you mean if you *are* confined you'll do #3? I think
for an unconfined app (e.g. system-image), the exception would be best. I
won't be expecting a file name with .<uuid> and wouldn't be looking for it.
(OTOH, I would never expect that the destination file would exist - that would
be a bug in my code.)

Fix committed into lp:ubuntu-download-manager at revision 146, scheduled for release in ubuntu-download-manager, milestone 0.3

This bug was fixed in the package ubuntu-download-manager - 0.2+13.10.20130930-0ubuntu1

---------------
ubuntu-download-manager (0.2+13.10.20130930-0ubuntu1) saucy; urgency=low

  [ Manuel de la Pena ]
  * Deal with the presence of the download file in a nicer way. (LP:
    #1228254)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 146
 -- Ubuntu daily release <email address hidden> Mon, 30 Sep 2013 14:28:20 +0000