unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: phodina via <help-guix@gnu.org>
To: help-guix <help-guix@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Ricardo Wurmus" <rekado@elephly.net>
Subject: Tex packages on core-updates failing
Date: Thu, 21 Apr 2022 10:43:28 +0000	[thread overview]
Message-ID: <cdn3YlYn3hiXW3iUsKkuZ9S6h6zUi6zdP1zvp513VuYVQR-xcbwkpszSm8DNcfksHZgoUedvCs_tqoPVhN-UYkn2U8C0sezaY6mjnbzxpDU=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]

Hi,

I'm attempting to build packages on branch core-updates (3f2b0e12f1ef0cc9e13d5ae00275fee8a0fa752d) and it seems some tex packages are broken.

I've attempted to fix one of them - texlive-amsmath - but there's another failing - texlive-psnfss-fixed.

I've found issue and applied patches about texlive-psnfss but now it does not build. [1]

Could you please help?

[1] https://issues.guix.gnu.org/53454#6

----
Petr

[-- Attachment #2: d9270jmvap4fjl8dlj0fr2k8vlgs16-texlive-psnfss-fixed-59745.drv.gz --]
[-- Type: application/gzip, Size: 5565 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: texlive-amsmath.patch --]
[-- Type: text/x-patch; name=texlive-amsmath.patch, Size: 1367 bytes --]

diff --git a/gnu/packages/tex.scm b/gnu/packages/tex.scm
index 7fab21679e..c39a568e2b 100644
--- a/gnu/packages/tex.scm
+++ b/gnu/packages/tex.scm
@@ -4168,11 +4168,15 @@ (define-public texlive-amsmath
              (add-before 'copy-files 'unchdir
                (lambda _
                  (chdir "../../..")))
-             (add-after 'copy-files 'delete-extra-files
-               (lambda* (#:key outputs #:allow-other-keys)
-                 (delete-file-recursively
-                  (string-append (assoc-ref outputs "out")
-                                 "/share/texmf-dist/source/latex/amsmath/build"))))))))
+             (replace 'copy-files
+               (lambda* (#:key inputs outputs #:allow-other-keys)
+                 (let ((origin (assoc-ref inputs "source"))
+                       (source (string-append (assoc-ref outputs "out")
+                                              "/share/texmf-dist/source"))
+                       (doc (string-append (assoc-ref outputs "doc")
+                                           "/share/texmf-dist/doc")))
+                   (copy-recursively (string-append origin "/source") source)
+                   (copy-recursively (string-append origin "/doc") doc))))))))
       (home-page "https://www.ctan.org/pkg/amsmath")
       (synopsis "AMS mathematical facilities for LaTeX")
       (description

             reply	other threads:[~2022-04-21 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 10:43 phodina via [this message]
2022-04-22  4:17 ` Tex packages on core-updates failing Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='cdn3YlYn3hiXW3iUsKkuZ9S6h6zUi6zdP1zvp513VuYVQR-xcbwkpszSm8DNcfksHZgoUedvCs_tqoPVhN-UYkn2U8C0sezaY6mjnbzxpDU=@protonmail.com' \
    --to=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --cc=phodina@protonmail.com \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).