Bug 1874760 - rabbitvcs pulls in mercurial dependencies which are totally useless
Summary: rabbitvcs pulls in mercurial dependencies which are totally useless
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitvcs
Version: 32
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-09-02 07:52 UTC by Franco Bugnano
Modified: 2020-09-25 16:46 UTC (History)
4 users (show)

Fixed In Version: rabbitvcs-0.18-2.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-09-25 16:46:16 UTC
Type: Bug

Attachments (Terms of Use)

Description Franco Bugnano 2020-09-02 07:52:11 UTC
Description of problem:
rabbitvcs is a graphical frontend to Subversion and GIT.
Why does installing rabbitvcs pull in mercurial as well, given that it's not supported?

Version-Release number of selected component (if applicable):

How reproducible:
Just install rabbitvcs

Steps to Reproduce:
sudo dnf install rabbitvcs-{cli,nautilus}

Actual results:
the mercurial-py2 package gets installed

Expected results:
Only the packages required tu run rabbitvcs get installed

Additional info:
Given that rabbitvcs is a frontend to either Subversion or GIT, but in 2020 the VCS landscape is pretty much 99% GIT, I don't know if pulling all the VCSs as dependencies makes sense.

I don't know if RPM supports this, but a possible solution could be that:

- If either subversion or git are already installed, then install rabbitvcs without further dependencies
- If neither subversion, nor git is installed, then pull in git as a dependency.

Could a solution like this be ok?

Comment 1 Pete Walter 2020-09-02 09:07:33 UTC
I wonder if it would make sense to not require any particular VCS at all, and just expect the user to already have installed whichever one they want? I'll note that standard Fedora Workstation comes with git installed, so most people should already have that.

Comment 2 Pete Walter 2020-09-04 10:57:59 UTC
I went ahead and did the above dependency change for F33+. I haven't tested it myself so it could be that it causes some unexpected fallout.

Comment 3 Fedora Update System 2020-09-04 11:02:28 UTC
FEDORA-2020-db141558f9 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-db141558f9

Comment 4 Fedora Update System 2020-09-04 19:17:21 UTC
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.

Comment 5 Fedora Update System 2020-09-25 16:46:16 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.