unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Jason Self <jason@bluehome.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: linux-libre-headers: Update to 3.18.11
Date: Tue, 14 Apr 2015 21:46:32 -0400	[thread overview]
Message-ID: <87d236go3r.fsf@netris.org> (raw)
In-Reply-To: <1429029191.6750@bluehome.net> (Jason Self's message of "Tue, 14 Apr 2015 09:33:13 -0700 (PDT)")

"Jason Self" <jason@bluehome.net> writes:
> I understand that updated headers are needed in order for the new
> version of VLC to compile successfully.

Updating linux-libre-headers entails a full rebuild of everything in
Guix.  As Andreas noted, I updated it to the latest LTS (3.14.37) in the
core-updates branch, which will hopefully be merged to master within a
few days.

Is 3.14.x new enough?  Should I have chosen differently?  If we need to
change it, we'll have to wait for the next core-updates cycle.

More generally, what should be our policy on how to choose a version for
linux-libre-headers?

> Also, since Alexandre Oliva periodically removes tarballs so as to
> free up space on the virtual machine that hosts these, it might also
> be a good idea to put a copy of linux-libre-3.18.11-gnu.tar.xz in
> http://alpha.gnu.org/gnu/guix/mirror/ along with the current version
> 3.3.8.

Indeed, we should keep a copy of the source tarball for our
linux-libre-headers there.  I don't know that I have the necessary
access to do that, so I guess that's a job for Ludovic.

     Mark

  parent reply	other threads:[~2015-04-15  1:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 16:33 [PATCH] gnu: linux-libre-headers: Update to 3.18.11 Jason Self
2015-04-14 16:45 ` Andreas Enge
2015-04-15  1:46 ` Mark H Weaver [this message]
2015-04-15  4:24   ` Jason Self
2015-04-15 20:53   ` Ludovic Courtès

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=87d236go3r.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=jason@bluehome.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 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).