Skip to content

easy_install fails with conflicting paver-minilib.zip files #46

Closed
ponty opened this Issue Jan 26, 2012 · 9 comments

3 participants

@ponty
ponty commented Jan 26, 2012

If paver-minilib.zip is generated for different dependant packages with different paver version
then easy_install can fail.
Example: ponty/PyVirtualDisplay#5

Possible workarounds:

  • using pip instead easy_install
  • calling easy_install more times: first fails, second succeeds
  • uploading all package with latest paver-minilib.zip
@ponty
ponty commented Feb 5, 2012

I resolved this problem by downgrading paver to 1.0.3

@Almad Almad was assigned Feb 5, 2012
@Almad
Paver community member
Almad commented Feb 5, 2012

By downgrading, you mean the paver you generated paver-minilib with?

@ponty
ponty commented Feb 6, 2012

Yes, I installed paver 1.0.3, then I regenerated paver-minilib in all projects, then I uploaded all packages to PyPI.
No more easy_install error.

@Almad
Paver community member
Almad commented Feb 6, 2012

OK, this should be fixed when new version is released then.

I will try to figure out how to release RC versions in such a way that they are available to easy_install on request, but not by default for new installs.

@yedpodtrzitko
Paver community member

what about add paver version as a suffix to minilib filename (ie paver-minilib-1_0_5.zip)?

@Almad
Paver community member
Almad commented Apr 3, 2012

@yedpodtrzitko IMO, this should be optional as it breaks backward compatibility.

@yedpodtrzitko yedpodtrzitko was assigned Apr 3, 2012
@yedpodtrzitko
Paver community member

@Almad what should be default status of this option, in your opinion? Buggy with warning message or backward-incompatible?

@Almad
Paver community member
Almad commented Apr 3, 2012

@yedpodtrzitko I'd go for buggy with deprecation warning when bad configuration is detected, as most people are using pip instead of easy_install those days, so I thing this bug is not so common.

@yedpodtrzitko
Paver community member

imho fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.