From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jelle Licht Subject: How to keep biber working Date: Mon, 21 Oct 2019 16:09:19 +0200 Message-ID: <877e4yi41c.fsf@jlicht.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:45270) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMYNA-00061q-Up for guix-devel@gnu.org; Mon, 21 Oct 2019 10:09:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMYN9-0003Ye-SU for guix-devel@gnu.org; Mon, 21 Oct 2019 10:09:24 -0400 Received: from mail1.fsfe.org ([217.69.89.151]:41052) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iMYN9-0003Xm-MY for guix-devel@gnu.org; Mon, 21 Oct 2019 10:09:23 -0400 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org, Ricardo Wurmus Guix, I've noticed some time ago that the biber version that we currently have is incompatible with the texlive revision we have packaged. Incidentally, since the latest core-updates merge, biber does not pass its test suite anymore due to the hardcoded `perl-unicode-collate'-related hashes. I think we need a more sustainable (and dynamic) fix for this, as this is not the first time this has happened. As far as I know, biber has no dependents other than itself. I could also downgrade it 2.11 so it works with our texlive packages again. Should I simply revert the "gnu: biber: Update to 2.12." commit, or only adjust the [source] and [version] fields of the biber package? I can push a short-term fix that involves disabling the test suite for biber nonetheless, as this seems to be required for both version 2.12 and 2.11. Thoughts?