Bug 1038670 - spice-server spec-file: fix some dates mismatch in the changelog
Summary: spice-server spec-file: fix some dates mismatch in the changelog
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 15:39 UTC by Uri Lublin
Modified: 2014-10-14 05:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
No doc needed
Clone Of:
Environment:
Last Closed: 2014-10-14 05:04:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
spice-server: spec-file: fix date mismatch (2.30 KB, patch)
2013-12-05 15:40 UTC, Uri Lublin 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1435 0 normal SHIPPED_LIVE spice-server bug fix update 2014-10-14 01:06:04 UTC

Description Uri Lublin 2013-12-05 15:39:46 UTC 
Description of problem:
Fix some date mismatch in the spec-file changelog.
See attached patch.

* Jan 11 2009 is actually a Sunday.
* Jul 28 2011 is actually a Thursday.
* Jun 05 2011 is actually a Sunday.
* Mar  7 2010 is actually a Sunday.
* May 19 2013 is actually a Sunday.
Comment 1 Uri Lublin 2013-12-05 15:40:56 UTC 
Created attachment 833219 [details]
spice-server: spec-file: fix date mismatch
Comment 2 Uri Lublin 2013-12-05 15:45:25 UTC 
To be specific: No code change.
Comment 5 errata-xmlrpc 2014-10-14 05:04:45 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1435.html
Note You need to log in before you can comment on or make changes to this bug.