Upgrading to v.0.4.23.1 on linux [SOLVED]

[xeroc]

-- Now I've learned another new thing: computer processes can get hangovers --

lol .. yhea .. they shouldn't but with compile processes that use several threads in parallel and might either take along time or simply get stuck .. all the parent threads will also get stuck .. shouldn't be the case though ..

Anyway .. glad to see your issues fix now ..

[mira]

I haven't seen it today, so perhaps you're right about the hangover. 

-- Now I've learned another new thing: computer processes can get hangovers --

[xeroc]

neither do I...!?

Oh .. so then ..

do you still get all those grep messages after a reboot .. i dont see them here when running the client ..

maybe you can figure out to which mother process they belong .. there should be a comman like "pstree" or so that can show the process tree

[mira]

neither do I...!?

[xeroc]

Hmmm .. odd ... not sure if its bitshare client related .. maybe some hangover of the compile process?
Cannot confirm as i dont have any windoes machines :/

[mira]

in the task manager

[xeroc]

grep is nothing more than search for a substring in a file/text ... where are you seening them?

[mira]

So I did have 23.1 installed!

I had followed those instructions for installing the GUI, and was running the .exe in qt_wallet folder, which is still the semi-functional v.22.

v23.1 is in the qt-wallet/bin folder... right where it had been when I originally installed v.22   

We currently don't have a 'simple' instruction to upgrade an existing source tree to the most recent version ..
but it's not too complicated:

Those instructions were actually so simple, and like a chinese puzzle, not too complicated only after learning the solution.

One last question:  Can you tell me what the grep ### process is that runs on and off when bitsharex is running?  It's bothering me not knowing what that is.

Thank you again for your help.

[xeroc]

The bad news is after all of that my client still says v.22 and is stuck syncing at the same block.

Can you go to the console and type "get_info" .. is it saying v0.22 there too?

which binary are you running? are you running the compile file in bitsharesx/programs/client/
or are you running some older system-install app?

the GUI requires some more extra steps

Should I have deleted something in my .bitsharesx folder?  might it be messing up when i'm installing the gui?

no need to delete anything from .bitsharex

BUT if you are using the GUI you need to do some more work to not only compile the client's core but also the user interface.
you may want to read trough this paragraph:
http://wiki.bitshares.org/index.php/Developer/Build#Configuration_and_Compilation_.28GUI.29

The upside for me is that through this process of trial and (mostly) error I've learned much that I didn't even know I wanted to know... but I really just want to learn how to upgrade this software properly, and it's eluding me.  NOTHING could compel me to reinstall windows OS again, so I have to learn how to do this!

We currently don't have a 'simple' instruction to upgrade an existing source tree to the most recent version ..
but it's not too complicated:

[mira]

You ROCK xeroc!  So helpful.

The bad news is after all of that my client still says v.22 and is stuck syncing at the same block.

Should I have deleted something in my .bitsharesx folder?  might it be messing up when i'm installing the gui?

The upside for me is that through this process of trial and (mostly) error I've learned much that I didn't even know I wanted to know... but I really just want to learn how to upgrade this software properly, and it's eluding me.  NOTHING could compel me to reinstall windows OS again, so I have to learn how to do this!

[xeroc]

no worries!

I already tried that and am in the midst of "make"

seems to be going smoothly...

Let me make you aware of a bug in the current version:
https://bitsharestalk.org/index.php?topic=10983.0

If I had to guess I'd say the next client upgrade will happen this week ..
compiling the current source still makes sense ass an upgrade of the source and recompile will finish alot faster as only the changed files are recompiled

[mira]

no worries!

I already tried that and am in the midst of "make"

seems to be going smoothly...

[xeroc]

shit, my fault

before running "cmake" you need to run

Code: [Select]

git submodule init ## once
git submodule update ## everytime you build a new version!

the reason for this is that the repository contains (for organizational reasons) .. sub repositories .. and you need to tell git to also download those ..

[mira]

I did this: 

git clone https://github.com/dacsunlimited/bitsharesx cd bitsharesx
git pull
git checkout v0.4.23.1
cmake .

it outputs:

 cmake .
-- The C compiler identification is GNU 4.8.2
-- The CXX compiler identification is GNU 4.8.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at CMakeLists.txt:29 (include):
  include could not find load file:

    GetGitRevisionDescription


CMake Error at CMakeLists.txt:30 (get_git_head_revision):
  Unknown CMake command "get_git_head_revision".


-- Configuring incomplete, errors occurred!
See also "/home/****/bitsharesx/CMakeFiles/CMakeOutput.log".

make 

and it outputs:

make: *** No targets specified and no makefile found.  Stop.


Don't I need to init and update before the cmake/make?

[xeroc]

okay.  so I started by deleting bitsharex folder.  Then tried the instructions for linux users on the dacsumlimited site that read:  "For Linux users, remember to checkout the tag v0.4.23.1 first"

When I enter git checkout v0.4.23.1, the message is:

"fatal: Not a git repository (or any parent up to mount point /home/****)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set)."

that error message tells you that there is no git repo downloaded that can be checked out from .. you need to INITIALLY download the repo as a whole

Code: [Select]

git clone https://github.com/dacsunlimited/bitsharesx.git
This includes all changes ever made.. and all Tags ever set to the source code

AFTER the cloning .. you can checkout a particular TAG (read:version)