Bug 595418 - gnome-panel has too many patches
gnome-panel has too many patches
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-panel (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Ray Strode [halfline]
: Rebase
Depends On:
  Show dependency treegraph
Reported: 2010-05-24 11:01 EDT by Ray Strode [halfline]
Modified: 2010-11-10 15:31 EST (History)
3 users (show)

See Also:
Fixed In Version: gnome-panel-2.30.2-1.el6
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 15:31:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ray Strode [halfline] 2010-05-24 11:01:21 EDT
Right now gnome-panel has a lot of patches in it.  We should try to trim the ones that don't matter and/or update to a later upstream version to drop some that way.
Comment 1 RHEL Product and Program Management 2010-05-24 11:06:28 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 5 Tomas Pelka 2010-06-24 09:30:01 EDT
Have no idea what all should we test, guess that basic sanity of this package could be sufficient.

Test results here:
no blockers appears during testing, think we can mark this issue as verified.

Feel free to reopen this bug when you need some additional testing.
Comment 6 releng-rhel@redhat.com 2010-11-10 15:31:18 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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