Bug 1767522
| Summary: | rabbitvcs-nautilus does not work in Fedora 31 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Franco Bugnano <fri8k> |
| Component: | rabbitvcs | Assignee: | Pete Walter <walter.pete> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 32 | CC: | belegdol, coelho, edgar.hoch, fedora, gwync, helge, i, jsd, madko, nushio, walter.pete |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rabbitvcs-0.18-1.fc32 rabbitvcs-0.18-1.fc31 rabbitvcs-0.18-2.fc33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-01 19:30:59 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: | |||
Same Problem, at fedora 30 Upstream related: https://github.com/rabbitvcs/rabbitvcs/issues/279 Maybe it's related, maybe it's not. As far as I understand, the latest git snapshot of RabbitVCS supports both Python2 and Python3, both GTK2 and GTK3, so if nautilus-python is built against Python3 and GTK3, then RabbitVCS should already work. I have build version 0.18, it solves the problem for me. I have created a pull request; please build packages for version 0.18. https://src.fedoraproject.org/rpms/rabbitvcs/pull-request/2 still there in Fedora 32 In Fedora 32 the situation is worse, as RabbitVCS not only is at the old 0.17.1 version, but it pulls in the python2 dependencies. Any chance of upgrading to the 0.18 version with Python3 and Gtk3? It looks like Edgar Hoch already fixed the issue on February, will his pull request be merged? any news on this? I went ahead and built the new 0.18 version which should hopefully fix this. FEDORA-2020-0e599300b3 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0e599300b3 FEDORA-2020-d92d298b37 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-d92d298b37 FEDORA-2020-0e599300b3 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0e599300b3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0e599300b3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-d92d298b37 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-d92d298b37` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d92d298b37 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-f647f8ce72 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f647f8ce72` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f647f8ce72 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. rabbitvcs again shows up in nautilus and works. however, the above command line 'dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f647f8ce72' does not work as expected; the --advisory part needs to be replaced by the desired package (base) name to get the bodhi update. (In reply to jan p. springer from comment #14) > rabbitvcs again shows up in nautilus and works. however, the above command > line 'dnf upgrade --enablerepo=updates-testing > --advisory=FEDORA-2020-f647f8ce72' does not work as expected; the --advisory > part needs to be replaced by the desired package (base) name to get the > bodhi update. The command for Fedora 32 dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0e599300b3 works perfect, no need to replace anything. Did you pick the command for your Fedora version? (In reply to jan p. springer from comment #14) > rabbitvcs again shows up in nautilus and works. Please would you leave karma if it works for you? (In reply to Edgar Hoch from comment #15) > The command for Fedora 32 > dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0e599300b3 > works perfect, no need to replace anything. > Did you pick the command for your Fedora version? sorry, my bad. picked the wrong one from the several emails. FEDORA-2020-0e599300b3 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-db141558f9 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-db141558f9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-db141558f9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-d92d298b37 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-db141558f9 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |
Description of problem: The Nautilus extension of RabbitVCS crashes with the following error: Traceback (most recent call last): File "/usr/share/nautilus-python/extensions/RabbitVCS.py", line 71, in <module> import rabbitvcs.vcs.status File "/usr/lib/python3.7/site-packages/rabbitvcs/vcs/status.py", line 403, in <module> class TestStatusObjects(unittest.TestCase): File "/usr/lib/python3.7/site-packages/rabbitvcs/vcs/status.py", line 408, in TestStatusObjects os.path.join(base, chr(x)) for x in range(97,123) File "/usr/lib/python3.7/site-packages/rabbitvcs/vcs/status.py", line 408, in <listcomp> os.path.join(base, chr(x)) for x in range(97,123) NameError: name 'base' is not defined Version-Release number of selected component (if applicable): rabbitvcs-core-0.17.1-11.fc31.noarch python3-rabbitvcs-0.17.1-11.fc31.noarch rabbitvcs-cli-0.17.1-11.fc31.noarch rabbitvcs-nautilus-0.17.1-11.fc31.noarch How reproducible: Always Steps to Reproduce: Install the rabbitvcs-nautilus RPM and run Nautilus. Actual results: Nautilus works, but without the RabbitVCS emblems and context-menu items, and if run from the command line, the traceback is printed. Expected results: Nautilus works, and in a Git repo, there are emblems that show the Git status of each file, and right clicking a file shows additional options (for example to show the file log, or to diff to a previous version). Additional info: It worked on Fedora 29 (using the Python 2 extension). I skipped Fedora 30, so I don't know if it worked there or not.