On 16/03/2020 06:28, Sandro Tosi wrote:
Hey Rebecca, do you have an updated list of these cycles?
Warning: this is based on open py2removal bugs, *not* actual package
relationships.
2 crossfire crossfire-maps
2 sugar sugar-pippy-activity
2 rabbyt snowballz
4 python-pysnmp4 pysmi python-pysnm
Hey Rebecca, do you have an updated list of these cycles?
On Wed, Oct 23, 2019 at 6:39 PM Rebecca N. Palmer
wrote:
>
> [Summary of previous messages: I noted that packages with circular
> dependencies can't be removed one at a time without breakage. Replies
> were to remove multiple packages at
Simon McVittie wrote:
You've listed dbus-python as being part of this cycle, but [it probably
shouldn't be]
Perhaps some of the blocks have been added the wrong way round?
Or perhaps the script is imperfectly guessing which binaries are Python
2? e.g. matplotlib is listed even though it's al
On Thu, Oct 24, 2019 at 08:49:41AM +0100, Simon McVittie wrote:
> in general we
> also consider broken Recommends to be a serious bug if anyone notices
> them (due to Policy ยง2.2.1 "must not require or recommend a package
> outside of main for compilation or execution").
Note that the release polic
On Wed, 23 Oct 2019 at 23:05:39 +0100, Rebecca N. Palmer wrote:
> - One big tangle (159 packages). This probably needs breaking up:
> --- Some of it involves documentation tools (e.g. sphinx). These cycles can
> be broken by using the Python 3 version of the tool.
You've listed dbus-python as be
[Summary of previous messages: I noted that packages with circular
dependencies can't be removed one at a time without breakage. Replies
were to remove multiple packages at once if necessary, but ask first if
other maintainers' packages are involved.]
I have now checked what cycles we have:
> Note that having an unbuildable package in sid for several days, until
> it's updated to a no-py2 version, is perfectly acceptable.
please note that may not be fine with every maintainer. dont just drop
packages without checking rdeps and/or if you know that will make
packages uninstallable/unbu
On Sat, Sep 21, 2019 at 10:18:16AM +0100, Rebecca N. Palmer wrote:
> Some Python 2 packages have circular (build-)dependencies, making it
> impossible to remove them one at a time without breaking anything.
Unless I'm missing something, this shouldn't be a problem, just go away
and remove them all
Some Python 2 packages have circular (build-)dependencies, making it
impossible to remove them one at a time without breaking anything.
One such cycle is seaborn, sphinx-gallery and matplotlib2 (#940873); I
have not attempted to systematically check for them.
How should these be dealt with?
9 matches
Mail list logo
