[Discover] [Bug 399371] offline update whitelist

2024-07-09 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=399371

soredake  changed:

   What|Removed |Added

 CC|katyaberezy...@gmail.com|

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2023-12-13 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=399371

Daniel  changed:

   What|Removed |Added

   Platform|Snap|Flatpak

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2023-12-13 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=399371

Daniel  changed:

   What|Removed |Added

   Platform|Other   |Snap

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2023-12-13 Thread Daniel
https://bugs.kde.org/show_bug.cgi?id=399371

Daniel  changed:

   What|Removed |Added

 CC||onlineplayer...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2022-04-01 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=399371

Nate Graham  changed:

   What|Removed |Added

 CC||aleix...@kde.org
   Severity|normal  |wishlist
  Component|PackageKit  |Updates (offline)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2021-08-15 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=399371

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2021-05-11 Thread Alex
https://bugs.kde.org/show_bug.cgi?id=399371

Alex  changed:

   What|Removed |Added

 CC||alex...@protonmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-11-22 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=399371

--- Comment #6 from Harald Sitter  ---
(In reply to Aleix Pol from comment #5)
> All packagekit packages are offline?

Really long term yes. Yes.

Perhaps somewhat less long term: anything that is not associated with an
application component in appstream.

Ultimately this could be a distro side decision actually, depending on the
specific distribution either may be suitable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-11 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=399371

--- Comment #5 from Aleix Pol  ---
@Harald If this is a transient thing, what would the end-goal be?

All packagekit packages are offline?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-09 Thread Harald Sitter
https://bugs.kde.org/show_bug.cgi?id=399371

--- Comment #4 from Harald Sitter  ---
@Neal this is a transient thing. the long term goal is to have offline updates
enabled for "some" parts of the system (the some part being real long term
anything that is not a bundle IMO). However, before we go there we need a way
to actually test this in production. That's where the whitelist comes in. We
can have very limited coverage so users do not get offline updates all that
often, but just often enough to give us feedback on the user experience.

@Aleix

example list for neon

```
- nvidia-*
- linux-image-*
- libkf5kio5
```

If any of these is in the set of packages for update the entire update would be
switched to offline behavior.

Discover could instead call a helper binary and give it the list of packageids
and that returns 0 or 1 based on whether the update should be offline? Which
not that I am thinking about it may be the nicer solution from a discover POV.

UX-wise I expect this should be much like the final goal for offline updates:

- User starts updater
- clicks upate all
- update runs; includes nvidia-* so it runs offline
- discover informs the user that they need to restart to complete the update
- updater plasmoid changes icon and is now in "restart" mode where it asks the
user to restart to apply the update and has a button in the popup to start the
restart
- user reboots; updates apply; restarts to updated system

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-08 Thread Fabian Vogt
https://bugs.kde.org/show_bug.cgi?id=399371

Fabian Vogt  changed:

   What|Removed |Added

 CC||fab...@ritter-vogt.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-08 Thread Neal Gompa
https://bugs.kde.org/show_bug.cgi?id=399371

--- Comment #3 from Neal Gompa  ---
Also, to the idea of a package whitelist, that's absolutely bonkers. I don't
know how that would reasonably scale. And how do you deal with virtual
packages, renames, splits, etc?

It's too cumbersome. It's better to use a property to identify what qualifies
as non-OS content to not trigger an offline update.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-08 Thread Neal Gompa
https://bugs.kde.org/show_bug.cgi?id=399371

Neal Gompa  changed:

   What|Removed |Added

 CC||ngomp...@gmail.com

--- Comment #2 from Neal Gompa  ---
>From a Fedora and Mageia perspective, I would expect that the filter for
mandating offline updates would be when you're requesting updates of content
that doesn't have AppStream data. GNOME Software filters this way
automatically, and things not associated with an app update will be set aside
in the "OS updates" category and that triggers a reboot.

I imagine the same mechanism would make sense here, and unifies the handling
across packages, flatpaks, and snaps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-08 Thread Aleix Pol
https://bugs.kde.org/show_bug.cgi?id=399371

--- Comment #1 from Aleix Pol  ---
How would you have this work?
Could you tell me what kind of whitelist you have in mind for e.g. Neon?

Also feedback on how this should work for Fedora/Suse would be useful.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-05 Thread Rex Dieter
https://bugs.kde.org/show_bug.cgi?id=399371

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 399371] offline update whitelist

2018-10-05 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=399371

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.