Version problems with CLI 2.25.1
26 views
Skip to first unread message
Sean Fitzpatrick
Aug 7, 2025, 11:42:59 AMAug 7
to PreTeXt support
An old ghost has re-emerged with CLI 2.25.1:
I am using versions with a number of different components to facilitate production of different versions.
In some cases the same element will appear twice, but in different components.
A couple of years ago, this broke building because CodeChat didn't like seeing a duplicate ID. I don't know if it's due to CodeChat, but the same error is back:
critical: ID vid_deriv_apps_taylor_poly_defn already defined, line 436, column 87
This ID does appear twice, but in different components. I'm not sure if the error is due to the xml:id on the figure, or the label on the video.
Sean Fitzpatrick
Aug 7, 2025, 11:52:11 AMAug 7
to PreTeXt support
The context here is that APEX has "early" and "late" Taylor polynomials: at Lethbridge we teach Taylor polynomials in Calc 1, right after differentials.
The original presentation explains the formula for the coefficients as a solution to an initial value problem, but that context doesn't make sense in Chapter 4, so I had to re-write the motivation.
This leads to a number of elements in that section being duplicated, but as part of different components.
In the past this wasn't a problem, other than a complaint about this breaking CodeChat.
Sean Fitzpatrick
Aug 7, 2025, 2:28:34 PMAug 7
to PreTeXt support
Additional nit to pick:
I had to comment out the section on Taylor polynomials to be able to build, which of course meant breaking some references from other sections.
This is now being logged by the CLI as a "CRITICAL" error.
I think this is misleading: everything will build fine; there is just going to be one ugly-looking undefined reference.
Rob Beezer
Aug 7, 2025, 2:45:26 PMAug 7
to pretext...@googlegroups.com
My understanding is that duplicate @xml:id *in the same file* will raise an
error by the processor. Not sure if that impedes further processing.
The CLI is perhaps raising this to something critical.
We check for duplicate @xml:id and duplicate @label, document-wide, *after* a
version is formed.
You don't want to do this: put your two versions with the same @xml:id into
their own files and "xi:include" them. The processor might not "see" the
duplication?
I'm doing "early" and "late" with FCLA, and I think I have the same siutation
(logical arrangment of material). I can look closer later if you want me to.
Rob
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-suppo...@googlegroups.com <mailto:pretext-
> support+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> support/15ab7acb-4de1-4966-ba66-6221fe40099cn%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966-
> ba66-6221fe40099cn%40googlegroups.com?utm_medium=email&utm_source=footer>.
error by the processor. Not sure if that impedes further processing.
The CLI is perhaps raising this to something critical.
We check for duplicate @xml:id and duplicate @label, document-wide, *after* a
version is formed.
You don't want to do this: put your two versions with the same @xml:id into
their own files and "xi:include" them. The processor might not "see" the
duplication?
I'm doing "early" and "late" with FCLA, and I think I have the same siutation
(logical arrangment of material). I can look closer later if you want me to.
Rob
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-suppo...@googlegroups.com <mailto:pretext-
> support+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> support/15ab7acb-4de1-4966-ba66-6221fe40099cn%40googlegroups.com <https://
> groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966-
> ba66-6221fe40099cn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Sean Fitzpatrick
Aug 7, 2025, 2:49:57 PMAug 7
to pretext...@googlegroups.com
Was there a recent change in how assembly works? This has been building fine for the last year or so.
My old solution was to have two files:
sec_taylor_poly_early.ptx
and
sec_taylor_poly_late.ptx
But then I had to remember to do any edits twice when working on that section.
I could use different IDs for different versions, but then I'd have to duplicate any paragraphs where those IDs are referenced, to have one for each version referencing the different IDs.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/MTAwMDA0Ny5iZWV6ZXI.1754592323%40pnsh.
Rob Beezer
Aug 7, 2025, 3:12:10 PMAug 7
to pretext...@googlegroups.com
Define "recent" and define "works". ;-)
I don't know if there are changes that would explain this! That's why we make
very careful commit messages. Or use "git bisect"?
But really, the error comes before we do any processing of our own (hence we
can't control it), so I am really tempted to just point the finger at your
source, until you can roll back PTX and show the identical source behaving
better at some old commit.
> I could use different IDs for different versions, but then I'd have to duplicate
> any paragraphs where those IDs are referenced, to have one for each version
> referencing the different IDs.
I think that is what I did with FCLA. I balked at first, but in a way it makes
sense - you are forced to locate the relevant #xref and maybe you really need to
say something different in the two cases in the vicinity of the #xref? (Right -
perhaps never. But you are forced to consider the possibiity.)
Rob
On 8/7/25 11:49, Sean Fitzpatrick wrote:
> Was there a recent change in how assembly works? This has been building fine for
> the last year or so.
>
> My old solution was to have two files:
> sec_taylor_poly_early.ptx
> and
> sec_taylor_poly_late.ptx
>
> But then I had to remember to do any edits twice when working on that section.
>
> I could use different IDs for different versions, but then I'd have to duplicate
> any paragraphs where those IDs are referenced, to have one for each version
> referencing the different IDs.
>
> support%2Bunsu...@googlegroups.com> <mailto:pretext- <mailto:pretext->
> > support+u...@googlegroups.com
> <mailto:support%2Bunsu...@googlegroups.com>>.
> > support/15ab7acb-4de1-4966-ba66-6221fe40099cn%40googlegroups.com
> <http://40googlegroups.com> <https://
> > groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966- <http://
> groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966->
> > ba66-6221fe40099cn%40googlegroups.com?utm_medium=email&utm_source=footer
> <http://40googlegroups.com?utm_medium=email&utm_source=footer>>.
> support%2Bunsu...@googlegroups.com>.
> msgid/pretext-support/MTAwMDA0Ny5iZWV6ZXI.1754592323%40pnsh>.
> groups.google.com/d/msgid/pretext-support/
> CAH%2BNcPafu0edhOc36zQkv9QEbBkwBtnhLusqmp7QReLuWe9JmA%40mail.gmail.com?
> utm_medium=email&utm_source=footer>.
I don't know if there are changes that would explain this! That's why we make
very careful commit messages. Or use "git bisect"?
But really, the error comes before we do any processing of our own (hence we
can't control it), so I am really tempted to just point the finger at your
source, until you can roll back PTX and show the identical source behaving
better at some old commit.
> I could use different IDs for different versions, but then I'd have to duplicate
> any paragraphs where those IDs are referenced, to have one for each version
> referencing the different IDs.
sense - you are forced to locate the relevant #xref and maybe you really need to
say something different in the two cases in the vicinity of the #xref? (Right -
perhaps never. But you are forced to consider the possibiity.)
Rob
On 8/7/25 11:49, Sean Fitzpatrick wrote:
> Was there a recent change in how assembly works? This has been building fine for
> the last year or so.
>
> My old solution was to have two files:
> sec_taylor_poly_early.ptx
> and
> sec_taylor_poly_late.ptx
>
> But then I had to remember to do any edits twice when working on that section.
>
> I could use different IDs for different versions, but then I'd have to duplicate
> any paragraphs where those IDs are referenced, to have one for each version
> referencing the different IDs.
>
> > support+u...@googlegroups.com
> <mailto:support%2Bunsu...@googlegroups.com>>.
> > To view this discussion visit https://groups.google.com/d/msgid/pretext-
> <https://groups.google.com/d/msgid/pretext->
> > support/15ab7acb-4de1-4966-ba66-6221fe40099cn%40googlegroups.com
> <http://40googlegroups.com> <https://
> > groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966- <http://
> groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966->
> > ba66-6221fe40099cn%40googlegroups.com?utm_medium=email&utm_source=footer
> <http://40googlegroups.com?utm_medium=email&utm_source=footer>>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-suppo...@googlegroups.com <mailto:pretext-
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> support%2Bunsu...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> support/MTAwMDA0Ny5iZWV6ZXI.1754592323%40pnsh <https://groups.google.com/d/
> msgid/pretext-support/MTAwMDA0Ny5iZWV6ZXI.1754592323%40pnsh>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-suppo...@googlegroups.com <mailto:pretext-
> support+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-support/
> CAH%2BNcPafu0edhOc36zQkv9QEbBkwBtnhLusqmp7QReLuWe9JmA%40mail.gmail.com <https://
> support+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-support/
> groups.google.com/d/msgid/pretext-support/
> CAH%2BNcPafu0edhOc36zQkv9QEbBkwBtnhLusqmp7QReLuWe9JmA%40mail.gmail.com?
> utm_medium=email&utm_source=footer>.
Sean Fitzpatrick
Aug 7, 2025, 3:29:24 PMAug 7
to pretext...@googlegroups.com
Looking back on -dev, it looks like things broke for me mid July of last year.
LaTeX built fine, HTML built fine with the devscript, but not the CLI.
We figured out that codechat was the culprit, and Oscar fixed things in CLI 2.5.2. I've been building without issue until today. (So just over a year without issues.)
I'll test other build options later today to see if this might be the same thing.
This is going to break builds of APEX on Runestone if Brad is using the most recent CLI, so I'd better track it down soon!
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/MTAwMDAxMy5iZWV6ZXI.1754593927%40pnsh.
Rob Beezer
Aug 7, 2025, 3:39:18 PMAug 7
to pretext...@googlegroups.com
I'd be surprised if CodeChat was very aware of our versions.
And I think it always assumed that the modularization of source files matched
the document structure (chapters, sections,...).
So I was never too optimistic that it was going to work out, and I suspect its
use with PreTeXt it is not being maintained at present.
Rob
On 8/7/25 12:29, Sean Fitzpatrick wrote:
> Looking back on -dev, it looks like things broke for me mid July of last year.
> LaTeX built fine, HTML built fine with the devscript, but not the CLI.
>
> We figured out that codechat was the culprit, and Oscar fixed things in CLI
> 2.5.2. I've been building without issue until today. (So just over a year
> without issues.)
>
> I'll test other build options later today to see if this might be the same thing.
>
> This is going to break builds of APEX on Runestone if Brad is using the most
> recent CLI, so I'd better track it down soon!
>
> On Thu, Aug 7, 2025, 1:12 p.m. 'Rob Beezer' via PreTeXt support <pretext-
> > sup...@googlegroups.com <mailto:sup...@googlegroups.com>
> <mailto:pretext...@googlegroups.com <mailto:pretext-
> > support%2Bunsu...@googlegroups.com
> <mailto:support%252Buns...@googlegroups.com>> <mailto:pretext-
> <mailto:pretext-> <mailto:pretext- <mailto:pretext->>
> > > support+u...@googlegroups.com
> <mailto:support%2Bunsu...@googlegroups.com>
> > <mailto:support%2Bunsu...@googlegroups.com
> <mailto:support%252Buns...@googlegroups.com>>>.
> groups.google.com/d/msgid/pretext->>
> > > support/15ab7acb-4de1-4966-ba66-6221fe40099cn%40googlegroups.com
> <http://40googlegroups.com>
> > <http://40googlegroups.com <http://40googlegroups.com>> <https://
> > > groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966-
> <http://groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966-> <http://
> <mailto:pretext->
> > support%2Bunsu...@googlegroups.com
> <mailto:support%252Buns...@googlegroups.com>>.
> groups.google.com/d/ <https://groups.google.com/d/>
> > CAH%2BNcPafu0edhOc36zQkv9QEbBkwBtnhLusqmp7QReLuWe9JmA%40mail.gmail.com
> <http://40mail.gmail.com> <https://
> > groups.google.com/d/msgid/pretext-support/ <http://groups.google.com/d/
> msgid/pretext-support/>
> > CAH%2BNcPafu0edhOc36zQkv9QEbBkwBtnhLusqmp7QReLuWe9JmA%40mail.gmail.com
> <http://40mail.gmail.com>?
> msgid/pretext-support/MTAwMDAxMy5iZWV6ZXI.1754593927%40pnsh>.
> <https://groups.google.com/d/msgid/pretext-support/
> CAH%2BNcPZ2W%2BY7cefY41FwtHsVhtY7VV5RA8DA%3D9EJPs0AZOBGkQ%40mail.gmail.com?
> utm_medium=email&utm_source=footer>.
And I think it always assumed that the modularization of source files matched
the document structure (chapters, sections,...).
So I was never too optimistic that it was going to work out, and I suspect its
use with PreTeXt it is not being maintained at present.
Rob
On 8/7/25 12:29, Sean Fitzpatrick wrote:
> Looking back on -dev, it looks like things broke for me mid July of last year.
> LaTeX built fine, HTML built fine with the devscript, but not the CLI.
>
> We figured out that codechat was the culprit, and Oscar fixed things in CLI
> 2.5.2. I've been building without issue until today. (So just over a year
> without issues.)
>
> I'll test other build options later today to see if this might be the same thing.
>
> This is going to break builds of APEX on Runestone if Brad is using the most
> recent CLI, so I'd better track it down soon!
>
> <mailto:pretext...@googlegroups.com <mailto:pretext-
> <mailto:support%252Buns...@googlegroups.com>> <mailto:pretext-
> <mailto:pretext-> <mailto:pretext- <mailto:pretext->>
> > > support+u...@googlegroups.com
> <mailto:support%2Bunsu...@googlegroups.com>
> > <mailto:support%2Bunsu...@googlegroups.com
> <mailto:support%252Buns...@googlegroups.com>>>.
> > > To view this discussion visit https://groups.google.com/d/msgid/
> pretext- <https://groups.google.com/d/msgid/pretext->
> > <https://groups.google.com/d/msgid/pretext- <https://
> pretext- <https://groups.google.com/d/msgid/pretext->
> groups.google.com/d/msgid/pretext->>
> > > support/15ab7acb-4de1-4966-ba66-6221fe40099cn%40googlegroups.com
> <http://40googlegroups.com>
> > <http://40googlegroups.com <http://40googlegroups.com>> <https://
> > > groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966-
> <http://groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966-> <http://
> > groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966- <http://
> groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966->>
> > > ba66-6221fe40099cn%40googlegroups.com?
> utm_medium=email&utm_source=footer <http://40googlegroups.com?
> utm_medium=email&utm_source=footer>
> > <http://40googlegroups.com?utm_medium=email&utm_source=footer
> groups.google.com/d/msgid/pretext-support/15ab7acb-4de1-4966->>
> > > ba66-6221fe40099cn%40googlegroups.com?
> utm_medium=email&utm_source=footer <http://40googlegroups.com?
> utm_medium=email&utm_source=footer>
> <http://40googlegroups.com?utm_medium=email&utm_source=footer>>>.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "PreTeXt support" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to pretext-suppo...@googlegroups.com
> <mailto:pretext-support%2Bunsu...@googlegroups.com> <mailto:pretext-
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "PreTeXt support" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to pretext-suppo...@googlegroups.com
> <mailto:pretext->
> > support%2Bunsu...@googlegroups.com
> <mailto:support%252Buns...@googlegroups.com>>.
> > To view this discussion visit https://groups.google.com/d/msgid/
> pretext- <https://groups.google.com/d/msgid/pretext->
> > support/MTAwMDA0Ny5iZWV6ZXI.1754592323%40pnsh <https://
> pretext- <https://groups.google.com/d/msgid/pretext->
> groups.google.com/d/ <https://groups.google.com/d/>
> > msgid/pretext-support/MTAwMDA0Ny5iZWV6ZXI.1754592323%40pnsh>.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "PreTeXt support" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> email
> > to pretext-suppo...@googlegroups.com <mailto:pretext-
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "PreTeXt support" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > to pretext-suppo...@googlegroups.com <mailto:pretext-
> support%2Bunsu...@googlegroups.com> <mailto:pretext- <mailto:pretext->
> > support+u...@googlegroups.com
> <mailto:support%2Bunsu...@googlegroups.com>>.
> > To view this discussion visit https://groups.google.com/d/msgid/pretext-
> support/ <https://groups.google.com/d/msgid/pretext-support/>
> > support+u...@googlegroups.com
> <mailto:support%2Bunsu...@googlegroups.com>>.
> > To view this discussion visit https://groups.google.com/d/msgid/pretext-
> > CAH%2BNcPafu0edhOc36zQkv9QEbBkwBtnhLusqmp7QReLuWe9JmA%40mail.gmail.com
> <http://40mail.gmail.com> <https://
> > groups.google.com/d/msgid/pretext-support/ <http://groups.google.com/d/
> msgid/pretext-support/>
> > CAH%2BNcPafu0edhOc36zQkv9QEbBkwBtnhLusqmp7QReLuWe9JmA%40mail.gmail.com
> <http://40mail.gmail.com>?
> > utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pretext-suppo...@googlegroups.com <mailto:pretext-
> support%2Bunsu...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> support/MTAwMDAxMy5iZWV6ZXI.1754593927%40pnsh <https://groups.google.com/d/
> support%2Bunsu...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-
> msgid/pretext-support/MTAwMDAxMy5iZWV6ZXI.1754593927%40pnsh>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-suppo...@googlegroups.com <mailto:pretext-
> support+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-support/
> CAH%2BNcPZ2W%2BY7cefY41FwtHsVhtY7VV5RA8DA%3D9EJPs0AZOBGkQ%40mail.gmail.com
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to pretext-suppo...@googlegroups.com <mailto:pretext-
> support+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/pretext-support/
> <https://groups.google.com/d/msgid/pretext-support/
> CAH%2BNcPZ2W%2BY7cefY41FwtHsVhtY7VV5RA8DA%3D9EJPs0AZOBGkQ%40mail.gmail.com?
> utm_medium=email&utm_source=footer>.
Rob Beezer
Aug 7, 2025, 5:40:58 PMAug 7
to pretext...@googlegroups.com
> but then I'd have to duplicate any paragraphs where those IDs are referenced,
to have one for each version referencing the different IDs.
Don't duplicate the paragraph, just line up two #xref right next to each other,
to have one for each version referencing the different IDs.
and put them into the two separate components?
Sean Fitzpatrick
Aug 7, 2025, 5:43:55 PMAug 7
to PreTeXt support
Right. I wasn't sure if xref would take component as an attribute.
I just downgraded to 2.24.0, and I'm able to build without any errors, despite having the duplicate IDs in different components.
So there is some change between 2.24.0 and 2.25.1 that doesn't like me having the same ID in two different components.
Rob Beezer
Aug 7, 2025, 6:07:17 PMAug 7
to pretext...@googlegroups.com
On 8/7/25 14:43, Sean Fitzpatrick wrote:
> Right. I wasn't sure if xref would take component as an attribute.
@component can go on just about anything.
> Right. I wasn't sure if xref would take component as an attribute.
> I just downgraded to 2.24.0, and I'm able to build without any errors, despite
> having the duplicate IDs in different components.
> So there is some change between 2.24.0 and 2.25.1 that doesn't like me having
> the same ID in two different components.
And if it fails there, you could use "git bisect".
Oscar Levin
Aug 7, 2025, 6:51:21 PMAug 7
to PreTeXt support
I can confirm that this broke starting with 2.25.0. I'll look into why later tonight. We did some refactoring of sniffing errors from core and making that exit, but I'm surprised this is happening.
Sean Fitzpatrick
Aug 7, 2025, 9:01:22 PMAug 7
to pretext...@googlegroups.com
I'll try to do some testing tomorrow but I'll be working around kids at home.
I can modify my source to work around this if necessary.
--
You received this message because you are subscribed to the Google Groups "PreTeXt support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/9e5feb69-131e-4733-96ad-3476cbd25020n%40googlegroups.com.
Oscar Levin
Aug 7, 2025, 11:12:32 PMAug 7
to PreTeXt support
I think I found the bug, or at least where it lives. Should be able to sort it out tomorrow morning and get a patch of the cli out soon after.
Reply all
Reply to author
Forward
0 new messages