TeXLive 2022 is available. Please bump. Reproducible: Always
It was released yesterday, please be patient. It takes quite a whlie to do.
I am unlikely to have time this year, can guide any interested gentoo dev though
Somebody, fix https://bugs.gentoo.org/865805 before this.
I am interested in providing texlive*-2022 in my overlay if it's not too difficult or too time-consuming. Anyone will be able to adapt texlive from my overlay to gentoo overlay. I personally use LaTeX and ConTeXt. But, I'm not familiar with texlive eclasses which look like monsters. Any help?
*** Bug 869914 has been marked as a duplicate of this bug. ***
(In reply to amano.kenji from comment #4) > Any help? https://wiki.gentoo.org/wiki/Project:TeX/Tex_Live_Bump_Story My hope is whoever ends up doing the bump in Gentoo this time around will flesh out that page further too.
*** Bug 903171 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=96fe8d6e52f342b6764536aca58ddd563df3e278 commit 96fe8d6e52f342b6764536aca58ddd563df3e278 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-05-19 05:01:11 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-05-19 05:05:17 +0000 app-text/texlive-core: patch CVE-2023-32700 This does not fix CVE-2023-32668 which changes behaviour so must be handled in a new version (>= 2023). Bug: https://bugs.gentoo.org/836779 Bug: https://bugs.gentoo.org/906712 Signed-off-by: Sam James <sam@gentoo.org> app-text/texlive-core/Manifest | 1 + app-text/texlive-core/texlive-core-2021-r7.ebuild | 392 ++++++++++++++++++++++ 2 files changed, 393 insertions(+)
*** Bug 915895 has been marked as a duplicate of this bug. ***
May I ask what progress has been made in the development so far? If there are technical challenges that cannot be overcome in the short term, can we consider maintaining a binary package?
There is an initial set of texlive-2023 ebuilds. They will go through gentoo internal testing because I've changed the way they are created. Once that is done I'll file a PR. So give us maybe a week?
We have produced a set of ebuilds for TeX Live 2023. The ebuilds currently undergo testing and can be found in the tex-overlay [1]. Adventurous and experienced users are encouraged to try the TeX Live 2023 ebuilds from the overlay. You can install the overlay via "eselect repository enable tex-overlay". Please report bugs and suggestions at #gentoo-tex IRC channel at libera or via mail to tex@gentoo.org. Thanks. 1: https://gitweb.gentoo.org/proj/tex-overlay.git/
(In reply to Florian Schmaus from comment #12) > We have produced a set of ebuilds for TeX Live 2023. The ebuilds currently > undergo testing and can be found in the tex-overlay [1]. Adventurous and > experienced users are encouraged to try the TeX Live 2023 ebuilds from the > overlay. You can install the overlay via "eselect repository enable > tex-overlay". > > Please report bugs and suggestions at #gentoo-tex IRC channel at libera or > via mail to tex@gentoo.org. > > Thanks. > > 1: https://gitweb.gentoo.org/proj/tex-overlay.git/ bilbo ~ # eselect repository enable tex-overlay error: tex-overlay: repository not in repositories.xml
(In reply to Florian Schmaus from comment #12) > We have produced a set of ebuilds for TeX Live 2023. The ebuilds currently > undergo testing and can be found in the tex-overlay [1]. Adventurous and > experienced users are encouraged to try the TeX Live 2023 ebuilds from the > overlay. The update from texlive 2021 to 2023 worked (I had to manually download the texlive base tarball though and an info text points to an empty wiki page after the installation); I was working for a couple of hours with a bigger lualatex document with text, math, tikz, komascript, minted, latexmk etc. and tried some of the new features like \DocumentMetadata to generate a pdf in version 2.0 and found no problems so far. There was no need to uninstall everything like in the past, a plain update worked. Thank you very much :-)
(In reply to Florian Schmaus from comment #12) > We have produced a set of ebuilds for TeX Live 2023. The ebuilds currently > undergo testing and can be found in the tex-overlay [1]. Adventurous and > experienced users are encouraged to try the TeX Live 2023 ebuilds from the > overlay. You can install the overlay via "eselect repository enable > tex-overlay". > > Please report bugs and suggestions at #gentoo-tex IRC channel at libera or > via mail to tex@gentoo.org. > > Thanks. > > 1: https://gitweb.gentoo.org/proj/tex-overlay.git/ Thank you Florian. This commit https://gitweb.gentoo.org/proj/tex-overlay.git/commit/?h=main&id=811c9ab604cdc32d7ac580b6925edfba9446c606 is applicable to more ebuilds in the overlay: ag ctan/Source/ app-text/ps2pkm/ps2pkm-1.8_p20230311.ebuild 8:SRC_URI="mirror://ctan/Source//texlive-${PV#*_p}-source.tar.xz" app-text/dvipsk/dvipsk-20230311_p66203.ebuild 11:SRC_URI="mirror://ctan/Source/texlive-${TL_VERSION}-source.tar.xz" app-text/ttf2pk2/ttf2pk2-2.0_p20230311.ebuild 8:SRC_URI="mirror://ctan/Source//texlive-${PV#*_p}-source.tar.xz" dev-libs/kpathsea/kpathsea-6.3.5_p20230311.ebuild 14: mirror://ctan/Source/${MY_SOURCE_FILE} dev-libs/ptexenc/ptexenc-1.4.3_p20230311.ebuild 10:SRC_URI="mirror://ctan/Source//texlive-${PV#*_p}-source.tar.xz" dev-tex/bibtexu/bibtexu-4.00_p20230311.ebuild 10:SRC_URI="mirror://ctan/Source/texlive-${PV#*_p}-source.tar.xz"
Should be updated.
We found a bug in the texlive-common.eclass of the texlive overlay at https://github.com/cschwan/sage-on-gentoo/issues/773 we could not figure why some japanese fonts were not properly generated making a build fail. Turns out there is a stray ")" on the line at https://gitweb.gentoo.org/proj/tex-overlay.git/tree/eclass/texlive-common.eclass?h=main#n61 which produces incorrect symlinks in texlive-core-2023 fbissey@tarazed ~ $ ll /usr/share/texmf-dist/web2c/updmap-hdr.cfg lrwxrwxrwx 1 root root 45 Dec 28 14:05 /usr/share/texmf-dist/web2c/updmap-hdr.cfg -> '../../../../etc/texmf/web2c).d/updmap-hdr.cfg' fbissey@tarazed ~ $ ll /usr/share/texmf-dist/web2c/fmtutil-hdr.cnf lrwxrwxrwx 1 root root 46 Dec 28 14:05 /usr/share/texmf-dist/web2c/fmtutil-hdr.cnf -> '../../../../etc/texmf/web2c).d/fmtutil-hdr.cnf' fbissey@tarazed ~ $ ll /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg lrwxrwxrwx 1 root root 46 Dec 28 14:05 /usr/share/texmf-dist/dvipdfmx/dvipdfmx.cfg -> '../../../../etc/texmf/dvipdfmx).d/dvipdfmx.cfg' Kudos to Steve Trogdon for finding the dvipdfmx.cfg one from which I unravelled the rest. Of course those are the wrong symlinks we found in texlive-core, any other ebuilds using texlive-common_do_symlinks will be equally affected.
Sorry I meant the "texlive-common_handle_config_files" function not "texlive-common_do_symlinks" in that last bit.
I'll go over the eclasses in a bit and see if we missed more unifying the $() calls.
Thanks for reporting. Fixed with https://gitweb.gentoo.org/proj/tex-overlay.git/commit/?h=main&id=02a45ff97b50eb0ecffa7532bf1697b065b71925
texlive-core-2023 from the tex-overlay cannot be configured in Prefix. After the configure phase I get: configure: creating cache config.cache checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes checking for x86_64-pc-linux-gnu-gcc option to enable C11 features... none needed checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes checking for native WIN32 or MINGW32... no configure: error: Sorry, incompatible options `--without-x' and `--enable-xpdfopen' While with texlive-core-2021-r7 I get: configure: creating cache config.cache checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed checking whether x86_64-pc-linux-gnu-gcc understands -c and -o together... yes checking for native WIN32 or MINGW32... no configure: Assuming `--enable-autosp=yes' configure: Assuming `--enable-axodraw2=yes' configure: Assuming `--enable-devnag=yes' configure: Assuming `--enable-lacheck=yes' configure: Assuming `--enable-m-tx=yes' configure: Assuming `--enable-pmx=yes' configure: Assuming `--enable-tpic2pdftex=yes' configure: Assuming `--with-clisp-runtime=system' configure: Assuming `--enable-xml2pmx=yes' configure: `--without-x' -> `--disable-xpdfopen' Let me know if I should file a separate Prefix bug.
I pushed a fix to the overlay. `app-text/texlive-core` is not finished yet and needs more work.
One commit per eclass in future? :p Anyway: commit b5a162f8b12688094165a3bdb995dac394bb7ac6 (HEAD -> master, origin/master, origin/HEAD) Author: Florian Schmaus <flow@gentoo.org> Date: Tue Jan 30 11:48:12 2024 +0100 eclass: update texlive eclasses for texlive 2023 Signed-off-by: Florian Schmaus <flow@gentoo.org>
*** Bug 924167 has been marked as a duplicate of this bug. ***
Today a building issue came up with dev-texlive/texlive-latexextra-2023_p69752. fmtutil creates an error message but I have no clue what it tries to tell me or how to fix this. Version 2023_p68643 did not have this issue. fmtutil [INFO]: log file copied to: /mnt/ramdisk/portage/dev-texlive/texlive-latexextra-2023_p69752/work/texmf-var/web2c/luahbtex/lualatex-dev.log fmtutil [INFO]: /mnt/ramdisk/portage/dev-texlive/texlive-latexextra-2023_p69752/work/texmf-var/web2c/luahbtex/lualatex-dev.fmt installed. fmtutil [WARNING]: inifile latex.ini for latex-dev/pdftex not found. fmtutil [WARNING]: inifile pdflatex.ini for pdflatex-dev/pdftex not found. fmtutil [INFO]: successfully rebuilt formats: 2 fmtutil [INFO]: failed to build: 2 (pdftex/latex-dev pdftex/pdflatex-dev) fmtutil [INFO]: total formats: 4 fmtutil [INFO]: ************************************************************* * * * WARNING: you are switching to fmtutil's per-user formats. * * Please read the following warnings! * * * ************************************************************* You have run fmtutil-user (as opposed to fmtutil-sys) for the first time; this has created format files which are local to your personal account. From now on, any changes in system formats will *not* be automatically reflected in your files; furthermore, running fmtutil-sys will no longer have any effect for you. As a consequence, you yourself have to rerun fmtutil-user after any change in the system directories. For example, when one of the LaTeX or other format source files changes, which happens frequently. See https://tug.org/texlive/scripts-sys-user.html for details. If you want to undo this, remove the files mentioned above. Run fmtutil --help for full documentation of fmtutil. fmtutil [INFO]: exiting with status 2 * ERROR: dev-texlive/texlive-latexextra-2023_p69752::tex-overlay failed (compile phase): * failed to build format texmf-dist/fmtutil/format.texlive-latexextra.cnf * * Call stack: * ebuild.sh, line 136: Called src_compile * environment, line 4510: Called texlive-module_src_compile * environment, line 4757: Called die * The specific snippet of code: * VARTEXFONTS="${T}/fonts" TEXMFHOME="${S}/texmf:${S}/texmf-dist:${S}/texmf-var" env -u TEXINPUTS "${fmt_call}" --cnffile "${i}" --fmtdir "${S}/texmf-var/web2c" --all || die "failed to build format ${i}";
(In reply to Mark from comment #25) > Today a building issue came up with > dev-texlive/texlive-latexextra-2023_p69752. > fmtutil creates an error message but I have no clue what it tries to tell me > or how to fix this. > Version 2023_p68643 did not have this issue. Can you attach the full build.log and /mnt/ramdisk/portage/dev-texlive/texlive-latexextra-2023_p69752/work/texmf-var/web2c/luahbtex/lualatex-dev.log please?
Created attachment 884743 [details] build.log and lualatex-dev.log
> fmtutil [WARNING]: inifile latex.ini for latex-dev/pdftex not found. > fmtutil [WARNING]: inifile pdflatex.ini for pdflatex-dev/pdftex not found. Seems like texlive-latexextra is missing a DEPEND on texlive-basic, which would pull in tex-ini-files which contains latex.ini and pdflatex.ini. @Mark: Could you emerge texlive-basic and see if this enables you to build texlive-latexextra?
(In reply to Florian Schmaus from comment #28) > > fmtutil [WARNING]: inifile latex.ini for latex-dev/pdftex not found. > > fmtutil [WARNING]: inifile pdflatex.ini for pdflatex-dev/pdftex not found. > > Seems like texlive-latexextra is missing a DEPEND on texlive-basic, which > would pull in tex-ini-files which contains latex.ini and pdflatex.ini. > > @Mark: Could you emerge texlive-basic and see if this enables you to build > texlive-latexextra? texlive-basic-2023_p59159 and a couple of the new testing packages are already installed. These files are available when I start the update and belong to dev-texlive/texlive-latex-2023_p63515: /usr/share/texmf-dist/tex/latex/latexconfig/latex.ini /usr/share/texmf-dist/tex/latex/latexconfig/pdflatex.ini This is the starting situation for the update: Installed packages: =dev-tex/biber-2.19 =dev-tex/biblatex-3.19 =dev-tex/bibtexu-4.00_p20230311 =dev-tex/glossaries-4.52 =dev-tex/latex-beamer-3.70 =dev-tex/latexmk-4.80 =dev-tex/minted-2.6 =dev-tex/pgf-3.1.9a =dev-tex/rail-1.2_p1-r1 =dev-tex/tex4ht-20230311_p68735 =dev-texlive/texlive-basic-2023_p59159 =dev-texlive/texlive-bibtexextra-2023_p67386 =dev-texlive/texlive-fontsextra-2023_p68231 =dev-texlive/texlive-fontsrecommended-2023_p54074 =dev-texlive/texlive-fontutils-2023_p61207 =dev-texlive/texlive-formatsextra-2023_p62226 =dev-texlive/texlive-langcjk-2023_p65824 =dev-texlive/texlive-langgerman-2023_p55706 =dev-texlive/texlive-langgreek-2023_p65038 =dev-texlive/texlive-langjapanese-2023_p64603 =dev-texlive/texlive-latex-2023_p63515 =dev-texlive/texlive-latexextra-2023_p68643 =dev-texlive/texlive-latexrecommended-2023_p65512 =dev-texlive/texlive-luatex-2023_p68053 =dev-texlive/texlive-mathscience-2023_p68312 =dev-texlive/texlive-metapost-2023_p67071 =dev-texlive/texlive-pictures-2023_p68515 =dev-texlive/texlive-plaingeneric-2023_p68513 =dev-texlive/texlive-pstricks-2023_p65367 =dev-texlive/texlive-publishers-2023_p68224 =dev-texlive/texlive-xetex-2023_p64951 emerge -puD world: [ebuild U ~] dev-texlive/texlive-latex-2023_p69131 [2023_p63515] [ebuild U ~] dev-texlive/texlive-latexrecommended-2023_p69131 [2023_p65512] [ebuild U ~] dev-tex/pgf-3.1.10 [3.1.9a] [ebuild U ~] dev-tex/latex-beamer-3.71 [3.70] [ebuild U ~] dev-texlive/texlive-pictures-2023_p69409 [2023_p68515] [ebuild U ~] dev-texlive/texlive-fontsextra-2023_p69663 [2023_p68231] [ebuild U ~] dev-texlive/texlive-langgerman-2023_p68711 [2023_p55706] [ebuild U ~] dev-texlive/texlive-luatex-2023_p69404 [2023_p68053] [ebuild U ~] dev-texlive/texlive-mathscience-2023_p69485 [2023_p68312] [ebuild U ~] dev-texlive/texlive-publishers-2023_p69759 [2023_p68224] [ebuild U ~] dev-texlive/texlive-plaingeneric-2023_p68675 [2023_p68513] [ebuild U ~] dev-texlive/texlive-latexextra-2023_p69752 [2023_p68643] [ebuild U ] dev-tex/glossaries-4.53 [4.52] [ebuild U ~] dev-tex/minted-2.9 [2.6] On emerge -uD world I get a file collision during the first ebuild (dev-texlive/texlive-latex-2023_p6913): * Detected file collision(s): * * /usr/share/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.lua * /usr/share/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * dev-texlive/texlive-latexrecommended-2023_p65512:0::tex-overlay * /usr/share/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.lua * /usr/share/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty After unmerging the conflicting dev-texlive/texlive-latexrecommended the update can be done, the new latexrecommended is pulled in as the second package automatically, installed without problems and then a couple of packages later I get the texlive-latexextra issue. I started a git bisect: c3933c4ddb29e1b7fee501efcec62181f0ffe676 is the first bad commit.
Just ran into the same issue with texlive-latexextra. Had to unmerge it first because of the file collision too.
I tried to run the command manually with variations of TEXMFHOME to include /usr/share/texmf-dist or some subfolder where the reported missing files are located without success.
On the basis of information returned by locate I thought I had the `latex.ini` and `pdflatex.ini` in `/usr/share/texmf-dist/tex/latex/latexconfig/` (a folder belonging to dev-texlive/texlive-latex) but in the end the files are missing. On the other hand `lualatex.ini` and `dvilualatex.ini`are present in the folder `/usr/share/texmf-dist/tex/generic/tex-ini-files/` that belongs to dev-texlive/texlive-basic. Could it be that those missing files should also be installed from texlive-basic?
In texlive-latex, latexconfig.r53525.tar.xz had the needed .ini files, but latexconfig.r68923.tar.xz does not have them. Not sure where they have gone.
I think we need a newer version of tex-ini-files. It looks like the files we need are there.
This is very complex. Somehow I've been able to upgrade texlive, mostly; at least no errors after resolving collisions. However I'm unable to rebuild texlive-core and possibly others: * Regenerating TeX formats * ERROR: app-text/texlive-core-2023::tex-overlay failed (postinst phase): * Failed to regenerate TeX formats * * Call stack: * ebuild.sh, line 136: Called pkg_postinst * environment, line 2070: Called die * The specific snippet of code: * fmtutil-sys --all &> /dev/null || die "Failed to regenerate TeX formats"; * * If you need support, post the output of `emerge --info '=app-text/texlive-core-2023::tex-overlay'`, * the complete build log and the output of `emerge -pqv '=app-text/texlive-core-2023::tex-overlay'`. * The complete build log is located at '/var/tmp/portage/app-text/texlive-core-2023/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-text/texlive-core-2023/temp/environment'. * Working directory: '/var/tmp/portage/app-text/texlive-core-2023/empty' * S: '/var/tmp/portage/app-text/texlive-core-2023/work/texlive-20230311-source' * FAILED postinst: 1 The command 'fmtutil-sys --all` fails with No pages of output. Transcript written on pdfjadetex.log. fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/pdfjadetex.log fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/pdfjadetex.fmt installed. fmtutil [ERROR]: no (or empty) hitex.fmt made by: hitex -ini -jobname=hitex -progname=hitex -etex -ltx hitex.ini </dev/null fmtutil [ERROR]: running `pdftex -ini -jobname=pdftex -progname=pdftex -translate-file=cp227.tcx *pdfetex.ini </dev/null' return status: 1 fmtutil [ERROR]: returning error due to option --strict fmtutil [ERROR]: running `pdftex -ini -jobname=pdfetex -progname=pdfetex -translate-file=cp227.tcx *pdfetex.ini </dev/null' return status: 1 fmtutil [ERROR]: returning error due to option --strict fmtutil [ERROR]: running `pdftex -ini -jobname=etex -progname=etex -translate-file=cp227.tcx *etex.ini </dev/null' return status: 1 fmtutil [ERROR]: returning error due to option --strict fmtutil [INFO]: successfully rebuilt formats: 35 fmtutil [INFO]: failed to build: 4 (hitex/hitex pdftex/pdftex pdftex/pdfetex pdftex/etex) fmtutil [INFO]: total formats: 39 fmtutil [INFO]: exiting with status 4
It seems texlive-basic includes the right version of tex-ini-files but for some reasons they are not all installed. And now when I try to reinstall texlive-basic it fails with a similar fmtutil error. Things may have been working so long as some version of those missing .ini files where present. And once they have gone things fail. We have to get texlive-basic to install all tex-ini-files and not break itself in the process. Would it be worth splitting tex-ini-files or to put it with a different texlive package that do not need itself to be bootstrapped?
> texlive-basic-2023_p59159 […] are already installed. Please make sure that this is the *current* texlive-basic version from the *latest* HEAD of tex-overlay.git. I recommend everyone that wants to test texlive from tex-overlay.git, which is very much appreciated, to first uninstall texlive and then re-install it. Only this guarantees that you have the current ebuilds from the overlay installed. Uninstalling (most of) texlive could be done, for example, via emerge -C app-text/texlive app-text/texlive-core `eix -C dev-texlive -I --only-names` then re-install app-text/texlive. I am pretty sure that this will fix your issues. If not, then please report back, but maybe consider joining #gentoo-tex, where we could debug the issue further.
(In reply to Florian Schmaus from comment #37) > > texlive-basic-2023_p59159 […] are already installed. > > Please make sure that this is the *current* texlive-basic version from the > *latest* HEAD of tex-overlay.git. > > I recommend everyone that wants to test texlive from tex-overlay.git, which > is very much appreciated, to first uninstall texlive and then re-install it. > Only this guarantees that you have the current ebuilds from the overlay > installed. > > Uninstalling (most of) texlive could be done, for example, via > > emerge -C app-text/texlive app-text/texlive-core `eix -C dev-texlive -I > --only-names` > > then re-install app-text/texlive. > > I am pretty sure that this will fix your issues. If not, then please report > back, but maybe consider joining #gentoo-tex, where we could debug the issue > further. This worked here even though I had previously sync'd the overlay.
Sorry for not taking to #gentoo-tex. I tried to follow your advice to unmerge everything first (not the first time that something like that is needed in that kind of mess). I now have a circular dependency when trying to emerge texlive * Error: circular dependencies: (dev-tex/biblatex-3.19:0/0::tex-overlay, ebuild scheduled for merge) depends on (dev-texlive/texlive-bibtexextra-2023_p67386:0/0::tex-overlay, ebuild scheduled for merge) (buildtime) (dev-tex/biblatex-3.19:0/0::tex-overlay, ebuild scheduled for merge) (runtime) Looking at the ebuilds there is no way to get out of it with useflags: --biblatex-3.19.ebuild-- DEPEND=" dev-texlive/texlive-bibtexextra dev-texlive/texlive-latexextra dev-texlive/texlive-plaingeneric " RDEPEND="${DEPEND}" # biblatex and biber must always have compatible versions PDEPEND="biber? ( ~dev-tex/biber-2.$(ver_cut 2) )" --texlive-bibtexextra-2023_p67386.ebuild-- COMMON_DEPEND=" >=dev-texlive/texlive-latex-2023 " RDEPEND=" ${COMMON_DEPEND} >=dev-tex/biber-2.19 >=dev-tex/biblatex-3.19 " DEPEND=" ${COMMON_DEPEND} " Should biblatex be a PDEPEND in texlive-bibtexextra?
(In reply to Florian Schmaus from comment #37) > > texlive-basic-2023_p59159 […] are already installed. > > Please make sure that this is the *current* texlive-basic version from the > *latest* HEAD of tex-overlay.git. ah, that solved the problem of Comment #25, thanks. (I assumed the package did not change.)
(In reply to François Bissey from comment #39) > Sorry for not taking to #gentoo-tex. I tried to follow your advice to > unmerge everything first (not the first time that something like that is > needed in that kind of mess). > > I now have a circular dependency when trying to emerge texlive > * Error: circular dependencies: > Yes, indeed. If one does emerge -C app-text/texlive app-text/texlive-core `eix -C dev-texlive -I --only-names` and a stray version of `biblatex` is still on ones system them installing `texlive` succeeds. However if the `biblatex` is removed via emerge -C app-text/texlive app-text/texlive-core `eix -C dev-tex -I --only-names` then there are circular dependencies # emerge -pv texlive These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 3.97 s (backtrack: 1/20). [nomerge ] app-text/texlive-2023::tex-overlay USE="X cjk extra graphics luatex png pstricks scienc -as -bg -bn -br -cs -cy -da -el -eo -et -eu -fa -fi -ga -gl -gu -he -hi -hr -hsb -hy -ia -id -is -kn -ko [nomerge ] dev-texlive/texlive-bibtexextra-2023_p67386::tex-overlay USE="-doc -source" [ebuild N ~] dev-tex/biblatex-3.19::tex-overlay USE="biber -doc -examples" 0 KiB [ebuild N ~] dev-tex/biber-2.19::tex-overlay USE="-test" 0 KiB [ebuild N ~] app-text/texlive-2023::tex-overlay USE="X cjk extra graphics luatex png pstricks scienc -as -bg -bn -br -cs -cy -da -el -eo -et -eu -fa -fi -ga -gl -gu -he -hi -hr -hsb -hy -ia -id -is -kn -ko [ebuild N ~] dev-texlive/texlive-bibtexextra-2023_p67386::tex-overlay USE="-doc -source" 0 KiB Total: 4 packages (4 new), Size of downloads: 0 KiB * Error: circular dependencies: (dev-tex/biblatex-3.19:0/0::tex-overlay, ebuild scheduled for merge) depends on (dev-texlive/texlive-bibtexextra-2023_p67386:0/0::tex-overlay, ebuild scheduled for merge) (buildtime) (dev-tex/biblatex-3.19:0/0::tex-overlay, ebuild scheduled for merge) (runtime)
(In reply to François Bissey from comment #39) > Should biblatex be a PDEPEND in texlive-bibtexextra? Yes, it should. I've pushed the change.
Some more circular dependency tarazed ~ # USE="-biber" emerge -pv texlive These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 7.92 s (backtrack: 1/20). [nomerge ] app-text/texlive-2023::tex-overlay USE="X extra* luatex png truetype xml -cjk -context -games -graphics -humanities -metapost -music (-pdfannotextractor) -pstricks -publishers -science -tex4ht -texi2html -xetex" L10N="ca de en es fr hu it ja pt ru tr -af -ar -as -bg -bn -br -cs -cy -da -el -eo -et -eu -fa -fi -ga -gl -gu -he -hi -hr -hsb -hy -ia -id -is -kn -ko -la -lo -lt -lv -ml -mn -mr -nb -nl -nn -no -or -pa -pl -rm -ro -sa -sco -sk -sl -sq -sr -sv -ta -te -th -tk -uk -vi -zh" [nomerge ] dev-texlive/texlive-bibtexextra-2023_p67386::tex-overlay USE="-doc -source" [ebuild N ~] dev-tex/biber-2.19::tex-overlay USE="-test" 1597 KiB [ebuild R ~] app-text/texlive-2023::tex-overlay USE="X extra* luatex png truetype xml -cjk -context -games -graphics -humanities -metapost -music (-pdfannotextractor) -pstricks -publishers -science -tex4ht -texi2html -xetex" L10N="ca de en es fr hu it ja pt ru tr -af -ar -as -bg -bn -br -cs -cy -da -el -eo -et -eu -fa -fi -ga -gl -gu -he -hi -hr -hsb -hy -ia -id -is -kn -ko -la -lo -lt -lv -ml -mn -mr -nb -nl -nn -no -or -pa -pl -rm -ro -sa -sco -sk -sl -sq -sr -sv -ta -te -th -tk -uk -vi -zh" 0 KiB [nomerge ] dev-tex/biber-2.19::tex-overlay USE="-test" [ebuild N ~] dev-tex/biblatex-3.19::tex-overlay USE="-biber -doc -examples" 18544 KiB [ebuild N ~] dev-texlive/texlive-bibtexextra-2023_p67386::tex-overlay USE="-doc -source" 2986 KiB Total: 4 packages (3 new, 1 reinstall), Size of downloads: 23126 KiB * Error: circular dependencies: (dev-tex/biber-2.19:0/0::tex-overlay, ebuild scheduled for merge) depends on (dev-tex/biblatex-3.19:0/0::tex-overlay, ebuild scheduled for merge) (buildtime) (dev-texlive/texlive-bibtexextra-2023_p67386:0/0::tex-overlay, ebuild scheduled for merge) (buildtime) (dev-tex/biber-2.19:0/0::tex-overlay, ebuild scheduled for merge) (runtime) * Note that circular dependencies can often be avoided by temporarily * disabling USE flags that trigger optional dependencies. ====== This a more complex dependency, texlive-bibtexextra depends on biber RDEPEND=" ${COMMON_DEPEND} >=dev-tex/biber-2.19 " biber depends on biblatex and biblatex depends on texlive-bibtexextra. Moving biber to PDEPEND in texlive-bibtexextra breaks the circular dependency. And as a bonus, it breaks it with or without the biber useflag, which was the obvious thing to try first.
(In reply to François Bissey from comment #43) > Moving biber to PDEPEND in texlive-bibtexextra breaks the circular > dependency. I've dropped biber from texlive-bibtextra entirely as it is conditionally pulled in by dev-tex/biblatex based on the biber USE flag.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a11d6d606c93613b853b73e8086a82094e82f1fd commit a11d6d606c93613b853b73e8086a82094e82f1fd Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-03-01 09:51:17 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-03-01 10:05:48 +0000 app-text/texlive: add 2023 Special thanks to Paul "negril" Zander for help and initially creating the ebuilds for TexLive 2023. Bug: https://bugs.gentoo.org/836779 Signed-off-by: Florian Schmaus <flow@gentoo.org> app-text/texlive/texlive-2023.ebuild | 133 +++++++++++++++++++++++++++++++++++ 1 file changed, 133 insertions(+)
I have switched to the masked version in the tree. Starting with a clean tex slate by running emerge -C app-text/texlive app-text/texlive-core `eix -C dev-texlive -I --only-names` first. We got a new collision between dev-texlive/texlive-binextra-2023_p69527-r1 and app-text/texlive-core-2023-r3[xindy]: >>> Installing (8 of 25) dev-texlive/texlive-binextra-2023_p69527-r1::gentoo * checking 1151 files for package collisions * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at https://bugs.gentoo.org/ unless you report exactly * which two packages install the same file(s). See * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how * to solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/texmf-dist/xindy/VERSION * /usr/share/texmf-dist/xindy/modules/rules/latin-tolower.xdy * /usr/share/texmf-dist/xindy/modules/rules/isolatin1-tolower.xdy * /usr/share/texmf-dist/xindy/modules/rules/isolatin1-exchange.xdy * /usr/share/texmf-dist/xindy/modules/rules/latin-exchange.xdy * /usr/share/texmf-dist/xindy/modules/class/pagenums.xdy * /usr/share/texmf-dist/xindy/modules/ord/letorder.xdy * /usr/share/texmf-dist/xindy/modules/styles/makeidx.xdy * /usr/share/texmf-dist/xindy/modules/styles/basic.xdy * /usr/share/texmf-dist/xindy/modules/base/latex.xdy * /usr/share/texmf-dist/xindy/modules/base/makeindex.xdy * /usr/share/texmf-dist/xindy/modules/base/ignore-punctuation.xdy * /usr/share/texmf-dist/xindy/modules/base/german-sty.xdy * /usr/share/texmf-dist/xindy/modules/base/ff-ranges-only.xdy * /usr/share/texmf-dist/xindy/modules/base/page-ranges.xdy * /usr/share/texmf-dist/xindy/modules/base/numeric-sort.xdy * /usr/share/texmf-dist/xindy/modules/base/tex.xdy * /usr/share/texmf-dist/xindy/modules/base/latin-lettergroups.xdy * /usr/share/texmf-dist/xindy/modules/base/latex-loc-fmts.xdy * /usr/share/texmf-dist/xindy/modules/base/ff-ranges.xdy * /usr/share/texmf-dist/xindy/modules/base/texindy.xdy * /usr/share/texmf-dist/xindy/modules/base/book-order.xdy * /usr/share/texmf-dist/xindy/modules/base/word-order.xdy * /usr/share/texmf-dist/xindy/modules/base/letter-order.xdy * /usr/share/texmf-dist/xindy/modules/base/ignore-hyphen.xdy * /usr/share/texmf-dist/xindy/modules/base/keep-blanks.xdy * /usr/share/texmf-dist/xindy/modules/lang/korean/utf8-lang.xdy * /usr/share/texmf-dist/xindy/modules/lang/korean/utf8.xdy * /usr/share/texmf-dist/xindy/modules/lang/german/din5007.xdy * /usr/share/texmf-dist/xindy/modules/lang/german/tex.xdy * /usr/share/texmf-dist/xindy/modules/lang/german/duden.xdy * /usr/share/texmf-dist/xindy/modules/lang/latin/caseisrt.xdy * /usr/share/texmf-dist/xindy/modules/lang/latin/letgroup.xdy * /usr/share/texmf-dist/scripts/xindy/texindy.pl * /usr/share/texmf-dist/scripts/xindy/xindy.pl * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * app-text/texlive-core-2023-r3:0::gentoo * /usr/share/texmf-dist/xindy/VERSION * /usr/share/texmf-dist/xindy/modules/base/ff-ranges-only.xdy * /usr/share/texmf-dist/xindy/modules/base/ff-ranges.xdy * /usr/share/texmf-dist/xindy/modules/base/german-sty.xdy * /usr/share/texmf-dist/xindy/modules/base/ignore-punctuation.xdy * /usr/share/texmf-dist/xindy/modules/base/latex-loc-fmts.xdy * /usr/share/texmf-dist/xindy/modules/base/latex.xdy * /usr/share/texmf-dist/xindy/modules/base/latin-lettergroups.xdy * /usr/share/texmf-dist/xindy/modules/base/makeindex.xdy * /usr/share/texmf-dist/xindy/modules/base/numeric-sort.xdy * /usr/share/texmf-dist/xindy/modules/base/page-ranges.xdy * /usr/share/texmf-dist/xindy/modules/base/tex.xdy * /usr/share/texmf-dist/xindy/modules/class/pagenums.xdy * /usr/share/texmf-dist/xindy/modules/ord/letorder.xdy * /usr/share/texmf-dist/xindy/modules/rules/isolatin1-exchange.xdy * /usr/share/texmf-dist/xindy/modules/rules/isolatin1-tolower.xdy * /usr/share/texmf-dist/xindy/modules/rules/latin-exchange.xdy * /usr/share/texmf-dist/xindy/modules/rules/latin-tolower.xdy * /usr/share/texmf-dist/xindy/modules/styles/basic.xdy * /usr/share/texmf-dist/xindy/modules/styles/makeidx.xdy * * Package 'dev-texlive/texlive-binextra-2023_p69527-r1' NOT merged due * to file collisions. If necessary, refer to your elog messages for the * whole content of the above message. Note: I tried to use texlive-core[-xindy] to see if the copy from texlive-binextra can provide the needed functionality for downstream packages that need xindy. It did not work.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7b74a7ff0a0941e59f1d75c4363c9ccc612741b4 commit 7b74a7ff0a0941e59f1d75c4363c9ccc612741b4 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-03-08 09:46:58 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-03-08 09:51:06 +0000 texlive: move xindy and texdoctk from binextra into texlive-core xindy is enabled via texlive-core[xindy], causing collisions with xindy in binextra. Same goes for texdoctk, which is enabled via texlive-core[tk]. Bug: https://bugs.gentoo.org/836779 Signed-off-by: Florian Schmaus <flow@gentoo.org> app-text/texlive-core/Manifest | 4 ++++ .../{texlive-core-2023-r3.ebuild => texlive-core-2023-r4.ebuild} | 9 +++++++++ dev-texlive/texlive-binextra/Manifest | 4 ---- ...3_p69527-r1.ebuild => texlive-binextra-2023_p69527-r2.ebuild} | 4 ---- 4 files changed, 13 insertions(+), 8 deletions(-)
(In reply to François Bissey from comment #46) > We got a new collision between dev-texlive/texlive-binextra-2023_p69527-r1 > and app-text/texlive-core-2023-r3[xindy]: Thanks for your report. This should be fixed in the latest revisions of the related packages. Please report such issues a new bugs instead of commenting here. That keeps it easier for us to track open issues of the TexLive 2023 bump. Thanks.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ccd60dfebfc30c1e96414bc803ff6b5defa2ff77 commit ccd60dfebfc30c1e96414bc803ff6b5defa2ff77 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-03-28 21:26:15 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-03-28 21:26:56 +0000 profiles: remove texlive 2023 mask Closes: https://bugs.gentoo.org/836779 Signed-off-by: Florian Schmaus <flow@gentoo.org> profiles/package.mask | 62 --------------------------------------------------- 1 file changed, 62 deletions(-)
