GLOBALEAKS
-
|
Describe the bug Expected behavior |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
|
Dear @elbill The scenario described is not supported by the application because the software do not support any downgrade. Let me clarify: |
Beta Was this translation helpful? Give feedback.
-
|
I'm not using a new database with an old version. Trying to create an old version to feed it the old database. In my scenario thta I have 4.9.9 db, how can I create a system on another vm to be able to access it? In a few words how can I create a 4.9.9 GL system today? |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to make a functional system 4.9.9 by installing a 4.10.7 and then using apt-get install globaleaks=4.9.9 |
Beta Was this translation helpful? Give feedback.
-
|
The current install script wont work for this use case. I will work editing it in order to add a parameter to specify a software version. |
Beta Was this translation helpful? Give feedback.
-
|
@elbill: I've modified the installation script does now accept a parameter -v where you can indicate a software version you can use it like: |
Beta Was this translation helpful? Give feedback.
-
|
Thats great. Thanks! |
Beta Was this translation helpful? Give feedback.
Dear @elbill
The scenario described is not supported by the application because the software do not support any downgrade.
Let me clarify:
When you update from one version to a newer version the database is updated and would typically not work anymore with a previous release of the software. If you do so you will incurr in similar issues like the one that you are running into.
If you really need to downgrade, you need the original directory /var/globaleaks archived before updating and corresponding to the same database format of the older globaleaks version.
To restore a previous version, restore a copy of your old data in the position /var/globaleaks and install the corresponding version.