-
Notifications
You must be signed in to change notification settings - Fork 43
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
\gre@ifnotlatex raises error in gregoriotex-symbols.tex (l. 239) #1241
Comments
I downloaded exemples.zip and tried to process Magnificat.tex. I couldn't get lyluatex to work, so I commented out Is there some other example I should look at? |
You'll find a document that shows the error in this archive. |
I'm unable to reproduce the problem with that archive, either. Perhaps someone else can try. |
Here is a MWE which, on my system, raises the error :
Ater investigating a little, it seems the problem would be Debian/Ubuntu specific : I've installed gregorio and gregoriotex 4.2 (from ppa), but gregorio(tex) 4.1 comes with standard TexLive as packaged for Debian/Ubuntu : so I've got gregoriotex 4.1 in What I don't understand is that, when I type |
Does your log file show that the wrong gregoriosyms.sty or gregoriotex.sty is being picked up? Perhaps you can attach the log file? It might be helpful if you (after restoring the files to the non-working state) run the contrib/system-setup.command and attach the output of that script as well. This is sounding less like a Gregorio bug than a TeX Live bug or (perhaps) a Debian/Ubuntu packaging bug. |
Here is the log. You'll effectively see that |
What do |
|
I'll try to set up a VM so I can try to reproduce what you are seeing, but perhaps @rpspringuel or @eroux will have some ideas, since this looks like a kpse issue. |
Please run system-setup.command (found in the contrib folder) and post the results. |
@henryso If you use docker, you could use this docker image to reproduce the error : https://hub.docker.com/r/musite/gregorio/ @rpspringuel Here is the content of
|
@jperon Please supply the output of If this does not return If, after moving the files, the |
Here you are :
Though the firs line is good, I've tested copying |
OK, thank you. This is a bug in the Debian scripts. The |
Which version should we target for this fix? |
Since this is a packaging bug, if we are going to re-release 4.2.0 as in #1233, I think we can make the fix in master. @eroux, @rpspringuel, what do you think? |
I agree that a packaging bug is ripe for inclusion in some subsequent 4.2 release. I do not, however, favor a rerelease as this involves moving the v4.2.0 tag and that is generally a hassel (it's doable, but annoying). I would prefer to make a v4.2.1 release which collects this fix and the one in #1233 (and possibly others that might come up between now and whenever we make the release). Also, I should point out that I will not have time to make a released (be it a re-release or a bugfix) before October 16th and probably not until the following weekend (October 21st and 22nd). My solemn profession is on October 16th and I have a whole lot to do between now and then to get ready while also keeping up with my school work. |
Looking at the |
You may have an example of this error by visiting this page ; commenting out lines 239 to end makes it disappear.
The text was updated successfully, but these errors were encountered: