[arch-general] Texlive 2013 packages releases to [testing]
Hello, I have pushed TeXLive 2013 packages to [testing]. The main difference with the 2012 packages is that /etc/texmf files are now in texlive-core rather than texlive-bin. The texlive-bin package now contains almost only binaries, and texlive-core contains all basic data files including the ones in /etc/texmf. Feel free to report any issues you encounter. If you have an existing installation, the upgrade might install new versions of /etc/texmf/ files as *.pacnew. It is unlikely that things work properly if you don't handle the pacnew files unless you realy know what you are doing. If pacnew files appear (notably texmf.cnf and fmtutil.cnf), and the installation reports a failure in regenerating formats (which you will know by not being able to use an engine), you will need to handle the pacnew files, and run "fmtutil-sys --all" by hand. If this situation reaches a high level of absurdity, and if possible considering pacman's behaviour, new packages not behaving like this might be built later before going to [extra]. Regards, Rémy.
On 07/02/2013 06:01 PM, Rémy Oudompheng wrote:
If pacnew files appear (notably texmf.cnf and fmtutil.cnf), and the installation reports a failure in regenerating formats (which you will know by not being able to use an engine), you will need to handle the pacnew files, and run "fmtutil-sys --all" by hand.
What does 'handle the .pacnew' files mean - move them over the orig?
If this situation reaches a high level of absurdity, and if possible considering pacman's behaviour, new packages not behaving like this might be built later before going to [extra].
I'd vote for non-absurd behaviour sooner rather than later ... :-) gene
On Tue, 02 Jul 2013 21:36:53 -0400
Genes Lists
On 07/02/2013 06:01 PM, Rémy Oudompheng wrote:
If pacnew files appear (notably texmf.cnf and fmtutil.cnf), and the installation reports a failure in regenerating formats (which you will know by not being able to use an engine), you will need to handle the pacnew files, and run "fmtutil-sys --all" by hand.
What does 'handle the .pacnew' files mean - move them over the orig?
If this situation reaches a high level of absurdity, and if possible considering pacman's behaviour, new packages not behaving like this might be built later before going to [extra].
I'd vote for non-absurd behaviour sooner rather than later ... :-)
gene
You want to merge the files usually, preferably the pacnew into the existing one. https://wiki.archlinux.org/index.php/Pacnew_and_Pacsave_Files
On 07/03/2013 09:42 AM, Øyvind Heggstad wrote:
You want to merge the files usually, preferably the pacnew into the existing one.
https://wiki.archlinux.org/index.php/Pacnew_and_Pacsave_Files
Yah usually - but these are all provided by the texlive packages with no user edits - seems to be because the files moved from 1 package to another - there is no merging to do I wouldn't think .. but that's kinda what I was trying to find out.
) Started testing texlive 2013 today - I have problems with bibliogrphy. I am working on a document which worked perfectly under texlive 2012. A) I installed when it moved to testing I moved all pacnew files over originals and ran fmtutil-sys --all B) Running biblatex I get: RUnning biblatex: This is BibTeX, Version 0.99d (TeX Live 2013/Arch Linux) The top-level auxiliary file: mbs-val-stochp.aux I found no \citation commands---while reading file mbs-val-stochp.aux I found no \bibdata command---while reading file mbs-val-stochp.aux I found no \bibstyle command---while reading file mbs-val-stochp.aux (There were 3 error messages) The command \printbibliography now does not generate any bibliography. Any suggestions how to fix this?
Forgot to say using this: \usepackage[backend=biber,authordate]{biblatex-chicago} biber seems to be the default now, so no impact with or without backend=biber Changing to biblatex makes no difference - same problems. Help?
On 07/12/2013 09:11 AM, Genes Lists wrote:
) Started testing texlive 2013 today - I have problems with bibliogrphy. I am working on a document which worked perfectly under texlive 2012.
A) I installed when it moved to testing I moved all pacnew files over originals and ran fmtutil-sys --all
B) Running biblatex I get:
RUnning biblatex: This is BibTeX, Version 0.99d (TeX Live 2013/Arch Linux) The top-level auxiliary file: mbs-val-stochp.aux I found no \citation commands---while reading file mbs-val-stochp.aux I found no \bibdata command---while reading file mbs-val-stochp.aux I found no \bibstyle command---while reading file mbs-val-stochp.aux (There were 3 error messages)
The command \printbibliography now does not generate any bibliography.
Any suggestions how to fix this?
Maybe this was heavy-handed, but what I did to get up and running was: 1 - upgrade 2 - fix .pacnew files 3 - fmtutil-sys --all 4 - pacman -S $(pacman -Qqs texlive) In other words, I just re-installed the texlive packages after doing the steps which you already did.
On 07/12/2013 11:34 AM, Matthew Monaco wrote:
3 - fmtutil-sys --all 4 - pacman -S $(pacman -Qqs texlive)
In other words, I just re-installed the texlive packages after doing the steps which you already did.
Thanksa for suggestion - tried didn't help ... same problem ... bibtex is still broken for me. gene/
On 07/12/2013 02:50 PM, Genes Lists wrote:
Thanksa for suggestion - tried didn't help ... same problem ... bibtex is still broken for me.
To be 100% clear - I'm using biblatex. Some additional info - if I run 'biber' directly on the file I get this: biber mbs-val-stochp INFO - This is Biber 1.6 INFO - Logfile is 'mbs-val-stochp.blg' INFO - Reading 'mbs-val-stochp.bcf' INFO - Using all citekeys in bib section 0 INFO - Processing section 0 INFO - Looking for bibtex format file 'mbs-val.bib' for section 0 INFO - Found BibTeX data source 'mbs-val.bib' INFO - Overriding locale 'en_US.UTF-8' default tailoring 'level = 4' with 'level = 2' INFO - Overriding locale 'en_US.UTF-8' default tailoring 'variable = shifted' with 'variable = non-ignorable' INFO - Sorting 'entry' list 'cms' keys INFO - No sort tailoring available for locale 'en_US.UTF-8' INFO - Writing 'mbs-val-stochp.bbl' with encoding 'ascii' "\x{fffd}" does not map to ascii at /home/gene/tmp/par-67656e65/cache-371b0cf3aa3eec4dfb0c82647515336d327c4e62/inc/lib/Biber/Utils.pm line 932. "\x{fffd}" does not map to ascii at /home/gene/tmp/par-67656e65/cache-371b0cf3aa3eec4dfb0c82647515336d327c4e62/inc/lib/Biber/Utils.pm line 932. "\x{fffd}" does not map to ascii at /home/gene/tmp/par-67656e65/cache-371b0cf3aa3eec4dfb0c82647515336d327c4e62/inc/lib/Biber/Utils.pm line 932. "\x{fffd}" does not map to ascii at /home/gene/tmp/par-67656e65/cache-371b0cf3aa3eec4dfb0c82647515336d327c4e62/inc/lib/Biber/Utils.pm line 932. "\x{fffd}" does not map to ascii at /home/gene/tmp/par-67656e65/cache-371b0cf3aa3eec4dfb0c82647515336d327c4e62/inc/lib/Biber/Utils.pm line 932. "\x{fffd}" does not map to ascii at /home/gene/tmp/par-67656e65/cache-371b0cf3aa3eec4dfb0c82647515336d327c4e62/inc/lib/Biber/Utils.pm line 932. INFO - Output to mbs-val-stochp.bbl The first one at line 932 contains this: print $fh NFC($string);# Unicode NFC boundary Sure looks like something is badly broken.
gene/
I think I resolved this. (i) the strange errors from biber are fixed by adding: \usepackage[utf8]{inputenc} (ii) The missing bibliography is fixed by running biber instead of bibtex. If using texmaker change the settings: bibtext %.aux to: biber % gene/
participants (4)
-
Genes Lists
-
Matthew Monaco
-
Rémy Oudompheng
-
Øyvind Heggstad