On 9/2/19 1:18 PM, Martin Kelly wrote:
On 9/1/19 10:07 PM, Scott Kitterman wrote:
On September 2, 2019 4:00:53 AM UTC, Sandro Tosi
wrote:
I would just stop building these. And if the reverse dependencies
have a
py2removal bug itself, then comment in these issues that the
suggested/recomm
On 9/1/19 10:07 PM, Scott Kitterman wrote:
On September 2, 2019 4:00:53 AM UTC, Sandro Tosi wrote:
I would just stop building these. And if the reverse dependencies
have a
py2removal bug itself, then comment in these issues that the
suggested/recommended package gets removed. If they don'
On September 2, 2019 4:00:53 AM UTC, Sandro Tosi wrote:
>> I would just stop building these. And if the reverse dependencies
>have a
>> py2removal bug itself, then comment in these issues that the
>> suggested/recommended package gets removed. If they don't have a
>py2removal
>> bug, please f
> I would just stop building these. And if the reverse dependencies have a
> py2removal bug itself, then comment in these issues that the
> suggested/recommended package gets removed. If they don't have a py2removal
> bug, please file the bugs for these packages.
i dont believe this is a sensibl
On 01.09.19 21:48, Martin Kelly wrote:
Hi,
I maintain python-gmpy and python-gmpy2, which need to transition to Python 3.
However, they have several packages that have Suggests or Recommends (not a hard
dependency) pointing to python-gmpy/python-gmpy2. These other packages appear to
be Python
Hi,
I maintain python-gmpy and python-gmpy2, which need to transition to
Python 3. However, they have several packages that have Suggests or
Recommends (not a hard dependency) pointing to python-gmpy/python-gmpy2.
These other packages appear to be Python 2 only.
Should I stop building the Py
6 matches
Mail list logo