From: Marius Bakke <mbakke@fastmail.com>
To: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: core-updates all over again :)
Date: Wed, 13 May 2020 21:24:57 +0200 [thread overview]
Message-ID: <87mu6bvdrq.fsf@devup.no> (raw)
In-Reply-To: <87imgzofm2.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> Hey,
>
> So, given that core-updates was recently merged, I guess it's time to
> start the branch again?
>
> I've got two patches in mind, [1] for parallel xz compression during the
> unpack phase if the build is happening in parallel, and [2] to enable
> p11-kit in gnutls.
>
> 1: https://issues.guix.info/issue/33643
> 2: https://issues.guix.info/issue/40654
For [2], you could define a 'gnutls+p11-kit' and use that in libcacard
for now, instead of having to wait N months for the branch to start
rolling (during which time things may change in libcacard or GnuTLS).
> There's also updating Ruby to 2.7 which can at least be considered for
> core-updates, I've seen some 2.7 incompatibilities in various Ruby
> libraries, but it's worth looking at.
Maybe we should have a 'package-with-ruby27' procedure, similar to
'package-with-python2'? Then we don't need to wait for core-updates to
try this either. :-)
> The above patches could do with a bit more review, but is there any
> formalities in terms of getting core-updates going again?
The job specification needs to be re-added on Cuirass, but other than
that it should be "safe to push".
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-05-13 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 18:27 core-updates all over again :) Christopher Baines
2020-05-13 19:24 ` Marius Bakke [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu6bvdrq.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.