Build failure for installing Mirage 2 in Dspace...Cannot run program "npm"

[Yerodin P]

Good Day all,

Before I post for help with my problem, here are the system specifics on which I am running DSpace v6.3:

- Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz, 2 cores, 4GB RAM

- Ubuntu Server 18.04.2 LTS

- PostgreSQL v10.10

- OpenSSH_7.6

- Tomcat7 in one instance and Tomcat8 in another. 

- javac 1.8.0_242

- openjdk version "1.8.0_242"

OpenJDK Runtime Environment (build 1.8.0_242-8u242-b08-0ubuntu3~18.04-b08)

OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)

- Apache Maven 3.6.0

Maven home: /usr/share/maven

Java version: 1.8.0_242, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre

Default locale: en_US, platform encoding: UTF-8

OS name: "linux", version: "4.15.0-76-generic", arch: "amd64", family: "unix"

- Git version 2.17.1

- $ rvm requirements

Checking requirements for ubuntu.

Requirements installation successful.

- Compass successfully installed

- Ruby-2.6.3 installed.

- home/useraccount/.nvm/versions/node/v6.5.0/lib

├── bo...@1.8.8

├── gr...@1.0.4

├── grun...@1.3.2

Please note:

The standard Mirage XMLUI theme works fine for me. 

I have been able as a DSpace Admin, to do such things as batch upload of files and execute search statistics.

MY DSPACE PROBLEM

I was able to successfully:

- load the pre-requisites for Mirage2

- edit [dspace-source]/dspace/config/xmlui.xconf  to uncomment the regular Mirage theme and add:

<theme name="Mirage 2" regex=".*" path="Mirage2/" />

- make adjustments to the file [dspace-source]/dspace-6.3-release/dspace/modules/xmlui-mirage2//pom.xml

where I changed the version of the dependencies to reflect what was actually loaded.

However, when I eventually ran:

$ mvn -Dmirage2.on=true -Dmirage2.deps.included=false clean package

Even though the directory

/build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/  

..does exist, I got the following error message and am temporarily stuck at this part of the Mirage2 installation:

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary for DSpace Parent Project 6.3:

[INFO]

[INFO] DSpace Parent Project .............................. SUCCESS [ 29.677 s]

[INFO] DSpace Addon Modules ............................... SUCCESS [  0.019 s]

[INFO] DSpace Kernel :: Additions and Local Customizations  SUCCESS [01:42 min]

[INFO] DSpace XML-UI Mirage2 Theme :: Local Customisations  FAILURE [ 49.864 s]

[INFO] DSpace XML-UI (Manakin) :: Local Customizations .... SKIPPED

[INFO] DSpace JSP-UI :: Local Customizations .............. SKIPPED

[INFO] DSpace RDF :: Local Customizations ................. SKIPPED

[INFO] DSpace REST :: Local Customizations ................ SKIPPED

[INFO] DSpace SWORD :: Local Customizations ............... SKIPPED

[INFO] DSpace SWORD v2 :: Local Customizations ............ SKIPPED

[INFO] DSpace SOLR :: Local Customizations ................ SKIPPED

[INFO] DSpace OAI-PMH :: Local Customizations ............. SKIPPED

[INFO] DSpace Assembly and Configuration .................. SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time:  03:02 min

[INFO] Finished at: 2020-01-30T16:05:17-04:00

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal com.soebes.maven.plugins:iterator-maven-plugin:0.3:iterator (default) on project xmlui-mirage2: Command execution failed.: Cannot run program "npm" (in directory "/build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2"): error=2, No such file or directory -> [Help 1]

Your suggestions on moving forward are welcome.

Yerodin P

DSpace newbie.

[Paul Münch]

Hello,

during Node installation there is a hint:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"

Use this in a script before the maven run. Or add it to your environment in a different way.

I hope this helps and kind regards,

Paul Münch

Am 31.01.20 um 21:29 schrieb Yerodin P:

--
All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/feb2a656-28c6-4753-bc9f-0338ab7f7c73%40googlegroups.com.

[Yerodin P]

Thank you for the hint Paul,
Forgive me if you get this twice as I did a "reply all" from my Gmail account.

I will try just the dspac...@googlegroups.com in my next post.

Anyway......

Close inspection indicates that your counsel is part of the steps described here:

https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-xmlui-mirage2/readme.md#compass  

.... for loading Mirage2 prerequisites.

I did encounter this suggestion after running the command:

$ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.31.7/install.sh | bash 

=> Close and reopen your terminal to start using nvm or run the following to use it now:
$ export NVM_DIR="/home/yerodinp/.nvm"
$ [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  

Hence, I am interpreting your hint to mean I should look to see if I missed any important steps, or didn't read and understand the provided instructions properly.

According to the DSpace literature, once Mirage2 prerequisites are successfully loaded, the build and implementation of Mirage2 should be easy peasy.

Will report my findings regardless of outcome and post solution if I find out what I was doing wrong.

Yerodin P

DSpace newbie.

You received this message because you are subscribed to a topic in the Google Groups "DSpace Technical Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-tech/hiVC3XU09U4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/b3ed16dc-4a21-9fe3-d7f6-4ce5a3b51b75%40staff.uni-marburg.de.

[Yerodin P]

Good day all,

Okay,

Can those of you running the Mirage2 responsive theme assist with the answer to this question?

In-spite of the following warnings:

1. Bower

$ npm install -g bower
npm WARN deprecated bo...@1.8.8: We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel.


2. Ruby SASS

$ gem install sass -v 3.3.14
Ruby Sass Has Reached End-of-Life
Ruby Sass should no longer be used, and will no longer be receiving any updates. See the Sass blog, and consider switching to the sassc gem

.....were those of you running DSpace's Mirage2 theme, able to successfully implement the theme in-spite of these warnings?

Yerodin P
DSpace newbie.

[Ndong, Maguette]

Hello Yerodin,

 

Try to install JRuby through rvm (If I remember it’s rvm install jruby)

Be sure that rvm is using ruby as current and default (check with rvm list and rvm use default ruby-xx.xx)

And in your “dspace-src/modules/xmlui-mirage2/pom.xml”, add this <jruby.version>9.2.6.0</jruby.version> under your npm version

 

Hope it will work for you! 😊

 

Cheers,

 

 

 

Maguette Thioro NDONG

Technical Advisor
Mail: PO Box 15115  |  Dakar Fann

Address: Fann Résidence Rue Saint John Perse x F  |  Dakar Senegal

Tel: +221 33 869 11 51  |  Mobile: +221 77 096 60 54

 

stay connected: @DigitalSQR | digitalsquare.org

   

 

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CACtoqqBrA1fX0AegJzS2%3DoRwRpuJ5_k9EafOLvEEHf75%2BM%2BJhw%40mail.gmail.com.

[Yerodin P]

Good day all,

Thanks for your suggestion Maguette,

I did try installing Jruby, and you were correct regarding the command to do so, it is:

rvm install jruby

However, that wasn't successful yielding ... 

Searching for binary rubies, this might take some time.
No binary rubies available for: ubuntu/18.04/x86_64/jruby-9.2.6.0.
Continuing with compilation. Please read 'rvm help mount' to get more information on binary rubies.

Checking requirements for ubuntu.
Requirements installation successful.

$JAVA_HOME was empty, setting up JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64, if it fails try setting JAVA_HOME to something sane and try again.
Cloning from https://github.com/jruby/jruby.git, this may take a while depending on your connection.
Error running 'command git clone https://github.com/jruby/jruby.git /usr/share/rvm/repos/jruby',
please read /home/yerodinp/.rvm/log/1580930136_jruby-9.2.6.0/git.clone.git.log
Cloning from https://github.com/jruby/jruby.git, this may take a while depending on your connection.
HEAD is now at ae9a21c2ac Add tags for new failing specs
fatal: unable to access 'https://github.com/jruby/jruby.git/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/jruby/jruby.git/': Could not resolve host: github.com
There has been an error while checking out branch master.
Halting the installation.
Copying from repo to src path...
jruby-9.2.6.0 - #mvnw.....................................................................................................
Error running '/usr/share/rvm/src/jruby-9.2.6.0/mvnw',
please read /home/yerodinp/.rvm/log/1580930136_jruby-9.2.6.0/mvnw.log

So I moved on and I looked at the INFO lines shown at the beginning of the build process. 

Then, compared them to where the build process failed after I typed the mvn command:

Two things jumped at me.

1. I obviously changed something for the worse, because the Mirage2 build is failing earlier than when I first posted to the DSpace technical support group.
2. The most recent attempt

yerodinp@ubuntu3_wk:/build/dspace-6.3-release$ mvn package -Dmirage2.on=true -Dmirage2.deps.included=false

yields:

[INFO] DSpace Kernel :: Additions and Local Customizations                [jar]

....and

[INFO] DSpace Kernel :: Additions and Local Customizations  FAILURE [ 14.901 s]

....suggesting that my Mirage2 build fails with step 3/13 where it attempts to do Building DSpace Kernel :: Additions and Local Customizations 6.3

Within this last build attempt, the 3/13 section of the build stated the following:

Downloading from maven-snapshots: http://oss.sonatype.org/content/repositories/snapshots/org/dspace/dspace-api-lang/maven-metadata.xml
Downloading from central: https://repo.maven.apache.org/maven2/org/dspace/dspace-api-lang/maven-metadata.xml
Downloaded from central: https://repo.maven.apache.org/maven2/org/dspace/dspace-api-lang/maven-metadata.xml (1.4 kB at 672 B/s)
Downloaded from maven-snapshots: http://oss.sonatype.org/content/repositories/snapshots/org/dspace/dspace-api-lang/maven-metadata.xml (366 B at 83 B/s)

[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-java) @ additions ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ additions ---
[INFO]
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ additions ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ additions ---

With the most telling error message stating:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project add


Guys and Ladies, I have proven to myself that I can revert back to the ordinary Mirage theme without losing access to any repository data.
However, I am thinking that maybe the script that the Mirage2 build attempts to follow,  might need some tweaking because I was able to successfully load all the Mirage2 pre-requisites

It's got to be something simple that I am either missing or not doing right.

Example:
In Windows, some programs won't successfully open a file if the path to the file is too long.

Yerodin P

DSpace newbie.

[Paul Münch]

Hello,

> .....were those of you running DSpace's Mirage2 theme, able to successfully implement the theme in-spite > of these warnings?

Yes. These are only warnings.

> Hence, I am interpreting your hint to mean I should look to see if I missed any important steps, or didn't
> read and understand the provided instructions properly.

It is important for the Mirage2-installation that your environment can solve the command 'npm'. When you have installed the 'nvm', you have to add the path to the script '/home/systemuser/.nvm/nvm.sh' to your environment. You can test it with open a terminal and run the command 'npm'.

At the Ruby topic: We do not use JRuby but the standard Debian ruby package. Also Sass and Compass we install via standard packages 'ruby-compass' and 'ruby-sass'. These are available on Ubuntu, too.

I hope this helps and kind regards,

Paul Münch

Am 04.02.20 um 15:53 schrieb Yerodin P:

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/CACtoqqBrA1fX0AegJzS2%3DoRwRpuJ5_k9EafOLvEEHf75%2BM%2BJhw%40mail.gmail.com.

[Yerodin P]

Good Day all,

I did some checks on my Mirage2 pre-requisites, and ran the following command:

sudo mvn -U clean package -Dmirage2.on=true -Dmirage2.deps.included=false

and received three messages which I have included below.

- The 1st one looks like a warning I can ignore if not accessing DSpace Mirage2 with IE6.

- The 2nd  looks like I might need to respond intelligently.

- The 3rd looks like it is probably connected to the 2nd.

I expect a bit of a learning curve, but a search of the DSpace tech Support forum yields nothing for "Exit value: 6".

I have doubts concerning  just adding mvn -fn to the build command, as I am worried what unexpectedly might not function later.

So i think I am close to solving my Mirage2 build issues, once I get over this " "Exit value: 6" issue.

Any advice from the Mirage2 scheme users is welcome, along with anybody who understands the pre-requisite software well enough to add insight.

--------->

Messages 1 and 2.

DEPRECATION WARNING on line 92 of /usr/share/compass/frameworks/compass/stylesheets/compass/css3/_deprecated-support.scss: #{} interpolation near operators will be simplified
in a future version of Sass. To preserve the current behavior, use quotes:

  unquote('"$ie6-"#{$legacy-support-for-ie6} "$ie7-"#{$legacy-support-for-ie7} "$ie8-"#{$legacy-support-for-ie8}')

You can use the sass-convert command to automatically fix most cases.

    error styles/main.scss (Line 16: File to import not found or unreadable: ../vendor/bootstrap-sass-official/assets/stylesheets/bootstrap.
Load paths:
  Compass::SpriteImporter
  /build/dspace-6.3-release/dspace/modules/xmlui-mirage2/target/themes/Mirage2/styles
  /usr/share/compass/frameworks/compass/stylesheets)
Compilation failed in 1 files.
Warning: ↑ Use --force to continue.

  --------->  

Message 3. 

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

[INFO] Total time:  01:24 min
[INFO] Finished at: 2020-02-11T15:32:47-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.soebes.maven.plugins:iterator-maven-plugin:0.3:iterator (default) on project xmlui-mirage2: Command execution failed.: Process exited with an error: 6 (Exit value: 6) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/78412133-a7ea-0ec7-8f6a-46a4efe03952%40staff.uni-marburg.de.