search

satnet-project / server

Repository with the source code for the server of the SATNet network.
Apache License 2.0
2 stars 1 forks source link

Setup errors (branch: development_3k) #22

Closed ajvazquez closed 9 years ago

ajvazquez commented 9 years ago

After runing:

 /satnet/server/scripts/server_setup -a

Output:

 [...]

 Copying files to the temporary directory...OK

 Stripping ELF binaries and libraries...OK

 Compressing man pages...OK

 Building file list...OK

 Building Debian package... FAILED!

 *** Failed to build the package

 Do you want to see the log file?  [y]: 

 dpkg-deb: error: parsing file '/var/tmp/tmp.mZjtAke0Rf/package/DEBIAN/control' near line 7 package 'node':
  error in Version string 'v0.12.1-1': version number does not start with digit
 /var/tmp/tmp.mZjtAke0Rf/dpkgbuild.log (END)

 Erasing temporary files...OK

 Writing backup package...OK
 OK

 Deleting temp dir...OK

 dpkg: error processing node_* (--install):
  cannot access archive: No such file or directory
 Errors were encountered while processing:
  node_*
 sudo: npm: command not found
 ./server-setup.sh: line 416: cd: /home/aj/satnet/server/website/static/scripts/: No such file or directory
 ./server-setup.sh: line 417: npm: command not found
 ./server-setup.sh: line 418: bower: command not found
 Press any key to continue
ajvazquez commented 9 years ago

Just got the same error with the master branch, so I may be missing some of the dependencies...

rtubio commented 9 years ago

@ajvazquez : this bug is related to the configuration of the NodeJS package. At the beginning of the project, we started using Debian Wheezy that does not include the NodeJS package within the default .deb packages of the official Debian repositories. Therefore, in order to install the NodeJS package we had to download it directly from the NodeJS development website and compile it "manually". As you might have notice, the compilation of that package is actually invoked by the installation script, but it requires of the user manually configuring it.

To keep using Debian Wheezy with that installer, the user has to manually change the version of the generated package within the menu of the NodeJS installer, from "v0.12.1-1" to "0.12.1-1".

Another option is to take a look at the next Debian version and find out whether it already includes the NodeJS package as part of the official distribution. In case it does, we can try to migrate the script and the default supported Debian version from Wheezy to the Testing release, which is already mature enough (I am using it in two desktops right now and it should become the stable official release soon).

Let me know what you think.

ajvazquez commented 9 years ago

Thank you! That worked, thanks for all the information.

Later I got another error "No such directory" related to line 386 on the same script. That was solved just by creating the folder $webservices_dir/website/static/scripts/ manually and re-running the script.

(Edited: moved second part to new issue)

rtubio commented 9 years ago

@ajvazquez : could we separate this new problem in a new issue? This way, we can close this one and open a new issue (better organization)... thanks!

rtubio commented 9 years ago

@ajvazquez : concerning this issue, I have just checked in one of the computers that I have at home that NodeJS and NPM are now part of the official repositories of Debian for the testing release (Jessy). I have already realized that the AngularJS interface has been moved to a separate repository, therefore this issue should never apply again.

The correct answer for this bug is to delete the installation of the AngularJS dependencies (Node, NPM and Bower packages), since now that is all handled from within the "satnet-ng" repository and should never appear again as part of the server installation.

ajvazquez commented 9 years ago

I think that's a good idea. I'll move the second part of the message into a new issue.

Thank you for the answer and for the info.