AH , now I can see the restriction:
https://github.com/mitogen-hq/mitogen/blob/master/ansible_mitogen/loaders.py#L52
Then it is the correct of the package to enforce that as well.
I still hope upstream comes to the conclusion, that this is wrong and
goes this way:
https://github.com/mitogen-hq/mitogen/issues/961

And You say while the burden of providing ansbile-mitogen is still on
the pyhon packaging team You would patch up 0.3.3 with
https://github.com/mitogen-hq/mitogen/pull/933 ?

Should I also try ? What are the next steps ?

Am So., 11. Sept. 2022 um 23:00 Uhr schrieb <stefa...@debian.org>:
>
> control: retitle -1 Support ansible 6 (2.13)
>
> Hi Florian (2022.09.11_20:09:21_+0000)
> > Looking at https://tracker.debian.org/pkg/python-mitogen
> > under actions it says:  "unsatisfied dependency on ansible-core (< 2.13)  "
> >
> > Now ansible-core 2.13.3-1 has a regression:
> > https://tracker.debian.org/pkg/ansible-core
> > "... makes ansible-mitogen/0.3.3-2/amd64 uninstallable".
>
> Aha, yes, that is just the problem.
>
> That restriction on 2.13 came from upstream. We include it as a package
> Depends, so that users know early that it won't work.
>
> Mitogen itself checks the version of ansible and fails if it's too new.
>
> We're going to need https://github.com/mitogen-hq/mitogen/pull/933 (and
> possibly other patches)
>
> SR
>
> --
> Stefano Rivera
>   http://tumbleweed.org.za/
>   +1 415 683 3272

Reply via email to