Re: Status of pymodbus (was: Status of sqlalchemy)
Hi, I finally got it working here ! For a very short time. Then it breaks again with today's new Pytest. https://salsa.debian.org/python-team/packages/pymodbus/-/jobs/5780102 -> "test" branch. https://github.com/pytest-dev/pytest/issues/12269 It needs a new pytest-asyncio ... https://tracker.debian.org/pkg/python-pytest-asyncio I look at it. Greetings Le mar. 23 avr. 2024 à 00:06, Martin a écrit : > > Hi Alexandre, > > I pushed my changes to debian/master. If you have time to work on > pymodbus (e.g. update disable-failing-unittests.patch), please go on. > I probably can't work on that this week. > > Cheers
Re: Status of pymodbus (was: Status of sqlalchemy)
helper.py is not so helpful (and not even used in test/conftest.py ?) anyway it builds now but maybe upstream would accept a patch to help reduce the downstream patch (maybe read certificates location from env variable, this needs more eyes) It's almost done. Greetings Le mar. 23 avr. 2024 à 00:06, Martin a écrit : > > Hi Alexandre, > > I pushed my changes to debian/master. If you have time to work on > pymodbus (e.g. update disable-failing-unittests.patch), please go on. > I probably can't work on that this week. > > Cheers
Re: Status of pymodbus (was: Status of sqlalchemy)
Hi Alexandre, I pushed my changes to debian/master. If you have time to work on pymodbus (e.g. update disable-failing-unittests.patch), please go on. I probably can't work on that this week. Cheers
Re: Status of pymodbus (was: Status of sqlalchemy)
Le lun. 22 avr. 2024, 09:57, Martin a écrit : > > 1. privacy-breach-fixes.patch (I updated this, can push > These ones are annoying to maintain. I wish dh_installdocs would be smart enough to strip these tiny widget that are present in so many Readme.md on GitHub. They re quite formulaic and it could be done with a regexp (but dh is in Perl ). Thanks
Re: Status of pymodbus (was: Status of sqlalchemy)
Quoting Alexandre Detiste : I ll check back home, but it's most likely I was waiting for SQLAlchemy 2.xx. Good! I know for share that one package does wait for SA 2.xx but can t remember which one. It looksk like all but one of the debian/patches are obsolete now? It seems, that *two* patches need to stay, but need work: 1. privacy-breach-fixes.patch (I updated this, can push later) 2. disable-failing-unittests.patch (needs more work, don't hold your breath) There are also two (?) new build-depends. Again, I can push later. debian/rules needs a minor PYTHONPATH fix. Will push when back home ;-) Cheers
Re: Status of pymodbus (was: Status of sqlalchemy)
Hi, I ll check back home, but it's most likely I was waiting for SQLAlchemy 2.xx. I know for share that one package does wait for SA 2.xx but can t remember which one. > It looks like all but one of the debian/patches are obsolete now? Sure Le lun. 22 avr. 2024, 08:09, Martin a écrit : > On 2024-04-15 11:38, Alexandre Detiste wrote: > > Le lun. 15 avr. 2024 à 11:20, Thomas Goirand a écrit : > >> The rest of: > >> - pymodbus > >> > >> I don't even know what they do. > > > > Life is better when one does not have to deal with modbus :-) > > Yes! > > > This package is outdated and need a refresh. > > As I see, you already pushed a new upstream to git in January/February, > but did not yet upload the package. Are there any blockers? It looks > like all but one of the debian/patches are obsolete now? >
Status of pymodbus (was: Status of sqlalchemy)
On 2024-04-15 11:38, Alexandre Detiste wrote: > Le lun. 15 avr. 2024 à 11:20, Thomas Goirand a écrit : >> The rest of: >> - pymodbus >> >> I don't even know what they do. > > Life is better when one does not have to deal with modbus :-) Yes! > This package is outdated and need a refresh. As I see, you already pushed a new upstream to git in January/February, but did not yet upload the package. Are there any blockers? It looks like all but one of the debian/patches are obsolete now?
