tudace / tuda_latex_templates

LaTeX Templates for TU Darmstadt
LaTeX Project Public License v1.3c
208 stars 71 forks source link

Move example files #467

Open TeXhackse opened 5 months ago

TeXhackse commented 5 months ago

the Example files have been moved back to their original location so the links in the CTAN Readme still work. This is my personal reminder to change that with the next update.

thrimbor commented 5 months ago

Moving the files also broke the prepare_tuda.sh script, which means the v3.37 release is broken (and clearly untested).

TeXhackse commented 5 months ago

@thrimbor The plan is to remove those with 4.0 as they are no longer required due to the l3build process.

TeXhackse commented 5 months ago

Out of curiosity: What did you use those for, as they were only part of out releasing progress.

thrimbor commented 5 months ago

I was trying to use an AUR package (https://aur.archlinux.org/packages/latex-tuda-ci, I know it's an external thing and not supported here, but it's the most convenient and clean way to install this under Arch Linux), which uses that script to build. I noticed the package didn't work properly, and found out it was empty, because the script failed and the error was ignored by the package building process.

TeXhackse commented 5 months ago

Thanks. Didn't know it used that.

As someone also using Arch I don't think it's the most convenient way ;-) I just attached my tlmgr updates to pacman via hooks.

Issue will still be, that the current development state of LaTeX concerning the support for tagged pdf always requires an up to date kernel… where the arch binary packages fail to keep updated. So there might be breaking things as the required kernel version will also increase.

freswa commented 5 months ago

I'm trying to fix the AUR package, but unfortunately the l3build process doesn't work for me. Bulding the docs with l3build doc leads to:

Package biblatex Warning: Please (re)run Biber on the file:
(biblatex)                DEMO-TUDaPhD-de
(biblatex)                and rerun LaTeX afterwards.

)
(see the transcript file for additional information)
 8012 words of node memory still in use:
   87 hlist, 10 vlist, 13 rule, 55 disc, 23 local_par, 6 math, 186 glue, 51 ker
n, 36 penalty, 6 margin_kern, 452 glyph, 278 attribute, 66 glue_spec, 145 attri
bute_list, 3 write, 2 pdf_action, 28 pdf_colorstack, 1 pdf_setmatrix, 1 pdf_sav
e, 1 pdf_restore nodes
   avail lists: 1:3,2:1064,3:373,4:132,5:637,6:128,7:5519,8:131,9:516,10:9,11:5
56,12:1
</usr/share/texmf-dist/fonts/opentype/public/xcharter/XCharter-Bold.otf></usr/s
hare/texmf-dist/fonts/opentype/google/roboto/RobotoMono-Regular.otf></usr/share
/texmf-dist/fonts/opentype/public/xcharter/XCharter-Roman.otf></usr/share/texmf
-dist/fonts/opentype/google/roboto/Roboto-Bold.otf></usr/share/texmf-dist/fonts
/opentype/google/roboto/Roboto-Regular.otf></usr/share/texmf-dist/fonts/type1/p
ublic/amsfonts/cm/cmsy10.pfb>
Output written on DEMO-TUDaPhD-de.pdf (25 pages, 614693 bytes).
Transcript written on DEMO-TUDaPhD-de.log.
INFO - This is Biber 2.19
INFO - Logfile is 'DEMO-TUDaPhD-de.blg'
INFO - Reading 'DEMO-TUDaPhD-de.bcf'
INFO - Found 2 citekeys in bib section 0
INFO - Processing section 0
INFO - Looking for bibtex file 'DEMO-TUDaBibliography' for section 0
ERROR - Cannot find 'DEMO-TUDaBibliography'!
INFO - ERRORS: 1
 ! Compilation failed

Any clue?

TeXhackse commented 5 months ago

Yes. there are reasons 4.0 is not yet released. any work you include into that now will be broken with 4.0 as this is a complete refactoring … that's why its taking that long. I may explain that within the office hour but don't have time for details atm. sorry.

freswa commented 5 months ago

The error happens with the 3.37 release tarball. But no need to rush, I've excluded the docs temporarily.

TeXhackse commented 5 months ago

The tarball is not the files released. Please not that the repo includes more than just the CTAN release files.

In case you want the 3.37 take the zip attached to the release or that from CTAN.

edit: and 3.37 was a rush-release which I enforced to build like 3.36 did, as there was a requirement to not wait any longer with that. I know that 4.0 takes longer than intended and actually 90% of the work in the 4.0 refactoring are done within my free time but the intention is to have to more compatible and easier to maintain in the future.