> The UUID is only appended by UDM in two cases: if the app is confined, or if > it's unconfined and the client has sent a > LOCAL_PATH_KEY metadata value.
Partially true, the UUID is used to uniquely indentify the download in the download manager. It is appended if the file is present in the file system in any case, even if the LOCAL_PATH_KEY metadata is used. LOCAL_PATH_KEY is used if you want to specify a diff directory to perform the download for example rather than to tell if it should be overwritten. Maybe added an override flag in the metadata of the download might be a good idea. > I filed a separate UDM bug to log more errors unconditionally. Makes perfect sense, I'll try to fix that bug ASAP as well as bug #1269078 so that the error code is stated in the logs. > Of course, once pkcon fails one time, UDM won't delete the downloaded package and we'll get the renaming again. That is not the case. The emition of the signal is done via the emitError method. The method does not only emit the error but stops the QNEtworkRely, disconnects from the signals and DELETES the file. > However, the real strange thing to me is why the file already exists in this case. This is precisely the real issue (at least for UDM), There are several cases when this can happen, for example, the phone is switched off during the installation of the package, or while the download is being processed (and we do not have the full file in the path but part of it). WE need to think carefully about what to do when the user stops the process in an unexpected moment. > As for whose bug it is, I don't care-- I just care so that the bug is fixed correctly rather than not masked for the time being, I'm really happy to fix bugs in UDM all the time is just that in this case we are in the middle of nowhere :-) > Maybe this is essentially what Mozilla calls an "evangelism" bug - that > is, we need to go and get the relevant third-party developers to update > their packages. If we killed off all pre-0.3 packages, this bug would > be irrelevant. Completely agree, if UDM and click are fixed we need to tell the developers to fix the packages. I wonder if there is a script that can be done to do this automaticaly and point to this bug as a reason. By the way, "evangelism" bug is a great term! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269058 Title: connect4 always fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-download-manager/+bug/1269058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
