Quantcast

[Mayan EDMS: 1495] 2.1.7 update overwrite local.py file

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Mayan EDMS: 1495] 2.1.7 update overwrite local.py file

Victor Zele
Just a heads up for anyone updating to 2.1.7, the /usr/share/mayan-edms/mayan/settings/local.py file get reset to a new key so no documents or logins work after the update.

Steps to restore functioning system is to restore the local.py from a backup and re-run the "mayan-edms.py performupgrade"
and  "mayan-edms.py collectstatic --noinput"


CONFIDENTIALITY NOTICE: 

This transmission may contain information which is Vimo, Inc. (DBA Getinsured) confidential and/or legally privileged. The information is intended only for the use of the individual or entity named on this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify me by return e-mail and destroy all copies of the original message.

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Mayan EDMS: 1498] Re: 2.1.7 update overwrite local.py file

rosarior
Administrator
This was caused by a long standing but of pypa wheel (https://bitbucket.org/pypa/wheel/issues/99/cannot-exclude-directory)
Which includes files being told to explicitly exclude. 

The make file for producing releases has been updated to work around this (https://gitlab.com/mayan-edms/mayan-edms/commit/26f17b6ede3823163558f4c16983bdb6a5bccad6)

On Monday, February 6, 2017 at 4:24:38 PM UTC-4, Victor Zele wrote:
Just a heads up for anyone updating to 2.1.7, the /usr/share/mayan-edms/mayan/settings/local.py file get reset to a new key so no documents or logins work after the update.

Steps to restore functioning system is to restore the local.py from a backup and re-run the "mayan-edms.py performupgrade"
and  "mayan-edms.py collectstatic --noinput"

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Mayan EDMS: 1500] Re: 2.1.7 update overwrite local.py file

Victor Zele
Hi Roberto,

I ran the update to 2.1.10 today and the local.py was removed.  A new one does not get created like before, but needed to copy my backup local.py back after the update.


On Sunday, February 12, 2017 at 7:13:29 PM UTC-8, Roberto Rosario wrote:
This was caused by a long standing but of pypa wheel (<a href="https://bitbucket.org/pypa/wheel/issues/99/cannot-exclude-directory" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fbitbucket.org%2Fpypa%2Fwheel%2Fissues%2F99%2Fcannot-exclude-directory\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHhae0jrO3lpYdfsOeskL5ALZYNrw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fbitbucket.org%2Fpypa%2Fwheel%2Fissues%2F99%2Fcannot-exclude-directory\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHhae0jrO3lpYdfsOeskL5ALZYNrw&#39;;return true;">https://bitbucket.org/pypa/wheel/issues/99/cannot-exclude-directory)
Which includes files being told to explicitly exclude. 

The make file for producing releases has been updated to work around this (<a href="https://gitlab.com/mayan-edms/mayan-edms/commit/26f17b6ede3823163558f4c16983bdb6a5bccad6" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcommit%2F26f17b6ede3823163558f4c16983bdb6a5bccad6\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHGANVQgGHHpG8euma_0WIvsCzSxA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcommit%2F26f17b6ede3823163558f4c16983bdb6a5bccad6\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHGANVQgGHHpG8euma_0WIvsCzSxA&#39;;return true;">https://gitlab.com/mayan-edms/mayan-edms/commit/26f17b6ede3823163558f4c16983bdb6a5bccad6)

On Monday, February 6, 2017 at 4:24:38 PM UTC-4, Victor Zele wrote:
Just a heads up for anyone updating to 2.1.7, the /usr/share/mayan-edms/mayan/settings/local.py file get reset to a new key so no documents or logins work after the update.

Steps to restore functioning system is to restore the local.py from a backup and re-run the "mayan-edms.py performupgrade"
and  "mayan-edms.py collectstatic --noinput"


CONFIDENTIALITY NOTICE: 

This transmission may contain information which is Vimo, Inc. (DBA Getinsured) confidential and/or legally privileged. The information is intended only for the use of the individual or entity named on this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify me by return e-mail and destroy all copies of the original message.

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Mayan EDMS: 1501] Re: 2.1.7 update overwrite local.py file

rosarior
Administrator
Hi Victor,

I tried it and can verify it gets deleted. I tried an upgrade from 2.1.6 to 2.1.10 and it doesn't happens so it must be an artifact of the problem that included the local.py in the 2.1.7 release.
My guess is that since PIP deletes all files during an upgrade to avoid clashes with the new version's files, the local.py that was included in the package, gets deleted too. 
It is being recognized as a package file and not an user file.
PyPI the Python Package Index doesn't allow re-uploading releases, even if it is to fix issues like this (https://github.com/pypa/packaging-problems/issues/74). 
Support was added to the Makefile to do a test release using the test PyPI server (https://testpypi.python.org/pypi) -> (https://gitlab.com/mayan-edms/mayan-edms/commit/4469f020a6b7f8bd4e35963e9201709d0d083d29)
It is not a bulletproof solution but will add a new step to allow doing mock releases before doing the final release. As for 2.1.7, the only course of action now that 2.1.10 is out is to delete it from PyPI.

On Monday, February 13, 2017 at 1:28:23 PM UTC-4, Victor Zele wrote:
Hi Roberto,

I ran the update to 2.1.10 today and the local.py was removed.  A new one does not get created like before, but needed to copy my backup local.py back after the update.


On Sunday, February 12, 2017 at 7:13:29 PM UTC-8, Roberto Rosario wrote:
This was caused by a long standing but of pypa wheel (<a href="https://bitbucket.org/pypa/wheel/issues/99/cannot-exclude-directory" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fbitbucket.org%2Fpypa%2Fwheel%2Fissues%2F99%2Fcannot-exclude-directory\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHhae0jrO3lpYdfsOeskL5ALZYNrw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fbitbucket.org%2Fpypa%2Fwheel%2Fissues%2F99%2Fcannot-exclude-directory\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHhae0jrO3lpYdfsOeskL5ALZYNrw&#39;;return true;">https://bitbucket.org/pypa/wheel/issues/99/cannot-exclude-directory)
Which includes files being told to explicitly exclude. 

The make file for producing releases has been updated to work around this (<a href="https://gitlab.com/mayan-edms/mayan-edms/commit/26f17b6ede3823163558f4c16983bdb6a5bccad6" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcommit%2F26f17b6ede3823163558f4c16983bdb6a5bccad6\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHGANVQgGHHpG8euma_0WIvsCzSxA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitlab.com%2Fmayan-edms%2Fmayan-edms%2Fcommit%2F26f17b6ede3823163558f4c16983bdb6a5bccad6\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHGANVQgGHHpG8euma_0WIvsCzSxA&#39;;return true;">https://gitlab.com/mayan-edms/mayan-edms/commit/26f17b6ede3823163558f4c16983bdb6a5bccad6)

On Monday, February 6, 2017 at 4:24:38 PM UTC-4, Victor Zele wrote:
Just a heads up for anyone updating to 2.1.7, the /usr/share/mayan-edms/mayan/settings/local.py file get reset to a new key so no documents or logins work after the update.

Steps to restore functioning system is to restore the local.py from a backup and re-run the "mayan-edms.py performupgrade"
and  "mayan-edms.py collectstatic --noinput"

--

---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Loading...