Why removing npm means removing nodejs as well on CentOS?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm trying to remove npm (EPEL repository), but yum wants me to remove nodejs as well. It's nodejs that is npm's dependency. Not the other way around. nodejs can live without npm just fine. Am I missing something?
centos yum node.js npm
asked Dec 6 '17 at 11:48
x-yuri
1,10711641
add a comment |Â
up vote
0
down vote
favorite
I'm trying to remove npm (EPEL repository), but yum wants me to remove nodejs as well. It's nodejs that is npm's dependency. Not the other way around. nodejs can live without npm just fine. Am I missing something?
centos yum node.js npm
asked Dec 6 '17 at 11:48
x-yuri
1,10711641
I'm no Yum user, but maybe NodeJS was installed as a dependency for npm and that's why it wants to remove NodeJS as well? You could try going along with it and then installing NodeJS again.
– Kusalananda
Dec 6 '17 at 12:00
You may be right, but the question is not about how to deal with it. But rather about what's going on.
– x-yuri
Dec 6 '17 at 12:14
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to remove npm (EPEL repository), but yum wants me to remove nodejs as well. It's nodejs that is npm's dependency. Not the other way around. nodejs can live without npm just fine. Am I missing something?
centos yum node.js npm
asked Dec 6 '17 at 11:48
x-yuri
1,10711641
I'm trying to remove npm (EPEL repository), but yum wants me to remove nodejs as well. It's nodejs that is npm's dependency. Not the other way around. nodejs can live without npm just fine. Am I missing something?
centos yum node.js npm
asked Dec 6 '17 at 11:48
x-yuri
1,10711641
asked Dec 6 '17 at 11:48
x-yuri
1,10711641
asked Dec 6 '17 at 11:48
x-yuri
1,10711641
asked Dec 6 '17 at 11:48
x-yuri
1,10711641
1,10711641
I'm no Yum user, but maybe NodeJS was installed as a dependency for npm and that's why it wants to remove NodeJS as well? You could try going along with it and then installing NodeJS again.
– Kusalananda
Dec 6 '17 at 12:00
You may be right, but the question is not about how to deal with it. But rather about what's going on.
– x-yuri
Dec 6 '17 at 12:14
add a comment |Â
I'm no Yum user, but maybe NodeJS was installed as a dependency for npm and that's why it wants to remove NodeJS as well? You could try going along with it and then installing NodeJS again.
– Kusalananda
Dec 6 '17 at 12:00
You may be right, but the question is not about how to deal with it. But rather about what's going on.
– x-yuri
Dec 6 '17 at 12:14
I'm no Yum user, but maybe NodeJS was installed as a dependency for npm and that's why it wants to remove NodeJS as well? You could try going along with it and then installing NodeJS again.
– Kusalananda
Dec 6 '17 at 12:00
I'm no Yum user, but maybe NodeJS was installed as a dependency for npm and that's why it wants to remove NodeJS as well? You could try going along with it and then installing NodeJS again.
– Kusalananda
Dec 6 '17 at 12:00
You may be right, but the question is not about how to deal with it. But rather about what's going on.
– x-yuri
Dec 6 '17 at 12:14
You may be right, but the question is not about how to deal with it. But rather about what's going on.
– x-yuri
Dec 6 '17 at 12:14
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I see. I had both EPEL and NodeSource repositories added. It appears repoquery -R and yum deplist report information regarding only the latest version. In my case it was from NodeSource repository. The following command:
yum deplist --showduplicates nodejs
showed that nodejs from EPEL does depend on npm. Alternativaly, you can run:
repoquery -R --disablerepo=* --enablerepo=epel nodejs
or (not at all convenient, no separation between packages):
repoquery -R --show-duplicates nodejs
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I see. I had both EPEL and NodeSource repositories added. It appears repoquery -R and yum deplist report information regarding only the latest version. In my case it was from NodeSource repository. The following command:
yum deplist --showduplicates nodejs
showed that nodejs from EPEL does depend on npm. Alternativaly, you can run:
repoquery -R --disablerepo=* --enablerepo=epel nodejs
or (not at all convenient, no separation between packages):
repoquery -R --show-duplicates nodejs
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
add a comment |Â
up vote
1
down vote
accepted
I see. I had both EPEL and NodeSource repositories added. It appears repoquery -R and yum deplist report information regarding only the latest version. In my case it was from NodeSource repository. The following command:
yum deplist --showduplicates nodejs
showed that nodejs from EPEL does depend on npm. Alternativaly, you can run:
repoquery -R --disablerepo=* --enablerepo=epel nodejs
or (not at all convenient, no separation between packages):
repoquery -R --show-duplicates nodejs
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I see. I had both EPEL and NodeSource repositories added. It appears repoquery -R and yum deplist report information regarding only the latest version. In my case it was from NodeSource repository. The following command:
yum deplist --showduplicates nodejs
showed that nodejs from EPEL does depend on npm. Alternativaly, you can run:
repoquery -R --disablerepo=* --enablerepo=epel nodejs
or (not at all convenient, no separation between packages):
repoquery -R --show-duplicates nodejs
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
I see. I had both EPEL and NodeSource repositories added. It appears repoquery -R and yum deplist report information regarding only the latest version. In my case it was from NodeSource repository. The following command:
yum deplist --showduplicates nodejs
showed that nodejs from EPEL does depend on npm. Alternativaly, you can run:
repoquery -R --disablerepo=* --enablerepo=epel nodejs
or (not at all convenient, no separation between packages):
repoquery -R --show-duplicates nodejs
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
answered Dec 6 '17 at 18:25
x-yuri
1,10711641
1,10711641
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f409183%2fwhy-removing-npm-means-removing-nodejs-as-well-on-centos%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I'm no Yum user, but maybe NodeJS was installed as a dependency for npm and that's why it wants to remove NodeJS as well? You could try going along with it and then installing NodeJS again.
– Kusalananda
Dec 6 '17 at 12:00
You may be right, but the question is not about how to deal with it. But rather about what's going on.
– x-yuri
Dec 6 '17 at 12:14