Summary: | =dev-texlive/texlive-xetex-2010-r1 - ! TeX capacity exceeded, sorry [pattern memory=600000]. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Current packages | Assignee: | Alexis Ballier <aballier> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | hwoarang, tex |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 355085 | ||
Attachments: | dev-texlive:texlive-xetex-2010-r1:20110802-175136.log |
Description
Jeroen Roovers (RETIRED)
![]() this is normal if you're using the config files prior to texlive 2010: tex memory was too low for xetex. please make sure you're updated files in /etc, ran texmf-update, and then try again; reopen if it still fails, with your /etc/texmf/web2c/texmf.cnf file You mean this kind of upgrade disaster is how you expect things to work for every user? And you're not even going to warn people or explain how to properly upgrade? Like [1] I mean, which is about the ->2008 upgrade (even though [2] still thinks it's 2007). The only mention of this bug in [1] is: "The 15options.cnf and 20sizes.cnf files can be modified with caution. The comments in these files should explain what options mean. For example, in 20sizes.cnf you can increase TeX memory, in case you are trying to compile a document that is too big and runs into //TeX capacity exceeded, sorry errors//. If the answer to my initial question is YES, then please reopen this bug report so that I can take action accordingly. [1] http://www.gentoo.org/proj/en/tex/texlive-migration-guide.xml [2] http://www.gentoo.org/proj/en/tex/ (In reply to comment #2) > You mean this kind of upgrade disaster is how you expect things to work for > every user? This only fails if you have a lot of texlive-lang* packages installed. > And you're not even going to warn people or explain how to properly > upgrade? elog elog "If you have configuration files in /etc/texmf to merge," elog "please update them and run /usr/sbin/texmf-update." elog ?? This process is called config protect... I don't think it would be wise to overwrite those files at every update, this will piss off people for a very small gain. (In reply to comment #3) > This only fails if you have a lot of texlive-lang* packages installed. Fair enough. So only a *few* users will have this lousy experience. :) > > And you're not even going to warn people or explain how to properly > > upgrade? > > elog > elog "If you have configuration files in /etc/texmf to merge," > elog "please update them and run /usr/sbin/texmf-update." > elog > > ?? Er, yeah: ?? Where are you going to put that? Looks like if someone is updating the entire texlive distribution, this would need to be done somewhere in between updating the language packages and this package. > This process is called config protect... I don't think it would be wise to > overwrite those files at every update, this will piss off people for a very > small gain. Pissing off people, like when you uninstall the complete 2008 distro and you get these awfully extended kpsewhich runs after every unmerge? OK, I see where you're going. 1) You could update your upgrade guide to warn of this problem and show people how to work around it. (But I already pointed that out.) 2) You could prevent a tool living in WORKDIR from parsing a runtime configuration installed on the live system, but use its to-be-installed runtime configuration files instead. If this could be fixed, there would be no need to piss off anyone. Oh by the way, WORKSFORME is the wrong resolution if you are intent on doing a WONTFIX. You've got to send the right message to your users, you know. (In reply to comment #4) > (In reply to comment #3) > > This only fails if you have a lot of texlive-lang* packages installed. > > Fair enough. So only a *few* users will have this lousy experience. :) > > > > And you're not even going to warn people or explain how to properly > > > upgrade? > > > > elog > > elog "If you have configuration files in /etc/texmf to merge," > > elog "please update them and run /usr/sbin/texmf-update." > > elog > > > > ?? > > Er, yeah: ?? Where are you going to put that? its been in tl-core since the beginning of it... > Looks like if someone is updating > the entire texlive distribution, this would need to be done somewhere in > between updating the language packages and this package. yes; on the very few cases there'll be a failure, people will see this because portage prints it and will be supposed to do it and try again... > > > This process is called config protect... I don't think it would be wise to > > overwrite those files at every update, this will piss off people for a very > > small gain. > > Pissing off people, like when you uninstall the complete 2008 distro and you > get these awfully extended kpsewhich runs after every unmerge? OK, I see where > you're going. this has nothing to do with the bug and has been improved in tl2010 btw ;) > > 1) You could update your upgrade guide to warn of this problem and show people > how to work around it. (But I already pointed that out.) the guide is outdated and was mainly meant as a ptex/tetex to texlive migration. It could be updated but since then I think b.g.o is also a good resource for such errors. > 2) You could prevent a tool living in WORKDIR from parsing a runtime > configuration installed on the live system, but use its to-be-installed > runtime configuration files instead. If this could be fixed, there would be > no need to piss off anyone. ??? the files on the live fs are used because users are allowed to modify them; that's why they're config protected in the first time, and that's why you've had this error. configuration files you needed to update are shared and provided by kpathsea, so I don't see what you mean by "use its to-be-installed runtime configuration files instead". what's the "tool living in WORKDIR" ? *** Bug 378527 has been marked as a duplicate of this bug. *** |