Closed
Bug 629721
Opened 14 years ago
Closed 14 years ago
Package failure when installing ManifestDestiny (depend on fixed 0.1.5 version)
Categories
(Testing :: Mozbase, defect)
Testing
Mozbase
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Keywords: regression, Whiteboard: [mozmill-1.5.2+])
Attachments
(1 file)
(deleted),
patch
|
k0scist
:
review+
|
Details | Diff | Splinter Review |
The newly uploaded Mozmill 1.5.2RC1 has a critical issue. The dependent ManifestDestiny cannot be installed because of package failures. Now that Mozmill Crowd uses the most recent version of the pypi package we broke the extension too. I hate to say that but why does pypi doesn't support beta update channels. :(
Installed /Volumes/data/testing/crowd/mozmill-env/lib/python2.6/site-packages/mozmill-1.5.2rc1-py2.6.egg
Processing dependencies for mozmill
Searching for ManifestDestiny>=0.1
Reading http://pypi.python.org/simple/ManifestDestiny/
Reading https://wiki.mozilla.org/Auto-tools/Projects/ManifestDestiny
Best match: ManifestDestiny 0.2
Downloading http://pypi.python.org/packages/source/M/ManifestDestiny/ManifestDestiny-0.2.tar.gz#md5=bdc425b32c06ded1e7f88c88c6669ee5
Processing ManifestDestiny-0.2.tar.gz
error: Couldn't find a setup script in /var/folders/85/85YEzSCiEiyDDPnVLLhW3k+++TI/-Tmp-/easy_install-AVecht/ManifestDestiny-0.2.tar.gz
This absolutely has to block Mozmill 1.5.2 and needs to be fixed as soon as possible.
Comment 1•14 years ago
|
||
Actually, it has nothing to do with Mozmill 1.5.2 and is a ManifestDestiny bug. The problem is this:
1. ManifestDestiny needs to be a single file: it is slated to land in build/manifestparser.py in m-c (see 618924)
2. ManifestDestiny needs to be installable as a package: mozmill imports manifestparser (though see bug 629575) and depends on it as a setuptools package.
3. evidently, unbeknownst to me, easy_install depends on that file being called setup.py :(
Satisfying these three design constraints is, at best, challenging.
Comment 2•14 years ago
|
||
It may be possible to do this by having a dummy setup.py script that calls ``manifestparser.py setup``, something like
import subprocess
import sys
here = os.path.dirname(os.path.abspath(__file__))
subprocess.call([sys.exectuable, os.path.join(here, 'manifestparser.py'), 'setup'] + sys.argv[1:]])
However, I can't test this until I can break pypi again
Assignee | ||
Comment 3•14 years ago
|
||
Attachment #507920 -
Flags: review?(jhammel)
Assignee | ||
Comment 4•14 years ago
|
||
Also we have made the decision to always depend on fixed versions of other packages. So '>=' went in per accident.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Assignee | ||
Updated•14 years ago
|
Summary: Package failure when installing ManifestDestiny → Package failure when installing ManifestDestiny (depend on fixed 0.1.5 version)
Updated•14 years ago
|
Attachment #507920 -
Flags: review?(jhammel) → review+
Assignee | ||
Comment 5•14 years ago
|
||
Landed as:
https://github.com/mozautomation/mozmill/commit/67605a0ba6b3dc8591a8c342516240a94e54445e
No more work can be done here. We have to push mozmill to pypi.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 6•14 years ago
|
||
Put a possible fix at http://hg.mozilla.org/automation/ManifestDestiny/rev/57cf81578fce ; Needs to be uploaded to pypi to test in the wild, however. So we're dependent on the rc2 version bump in bug 629107
Assignee | ||
Comment 7•14 years ago
|
||
Tested with the crowd extension and it works perfectly. Marking as verified fixed.
Status: RESOLVED → VERIFIED
Comment 8•14 years ago
|
||
Confirmed that easy_install ManifestDestiny and associated dependencies now work with the current trunk deployed at pypi as 0.2.2:
http://pypi.python.org/pypi/ManifestDestiny
You need to log in
before you can comment on or make changes to this bug.
Description
•