<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Manuel Amador (Rudd-O) wrote:
<blockquote cite="mid200903131056.08524.rudd-o@rudd-o.com" type="cite">
<meta name="qrichtext" content="1">
<style type="text/css">p, li { white-space: pre-wrap; }</style>1) The
Python StrictVersion and LooseVersion classes in Setuptools used to
validate and compare versions are incompatible with RPM's
lexicographical order. Even the setuptools metadata documentation,
which is in full force and implemented, says alpha and beta and rc are
expressly permitted (and ENCOURAGED) in the version name, and
setuptools' dependency resolution actually uses that information. </blockquote>
Then this is a 'setuptools' ERROR. Go fix it in setuptools. If
setuptools creates lexigraphically stupid version and release strings
that are incompatible with RPM then that is a 'setuptools' problem, NOT
a bdist_rpm problem.<br>
<br>
Go fix 'setuptools'.<br>
<br>
<br>
Again, I'm a big -1 on this patch. There is nothing broken in
'bdist_rpm'. But there is obviously something broken in 'setuptools'.<br>
<br>
<br>
Regards,<br>
Gerry<br>
<br>
</body>
</html>