Bug 2359567
| Summary: | File conflicts: /usr/bin/typer between erlang-dialyzer and python3-typer-cli | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ben Beasley <code> |
| Component: | erlang | Assignee: | Peter Lemenkov <lemenkov> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | atu.guda, jonathan, lemenkov, rhbugs, rjones |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | erlang-26.2.5.13-3.fc42 erlang-26.2.5.13-3.fc41 erlang-26.2.5.14-1.fc43 erlang-27.3.4.16-1.fc45 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-06-30 02:21:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ben Beasley
2025-04-14 19:38:09 UTC
(In reply to Ben Beasley from comment #0) > 1) Remove and Obsolete the python3-typer-cli subpackage from python-typer > for F43. Since python3-typer depends on python3-typer-cli, I guess this isn’t an option. Renaming the entry point might be the best option, even though users of python3dist(typer) might expect "typer" to be available on the PATH. One can only do so much… Do any of the erlang maintainers have any thoughts on this? Thanks. typer is essentially a developer tool: https://www.erlang.org/docs/26/man/typer.html It's not part of Erlang itself, but erlang-dialyzer ("A DIscrepancy AnaLYZer for ERlang programs.") I think renaming the Erlang tool is by far the simplest thing here (erlang-typer?). If you put together a merge request I'm inclined to approve it. Ok, I can do that. Thanks for the reply. Do you have any idea what the
> # FIXME FIXME FIXME this must be installed properly!!!!!!
line in erlang.spec is about?
The comment was added by Peter in 2018. Not sure why. Should it be a symlink? It looks like it already is part of a symlink chain: /usr/bin/typer -> /usr/lib64/erlang/bin/typer -> ../erts-14.2.5.8/bin/typer Maybe the idea is that the binaries shouldn’t live under /usr/lib64/erlang/bin for FHS reasons? I won’t be meddling with that right now. Here’s a PR that would rename the top-level /usr/bin/typer symlink to /usr/bin/erlang-typer: https://src.fedoraproject.org/rpms/erlang/pull-request/6 FEDORA-2025-b8795f48c0 (erlang-26.2.5.13-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-b8795f48c0 FEDORA-2025-ecd29fd194 (erlang-26.2.5.13-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ecd29fd194 FEDORA-2025-ecd29fd194 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ecd29fd194` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ecd29fd194 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-b8795f48c0 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b8795f48c0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b8795f48c0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-f9773dd65e has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f9773dd65e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f9773dd65e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-756e2073fe has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-756e2073fe` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-756e2073fe See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-756e2073fe (erlang-26.2.5.13-3.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-f9773dd65e (erlang-26.2.5.13-3.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-10dce3189a (erlang-26.2.5.14-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-10dce3189a FEDORA-2025-10dce3189a (erlang-26.2.5.14-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2026-163f944889 (erlang-27.3.4.16-1.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-163f944889 FEDORA-2026-163f944889 (erlang-27.3.4.16-1.fc45) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report. |