From: Maxime Devos <maximedevos@telenet.be>
To: Christopher Rodriguez <yewscion@gmail.com>
Cc: 55814@debbugs.gnu.org
Subject: [bug#55814] [PATCH v2] Updated python-flake8 and inputs to reenable build.
Date: Mon, 06 Jun 2022 21:05:07 +0200 [thread overview]
Message-ID: <37b08812fea6846879b5a9d8cb9177171c13cdf9.camel@telenet.be> (raw)
In-Reply-To: <pkmp4e1qw11v98.fsf@crane.ant.amazon.com>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
Christopher Rodriguez schreef op ma 06-06-2022 om 14:44 [-0400]:
> Without the changes in this patch, `python-flake8` (and thus, any
> packages that
> depend on it) will not be able to successfully build (I use `python-
> lsp-server`
> in my profile; I believe that is where I ran into an issue with this
> package). Can this, then, be considered a "single independent
> change"? All of
> the changes made were made to support `python-flake8` building, even
> though the
> changes effected 3 separate packages.
They are related changed (same external purpose: make python-flake8),
but each change can stand on its own (different internal purposes:
update this, run tests, respect #:tests?) without causing new build
failures AFAIK.
> If not, I suppose I can split the patch into three separate packages
> like this:
>
> 1. `python-pycodestyle` changes. (needed for `python-flake8` to build
> with tests)
> 2. `python-pyflakes` changes. (needed for `python-flake8` to build
> with tests)
> 3. `python-flake8` changes. (the package that would not build)
That, and seperate the update and the (when tests? ...).
TBC the just need to be separate patches, but not a seperate patch
series (all six can go to 55814@debbugs.gnu.org).
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-06 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 1:43 [bug#55814] [PATCH] Updated python-flake8 and inputs to reenable build Christopher Rodriguez
2022-06-06 6:13 ` Liliana Marie Prikler
2022-06-06 9:31 ` Maxime Devos
2022-06-06 17:24 ` [bug#55814] [PATCH v2] " Christopher Rodriguez
2022-06-06 18:33 ` Maxime Devos
[not found] ` <pkmp4e1qw11v98.fsf@crane.ant.amazon.com>
2022-06-06 19:05 ` Maxime Devos [this message]
2022-06-07 1:10 ` [bug#55814] [PATCH v3 1/8] Refreshed `python-pycodestyle` to version 2.8.0 Christopher Rodriguez
2022-06-07 1:10 ` [bug#55814] [PATCH v3 2/8] Refreshed `python-flake8` to 4.0.1 Christopher Rodriguez
2022-06-07 1:10 ` [bug#55814] [PATCH v3 3/8] `python-pycodestyle` now respects `#:tests?` Christopher Rodriguez
2022-06-07 1:10 ` [bug#55814] [PATCH v3 4/8] `python-flake8` now supports `#:tests?` Christopher Rodriguez
2022-06-07 1:10 ` [bug#55814] [PATCH v3 5/8] Added `python-pyflakes-2.3` as a variant package Christopher Rodriguez
2022-06-07 1:10 ` [bug#55814] [PATCH v3 6/8] Added `python-pycodestyle-2.7` " Christopher Rodriguez
2022-06-07 1:10 ` [bug#55814] [PATCH v3 7/8] Added `python-flake8-3.9` " Christopher Rodriguez
2022-06-07 1:10 ` [bug#55814] [PATCH v3 8/8] Formatted Code with `guix style` Christopher Rodriguez
2022-06-07 1:12 ` [bug#55814] Status of Rebuilds for Change Christopher Rodriguez
2022-06-07 13:22 ` bug#55814: [PATCH] Updated python-flake8 and inputs to reenable build Maxim Cournoyer
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=37b08812fea6846879b5a9d8cb9177171c13cdf9.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55814@debbugs.gnu.org \
--cc=yewscion@gmail.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.