Re: [dspace-tech] Re: Correct permissions prior to using Maven and Ant while installing Dspace 6.3

[Ashim Kapoor]

Dear Fru and Darryl,

If my memory serves me correctly, I do think these settings worked for me.

I could be mistaken though.

I will do an experiment and again use the settings which I was curious
about and let you know. You will have to give me some time though for
me to do this experiment.

Best,
Ashim


On Thu, 5 May 2022 at 09:12, darryl@usask.ca
 wrote:
>
> Ashim, those permissions look pretty restrictive.  Does the build and install 
> actually work for you?
>
> I know the install docs mention the "dspace" user, but it also states "you 
> must ensure the Tomcat owner also owns [dspace], OR you can create a new 
> 'dspace' user account, and ensure that Tomcat also runs as that account".  We 
> went with the former (because that was easier and more standard than changing 
> the account Tomcat runs as), and made sure the "tomcat" user and group owned 
> all the files.
>
> This is mostly from memory, but for the [dspace] directory I did something 
> like:
>
>  sudo mkdir [dspace]
>  sudo chown tomcat:tomcat [dspace]
>  sudo chmod 2775 [dspace]
>
> And for the [dspace-source] directory I did something like:
>
>  # Set the permissions
>  sudo chown -R tomcat:tomcat [dspace-source]
>  sudo chmod -R ug+rw [dspace-source]
>  # Build DSpace
>  sudo su - tomcat
>  cd [dspace-source]
>  $ Install
>  mvn package
>  cd dspace/target/dspace-installer
>  ant fresh_install
>
> I won't say that that's the only way, or even the correct way, but that 
> worked for us.
>
> - Darryl
>
> On Wednesday, May 4, 2022 at 4:02:46 PM UTC-6 fru9...@gmail.com wrote:
>>
>> Hello,
>>
>> Does setting these permissions allow you tu run ant ?
>>
>> Kind regards,
>>
>> On Wednesday, April 28, 2021 at 3:51:32 PM UTC+1 ashim@nipfp.org.in 
>> wrote:
>>>
>>> Dear Dspace Experts,
>>>
>>> I wish to know the correct permissions for the directories [dspace]
>>> and [dspace-source] prior to running Maven and Ant.
>>>
>>> I am using the definitions of [dspace] and [dspace-source] as on this page:
>>>
>>> https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace
>>>
>>> Here is what I have been doing till now:
>>>
>>> For Running Maven (as user dspace):
>>> I first make sure that the dspace user owns the [dspace-source] directory.
>>>
>>> sudo chmod 700 -R [dspace-source]
>>> ( Basically rwx for [dspace-source])
>>> mvn package
>>>
>>> For Running Ant as user dspace:
>>>
>>> sudo chmod 500 -R [dspace-source]
>>> ( Basically READ and EXECUTE permission for [dspace-source])
>>> sudo chmod 200 -R [dspace]
>>> ( Amounts to WRITE permission for [dspace])
>>> sudo chmod u+x -R [dspace]
>>> This is so that the installed files can be executed
>>> sudo chmod g+s -R [dspace]
>>> This is so that the newly created files in [dspace] should inherit the
>>> group ( which is the same as the dspace user). so that permissions are
>>> inherited.
>>> sudo chmod 700 -R [dspace-source]
>>>
>>> Then I do, as user dspace:-
>>> cd [dspace-source]/dspace/target/dspace-installer
>>> ant fresh_install
>>>
>>> Can someone here comment on my attempt ? Please share the best practice.
>>>
>>> Thank you,
>>> Ashim
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/93d3d862-38ff-4951-b66e-2d3e0d14c39dn%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAGEJAoFj78%2BT4-ZeNTvd457xM3DWtZs0%3DGiy1brnC4Bh6-0otw%40mail.gmail.com.

[dspace-tech] Re: Correct permissions prior to using Maven and Ant while installing Dspace 6.3

[darryl....@usask.ca]

Ashim, those permissions look pretty restrictive.  Does the build and 
install actually work for you?

I know the install docs mention the "dspace" user, but it also states "you 
must ensure the Tomcat owner also owns [dspace], OR you can create a new '
dspace' user account, and ensure that Tomcat also runs as that account".  
We went with the former (because that was easier and more standard than 
changing the account Tomcat runs as), and made sure the "tomcat" user and 
group owned all the files.

This is mostly from memory, but for the [dspace] directory I did something 
like:

 sudo mkdir [dspace]
 sudo chown tomcat:tomcat [dspace]
 sudo chmod 2775 [dspace]

And for the [dspace-source] directory I did something like:

 # Set the permissions
 sudo chown -R tomcat:tomcat [dspace-source]
 sudo chmod -R ug+rw [dspace-source]
 # Build DSpace
 sudo su - tomcat
 cd [dspace-source]
 $ Install
 mvn package
 cd dspace/target/dspace-installer
 ant fresh_install

I won't say that that's the only way, or even the correct way, but that 
worked for us.

- Darryl

On Wednesday, May 4, 2022 at 4:02:46 PM UTC-6 fru9...@gmail.com wrote:

> Hello, 
>
> Does setting these permissions allow you tu run ant ?
>
> Kind regards,
>
> On Wednesday, April 28, 2021 at 3:51:32 PM UTC+1 ashim@nipfp.org.in 
> wrote:
>
>> Dear Dspace Experts, 
>>
>> I wish to know the correct permissions for the directories [dspace] 
>> and [dspace-source] prior to running Maven and Ant. 
>>
>> I am using the definitions of [dspace] and [dspace-source] as on this 
>> page: 
>>
>> https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace 
>>
>> Here is what I have been doing till now: 
>>
>> For Running Maven (as user dspace): 
>> I first make sure that the dspace user owns the [dspace-source] 
>> directory. 
>>
>> sudo chmod 700 -R [dspace-source] 
>> ( Basically rwx for [dspace-source]) 
>> mvn package 
>>
>> For Running Ant as user dspace: 
>>
>> sudo chmod 500 -R [dspace-source] 
>> ( Basically READ and EXECUTE permission for [dspace-source]) 
>> sudo chmod 200 -R [dspace] 
>> ( Amounts to WRITE permission for [dspace]) 
>> sudo chmod u+x -R [dspace] 
>> This is so that the installed files can be executed 
>> sudo chmod g+s -R [dspace] 
>> This is so that the newly created files in [dspace] should inherit the 
>> group ( which is the same as the dspace user). so that permissions are 
>> inherited. 
>> sudo chmod 700 -R [dspace-source] 
>>
>> Then I do, as user dspace:- 
>> cd [dspace-source]/dspace/target/dspace-installer 
>> ant fresh_install 
>>
>> Can someone here comment on my attempt ? Please share the best practice. 
>>
>> Thank you, 
>> Ashim 
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/93d3d862-38ff-4951-b66e-2d3e0d14c39dn%40googlegroups.com.

[dspace-tech] Re: ant fresh_install fails

[darryl....@usask.ca]

On our servers, Tomcat runs as the "tomcat" user, so all our source files 
are owned by that user and group, as is the DSpace target group.  It's been 
a while since I did a fresh install, but I probably did the initial setup 
of our target directory something like this:

 sudo mkdir /dspace
 sudo chown tomcat:tomcat /dspace
 sudo chmod 2775 /dspace

Then I would have run the "ant fresh_install" as the "tomcat" user.

Your setup make be slightly different of course, but it looks to me like 
whatever user you are running "ant" as does not have permissions to 
actually write to your "/dspace" directory.  I'd start with looking at 
permissions.

- Darryl




On Wednesday, May 4, 2022 at 4:02:46 PM UTC-6 fru9...@gmail.com wrote:

> Hello, 
>
> I am following the steps to installing dspace but I run into an issue when 
> I run *ant fresh_install*
>
> Here's the output I get
>
> [image: ant_install.PNG]
>
> Please help
>
> Thanks
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/115632f7-46e2-4bd5-a154-3ab98a1d389cn%40googlegroups.com.

[dspace-tech] ant fresh_install fails

[Fru Emmanuel]

Hello, 

I am following the steps to installing dspace but I run into an issue when 
I run *ant fresh_install*

Here's the output I get

[image: ant_install.PNG]

Please help

Thanks

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/49102f32-dfd0-4464-a154-0cfa10bb98edn%40googlegroups.com.

[dspace-tech] Re: Correct permissions prior to using Maven and Ant while installing Dspace 6.3

[Fru Emmanuel]

Hello, 

Does setting these permissions allow you tu run ant ?

Kind regards,

On Wednesday, April 28, 2021 at 3:51:32 PM UTC+1 ashim@nipfp.org.in 
wrote:

> Dear Dspace Experts,
>
> I wish to know the correct permissions for the directories [dspace]
> and [dspace-source] prior to running Maven and Ant.
>
> I am using the definitions of [dspace] and [dspace-source] as on this page:
>
> https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace
>
> Here is what I have been doing till now:
>
> For Running Maven (as user dspace):
> I first make sure that the dspace user owns the [dspace-source] directory.
>
> sudo chmod 700 -R [dspace-source]
> ( Basically rwx for [dspace-source])
> mvn package
>
> For Running Ant as user dspace:
>
> sudo chmod 500 -R [dspace-source]
> ( Basically READ and EXECUTE permission for [dspace-source])
> sudo chmod 200 -R [dspace]
> ( Amounts to WRITE permission for [dspace])
> sudo chmod u+x -R [dspace]
> This is so that the installed files can be executed
> sudo chmod g+s -R [dspace]
> This is so that the newly created files in [dspace] should inherit the
> group ( which is the same as the dspace user). so that permissions are
> inherited.
> sudo chmod 700 -R [dspace-source]
>
> Then I do, as user dspace:-
> cd [dspace-source]/dspace/target/dspace-installer
> ant fresh_install
>
> Can someone here comment on my attempt ? Please share the best practice.
>
> Thank you,
> Ashim
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/5e473a69-be58-4c14-ad98-6316281cc969n%40googlegroups.com.

[dspace-tech] Re: DS7.x: Item page customization and custom themes

[darryl....@usask.ca]

Thanks Agustina.  I read those comments, and that was where I was headed 
next, but I thought I'd double check with folks here before I got started.  
Partly because of this statement "This part of the  code might be 
refactored in a subsequent release, so this is kind of a temporary 
solution.".  But it's reassuring to know others are using the same strategy.

I mean. if you had some code or tips to share, I wouldn't turn that 
down.  :)   I've done a bit of work with Vue but, like you, Angular is new 
to me.  I welcome any help I can get.

As for workflow, we started with a Git clone, then created a local branch 
from the 7.2 release, to keep our customizations separate.  My plan is to 
then merge the 7.3 release into my branch to keep it up to date.  By 
starting with a copy of the custom theme though, I'll need to manually move 
any 7.3 changes to "custom" into my theme, so I'm wondering if that that 
copy was a good decision, and whether I should have just made changes 
directly to "custom".  I too welcome any suggestions on the best way to 
manage things going forward.

Thanks again Agustina!

- Darryl

On Wednesday, May 4, 2022 at 6:12:03 AM UTC-6 Agustina Martinez wrote:

> Hi Darryl,
>
> We are currently at the same stage as you are regarding custom theming. I 
> have opted for now to take a copy of the custom theme and use it as the 
> basis for our institutional theme (to make updates a bit easier going 
> forward I've removed all of those customisations from the custom theme that 
> we do not use for now). But like you, do not know whether this is the best 
> approach. I found the documentation pages really good: 
> https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization and 
> in particular the comments at the end answer your question about 
> customising components such as the "untyped item". I have successfully done 
> that in our test instance and happy to share with you if you don't get it 
> working based on the info in the docs pages.
>
> It would be great if someone could comment on best ways forward for 
> customising in ways that make future upgrades simpler. I am really knew to 
> angular so just slowly finding our ways!
>
> Agustina
>
> On Tuesday, 3 May 2022 at 21:02:24 UTC+1 darryl@usask.ca wrote:
>
>>
>> How are people theming DSpace 7.x? Is it better to create a new theme 
>> from a copy of "custom" (and deal with integrating any future changes made 
>> to "custom" manually), or just create a local branch of the dspace-angular 
>> repo and modify the "custom" theme directly (and then pull in changes to 
>> "custom" via a merge request from the main branch)?
>>
>> Also, can anyone point me in the right direction to make changes to the 
>> simple item view? It seems the default for items in DSpace is "untyped 
>> item" (I haven't enabled any of the entity stuff).  I've modified 
>> src/app/item-page/simple/item-types/untyped-item/untyped-item.component.html 
>> to get the results I want, but it seems like a bad idea to modify the 
>> global code rather than something in my theme.
>>
>> The "custom" theme contains simple page templates for Publication items, 
>> -- src/themes/limestone/app/item-page/simple/item-types/publication -- but 
>> not untyped items.  Simply copying the "untyped-item" folder from the 
>> global code into that "item-types" folder didn't seem to work.  I assume 
>> there some additional changes required in a .ts file somewhere I also need 
>> to update, but I'm, not quite sure which ones.  Or do I need to copy the 
>> entire src/app/item-page directory tree into my theme?
>>
>> Unless there's some other (easier) way to add additional metadata fields 
>> to the simple display that I've not discovered??
>>
>> Thanks,
>>
>> - Darryl
>>
>>
>>
>> --
>> *Darryl Friesen, BSc*
>> Programmer/Analyst
>> *University of Saskatchewan*
>> *ICT / University Library*
>>
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/b0519090-eeaa-4f02-b27e-5964f6ba2ecdn%40googlegroups.com.

Re: [dspace-tech] error building

[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.

--
Sean

From: Jose Blanco 
Date: Wednesday, May 4, 2022 at 10:24 AM
To: Sean Kalynuk 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

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

On Wed, May 4, 2022 at 9:49 AM Jose Blanco 
mailto:blan...@umich.edu>> wrote:
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

On Tue, May 3, 2022 at 8:53 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
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.
--
Sean

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 5:45 PM
To: Sean Kalynuk mailto:sean.kaly...@umanitoba.ca>>
Cc: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

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

On Tue, May 3, 2022 at 5:55 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
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

--
Sean

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 2022 at 4:46 PM
To: Sean Kalynuk mailto:sean.kaly...@umanitoba.ca>>
Cc: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: Re: [dspace-tech] error building
Caution: This message was sent from outside the University of Manitoba.

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

On Tue, May 3, 2022 at 4:36 PM Sean Kalynuk 
mailto:sean.kaly...@umanitoba.ca>> wrote:
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

From: Jose Blanco mailto:blan...@umich.edu>>
Date: Tuesday, May 3, 

[dspace-tech] question about Mirage2

[Jose Blanco]

can you do these installations as userA

https://github.com/DSpace/DSpace/tree/dspace-6_x/dspace-xmlui-mirage2#prerequisites-for-osx--linux

and then build dspace as userB ?

Because of our setup, I have to do this, and I'm getting this error:

npm  -h  quick help on 

npm -ldisplay full usage info

npm helpsearch for help on 

npm help npm  involved overview


Specify configs in the ini-formatted file:

/dir_of_instance/userB/.npmrc

or on the command line via: npm  --key value

Config info can be viewed via: npm help config


npm@6.14.12 /usr/lib/node_modules/npm




[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: 1 (Exit value: 1) -> [Help 1]

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal com.soebes.maven.plugins:iterator-maven-plugin:0.3:iterator (default)
on project xmlui-mirage2: Command execution failed.

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-snrdU_m%2BuKSicQaXruHNhZi1qV7410QC_0AjHOd-yYHA%40mail.gmail.com.

Re: [dspace-tech] error building

[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

On Wed, May 4, 2022 at 9:49 AM Jose Blanco  wrote:

> 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
>
> On Tue, May 3, 2022 at 8:53 PM Sean Kalynuk 
> wrote:
>
>> 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.
>>
>> --
>>
>> Sean
>>
>>
>>
>> *From: *Jose Blanco 
>> *Date: *Tuesday, May 3, 2022 at 5:45 PM
>> *To: *Sean Kalynuk 
>> *Cc: *DSpace Technical Support 
>> *Subject: *Re: [dspace-tech] error building
>>
>> *Caution:* This message was sent from outside the University of Manitoba.
>>
>>
>>
>> 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
>>
>>
>>
>> On Tue, May 3, 2022 at 5:55 PM Sean Kalynuk 
>> wrote:
>>
>> 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
>>
>>
>>
>> --
>>
>> Sean
>>
>>
>>
>> *From: *Jose Blanco 
>> *Date: *Tuesday, May 3, 2022 at 4:46 PM
>> *To: *Sean Kalynuk 
>> *Cc: *DSpace Technical Support 
>> *Subject: *Re: [dspace-tech] error building
>>
>> *Caution:* This message was sent from outside the University of Manitoba.
>>
>>
>>
>> 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
>>
>>
>>
>> On Tue, May 3, 2022 at 4:36 PM Sean Kalynuk 
>> wrote:
>>
>> 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
>>
>>
>>
>> *From: *Jose Blanco 
>> *Date: *Tuesday, May 3, 2022 at 3:12 PM
>> *To: *Sean Kalynuk 
>> *Cc: *DSpace Technical Support 
>> *Subject: *Re: [dspace-tech] error building
>>
>> *Caution:* This message was sent from outside the University of Manitoba.
>>
>>
>>
>> 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
>>
>>
>>
>> On Tue, May 3, 2022 at 3:08 PM Sean Kalynuk 
>> wrote:
>>
>> 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: *dspace-tech@googlegroups.com  on
>> behalf of Jose Blanco 
>> *Date: *Tuesday, May 3, 20

[dspace-tech] Re: UnsupportedOperationException from community-filiator --remove in dspace 6.1

[Braxton Van Gundy]

Did you all ever find a solution to this? I'm hitting the exact same issue 
with Dspace 6.3 right now. 

On Tuesday, November 14, 2017 at 4:34:14 AM UTC-5 Bolette A. Jurik wrote:

> Hi all,
>
> I get a
> java.lang.UnsupportedOperationException
> when using the community-filiator --remove operation in my dspace 6.1 
> installation
>
> More specifically
> $ ./bin/dspace community-filiator --remove --parent 1902/1 --child 1902/11
> Exception: null
> java.lang.UnsupportedOperationException
> at java.util.AbstractList.remove(AbstractList.java:161)
> at java.util.AbstractList$Itr.remove(AbstractList.java:374)
> at java.util.AbstractCollection.remove(AbstractCollection.java:293)
> at 
> org.dspace.administer.CommunityFiliator.defiliate(CommunityFiliator.java:264)
> at 
> org.dspace.administer.CommunityFiliator.main(CommunityFiliator.java:164)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
>
> But it looks like the --set operation works
> $ ./bin/dspace community-filiator --set --parent 1902/17 --child 1902/1
>
> Filiation complete. Community: '0f4f6f9d-f9be-45e6-ad13-217b07ad17ad' is 
> parent of community: '1ed059f9-fd5b-4921-a5fe-65dc9ba95265'
>
> Has anyone else experienced this, and/or do you have any idea how to fix 
> the community-filiator --remove operation?
>
> Regards
> Bolette
>
>
> BOLETTE AMMITZBØLL JURIK
> Developer, IT Development 2
> DIRECT 8946 2322
>
>
>
> Det Kgl. Bibliotek
> Royal Danish Library
>  
> Victor Albecks Vej 1
> DK-8000 Aarhus C
> +45 3347 4747 <+45%2033%2047%2047%2047>
>  
> CVR 2898 8842
> EAN 5798 000 792142
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/16d9b138-4c0c-4786-a820-c2116daa9125n%40googlegroups.com.

Re: [dspace-tech] error building

[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

On Tue, May 3, 2022 at 8:53 PM Sean Kalynuk 
wrote:

> 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.
>
> --
>
> Sean
>
>
>
> *From: *Jose Blanco 
> *Date: *Tuesday, May 3, 2022 at 5:45 PM
> *To: *Sean Kalynuk 
> *Cc: *DSpace Technical Support 
> *Subject: *Re: [dspace-tech] error building
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
>
>
> 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
>
>
>
> On Tue, May 3, 2022 at 5:55 PM Sean Kalynuk 
> wrote:
>
> 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
>
>
>
> --
>
> Sean
>
>
>
> *From: *Jose Blanco 
> *Date: *Tuesday, May 3, 2022 at 4:46 PM
> *To: *Sean Kalynuk 
> *Cc: *DSpace Technical Support 
> *Subject: *Re: [dspace-tech] error building
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
>
>
> 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
>
>
>
> On Tue, May 3, 2022 at 4:36 PM Sean Kalynuk 
> wrote:
>
> 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
>
>
>
> *From: *Jose Blanco 
> *Date: *Tuesday, May 3, 2022 at 3:12 PM
> *To: *Sean Kalynuk 
> *Cc: *DSpace Technical Support 
> *Subject: *Re: [dspace-tech] error building
>
> *Caution:* This message was sent from outside the University of Manitoba.
>
>
>
> 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
>
>
>
> On Tue, May 3, 2022 at 3:08 PM Sean Kalynuk 
> wrote:
>
> 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: *dspace-tech@googlegroups.com  on
> behalf of Jose Blanco 
> *Date: *Tuesday, May 3, 2022 at 1:47 PM
> *To: *DSpace Technical Support 
> *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:g

[dspace-tech] Re: DS7.x: Item page customization and custom themes

[Agustina Martinez]

Hi Darryl,

We are currently at the same stage as you are regarding custom theming. I 
have opted for now to take a copy of the custom theme and use it as the 
basis for our institutional theme (to make updates a bit easier going 
forward I've removed all of those customisations from the custom theme that 
we do not use for now). But like you, do not know whether this is the best 
approach. I found the documentation pages really 
good: https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization 
and in particular the comments at the end answer your question about 
customising components such as the "untyped item". I have successfully done 
that in our test instance and happy to share with you if you don't get it 
working based on the info in the docs pages.

It would be great if someone could comment on best ways forward for 
customising in ways that make future upgrades simpler. I am really knew to 
angular so just slowly finding our ways!

Agustina

On Tuesday, 3 May 2022 at 21:02:24 UTC+1 darryl@usask.ca wrote:

>
> How are people theming DSpace 7.x? Is it better to create a new theme from 
> a copy of "custom" (and deal with integrating any future changes made to 
> "custom" manually), or just create a local branch of the dspace-angular 
> repo and modify the "custom" theme directly (and then pull in changes to 
> "custom" via a merge request from the main branch)?
>
> Also, can anyone point me in the right direction to make changes to the 
> simple item view? It seems the default for items in DSpace is "untyped 
> item" (I haven't enabled any of the entity stuff).  I've modified 
> src/app/item-page/simple/item-types/untyped-item/untyped-item.component.html 
> to get the results I want, but it seems like a bad idea to modify the 
> global code rather than something in my theme.
>
> The "custom" theme contains simple page templates for Publication items, 
> -- src/themes/limestone/app/item-page/simple/item-types/publication -- but 
> not untyped items.  Simply copying the "untyped-item" folder from the 
> global code into that "item-types" folder didn't seem to work.  I assume 
> there some additional changes required in a .ts file somewhere I also need 
> to update, but I'm, not quite sure which ones.  Or do I need to copy the 
> entire src/app/item-page directory tree into my theme?
>
> Unless there's some other (easier) way to add additional metadata fields 
> to the simple display that I've not discovered??
>
> Thanks,
>
> - Darryl
>
>
>
> --
> *Darryl Friesen, BSc*
> Programmer/Analyst
> *University of Saskatchewan*
> *ICT / University Library*
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/bcdf63ee-ff06-4ba7-a8e5-3f2ca29da1e7n%40googlegroups.com.