From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: core-updates vs. core-updates-next
Date: Fri, 27 May 2016 10:56:35 -0400 [thread overview]
Message-ID: <20160527145635.GA21969@jasmine> (raw)
In-Reply-To: <87bn3rx6i6.fsf_-_@gnu.org>
On Fri, May 27, 2016 at 10:14:09AM +0200, Ludovic Courtès wrote:
> Hi!
>
> leo@famulari.name (Leo Famulari) skribis:
>
> > commit b0bbf2491e346a355c1ec5584c16de7fbfa14f5e
> > Author: Leo Famulari <leo@famulari.name>
> > Date: Thu May 26 13:24:41 2016 -0400
> >
> > gnu: expat: Remove replacement.
> >
> > * gnu/packages/xml.scm (expat)[replacement]: Remove field.
> > (expat/fixed): Remove variable.
>
> [...]
>
> > commit aee7f2e98ae2cbbd0cd765beda6c0a4279929c94
> > Author: Leo Famulari <leo@famulari.name>
> > Date: Thu May 26 22:45:51 2016 -0400
> >
> > gnu: libxslt: Update to 1.1.29.
> >
> > * gnu/packages/patches/libxslt-CVE-2015-7995.patch: Delete file.
> > * gnu/local.mk (dist_patch_DATA): Remove it.
> > * gnu/packages/xml.scm (libxslt): Update to 1.1.29.
> > [source]: Remove patch.
>
> Clarification: until Hydra has started building all of core-updates,
> it’s OK to push non-core updates like these to core-updates.
>
> There are still a couple of issues at
> <https://hydra.gnu.org/jobset/gnu/core-updates> to be fixed in the core
> packages before we can ask Hydra to build all of core-updates. Until
> then, feel free! :-)
Okay, do you think I should move the commits from core-updates-next to
core-updates?
next prev parent reply other threads:[~2016-05-27 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160526173645.9317.58057@vcs.savannah.gnu.org>
[not found] ` <20160526173645.520A2220153@vcs.savannah.gnu.org>
2016-05-27 8:14 ` core-updates vs. core-updates-next Ludovic Courtès
2016-05-27 14:56 ` Leo Famulari [this message]
2016-05-28 15:38 ` Ludovic Courtès
2016-05-28 16:04 ` Leo Famulari
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=20160527145635.GA21969@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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).