error building

[Jose Blanco]

Getting this error when building 6.3.  It was working fine a week ago

[ERROR] Failed to execute goal on project xmlui-mirage2: Could not resolve dependencies for project org.dspace.modules:xmlui-mirage2:war:6.3: Failed to collect dependencies at rubygems:compass:gem:1.0.1 -> rubygems:sass:gem:[3.3.13,3.5): No versions available for rubygems:sass:gem:[3.3.13,3.5) within specified range -> [Help 1]

-Jose

[Sean Kalynuk]

The torquebox.org domain has expired.

 

See old discussion: https://groups.google.com/g/dspace-tech/c/RPL_qoTGvMI

 

The workaround is to install the prerequisite software for building Mirage 2:

 

https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#installation

 

I’m currently setting up the workaround myself since I ran into this yesterday and can’t wait for torquebox.org to return. Will be more stable (and faster!) for builds in the long run too.

 

--

Sean

 

From: dspac...@googlegroups.com <dspac...@googlegroups.com> on behalf of Jose Blanco <bla...@umich.edu>
Date: Tuesday, May 3, 2022 at 1:47 PM
To: DSpace Technical Support <dspac...@googlegroups.com>
Subject: [dspace-tech] error building

Caution: This message was sent from outside the University of Manitoba.

 

Getting this error when building 6.3.  It was working fine a week ago

 

[ERROR] Failed to execute goal on project xmlui-mirage2: Could not resolve dependencies for project org.dspace.modules:xmlui-mirage2:war:6.3: Failed to collect dependencies at rubygems:compass:gem:1.0.1 -> rubygems:sass:gem:[3.3.13,3.5): No versions available for rubygems:sass:gem:[3.3.13,3.5) within specified range -> [Help 1]

-Jose

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
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/CAK%3DKc-s6a-G-N_1sQGNmBc8E%3DVR82c%3Dt%2BZV2%3DUfC-Wu5b-6iSw%40mail.gmail.com.

[Jose Blanco]

Sean, I'm doing the install and it takes a while and now I'm getting :

nvm: install v12.22.12 failed!

is there any chance we will be able to build without having to do this?  

-Jose

[Sean Kalynuk]

Hi Jose,

 

Sorry, I don’t know about the status of torquebox.org, but since there have been issues with that domain before, I’m sticking with the locally installed Mirage 2 prerequisites now since I managed to get a full compile.

 

When you installed nvm, it would have modified your account’s login scripts. In my case, it modified my .bashrc file. I logged out and back in again to make sure I had the right environment settings before running “nvm install 12”.

 

--

Sean

[Jose Blanco]

Sean,

Sorry to bother you, I just tried again and it fails like this:

if [ ! -r node -o ! -L node ]; then \

  ln -fs out/Release/node node; fi

ln: failed to create symbolic link 'node': Operation not supported

Makefile:104: recipe for target 'node' failed

make: *** [node] Error 1

nvm: install v12.22.12 failed!

Why?

-Jose

[Sean Kalynuk]

Not sure. I installed nvm locally to my account with:

 

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

 

Logged out and back in and then ran:

 

nvm install 12

nvm alias default 12

 

In my environment, this gets added to my .bashrc:

 

export NVM_DIR="$HOME/.nvm"

[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm

[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

[Jose Blanco]

Sean,  You know the way I work here, I log in as myself then I become the dspace user.  So I just tried doing this as myself and it worked.  I was trying to do the installation as a dspace user.

When I build dspace normally, I am the dspace user.  I wonder if I can do all these installations as myself and then build dspace as a dspace user. Do you think that will work?

Thank you!

-Jose

[Sean Kalynuk]

In our environment, I build using my personal account, then run any ant commands as the dspace user to do installs/updates. I just make sure that the dspace account has read-access to the build targets in my account’s directory.

[Jose Blanco]

Now, I'm getting this error:

[ERROR] org.codehaus.plexus.archiver.ArchiverException: Failed setting file attributes with java7+: .../dspace/dspace/modules/xmlui-mirage2/target/mirage2-source-extracted/bower.json: Operation not permitted

I have installed the code required.  I could not install ruby as my own user, so I had a sys admin install it as root.  Does this ring a bell?

This is from running:

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

Very grateful for your help!!!

-Jose

[Jose Blanco]

Sean, 

We have a few different things going on over here. I wonder if when you did all those installations, did you do it as the same user that builds dspace?

Because of permissions and accounts, I  could not do that.

Thank you!

-Jose

[Sean Kalynuk]

I build everything as the same user and have most components installed locally to my account.

 

Here are the versions I used to set up the environment and compile (on RHEL 7):

 

openjdk 1.8.0_332 (global install)

mvn 3.3.9 (global install)

ant 1.9.4 (global install)

nvm 0.39.1 (local install)

node v12.22.12 (local install using nvm)

npm 6.14.16 (local install using nvm)

bower 1.8.14 (local install using local npm)

grunt 1.5.2 (local install using local npm)

grunt-cli v1.4.3 (local install using local npm)

rvm 1.29.12 (local install)

ruby 2.2.10p489 (2018-03-28 revision 63023) [x86_64-linux] (local install using local rvm)

gem 3.0.9 (local install along with local ruby)

sass 3.3.14 (local install using local gem)

ffi 1.12.2 (had to install this version before compass to be compatible with Ruby 2.2)

compass 1.0.1 (local install using local gem)

 

I do have root access to the host (via sudo) and did require that during the ruby install so that some required CentOS/RHEL packages could be installed.

[Alan Orth]

Dear all,

I am working to provide a solution to build Mirage 2 without Ruby for DSpace 6.4. It relies only on Node.js and npm, removing the dependency on Ruby and bower, which solves several issues I see people having in this thread. If you are willing and able to test, we would appreciate your feedback:

- Pull request: https://github.com/DSpace/DSpace/pull/8292

- Patch: https://patch-diff.githubusercontent.com/raw/DSpace/DSpace/pull/8292.patch

This applies cleanly on top of the current dspace-6_x branch. Once the patch is applied you can build like this:

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

We would especially appreciate people who have custom Mirage 2 modifications to provide feedback.

Thank you,

To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/YQBPR0101MB54048744D4D26658F47051DDE8C39%40YQBPR0101MB5404.CANPRD01.PROD.OUTLOOK.COM.

--

Alan Orth
alan...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch