PEP 541 Request: Kconfiglib #2526
Comments
|
Just to add my support here as I have been trying to contact the original author also. There are unanswered PRs going back >2 years https://github.com/ulfalizer/Kconfiglib/pulls I have a PR that was raised a year ago. This is a very useful project and it is important to move it to a new owner. We have identified someone is willing and able to maintain it: https://github.com/jackrosenthal Without this request being approved our only option is to rename the package, which will create a lot of confusion. |
|
In fact the original author went inactive not just in this project but all across the Internet:
This has been confirmed by people trying to contact him using other methods. |
|
Dear pypi maintainers, can we get an update on this request, please? |
|
I didn't find any "escalation" process at https://pypi.org/help/#project-name-claim, https://peps.python.org/pep-0541/#how-to-request-a-name-transfer There is however a link to the obsolete distutils-sig mailing list: https://mail.python.org/archives/list/[email protected]/thread/TINMM5LQKQTTJDVGC224RMG7JGPXL4MQ/ I think it has been moved to https://discuss.python.org/t/about-the-packaging-category/365 |
|
Scanning https://github.com/pypi/support/issues?q=sort%3Aupdated-desc+label%3A%22PEP+541%22+is%3Aclosed I found that @yeraydiazdiaz worked on a number of PEP 541 requests 2 weeks ago but unfortunately not this one :'-( |
|
@yeraydiazdiaz could you or someone else please help with this? Zephyr is an incredibly active and popular project with a spectacular track record. It's an official Linux Foundation project backed by some of the largest companies in the industry. It's been called the "Linux of the embedded world" across the technical press. Could you or someone else please unblock it? More background info if needed: zephyrproject-rtos/zephyr#53894 EDIT: I just cried for help in https://discuss.python.org/t/official-zephyr-project-getting-desperate-with-2-months-old-pep-541-name-claim/24431 |
|
Hi all, I will now start the reachability process for your request which can take up to 6 weeks. Thank you for gathering resources regarding the owner, hopefully we can get a response soon and proceed with the transfer. |
|
Hi @yeraydiazdiaz wondering if the reachability process has completed. Thanks! |
|
Hi @yeraydiazdiaz, bumping up this request, since it's now been well beyond 6 weeks since the last update. Thanks! |
|
Has there been any progress regarding this request in the meantime? |
|
@yeraydiazdiaz could you please update us on this issue? It's now been several months with no news. |
There is bunch of kernel config options that are not propagated correctly to the kernel configuration after fragments are merged and processed by Kconfig. Current Buildroot tools are not good at discovering these - while we cleaned up most inconsistencies by using linux-diff-config and output from the merge_config.sh script, there are still options that are deprecated or get a different value than intended because of dependencies, etc. This commit adds a Python script that is using Kconfiglib to parse current kernel's Kconfig files and the generated .config and compare the requested values from individual kernel config fragments. The script can be used manually by running `make linux-check-dotconfig` from the buildroto directory (with path to BR2_EXTERNAL directory set) and it's called also from the CI, where it generates Github Workflow warning annotations when some of the values are not present or set correctly. The kconfiglib.py is checked-in to the repo as well, because the library is currently abandoned on PyPI and packaged version has a bug that causes errors parsing Kconfigs in newer Linux versions, fixed in outstanding pull request ulfalizer/Kconfiglib#119 - so version from this PR is used here. If pypi/support#2526 is ever resolved, we could remove it from our repo and use pip for installing the package as a requirement during build of the build container.
There is bunch of kernel config options that are not propagated correctly to the kernel configuration after fragments are merged and processed by Kconfig. Current Buildroot tools are not good at discovering these - while we cleaned up most inconsistencies by using linux-diff-config and output from the merge_config.sh script, there are still options that were removed or get a different value than intended because of dependencies, etc. This commit adds a Python script that is using Kconfiglib to parse current kernel's Kconfig files and the generated .config and compare the requested values from individual kernel config fragments. The script can be used manually by running `make linux-check-dotconfig` from the buildroto directory (with path to BR2_EXTERNAL directory set) and it's called also from the CI, where it generates Github Workflow warning annotations when some of the values are not present or set correctly. The kconfiglib.py is checked-in to the repo as well, because the library is currently abandoned on PyPI and packaged version has a bug that causes errors parsing Kconfigs in newer Linux versions, fixed in outstanding pull request ulfalizer/Kconfiglib#119 - so version from this PR is used here. If pypi/support#2526 is ever resolved, we could remove it from our repo and use pip for installing the package as a requirement during build of the build container.
There is bunch of kernel config options that are not propagated correctly to the kernel configuration after fragments are merged and processed by Kconfig. Current Buildroot tools are not good at discovering these - while we cleaned up most inconsistencies by using linux-diff-config and output from the merge_config.sh script, there are still options that were removed or get a different value than intended because of dependencies, etc. This commit adds a Python script that is using Kconfiglib to parse current kernel's Kconfig files and the generated .config and compare the requested values from individual kernel config fragments. The script can be used manually by running `make linux-check-dotconfig` from the buildroot directory (with path to BR2_EXTERNAL directory set) and it's called also from the CI, where it generates Github Workflow warning annotations when some of the values are not present or when set incorrectly. The kconfiglib.py is checked-in to the repo as well, because the library is currently abandoned on PyPI and packaged version has a bug that causes errors parsing Kconfigs in newer Linux versions, fixed in outstanding pull request ulfalizer/Kconfiglib#119 - so version from this PR is used here. If pypi/support#2526 is ever resolved, we could remove it from our repo and use pip for installing the package as a requirement during build of the build container.
There is bunch of kernel config options that are not propagated correctly to the kernel configuration after fragments are merged and processed by Kconfig. Current Buildroot tools are not good at discovering these - while we cleaned up most inconsistencies by using linux-diff-config and output from the merge_config.sh script, there are still options that were removed or get a different value than intended because of dependencies, etc. This commit adds a Python script that is using Kconfiglib to parse current kernel's Kconfig files and the generated .config and compare the requested values from individual kernel config fragments. The script can be used manually by running `make linux-check-dotconfig` from the buildroot directory (with path to BR2_EXTERNAL directory set) and it's called also from the CI, where it generates Github Workflow warning annotations when some of the values are not present or when set incorrectly. The kconfiglib.py is checked-in to the repo as well, because the library is currently abandoned on PyPI and packaged version has a bug that causes errors parsing Kconfigs in newer Linux versions, fixed in outstanding pull request ulfalizer/Kconfiglib#119 - so version from this PR is used here. If pypi/support#2526 is ever resolved, we could remove it from our repo and use pip for installing the package as a requirement during build of the build container.
There is bunch of kernel config options that are not propagated correctly to the kernel configuration after fragments are merged and processed by Kconfig. Current Buildroot tools are not good at discovering these - while we cleaned up most inconsistencies by using linux-diff-config and output from the merge_config.sh script, there are still options that were removed or get a different value than intended because of dependencies, etc. This commit adds a Python script that is using Kconfiglib to parse current kernel's Kconfig files and the generated .config and compare the requested values from individual kernel config fragments. The script can be used manually by running `make linux-check-dotconfig` from the buildroot directory (with path to BR2_EXTERNAL directory set) and it's called also from the CI, where it generates Github Workflow warning annotations when some of the values are not present or when set incorrectly. The kconfiglib.py is checked-in to the repo as well, because the library is currently abandoned on PyPI and packaged version has a bug that causes errors parsing Kconfigs in newer Linux versions, fixed in outstanding pull request ulfalizer/Kconfiglib#119 - so version from this PR is used here. If pypi/support#2526 is ever resolved, we could remove it from our repo and use pip for installing the package as a requirement during build of the build container.
|
Since Yuray seems to no longer be involved, we will restart the reachability process. |
|
We are working to contact the owner to determine if they're reachable. Disclaimer: We are providing support to the PyPI Administrators to validate this request and make a recommendation on the outcome and actions to be taken. Final determination will be made by the PyPI Administrators when our process is complete. |
|
We could not reach the owner, and we consider the project abandoned per |
|
@encukou it's now been a while since this process was started, is there a chance we can resolve this in the near future? Thanks in advance! |
|
I'm sorry, but I don't know. It's up to the PyPI admins now. |
|
@carlescufi have you reached out to [email protected] ? |
No, I have not. Do you want to do it yourself @kartben ? |
|
|
Project to be claimed
Kconfiglib: https://pypi.org/project/kconfiglibYour PyPI username
zephyr-project: https://pypi.org/user/zephyr-project/Reasons for the request
The original author of the widely used library Kconfiglib is no longer active or reachable.
Since the Zephyr Project is a heavy user of Kconfiglib we have volunteered to take over the project and maintain it. In order to avoid having to rename it it would be great if we could take over the PyPI package.
Maintenance or replacement?
Maintenance
Source code repositories URLs
Current project: https://github.com/ulfalizer/Kconfiglib
Future home: https://github.com/zephyrproject-rtos/Kconfiglib
Contact and additional research
We have tried contacting him for nearly 3 years using every means possible to no avail. This includes email, professional telephone number, GitHub mentions and even his personal phone number.
Code of Conduct
The text was updated successfully, but these errors were encountered: