Bug 1161912

Summary: too many spaces ...
Product: Red Hat Enterprise Linux 7 Reporter: Karel Srot <ksrot>
Component: fileAssignee: Jan Kalu┼ża <jkaluza>
Status: CLOSED ERRATA QA Contact: Stanislav Zidek <szidek>
Severity: low Docs Contact:
Priority: low    
Version: 7.0CC: jkaluza, lkocman, szidek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: file-5.11-23.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 664513 Environment:
Last Closed: 2015-11-19 08:09:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1110700, 1191021    

Description Karel Srot 2014-11-09 09:48:59 UTC
the bug is present also on rhel-7

$ file bz664513/bin.iso
bz664513/bin.iso: # ISO 9660 CD-ROM filesystem data 'CDROM                           '

+++ This bug was initially created as a clone of Bug #664513 +++

Description of problem:

file ../ic60/RHEV-toolsSetup_2.3_130.iso 
../ic60/RHEV-toolsSetup_2.3_130.iso: ISO 9660 CD-ROM filesystem data 'RHEV-tools                     '


[lkocman@dhcp-28-248 ISO]$ file a.txt
a.txt: cannot open `a.txt' (No such file or directory)

^ This one also looks quiet weird with that back-stick ^

[lkocman@dhcp-28-248 ISO]$ file Fedora-14-i386-DVD.iso 
Fedora-14-i386-DVD.iso: ISO 9660 CD-ROM filesystem data 'Fedora 14 i386 DVD             ' (bootable)

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


Actual results:

'RHEV-tools                     '
'Fedora 14 i386 DVD             ' (bootable)

Expected results:

'Fedora 14 i386 DVD' (bootable)

Additional info:

Shouldn't be somehow checked length of the string except of setting some FIXED_LENGTH?

Comment 2 Karel Srot 2015-04-20 14:32:13 UTC
*** Bug 1162130 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2015-11-19 08:09:44 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.