Bug 489643 - distutils produces invalid RPM packages of prerelease python packages
Summary: distutils produces invalid RPM packages of prerelease python packages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: python
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-11 03:42 UTC by Rudd-O DragonFear
Modified: 2011-06-27 14:07 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-27 14:07:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
fix for distutils (1.56 KB, patch)
2009-03-11 03:43 UTC, Rudd-O DragonFear
no flags Details | Diff
prerequisite fix for bdist_rpm (2.87 KB, patch)
2009-03-11 04:23 UTC, Rudd-O DragonFear
no flags Details | Diff
updated for svnversions use case (1.11 KB, patch)
2009-03-11 07:53 UTC, Rudd-O DragonFear
no flags Details | Diff
replaces others, handles improvement of corner cases, provides packager with the ability to turn it off (2.49 KB, patch)
2009-03-13 05:51 UTC, Rudd-O DragonFear
no flags Details | Diff
applies on top of the last one (lexicographical order), introduces automatic dependency detection based on egg metadata if available (3.08 KB, patch)
2009-03-13 08:33 UTC, Rudd-O DragonFear
no flags Details | Diff
fixed lexicographical order patch (2.53 KB, patch)
2009-03-13 11:33 UTC, Rudd-O DragonFear
no flags Details | Diff

Description Rudd-O DragonFear 2009-03-11 03:42:29 UTC
Description of problem:

Building pre-release python distutils packages with python setup.py bdist_rpm works, but the version number is "RPM-higher" than the official release package that is released later.

This constitutes a problem because many of the components in major Python apps like Zope -- distributed as cheese shop eggs and downloadable via pip or buildout -- are pre-release packages which, when turned into RPMs, contain RPM-invalid version numbers.  The RPMs build, but the pre-release packages are considered "newer" by yum, so you can imagine the havoc that breaks.

How reproducible:

always


Steps to Reproduce:
1. python setup.py bdist_rpm
2. inspect version / release number of resulting RPMs, find out it's wrong
3. do not profit!
  
Actual results:

distutils package version: 1.4a
rpm package version: 1.4a


Expected results:

http://fedoraproject.org/wiki/Packaging/NamingGuidelines#Non-Numeric_Version_in_Release

Additional info:

patch attached.  works against python 2.4, may apply fine to python 2.5 or 2.6 too since distutils hasn't undergone that big of a rewrite.

Comment 1 Rudd-O DragonFear 2009-03-11 03:43:02 UTC
Created attachment 334744 [details]
fix for distutils

Comment 2 Rudd-O DragonFear 2009-03-11 04:23:19 UTC
Heads up: The fix requires a patch (distributed with the python 2.4.x RPM in CentOS) to be applied first.  I am attaching said patch so you can apply the fix.

Comment 3 Rudd-O DragonFear 2009-03-11 04:23:55 UTC
Created attachment 334746 [details]
prerequisite fix for bdist_rpm

Comment 4 Rudd-O DragonFear 2009-03-11 07:53:23 UTC
Created attachment 334759 [details]
updated for svnversions use case

the newest svnversions patch is to handle the case of people who want to build svn checkouts (usually versionnumbered by dev or dev-rXXXYYZZ).  it overrides the release to be zero so they never upgrade alpha, beta packages.

Comment 5 Rudd-O DragonFear 2009-03-13 05:51:06 UTC
Created attachment 335056 [details]
replaces others, handles improvement of corner cases, provides packager with the ability to turn it off

Comment 6 Rudd-O DragonFear 2009-03-13 08:33:09 UTC
Created attachment 335062 [details]
applies on top of the last one (lexicographical order), introduces automatic dependency detection based on egg metadata if available

Comment 7 Rudd-O DragonFear 2009-03-13 11:33:27 UTC
Created attachment 335073 [details]
fixed lexicographical order patch

brown paper bug in the last lexic patch

Comment 8 Bug Zapper 2009-11-18 11:19:40 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Dave Malcolm 2009-12-02 22:33:32 UTC
See also http://www.python.org/dev/peps/pep-0386/

Comment 10 Bug Zapper 2009-12-18 08:59:47 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 11 Dave Malcolm 2009-12-18 14:23:24 UTC
Reopening; this was closed by an automated process; I want to review this further.

Comment 12 Bug Zapper 2010-03-15 12:28:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 13 Bug Zapper 2011-06-02 18:13:17 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 14 Bug Zapper 2011-06-27 14:07:39 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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