From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [PATCH 0/5] Sphinx reproducibility update Date: Sun, 03 Jul 2016 23:52:00 +0200 Message-ID: <87k2h2crun.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bJpJ9-00072c-SX for guix-devel@gnu.org; Sun, 03 Jul 2016 17:52:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bJpJ5-0007pp-MR for guix-devel@gnu.org; Sun, 03 Jul 2016 17:52:06 -0400 In-Reply-To: (Leo Famulari's message of "Fri, 1 Jul 2016 21:04:48 -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: Leo Famulari Cc: guix-devel@gnu.org Hello, Leo Famulari skribis: > Since version 1.4.0, Sphinx has respected the SOURCE_DATE_EPOCH > environment variable for the timestamps it puts in generated > documentation [0]. Awesome! > This patch series updates Sphinx to the latest version, 1.4.4, and > provides all the new dependencies. The final commit in the series > requires the new Sphinx. > > Why propagate pytz and snowballstemmer? Otherwise, many packages that > use Sphinx started failing due to pytz or snowballstemmer not being > avaiable. Rather than provide pytz and snowballstemmer to all those > packages, I propagated them from Sphinx itself. I can add pytz and > snowballstemmer to the Sphinx users if desired. Makes sense. > With this change, many Python 2 packages will become reproducible, at > least on a single machine; the only thing holding them back was the > manpage timestamps. > > These changes will require 142 rebuilds, mostly of Python packages, but > also of libreoffice (libreoffice seems to depend on *everything*) and a > few others. If the patches are good, should they go to master or to > another branch? You could push them to =E2=80=98core-updates=E2=80=99 as a way to save a li= ttle bit of build time. Thank you! Ludo=E2=80=99.