unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Ricardo Wurmus <rekado@elephly.net>, 64827@debbugs.gnu.org
Subject: bug#64827: texlive is broken
Date: Thu, 17 Aug 2023 14:10:57 +0200	[thread overview]
Message-ID: <ZN4OUZlhuHRYnJ5p@jurong> (raw)
In-Reply-To: <ZN4KkrrR1LErPnNT@jurong>

Am Thu, Aug 17, 2023 at 01:54:58PM +0200 schrieb Andreas Enge:
> Okay then, fine to remove biber again!

Done in wip-texlive-mono. I also dropped disabling tests for mips64,
as anyway we have no means of testing the architecture any more, so I see
no point in complicating the build recipe.

Where shall we go from here?

Are you okay with me either pushing the package in its own texlive module
where it is now, or moving the definition back into the tex module?
In either case it would probably be a good idea to make the texlivebin
and texlivetexmf variables private again.

Andreas





  reply	other threads:[~2023-08-17 12:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  9:52 bug#64827: Texlive-biber not installable Andreas Enge
     [not found] ` <handler.64827.B.169019239510118.ack@debbugs.gnu.org>
2023-07-24 10:11   ` bug#64827: Acknowledgement (Texlive-biber not installable) Andreas Enge
2023-07-24 22:09     ` Ricardo Wurmus
2023-07-25  8:42       ` bug#64827: Texlive has become slow Andreas Enge
2023-07-26 15:25         ` Nicolas Goaziou
2023-07-26 16:33           ` bug#64827: Texlive-biber not installable Andreas Enge
2023-07-26 18:17             ` Andreas Enge
2023-07-26 19:51               ` bug#64827: texlive is broken Andreas Enge
2023-07-26 21:21                 ` Andreas Enge
2023-07-26 22:43                   ` Andreas Enge
2023-07-27  9:55                     ` Nicolas Goaziou
2023-07-27 10:59                       ` Andreas Enge
2023-08-07 11:53                         ` Andreas Enge
2023-08-07 16:16                         ` Andreas Enge
2023-08-09  7:39                           ` Andreas Enge
2023-08-09 16:35                             ` Nicolas Goaziou
2023-08-09 19:02                               ` Andreas Enge
2023-08-13 20:48                                 ` Nicolas Goaziou
2023-08-17 11:54                                   ` Andreas Enge
2023-08-17 12:10                                     ` Andreas Enge [this message]
2023-08-17 13:17                                       ` Nicolas Goaziou
2023-08-17 14:31                                         ` Andreas Enge
2023-07-26 14:51     ` bug#64827: Acknowledgement (Texlive-biber not installable) Nicolas Goaziou
2023-07-26 15:02       ` Andreas Enge
2023-07-26 15:35         ` Nicolas Goaziou
2023-07-24 21:23 ` Igor Gajsin via Bug reports for GNU Guix
2023-07-24 21:28 ` bug#64827: (no subject) Igor Gajsin via Bug reports for GNU Guix
2023-08-16  0:15 ` bug#64827: Texlive-biber not installable Vinicius Monego
2023-08-16  9:25   ` Nicolas Goaziou

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=ZN4OUZlhuHRYnJ5p@jurong \
    --to=andreas@enge.fr \
    --cc=64827@debbugs.gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).