Bug 26684 (Dante) - PackageKit's order of operation issues.
Summary: PackageKit's order of operation issues.
Status: RESOLVED NOTABUG
Alias: Dante
Product: PackageKit
Classification: Unclassified
Component: backend-apt (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium major
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-21 10:03 UTC by Dante Ashton
Modified: 2018-08-21 15:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dante Ashton 2010-02-21 10:03:03 UTC
Hey,

I've got a bit of a major problem with KPackageKit. 
(My apologies if I'm doing this incorrectly, I haven't used Bugzilla before)

After having a few networking problems, I decided to replace my network manager; doing this through PackageKit was fairly easy, if only for one major part;
After asking PackageKit to install a new networking manager, it had correctly identified a package conflict and would thus remove the offending package (the old network manager)

However, it would do this before downloading the new package...which of course means I get an error that I cannot connect to the 'net to download the new package.

This *could* be solved by running through the terminal, however I do not beleive users of PackageKit should do so, nor is it currently possible to do so when using mobile broadband dongles (such as I'm doing)

I would ask that instead of PackageKit's apparent -Remove-Download-Install- method of operation, it is instead -Download-Remove-Install-

Thank you for your time.
Comment 1 Richard Hughes 2018-08-21 15:52:59 UTC
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
 
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.