Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distfile incomplete ("ImportError: No module named dispersy.util") #1075

Closed
Rhialto opened this issue Dec 24, 2014 · 1 comment
Closed

Distfile incomplete ("ImportError: No module named dispersy.util") #1075

Rhialto opened this issue Dec 24, 2014 · 1 comment

Comments

@Rhialto
Copy link

Rhialto commented Dec 24, 2014

I downloaded the distfile https://github.com/Tribler/tribler/archive/v6.4.0.zip with the aim of creating a pkgsrc package for it. However, it doesn't seem to contain the git submodules.
Of course, for packaging purposes one wants to work only with stable releases and avoid having to rely on git checkouts, which are by their nature unstable.

I'm also missing an installation procedure. It is unclear which files need to be packaged to create a runnable package.

Furthermore, the list of dependencies, as given in Tribler/readme.md, seems incomplete. Leaving aside the optional ones, so far I have had to add at least py-twisted as a prerequisite.

Note that this is a different issue than #1056 despite the similar initial symptom.

@whirm
Copy link

whirm commented Dec 25, 2014

These are actually 3 issues:

  1. Oh well, Seems that GH doesn't put the submodules in the zip file. We will have to manually upload them for each release. (Follow issue: Github's .zip archives don't contain the repo's submodules #1077)

  2. About packaging info: Yeah, we should create a setup.py that works everywhere. Right now there are separate scripts for win/mac/linux. You could take a look at debian/ in the meanwhile to see how it's done there. (Follow issue README.md Doesn't contain instructions on how to package Tribler. #1078)

  3. About the deps: They should be up to date on devel's README.md take a look there, that will get merged back to next on the next release cycle. You can also look at debian/control

Any more info you need, just comment on one of the issues or create a new one.

Have in mind you won't get any replies until after the holidays.

Closing this issue as we should follow up in #1077 and #1078.

Thanks for the report(s)!

@whirm whirm closed this as completed Dec 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants