all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Herman Rimm <herman@rimm.ee>, 67261@debbugs.gnu.org
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Munyoki Kilyungi <me@bonfacemunyoki.com>,
	Lars-Dominik Braun <lars@6xq.net>,
	Efraim Flashner <efraim@flashner.co.il>,
	jgart@dismail.de, Marius Bakke <marius@gnu.org>
Subject: [bug#67261] [PATCH v2] gnu: u-boot: Update to 2023.10.
Date: Fri, 01 Dec 2023 11:48:55 -0800	[thread overview]
Message-ID: <875y1hln4o.fsf@wireframe> (raw)
In-Reply-To: <84197f2f58280985be25675aaf7e06fa3309c2cf.1701072816.git.herman@rimm.ee>

[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]

On 2023-11-27, Herman Rimm wrote:
> If you would like to test u-boot v2023.10 and have a HiFive Unmatched,
> please test this revision of the patch and let me know whether or not
> the device still boots.

Will check booting an unmatched board; I need to do the same test to
upgrade u-boot in Debian anyways.

The main outstanding issue is that u-boot-documentation still fails to
build.

In order to get u-boot-documentation to build, I had to add
python-sphinx-prompt, and in order to get python-sphinx-prompt to build,
I needed to disable tests. Can someone from the python team take a look
at python-sphinx-prompt?

python-sphinx-rtd-theme is an optional dependency for the documentation,
but it does build without it. I am not sure how much nicer it is with or
without it. Any opinions on enabling that or using the default theme?


Applying this patch on top of v2 gets everything building for me, though
obviously disabling tests for python-sphinx-prompt is not ideal:

diff --git a/gnu/packages/bootloaders.scm b/gnu/packages/bootloaders.scm
index 5e6edb143e..1b5e745fce 100644
--- a/gnu/packages/bootloaders.scm
+++ b/gnu/packages/bootloaders.scm
@@ -764,6 +764,8 @@ (define-public u-boot-documentation
      (modify-inputs (package-native-inputs u-boot)
        (append fontconfig
                python-sphinx
+               python-sphinx-prompt
+               ; python-sphinx-rtd-theme
                texinfo
                which)))
     (synopsis "U-Boot documentation")
diff --git a/gnu/packages/sphinx.scm b/gnu/packages/sphinx.scm
index eee1f1c4a8..020e0794ef 100644
--- a/gnu/packages/sphinx.scm
+++ b/gnu/packages/sphinx.scm
@@ -637,7 +637,8 @@ (define-public python-sphinx-prompt
         (base32 "0x9wmgf04rzivbzp7jv1b7fkhkpi02lpk5w1qf4i7bcgih00ym8a"))))
     (build-system python-build-system)
     (arguments
-     `(#:phases
+     `(#:tests? #f ; FIXME build fails without this, needed to build u-boot-documentation 2023.10+
+       #:phases
        (modify-phases %standard-phases
          (replace 'check
            (lambda* (#:key inputs outputs tests? #:allow-other-keys)


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2023-12-01 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 15:38 [bug#67261] [PATCH 0/3] Update u-boot to 2023.10 Herman Rimm via Guix-patches via
2023-11-18 16:01 ` [bug#67261] [PATCH 1/3] gnu: u-boot: Update " Herman Rimm via Guix-patches via
2023-11-24 21:23   ` Vagrant Cascadian
2023-11-18 16:01 ` [bug#67261] [PATCH 2/3] gnu: bootloader: Add orangepi-r1-plus-lts-rk3328 bootloader Herman Rimm via Guix-patches via
2023-12-01 19:50   ` Vagrant Cascadian
2023-11-18 16:01 ` [bug#67261] [PATCH 3/3] images: Add orangepi-r1-plus-lts image Herman Rimm via Guix-patches via
2023-12-01 19:58   ` Vagrant Cascadian
2023-12-03 10:22     ` Efraim Flashner
2023-12-22 23:59       ` Vagrant Cascadian
2023-11-27  8:33 ` [bug#67261] [PATCH v2] gnu: u-boot: Update to 2023.10 Herman Rimm via Guix-patches via
2023-12-01 19:48   ` Vagrant Cascadian [this message]
2023-12-02  7:11     ` Lars-Dominik Braun
2023-12-23  0:19 ` bug#67261: [PATCH 0/3] Update u-boot " Vagrant Cascadian

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=875y1hln4o.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=67261@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=herman@rimm.ee \
    --cc=jgart@dismail.de \
    --cc=lars@6xq.net \
    --cc=marius@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@bonfacemunyoki.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 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.