Permission problem when installing package from tlmgr The 2019 Stack Overflow Developer Survey...

system() function string length limit

Would an alien lifeform be able to achieve space travel if lacking in vision?

How did passengers keep warm on sail ships?

When did F become S in typeography, and why?

Why did all the guest students take carriages to the Yule Ball?

Can the prologue be the backstory of your main character?

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?

How are presidential pardons supposed to be used?

What are these Gizmos at Izaña Atmospheric Research Center in Spain?

How does this infinite series simplify to an integral?

Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?

He got a vote 80% that of Emmanuel Macron’s

Simulating Exploding Dice

How to pronounce 1ターン?

Sort list of array linked objects by keys and values

Make it rain characters

Who or what is the being for whom Being is a question for Heidegger?

Do warforged have souls?

Can smartphones with the same camera sensor have different image quality?

Does Parliament hold absolute power in the UK?

Problems with Ubuntu mount /tmp

Difference between "generating set" and free product?

Windows 10: How to Lock (not sleep) laptop on lid close?

What do you call a plan that's an alternative plan in case your initial plan fails?



Permission problem when installing package from tlmgr



The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How to configure kile to run texlive 2011?How to install latex packages in kile under UbuntuTroubles in installing packageMissing tlmgr texlive 2012Problem Installing TeX Live under Windows 8 Resistant to Past FixesHow to add new fonts to MacTeX 2013Two Latex installations on the same ubuntu systemHaving a problem with TexLive Manager - tlmgr version conflict 2013TeX Live Manager Update setup on LinuxCan not install xzdec by tlmgr












5















I migrated from MiKTeX on windows to TeXLive in ubuntu. At first I installed texlive-full from ubuntu repositories but I realized that I wanted to install more packages which isn't very convenient when there is no tlmgr.



So I decided to removeTeXLive and reinstall it from TUG. The installation had no problems. Then I added the following lines to bashrc



export PATH=$PATH:/usr/local/texlive/2014/bin/i386-linux
export PATH=$PATH:/usr/local/texlive/2014/tlpkg/


and then I run a simple document and it seemed to be working. I tried to install a package(i.e. units) through tlmgr but I don't have permission to write to a specific directory. What I did was to use sudo privilleges but again no luck. My effort is the following



thanos@thanos-laptop:~$ tlmgr install units
You don't have permission to change the installation in any way,
specifically, the directory /usr/local/texlive/2014/tlpkg/ is not writable.
Please run this program as administrator, or contact your local admin.
thanos@thanos-laptop:~$ sudo tlmgr install units
[sudo] password for thanos:
sudo: tlmgr: command not found


I also tried through the relevant tlmgr's gui but I get the same message as above.



What can I do to install packages through tlmgr?










share|improve this question























  • If you do sudo su and then tlmgr .... should work. But be careful with commands as root.

    – Sigur
    Jun 28 '14 at 14:39











  • You don't need to add /usr/local/texlive/2014/tlpkg/ to PATH. You should add /usr/local/texlive/2014/bin/i386-linux at the beginning of PATH rather than the end.

    – cfr
    Jun 28 '14 at 15:03
















5















I migrated from MiKTeX on windows to TeXLive in ubuntu. At first I installed texlive-full from ubuntu repositories but I realized that I wanted to install more packages which isn't very convenient when there is no tlmgr.



So I decided to removeTeXLive and reinstall it from TUG. The installation had no problems. Then I added the following lines to bashrc



export PATH=$PATH:/usr/local/texlive/2014/bin/i386-linux
export PATH=$PATH:/usr/local/texlive/2014/tlpkg/


and then I run a simple document and it seemed to be working. I tried to install a package(i.e. units) through tlmgr but I don't have permission to write to a specific directory. What I did was to use sudo privilleges but again no luck. My effort is the following



thanos@thanos-laptop:~$ tlmgr install units
You don't have permission to change the installation in any way,
specifically, the directory /usr/local/texlive/2014/tlpkg/ is not writable.
Please run this program as administrator, or contact your local admin.
thanos@thanos-laptop:~$ sudo tlmgr install units
[sudo] password for thanos:
sudo: tlmgr: command not found


I also tried through the relevant tlmgr's gui but I get the same message as above.



What can I do to install packages through tlmgr?










share|improve this question























  • If you do sudo su and then tlmgr .... should work. But be careful with commands as root.

    – Sigur
    Jun 28 '14 at 14:39











  • You don't need to add /usr/local/texlive/2014/tlpkg/ to PATH. You should add /usr/local/texlive/2014/bin/i386-linux at the beginning of PATH rather than the end.

    – cfr
    Jun 28 '14 at 15:03














5












5








5


1






I migrated from MiKTeX on windows to TeXLive in ubuntu. At first I installed texlive-full from ubuntu repositories but I realized that I wanted to install more packages which isn't very convenient when there is no tlmgr.



So I decided to removeTeXLive and reinstall it from TUG. The installation had no problems. Then I added the following lines to bashrc



export PATH=$PATH:/usr/local/texlive/2014/bin/i386-linux
export PATH=$PATH:/usr/local/texlive/2014/tlpkg/


and then I run a simple document and it seemed to be working. I tried to install a package(i.e. units) through tlmgr but I don't have permission to write to a specific directory. What I did was to use sudo privilleges but again no luck. My effort is the following



thanos@thanos-laptop:~$ tlmgr install units
You don't have permission to change the installation in any way,
specifically, the directory /usr/local/texlive/2014/tlpkg/ is not writable.
Please run this program as administrator, or contact your local admin.
thanos@thanos-laptop:~$ sudo tlmgr install units
[sudo] password for thanos:
sudo: tlmgr: command not found


I also tried through the relevant tlmgr's gui but I get the same message as above.



What can I do to install packages through tlmgr?










share|improve this question














I migrated from MiKTeX on windows to TeXLive in ubuntu. At first I installed texlive-full from ubuntu repositories but I realized that I wanted to install more packages which isn't very convenient when there is no tlmgr.



So I decided to removeTeXLive and reinstall it from TUG. The installation had no problems. Then I added the following lines to bashrc



export PATH=$PATH:/usr/local/texlive/2014/bin/i386-linux
export PATH=$PATH:/usr/local/texlive/2014/tlpkg/


and then I run a simple document and it seemed to be working. I tried to install a package(i.e. units) through tlmgr but I don't have permission to write to a specific directory. What I did was to use sudo privilleges but again no luck. My effort is the following



thanos@thanos-laptop:~$ tlmgr install units
You don't have permission to change the installation in any way,
specifically, the directory /usr/local/texlive/2014/tlpkg/ is not writable.
Please run this program as administrator, or contact your local admin.
thanos@thanos-laptop:~$ sudo tlmgr install units
[sudo] password for thanos:
sudo: tlmgr: command not found


I also tried through the relevant tlmgr's gui but I get the same message as above.



What can I do to install packages through tlmgr?







packages texlive






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jun 28 '14 at 14:11









ThanosThanos

6,1561555107




6,1561555107













  • If you do sudo su and then tlmgr .... should work. But be careful with commands as root.

    – Sigur
    Jun 28 '14 at 14:39











  • You don't need to add /usr/local/texlive/2014/tlpkg/ to PATH. You should add /usr/local/texlive/2014/bin/i386-linux at the beginning of PATH rather than the end.

    – cfr
    Jun 28 '14 at 15:03



















  • If you do sudo su and then tlmgr .... should work. But be careful with commands as root.

    – Sigur
    Jun 28 '14 at 14:39











  • You don't need to add /usr/local/texlive/2014/tlpkg/ to PATH. You should add /usr/local/texlive/2014/bin/i386-linux at the beginning of PATH rather than the end.

    – cfr
    Jun 28 '14 at 15:03

















If you do sudo su and then tlmgr .... should work. But be careful with commands as root.

– Sigur
Jun 28 '14 at 14:39





If you do sudo su and then tlmgr .... should work. But be careful with commands as root.

– Sigur
Jun 28 '14 at 14:39













You don't need to add /usr/local/texlive/2014/tlpkg/ to PATH. You should add /usr/local/texlive/2014/bin/i386-linux at the beginning of PATH rather than the end.

– cfr
Jun 28 '14 at 15:03





You don't need to add /usr/local/texlive/2014/tlpkg/ to PATH. You should add /usr/local/texlive/2014/bin/i386-linux at the beginning of PATH rather than the end.

– cfr
Jun 28 '14 at 15:03










3 Answers
3






active

oldest

votes


















2














What I did was to let sudo know about the modification of the $PATH variable. This was done typing the following command on terminal



sudo env PATH="$PATH" tlmgr


In this way, I somehow enabled sudo in tlmgr. After that packages can be installed using



sudo tlmgr install package





share|improve this answer































    2














    In case anyone else tried previous suggestions and they didn't work, this worked for me:



    sudo /usr/local/texlive/2015/bin/x86_64-linux/tlmgr ...





    share|improve this answer
























    • Using the which construction in back quotes can be of help too. For example: sudo `which tlmgr` gui (it is rendered not the proper way, but one can get the idea, I hope)

      – Leonid
      Jan 6 at 10:39





















    0














    Thanos' answer basically works, but the description of multiple commands is misleading.



    All root actions will need to be explicitly paired with the env modification.

    By design, the environmental variables for the root user are reset every time it is invoked. If you subsequently try to execute a regular sudo command, the PATH variable will have already been reset. This holds even in a sudo su environment. So for instance, if you wanted to use the --dry-run option to preview installing a package named package, the following would NOT work:



     sudo env PATH="$PATH" tlmgr install package --dry-run

    sudo tlmgr install package


    Instead, you have to fix the PATH variable every time, like this:



     sudo env PATH="$PATH" tlmgr install package --dry-run

    sudo env PATH="$PATH" tlmgr install package


    The underlying problem is that a standard TeX Live installation places the binaries in a non-standard directory, so the set of PATH locations that root is designed to recognize does not include anything that came with TeX Live. By design, you are not supposed to be able to permanently modify root's PATH variable, so any task that needs privilege elevation becomes tricky.



    Approaches to fixing this issue more permanently are described on the Ubuntu forums. Doing so is more involved, and I haven't tried it myself.





    share








    New contributor




    Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "85"
      };
      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',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f187073%2fpermission-problem-when-installing-package-from-tlmgr%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      What I did was to let sudo know about the modification of the $PATH variable. This was done typing the following command on terminal



      sudo env PATH="$PATH" tlmgr


      In this way, I somehow enabled sudo in tlmgr. After that packages can be installed using



      sudo tlmgr install package





      share|improve this answer




























        2














        What I did was to let sudo know about the modification of the $PATH variable. This was done typing the following command on terminal



        sudo env PATH="$PATH" tlmgr


        In this way, I somehow enabled sudo in tlmgr. After that packages can be installed using



        sudo tlmgr install package





        share|improve this answer


























          2












          2








          2







          What I did was to let sudo know about the modification of the $PATH variable. This was done typing the following command on terminal



          sudo env PATH="$PATH" tlmgr


          In this way, I somehow enabled sudo in tlmgr. After that packages can be installed using



          sudo tlmgr install package





          share|improve this answer













          What I did was to let sudo know about the modification of the $PATH variable. This was done typing the following command on terminal



          sudo env PATH="$PATH" tlmgr


          In this way, I somehow enabled sudo in tlmgr. After that packages can be installed using



          sudo tlmgr install package






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jun 29 '14 at 15:10









          ThanosThanos

          6,1561555107




          6,1561555107























              2














              In case anyone else tried previous suggestions and they didn't work, this worked for me:



              sudo /usr/local/texlive/2015/bin/x86_64-linux/tlmgr ...





              share|improve this answer
























              • Using the which construction in back quotes can be of help too. For example: sudo `which tlmgr` gui (it is rendered not the proper way, but one can get the idea, I hope)

                – Leonid
                Jan 6 at 10:39


















              2














              In case anyone else tried previous suggestions and they didn't work, this worked for me:



              sudo /usr/local/texlive/2015/bin/x86_64-linux/tlmgr ...





              share|improve this answer
























              • Using the which construction in back quotes can be of help too. For example: sudo `which tlmgr` gui (it is rendered not the proper way, but one can get the idea, I hope)

                – Leonid
                Jan 6 at 10:39
















              2












              2








              2







              In case anyone else tried previous suggestions and they didn't work, this worked for me:



              sudo /usr/local/texlive/2015/bin/x86_64-linux/tlmgr ...





              share|improve this answer













              In case anyone else tried previous suggestions and they didn't work, this worked for me:



              sudo /usr/local/texlive/2015/bin/x86_64-linux/tlmgr ...






              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jan 12 '16 at 19:36









              JordanJordan

              1384




              1384













              • Using the which construction in back quotes can be of help too. For example: sudo `which tlmgr` gui (it is rendered not the proper way, but one can get the idea, I hope)

                – Leonid
                Jan 6 at 10:39





















              • Using the which construction in back quotes can be of help too. For example: sudo `which tlmgr` gui (it is rendered not the proper way, but one can get the idea, I hope)

                – Leonid
                Jan 6 at 10:39



















              Using the which construction in back quotes can be of help too. For example: sudo `which tlmgr` gui (it is rendered not the proper way, but one can get the idea, I hope)

              – Leonid
              Jan 6 at 10:39







              Using the which construction in back quotes can be of help too. For example: sudo `which tlmgr` gui (it is rendered not the proper way, but one can get the idea, I hope)

              – Leonid
              Jan 6 at 10:39













              0














              Thanos' answer basically works, but the description of multiple commands is misleading.



              All root actions will need to be explicitly paired with the env modification.

              By design, the environmental variables for the root user are reset every time it is invoked. If you subsequently try to execute a regular sudo command, the PATH variable will have already been reset. This holds even in a sudo su environment. So for instance, if you wanted to use the --dry-run option to preview installing a package named package, the following would NOT work:



               sudo env PATH="$PATH" tlmgr install package --dry-run

              sudo tlmgr install package


              Instead, you have to fix the PATH variable every time, like this:



               sudo env PATH="$PATH" tlmgr install package --dry-run

              sudo env PATH="$PATH" tlmgr install package


              The underlying problem is that a standard TeX Live installation places the binaries in a non-standard directory, so the set of PATH locations that root is designed to recognize does not include anything that came with TeX Live. By design, you are not supposed to be able to permanently modify root's PATH variable, so any task that needs privilege elevation becomes tricky.



              Approaches to fixing this issue more permanently are described on the Ubuntu forums. Doing so is more involved, and I haven't tried it myself.





              share








              New contributor




              Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                0














                Thanos' answer basically works, but the description of multiple commands is misleading.



                All root actions will need to be explicitly paired with the env modification.

                By design, the environmental variables for the root user are reset every time it is invoked. If you subsequently try to execute a regular sudo command, the PATH variable will have already been reset. This holds even in a sudo su environment. So for instance, if you wanted to use the --dry-run option to preview installing a package named package, the following would NOT work:



                 sudo env PATH="$PATH" tlmgr install package --dry-run

                sudo tlmgr install package


                Instead, you have to fix the PATH variable every time, like this:



                 sudo env PATH="$PATH" tlmgr install package --dry-run

                sudo env PATH="$PATH" tlmgr install package


                The underlying problem is that a standard TeX Live installation places the binaries in a non-standard directory, so the set of PATH locations that root is designed to recognize does not include anything that came with TeX Live. By design, you are not supposed to be able to permanently modify root's PATH variable, so any task that needs privilege elevation becomes tricky.



                Approaches to fixing this issue more permanently are described on the Ubuntu forums. Doing so is more involved, and I haven't tried it myself.





                share








                New contributor




                Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  0












                  0








                  0







                  Thanos' answer basically works, but the description of multiple commands is misleading.



                  All root actions will need to be explicitly paired with the env modification.

                  By design, the environmental variables for the root user are reset every time it is invoked. If you subsequently try to execute a regular sudo command, the PATH variable will have already been reset. This holds even in a sudo su environment. So for instance, if you wanted to use the --dry-run option to preview installing a package named package, the following would NOT work:



                   sudo env PATH="$PATH" tlmgr install package --dry-run

                  sudo tlmgr install package


                  Instead, you have to fix the PATH variable every time, like this:



                   sudo env PATH="$PATH" tlmgr install package --dry-run

                  sudo env PATH="$PATH" tlmgr install package


                  The underlying problem is that a standard TeX Live installation places the binaries in a non-standard directory, so the set of PATH locations that root is designed to recognize does not include anything that came with TeX Live. By design, you are not supposed to be able to permanently modify root's PATH variable, so any task that needs privilege elevation becomes tricky.



                  Approaches to fixing this issue more permanently are described on the Ubuntu forums. Doing so is more involved, and I haven't tried it myself.





                  share








                  New contributor




                  Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  Thanos' answer basically works, but the description of multiple commands is misleading.



                  All root actions will need to be explicitly paired with the env modification.

                  By design, the environmental variables for the root user are reset every time it is invoked. If you subsequently try to execute a regular sudo command, the PATH variable will have already been reset. This holds even in a sudo su environment. So for instance, if you wanted to use the --dry-run option to preview installing a package named package, the following would NOT work:



                   sudo env PATH="$PATH" tlmgr install package --dry-run

                  sudo tlmgr install package


                  Instead, you have to fix the PATH variable every time, like this:



                   sudo env PATH="$PATH" tlmgr install package --dry-run

                  sudo env PATH="$PATH" tlmgr install package


                  The underlying problem is that a standard TeX Live installation places the binaries in a non-standard directory, so the set of PATH locations that root is designed to recognize does not include anything that came with TeX Live. By design, you are not supposed to be able to permanently modify root's PATH variable, so any task that needs privilege elevation becomes tricky.



                  Approaches to fixing this issue more permanently are described on the Ubuntu forums. Doing so is more involved, and I haven't tried it myself.






                  share








                  New contributor




                  Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share


                  share






                  New contributor




                  Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 4 mins ago









                  HutchHutch

                  1




                  1




                  New contributor




                  Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Hutch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to TeX - LaTeX 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.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f187073%2fpermission-problem-when-installing-package-from-tlmgr%23new-answer', 'question_page');
                      }
                      );

                      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







                      Popular posts from this blog

                      Paper upload error, “Upload failed: The top margin is 0.715 in on page 3, which is below the required...

                      Emraan Hashmi Filmografia | Linki zewnętrzne | Menu nawigacyjneGulshan GroverGulshan...

                      How can I write this formula?newline and italics added with leqWhy does widehat behave differently if I...