Error installing perl-doc: bug or poor usage?

The name of the pictureThe name of the pictureThe name of the pictureClash 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?







share|improve this question

























    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?







    share|improve this question





















      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?







      share|improve this question











      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?









      share|improve this question










      share|improve this question




      share|improve this question









      asked yesterday









      giusti

      600217




      600217

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          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



































          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes










           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          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













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Christian Cage

          How to properly install USB display driver for Fresco Logic FL2000DX on Ubuntu?