Bug 2125737
| Summary: | sage cannot find nauty binaries | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jsliacan |
| Component: | sagemath | Assignee: | Paulo Andrade <paulo.cesar.pereira.de.andrade> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | paulo.cesar.pereira.de.andrade |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | sagemath-9.6-7.fc37 sagemath-9.6-3.fc36 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-12-30 00:31:18 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: | |||
FEDORA-2022-b6e7a17d24 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b6e7a17d24 FEDORA-2022-878f113400 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-878f113400 FEDORA-2022-878f113400 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-878f113400` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-878f113400 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-b6e7a17d24 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b6e7a17d24` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b6e7a17d24 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-b6e7a17d24 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-878f113400 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |
Description of problem: Sage cannot find any nauty binaries where they're expected. When I query `rpm -ql nauty`, I get: ``` rpm -ql nauty /usr/bin/dreadnaut ... /usr/bin/nauty-geng ... ``` Version-Release number of selected component (if applicable): SageMath version 9.6, Release Date: 2022-05-15 How reproducible: 100% Steps to Reproduce: 1. From sage interpreter type e.g.: ``` sage: gen = graphs.nauty_geng("2") sage: next(gen) ``` Actual results: ``` --------------------------------------------------------------------------- FeatureNotPresentError Traceback (most recent call last) Input In [6], in <cell line: 1>() ----> 1 next(gen) File /usr/lib64/python3.10/site-packages/sage/graphs/graph_generators.py:960, in GraphGenerators.nauty_geng(self, options, debug) 958 import shlex 959 from sage.features.nauty import NautyExecutable --> 960 geng_path = NautyExecutable("geng").absolute_filename() 961 sp = subprocess.Popen(shlex.quote(geng_path) + " {0}".format(options), shell=True, 962 stdin=subprocess.PIPE, stdout=subprocess.PIPE, 963 stderr=subprocess.PIPE, close_fds=True, 964 encoding='latin-1') 965 msg = sp.stderr.readline() File /usr/lib64/python3.10/site-packages/sage/features/__init__.py:619, in Executable.absolute_filename(self) 617 if path is not None: 618 return path --> 619 raise FeatureNotPresentError(self, 620 reason="Executable {executable!r} not found on PATH.".format(executable=self.executable), 621 resolution=self.resolution()) FeatureNotPresentError: nauty_geng is not available. Executable 'geng' not found on PATH. No equivalent system packages for pip are known to Sage. ``` I asked on sage-devel forum, and it was suggested that packaging might be the problem. See [0]. [0] https://groups.google.com/g/sage-devel/c/XVMescQ1hJM