Bug#938157: [Python-modules-team] Bug#938157: python-scipy: Python2 removal in sid/bullseye
On Mon, Jan 13, 2020 at 9:08 PM Drew Parsons wrote: > > On 2020-01-14 02:13, Sandro Tosi wrote: > >> >It's just that there is no extra effort required in this case. > >> >python3-scipy does indeed need the effort taken, but once that effort > >> >is > >> >done, it's no more effort to apply the same fix to python-scipy. So > >> >yes, please do focus on fixing python3-scipy! :) > >> > >> Yes, maybe so, but delaying the python2-rm blocks other work and thus > >> delays and complicates getting that major effort completed. Let's > >> not. > > > > exactly, i really dont understand what's the value of fixing something > > that's gonna be removed anyway. > > > > I think i'm just gonna wait a couple more days and then file a RM > > Fair enough then. I'm out-voted :) i pulled the trigger and opened #948946 :) -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#938157: [Python-modules-team] Bug#938157: python-scipy: Python2 removal in sid/bullseye
On 2020-01-14 02:13, Sandro Tosi wrote: >It's just that there is no extra effort required in this case. >python3-scipy does indeed need the effort taken, but once that effort >is >done, it's no more effort to apply the same fix to python-scipy. So >yes, please do focus on fixing python3-scipy! :) Yes, maybe so, but delaying the python2-rm blocks other work and thus delays and complicates getting that major effort completed. Let's not. exactly, i really dont understand what's the value of fixing something that's gonna be removed anyway. I think i'm just gonna wait a couple more days and then file a RM Fair enough then. I'm out-voted :)
Bug#938157: [Python-modules-team] Bug#938157: python-scipy: Python2 removal in sid/bullseye
On 2020-01-13 12:47, Sandro Tosi wrote: Thanks Sandro. There is RC bug#946624 affecting python-scipy, with a counterpart in #946625 for python3-scipy. Something subtle has changed in the syntax for skipping tests, I haven't figured out what yet. Help needed. Since that problem needs to be fixed anyway for python3-scipy, I propose dealing with that first before decommissioning python-scipy. I expect that whatever the fix is that's needed for python3-scipy, the same patch will fix the tests for python-scipy. That way we can put python-scipy to sleep on a clean bed. what is the benefit of fixing python-scipy, when we can remove it right now? i feel like we could just focus on fixing python3-scipy and use the time/effort for python-scipy for something else :) It's just that there is no extra effort required in this case. python3-scipy does indeed need the effort taken, but once that effort is done, it's no more effort to apply the same fix to python-scipy. So yes, please do focus on fixing python3-scipy! :) Drew
Bug#938157: [Python-modules-team] Bug#938157: python-scipy: Python2 removal in sid/bullseye
On Sunday, January 12, 2020 11:28:55 PM EST Drew Parsons wrote: > On 2020-01-13 09:52, Sandro Tosi wrote: > > we finally reach the point were src:python-scipy produces only leaf > > binary packages (excluding packages that are not in testing because RC > > already), so i think it's time to file for its removal, and continue > > with src:scipy. > > > > I've copied maintainers and Drew (whos been doing all the work > > recently); if i dont receive a NACK within a week, i'll file for the > > removal of src:python-scipy. > > Thanks Sandro. There is RC bug#946624 affecting python-scipy, with a > counterpart in #946625 for python3-scipy. Something subtle has changed > in the syntax for skipping tests, I haven't figured out what yet. Help > needed. > > Since that problem needs to be fixed anyway for python3-scipy, I propose > dealing with that first before decommissioning python-scipy. I expect > that whatever the fix is that's needed for python3-scipy, the same patch > will fix the tests for python-scipy. That way we can put python-scipy > to sleep on a clean bed. I don't follow this at all. It sounds to me like you are suggesting not removing a package that is ready to be removed due to python2-rm until it can be fixed. Any bugs on the python2 package are gone as soon as it is. Please don't delay removing packages in order to fix them first. Scott K signature.asc Description: This is a digitally signed message part.
Bug#938157: [Python-modules-team] Bug#938157: python-scipy: Python2 removal in sid/bullseye
> Thanks Sandro. There is RC bug#946624 affecting python-scipy, with a > counterpart in #946625 for python3-scipy. Something subtle has changed > in the syntax for skipping tests, I haven't figured out what yet. Help > needed. > > Since that problem needs to be fixed anyway for python3-scipy, I propose > dealing with that first before decommissioning python-scipy. I expect > that whatever the fix is that's needed for python3-scipy, the same patch > will fix the tests for python-scipy. That way we can put python-scipy > to sleep on a clean bed. what is the benefit of fixing python-scipy, when we can remove it right now? i feel like we could just focus on fixing python3-scipy and use the time/effort for python-scipy for something else :) -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
