texlive: 2018 -> 2019, poppler: 0.74.0 -> 0.81.0 #71419
Conversation
ofborg
bot
added
6.topic: TeX
|
@GrahamcOfBorg build texlive.bin |
veprbl
force-pushed
the
pr/texlive-2019
branch
from
bbd6cb0 to
9b55697
Compare
veprbl
force-pushed
the
pr/texlive-2019
branch
from
9b55697 to
5cea0ee
Compare
veprbl
changed the title
|
@GrahamcOfBorg build texlive.combined.scheme-small poppler cups-filters |
ofborg
bot
added
10.rebuild-darwin: 101-500
and removed
10.rebuild-darwin: 11-100
labels
|
So what really held back the other update (AFAIK) was our ongoing problem regarding hosting a snapshot of CTAN and our reliance on folks to provide hosting or no updates :(. Anyway there might be hope! Not to oversell but about a month ago this was sent to the list: https://tug.org/pipermail/tex-live/2019-September/044086.html I flagged it for next time I went back to texlive packaging, but I think this might allow us to do two huge improvements:
Apologies if I misjudged the implications, hope this helps and starts a new chapter of NixOS texlive goodness? 😁 |
|
@dtzWill This sounds good, however, upon reading into the messages [1][2], it doesn't seem like anywhere they imply that the old versions within a current release will be preserved. In any case this would be a step in the right direction. [1] https://tug.org/pipermail/tex-live/2019-August/044032.html |
Aww, was afraid it was something like that. Thanks for taking a look anyway :). |
Well, thank you for sharing, @dtzWill. I will certainly follow how this goes and see if in the end we can nudge them towards preserving the tarballs. |
|
nix-review on x86_64-linux (non-NixOS, no sandboxing)
|
|
nix-review on x86_64-darwin (no sandboxing)
|
|
Failures appear to be not relevant. I believe this PR should be okay to merge. |
|
|
This package is in the list of those that build successfully. |
|
Ah right sorry. I am a bit surprised that LibreOffice fails, though… |
|
Been using this for a while, at least the update portion! Sorry for slow review. Had trouble connecting to mirror address over the past 24 hours or so-- is the host still okay? Is there a not-the-worst way to share your snapshot such that one or more of us could try mirroring as well? Thanks for offering at all, I'll see what I can put together here too... :). But ideally we'd host the same content... :) |
I was messing with the server configuration last night, this is now fixed. Thanks.
I tried adding IPFS for texlive-2017, but AFAIK nobody joined that. I'm open to proposals, though.
@7c6f434c It failed on my machine during the test with IO exception while trying to write to the $TEMP. It builds just fine on NixOS with sandboxing. |
|
If it's in any way useful I've been using this as well and haven't encountered any issues so far. |
biber: 2.12 -> 2.13 Vendored potrace was moved from libs/potrace to texk/dvisvgm/dvisvgm-src/libs/potrace. Unfortunately, it is not trivial to remove it from there, so for now dvisvgm seems to be using its vendored dependencies.
veprbl
force-pushed
the
pr/texlive-2019
branch
from
5cea0ee to
deaaf82
Compare
|
Rebased on master to fix breakage in inkscape that happened after #72491 @GrahamcOfBorg build texlive.combined.scheme-small poppler cups-filters inkscape |
texlive: 2018 -> 2019, poppler: 0.74.0 -> 0.81.0 (cherry picked from commit 6fa62db)
For some context, this was previously and recently discussed: NixOS#61469 (comment) NixOS#71419 (comment) Fortunately it appears, due to developments since those discussion, that there is now a versioned mirror for ctan contents!! Naturally this commit is about moving to that mirror: updating the package lists and regenerating the hashes. This has two huge advantages: * Updating the pinned ctan packages can be done more frequently than the current "once a year". * We don't have to rely on community members to create a snapshot and mirror it indefinitely and at their own cost. Minor "advantage": * I should be writing but instead I was working on this :P It appears new, I stumbled upon a mention of it here[1]: > Native TL updates ultimately come from a directory named tlnet (on CTAN). > An archive for tlnet is available, with daily updates since > September 2019, and the final yearly release going back about ten years. [1] https://www.tug.org/texlive/pkginstall.html ---- Concerns and theirs status: * Package integrity: There may be concerns about ensuring the package hashes are obtained from a trusted source-- I haven't looked into this at all "yet". * Mirror reliability and not-abusing-nice-things-from-good-people If the mirror is a small operation it may be hostile to point the network request fury of the Nixpkgs texlive community ;). This doesn't appear to be the case and there's no mention of it, and presumably wouldn't be linked from tug.org if wasn't to be used? Would be good to chase down an announcement or otherwise ensure this is expected usage. Time will tell re:mirror reliability (or speed?), so far it seems like a solid service meant to be used and unlikely to be problematic. * Is the archive only updated once a day? The archive is organized by date, which is wonderful (!) but might mean the contents may see changes during the day. I suspect this is not the case but just a thought. Regardless, any problems seem easily avoided by simply not updating to the current day and use yesterday instead. ---- If this is the way we move forward, there are changes/fixes/improvements to be made in terms of documentation as well as (possibly) putting together some update automation tooling. --- I have only tested this with a single project so far, and it doesn't have any especially esoteric or demanding needs. Help testing by checking your projects to see that they build and produce expected results. Building against the before/after set and using `diffpdf` is how I usually vet these updates, if that's useful. The `diffpdf` especially helps identify the minor appearance changes I usually miss visually-- tweaks to microtype behavior or slightly different layout/placement of figures or handling of beamer slides, etc.
For some context, this was previously and recently discussed: NixOS#61469 (comment) NixOS#71419 (comment) Fortunately it appears, due to developments since those discussion, that there is now a versioned mirror for ctan contents!! Naturally this commit is about moving to that mirror: updating the package lists and regenerating the hashes. This has two huge advantages: * Updating the pinned ctan packages can be done more frequently than the current "once a year". * We don't have to rely on community members to create a snapshot and mirror it indefinitely and at their own cost. Minor "advantage": * I should be writing but instead I was working on this :P It appears new, I stumbled upon a mention of it here[1]: > Native TL updates ultimately come from a directory named tlnet (on CTAN). > An archive for tlnet is available, with daily updates since > September 2019, and the final yearly release going back about ten years. [1] https://www.tug.org/texlive/pkginstall.html ---- Concerns and theirs status: * Package integrity: There may be concerns about ensuring the package hashes are obtained from a trusted source-- I haven't looked into this at all "yet". * Mirror reliability and not-abusing-nice-things-from-good-people If the mirror is a small operation it may be hostile to point the network request fury of the Nixpkgs texlive community ;). This doesn't appear to be the case and there's no mention of it, and presumably wouldn't be linked from tug.org if wasn't to be used? Would be good to chase down an announcement or otherwise ensure this is expected usage. Time will tell re:mirror reliability (or speed?), so far it seems like a solid service meant to be used and unlikely to be problematic. * Is the archive only updated once a day? The archive is organized by date, which is wonderful (!) but might mean the contents may see changes during the day. I suspect this is not the case but just a thought. Regardless, any problems seem easily avoided by simply not updating to the current day and use yesterday instead. ---- If this is the way we move forward, there are changes/fixes/improvements to be made in terms of documentation as well as (possibly) putting together some update automation tooling. --- I have only tested this with a single project so far, and it doesn't have any especially esoteric or demanding needs. Help testing by checking your projects to see that they build and produce expected results. Building against the before/after set and using `diffpdf` is how I usually vet these updates, if that's useful. The `diffpdf` especially helps identify the minor appearance changes I usually miss visually-- tweaks to microtype behavior or slightly different layout/placement of figures or handling of beamer slides, etc. (cherry picked from commit 9c75eec)
For some context, this was previously and recently discussed: NixOS#61469 (comment) NixOS#71419 (comment) Fortunately it appears, due to developments since those discussion, that there is now a versioned mirror for ctan contents!! Naturally this commit is about moving to that mirror: updating the package lists and regenerating the hashes. This has two huge advantages: * Updating the pinned ctan packages can be done more frequently than the current "once a year". * We don't have to rely on community members to create a snapshot and mirror it indefinitely and at their own cost. Minor "advantage": * I should be writing but instead I was working on this :P It appears new, I stumbled upon a mention of it here[1]: > Native TL updates ultimately come from a directory named tlnet (on CTAN). > An archive for tlnet is available, with daily updates since > September 2019, and the final yearly release going back about ten years. [1] https://www.tug.org/texlive/pkginstall.html ---- Concerns and theirs status: * Package integrity: There may be concerns about ensuring the package hashes are obtained from a trusted source-- I haven't looked into this at all "yet". * Mirror reliability and not-abusing-nice-things-from-good-people If the mirror is a small operation it may be hostile to point the network request fury of the Nixpkgs texlive community ;). This doesn't appear to be the case and there's no mention of it, and presumably wouldn't be linked from tug.org if wasn't to be used? Would be good to chase down an announcement or otherwise ensure this is expected usage. Time will tell re:mirror reliability (or speed?), so far it seems like a solid service meant to be used and unlikely to be problematic. * Is the archive only updated once a day? The archive is organized by date, which is wonderful (!) but might mean the contents may see changes during the day. I suspect this is not the case but just a thought. Regardless, any problems seem easily avoided by simply not updating to the current day and use yesterday instead. ---- If this is the way we move forward, there are changes/fixes/improvements to be made in terms of documentation as well as (possibly) putting together some update automation tooling. --- I have only tested this with a single project so far, and it doesn't have any especially esoteric or demanding needs. Help testing by checking your projects to see that they build and produce expected results. Building against the before/after set and using `diffpdf` is how I usually vet these updates, if that's useful. The `diffpdf` especially helps identify the minor appearance changes I usually miss visually-- tweaks to microtype behavior or slightly different layout/placement of figures or handling of beamer slides, etc.
|
@alexvorobiev This should have been addressed by d6fdab5. |
Motivation for this change
Resolves: #60890
Fixes crash in #54286 (does not fix texdoc)
The original PR was done by @dtzWill in #61469. I redid the update from scratch to ensure that I understand all parts of it.
Things done
sandboxinnix.confon non-NixOS)nix-shell -p nix-review --run "nix-review wip"./result/bin/)nix path-info -Sbefore and after)Closes: #61469