unofficial mirror of 
 help / color / Atom feed
From: Tanguy Le Carrour <>
To: Marius Bakke <>
Cc: Guix <>
Subject: Re: [PATCH 0/X] gnu: poetry: Fix broken dependency after dependency's version update.
Date: Thu, 30 Jul 2020 15:18:05 +0200
Message-ID: <20200730131805.f3lqoiszb456jx4y@rafflesia> (raw)
In-Reply-To: <>

Hi Marius,

Le 07/30, Marius Bakke a écrit :
> Tanguy Le Carrour <> writes:
> > Few days ago, I submitted a patch to update `python-tomlkit`. It was pushed
> > to master and, after I upgraded my packages today, I realised that `poetry`
> > (and possibly other python packages) was broken!
> >
> > The "problem" is that Poetry depends on `tomlkit = "^0.5.11"`. This
> > translates to `>=0.5.11,<0.6.0`. And I updated `python-tomlkit` to… 0.6.0!
> >
> > In SemVer [1], minor releases are supposed to "add functionality
> > in a backwards compatible manner", so this "<0.6.0" seems, IMHO, wrong.
> > But that's not the point…
> >
> > [1]:
> >
> > Now, I have to fix Poetry and I have 2 options:
> > - modify poetry `` and substitute `>=0.5.11,<0.7.0` to `>=0.5.11,<0.6.0`;
> > - add a new `python-tomlkit-0.5` and use it in the propagated inputs.
> >
> > Any suggestion on the one I should implement?
> I haven't looked into it, but if the tomlkit API really is compatible,
> the first suggestion sounds good to me.  It would be good to notify
> upstream about the unreasonable "pinning" in that case.

Problem reported upstream: <>.

> Otherwise the second suggestion sounds good too.  There is plenty of
> precedence for both solutions in Guix and is really something that needs
> to be decided on a case-by-case basis.

I decided to implement the "quick fix": <>.
I'll implement the `python-tomlkit-0.5` solution if upstream does not
see this as a problem.



      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 15:48 Tanguy Le Carrour
2020-07-29 22:42 ` Marius Bakke
2020-07-30 13:18   ` Tanguy Le Carrour [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200730131805.f3lqoiszb456jx4y@rafflesia \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

unofficial mirror of 

Archives are clonable:
	git clone --mirror guix-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-devel guix-devel/ \
	public-inbox-index guix-devel

Example config snippet for mirrors

Newsgroups are available over NNTP:

AGPL code for this site: git clone