tlmgr: Remote repository is newer than local (2017 < 2018)
up vote
17
down vote
favorite
4
I'm not able to get past this error. I do not wish to do a fresh install of texlive. Why is texlive so frickin annoying? Why does it force me too fresh install? Why can't I just upgrade texlive like any other piece of software? Why can't I just use the older version? Why can't I live in peace?
nikhil@spyder:~/report$ tlmgr install listings
(running on Debian, switching to user mode!)
tlmgr: Remote repository is newer than local (2017 < 2018)
Cross release updates are only supported with
update-tlmgr-latest(.sh/.exe) --update
Please see https://tug.org/texlive/upgrade.html for details.
tlmgr update
asked May 2 at 16:30
nikhilweee
37628
add a comment |
up vote
17
down vote
favorite
4
I'm not able to get past this error. I do not wish to do a fresh install of texlive. Why is texlive so frickin annoying? Why does it force me too fresh install? Why can't I just upgrade texlive like any other piece of software? Why can't I just use the older version? Why can't I live in peace?
nikhil@spyder:~/report$ tlmgr install listings
(running on Debian, switching to user mode!)
tlmgr: Remote repository is newer than local (2017 < 2018)
Cross release updates are only supported with
update-tlmgr-latest(.sh/.exe) --update
Please see https://tug.org/texlive/upgrade.html for details.
tlmgr update
asked May 2 at 16:30
nikhilweee
37628
4
Welcome! As it stands, this is more a rant than a question. What do you want help with? As you probably know, we are not responsible for the design of TeX Live. (Of course, someone who is may answer your question, but if you really want it answered as such, this isn't the best place.) I would say: it is not really TL which is annoying you, but Debian's packaging of TL. Luckily, you can install the packages you need usingaptwithout needing to update your TL installation. If you had an upstream install, you could just keep using the 2017 version. So nothing forces you to update either way.
– cfr
May 2 at 16:38
Package updates might be using new features of TeX Live 2018, for instance.
– egreg
May 2 at 16:39
1
@cfr You are right. This was intended to be a question more than a rant but turned out to be the opposite. I still don't blame myself though. I simply wanted to get rid of this error and install thelistingspackage peacefully. Sorry if that is not evident from the question. Thanks for your insights though. I wasn't aware that I could simply install packages usingapt.
– nikhilweee
May 2 at 17:21
Or, you can switch to MiKTeX, if you prefer a rolling release model. Now MiKTeX is also available for Linux and MacOS and it's no longer a Windows-exclusive TeX distro.
– andselisk
47 mins ago
add a comment |
up vote
17
down vote
favorite
4
up vote
17
down vote
favorite
4
4
I'm not able to get past this error. I do not wish to do a fresh install of texlive. Why is texlive so frickin annoying? Why does it force me too fresh install? Why can't I just upgrade texlive like any other piece of software? Why can't I just use the older version? Why can't I live in peace?
nikhil@spyder:~/report$ tlmgr install listings
(running on Debian, switching to user mode!)
tlmgr: Remote repository is newer than local (2017 < 2018)
Cross release updates are only supported with
update-tlmgr-latest(.sh/.exe) --update
Please see https://tug.org/texlive/upgrade.html for details.
tlmgr update
asked May 2 at 16:30
nikhilweee
37628
I'm not able to get past this error. I do not wish to do a fresh install of texlive. Why is texlive so frickin annoying? Why does it force me too fresh install? Why can't I just upgrade texlive like any other piece of software? Why can't I just use the older version? Why can't I live in peace?
nikhil@spyder:~/report$ tlmgr install listings
(running on Debian, switching to user mode!)
tlmgr: Remote repository is newer than local (2017 < 2018)
Cross release updates are only supported with
update-tlmgr-latest(.sh/.exe) --update
Please see https://tug.org/texlive/upgrade.html for details.
tlmgr update
tlmgr update
asked May 2 at 16:30
nikhilweee
37628
asked May 2 at 16:30
nikhilweee
37628
asked May 2 at 16:30
nikhilweee
37628
asked May 2 at 16:30
nikhilweee
37628
asked May 2 at 16:30
nikhilweee
37628
37628
4
Welcome! As it stands, this is more a rant than a question. What do you want help with? As you probably know, we are not responsible for the design of TeX Live. (Of course, someone who is may answer your question, but if you really want it answered as such, this isn't the best place.) I would say: it is not really TL which is annoying you, but Debian's packaging of TL. Luckily, you can install the packages you need usingaptwithout needing to update your TL installation. If you had an upstream install, you could just keep using the 2017 version. So nothing forces you to update either way.
– cfr
May 2 at 16:38
Package updates might be using new features of TeX Live 2018, for instance.
– egreg
May 2 at 16:39
1
@cfr You are right. This was intended to be a question more than a rant but turned out to be the opposite. I still don't blame myself though. I simply wanted to get rid of this error and install thelistingspackage peacefully. Sorry if that is not evident from the question. Thanks for your insights though. I wasn't aware that I could simply install packages usingapt.
– nikhilweee
May 2 at 17:21
Or, you can switch to MiKTeX, if you prefer a rolling release model. Now MiKTeX is also available for Linux and MacOS and it's no longer a Windows-exclusive TeX distro.
– andselisk
47 mins ago
add a comment |
4
Welcome! As it stands, this is more a rant than a question. What do you want help with? As you probably know, we are not responsible for the design of TeX Live. (Of course, someone who is may answer your question, but if you really want it answered as such, this isn't the best place.) I would say: it is not really TL which is annoying you, but Debian's packaging of TL. Luckily, you can install the packages you need usingaptwithout needing to update your TL installation. If you had an upstream install, you could just keep using the 2017 version. So nothing forces you to update either way.
– cfr
May 2 at 16:38
Package updates might be using new features of TeX Live 2018, for instance.
– egreg
May 2 at 16:39
1
@cfr You are right. This was intended to be a question more than a rant but turned out to be the opposite. I still don't blame myself though. I simply wanted to get rid of this error and install thelistingspackage peacefully. Sorry if that is not evident from the question. Thanks for your insights though. I wasn't aware that I could simply install packages usingapt.
– nikhilweee
May 2 at 17:21
Or, you can switch to MiKTeX, if you prefer a rolling release model. Now MiKTeX is also available for Linux and MacOS and it's no longer a Windows-exclusive TeX distro.
– andselisk
47 mins ago
4
4
Welcome! As it stands, this is more a rant than a question. What do you want help with? As you probably know, we are not responsible for the design of TeX Live. (Of course, someone who is may answer your question, but if you really want it answered as such, this isn't the best place.) I would say: it is not really TL which is annoying you, but Debian's packaging of TL. Luckily, you can install the packages you need using
apt without needing to update your TL installation. If you had an upstream install, you could just keep using the 2017 version. So nothing forces you to update either way.– cfr
May 2 at 16:38
Welcome! As it stands, this is more a rant than a question. What do you want help with? As you probably know, we are not responsible for the design of TeX Live. (Of course, someone who is may answer your question, but if you really want it answered as such, this isn't the best place.) I would say: it is not really TL which is annoying you, but Debian's packaging of TL. Luckily, you can install the packages you need using
apt without needing to update your TL installation. If you had an upstream install, you could just keep using the 2017 version. So nothing forces you to update either way.– cfr
May 2 at 16:38
Package updates might be using new features of TeX Live 2018, for instance.
– egreg
May 2 at 16:39
Package updates might be using new features of TeX Live 2018, for instance.
– egreg
May 2 at 16:39
1
1
@cfr You are right. This was intended to be a question more than a rant but turned out to be the opposite. I still don't blame myself though. I simply wanted to get rid of this error and install the
listings package peacefully. Sorry if that is not evident from the question. Thanks for your insights though. I wasn't aware that I could simply install packages using apt.– nikhilweee
May 2 at 17:21
@cfr You are right. This was intended to be a question more than a rant but turned out to be the opposite. I still don't blame myself though. I simply wanted to get rid of this error and install the
listings package peacefully. Sorry if that is not evident from the question. Thanks for your insights though. I wasn't aware that I could simply install packages using apt.– nikhilweee
May 2 at 17:21
Or, you can switch to MiKTeX, if you prefer a rolling release model. Now MiKTeX is also available for Linux and MacOS and it's no longer a Windows-exclusive TeX distro.
– andselisk
47 mins ago
Or, you can switch to MiKTeX, if you prefer a rolling release model. Now MiKTeX is also available for Linux and MacOS and it's no longer a Windows-exclusive TeX distro.
– andselisk
47 mins ago
add a comment |
3 Answers
3
active
oldest
votes
up vote
19
down vote
accepted
This seems to do the trick. The solution is to downgrade the repository to 2017 version. This seems to be easy enough, but a quick search for the error did not suggest anything of this sort. I hope this post will be useful for people facing the same problem in the future.
sudo tlmgr option repository ftp://tug.org/historic/systems/texlive/2017/tlnet-final
`
answered May 2 at 16:58
nikhilweee
37628
2
this is "staying at tl2017" as I mentioned in my answer. If you had updated with tlmgr before texlive 2018 was released then this will never do anything as thetlnet-finalare just fixed snapshots they will never be updated so you will get no updates via that repository.
– David Carlisle
May 2 at 18:10
1
In addition, unlike a normal ctan mirror that uses a distributed mirrored network to share load around the globe, this is directly hitting TUG's main server, that server is not set up as a global delivery network, and is designed for occasional one-off downloads of the archived systems.
– David Carlisle
May 2 at 20:30
1
Noting the concerns in the above comments, this answer still serves as a great temporary workaround. Thanks!
– cemulate
May 9 at 3:50
I need this workaround every year between the time of the official release and the time I actually get around to upgrading my TL installation.
– corwin.amber
Jul 11 at 8:51
add a comment |
up vote
5
down vote
You don't have to upgrade at all, you can stop at tl2017 (lots of people installed tex years ago and have never updated)
However if you want to update from one texlive to the next without doing a full install (which is the recommended route) then the texlive team have a page detailing what you need to do
https://www.tug.org/texlive/upgrade.html
Note that this URL is exactly the address given in the error message that you quoted in the question.
answered May 2 at 16:39
David Carlisle
479k3811101844
Thank you for your insights. I see thattexlivehas an update mechanism, but it seems that it involves more effort than doing a fresh install altogether. On the other hand, I was looking for a quick fix like the answer below. Sorry If the question wasn't clear though.
– nikhilweee
May 2 at 17:03
@nikhilweee it is commands to type to do an in -place update but the usual reasons for doing it are to save download time by not doewnloading unchanged files and to save disk space by not having both versions installed. If you do not have those requirements then simply installing the new version is of course easier.
– David Carlisle
May 2 at 18:14
1
This won't work: the user's TL is Debian's packaging. An in-place update would require an upstream installation. (At least, it certainly should.) I doubt such an update mechanism is designed to operate in user mode in such cases.
– cfr
May 2 at 21:06
@cfr I did wonder (although most of the question applies to any TL) I thought the debian TL was always updated by the system apt-get, tlmgr also works does it? (if this answer is wrong, the debian packaged tlmgr's error message which gives the same link probably should be changed)
– David Carlisle
May 2 at 21:14
The main tree is updated withapt. But there's a kind of watered-down version oftlmgrwhich users can use to install particular packages themselves.... switching to user mode!is the give away. If this were upstream, it would not say that - either it would go ahead in sys mode or it would complain about permissions. I think the error message is supplied by the repository and not bytlmgr, but I'm not certain. I agree it is messed up, though.
– cfr
May 3 at 3:13
|
show 3 more comments
up vote
0
down vote
I had this issue because although I installed the latest version of TexLive
I didn't setup the PATH right. I would recommend if anyone has this issue to inspect
the PATH variable and run
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
to make sure that the tlmgr of new installation is discovered before any other already in the system.
edited 1 hour ago
Kurt
34.3k846157
answered 1 hour ago
kpsychas
1
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
19
down vote
accepted
This seems to do the trick. The solution is to downgrade the repository to 2017 version. This seems to be easy enough, but a quick search for the error did not suggest anything of this sort. I hope this post will be useful for people facing the same problem in the future.
sudo tlmgr option repository ftp://tug.org/historic/systems/texlive/2017/tlnet-final
`
answered May 2 at 16:58
nikhilweee
37628
2
this is "staying at tl2017" as I mentioned in my answer. If you had updated with tlmgr before texlive 2018 was released then this will never do anything as thetlnet-finalare just fixed snapshots they will never be updated so you will get no updates via that repository.
– David Carlisle
May 2 at 18:10
1
In addition, unlike a normal ctan mirror that uses a distributed mirrored network to share load around the globe, this is directly hitting TUG's main server, that server is not set up as a global delivery network, and is designed for occasional one-off downloads of the archived systems.
– David Carlisle
May 2 at 20:30
1
Noting the concerns in the above comments, this answer still serves as a great temporary workaround. Thanks!
– cemulate
May 9 at 3:50
I need this workaround every year between the time of the official release and the time I actually get around to upgrading my TL installation.
– corwin.amber
Jul 11 at 8:51
add a comment |
up vote
19
down vote
accepted
This seems to do the trick. The solution is to downgrade the repository to 2017 version. This seems to be easy enough, but a quick search for the error did not suggest anything of this sort. I hope this post will be useful for people facing the same problem in the future.
sudo tlmgr option repository ftp://tug.org/historic/systems/texlive/2017/tlnet-final
`
answered May 2 at 16:58
nikhilweee
37628
2
this is "staying at tl2017" as I mentioned in my answer. If you had updated with tlmgr before texlive 2018 was released then this will never do anything as thetlnet-finalare just fixed snapshots they will never be updated so you will get no updates via that repository.
– David Carlisle
May 2 at 18:10
1
In addition, unlike a normal ctan mirror that uses a distributed mirrored network to share load around the globe, this is directly hitting TUG's main server, that server is not set up as a global delivery network, and is designed for occasional one-off downloads of the archived systems.
– David Carlisle
May 2 at 20:30
1
Noting the concerns in the above comments, this answer still serves as a great temporary workaround. Thanks!
– cemulate
May 9 at 3:50
I need this workaround every year between the time of the official release and the time I actually get around to upgrading my TL installation.
– corwin.amber
Jul 11 at 8:51
add a comment |
up vote
19
down vote
accepted
up vote
19
down vote
accepted
This seems to do the trick. The solution is to downgrade the repository to 2017 version. This seems to be easy enough, but a quick search for the error did not suggest anything of this sort. I hope this post will be useful for people facing the same problem in the future.
sudo tlmgr option repository ftp://tug.org/historic/systems/texlive/2017/tlnet-final
`
answered May 2 at 16:58
nikhilweee
37628
This seems to do the trick. The solution is to downgrade the repository to 2017 version. This seems to be easy enough, but a quick search for the error did not suggest anything of this sort. I hope this post will be useful for people facing the same problem in the future.
sudo tlmgr option repository ftp://tug.org/historic/systems/texlive/2017/tlnet-final
`
answered May 2 at 16:58
nikhilweee
37628
answered May 2 at 16:58
nikhilweee
37628
answered May 2 at 16:58
nikhilweee
37628
answered May 2 at 16:58
nikhilweee
37628
37628
2
this is "staying at tl2017" as I mentioned in my answer. If you had updated with tlmgr before texlive 2018 was released then this will never do anything as thetlnet-finalare just fixed snapshots they will never be updated so you will get no updates via that repository.
– David Carlisle
May 2 at 18:10
1
In addition, unlike a normal ctan mirror that uses a distributed mirrored network to share load around the globe, this is directly hitting TUG's main server, that server is not set up as a global delivery network, and is designed for occasional one-off downloads of the archived systems.
– David Carlisle
May 2 at 20:30
1
Noting the concerns in the above comments, this answer still serves as a great temporary workaround. Thanks!
– cemulate
May 9 at 3:50
I need this workaround every year between the time of the official release and the time I actually get around to upgrading my TL installation.
– corwin.amber
Jul 11 at 8:51
add a comment |
2
this is "staying at tl2017" as I mentioned in my answer. If you had updated with tlmgr before texlive 2018 was released then this will never do anything as thetlnet-finalare just fixed snapshots they will never be updated so you will get no updates via that repository.
– David Carlisle
May 2 at 18:10
1
In addition, unlike a normal ctan mirror that uses a distributed mirrored network to share load around the globe, this is directly hitting TUG's main server, that server is not set up as a global delivery network, and is designed for occasional one-off downloads of the archived systems.
– David Carlisle
May 2 at 20:30
1
Noting the concerns in the above comments, this answer still serves as a great temporary workaround. Thanks!
– cemulate
May 9 at 3:50
I need this workaround every year between the time of the official release and the time I actually get around to upgrading my TL installation.
– corwin.amber
Jul 11 at 8:51
2
2
this is "staying at tl2017" as I mentioned in my answer. If you had updated with tlmgr before texlive 2018 was released then this will never do anything as the
tlnet-final are just fixed snapshots they will never be updated so you will get no updates via that repository.– David Carlisle
May 2 at 18:10
this is "staying at tl2017" as I mentioned in my answer. If you had updated with tlmgr before texlive 2018 was released then this will never do anything as the
tlnet-final are just fixed snapshots they will never be updated so you will get no updates via that repository.– David Carlisle
May 2 at 18:10
1
1
In addition, unlike a normal ctan mirror that uses a distributed mirrored network to share load around the globe, this is directly hitting TUG's main server, that server is not set up as a global delivery network, and is designed for occasional one-off downloads of the archived systems.
– David Carlisle
May 2 at 20:30
In addition, unlike a normal ctan mirror that uses a distributed mirrored network to share load around the globe, this is directly hitting TUG's main server, that server is not set up as a global delivery network, and is designed for occasional one-off downloads of the archived systems.
– David Carlisle
May 2 at 20:30
1
1
Noting the concerns in the above comments, this answer still serves as a great temporary workaround. Thanks!
– cemulate
May 9 at 3:50
Noting the concerns in the above comments, this answer still serves as a great temporary workaround. Thanks!
– cemulate
May 9 at 3:50
I need this workaround every year between the time of the official release and the time I actually get around to upgrading my TL installation.
– corwin.amber
Jul 11 at 8:51
I need this workaround every year between the time of the official release and the time I actually get around to upgrading my TL installation.
– corwin.amber
Jul 11 at 8:51
add a comment |
up vote
5
down vote
You don't have to upgrade at all, you can stop at tl2017 (lots of people installed tex years ago and have never updated)
However if you want to update from one texlive to the next without doing a full install (which is the recommended route) then the texlive team have a page detailing what you need to do
https://www.tug.org/texlive/upgrade.html
Note that this URL is exactly the address given in the error message that you quoted in the question.
answered May 2 at 16:39
David Carlisle
479k3811101844
Thank you for your insights. I see thattexlivehas an update mechanism, but it seems that it involves more effort than doing a fresh install altogether. On the other hand, I was looking for a quick fix like the answer below. Sorry If the question wasn't clear though.
– nikhilweee
May 2 at 17:03
@nikhilweee it is commands to type to do an in -place update but the usual reasons for doing it are to save download time by not doewnloading unchanged files and to save disk space by not having both versions installed. If you do not have those requirements then simply installing the new version is of course easier.
– David Carlisle
May 2 at 18:14
1
This won't work: the user's TL is Debian's packaging. An in-place update would require an upstream installation. (At least, it certainly should.) I doubt such an update mechanism is designed to operate in user mode in such cases.
– cfr
May 2 at 21:06
@cfr I did wonder (although most of the question applies to any TL) I thought the debian TL was always updated by the system apt-get, tlmgr also works does it? (if this answer is wrong, the debian packaged tlmgr's error message which gives the same link probably should be changed)
– David Carlisle
May 2 at 21:14
The main tree is updated withapt. But there's a kind of watered-down version oftlmgrwhich users can use to install particular packages themselves.... switching to user mode!is the give away. If this were upstream, it would not say that - either it would go ahead in sys mode or it would complain about permissions. I think the error message is supplied by the repository and not bytlmgr, but I'm not certain. I agree it is messed up, though.
– cfr
May 3 at 3:13
|
show 3 more comments
up vote
5
down vote
You don't have to upgrade at all, you can stop at tl2017 (lots of people installed tex years ago and have never updated)
However if you want to update from one texlive to the next without doing a full install (which is the recommended route) then the texlive team have a page detailing what you need to do
https://www.tug.org/texlive/upgrade.html
Note that this URL is exactly the address given in the error message that you quoted in the question.
answered May 2 at 16:39
David Carlisle
479k3811101844
Thank you for your insights. I see thattexlivehas an update mechanism, but it seems that it involves more effort than doing a fresh install altogether. On the other hand, I was looking for a quick fix like the answer below. Sorry If the question wasn't clear though.
– nikhilweee
May 2 at 17:03
@nikhilweee it is commands to type to do an in -place update but the usual reasons for doing it are to save download time by not doewnloading unchanged files and to save disk space by not having both versions installed. If you do not have those requirements then simply installing the new version is of course easier.
– David Carlisle
May 2 at 18:14
1
This won't work: the user's TL is Debian's packaging. An in-place update would require an upstream installation. (At least, it certainly should.) I doubt such an update mechanism is designed to operate in user mode in such cases.
– cfr
May 2 at 21:06
@cfr I did wonder (although most of the question applies to any TL) I thought the debian TL was always updated by the system apt-get, tlmgr also works does it? (if this answer is wrong, the debian packaged tlmgr's error message which gives the same link probably should be changed)
– David Carlisle
May 2 at 21:14
The main tree is updated withapt. But there's a kind of watered-down version oftlmgrwhich users can use to install particular packages themselves.... switching to user mode!is the give away. If this were upstream, it would not say that - either it would go ahead in sys mode or it would complain about permissions. I think the error message is supplied by the repository and not bytlmgr, but I'm not certain. I agree it is messed up, though.
– cfr
May 3 at 3:13
|
show 3 more comments
up vote
5
down vote
up vote
5
down vote
You don't have to upgrade at all, you can stop at tl2017 (lots of people installed tex years ago and have never updated)
However if you want to update from one texlive to the next without doing a full install (which is the recommended route) then the texlive team have a page detailing what you need to do
https://www.tug.org/texlive/upgrade.html
Note that this URL is exactly the address given in the error message that you quoted in the question.
answered May 2 at 16:39
David Carlisle
479k3811101844
You don't have to upgrade at all, you can stop at tl2017 (lots of people installed tex years ago and have never updated)
However if you want to update from one texlive to the next without doing a full install (which is the recommended route) then the texlive team have a page detailing what you need to do
https://www.tug.org/texlive/upgrade.html
Note that this URL is exactly the address given in the error message that you quoted in the question.
answered May 2 at 16:39
David Carlisle
479k3811101844
answered May 2 at 16:39
David Carlisle
479k3811101844
answered May 2 at 16:39
David Carlisle
479k3811101844
answered May 2 at 16:39
David Carlisle
479k3811101844
479k3811101844
Thank you for your insights. I see thattexlivehas an update mechanism, but it seems that it involves more effort than doing a fresh install altogether. On the other hand, I was looking for a quick fix like the answer below. Sorry If the question wasn't clear though.
– nikhilweee
May 2 at 17:03
@nikhilweee it is commands to type to do an in -place update but the usual reasons for doing it are to save download time by not doewnloading unchanged files and to save disk space by not having both versions installed. If you do not have those requirements then simply installing the new version is of course easier.
– David Carlisle
May 2 at 18:14
1
This won't work: the user's TL is Debian's packaging. An in-place update would require an upstream installation. (At least, it certainly should.) I doubt such an update mechanism is designed to operate in user mode in such cases.
– cfr
May 2 at 21:06
@cfr I did wonder (although most of the question applies to any TL) I thought the debian TL was always updated by the system apt-get, tlmgr also works does it? (if this answer is wrong, the debian packaged tlmgr's error message which gives the same link probably should be changed)
– David Carlisle
May 2 at 21:14
The main tree is updated withapt. But there's a kind of watered-down version oftlmgrwhich users can use to install particular packages themselves.... switching to user mode!is the give away. If this were upstream, it would not say that - either it would go ahead in sys mode or it would complain about permissions. I think the error message is supplied by the repository and not bytlmgr, but I'm not certain. I agree it is messed up, though.
– cfr
May 3 at 3:13
|
show 3 more comments
Thank you for your insights. I see thattexlivehas an update mechanism, but it seems that it involves more effort than doing a fresh install altogether. On the other hand, I was looking for a quick fix like the answer below. Sorry If the question wasn't clear though.
– nikhilweee
May 2 at 17:03
@nikhilweee it is commands to type to do an in -place update but the usual reasons for doing it are to save download time by not doewnloading unchanged files and to save disk space by not having both versions installed. If you do not have those requirements then simply installing the new version is of course easier.
– David Carlisle
May 2 at 18:14
1
This won't work: the user's TL is Debian's packaging. An in-place update would require an upstream installation. (At least, it certainly should.) I doubt such an update mechanism is designed to operate in user mode in such cases.
– cfr
May 2 at 21:06
@cfr I did wonder (although most of the question applies to any TL) I thought the debian TL was always updated by the system apt-get, tlmgr also works does it? (if this answer is wrong, the debian packaged tlmgr's error message which gives the same link probably should be changed)
– David Carlisle
May 2 at 21:14
The main tree is updated withapt. But there's a kind of watered-down version oftlmgrwhich users can use to install particular packages themselves.... switching to user mode!is the give away. If this were upstream, it would not say that - either it would go ahead in sys mode or it would complain about permissions. I think the error message is supplied by the repository and not bytlmgr, but I'm not certain. I agree it is messed up, though.
– cfr
May 3 at 3:13
Thank you for your insights. I see that
texlive has an update mechanism, but it seems that it involves more effort than doing a fresh install altogether. On the other hand, I was looking for a quick fix like the answer below. Sorry If the question wasn't clear though.– nikhilweee
May 2 at 17:03
Thank you for your insights. I see that
texlive has an update mechanism, but it seems that it involves more effort than doing a fresh install altogether. On the other hand, I was looking for a quick fix like the answer below. Sorry If the question wasn't clear though.– nikhilweee
May 2 at 17:03
@nikhilweee it is commands to type to do an in -place update but the usual reasons for doing it are to save download time by not doewnloading unchanged files and to save disk space by not having both versions installed. If you do not have those requirements then simply installing the new version is of course easier.
– David Carlisle
May 2 at 18:14
@nikhilweee it is commands to type to do an in -place update but the usual reasons for doing it are to save download time by not doewnloading unchanged files and to save disk space by not having both versions installed. If you do not have those requirements then simply installing the new version is of course easier.
– David Carlisle
May 2 at 18:14
1
1
This won't work: the user's TL is Debian's packaging. An in-place update would require an upstream installation. (At least, it certainly should.) I doubt such an update mechanism is designed to operate in user mode in such cases.
– cfr
May 2 at 21:06
This won't work: the user's TL is Debian's packaging. An in-place update would require an upstream installation. (At least, it certainly should.) I doubt such an update mechanism is designed to operate in user mode in such cases.
– cfr
May 2 at 21:06
@cfr I did wonder (although most of the question applies to any TL) I thought the debian TL was always updated by the system apt-get, tlmgr also works does it? (if this answer is wrong, the debian packaged tlmgr's error message which gives the same link probably should be changed)
– David Carlisle
May 2 at 21:14
@cfr I did wonder (although most of the question applies to any TL) I thought the debian TL was always updated by the system apt-get, tlmgr also works does it? (if this answer is wrong, the debian packaged tlmgr's error message which gives the same link probably should be changed)
– David Carlisle
May 2 at 21:14
The main tree is updated with
apt. But there's a kind of watered-down version of tlmgr which users can use to install particular packages themselves. ... switching to user mode! is the give away. If this were upstream, it would not say that - either it would go ahead in sys mode or it would complain about permissions. I think the error message is supplied by the repository and not by tlmgr, but I'm not certain. I agree it is messed up, though.– cfr
May 3 at 3:13
The main tree is updated with
apt. But there's a kind of watered-down version of tlmgr which users can use to install particular packages themselves. ... switching to user mode! is the give away. If this were upstream, it would not say that - either it would go ahead in sys mode or it would complain about permissions. I think the error message is supplied by the repository and not by tlmgr, but I'm not certain. I agree it is messed up, though.– cfr
May 3 at 3:13
|
show 3 more comments
up vote
0
down vote
I had this issue because although I installed the latest version of TexLive
I didn't setup the PATH right. I would recommend if anyone has this issue to inspect
the PATH variable and run
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
to make sure that the tlmgr of new installation is discovered before any other already in the system.
edited 1 hour ago
Kurt
34.3k846157
answered 1 hour ago
kpsychas
1
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
I had this issue because although I installed the latest version of TexLive
I didn't setup the PATH right. I would recommend if anyone has this issue to inspect
the PATH variable and run
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
to make sure that the tlmgr of new installation is discovered before any other already in the system.
edited 1 hour ago
Kurt
34.3k846157
answered 1 hour ago
kpsychas
1
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
I had this issue because although I installed the latest version of TexLive
I didn't setup the PATH right. I would recommend if anyone has this issue to inspect
the PATH variable and run
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
to make sure that the tlmgr of new installation is discovered before any other already in the system.
edited 1 hour ago
Kurt
34.3k846157
answered 1 hour ago
kpsychas
1
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had this issue because although I installed the latest version of TexLive
I didn't setup the PATH right. I would recommend if anyone has this issue to inspect
the PATH variable and run
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH
to make sure that the tlmgr of new installation is discovered before any other already in the system.
edited 1 hour ago
Kurt
34.3k846157
answered 1 hour ago
kpsychas
1
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 1 hour ago
Kurt
34.3k846157
edited 1 hour ago
Kurt
34.3k846157
edited 1 hour ago
Kurt
34.3k846157
34.3k846157
answered 1 hour ago
kpsychas
1
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
kpsychas
1
answered 1 hour ago
kpsychas
1
1
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
kpsychas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f429714%2ftlmgr-remote-repository-is-newer-than-local-2017-2018%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
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
4
Welcome! As it stands, this is more a rant than a question. What do you want help with? As you probably know, we are not responsible for the design of TeX Live. (Of course, someone who is may answer your question, but if you really want it answered as such, this isn't the best place.) I would say: it is not really TL which is annoying you, but Debian's packaging of TL. Luckily, you can install the packages you need using
aptwithout needing to update your TL installation. If you had an upstream install, you could just keep using the 2017 version. So nothing forces you to update either way.– cfr
May 2 at 16:38
Package updates might be using new features of TeX Live 2018, for instance.
– egreg
May 2 at 16:39
1
@cfr You are right. This was intended to be a question more than a rant but turned out to be the opposite. I still don't blame myself though. I simply wanted to get rid of this error and install the
listingspackage peacefully. Sorry if that is not evident from the question. Thanks for your insights though. I wasn't aware that I could simply install packages usingapt.– nikhilweee
May 2 at 17:21
Or, you can switch to MiKTeX, if you prefer a rolling release model. Now MiKTeX is also available for Linux and MacOS and it's no longer a Windows-exclusive TeX distro.
– andselisk
47 mins ago