#869 F18 Feature: Offline Updates using systemd and packagekit - https://fedoraproject.org/wiki/Features/OfflineSystemUpdates
Closed None Opened 6 years ago by rbergero.

For 2012-06-18 FESCo meeting.


This might be removed or making configurable in settings: "Verify that you are not notified about available updates before they have been downloaded "
If you are using mobile connection or roaming, it could be expensive.

I'm also not sure if developers shouldn't test their apps after update with yum and second time after system update.

Which packages will be in those updates? All available updates will be downloaded or only system updates?

I'd rather don't vote on this one without further discussion.

After heated debate with people from rpm, yum, who were unaware of the feature, I'd like to change my statement to -1. Shouldn't feature owners push this change as a feature for rpm and track the real problems low level? More discussion with rpm/yum people can't hurt.

Replying to [comment:1 mmaslano]:

I'd rather don't vote on this one without further discussion.

We've answered a lot of the questions on the talk page, but feel free to add another comment if we've not quelled any fears you've got.

Replying to [comment:2 mmaslano]:

After heated debate with people from rpm, yum, who were unaware of the feature, I'd like to change my statement to -1. Shouldn't feature owners push this change as a feature for rpm and track the real problems low level? More discussion with rpm/yum people can't hurt.

This isn't being driven by Fedora. I've also got no idea why this should have caused a heated debate. This is a distribution-agnostic feature that is going to be used by all the distros shipping GNOME3. I've discussed this quite a lot with other distributions and the overwhelming consensus is it's the right thing to do. We can't realistically do this kind of thing in rpm or yum as it's logically a higher level than a package manager that downloads packages and installs files. YUM can't access the session and find out if the user is idle, nor can it access the user proxy settings, wireless broadband preference or find out if applications are actually running.

From a rpm point of view, nothing is changing. We're still using yum to apply the updates.
From a yum point of view, it's being asked by PackageKit to download specific packages in the session to the existing yum cache and then it's being asked to update those packages in a special boot mode where nothing else is running.

If you want to talk about this on IRC feel free to ping me (hughsie on GIMPNet/Freenode) and I can discuss this. If someone can also ping me for the meeting on Monday, I'd really appreciate that. Thanks.

This Feature was approved at the 2012-06-18 meeting.

Login to comment on this ticket.

Metadata