Bug 23892 - "Ignore this Update" Greyed out
Summary: "Ignore this Update" Greyed out
Status: RESOLVED FIXED
Alias: None
Product: PackageKit
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Richard Hughes
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-12 17:43 UTC by Steven M. Parrish
Modified: 2012-01-05 10:49 UTC (History)
0 users

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 Steven M. Parrish 2009-09-12 17:43:09 UTC
From the downstream Fedora bug report https://bugzilla.redhat.com/show_bug.cgi?id=513960

   Description From  Frank Murphy (frankly3d@gmail.com)  2009-07-27 06:34:10 EDT   (-) [reply]

Description of problem: PK Won't ignore package with depsolving errors.



Version-Release number of selected component (if applicable):

PackageKit-gstreamer-plugin-0.4.8-2.fc11.x86_64
gnome-packagekit-2.27.3-1.fc11.x86_64
fontpackages-filesystem-1.20-2.fc11.noarch
PackageKit-glib-0.4.8-2.fc11.x86_64
PackageKit-0.4.8-2.fc11.x86_64
PackageKit-yum-0.4.8-2.fc11.x86_64
PackageKit-yum-plugin-0.4.8-2.fc11.x86_64
PackageKit-gtk-module-0.4.8-2.fc11.x86_64



How reproducible: Always


Steps to Reproduce:
Installed moonlight-plugin 
http://olea.org/diario/archive/2009/mar-15-1.html

Actual results: PK stays in tray with Depsolving update


Expected results: Ignore Package


Additional info: Sorry cannot screen-grab greyed out sub-menu  

------- Comment #1 From Richard Hughes (rhughes@redhat.com) 2009-07-27 08:16:18 EDT (-) [reply] -------

Somebody needs to implement the code to do the client-side ignoring.  

------- Comment #2 From Frank Murphy (frankly3d@gmail.com) 2009-07-27 08:21:02 EDT (-) [reply] -------

Is that upstream PackageKit?  

------- Comment #3 From Richard Hughes (rhughes@redhat.com) 2009-07-27 13:13:17 EDT (-) [reply] -------

Yup.


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.