Re: CVS commit: pkgsrc/math/py-scipy

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Wed, Apr 07, 2021 at 08:34:35AM +0000, nia wrote:
> On Wed, Apr 07, 2021 at 09:25:36AM +0100, Patrick Welche wrote:
> > On Wed, Apr 07, 2021 at 08:12:47AM +0000, nia wrote:
> > > On Tue, Apr 06, 2021 at 04:44:25PM +0100, Patrick Welche wrote:
> > > > On Tue, Apr 06, 2021 at 01:11:17PM +0000, Nia Alarie wrote:
> > > > > Module Name:  pkgsrc
> > > > > Committed By: nia
> > > > > Date:         Tue Apr  6 13:11:17 UTC 2021
> > > > > 
> > > > > Modified Files:
> > > > >       pkgsrc/math/py-scipy: Makefile
> > > > > 
> > > > > Log Message:
> > > > > py-scipy: unbreak bulk builds
> > > > > 
> > > > > if you mark a package incompatible with python version X, you also
> > > > > need to mark any dependent packages incompatible with version X
> > > > 
> > > > I think the person who updated the package was right in marking
> > > > it not suitable for 3.6. 
> > > > 
> > > > So is it that the failure mode of the bulk build will now be in
> > > > some sense better?
> > > > Is this a general python version issue better solved in pbulk?
> > > 
> > > If you mark a package incompatible with Python version X without
> > > also marking dependent packages incompatible, the pbulk resolver
> > > will be unable to resolve dependencies, and bulk builds will break
> > > (stop running).
> > 
> > Doesn't pbulk have all of the information at its disposal?
> 
> Not unless you mark dependent packages incompatible so it stops
> trying to resolve depends for that version.

Which the human uses pbulk to find out to tell pbulk what it already knows.

There isn't a decision for the human to make, is there? Am I missing something?