Unable to execute new pre-installation script (/var/lib/dpkg/tmp.ci/preinst)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












I try to install a .deb file in my vagrant box that use generic/ubuntu1604 image but i got the following error:



Reading package lists... Done
Building dependency tree

Reading state information... Done
Reading state information... Done

A queue based service for watching directories for files to process as per its configuration.
Do you want to install the software package? [y/N]:y
(Reading database ... 108439 files and directories currently installed.)
Preparing to unpack wtbuild.deb ...
dpkg (subprocess): unable to execute new pre-installation script (/var/lib/dpkg/tmp.ci/preinst): No such file or directory
dpkg: error processing archive wtbuild.deb (--install):
subprocess new pre-installation script returned error exit status 2
Errors were encountered while processing:
wtbuild.deb


error



That only happens with that image. If i try to install the same .deb file in my linux machine ( xenial ) or in another vagrant box with a different linux image the .deb file is installed correctly.










share|improve this question

























    up vote
    1
    down vote

    favorite












    I try to install a .deb file in my vagrant box that use generic/ubuntu1604 image but i got the following error:



    Reading package lists... Done
    Building dependency tree

    Reading state information... Done
    Reading state information... Done

    A queue based service for watching directories for files to process as per its configuration.
    Do you want to install the software package? [y/N]:y
    (Reading database ... 108439 files and directories currently installed.)
    Preparing to unpack wtbuild.deb ...
    dpkg (subprocess): unable to execute new pre-installation script (/var/lib/dpkg/tmp.ci/preinst): No such file or directory
    dpkg: error processing archive wtbuild.deb (--install):
    subprocess new pre-installation script returned error exit status 2
    Errors were encountered while processing:
    wtbuild.deb


    error



    That only happens with that image. If i try to install the same .deb file in my linux machine ( xenial ) or in another vagrant box with a different linux image the .deb file is installed correctly.










    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I try to install a .deb file in my vagrant box that use generic/ubuntu1604 image but i got the following error:



      Reading package lists... Done
      Building dependency tree

      Reading state information... Done
      Reading state information... Done

      A queue based service for watching directories for files to process as per its configuration.
      Do you want to install the software package? [y/N]:y
      (Reading database ... 108439 files and directories currently installed.)
      Preparing to unpack wtbuild.deb ...
      dpkg (subprocess): unable to execute new pre-installation script (/var/lib/dpkg/tmp.ci/preinst): No such file or directory
      dpkg: error processing archive wtbuild.deb (--install):
      subprocess new pre-installation script returned error exit status 2
      Errors were encountered while processing:
      wtbuild.deb


      error



      That only happens with that image. If i try to install the same .deb file in my linux machine ( xenial ) or in another vagrant box with a different linux image the .deb file is installed correctly.










      share|improve this question













      I try to install a .deb file in my vagrant box that use generic/ubuntu1604 image but i got the following error:



      Reading package lists... Done
      Building dependency tree

      Reading state information... Done
      Reading state information... Done

      A queue based service for watching directories for files to process as per its configuration.
      Do you want to install the software package? [y/N]:y
      (Reading database ... 108439 files and directories currently installed.)
      Preparing to unpack wtbuild.deb ...
      dpkg (subprocess): unable to execute new pre-installation script (/var/lib/dpkg/tmp.ci/preinst): No such file or directory
      dpkg: error processing archive wtbuild.deb (--install):
      subprocess new pre-installation script returned error exit status 2
      Errors were encountered while processing:
      wtbuild.deb


      error



      That only happens with that image. If i try to install the same .deb file in my linux machine ( xenial ) or in another vagrant box with a different linux image the .deb file is installed correctly.







      dpkg deb vagrant






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 31 at 17:15









      Javier Galarza

      62




      62




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          You're missing the executable that appears in the preinst script's shebang line.



          1. Extract the package metadata to a temporary directory: dpkg -e wtbuild.deb tmp

          2. Open tmp/preinst in a text editor.

          3. The first line should begin with the characters #!. The text that appears after that is the program that will be used to run the file. You're missing that program.

          4. Determine the package that provides the missing program. For example, if the program is /usr/bin/python, you should install the python package: sudo apt-get install python

          If you maintain wtbuild.deb, you should take the time to add the missing dependency to the package's control file. If someone else maintains wtbuild.deb, you should file a bug report and include the name of the missing dependency package.






          share|improve this answer
















          • 1




            Thanks @Zenexer. This pointed me in the right direction. My shebang was off but not because the file didn't exist but because I had CrLf line endings instead of Lf.
            – N Jones
            Mar 2 at 22:16










          • @NJones That's effectively the same thing. Linux treats the CR as part of the executable name, so it's searching for a binary that (probably) doesn't exist.
            – Zenexer
            Mar 3 at 2:35










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          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: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2faskubuntu.com%2fquestions%2f1001795%2funable-to-execute-new-pre-installation-script-var-lib-dpkg-tmp-ci-preinst%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote













          You're missing the executable that appears in the preinst script's shebang line.



          1. Extract the package metadata to a temporary directory: dpkg -e wtbuild.deb tmp

          2. Open tmp/preinst in a text editor.

          3. The first line should begin with the characters #!. The text that appears after that is the program that will be used to run the file. You're missing that program.

          4. Determine the package that provides the missing program. For example, if the program is /usr/bin/python, you should install the python package: sudo apt-get install python

          If you maintain wtbuild.deb, you should take the time to add the missing dependency to the package's control file. If someone else maintains wtbuild.deb, you should file a bug report and include the name of the missing dependency package.






          share|improve this answer
















          • 1




            Thanks @Zenexer. This pointed me in the right direction. My shebang was off but not because the file didn't exist but because I had CrLf line endings instead of Lf.
            – N Jones
            Mar 2 at 22:16










          • @NJones That's effectively the same thing. Linux treats the CR as part of the executable name, so it's searching for a binary that (probably) doesn't exist.
            – Zenexer
            Mar 3 at 2:35














          up vote
          1
          down vote













          You're missing the executable that appears in the preinst script's shebang line.



          1. Extract the package metadata to a temporary directory: dpkg -e wtbuild.deb tmp

          2. Open tmp/preinst in a text editor.

          3. The first line should begin with the characters #!. The text that appears after that is the program that will be used to run the file. You're missing that program.

          4. Determine the package that provides the missing program. For example, if the program is /usr/bin/python, you should install the python package: sudo apt-get install python

          If you maintain wtbuild.deb, you should take the time to add the missing dependency to the package's control file. If someone else maintains wtbuild.deb, you should file a bug report and include the name of the missing dependency package.






          share|improve this answer
















          • 1




            Thanks @Zenexer. This pointed me in the right direction. My shebang was off but not because the file didn't exist but because I had CrLf line endings instead of Lf.
            – N Jones
            Mar 2 at 22:16










          • @NJones That's effectively the same thing. Linux treats the CR as part of the executable name, so it's searching for a binary that (probably) doesn't exist.
            – Zenexer
            Mar 3 at 2:35












          up vote
          1
          down vote










          up vote
          1
          down vote









          You're missing the executable that appears in the preinst script's shebang line.



          1. Extract the package metadata to a temporary directory: dpkg -e wtbuild.deb tmp

          2. Open tmp/preinst in a text editor.

          3. The first line should begin with the characters #!. The text that appears after that is the program that will be used to run the file. You're missing that program.

          4. Determine the package that provides the missing program. For example, if the program is /usr/bin/python, you should install the python package: sudo apt-get install python

          If you maintain wtbuild.deb, you should take the time to add the missing dependency to the package's control file. If someone else maintains wtbuild.deb, you should file a bug report and include the name of the missing dependency package.






          share|improve this answer












          You're missing the executable that appears in the preinst script's shebang line.



          1. Extract the package metadata to a temporary directory: dpkg -e wtbuild.deb tmp

          2. Open tmp/preinst in a text editor.

          3. The first line should begin with the characters #!. The text that appears after that is the program that will be used to run the file. You're missing that program.

          4. Determine the package that provides the missing program. For example, if the program is /usr/bin/python, you should install the python package: sudo apt-get install python

          If you maintain wtbuild.deb, you should take the time to add the missing dependency to the package's control file. If someone else maintains wtbuild.deb, you should file a bug report and include the name of the missing dependency package.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 7 at 21:29









          Zenexer

          567615




          567615







          • 1




            Thanks @Zenexer. This pointed me in the right direction. My shebang was off but not because the file didn't exist but because I had CrLf line endings instead of Lf.
            – N Jones
            Mar 2 at 22:16










          • @NJones That's effectively the same thing. Linux treats the CR as part of the executable name, so it's searching for a binary that (probably) doesn't exist.
            – Zenexer
            Mar 3 at 2:35












          • 1




            Thanks @Zenexer. This pointed me in the right direction. My shebang was off but not because the file didn't exist but because I had CrLf line endings instead of Lf.
            – N Jones
            Mar 2 at 22:16










          • @NJones That's effectively the same thing. Linux treats the CR as part of the executable name, so it's searching for a binary that (probably) doesn't exist.
            – Zenexer
            Mar 3 at 2:35







          1




          1




          Thanks @Zenexer. This pointed me in the right direction. My shebang was off but not because the file didn't exist but because I had CrLf line endings instead of Lf.
          – N Jones
          Mar 2 at 22:16




          Thanks @Zenexer. This pointed me in the right direction. My shebang was off but not because the file didn't exist but because I had CrLf line endings instead of Lf.
          – N Jones
          Mar 2 at 22:16












          @NJones That's effectively the same thing. Linux treats the CR as part of the executable name, so it's searching for a binary that (probably) doesn't exist.
          – Zenexer
          Mar 3 at 2:35




          @NJones That's effectively the same thing. Linux treats the CR as part of the executable name, so it's searching for a binary that (probably) doesn't exist.
          – Zenexer
          Mar 3 at 2:35

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1001795%2funable-to-execute-new-pre-installation-script-var-lib-dpkg-tmp-ci-preinst%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491