-
Notifications
You must be signed in to change notification settings - Fork 14
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
A different dulwich error using Fedora 23 #75
Comments
It seems like your gitconfig lacks a user/name. Try |
This is due to a missing git username. Reopen if that doesn't fix it. |
I'm getting this stack trace
when running any one of several variants of this script:
It's working up through the openshift deployment. As per #75 (comment) I've played around with how I quote user.name and user.email but it seems not to matter. |
I'm not sure I can re-open this myself: |
That appears to be a dulwich bug - it's not resulting from things ofcourse passes in, but rather choking on decoding the sha (inside plumbing). |
pip freeze output, as requested via IRC
|
dulwich isn't in there - is it living outside your virtualenv or something? |
Not sure when the script bombs out of the venv, but making sure I'm in the venv and trying the ofcourse openshift step again interactively I get what looks like the same trace, but with this pip freeze:
|
Confirmed that it was just that the subshell from my script that was in the venv and that therefor left the venv as the subshell exited on finishing the script. So, that pip freeze is representative of what is in the venv |
issuing
from within the venv takes dulwich from 0.10.0 to 0.14.1 which moves us past the error above, but then generates
That can then be ameliorated by making the line in question:
Allows things to move a bit further, before running into this error:
and that's as far as I've gotten. It looks like they've been working on this in dulwich, see this latest commit: Fix python3 compatibility But I think the most recent release (from early July) does not yet include the python3 fix |
More from our IRC conversation, with regard to forcing an even more recent version of Dulwich with python3 fixes (see above), pending its release:
|
Great, that looks like the best solution for now. Once a new release is out, I'll pin the requirements.txt to the newer version for Python 3 installations. |
OK, this saw me through last year. That said, looks like we should put this to bed one way or another now. With the new year starting and some changes in my own environment, I'm taking a look at this again. On the one hand, so far as I know, no one is using ofcourse this semester so we have some leisure to spend time looking at this instead of OMG PLEASE JUST MAKE IT WORK. On the other hand, pressures off and easy to forget in light of other priorities. |
I've generated a 64-bit Fedora 23 workstation virtual machine to try (among other reasons) to get closer to what other ofCourse developers may be using in their own builds.
I end up with this traceback:
To better document and make consistent what I'm doing, I made the attached script to run through the whole process of generating a test course, and captured a run of it in the second attached file using 'script'.
script.txt
output.txt
The text was updated successfully, but these errors were encountered: