From: Simon South <simon@simonsouth.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 43915@debbugs.gnu.org
Subject: [bug#43915] [PATCH 0/3] Update python-breathe and dependencies
Date: Fri, 23 Oct 2020 18:39:36 -0400 [thread overview]
Message-ID: <87imb0bm8n.fsf@simonsouth.net> (raw)
In-Reply-To: <87y2jw1ung.fsf@cbaines.net> (Christopher Baines's message of "Fri, 23 Oct 2020 22:48:03 +0100")
Christopher Baines <mail@cbaines.net> writes:
> I've pushed the python-six change to the core-updates branch as
> 6f95911ad175a836fbd5aaa42a8aecb0fc335a1e.
Nice, thanks.
> Given the python-sphinx change is a major version update, I was unsure
> about pushing it to master, at least without testing whether any of
> the 363 dependent packages are broken by this change.
Yes, after submitting the patch I realized: It's really too significant
a change for the amount of testing I've done on it. Better to hold off
for now I think, especially with the release coming up.
My interest really was in seeing python-breathe updated, as the new
version happens to fix a warning from Sphinx when generating Texinfo
output (and there's only one other package it affects, which I
definitely have tested). I thought updating its dependencies at the same
time would be a good idea but now I think it would be a bit reckless.
--
Simon South
simon@simonsouth.net
next prev parent reply other threads:[~2020-10-23 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 22:21 [bug#43915] [PATCH 0/3] Update python-breathe and dependencies Simon South
2020-10-10 22:24 ` [bug#43915] [PATCH 1/3] gnu: python-six: Update to 1.15.0 Simon South
2020-10-10 22:24 ` [bug#43915] [PATCH 2/3] gnu: python-sphinx: Update to 3.2.1 Simon South
2020-10-10 22:24 ` [bug#43915] [PATCH 3/3] gnu: python-breathe: Update to 4.22.1 Simon South
2020-10-10 22:28 ` [bug#43915] [PATCH 0/3] Update python-breathe and dependencies Simon South
2020-10-23 21:48 ` Christopher Baines
2020-10-23 22:39 ` Simon South [this message]
2020-10-24 20:17 ` Christopher Baines
2020-12-18 14:27 ` bug#43915: " Simon South
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=87imb0bm8n.fsf@simonsouth.net \
--to=simon@simonsouth.net \
--cc=43915@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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).