unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: Bruno Victal <mirai@makinata.eu>
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
	67973@debbugs.gnu.org,
	Liliana Marie Prikler <liliana.prikler@gmail.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#67973: [PATCH core-updates 0/1] gnu: docbook2x: Fix build.
Date: Wed, 6 Mar 2024 13:47:52 -0500	[thread overview]
Message-ID: <CA+3U0Zk2GjqUgLGR84h9xFpoEvJfRPmjfnUz6VWG9rLG9uVWxQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1703887805.git.mirai@makinata.eu>

On Fri, Dec 29, 2023 at 5:14 PM Bruno Victal <mirai@makinata.eu> wrote:
>
> Hi Greg,
>
> Thanks for noticing, it turned out to be a regression introduced in v3.
>
> Bruno Victal (1):
>   gnu: docbook2x: Fix build.
>
>  gnu/packages/docbook.scm | 17 ++++++++---------
>  1 file changed, 8 insertions(+), 9 deletions(-)
>
>
> base-commit: e769385a7e348c8ba97614d889d7e8625fd8226a
> --
> 2.41.0

Hi Bruno,

Can this issue be closed? I am now able to build dockbook2x on
core-updates, and I believe this was fixed by Josselin Poiret in
d3a45711392fcecff640915c8bd881ff82559757 (also on 2023/12/29).


Greg




      parent reply	other threads:[~2024-03-06 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 19:01 bug#67973: docbook2x build failure Greg Hogan
2023-12-29 22:13 ` bug#67973: [PATCH core-updates 0/1] gnu: docbook2x: Fix build Bruno Victal
2023-12-29 22:13   ` bug#67973: [PATCH core-updates 1/1] " Bruno Victal
2024-04-23 13:26     ` Steve George
2024-03-06 18:47   ` Greg Hogan [this message]

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=CA+3U0Zk2GjqUgLGR84h9xFpoEvJfRPmjfnUz6VWG9rLG9uVWxQ@mail.gmail.com \
    --to=code@greghogan.com \
    --cc=67973@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=mirai@makinata.eu \
    --cc=rg@raghavgururajan.name \
    /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).