unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>, Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel@gnu.org
Subject: Re: How to keep biber working
Date: Mon, 21 Oct 2019 17:44:35 +0200	[thread overview]
Message-ID: <878spe9k7w.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87h842jfqt.fsf@elephly.net>

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

Ricardo Wurmus <rekado@elephly.net> writes:

> Jelle Licht <jlicht@fsfe.org> writes:
>
>> I've noticed some time ago that the biber version that we currently have
>> is incompatible with the texlive revision we have packaged.
> […]
>> Thoughts?
>
> We should update texlive.  The latest tagged release according to
> https://tug.org/svn/texlive/tags/ is “texlive-2019.3”.
>
> Whoever upgrades this would have to ensure that *all* hashes for all SVN
> checkouts are updated.  Who would like to start a new branch for this?

I know it's been a while, but what about the wip-texlive* branch with
the texlive importer?  We could easily import the 2000 packages once
it's done.

Personnally I just need the time and money to get down to it :p

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-10-21 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 14:09 How to keep biber working Jelle Licht
2019-10-21 15:11 ` Ricardo Wurmus
2019-10-21 15:44   ` Pierre Neidhardt [this message]
2019-10-21 17:03     ` Ricardo Wurmus
2019-10-21 17:30       ` Pierre Neidhardt
2019-10-21 19:04         ` Ricardo Wurmus
2019-10-21 19:08           ` Pierre Neidhardt
2019-10-21 21:32             ` Ricardo Wurmus
2019-10-22  8:04               ` Pierre Neidhardt
2019-10-22  9:24                 ` Efraim Flashner
2019-10-22  9:27                   ` Pierre Neidhardt

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=878spe9k7w.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=jlicht@fsfe.org \
    --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).