`python-fslpy` provides files that conflict with `cyrus-imapd`. Please, rename the wrapper script and its manual page so it doesn't conflict with files provided by `cyrus-imapd`. Reproducible: Always Steps to Reproduce: 1. dnf install cyrus-imapd -y 2. dnf install python-fslpy -y Actual Results: - file /usr/bin/imtest from install of python3-fslpy-3.13.3-1.fc39.noarch conflicts with file from package cyrus-imapd-utils-3.6.0-9.fc39.x86_64 - file /usr/share/man/man1/imtest.1.gz from install of python3-fslpy-3.13.3-1.fc39.noarch conflicts with file from package cyrus-imapd-utils-3.6.0-9.fc39.x86_64 Expected Results: No conflicts
Requested upstream: https://github.com/pauldmccarthy/fslpy/issues/18
Hi @mosvald , unfortunately, `imtest` in fslpy is very very commonly used in the FSL ecosystem---which is sort of the standard pipeline for neuroimaging data analysis. Here's what upstream said: """ Hi @sanjayankur31, this is unfortunately not a trivial change for us, as there are several hundred calls to $FSLDIR/bin/imtest in other FSL scripts/applications. However, if I understand correctly, you're only packaging fslpy so that you can package FSLeyes, right? FSLeyes doesn't use the imtest command, so you could safely re-name it in your fslpy package without affecting FSLeyes at all... P.S. You're correct in that cyrus-imapd claimed the imtest name first, although it was only by a few years! The imtest script has existed in FSL in one form or another since 2004 :) """ Here's some information on FSL: https://fsl.fmrib.ox.ac.uk/fsl/fslwiki/FSL Packaging other FSL pipeline tools is on our list of todos (a very long list at the moment: https://pagure.io/neuro-sig/NeuroFedora/issues?tags=T%3A+Software&status=Open). However, irrespective of what tools we package, even if renaming doesn't affect fsleyes, users that do install the other FSL tools will have to update all their scripts. These are often whole pipelines that have been setup at various research groups by technicians and it'll be quite a bit of fiddling for the academics (usually very non-technical) to tweak. I know cyrus-imapd claimed `imtest` first, but is it as commonly/widely used as the `imtest` in fslpy? If not, could that be renamed instead?
Interesting. Did the cyrus-imapd maintainers do some housekeeping? I received a bug report regarding a naming conflict myself. It's not a NeuroFedora package, though.
Hi Ankur, thank you for the background info about the `imtest` usage and problems/difficulties that could arise for the users. In that light changing the imtest for cyrus-imapd to e.g. cyr_imtest would sound easier. I am currently investigating the feasibility to rename it on cyrus-imapd's side: https://src.fedoraproject.org/fork/mosvald/rpms/cyrus-imapd/c/7673496ec0880a5157fd0b39ddbc226854d47f4b?branch=rename_imtest The upstream itself is aware of possible binary name clashes so they themselves are encouraging to rename them: https://www.cyrusimap.org/imap/download/packagers.html#binary-naming There is also an upstream issue opened for that, but nothing happened for a long time there: https://github.com/cyrusimap/cyrus-imapd/issues/2027 So for now I am keeping the component the same and if there are no obstacles I will change it to cyrus-imapd then. Regarding the other issue which popped up in comment #3 (bug 2228002), I would really like to have it renamed because it is used a lot by the user base unlike the imtest and we have it mentioned in our knowledge base articles for RHEL. If only these conflicts were discovered earlier.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.