Bug 185392 - Incorrect error message about hexadecimal digits
Summary: Incorrect error message about hexadecimal digits
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-bind
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Martin Stransky
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-14 10:12 UTC by Göran Uddeborg
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: FC5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-17 11:28:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Göran Uddeborg 2006-03-14 10:12:09 UTC 
Description of problem:
In sysstem-config-bind, line 508 of RRGUI.py, there is a message about bad
characters in an hexadecimal IPv6 address.  But the error message claims all
ASCII letters (A-Z) should be valid.  This is incorrect, only characters in the
range A-F are valid.  (The actual check in the code a few lines above is
correct.)  The ranges in the error message should be corrected.

Version-Release number of selected component (if applicable):
system-config-bind-4.0.0-38_FC4
Comment 1 Jason Vas Dias 2006-03-14 20:26:14 UTC 
Thanks - sorry for the typo. Fixed in CVS - will go into next version (4.0.0-42+).
Comment 2 Bill Nottingham 2006-09-22 02:15:11 UTC 
Closing bugs in MODIFIED state from prior Fedora releases. If this bug persists
in a current Fedora release (such as Fedora Core 5 or later), please reopen and
set the version appropriately.
Comment 3 Göran Uddeborg 2006-09-24 10:33:18 UTC 
It is still there when I look:

server2$ rpm -q system-config-bind
system-config-bind-4.0.0-42_FC5
server2$ sed -n 508p /usr/share/system-config-bind/RRGUI.py
            s.dialog.gui.modalError(s.dialog.dialog,_('Invalid IPv6 Address "%s"
contains invalid hex digits : only [0-9] [A-Z] [a-z] allowed.') % hex)
Comment 4 Martin Stransky 2006-10-17 11:28:26 UTC 
fixed in rawhide now.
Note You need to log in before you can comment on or make changes to this bug.