| Summary: | Don't install gpk-update-viewer by default | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Allan Day <aday> |
| Component: | gnome-packagekit | Assignee: | Richard Hughes <rhughes> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | awilliam, mclasen, rhughes, robatino |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gnome-packagekit-3.10.0-2.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-12 04:34:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 980651 | ||
|
Description
Allan Day
2013-09-26 15:03:21 UTC
Nominating this as a Beta blocker per criterion "Release-blocking desktops must notify the user of available updates, but must not do so when running as a live image." - https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria#Update_notification It's a bit of a stretch because current F20 _does_ notify the user, but it notifies the user _twice_, and one notification (as Allan notes) is hooked into a mechanism we don't want to be the default any more (and possibly don't want to block the release on), so that's a big problem. http://koji.fedoraproject.org/koji/buildinfo?buildID=470358 is a build that has gpk-update-viewer and gpk-application split out as subpackages. gnome-packagekit-3.10.0-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/gnome-packagekit-3.10.0-2.fc20 gnome-packagekit-3.10.0-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. |