From: John Kehayias <john.kehayias@protonmail.com>
To: Tanguy LE CARROUR <tanguy@bioneland.org>
Cc: guix-devel@gnu.org
Subject: Re: Reverting d477018b57 "gnu: poetry: Update to 1.1.12."
Date: Thu, 04 May 2023 15:09:14 +0000 [thread overview]
Message-ID: <875y9816cr.fsf@protonmail.com> (raw)
In-Reply-To: <168310015384.3439.10255060373979568367@localhost>
Hi Tanguy,
On Wed, May 03, 2023 at 09:49 AM, Tanguy LE CARROUR wrote:
> Hi Guix,
>
> I noticed yesterday that Poetry was broken:
> <https://ci.guix.gnu.org/build/1227911/details>.
>
> I might have spotted it earlier if I had spend time testing `core-update`.
> My bad!
>
Yes, I noticed that too but fixing the current version of Poetry sent
me down quite a rabbit hole of dependencies and updates. I didn't
emerge in time for the core-updates merge. There might be a better way
than causing a python world rebuild, but this is my current series
which does have Poetry building (might as well do the updates I
figure): <https://issues.guix.gnu.org/63139>
The proper polishing and bootstrapping updates is WIP, but that series
will get you Poetry building, after lots of other rebuilding :)
> The problematic commit seems to be d477018b57 "gnu: poetry: Update to 1.1.12.".
>
> What also questions me is the fact that the commit message states that
> it's an upgrade to `1.1.12` when it's the current version and it's
> actually an upgrade to `1.4.2`.
>
Right, probably a typo in the commit message.
> Unfortunately, I have no time to work on this right now. Would it be
> possible to revert the change? Or should I submit a patch to downgrade it?
>
> Cheers,
I haven't tried if a simple revert will build given all the other
changes from core-updates. If that works that would be a good stopgap.
Do you know if that works and is simple enough? Or can you test?
Thanks,
John
next prev parent reply other threads:[~2023-05-04 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 7:49 Reverting d477018b57 "gnu: poetry: Update to 1.1.12." Tanguy LE CARROUR
2023-05-04 15:09 ` John Kehayias [this message]
2023-05-04 15:23 ` Tanguy LE CARROUR
2023-05-24 16:48 ` Tanguy LE CARROUR
2023-05-25 3:19 ` John Kehayias
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=875y9816cr.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@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).