mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #645] Upgrade to 1.2. rc1 fails via pip with django-versionfield errors #602
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#602
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @piwats on GitHub (Dec 7, 2014).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/645
As mentioned above:
with /root/.pip/pip.log
The use of --allow-external django-versionfield results in the same error.
So the question is how to upgrade to 1.2.0-rc1...
-Paul
@tonioo commented on GitHub (Dec 8, 2014):
Hi,
try to install django-versionfield manually:
@ghost commented on GitHub (Dec 8, 2014):
I got the same error.
I tried manually, but it is still not working for me.
@tonioo commented on GitHub (Dec 8, 2014):
Strange...
@csmk Can you paste the command output please?
@ghost commented on GitHub (Dec 8, 2014):
@tonioo commented on GitHub (Dec 8, 2014):
It looks like the manual installation worked. Now, can you try the following command:
@ghost commented on GitHub (Dec 8, 2014):
It's working now!
Thank you! ;)
@piwats commented on GitHub (Dec 8, 2014):
Same here - the manual install of django-versionfield and the later command helped.
-Paul
@piwats commented on GitHub (Dec 8, 2014):
Although the installation seemed to be working, now I'm getting this error when trying to access modoboa:
with pip list:
@piwats commented on GitHub (Dec 8, 2014):
Also, no bootstrap files are found in the sitestatic dir after collectstatic.
@tonioo commented on GitHub (Dec 8, 2014):
I don't understand the ImportError yet...
About static files, I forgot to mention into the documentation that it is necessary to modify the
STATICFILES_DIRSvariable (settings.py) by adding an extra path. Something like:In your case, the appropriate path seems to be
/usr/lib64/python2.7/site-packages/modoboa/bower_components.@piwats commented on GitHub (Dec 8, 2014):
It seems django versionfields wont install itself in the site-package directory. Because it is now gone from my pip list.... and I don't know why.
Update: this is the output from the versionfield installation process:
Because I run this command in the /root folder, there might have been some access problems since the link file in the site-packages folder is linking to the /root/src/..... folder.
Reinstalling django versionfield ina accessible folder I now get this error:
@tonioo commented on GitHub (Dec 8, 2014):
It seems the
--upgradeoption mentioned in the documentation (when running pip to install the new version of Modoboa) is a bad idea. I've fixed the documentation. Can you try to install this dependency once again? I don't really understand this behaviour...@piwats commented on GitHub (Dec 8, 2014):
I've got it running:
pip install --allow-external django-versionfield modoboa==1.2.0-rc1diff showed me, that the complete block before top_notifications was missing
in the 1.1.7 settings.py this block was missing
@tonioo commented on GitHub (Dec 8, 2014):
Indeed, the documentation is not clear enough about this part. I think the best would be to tell people to run the deploy command even for upgrades.
I'll update the documentation.