Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux rpm instrument directory permission incorrect #6066

Closed
Anders-Markvardsen opened this issue May 2, 2012 · 3 comments
Closed

Linux rpm instrument directory permission incorrect #6066

Anders-Markvardsen opened this issue May 2, 2012 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@Anders-Markvardsen
Copy link
Member

This issue was originally TRAC 5220

The linux rpm instrument directory permissions is not
writable to everyone. An effect of this is that .vtp
files cannot be written to this directory from an installed
version on Linux, and instead default to /tmp.

In cmake it is setup to be writable but somehow loses
this knowledge. Note this effect is only seen on Linux not Mac (or windows
for that matter).

Make this directory writable on linux also

@Anders-Markvardsen
Copy link
Member Author

@martyngigg (2012-05-04T10:47:23):
Just a note: This is something to do with CPACK and is confined to the RPM. The debian installation has the permissions set correctly.

Looking at the directory structure you can see that the permissions are correct after CPack has generated the temporary structure it is only once it has been packaged that the RPM fails to set the correct permissions. This used to work.


@NickDraper (2012-08-10T12:43:46):
Moved at the end of release 2.2


@NickDraper (2012-10-28T11:38:57):
Moved to milestone 2.4


@NickDraper (2013-01-28T09:23:06):
Moved at the code freeze for release 2.4


@NickDraper (2013-04-29T09:49:41):
Moved to r2.6 at the end of r2.5


@NickDraper (2013-07-26T13:54:59):
Moved to backlog at the code freeze for R2.6


@NickDraper (2014-02-14T11:04:56):
Bulk move to assigned at the introduction of the triage step

@Anders-Markvardsen Anders-Markvardsen added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@stale
Copy link

stale bot commented Feb 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 24, 2021
@martyngigg
Copy link
Member

No longer relevant. The directories are not writable but now the files go to the mantid user file directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

3 participants