[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Rebuilds and branches

From: Ludovic Courtès
Subject: Rebuilds and branches
Date: Sun, 12 Oct 2014 14:58:36 +0200
User-agent: Gnus/5.130011 (Ma Gnus v0.11) Emacs/24.3 (gnu/linux)

Mark H Weaver <address@hidden> skribis:

> address@hidden (Ludovic Courtès) writes:
>> Eric Bavier <address@hidden> skribis:
>>> From 88a4cc3aa53c73186b5dbb85bf03b2138f24c825 Mon Sep 17 00:00:00 2001
>>> From: Eric Bavier <address@hidden>
>>> Date: Fri, 10 Oct 2014 13:07:55 -0500
>>> Subject: [PATCH 2/4] gnu: libjpeg: Upgrade to version 9a.
>>> * gnu/packages/image.scm (libjpeg): Upgrade to version 9a.
>> OK.
> This triggered over 450 rebuilds.  I wonder if it should have been done
> in core-updates instead.

Arf, probably yes, in a ‘libjpeg-update’ branch, rather.

What about having a policy for that?  Like, above some threshold of the
number of rebuilds reported by ‘guix refresh -l’ (200 packages?), set up
a separate branch and Hydra job set.

In an ideal world a patch queue manager would automatically take care of


reply via email to

[Prev in Thread] Current Thread [Next in Thread]