Marcin Cieślak

Is there anyway to use this in the Jenkins Artifactory plugin? At minimum, supply the checksum not to override file if it is the same?

That is very kind of you to tag me here but I don't have the powers to do anything about it. Still running a locally modified version of https://github.com/NXPmicro/spsdk/releases/tag/0.2.2, wonder...

Don't we have the same problem with https://pypi.org/project/pylink-square/ ? Maybe [those imports](https://github.com/NXPmicro/spsdk/blob/5ab36c5db3cda4a118d4d09bc42d6e6c60900a1e/spsdk/debuggers/__init__.py#L11-L12) should be wrapped in `try: ... except ImportError: ` and remove them from requirements.txt? J-Link works with OpenOCD...

> > Don't we have the same problem with https://pypi.org/project/pylink-square/ ? > > Why? Does it also bundle shared libraries with obfuscated code from unknown origin? ;-) https://pypi.org/project/pylink-square/ Python interface...

``` (nxp) m.saper.info> /usr/local/bin/virtualenv-3.8 ~/nxp Using base prefix '/usr/local' New python executable in /home/saper/nxp/bin/python3.8 Also creating executable in /home/saper/nxp/bin/python Installing setuptools, pip, wheel... done. (nxp) m.saper.info> pip install pylink-square Collecting...

But good news is, those packages do install, they just don't work - I don't see a problem here.

I see what you mean: ``` > find nxp/lib/python3.8/site-packages/pypemicro -type f nxp/lib/python3.8/site-packages/pypemicro/__init__.py nxp/lib/python3.8/site-packages/pypemicro/pemicro_const.py nxp/lib/python3.8/site-packages/pypemicro/libs/Linux/unitacmp-64.so nxp/lib/python3.8/site-packages/pypemicro/libs/MacOS/unitacmp-64.dylib nxp/lib/python3.8/site-packages/pypemicro/libs/MacOS/libusb.dylib nxp/lib/python3.8/site-packages/pypemicro/libs/Windows/unitacmp-32.dll nxp/lib/python3.8/site-packages/pypemicro/libs/Windows/unitacmp-64.dll nxp/lib/python3.8/site-packages/pypemicro/__pycache__/pemicro_const.cpython-38.pyc nxp/lib/python3.8/site-packages/pypemicro/__pycache__/pemicro.cpython-38.pyc nxp/lib/python3.8/site-packages/pypemicro/__pycache__/__init__.cpython-38.pyc nxp/lib/python3.8/site-packages/pypemicro/pemicro.py ``` I'd say this is a distribution policy...

Thank you @mstarecek - [OP](https://support.nitrokey.com/t/nitropy-on-bsds/4833) here. Yes, the main problem is there is no place to discuss eventual changes to `libusbsio`. I think it could easily support upstream, unchanged https://github.com/signal11/hidapi....

There are two conflicting goals: - integrators (like myself) that use SPSDK as a library demand flexibility because they need to satisfy other dependencies - end-users who just for example...

Seems like this change might break access to some HSMs https://bugzilla.redhat.com/show_bug.cgi?id=2298882 https://github.com/alonbl/gnupg-pkcs11-scd/issues/63