From: Vagrant Cascadian <vagrant@debian.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Marius Bakke <mbakke@fastmail.com>
Subject: Re: Linux-libre 5.8 and beyond
Date: Sun, 09 Aug 2020 11:09:01 -0700 [thread overview]
Message-ID: <877du7adz6.fsf@ponder> (raw)
In-Reply-To: <87v9hscwm7.fsf@ponder>
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
On 2020-08-08, Vagrant Cascadian wrote:
> On 2020-08-08, Mark H. Weaver wrote:
>> Vagrant Cascadian <vagrant@debian.org> wrote:
>>> I saw the 5.8 was out, and gave a quick shot at updating it, but it hung
>>> python indefinitely during the deblobbing process.
>>
>> I was unable to reproduce this problem. I simply added version 5.8 in
>> the usual way, without changing the deblobbing code at all, and the
>> deblobbing process worked correctly on my Thinkpad X200 (x86_64-linux).
>
> Curious. At a quick glance it looks like the same hashes for linux and
> the deblob and scripts that I used.
At a longer glance, it looks like I failed to update the hashes
correctly. The hashes for deblob-check 5.7 and deblob-check 5.8 both
began with "1n" and I must have somehow glazed over the differences and
not updated the local commit.
How guix actually managed to download deblob-check 5.8 from a different
URL and proceed to attempt to use the "old" store item without noticing
the hash was different still remains a mystery to me... I would have
expected it to error out before getting that far.
> I encountered the issue both on a
> pinebook pro (aarch64) and a ~6 year old i5 (x86_64) laptop, which I
> figured were different enough that it was a problem in the code...
>
>
>> I pushed commit cb97d076491495aa956dbff93679a51cc5708010 to 'master',
>> which adds the linux-libre@5.8 source and headers packages. You should
>> be able to build the deblobbed and patched source with the following
>> command:
>>
>> guix build -S -e '(@ (gnu packages linux) linux-libre-5.8-source)'
>>
>> Does it work for you? If so, how does it differ from what you tried
>> before?
>
> Will try to test again sometime in the coming days.
in progress...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-08-09 18:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 20:57 Linux-libre 5.8 and beyond Vagrant Cascadian
2020-08-09 0:02 ` Mark H Weaver
2020-08-09 3:30 ` Mark H Weaver
2020-08-09 3:43 ` Vagrant Cascadian
2020-08-09 18:09 ` Vagrant Cascadian [this message]
2020-08-09 22:17 ` Mark H Weaver
2020-08-10 22:39 ` Bengt Richter
2020-08-11 2:37 ` Tobias Geerinckx-Rice
2020-08-09 18:49 ` Leo Famulari
2020-08-25 21:01 ` Leo Famulari
2020-08-26 3:17 ` Leo Famulari
2020-08-26 15:41 ` Katherine Cox-Buday
-- strict thread matches above, loose matches on Subject: below --
2020-08-09 20:15 Jason Self
2020-08-13 0:39 ` Mark H Weaver
2020-08-14 13:47 ` Alexandre Oliva
2020-08-15 6:03 ` Mark H Weaver
2020-08-16 1:24 ` Mark H Weaver
2020-08-16 12:43 ` Jason Self
2020-08-16 10:54 ` Jason Self
2020-08-24 3:45 ` Alexandre Oliva
2020-08-25 4:14 ` Mark H Weaver
2020-08-25 11:12 ` Alexandre Oliva
2020-08-24 3:58 ` Alexandre Oliva
2020-08-24 4:12 ` Alexandre Oliva
2020-08-24 4:34 ` Alexandre Oliva
2020-08-24 4:42 ` Alexandre Oliva
2020-08-11 4:07 Mark H Weaver
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=877du7adz6.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
--cc=mhw@netris.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).