Bug 152276 - rhn api: list_latest_packages gives package_version as integer instead of string.
Summary: rhn api: list_latest_packages gives package_version as integer instead of str...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Other
Version: RHN Stable
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Mike Orazi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-27 08:58 UTC by Pierre Amadio
Modified: 2008-10-17 20:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-17 20:05:20 UTC
Embargoed:


Attachments (Terms of Use)
illustrate the difference between udev and zsh (408 bytes, text/plain)
2005-03-27 09:03 UTC, Pierre Amadio
no flags Details

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.


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