The AUH upgrade from python3-meson-python 0.15.0 to 0.16.0 failed with an odd error[1]: fatal: pathspec 'tests/packages/encoding/343203206343202271343203210.py' did not match any files Manually upgrading the recipe to the 0.16.0 version had no issues. Hunting down the error leads to the conclusion that 'devtool upgrade' cannot handle file names with unicode characters: ls meson_python-0.16.0/tests/packages/encoding/ meson.build pyproject.toml テスト.py NOTE: the 0.15.0 version did not have tests/packages/encoding at all [1] https://lore.kernel.org/openembedded-core/CAOyo-84ow3Ugj8=qFD5bNrpq23t8xPKZ-E0L8=KvvkCVHnOVPg@mail.gmail.com/T/#u
I have a recollection that using unicode characters in layer names also does not work, so this might be a limitation of bitbake or elsewhere and not a problem in devtool itself. e.g. meta-🎉 can be created by "bitbake-layers create-layer meta-🎉" but cannot added to bblayers.conf by "bitbake-layers add-layer meta-🎉" or something like that. This was one of the reasons I filed this bug to define what can and cannot be in a layer name: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15375
There are likely lots of assumption on ASCII strings only for filenames.
I would like to work on this bug.
Hi, I attempted to reproduce this issue on current OE-Core master (using BitBake 2.19.0). Steps performed: - Used upstream meson-python git source (version 0.16.0) which contains unicode filenames such as: tests/packages/encoding/テスト.py - Ran devtool upgrade with explicit version and source tree Result: devtool upgrade completed successfully without any errors. The unicode filename was handled correctly, and no pathspec errors occurred. Conclusion: It appears that this issue has already been resolved in the current devtool/BitBake implementation. Could you please confirm if this bug can be closed? Thanks, Aditya