unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0.
Date: Wed, 22 Apr 2015 14:06:42 +0200	[thread overview]
Message-ID: <20150422120642.GB4297@debian.math.u-bordeaux1.fr> (raw)
In-Reply-To: <87pp6x6s6v.fsf@netris.org>

On Tue, Apr 21, 2015 at 06:18:48PM -0400, Mark H Weaver wrote:
> We shouldn't ask Hydra to build it until all of the relevant patches are
> pushed.  Therefore, I have deleted the 'wip-glib' jobset for now, since
> it was about to rebuild 1335 builds based on the libidn-1.30 update,

These were shared with master anyway, so the argument does not apply.

I still think we should evaluate once without the patches in the new
branch (which causes only little work, modulo the problems with the
virtual machine...) so that we can see under "newly failing builds" what
problems have been caused by the patches.

Currently, all packages in wip-glib are listed under "new jobs", so the
successful and the (currently close to 500) failed builds are mixed up in an
enormous list of over 5000 packages, as well as those that already fail
on master are mixed up with those that fail only in the new branch.

> I also have an libxfont security update to add to the branch as well.

Well, in an ideal world, these two patch sets would be built separately,
so that any failure could be attributed to one or the other. So I would
not call two rebuilds "wasted work" in such a context. Apart from that,
maybe with the lack of build resources, we cannot afford to rebuild after
each git commit...

Andreas

  parent reply	other threads:[~2015-04-22 12:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 10:11 [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0 宋文武
2015-04-20 10:11 ` [PATCH 2/7] gnu: itstool: Update to 2.0.2 宋文武
2015-04-20 10:11 ` [PATCH 3/7] gnu: dbus-glib: Update to 0.104 宋文武
2015-04-20 10:11 ` [PATCH 4/7] gnu: libsigc++: Update to 2.4.1 宋文武
2015-04-20 10:11 ` [PATCH 5/7] gnu: glibmm: Update to 2.44.0 宋文武
2015-04-20 10:12 ` [PATCH 6/7] gnu: python-pygobject: Update to 3.16.1 宋文武
2015-04-20 10:12 ` [PATCH 7/7] gnu: poppler: Update to 0.32.0 宋文武
2015-04-21 21:04 ` [PATCH 1/7] gnu: gobject-introspection: Update to 1.44.0 Ludovic Courtès
2015-04-22  2:03   ` 宋文武
2015-04-21 21:05 ` Ludovic Courtès
2015-04-21 21:15   ` Andreas Enge
2015-04-21 22:18     ` Mark H Weaver
2015-04-22  2:06       ` 宋文武
2015-04-22 12:06       ` Andreas Enge [this message]
2015-04-22 15:03         ` Mark H Weaver
2015-04-22 15:54           ` Andreas Enge
2015-04-22 21:00             ` Ludovic Courtès
2015-04-22 21:23               ` Mark H Weaver
2015-04-24 22:22           ` Mark H Weaver
2015-04-25  9:00             ` Mark H Weaver
2015-04-25 18:41               ` Andreas Enge
2015-04-26  0:00                 ` 宋文武
2015-04-26  9:36                   ` Andreas Enge
2015-04-26 14:07                     ` Andreas Enge

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=20150422120642.GB4297@debian.math.u-bordeaux1.fr \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.org \
    /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).