Error installing perl-doc: bug or poor usage?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
I encountered the following error while trying to install perl-doc
:
$ su
Password:
# apt-get install perl-doc
<snip>
Get:1 http://ftp.br.debian.org/debian testing/main amd64 perl-doc all 5.26.2-6 [7,429 kB]
Fetched 7,429 kB in 4s (1,721 kB/s)
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
Granted, the solution was obvious:
# exit
$ su -
Password:
# apt-get install perl-doc
However, I have always installed with a simple su
. And the perl-doc
installation has always been pretty trivial.
My question is: does the package requiring ldconfig
to be in PATH
is reasonable (therefore my mistake and I need to get used to su -
from now on) or is this bad practice from the packaging process and therefore a bug?
debian packaging
add a comment |Â
up vote
0
down vote
favorite
I encountered the following error while trying to install perl-doc
:
$ su
Password:
# apt-get install perl-doc
<snip>
Get:1 http://ftp.br.debian.org/debian testing/main amd64 perl-doc all 5.26.2-6 [7,429 kB]
Fetched 7,429 kB in 4s (1,721 kB/s)
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
Granted, the solution was obvious:
# exit
$ su -
Password:
# apt-get install perl-doc
However, I have always installed with a simple su
. And the perl-doc
installation has always been pretty trivial.
My question is: does the package requiring ldconfig
to be in PATH
is reasonable (therefore my mistake and I need to get used to su -
from now on) or is this bad practice from the packaging process and therefore a bug?
debian packaging
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I encountered the following error while trying to install perl-doc
:
$ su
Password:
# apt-get install perl-doc
<snip>
Get:1 http://ftp.br.debian.org/debian testing/main amd64 perl-doc all 5.26.2-6 [7,429 kB]
Fetched 7,429 kB in 4s (1,721 kB/s)
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
Granted, the solution was obvious:
# exit
$ su -
Password:
# apt-get install perl-doc
However, I have always installed with a simple su
. And the perl-doc
installation has always been pretty trivial.
My question is: does the package requiring ldconfig
to be in PATH
is reasonable (therefore my mistake and I need to get used to su -
from now on) or is this bad practice from the packaging process and therefore a bug?
debian packaging
I encountered the following error while trying to install perl-doc
:
$ su
Password:
# apt-get install perl-doc
<snip>
Get:1 http://ftp.br.debian.org/debian testing/main amd64 perl-doc all 5.26.2-6 [7,429 kB]
Fetched 7,429 kB in 4s (1,721 kB/s)
dpkg: warning: 'ldconfig' not found in PATH or not executable
dpkg: warning: 'start-stop-daemon' not found in PATH or not executable
dpkg: error: 2 expected programs not found in PATH or not executable
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin
E: Sub-process /usr/bin/dpkg returned an error code (2)
Granted, the solution was obvious:
# exit
$ su -
Password:
# apt-get install perl-doc
However, I have always installed with a simple su
. And the perl-doc
installation has always been pretty trivial.
My question is: does the package requiring ldconfig
to be in PATH
is reasonable (therefore my mistake and I need to get used to su -
from now on) or is this bad practice from the packaging process and therefore a bug?
debian packaging
asked yesterday
giusti
600217
600217
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f460593%2ferror-installing-perl-doc-bug-or-poor-usage%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