Bug 190915

Summary: yum list format truncates version numbers
Product: [Fedora] Fedora Reporter: Ed Hill <ed>
Component: yumAssignee: Jeremy Katz <katzj>
Status: CLOSED CANTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: katzj
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-25 17:35:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
a simple patch to keep from truncating version information in simpleList none

Description Ed Hill 2006-05-06 12:26:39 UTC 
Description of problem:
The output from "yum list" truncates version numbers and there 
does not appear to be any way (short of perhaps writing a yum 
plugin) to change the output format.

Version-Release number of selected component (if applicable):
yum-2.6.1-0.fc5

How reproducible:
every time

Steps to Reproduce:
1. run "yum list 'kmod*'"
2. notice that version numbers in output are truncated

  
Actual results:
Version numbers are truncated and heres an example:

  kmod-madwifi.i686              0.0.0.20060317-3.2.6.1 livna

Notice how its impossible to tell *which* kernel version this particular 
kmod package corresponds to since the critical parts of the version 
information have been cut off.  Bad, bad!

Expected results:
Output formatting should preserve the full version information.
Acceptable solutions include increasing the width of the output.
Comment 1 Ed Hill 2006-05-06 14:12:54 UTC 
Created attachment 128694 [details]
a simple patch to keep from truncating version information in simpleList
Comment 2 Ed Hill 2006-06-28 02:08:46 UTC 
Hi folks, any news here?
Comment 3 Jeremy Katz 2006-09-18 20:35:26 UTC 
The problem with this is that it then "overflows" a standard terminal :/
Comment 4 Jeremy Katz 2007-04-25 17:35:17 UTC 
Breaking the terminal output isn't really an option.. and there's no good wya to
find out the width we can go to without using something like curses (... which
we really don't want to do)