Hello, I'm installing latest version of transmission, transmission-daemon and transmission-web, version 3.00, using portmaster using following command: portmaster net-p2p/transmission net-p2p/transmission-daemon www/transmission-web Unfortunately, when trying to install transmission-daemon-3.00, process fails with following error: ===> Installing for transmission-daemon-3.00 ===> Checking if transmission-daemon is already installed ===> Registering installation for transmission-daemon-3.00 Installing transmission-daemon-3.00... pkg-static: transmission-daemon-3.00 conflicts with transmission-cli-3.00 (installs files into the same place). Problematic file: /usr/local/bin/transmission-create *** Error code 70 Stop. make[1]: stopped in /srv/nas/freebsd-ports/net-p2p/transmission-daemon *** Error code 1 Stop. make: stopped in /srv/nas/freebsd-ports/net-p2p/transmission-daemon ===>>> Installation of transmission-daemon-3.00 (net-p2p/transmission-daemon) failed ===>>> Aborting update Output of "pkg list transmission-cli": [root@nas ~]# pkg list transmission-cli /usr/local/bin/transmission-cli /usr/local/bin/transmission-create /usr/local/bin/transmission-edit /usr/local/bin/transmission-remote /usr/local/bin/transmission-show /usr/local/man/man1/transmission-cli.1.gz /usr/local/man/man1/transmission-create.1.gz /usr/local/man/man1/transmission-edit.1.gz /usr/local/man/man1/transmission-remote.1.gz /usr/local/man/man1/transmission-show.1.gz /usr/local/share/doc/transmission-cli/AUTHORS /usr/local/share/doc/transmission-cli/COPYING /usr/local/share/doc/transmission-cli/NEWS.md /usr/local/share/doc/transmission-cli/README.md /usr/local/share/doc/transmission-cli/rpc-spec.txt /usr/local/share/doc/transmission-cli/send-email-when-torrent-done.sh /usr/local/share/licenses/transmission-cli-3.00/LICENSE /usr/local/share/licenses/transmission-cli-3.00/MIT /usr/local/share/licenses/transmission-cli-3.00/catalog.mk portmasterfail.txt does not show much, though: cat portmasterfail.txt portmaster <flags> net-p2p/transmission-daemon Please let me know if there's anything else you need from me. Thank you
Hello! o/ First of all transmission-cli is self-contained and can't be used as transmission-daemon client, just transmission-gtk does (unless the support was also added to transmission-qt too, IDK) otherwise third party tools like Tremc also does. That said, both transmission-cli and transmission-daemon need ENABLE_UTILS (transmission-create, transmission-show etc.) to be fully functional, and then the files will conflict. In 2.xx series there were some differences of how transmission was built and the conflict could be avoided, but not anymore. PS. I will leave this open for a while. Thank you.
Thanks Alexandre for the feedback! I perfectly understand the reason is due to changes on how version 3.x vs 2.y transmission is built; this leads me to the following question, then: is it possible to change transmission configuration to make sure only one of "CLI" or "Daemon" options is chosen when building from source? I know it should, but would it make sense given new port behaviour? Let me know if there's anything else you need from me
(In reply to Alessandro Sagratini from comment #2) If you are asking about the ability to enable/disable the ENABLE_UTILS support, this is feasible, and I am already considering adding that OPTION since several people asked the same, but I may just have time during the weekend or the next. If you are in a hurry you can modify this line on the transmission-cli Makefile, removing the transmission variant you *don't* want to have the utils tooling: . if ${SLAVEPORT:Nweb:Ncli:Ndaemon}
thanks for the prompt answer Alexandre, you are correct; I think we can: 1. either add a flag to enable/disable ENABLE_UTILS support option for cli and daemon packages so only one of them will provide those tools 2. alternatively. the other option I was thinking about is using "OPTIONS_SINGLE" in net-p2p/transmission Makefile to make sure only cli *or* daemon is chosen Based on your feedback, I understand it's a better idea to go with first option? Finally, I am not really in a rush, at the moment and I can wait a couple of weeks til new patch is out :) Let me know if there's anything else you need from me, thank you
(In reply to Alessandro Sagratini from comment #4) I need to look at it carefully because this port is particularly annoying to make changes. :-/
sure, that is absolutely fine :) If my thoughts are not applicable, we can think about a different solution
The transmission port isn't just 1 port but involves a meta port, a master port, slaves ports, and a flavored slave port... everything tied in a complicated setup where you touch something in here and this break something in there. In regards to using OPTIONS_SINGLE, in short, can't be done[1]. It can't be used to tell like if this option is ON for this slave port then disable for that one. [1] may eventually be feasible but with a over-complicated setup.
not a problem Alexandre, thanks for the feedback! At this point, I'm good with adding my interest in adding ENABLE_UTILS option to the port, if feasible: I'm not sure we should leave this PR opened, but if there's another one for the same exact request, we can simply go ahead and close this
A commit references this bug: Author: rigoletto Date: Wed May 20 01:52:07 UTC 2020 New revision: 535962 URL: https://svnweb.freebsd.org/changeset/ports/535962 Log: net-p2p/transmission: Allow all variants to be installed concurrently - split utils in a separated port PR: 246272 Differential Revision: https://reviews.freebsd.org/D24851 Changes: head/net-p2p/Makefile head/net-p2p/transmission/Makefile head/net-p2p/transmission-cli/Makefile head/net-p2p/transmission-cli/pkg-plist head/net-p2p/transmission-daemon/Makefile head/net-p2p/transmission-daemon/pkg-plist head/net-p2p/transmission-gtk/Makefile head/net-p2p/transmission-utils/ head/net-p2p/transmission-utils/Makefile head/net-p2p/transmission-utils/pkg-descr head/net-p2p/transmission-utils/pkg-plist
Fixed. Thanks! :-D