Bug 440549 - First ever FasTrack security release
Summary: First ever FasTrack security release
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gnome-screensaver
Version: 5.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-03 22:24 UTC by Johnny Hughes
Modified: 2023-09-14 01:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-03 12:37:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Johnny Hughes 2008-04-03 22:24:32 UTC 
Description of problem:
There gnome-screensaver security release on 5.1 FasTrack announced today.

The version is:

gnome-screensaver-2.16.1-8.el5.src.rpm

Is  that only a security update for gnome-screensaver-2.16.1-6.el5 (in FasTrack)
or is that also a security update for gnome-screensaver-2.16.1-5.el5 which is in
the main RHEL5 branch?
Comment 1 RHEL Program Management 2014-03-07 12:43:15 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 2 RHEL Program Management 2014-06-03 12:37:24 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Comment 3 Red Hat Bugzilla 2023-09-14 01:12:20 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.