tlmgr thinks local repo is 2017, but was installed from TeXLive 2018 Announcing the arrival of...

Using et al. for a last / senior author rather than for a first author

List *all* the tuples!

Is a manifold-with-boundary with given interior and non-empty boundary essentially unique?

Bonus calculation: Am I making a mountain out of a molehill?

Is it true that "carbohydrates are of no use for the basal metabolic need"?

Best practices for giving outside developer SSH access?

What LEGO pieces have "real-world" functionality?

Letter Boxed validator

What are the motives behind Cersei's orders given to Bronn?

Why don't the Weasley twins use magic outside of school if the Trace can only find the location of spells cast?

Did Xerox really develop the first LAN?

What happens to sewage if there is no river near by?

How do I determine if the rules for a long jump or high jump are applicable for Monks?

Is high blood pressure ever a symptom attributable solely to dehydration?

How discoverable are IPv6 addresses and AAAA names by potential attackers?

What is the longest distance a 13th-level monk can jump while attacking on the same turn?

What is this single-engine low-wing propeller plane?

How much radiation do nuclear physics experiments expose researchers to nowadays?

Examples of mediopassive verb constructions

If a contract sometimes uses the wrong name, is it still valid?

How widely used is the term Treppenwitz? Is it something that most Germans know?

When to stop saving and start investing?

Why did the IBM 650 use bi-quinary?

Can a non-EU citizen traveling with me come with me through the EU passport line?



tlmgr thinks local repo is 2017, but was installed from TeXLive 2018



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 remove everything related to TeX Live for fresh install on Ubuntu?In TexLive 2009, 'tlmgr' tells me there are 'no updates available' for months now. Really?(k)ubuntu, TeXLive manually installed, tlmgr not workingHaving a problem with TexLive Manager - tlmgr version conflict 2013Lyx/Tex installation problems on Linux Mint 17Trouble tlmgr Ubuntu 16.04 and TexLivetlmgr gui claims bizarre TeXLive dist #, cl updates finecompressed data corruption with tlmgr (TeXlive 2018)`tlmgr: Remote repository is newer than local (2017 < 2018)` but I just did a fresh install?Just installed texlive-full and it is outdatedtlmgr: Remote repository is newer than local (2017 < 2018), No it is not












2















I am trying to get LaTeX working on a fresh Ubuntu 18.04 installation. When I install texlive using apt-get, I get an extremely minimal (and insufficient) set of packages (not even Tikz!). Trying to install texlive-full brings up a bunch of errors about not being able to connect to certain repos, so I also gave up on that.



I have now installed TeXLive 2018 from TeXLive's website, as I understand this is the recommended way to install it for Ubuntu. However this installation still does not contain all the packages I need. I have tried installing the package texliveonfly using tlmgr to get the packages I need, and (after already fixing some errors), I get the following message:



tlmgr: Remote repository is newer than local (2017 < 2018)



How can this even be the case, when I installed TeXLive 2018, and now how can I fix this? Any help would be greatly appreciated, as I've been bashing my head against getting LaTeX working for half a week now.










share|improve this question














bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 2





    you presumably have not set your PATH so that texlive2018 is ahead of the system tex. what does type tlmgr report ? (or which tlmgr if you prefer)

    – David Carlisle
    Aug 6 '18 at 14:24











  • @DavidCarlisle This adds a lot of clarity to why what I was doing didn't work, and although it didn't work because I was new to Linux and didn't understand anything about PATHs (I was typing the commands to add to PATH into the terminal rather than editing .profile, and so it was obviously not saved when I restarted the shell), the error I was getting really threw me off the track.

    – Notso
    Sep 4 '18 at 9:02
















2















I am trying to get LaTeX working on a fresh Ubuntu 18.04 installation. When I install texlive using apt-get, I get an extremely minimal (and insufficient) set of packages (not even Tikz!). Trying to install texlive-full brings up a bunch of errors about not being able to connect to certain repos, so I also gave up on that.



I have now installed TeXLive 2018 from TeXLive's website, as I understand this is the recommended way to install it for Ubuntu. However this installation still does not contain all the packages I need. I have tried installing the package texliveonfly using tlmgr to get the packages I need, and (after already fixing some errors), I get the following message:



tlmgr: Remote repository is newer than local (2017 < 2018)



How can this even be the case, when I installed TeXLive 2018, and now how can I fix this? Any help would be greatly appreciated, as I've been bashing my head against getting LaTeX working for half a week now.










share|improve this question














bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 2





    you presumably have not set your PATH so that texlive2018 is ahead of the system tex. what does type tlmgr report ? (or which tlmgr if you prefer)

    – David Carlisle
    Aug 6 '18 at 14:24











  • @DavidCarlisle This adds a lot of clarity to why what I was doing didn't work, and although it didn't work because I was new to Linux and didn't understand anything about PATHs (I was typing the commands to add to PATH into the terminal rather than editing .profile, and so it was obviously not saved when I restarted the shell), the error I was getting really threw me off the track.

    – Notso
    Sep 4 '18 at 9:02














2












2








2








I am trying to get LaTeX working on a fresh Ubuntu 18.04 installation. When I install texlive using apt-get, I get an extremely minimal (and insufficient) set of packages (not even Tikz!). Trying to install texlive-full brings up a bunch of errors about not being able to connect to certain repos, so I also gave up on that.



I have now installed TeXLive 2018 from TeXLive's website, as I understand this is the recommended way to install it for Ubuntu. However this installation still does not contain all the packages I need. I have tried installing the package texliveonfly using tlmgr to get the packages I need, and (after already fixing some errors), I get the following message:



tlmgr: Remote repository is newer than local (2017 < 2018)



How can this even be the case, when I installed TeXLive 2018, and now how can I fix this? Any help would be greatly appreciated, as I've been bashing my head against getting LaTeX working for half a week now.










share|improve this question














I am trying to get LaTeX working on a fresh Ubuntu 18.04 installation. When I install texlive using apt-get, I get an extremely minimal (and insufficient) set of packages (not even Tikz!). Trying to install texlive-full brings up a bunch of errors about not being able to connect to certain repos, so I also gave up on that.



I have now installed TeXLive 2018 from TeXLive's website, as I understand this is the recommended way to install it for Ubuntu. However this installation still does not contain all the packages I need. I have tried installing the package texliveonfly using tlmgr to get the packages I need, and (after already fixing some errors), I get the following message:



tlmgr: Remote repository is newer than local (2017 < 2018)



How can this even be the case, when I installed TeXLive 2018, and now how can I fix this? Any help would be greatly appreciated, as I've been bashing my head against getting LaTeX working for half a week now.







texlive tlmgr






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 6 '18 at 13:51









NotsoNotso

1112




1112





bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 2 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 2





    you presumably have not set your PATH so that texlive2018 is ahead of the system tex. what does type tlmgr report ? (or which tlmgr if you prefer)

    – David Carlisle
    Aug 6 '18 at 14:24











  • @DavidCarlisle This adds a lot of clarity to why what I was doing didn't work, and although it didn't work because I was new to Linux and didn't understand anything about PATHs (I was typing the commands to add to PATH into the terminal rather than editing .profile, and so it was obviously not saved when I restarted the shell), the error I was getting really threw me off the track.

    – Notso
    Sep 4 '18 at 9:02














  • 2





    you presumably have not set your PATH so that texlive2018 is ahead of the system tex. what does type tlmgr report ? (or which tlmgr if you prefer)

    – David Carlisle
    Aug 6 '18 at 14:24











  • @DavidCarlisle This adds a lot of clarity to why what I was doing didn't work, and although it didn't work because I was new to Linux and didn't understand anything about PATHs (I was typing the commands to add to PATH into the terminal rather than editing .profile, and so it was obviously not saved when I restarted the shell), the error I was getting really threw me off the track.

    – Notso
    Sep 4 '18 at 9:02








2




2





you presumably have not set your PATH so that texlive2018 is ahead of the system tex. what does type tlmgr report ? (or which tlmgr if you prefer)

– David Carlisle
Aug 6 '18 at 14:24





you presumably have not set your PATH so that texlive2018 is ahead of the system tex. what does type tlmgr report ? (or which tlmgr if you prefer)

– David Carlisle
Aug 6 '18 at 14:24













@DavidCarlisle This adds a lot of clarity to why what I was doing didn't work, and although it didn't work because I was new to Linux and didn't understand anything about PATHs (I was typing the commands to add to PATH into the terminal rather than editing .profile, and so it was obviously not saved when I restarted the shell), the error I was getting really threw me off the track.

– Notso
Sep 4 '18 at 9:02





@DavidCarlisle This adds a lot of clarity to why what I was doing didn't work, and although it didn't work because I was new to Linux and didn't understand anything about PATHs (I was typing the commands to add to PATH into the terminal rather than editing .profile, and so it was obviously not saved when I restarted the shell), the error I was getting really threw me off the track.

– Notso
Sep 4 '18 at 9:02










1 Answer
1






active

oldest

votes


















0














Apparently Ubuntu 18.04 default installation comes with a few packages that conflicts with texlive from tug.org.



To do a proper latex full installation, after I installed Ubuntu desktop 18.04 I had first to remove any latex related packages from my machine and only after that a clean install using install-tl worked fine.



Don't forget to add the correct paths to your .bashrc after the installation:



# Texlive
export MANPATH="${MANPATH}:/usr/local/texlive/2018/texmf-dist/doc/man"
export INFOPATH="${INFOPATH}:/usr/local/texlive/2018/texmf-dist/doc/info"
export PATH="${PATH}:/usr/local/texlive/2018/bin/x86_64-linux"





share|improve this answer



















  • 4





    For future visitors: remember, it is not a good idea to just set the PATH change in .bashrc , because, if you start your editor through a menu, double clicking a file or a short cut, nothing bashy is ever executed, and thus bashrc is never executed and thus your editor cannot find the new latex and might pick up a system installed latex (the wrong latex). This is a big problem as the bashrc thing is mentioned so many times. Proper way: add the PATH change to .profile, log out and in again. Now the PATH change is attached to the main process and can be seen by all new processes

    – daleif
    Aug 19 '18 at 7:21












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%2f444836%2ftlmgr-thinks-local-repo-is-2017-but-was-installed-from-texlive-2018%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Apparently Ubuntu 18.04 default installation comes with a few packages that conflicts with texlive from tug.org.



To do a proper latex full installation, after I installed Ubuntu desktop 18.04 I had first to remove any latex related packages from my machine and only after that a clean install using install-tl worked fine.



Don't forget to add the correct paths to your .bashrc after the installation:



# Texlive
export MANPATH="${MANPATH}:/usr/local/texlive/2018/texmf-dist/doc/man"
export INFOPATH="${INFOPATH}:/usr/local/texlive/2018/texmf-dist/doc/info"
export PATH="${PATH}:/usr/local/texlive/2018/bin/x86_64-linux"





share|improve this answer



















  • 4





    For future visitors: remember, it is not a good idea to just set the PATH change in .bashrc , because, if you start your editor through a menu, double clicking a file or a short cut, nothing bashy is ever executed, and thus bashrc is never executed and thus your editor cannot find the new latex and might pick up a system installed latex (the wrong latex). This is a big problem as the bashrc thing is mentioned so many times. Proper way: add the PATH change to .profile, log out and in again. Now the PATH change is attached to the main process and can be seen by all new processes

    – daleif
    Aug 19 '18 at 7:21
















0














Apparently Ubuntu 18.04 default installation comes with a few packages that conflicts with texlive from tug.org.



To do a proper latex full installation, after I installed Ubuntu desktop 18.04 I had first to remove any latex related packages from my machine and only after that a clean install using install-tl worked fine.



Don't forget to add the correct paths to your .bashrc after the installation:



# Texlive
export MANPATH="${MANPATH}:/usr/local/texlive/2018/texmf-dist/doc/man"
export INFOPATH="${INFOPATH}:/usr/local/texlive/2018/texmf-dist/doc/info"
export PATH="${PATH}:/usr/local/texlive/2018/bin/x86_64-linux"





share|improve this answer



















  • 4





    For future visitors: remember, it is not a good idea to just set the PATH change in .bashrc , because, if you start your editor through a menu, double clicking a file or a short cut, nothing bashy is ever executed, and thus bashrc is never executed and thus your editor cannot find the new latex and might pick up a system installed latex (the wrong latex). This is a big problem as the bashrc thing is mentioned so many times. Proper way: add the PATH change to .profile, log out and in again. Now the PATH change is attached to the main process and can be seen by all new processes

    – daleif
    Aug 19 '18 at 7:21














0












0








0







Apparently Ubuntu 18.04 default installation comes with a few packages that conflicts with texlive from tug.org.



To do a proper latex full installation, after I installed Ubuntu desktop 18.04 I had first to remove any latex related packages from my machine and only after that a clean install using install-tl worked fine.



Don't forget to add the correct paths to your .bashrc after the installation:



# Texlive
export MANPATH="${MANPATH}:/usr/local/texlive/2018/texmf-dist/doc/man"
export INFOPATH="${INFOPATH}:/usr/local/texlive/2018/texmf-dist/doc/info"
export PATH="${PATH}:/usr/local/texlive/2018/bin/x86_64-linux"





share|improve this answer













Apparently Ubuntu 18.04 default installation comes with a few packages that conflicts with texlive from tug.org.



To do a proper latex full installation, after I installed Ubuntu desktop 18.04 I had first to remove any latex related packages from my machine and only after that a clean install using install-tl worked fine.



Don't forget to add the correct paths to your .bashrc after the installation:



# Texlive
export MANPATH="${MANPATH}:/usr/local/texlive/2018/texmf-dist/doc/man"
export INFOPATH="${INFOPATH}:/usr/local/texlive/2018/texmf-dist/doc/info"
export PATH="${PATH}:/usr/local/texlive/2018/bin/x86_64-linux"






share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 18 '18 at 21:50









J. BarrosJ. Barros

1




1








  • 4





    For future visitors: remember, it is not a good idea to just set the PATH change in .bashrc , because, if you start your editor through a menu, double clicking a file or a short cut, nothing bashy is ever executed, and thus bashrc is never executed and thus your editor cannot find the new latex and might pick up a system installed latex (the wrong latex). This is a big problem as the bashrc thing is mentioned so many times. Proper way: add the PATH change to .profile, log out and in again. Now the PATH change is attached to the main process and can be seen by all new processes

    – daleif
    Aug 19 '18 at 7:21














  • 4





    For future visitors: remember, it is not a good idea to just set the PATH change in .bashrc , because, if you start your editor through a menu, double clicking a file or a short cut, nothing bashy is ever executed, and thus bashrc is never executed and thus your editor cannot find the new latex and might pick up a system installed latex (the wrong latex). This is a big problem as the bashrc thing is mentioned so many times. Proper way: add the PATH change to .profile, log out and in again. Now the PATH change is attached to the main process and can be seen by all new processes

    – daleif
    Aug 19 '18 at 7:21








4




4





For future visitors: remember, it is not a good idea to just set the PATH change in .bashrc , because, if you start your editor through a menu, double clicking a file or a short cut, nothing bashy is ever executed, and thus bashrc is never executed and thus your editor cannot find the new latex and might pick up a system installed latex (the wrong latex). This is a big problem as the bashrc thing is mentioned so many times. Proper way: add the PATH change to .profile, log out and in again. Now the PATH change is attached to the main process and can be seen by all new processes

– daleif
Aug 19 '18 at 7:21





For future visitors: remember, it is not a good idea to just set the PATH change in .bashrc , because, if you start your editor through a menu, double clicking a file or a short cut, nothing bashy is ever executed, and thus bashrc is never executed and thus your editor cannot find the new latex and might pick up a system installed latex (the wrong latex). This is a big problem as the bashrc thing is mentioned so many times. Proper way: add the PATH change to .profile, log out and in again. Now the PATH change is attached to the main process and can be seen by all new processes

– daleif
Aug 19 '18 at 7:21


















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%2f444836%2ftlmgr-thinks-local-repo-is-2017-but-was-installed-from-texlive-2018%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

El tren de la libertad Índice Antecedentes "Porque yo decido" Desarrollo de la...

Castillo d'Acher Características Menú de navegación

Connecting two nodes from the same mother node horizontallyTikZ: What EXACTLY does the the |- notation for...