Bug 73099 - "redhat-config-date" allows time not supported by GNU date utility
"redhat-config-date" allows time not supported by GNU date utility
Status: CLOSED DEFERRED
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-date (Show other bugs)
null
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Brent Fox
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-08-30 14:53 EDT by Peter van Egdom
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-08-30 14:56:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Year 2046 unsupported by GNU date but supported by redhat-config-date (61.50 KB, image/png)
2002-08-30 14:56 EDT, Peter van Egdom
no flags Details

  None (edit)
Description Peter van Egdom 2002-08-30 14:53:01 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826

Description of problem:
The "redhat-config-date" tool allows the user to set a date which is
unsupported by the GNU date tool.

See screenshot.

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


How reproducible:
Always

Steps to Reproduce:
1. Start redhat-config-date
2. Select 2053 as year.
3.
	

Actual Results:
Observe that redhat-config-date allows to set this year, but GNU's date
utility doesn't.

Expected Results:  Consistency :-)

Additional info:

redhat-config-date-1.5.2-7
sh-utils-2.0.12-2
Comment 1 Peter van Egdom 2002-08-30 14:56:08 EDT
Created attachment 74004 [details]
Year 2046 unsupported by GNU date but supported by redhat-config-date
Comment 2 Brent Fox 2002-08-30 16:54:01 EDT
I hope I get this fixed by 2046.  ;)

Seriously though, it's too late to change this for this release, but I'll take a
look at it for the next release.  Deferring for now.

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