Bug 735606 - RFE: disable updates on particular networks
Summary: RFE: disable updates on particular networks
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 15
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-04 02:19 UTC by Michael Ekstrand
Modified: 2012-08-07 16:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-08-07 16:19:03 UTC

Attachments (Terms of Use)

Description Michael Ekstrand 2011-09-04 02:19:18 UTC
PackageKit provides an option to suppress update checks on mobile broadband.  It would be useful to generalize this to other network types, especially wireless, by allowing the user to select certain network connections which should not be used to check for updates (or, alternatively, only allow updates on whitelisted connections).  This would be useful for avoiding update checks on heavily-capped connections such as tethered mobile connections.

For usability, it may be good to integrate this with NetworkManager, so there is an option in the connection settings dialog to enable/disable fetching updates over each connection, and then expose that setting over D-Bus for PackageKit to consult before automatically fetching update information.

Comment 1 Richard Hughes 2011-09-04 17:57:44 UTC
Have you had any ideas on what the UI would look like?

Comment 2 Michael Ekstrand 2011-09-04 19:22:07 UTC
If the UI is provided through NetworkManager, which seems to be the cleanest way to do it, then it could be a checkbox added to the connection settings dialog.  This checkbox could be "Check for updates over this connection".  This feature on that side cold be much more general, however, so it could be "Use this connection for background transfers" or "Disable background transfers on this connection".  The most logical place for this checkbox is probably directly above or below the set of tabs, as it does not seem to belong in any tab.

PackageKit would then just check that flag in the network properties and respect it.  Other tools such as BitTorrent clients and anything else with optional network operations can also use this flag.  I'm not sure how best to communicate to users that respecting this flag requires support in each software package, though.

If the feature is implemented entirely in PackageKit, then the UI becomes more complicated.  Perhaps an "Advanced..." button in the Software Update Preferences dialog.  That would bring up a dialog with a "Use these network connections to check for updates" panel, which could be a ListView of NM connections with check boxes beside them to disable network checking on them.

Comment 3 Fedora End Of Life 2012-08-07 16:19:08 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:

Note You need to log in before you can comment on or make changes to this bug.