Summary: | dev-texlive/texlive-context-2023_p69108 failed to emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Leonid Kopylov <leonchik1976> |
Component: | Current packages | Assignee: | Alexis Ballier <aballier> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | flow, jstein, leonchik1976, tex |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=933520 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
emerge-info.txt |
Description
Leonid Kopylov
2024-03-29 11:20:34 UTC
Created attachment 889003 [details]
build.log
Is the USE flag 'luajittex' enabled on app-text/texlive-core? If not, could you enable it and see if this allows you to emerge texlive-context? (In reply to Florian Schmaus from comment #2) > Is the USE flag 'luajittex' enabled on app-text/texlive-core? If not, could > you enable it and see if this allows you to emerge texlive-context? # emerge texlive-core -pvq [ebuild R ] app-text/texlive-core-2023-r5 USE="X doc source tk xetex -cjk (-luajittex) (-xindy)" it masked Could you add the output of `emerge --info` to the attachments of this bug? Created attachment 889012 [details]
emerge-info.txt
You are most likely hitting the following package.use.mask: https://github.com/gentoo/gentoo/blob/a9670d41c7d9966978d056549255280f2a409ad8/profiles/arch/arm64/package.use.mask#L367-L371 Given that the mask is from 2018, and regardless if this can be considered the proper fix of the bug, I wonder if this mask is still valid for texlive 2023. Could I bribe you into locally unmasking the mask and see if luajittex works on arm64? That said, I wonder if the correct fix for the issue is to convince fmtutil to not build stuff for engines that aren't available. However, as of now, I have not really an idea how this would work. Therefore, I would need more time to look into it. It still would be nice if you could test luajittex on arm64. That would be much appreciated. (In reply to Florian Schmaus from comment #6) > You are most likely hitting the following package.use.mask: > https://github.com/gentoo/gentoo/blob/ > a9670d41c7d9966978d056549255280f2a409ad8/profiles/arch/arm64/package.use. > mask#L367-L371 > > Given that the mask is from 2018, and regardless if this can be considered > the proper fix of the bug, I wonder if this mask is still valid for texlive > 2023. > > Could I bribe you into locally unmasking the mask and see if luajittex works > on arm64? > > That said, I wonder if the correct fix for the issue is to convince fmtutil > to not build stuff for engines that aren't available. However, as of now, I > have not really an idea how this would work. Therefore, I would need more > time to look into it. > > It still would be nice if you could test luajittex on arm64. That would be > much appreciated. after unmasking, these rebuild with USE=luajittex: # emerge texlive-core texlive-basic -pvq [ebuild R ] app-text/texlive-core-2023-r5 USE="X doc luajittex source tk xetex -cjk (-xindy)" [ebuild R ] dev-texlive/texlive-basic-2023_p59159-r2 USE="doc luajittex source" and..success: # emerge =dev-texlive/texlive-context-2023_p69108 -pvq [ebuild R ] dev-texlive/texlive-context-2023_p69108 USE="doc source" The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1bca88987927e0aa8a8b4f7a99c912b27d971a59 commit 1bca88987927e0aa8a8b4f7a99c912b27d971a59 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-03-29 17:18:18 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-03-29 17:18:28 +0000 dev-texlive/texlive-context: set TEXLIVE_MODULE_OPTIONAL_ENGINE=luajittex Closes: https://bugs.gentoo.org/928122 Signed-off-by: Florian Schmaus <flow@gentoo.org> dev-texlive/texlive-context/metadata.xml | 3 +++ ...ntext-2023_p69108.ebuild => texlive-context-2023_p69108-r1.ebuild} | 4 +++- 2 files changed, 6 insertions(+), 1 deletion(-) The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fa6fadb1b7323f22a157b769d4d383ef439ee2f2 commit fa6fadb1b7323f22a157b769d4d383ef439ee2f2 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-06-05 12:05:06 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-06-05 12:18:03 +0000 dev-texlive/texlive-{basic,context}: move luajittex from -context into -basic The motivation for this change is a little bit complex. The gist is, that luajittex belongs into -basic, even though tlpdb lists luajittex in collection-context for Tex Live 2023 (and probably in collection-binextra for TeX Live 2024). In Gentoo, texlive-basic had already luajittex in IUSE, at least since TeX Live 2021. And this seems sensible. We can not easily put the luajittex TeX Live package in app-text/texlive-core, even though we *build* luajit(hb)tex there. But the luajittex TeX Live package also has a AddFormat directive in its tlpobj, which we do not process in texlive-core. This is mostly because texilve-core only inherits texlive-common.eclass, but the tlpojb processing, including the AddFormat processing, is done by texlive-module.eclass. Therefore, we put luajittex in texlive-basic, since this will always be installed and the texlive-basic ebuilds processes luajits AddFormat directive, because it inherits texlive-module.eclass. Closes: https://bugs.gentoo.org/933520 Bug: https://bugs.gentoo.org/928122 Fixes: 1bca88987927 ("dev-texlive/texlive-context: set TEXLIVE_MODULE_OPTIONAL_ENGINE=luajittex") Signed-off-by: Florian Schmaus <flow@gentoo.org> dev-texlive/texlive-basic/Manifest | 2 ++ ...23_p59159-r3.ebuild => texlive-basic-2023_p59159-r4.ebuild} | 10 ++++++++++ dev-texlive/texlive-context/Manifest | 2 -- dev-texlive/texlive-context/metadata.xml | 3 --- ..._p69108-r2.ebuild => texlive-context-2023_p69108-r3.ebuild} | 6 +----- 5 files changed, 13 insertions(+), 10 deletions(-) |