From: Greg Hogan <code@greghogan.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 63453@debbugs.gnu.org
Subject: [bug#63453] [PATCH] gnu: python-ipython-documentation: Remove patches.
Date: Mon, 22 May 2023 15:37:41 -0400 [thread overview]
Message-ID: <CA+3U0Znt6Dc9Ptn9VVrY9-EOHQsUWSwUx5GtNWQwji1Kv4CbzQ@mail.gmail.com> (raw)
In-Reply-To: <878rdgxvyl.fsf@gnu.org>
On Mon, May 22, 2023 at 10:49 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi,
>
> Greg Hogan <code@greghogan.com> skribis:
>
> > Maxim's patch was merged and released upstream in 8.5.0:
> > https://github.com/ipython/ipython/commit/f20e3b80393a1a5909a050cb7bb9cbce9e044827
> >
> > * gnu/packages/python-xyz.scm (python-ipython-documentation)[source]:
> > Remove upstreamed patches.
> > * gnu/packages/patches/python-ipython-documentation-chars.patch,
> > gnu/packages/patches/python-ipython-documentation-repro.patch:
> > Delete files.
> > * gnu/local.mk: Remove files.
>
> The patch LGTM but currently ‘python-docrepr’ fails to build (test
> failures) so we cannot test it.
>
> Do you happen to have an idea how to address that?
>
> Thanks,
> Ludo’.
Thanks for looking this over. I have a fix for python-docrepr and will
send an updated patchset after the python-ipython-documentation build
completes.
next prev parent reply other threads:[~2023-05-22 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 20:36 [bug#63453] [PATCH] gnu: python-ipython-documentation: Remove patches Greg Hogan
2023-05-22 14:49 ` Ludovic Courtès
2023-05-22 19:37 ` Greg Hogan [this message]
2023-05-22 20:17 ` [bug#63453] [PATCH v2 0/3] Fix build for python-ipython-documentation Greg Hogan
2023-05-22 20:17 ` [bug#63453] [PATCH v2 1/3] gnu: python-docrepr: Fix tests Greg Hogan
2023-05-22 20:17 ` [bug#63453] [PATCH v2 2/3] gnu: python-ipython-documentation: Remove patches Greg Hogan
2023-05-22 20:17 ` [bug#63453] [PATCH v2 3/3] gnu: python-ipython-documentation: Update dependencies Greg Hogan
2023-06-02 14:14 ` bug#63453: [PATCH] gnu: python-ipython-documentation: Remove patches Ludovic Courtès
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+3U0Znt6Dc9Ptn9VVrY9-EOHQsUWSwUx5GtNWQwji1Kv4CbzQ@mail.gmail.com \
--to=code@greghogan.com \
--cc=63453@debbugs.gnu.org \
--cc=ludo@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.
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).