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

[Bug]: Inconsistent ownership of /usr/lib/node_modules #139

Closed
Kyuuhachi opened this issue Mar 3, 2022 · 3 comments
Closed

[Bug]: Inconsistent ownership of /usr/lib/node_modules #139

Kyuuhachi opened this issue Mar 3, 2022 · 3 comments
Labels

Comments

@Kyuuhachi
Copy link

Kyuuhachi commented Mar 3, 2022

General description of the problem:

After adding vscode-langservers-extracted, aconfmgr started exhibiting strange behavior where every run toggles ownership of /usr/lib/node_modules between root and my user. This is possibly due to v-l-e being an AUR package, though other AUR packages don't have that behavior, so it's kinda weird.

Steps to reproduce the problem:

I don't know the full steps, but for me it started when I added

AddPackage --foreign vscode-langservers-extracted

Run aconfmgr apply several times to see the results.

Configuration:

AddPackage --foreign vscode-langservers-extracted

Expected result:

Ownership of /usr/lib/node_modules should be root:root.

Actual result:

Ownership of /usr/lib/node_modules toggles between root:root and me:me each time I run aconfmgr apply.

Log:

...
::: Searching for modified files...
...
:::: nodejs: /usr/lib/node_modules
:::: vscode-langservers-extracted: /usr/bin
...
:: Examining file properties...
::: Loading data...
:::: Done.
::: Comparing file properties...
:::: Done.
::: Done (2 only in system, 0 changed, 0 only in config).
...
:::: Found 0 new, 0 changed, and 2 extra files properties.
::::: Proceed? [Y/n/d] y
::::: Setting owner of /usr/lib/node_modules to root (default value)
::::: Setting group of /usr/lib/node_modules to root (default value)
::::: Done.:::: Done.
::: Done.
:: Done (system state changed).
::: Searching for modified files...
...
:::: vscode-langservers-extracted: /usr/bin
:::: vscode-langservers-extracted: /usr/lib/node_modules
...
:: Examining file properties...
::: Loading data...
:::: Done.
::: Comparing file properties...
:::: Done.
::: Done (2 only in system, 0 changed, 0 only in config).
:: Done.
...
:::: Found 0 new, 0 changed, and 2 extra files properties.
::::: Proceed? [Y/n/d] y
::::: Setting owner of /usr/lib/node_modules to me (default value)
::::: Setting group of /usr/lib/node_modules to me (default value)
::::: Done.
:::: Done.
::: Done.
:: Done (system state changed).

Additional context:

Using Yay for AUR, in case it matters.

@Kyuuhachi Kyuuhachi added the bug label Mar 3, 2022
@CyberShadow
Copy link
Owner

It's a bug in the package. /usr/lib/node_modules should be owned by root in the package file (.pkg.tar.zst).

Some discussion here: #115 (comment)

@CyberShadow
Copy link
Owner

I see someone already reported the package bug:
https://aur.archlinux.org/packages/vscode-langservers-extracted#comment-853074

@Kyuuhachi
Copy link
Author

Oh, okay. Only noticed symptoms when using it with ACM, so I figured that's where the problem was.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants