From: Vagrant Cascadian <vagrant@debian.org>
To: Mathieu Othacehe <othacehe@gnu.org>,
Pierre Langlois <pierre.langlois@gmx.com>
Cc: 49552@debbugs.gnu.org
Subject: [bug#49552] [PATCH] gnu: u-boot: Update to 2021.07.
Date: Sun, 25 Jul 2021 10:06:10 -0700 [thread overview]
Message-ID: <87lf5ugw71.fsf@yucca> (raw)
In-Reply-To: <875ywyqtfj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
On 2021-07-25, Mathieu Othacehe wrote:
>> * gnu/packages/bootloaders.scm (u-boot): Update to 2021.07.
>> [native-inputs]: Add python-pycryptodomex.
>> (u-boot-2021.07): Delete variable.
>> (u-boot-tools)[arguments]: Adapt 'patch phase, disable failing test_spl test.
>> (u-boot-sifive-unmatched): Use default u-boot package.
>> (u-boot-pinebook-pro-rk3328): Use default u-boot package.
>
> This seems fine to me, Vagrant any objections here?
Heh. Just uploaded 2021.07 to Debian last night! Been meaning to look at
updating in guix, but apparently someone beat me to it :)
Overall, sounds fine to me, with one relatively minor change...
u-boot-sifive-unmatched will need a pretty trivial patch in order to
update to 2021.07:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1937246
https://salsa.debian.org/debian/u-boot/-/blob/debian/latest/debian/patches/riscv64/unmatched-prevent-relocating-initrd-and-fdt.patch
At least, it did when building on Debian (and apparently Ubuntu)...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-07-25 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 19:56 [bug#49552] [PATCH] gnu: u-boot: Update to 2021.07 Pierre Langlois
2021-07-25 15:55 ` Mathieu Othacehe
2021-07-25 17:06 ` Vagrant Cascadian [this message]
2021-07-26 10:54 ` Pierre Langlois
2021-08-01 21:03 ` Vagrant Cascadian
2021-08-02 12:31 ` bug#49552: " Pierre Langlois
2021-08-02 16:02 ` [bug#49552] " Pierre Langlois
2021-08-02 19:32 ` Vagrant Cascadian
2021-08-05 12:37 ` Pierre Langlois
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=87lf5ugw71.fsf@yucca \
--to=vagrant@debian.org \
--cc=49552@debbugs.gnu.org \
--cc=othacehe@gnu.org \
--cc=pierre.langlois@gmx.com \
/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).