In which case can I use the option '--nodeps' of rpm command?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I heard that I should never use --nodeps option when I do a rpm -e command.
Why does this option exist then?
rpm options
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
asked Feb 10 '16 at 9:30
Pozinux
3962720
add a comment |
up vote
1
down vote
favorite
I heard that I should never use --nodeps option when I do a rpm -e command.
Why does this option exist then?
rpm options
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
asked Feb 10 '16 at 9:30
Pozinux
3962720
1
Simple answer: When you really, really, really know what you're doing.
– Shadur
Feb 10 '16 at 12:35
I love simple answers !
– Pozinux
Feb 10 '16 at 14:07
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I heard that I should never use --nodeps option when I do a rpm -e command.
Why does this option exist then?
rpm options
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
asked Feb 10 '16 at 9:30
Pozinux
3962720
I heard that I should never use --nodeps option when I do a rpm -e command.
Why does this option exist then?
rpm options
rpm options
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
asked Feb 10 '16 at 9:30
Pozinux
3962720
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
asked Feb 10 '16 at 9:30
Pozinux
3962720
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
edited Nov 24 at 19:51
Rui F Ribeiro
38.3k1476127
38.3k1476127
asked Feb 10 '16 at 9:30
Pozinux
3962720
asked Feb 10 '16 at 9:30
Pozinux
3962720
asked Feb 10 '16 at 9:30
Pozinux
3962720
3962720
1
Simple answer: When you really, really, really know what you're doing.
– Shadur
Feb 10 '16 at 12:35
I love simple answers !
– Pozinux
Feb 10 '16 at 14:07
add a comment |
1
Simple answer: When you really, really, really know what you're doing.
– Shadur
Feb 10 '16 at 12:35
I love simple answers !
– Pozinux
Feb 10 '16 at 14:07
1
1
Simple answer: When you really, really, really know what you're doing.
– Shadur
Feb 10 '16 at 12:35
Simple answer: When you really, really, really know what you're doing.
– Shadur
Feb 10 '16 at 12:35
I love simple answers !
– Pozinux
Feb 10 '16 at 14:07
I love simple answers !
– Pozinux
Feb 10 '16 at 14:07
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
It exists for broadly the same reasons rm will allow you to delete the filesystem root, or dd will allow you to overwrite the physical hard drive:
Linux and unix have a long history of giving you all the ammo you need when you really insist on shooting yourself in the foot.
Less flippantly, when something has gone badly wrong during a package install, whether due to a badly built package or an outage at the worst possible moment, it's possible to wind up with your package manager's dependency database in gridlock -- IE, it can't resolve the problem because attempting any of the solutions would violate the dependencies of the other packages involved. In that case, you can use --nodeps, or for dpkg, the --force-* options to manually and forcibly remove the offending package, and then immediately issue what commands are necessary to fix the now broken dependencies.
That's something you should only do if you're really sure of what you're doing, however; as a rule of thumb, if you aren't sure what use --nodep is, don't use it. You're essentially taking all the safeties off, and gods help you if you screw something up while doing it.
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
Exactly what I wanted to know and thanks for answering so quickly.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
up vote
2
down vote
--nodeps is when we do not want to verify package dependencies.
If you will use it with rpm it will not verify the package dependencies, and the installed package might not work as it should.
If you will use it with rpm -e command, the package will be erased without giving you warning, if some other packages are dependent on the package you are trying to erase.
answered Feb 10 '16 at 9:45
Piyush Jain
30816
Ok thanks for the precisions. In fact I know what it does and doesn't. I just wanted to know in which case I would need to use this option.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It exists for broadly the same reasons rm will allow you to delete the filesystem root, or dd will allow you to overwrite the physical hard drive:
Linux and unix have a long history of giving you all the ammo you need when you really insist on shooting yourself in the foot.
Less flippantly, when something has gone badly wrong during a package install, whether due to a badly built package or an outage at the worst possible moment, it's possible to wind up with your package manager's dependency database in gridlock -- IE, it can't resolve the problem because attempting any of the solutions would violate the dependencies of the other packages involved. In that case, you can use --nodeps, or for dpkg, the --force-* options to manually and forcibly remove the offending package, and then immediately issue what commands are necessary to fix the now broken dependencies.
That's something you should only do if you're really sure of what you're doing, however; as a rule of thumb, if you aren't sure what use --nodep is, don't use it. You're essentially taking all the safeties off, and gods help you if you screw something up while doing it.
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
Exactly what I wanted to know and thanks for answering so quickly.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
up vote
1
down vote
accepted
It exists for broadly the same reasons rm will allow you to delete the filesystem root, or dd will allow you to overwrite the physical hard drive:
Linux and unix have a long history of giving you all the ammo you need when you really insist on shooting yourself in the foot.
Less flippantly, when something has gone badly wrong during a package install, whether due to a badly built package or an outage at the worst possible moment, it's possible to wind up with your package manager's dependency database in gridlock -- IE, it can't resolve the problem because attempting any of the solutions would violate the dependencies of the other packages involved. In that case, you can use --nodeps, or for dpkg, the --force-* options to manually and forcibly remove the offending package, and then immediately issue what commands are necessary to fix the now broken dependencies.
That's something you should only do if you're really sure of what you're doing, however; as a rule of thumb, if you aren't sure what use --nodep is, don't use it. You're essentially taking all the safeties off, and gods help you if you screw something up while doing it.
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
Exactly what I wanted to know and thanks for answering so quickly.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It exists for broadly the same reasons rm will allow you to delete the filesystem root, or dd will allow you to overwrite the physical hard drive:
Linux and unix have a long history of giving you all the ammo you need when you really insist on shooting yourself in the foot.
Less flippantly, when something has gone badly wrong during a package install, whether due to a badly built package or an outage at the worst possible moment, it's possible to wind up with your package manager's dependency database in gridlock -- IE, it can't resolve the problem because attempting any of the solutions would violate the dependencies of the other packages involved. In that case, you can use --nodeps, or for dpkg, the --force-* options to manually and forcibly remove the offending package, and then immediately issue what commands are necessary to fix the now broken dependencies.
That's something you should only do if you're really sure of what you're doing, however; as a rule of thumb, if you aren't sure what use --nodep is, don't use it. You're essentially taking all the safeties off, and gods help you if you screw something up while doing it.
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
It exists for broadly the same reasons rm will allow you to delete the filesystem root, or dd will allow you to overwrite the physical hard drive:
Linux and unix have a long history of giving you all the ammo you need when you really insist on shooting yourself in the foot.
Less flippantly, when something has gone badly wrong during a package install, whether due to a badly built package or an outage at the worst possible moment, it's possible to wind up with your package manager's dependency database in gridlock -- IE, it can't resolve the problem because attempting any of the solutions would violate the dependencies of the other packages involved. In that case, you can use --nodeps, or for dpkg, the --force-* options to manually and forcibly remove the offending package, and then immediately issue what commands are necessary to fix the now broken dependencies.
That's something you should only do if you're really sure of what you're doing, however; as a rule of thumb, if you aren't sure what use --nodep is, don't use it. You're essentially taking all the safeties off, and gods help you if you screw something up while doing it.
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
answered Feb 10 '16 at 12:43
Shadur
19.2k64357
19.2k64357
Exactly what I wanted to know and thanks for answering so quickly.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
Exactly what I wanted to know and thanks for answering so quickly.
– Pozinux
Feb 10 '16 at 14:21
Exactly what I wanted to know and thanks for answering so quickly.
– Pozinux
Feb 10 '16 at 14:21
Exactly what I wanted to know and thanks for answering so quickly.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
up vote
2
down vote
--nodeps is when we do not want to verify package dependencies.
If you will use it with rpm it will not verify the package dependencies, and the installed package might not work as it should.
If you will use it with rpm -e command, the package will be erased without giving you warning, if some other packages are dependent on the package you are trying to erase.
answered Feb 10 '16 at 9:45
Piyush Jain
30816
Ok thanks for the precisions. In fact I know what it does and doesn't. I just wanted to know in which case I would need to use this option.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
up vote
2
down vote
--nodeps is when we do not want to verify package dependencies.
If you will use it with rpm it will not verify the package dependencies, and the installed package might not work as it should.
If you will use it with rpm -e command, the package will be erased without giving you warning, if some other packages are dependent on the package you are trying to erase.
answered Feb 10 '16 at 9:45
Piyush Jain
30816
Ok thanks for the precisions. In fact I know what it does and doesn't. I just wanted to know in which case I would need to use this option.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
up vote
2
down vote
up vote
2
down vote
--nodeps is when we do not want to verify package dependencies.
If you will use it with rpm it will not verify the package dependencies, and the installed package might not work as it should.
If you will use it with rpm -e command, the package will be erased without giving you warning, if some other packages are dependent on the package you are trying to erase.
answered Feb 10 '16 at 9:45
Piyush Jain
30816
--nodeps is when we do not want to verify package dependencies.
If you will use it with rpm it will not verify the package dependencies, and the installed package might not work as it should.
If you will use it with rpm -e command, the package will be erased without giving you warning, if some other packages are dependent on the package you are trying to erase.
answered Feb 10 '16 at 9:45
Piyush Jain
30816
answered Feb 10 '16 at 9:45
Piyush Jain
30816
answered Feb 10 '16 at 9:45
Piyush Jain
30816
answered Feb 10 '16 at 9:45
Piyush Jain
30816
30816
Ok thanks for the precisions. In fact I know what it does and doesn't. I just wanted to know in which case I would need to use this option.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
Ok thanks for the precisions. In fact I know what it does and doesn't. I just wanted to know in which case I would need to use this option.
– Pozinux
Feb 10 '16 at 14:21
Ok thanks for the precisions. In fact I know what it does and doesn't. I just wanted to know in which case I would need to use this option.
– Pozinux
Feb 10 '16 at 14:21
Ok thanks for the precisions. In fact I know what it does and doesn't. I just wanted to know in which case I would need to use this option.
– Pozinux
Feb 10 '16 at 14:21
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f261200%2fin-which-case-can-i-use-the-option-nodeps-of-rpm-command%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Simple answer: When you really, really, really know what you're doing.
– Shadur
Feb 10 '16 at 12:35
I love simple answers !
– Pozinux
Feb 10 '16 at 14:07