[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
core-updates vs. core-updates-next
From: |
Ludovic Courtès |
Subject: |
core-updates vs. core-updates-next |
Date: |
Fri, 27 May 2016 10:14:09 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Hi!
address@hidden (Leo Famulari) skribis:
> commit b0bbf2491e346a355c1ec5584c16de7fbfa14f5e
> Author: Leo Famulari <address@hidden>
> 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 <address@hidden>
> 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! :-)
Ludo’.
- core-updates vs. core-updates-next,
Ludovic Courtès <=