[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1026104: marked as done (longstanding problem with dependencies of python3-numpy in testing)

Your message dated Tue, 10 Jan 2023 20:04:08 +0100
with message-id <Y722qKUA4shRmjjO@alf.mars>
and subject line Re: Bug#1026104: longstanding problem with dependencies of python3-numpy in testing
has caused the Debian Bug report #1026104,
regarding longstanding problem with dependencies of python3-numpy in testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1026104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026104
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: tech-ctte

Estimated volunteers of the Debian Technical Committee:

At times, python3-numpy in testing depends on two python3
minor versions in parallel. This is unusual, annoying for
many users, and breaking dependent software for some.
Complaints have been filed at

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800620
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878281
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903663
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945824
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003805
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025169

Explanations have been given in particular in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945824
According to these, the simultaneous dependency on old and
new Python subversions is a deliberate choice as part of
a multi-step migration strategy.

My request to you, estimated committee members, would be
to review this migration strategy. The best possible
outcome would be an advise to the package maintainer
how to continue his otherwise excellent work without
publishing intermediate versions of python3-numpy that
cause difficulties downstream.

With best regards, Joachim Wuttke

--- End Message ---
--- Begin Message --- 
Hi Joachim,

We discussed this issue at our monthly CTTE meeting and concluded to
close this bug as "not actionable".

On Sun, Jan 08, 2023 at 04:51:57PM +0100, Joachim Wuttke wrote:
> Other solution?: just not release problematic transitory versions.

This is not a solution. Python transitions work by adding a new
interpreter version and then removing the old one. This is how Python
and Ruby do transitions in Debian. Changing this aspect is a bigger can
of worms.

In any case, we recognize that the current behaviour of numpy is
suboptimal during Python transitions. We do not see a simple change or
patch that would be readily applicable to improve the situation. Sandro
indicated that he does not want to work on such a patch, which is his
right granted by the Debian Constitution. On the other hand, he
indicated that he would be reviewing a patch. Thank you. For these
reasons, we think that it is too early to ask the CTTE to decide on this
matter. We encourage you to work on a technical solution to this problem
and present it to the numpy maintainers. In the event that this does not
resolve the matter, we encourage you to get back to us and reopen this
bug.

Thanks for your understanding

Helmut Grohne on behalf of the Debian technical committee

--- End Message ---
Reply to: