unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Wired networking problems after guix system reconfigure
Date: Fri, 04 Mar 2016 09:59:25 +0100	[thread overview]
Message-ID: <8737s67h5e.fsf@gnu.org> (raw)
In-Reply-To: <878u1yrbvd.fsf@gmail.com> (Chris Marusich's message of "Thu, 03 Mar 2016 22:33:10 -0800")

Chris Marusich <cmmarusich@gmail.com> skribis:

> Can I pin my system to a specific kernel version without modifying the
> files in my local guix git repository?

Of course!  :-)

> Here's why I want to do this. By using git bisect, I've determined that
> the following change introduced the regression I mentioned in my
> previous email:
>
> 6b0d24b gnu: linux-libre: Update to 4.4.
>
> This change updated linux-libre from 4.3.3 to 4.4, so the problem was
> introduced somewhere inbetween.
>
> As a temporary workaround, I've added a linux-libre-4.3 variable to the
> (gnu packages linux) module in my local guix git repository, which
> allows me to use that variable in my GuixSD system configuration
> file. This is basically the same thing that was done in commit adddd5b,
> in which a linux-libre-4.1 variable was added to enable Libreboot X200
> users to work around a different known kernel regression [1].

Perfect.  To avoid modifying files in the Guix tree itself, you could
put this ‘linux-libre-4.3’ in a module of its own that you keep in
$GUIX_PACKAGE_PATH, just for your own uses.

Now, if the regression is serious and widespread, you might want to
start an argument on guix-devel as to whether we should provide this
particular kernel version in Guix proper.

Thanks,
Ludo’.

  reply	other threads:[~2016-03-04  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  8:40 Wired networking problems after guix system reconfigure Chris Marusich
2016-03-04  6:33 ` Chris Marusich
2016-03-04  8:59   ` Ludovic Courtès [this message]
2016-03-04 17:59     ` Chris Marusich
2016-03-07  9:50       ` Ludovic Courtès
2016-03-07 11:05         ` Chris Marusich
2016-03-07 12:47         ` 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=8737s67h5e.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=help-guix@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.
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).