Re: Updating pytest

2022-06-02 Thread julien . puydt
Le jeudi 02 juin 2022 à 10:28 -0400, Sandro Tosi a écrit :
> > I would suggest ratt-rebuilding all reverse dependencies. Could
> > that be
> > done?
> 
> there order of thousands rdeps, i dont think it's fair to ask any
> individual contributor the time and resources to check that via ratt.

Agreed. If the list of packages to check can't be handled by my modest
setup during the night, I won't check them all.

> Something i've done in the past (f.e. with numpy and matplotlib) is
> leveraging Lucas' archive rebuild infrastructure to run a rebuild the
> rdeps with a new package, usually uploaded in experimental.

When I upgrade a package with a number of rdeps I deem unreasonable for
my setup, I pick some rdeps semi-randomly (mostly random, but having a
look at the list to hand-pick a few promising ones, or make sure I drop
problematic ones [sagemath comes to mind]).

That won't guarantee nothing will break, but does detect glaring
issues.

And indeed, uploading to experimental and giving people a head's up if
there's a thousand rdeps and you can only test 1% is important.

Cheers,

J.Puydt



Re: Updating pytest

2022-06-02 Thread Sandro Tosi
> I would suggest ratt-rebuilding all reverse dependencies. Could that be
> done?

there order of thousands rdeps, i dont think it's fair to ask any
individual contributor the time and resources to check that via ratt.

Something i've done in the past (f.e. with numpy and matplotlib) is
leveraging Lucas' archive rebuild infrastructure to run a rebuild the
rdeps with a new package, usually uploaded in experimental.

I think a service should be provided to developers/maintainers to test
their packages against their rdeps, but it's not there yet (i prepared
an initial plan for it, but never got to actually implement it).

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi



Re: Joining the team

2022-06-02 Thread Stefano Rivera
Hi Ben (2022.06.01_20:42:21_+)
> I sent this message to the mailing list over a month ago and also asked
> about it on IRC, getting no response from either platform. The Wiki says
> this is how I join the team, so I'm just sending it again.

Sorry about the delay. Welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Updating pytest

2022-06-02 Thread Andrius Merkys
Hi Julian,

On 2022-06-02 11:23, Julian Gilbey wrote:
> When I updated pytest-mock, I noticed that pytest is somewhat out of
> date and it would be good to upgrade it.  But it's quite a major
> package, and I don't really want to do it without a go-ahead from
> others.
> 
> Perhaps we could upload a newer version to experimental first to see
> what breaks?

I would suggest ratt-rebuilding all reverse dependencies. Could that be
done?

Best,
Andrius



Updating pytest

2022-06-02 Thread Julian Gilbey
Hi all,

When I updated pytest-mock, I noticed that pytest is somewhat out of
date and it would be good to upgrade it.  But it's quite a major
package, and I don't really want to do it without a go-ahead from
others.

Perhaps we could upload a newer version to experimental first to see
what breaks?

Best wishes,

   Julian