From: Tanguy LE CARROUR via Guix-patches <guix-patches@gnu.org>
To: 58792@debbugs.gnu.org
Subject: [bug#58792] Acknowledgement ([PATCH] gnu: python-filelock: Update to 3.8.0.)
Date: Wed, 26 Oct 2022 10:03:18 +0200 [thread overview]
Message-ID: <166677139827.9762.17717851787532695386@localhost> (raw)
In-Reply-To: <handler.58792.B.166676841713051.ack@debbugs.gnu.org>
Hi Guix,
Contrary to what I said, this patch might not be trivial!
The resulting package exposes version 0.0.0, which seems to break every
package that depends on it!
The issue has been reported upstream [1][]. The solution would be to use
a different build system.
[1]: https://github.com/tox-dev/py-filelock/issues/133)
I'm working on it…
--
Tanguy
next prev parent reply other threads:[~2022-10-26 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 7:13 [bug#58792] [PATCH] gnu: python-filelock: Update to 3.8.0 Tanguy Le Carrour
[not found] ` <handler.58792.B.166676841713051.ack@debbugs.gnu.org>
2022-10-26 8:03 ` Tanguy LE CARROUR via Guix-patches [this message]
2022-10-26 13:44 ` [bug#58792] [PATCH v2 1/2] " Tanguy Le Carrour
2022-10-26 13:44 ` [bug#58792] [PATCH v2 2/2] gnu: python-virtualenv: Update to 20.16.5 Tanguy Le Carrour
2022-11-05 11:24 ` [bug#58792] [PATCH v3 1/2] gnu: python-filelock: Update to 3.8.0 Tanguy Le Carrour
2022-11-05 11:24 ` [bug#58792] [PATCH v3 2/2] gnu: python-virtualenv: Update to 20.16.5 Tanguy Le Carrour
2024-02-29 8:20 ` bug#58792: [PATCH] gnu: python-filelock: Update to 3.8.0 Tanguy LE CARROUR
2024-02-29 8:32 ` [bug#58792] " Tanguy LE CARROUR
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=166677139827.9762.17717851787532695386@localhost \
--to=guix-patches@gnu.org \
--cc=58792@debbugs.gnu.org \
--cc=tanguy@bioneland.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).