Bug 152276

Summary: rhn api: list_latest_packages gives package_version as integer instead of string.
Product: [Retired] Red Hat Network Reporter: Pierre Amadio <pamadio>
Component: RHN/OtherAssignee: Mike Orazi <morazi>
Status: CLOSED WONTFIX QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: low Docs Contact:
Priority: medium    
Version: RHN StableCC: acarter, rhn-bugs
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: 2008-10-17 20:05:20 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
illustrate the difference between udev and zsh none

Description Pierre Amadio 2005-03-27 08:58:28 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
rhn api list_latest_packages returns inapprorpiate data type for packages_version https://rhn.redhat.com/rpc/api/channel/software/list_latest_packages/

If the package_version of a given rpm may be interpreted as a string, it returns a string instead of an integer.

This may be problematic for such packages as the current udev when one expect '039' as version   and not 39.



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


How reproducible:
Always

Steps to Reproduce:
1. ask for list_latest_packages for a given channel
2. display all 'package_version' 

  

Actual Results:  you get a mix of integer and strings

Expected Results:  only strings

Additional info:
Comment 1 Pierre Amadio 2005-03-27 09:03:10 UTC 
Created attachment 112373 [details]
illustrate the difference between udev and zsh

i would have expected the udev version to be '039'
Comment 2 Amanda Carter 2008-10-17 20:05:20 UTC 
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.