-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TeXLive-texmf does not install on macOS 15 - Sequoia #1188
Comments
You need to make a separate texlive-texmf-15.0.info file that applies the luajittex patch (applying the patch doesn't need to be conditionalized then). This .info file needs to have a |
For cross-finding, here's the original thread on fink-users if people find one or the other: https://sourceforge.net/p/fink/mailman/fink-users/thread/E0A2991A-8669-4079-8B96-B8ADC899FC3A%40gmail.com/#msg58838145 |
@nieder you are right. I figured that out overnight (sleep helps). So I don't need a distribution list for the non 15.0-info file? Because I just use a big revision number so it takes precedent? And also for the texlive dependancy. I get it. |
Texlive is only at 20240312-1 and the v6.5 dependency is for
The texlive-texmf dependency is further down and versioned accordingly: fink-distributions/10.9-libcxx/stable/main/finkinfo/text/texlive.info Lines 360 to 364 in 51d1b05
You're right that for the non-15.0 .info files you don't need a |
Yes, it does execute them all independently, though running it under [ `sw_vers --productVersion | cut -d. -f1` -ge 15 ] && patch -d texmf-dist -p1 < %{PatchFile2} Don't know if that would make things easier than maintaining a separate Distribution version... Has anyone tested this on Sonoma? |
As @dhomeier said, {Patch/Compile/Test/Install}Script are evaluated as system() invocations per line unless everything is wrapped with a Here's the documentation Because we're turning off luajittex on 15.0, someone installing texlive-texmf on 14.0, then upgrading to 15, will have a broken texlive-texmf that will crash any attempt to install texlive (and I believe any other package that uses the texlive-texmf configurations) in PostInstScript. If they all have the same %v-%r (because they share a common .info), then the only way out is to rebuild texlive-texmf. By having a separate .info with a higher %r, an upgrader will still have a broken texlive-texmf and texlive until they install the new %r, but the reason why and fix will be clear from the .info rather than relying on someone remembering that bug reporters must rebuild to kill the bug. @sth0 if @dhomeier is not seeing the the problem on arm64, the new 15.0 info for texlive-texmf and texlive, can be set to have |
I think I have a valid texlive-texmf-15.0.info and am testing the texlive-15.0.info at the moment. I have set the revision value to 100 to force a rebuild for already installed versions on an upgrade. I was trying to bootstrap a new fink on my arm64 machine, but ran into problems with the latest Xcode. I will set the architecture value for both texlive-texmf-15.0.info and texlive-15.0.info to |
Building TexLive has one failing test now. Not sure how to tell the test setup to skip this one: |
Seems to be working and passes all tests see PR 1192 |
This is the old problem mentioned in issue #533 that luajittex and luajithbtex die with a segfault in macOS 15. I can reuse the patch that was done for that, but how does one create a conditional patch? The patch script does not seem to allow bourne shell syntax. So should the following patch script work to only patch macOS >=15 or do I need to make two separate distributions for texlive-texmf? One for 15.0 and on for 9->14?
It appears the patch script executes each line to its own shell?
The text was updated successfully, but these errors were encountered: