Bug 474872 - Fedora 10 has an outdated version of lsscsi (0.17). Should be 0.21 (available in Fedora 9 Updates).
Summary: Fedora 10 has an outdated version of lsscsi (0.17). Should be 0.21 (available...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: lsscsi
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-05 17:36 UTC by bcling
Modified: 2008-12-07 15:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-07 15:43:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description bcling 2008-12-05 17:36:29 UTC
Description of problem:

lsscsi produces some errors on STDOUT and does not display device numbers. Update was pushed to Fedora 9 but has not shown up in Fedora 10.

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

Old version of lsscsi (0.17), should be updated to 0.21.

How reproducible:

100%

Steps to Reproduce:
1. lsscsi
  
Actual results:

# lsscsi
sdev_scandir_sort: left parse failed
sdev_scandir_sort: left parse failed
sdev_scandir_sort: left parse failed
sdev_scandir_sort: right parse failed
[target0:0:0]type?   vendor?  model?           rev?  -       
[target1:0:0]type?   vendor?  model?           rev?  -       
[0:0:0:0]    disk    ATA      ST9160821A       3.AL  -       
[1:0:0:0]    cd/dvd  MATSHITA UJDA747 DVD/CDRW 1.20  - 

Expected results:

# lsscsi
[0:0:0:0]    disk    ATA      ST9160821A       3.AL  /dev/sda
[1:0:0:0]    cd/dvd  MATSHITA UJDA747 DVD/CDRW 1.20  /dev/sr0

Additional info:

Tested with lsscsi-0.21-2.fc9.i386.rpm

Comment 1 Dan Horák 2008-12-05 18:27:43 UTC
It was sitting in updates-testing but I have already requested the move to regular updates earlier today.

Comment 2 bcling 2008-12-06 02:28:12 UTC
Oops. Don't know how I missed that in testing. fc10 release works fine too. Thanks.


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