How to mark a package to prevent from being installed [duplicate]
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
4
down vote
favorite
This question already has an answer here:
How can I prevent installation of a specific package on Linux Mint?
1 answer
apt pinning package versions
1 answer
I've detected some packages that breaks my configuration (like light-locker
, evince
, etc...)
How can I prevent these packages to be able to install via apt-get install
in my system (Debian) with the provided error reason?
debian package-management
marked as duplicate by Thomas Dickey, Thomas, schily, muru, Wouter Verhelst Jul 30 at 13:17
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |Â
up vote
4
down vote
favorite
This question already has an answer here:
How can I prevent installation of a specific package on Linux Mint?
1 answer
apt pinning package versions
1 answer
I've detected some packages that breaks my configuration (like light-locker
, evince
, etc...)
How can I prevent these packages to be able to install via apt-get install
in my system (Debian) with the provided error reason?
debian package-management
marked as duplicate by Thomas Dickey, Thomas, schily, muru, Wouter Verhelst Jul 30 at 13:17
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
No, it's not duplicate. They may or may not have the same solution, questions are different.
â ceremcem
Jul 29 at 12:14
2
It is not a duplicate because the question belong to AskUbuntu, also the duplicate flag doesn't explain how to prevent a package from being installed.
â GAD3R
Jul 29 at 12:43
@ceremcem that doesn't mean anything without also telling us what exact configuration you tried.
â muru
Jul 30 at 8:31
I mean by "not solving my case" is that it still lets me install a "banned" package. The same answer is below and after banning a packageapt policy light-locker
still shows a candidate. It's not exactly related with my own use case, packages are still be able to install.
â ceremcem
Jul 30 at 8:37
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
This question already has an answer here:
How can I prevent installation of a specific package on Linux Mint?
1 answer
apt pinning package versions
1 answer
I've detected some packages that breaks my configuration (like light-locker
, evince
, etc...)
How can I prevent these packages to be able to install via apt-get install
in my system (Debian) with the provided error reason?
debian package-management
This question already has an answer here:
How can I prevent installation of a specific package on Linux Mint?
1 answer
apt pinning package versions
1 answer
I've detected some packages that breaks my configuration (like light-locker
, evince
, etc...)
How can I prevent these packages to be able to install via apt-get install
in my system (Debian) with the provided error reason?
This question already has an answer here:
How can I prevent installation of a specific package on Linux Mint?
1 answer
apt pinning package versions
1 answer
debian package-management
edited Jul 29 at 19:54
Mark Stewart
6001415
6001415
asked Jul 29 at 10:58
ceremcem
5021420
5021420
marked as duplicate by Thomas Dickey, Thomas, schily, muru, Wouter Verhelst Jul 30 at 13:17
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by Thomas Dickey, Thomas, schily, muru, Wouter Verhelst Jul 30 at 13:17
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
No, it's not duplicate. They may or may not have the same solution, questions are different.
â ceremcem
Jul 29 at 12:14
2
It is not a duplicate because the question belong to AskUbuntu, also the duplicate flag doesn't explain how to prevent a package from being installed.
â GAD3R
Jul 29 at 12:43
@ceremcem that doesn't mean anything without also telling us what exact configuration you tried.
â muru
Jul 30 at 8:31
I mean by "not solving my case" is that it still lets me install a "banned" package. The same answer is below and after banning a packageapt policy light-locker
still shows a candidate. It's not exactly related with my own use case, packages are still be able to install.
â ceremcem
Jul 30 at 8:37
add a comment |Â
No, it's not duplicate. They may or may not have the same solution, questions are different.
â ceremcem
Jul 29 at 12:14
2
It is not a duplicate because the question belong to AskUbuntu, also the duplicate flag doesn't explain how to prevent a package from being installed.
â GAD3R
Jul 29 at 12:43
@ceremcem that doesn't mean anything without also telling us what exact configuration you tried.
â muru
Jul 30 at 8:31
I mean by "not solving my case" is that it still lets me install a "banned" package. The same answer is below and after banning a packageapt policy light-locker
still shows a candidate. It's not exactly related with my own use case, packages are still be able to install.
â ceremcem
Jul 30 at 8:37
No, it's not duplicate. They may or may not have the same solution, questions are different.
â ceremcem
Jul 29 at 12:14
No, it's not duplicate. They may or may not have the same solution, questions are different.
â ceremcem
Jul 29 at 12:14
2
2
It is not a duplicate because the question belong to AskUbuntu, also the duplicate flag doesn't explain how to prevent a package from being installed.
â GAD3R
Jul 29 at 12:43
It is not a duplicate because the question belong to AskUbuntu, also the duplicate flag doesn't explain how to prevent a package from being installed.
â GAD3R
Jul 29 at 12:43
@ceremcem that doesn't mean anything without also telling us what exact configuration you tried.
â muru
Jul 30 at 8:31
@ceremcem that doesn't mean anything without also telling us what exact configuration you tried.
â muru
Jul 30 at 8:31
I mean by "not solving my case" is that it still lets me install a "banned" package. The same answer is below and after banning a package
apt policy light-locker
still shows a candidate. It's not exactly related with my own use case, packages are still be able to install.â ceremcem
Jul 30 at 8:37
I mean by "not solving my case" is that it still lets me install a "banned" package. The same answer is below and after banning a package
apt policy light-locker
still shows a candidate. It's not exactly related with my own use case, packages are still be able to install.â ceremcem
Jul 30 at 8:37
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
Use Pin-Priority: -1
for example:
$ cat >/etc/apt/preferences.d/libsystemd0 <<EOF
Package: libsystemd0
Pin: origin ""
Pin-Priority: -1
EOF
I placed a file forevince
andapt-get install evince
still installs it. Would you confirm that you can't install some specific package with this configuration?
â ceremcem
Jul 29 at 12:17
1
@ceremcem I think pining a specific package version of (a buggy) package is the best way. For example you can usePin: version 3.22.1-3+deb9u1
forevince
(note that evince isn't buggy) if the package version change the package will be installed. useapt-cache policy pkg_name
to get the exact version.
â GAD3R
Jul 29 at 12:37
Sometimes I may want to ban a package because of a bug according to me which is a feature from the point of view of developers. For example, light-locker was my sneaky screen locker which I didn't find a way to disable it and when I learned its name, uninstalling it solved my problem.
â ceremcem
Jul 30 at 8:48
add a comment |Â
up vote
2
down vote
I've detected some packages that breaks my configuration (like light-locker, evince, etc...)
The apt-listbugs
is the correct tool to deal with a buggy package allowing you to pin the package or the dependencies. For example:
# apt install apt-listbugs
$ apt-listbugs list light-locker
grave bugs of light-locker (-> ) <Outstanding>
b1 - #892290 - light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect
Summary:
light-locker(1 bug)
how does that help the OP ?
â Berry Tsakala
Jul 29 at 13:07
@BerryTsakala Only the buggy package break the system, the OP ask for a solution to prevent the buggy package from being installed. I have quoted the first line to understand what happened.
â GAD3R
Jul 29 at 13:24
1
apt-listbugs
seems a helper tool but 1. it can not prevent a package from being automatically installed, 2. it isn't a proper error handling (if we don't use it or ignore its output, the package is able to be installed, 3. we can't always examine all the bugs for every package. But it's good to know that there is such a tool.
â ceremcem
Jul 30 at 8:33
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Use Pin-Priority: -1
for example:
$ cat >/etc/apt/preferences.d/libsystemd0 <<EOF
Package: libsystemd0
Pin: origin ""
Pin-Priority: -1
EOF
I placed a file forevince
andapt-get install evince
still installs it. Would you confirm that you can't install some specific package with this configuration?
â ceremcem
Jul 29 at 12:17
1
@ceremcem I think pining a specific package version of (a buggy) package is the best way. For example you can usePin: version 3.22.1-3+deb9u1
forevince
(note that evince isn't buggy) if the package version change the package will be installed. useapt-cache policy pkg_name
to get the exact version.
â GAD3R
Jul 29 at 12:37
Sometimes I may want to ban a package because of a bug according to me which is a feature from the point of view of developers. For example, light-locker was my sneaky screen locker which I didn't find a way to disable it and when I learned its name, uninstalling it solved my problem.
â ceremcem
Jul 30 at 8:48
add a comment |Â
up vote
3
down vote
Use Pin-Priority: -1
for example:
$ cat >/etc/apt/preferences.d/libsystemd0 <<EOF
Package: libsystemd0
Pin: origin ""
Pin-Priority: -1
EOF
I placed a file forevince
andapt-get install evince
still installs it. Would you confirm that you can't install some specific package with this configuration?
â ceremcem
Jul 29 at 12:17
1
@ceremcem I think pining a specific package version of (a buggy) package is the best way. For example you can usePin: version 3.22.1-3+deb9u1
forevince
(note that evince isn't buggy) if the package version change the package will be installed. useapt-cache policy pkg_name
to get the exact version.
â GAD3R
Jul 29 at 12:37
Sometimes I may want to ban a package because of a bug according to me which is a feature from the point of view of developers. For example, light-locker was my sneaky screen locker which I didn't find a way to disable it and when I learned its name, uninstalling it solved my problem.
â ceremcem
Jul 30 at 8:48
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Use Pin-Priority: -1
for example:
$ cat >/etc/apt/preferences.d/libsystemd0 <<EOF
Package: libsystemd0
Pin: origin ""
Pin-Priority: -1
EOF
Use Pin-Priority: -1
for example:
$ cat >/etc/apt/preferences.d/libsystemd0 <<EOF
Package: libsystemd0
Pin: origin ""
Pin-Priority: -1
EOF
edited Jul 29 at 23:11
slmâ¦
232k65479649
232k65479649
answered Jul 29 at 11:20
Ipor Sircer
8,6271920
8,6271920
I placed a file forevince
andapt-get install evince
still installs it. Would you confirm that you can't install some specific package with this configuration?
â ceremcem
Jul 29 at 12:17
1
@ceremcem I think pining a specific package version of (a buggy) package is the best way. For example you can usePin: version 3.22.1-3+deb9u1
forevince
(note that evince isn't buggy) if the package version change the package will be installed. useapt-cache policy pkg_name
to get the exact version.
â GAD3R
Jul 29 at 12:37
Sometimes I may want to ban a package because of a bug according to me which is a feature from the point of view of developers. For example, light-locker was my sneaky screen locker which I didn't find a way to disable it and when I learned its name, uninstalling it solved my problem.
â ceremcem
Jul 30 at 8:48
add a comment |Â
I placed a file forevince
andapt-get install evince
still installs it. Would you confirm that you can't install some specific package with this configuration?
â ceremcem
Jul 29 at 12:17
1
@ceremcem I think pining a specific package version of (a buggy) package is the best way. For example you can usePin: version 3.22.1-3+deb9u1
forevince
(note that evince isn't buggy) if the package version change the package will be installed. useapt-cache policy pkg_name
to get the exact version.
â GAD3R
Jul 29 at 12:37
Sometimes I may want to ban a package because of a bug according to me which is a feature from the point of view of developers. For example, light-locker was my sneaky screen locker which I didn't find a way to disable it and when I learned its name, uninstalling it solved my problem.
â ceremcem
Jul 30 at 8:48
I placed a file for
evince
and apt-get install evince
still installs it. Would you confirm that you can't install some specific package with this configuration?â ceremcem
Jul 29 at 12:17
I placed a file for
evince
and apt-get install evince
still installs it. Would you confirm that you can't install some specific package with this configuration?â ceremcem
Jul 29 at 12:17
1
1
@ceremcem I think pining a specific package version of (a buggy) package is the best way. For example you can use
Pin: version 3.22.1-3+deb9u1
for evince
(note that evince isn't buggy) if the package version change the package will be installed. use apt-cache policy pkg_name
to get the exact version.â GAD3R
Jul 29 at 12:37
@ceremcem I think pining a specific package version of (a buggy) package is the best way. For example you can use
Pin: version 3.22.1-3+deb9u1
for evince
(note that evince isn't buggy) if the package version change the package will be installed. use apt-cache policy pkg_name
to get the exact version.â GAD3R
Jul 29 at 12:37
Sometimes I may want to ban a package because of a bug according to me which is a feature from the point of view of developers. For example, light-locker was my sneaky screen locker which I didn't find a way to disable it and when I learned its name, uninstalling it solved my problem.
â ceremcem
Jul 30 at 8:48
Sometimes I may want to ban a package because of a bug according to me which is a feature from the point of view of developers. For example, light-locker was my sneaky screen locker which I didn't find a way to disable it and when I learned its name, uninstalling it solved my problem.
â ceremcem
Jul 30 at 8:48
add a comment |Â
up vote
2
down vote
I've detected some packages that breaks my configuration (like light-locker, evince, etc...)
The apt-listbugs
is the correct tool to deal with a buggy package allowing you to pin the package or the dependencies. For example:
# apt install apt-listbugs
$ apt-listbugs list light-locker
grave bugs of light-locker (-> ) <Outstanding>
b1 - #892290 - light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect
Summary:
light-locker(1 bug)
how does that help the OP ?
â Berry Tsakala
Jul 29 at 13:07
@BerryTsakala Only the buggy package break the system, the OP ask for a solution to prevent the buggy package from being installed. I have quoted the first line to understand what happened.
â GAD3R
Jul 29 at 13:24
1
apt-listbugs
seems a helper tool but 1. it can not prevent a package from being automatically installed, 2. it isn't a proper error handling (if we don't use it or ignore its output, the package is able to be installed, 3. we can't always examine all the bugs for every package. But it's good to know that there is such a tool.
â ceremcem
Jul 30 at 8:33
add a comment |Â
up vote
2
down vote
I've detected some packages that breaks my configuration (like light-locker, evince, etc...)
The apt-listbugs
is the correct tool to deal with a buggy package allowing you to pin the package or the dependencies. For example:
# apt install apt-listbugs
$ apt-listbugs list light-locker
grave bugs of light-locker (-> ) <Outstanding>
b1 - #892290 - light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect
Summary:
light-locker(1 bug)
how does that help the OP ?
â Berry Tsakala
Jul 29 at 13:07
@BerryTsakala Only the buggy package break the system, the OP ask for a solution to prevent the buggy package from being installed. I have quoted the first line to understand what happened.
â GAD3R
Jul 29 at 13:24
1
apt-listbugs
seems a helper tool but 1. it can not prevent a package from being automatically installed, 2. it isn't a proper error handling (if we don't use it or ignore its output, the package is able to be installed, 3. we can't always examine all the bugs for every package. But it's good to know that there is such a tool.
â ceremcem
Jul 30 at 8:33
add a comment |Â
up vote
2
down vote
up vote
2
down vote
I've detected some packages that breaks my configuration (like light-locker, evince, etc...)
The apt-listbugs
is the correct tool to deal with a buggy package allowing you to pin the package or the dependencies. For example:
# apt install apt-listbugs
$ apt-listbugs list light-locker
grave bugs of light-locker (-> ) <Outstanding>
b1 - #892290 - light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect
Summary:
light-locker(1 bug)
I've detected some packages that breaks my configuration (like light-locker, evince, etc...)
The apt-listbugs
is the correct tool to deal with a buggy package allowing you to pin the package or the dependencies. For example:
# apt install apt-listbugs
$ apt-listbugs list light-locker
grave bugs of light-locker (-> ) <Outstanding>
b1 - #892290 - light-locker: at unlock, crash with: arguments to dbus_message_new_method_call() were incorrect
Summary:
light-locker(1 bug)
edited Jul 29 at 12:39
Jeff Schaller
30.7k846104
30.7k846104
answered Jul 29 at 12:09
GAD3R
22k154891
22k154891
how does that help the OP ?
â Berry Tsakala
Jul 29 at 13:07
@BerryTsakala Only the buggy package break the system, the OP ask for a solution to prevent the buggy package from being installed. I have quoted the first line to understand what happened.
â GAD3R
Jul 29 at 13:24
1
apt-listbugs
seems a helper tool but 1. it can not prevent a package from being automatically installed, 2. it isn't a proper error handling (if we don't use it or ignore its output, the package is able to be installed, 3. we can't always examine all the bugs for every package. But it's good to know that there is such a tool.
â ceremcem
Jul 30 at 8:33
add a comment |Â
how does that help the OP ?
â Berry Tsakala
Jul 29 at 13:07
@BerryTsakala Only the buggy package break the system, the OP ask for a solution to prevent the buggy package from being installed. I have quoted the first line to understand what happened.
â GAD3R
Jul 29 at 13:24
1
apt-listbugs
seems a helper tool but 1. it can not prevent a package from being automatically installed, 2. it isn't a proper error handling (if we don't use it or ignore its output, the package is able to be installed, 3. we can't always examine all the bugs for every package. But it's good to know that there is such a tool.
â ceremcem
Jul 30 at 8:33
how does that help the OP ?
â Berry Tsakala
Jul 29 at 13:07
how does that help the OP ?
â Berry Tsakala
Jul 29 at 13:07
@BerryTsakala Only the buggy package break the system, the OP ask for a solution to prevent the buggy package from being installed. I have quoted the first line to understand what happened.
â GAD3R
Jul 29 at 13:24
@BerryTsakala Only the buggy package break the system, the OP ask for a solution to prevent the buggy package from being installed. I have quoted the first line to understand what happened.
â GAD3R
Jul 29 at 13:24
1
1
apt-listbugs
seems a helper tool but 1. it can not prevent a package from being automatically installed, 2. it isn't a proper error handling (if we don't use it or ignore its output, the package is able to be installed, 3. we can't always examine all the bugs for every package. But it's good to know that there is such a tool.â ceremcem
Jul 30 at 8:33
apt-listbugs
seems a helper tool but 1. it can not prevent a package from being automatically installed, 2. it isn't a proper error handling (if we don't use it or ignore its output, the package is able to be installed, 3. we can't always examine all the bugs for every package. But it's good to know that there is such a tool.â ceremcem
Jul 30 at 8:33
add a comment |Â
No, it's not duplicate. They may or may not have the same solution, questions are different.
â ceremcem
Jul 29 at 12:14
2
It is not a duplicate because the question belong to AskUbuntu, also the duplicate flag doesn't explain how to prevent a package from being installed.
â GAD3R
Jul 29 at 12:43
@ceremcem that doesn't mean anything without also telling us what exact configuration you tried.
â muru
Jul 30 at 8:31
I mean by "not solving my case" is that it still lets me install a "banned" package. The same answer is below and after banning a package
apt policy light-locker
still shows a candidate. It's not exactly related with my own use case, packages are still be able to install.â ceremcem
Jul 30 at 8:37