From: jgart via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 52359@debbugs.gnu.org
Subject: [bug#52359] [PATCH] gnu: python2-bottle: Remove package.
Date: Sun, 19 Dec 2021 17:58:16 -0500 [thread overview]
Message-ID: <20211219175816.GB5741@gac> (raw)
In-Reply-To: <87bl1cmdvh.fsf@gnu.org>
On Sun, 19 Dec 2021 23:25:06 +0100 Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> jgart <jgart@dismail.de> skribis:
>
> > * gnu/packages/python-web.scm (python2-bottle): Delete variable.
>
> Apparently it still has users so we can’t remove it yet:
Hi Ludo,
Thanks for the review!
The best way to check is with `guix refresh --list-dependent python2-bottle`?
Or, you're referring to the fact that there are still users using the
python2 version of bottle itself?
Also, when upgrading a package, what is your workflow for testing and making
sure you don't break a dependent package?
Do you also build all packages listed in the output of
`guix refresh --list-dependent package-name` before sending a patch?
My experience with this issue is when I updated python-jedi recently.
I sent the patch. It got accepted. (Un)relatedly, I tried installing
bpython a day later and bpython was broken. My first guess is that the
upgrade of python-jedi broke the current version of bpython in master. I
wasn't thinking about bpython when I was upgrading python-jedi.
Could any of the above be mentioned in the cookbook or the manual? Excuse me if
I TDLR'ed that part.
Any advice is much appreciated.
>
> --8<---------------cut here---------------start------------->8---
> $ ./pre-inst-env guix refresh -l python2-bottle
> Building the following 2 packages would ensure 3 dependent packages are rebuilt: h-client@0.0a0-138 virtaal@0.7.1
> --8<---------------cut here---------------end--------------->8---
>
> Ludo’.
prev parent reply other threads:[~2021-12-19 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 21:00 [bug#52359] [PATCH] gnu: python2-bottle: Remove package jgart via Guix-patches via
2021-12-19 22:25 ` Ludovic Courtès
2021-12-19 22:58 ` jgart via Guix-patches via [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=20211219175816.GB5741@gac \
--to=guix-patches@gnu.org \
--cc=52359@debbugs.gnu.org \
--cc=jgart@dismail.de \
--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).