Bug#930928: mypy: New upstream release

2019-06-23 Thread Salvo Tomaselli
Oh I had no idea the new version is much different in the way it works. Yeah I guess experimental would work. Il giorno dom 23 giu 2019 alle ore 08:47 Michael Crusoe ha scritto: > > How about we start on the latest version via an upload to experimentsl? > > I must admit that I don't have a

Bug#930928: mypy: New upstream release

2019-06-23 Thread Michael Crusoe
How about we start on the latest version via an upload to experimentsl? I must admit that I don't have a plan for the new compiled versions of mypy yet. -- Michael R. Crusoe On Sun, Jun 23, 2019, 01:21 Salvo Tomaselli wrote: > Hello, > > I understand, but at this stage, with release almost

Bug#930928: mypy: New upstream release

2019-06-22 Thread Salvo Tomaselli
Hello, I understand, but at this stage, with release almost there, uploading to unstable would not be so bad I guess. Anyway my problem is that localslackirc uses github and there it pulls mypy from pip (so latest version) but in debian of course it builds with the package, so having the

Bug#930928: mypy: New upstream release

2019-06-22 Thread Michael Crusoe
Hello, During a freeze I don't upload new versions to unstable. On Sat, Jun 22, 2019 at 6:51 PM Salvo Tomaselli wrote: > Package: mypy > Version: 0.670-2 > Severity: normal > > Dear Maintainer, > > there is a new upstream release for this. > > Could you upgrade? > > If needed, I can help. > >

Bug#930928: mypy: New upstream release

2019-06-22 Thread Salvo Tomaselli
Package: mypy Version: 0.670-2 Severity: normal Dear Maintainer, there is a new upstream release for this. Could you upgrade? If needed, I can help. Best -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64