Red Hat Bugzilla – Bug 222506
cyrus-imapd conflicts with uw-imap
Last modified: 2008-03-19 15:47:19 EDT
Description of problem: cyrus-imapd - 2.3.7-6.fc7.i386 File conflict with: /etc/pam.d/imap File conflict with: /etc/pam.d/imap File conflict with: /etc/pam.d/pop File conflict with: /etc/pam.d/pop File conflict with: /etc/pam.d/pop File conflict with: /etc/pam.d/pop File conflict with: /usr/share/man/man8/imapd.8.gz File conflict with: /etc/pam.d/imap File conflict with: /etc/pam.d/imap => Package conflicts with: uw-imap - 2006d-1.fc7.i386 Version-Release number of selected component (if applicable): cyrus-imapd-2.3.7-6 How reproducible: Everytime, see above. Actual results: Package conflicts with: uw-imap - 2006d-1.fc7.i386 Expected results: Can we rename /etc/pam.d/{imap,pop} etc. somehow? Additional info: Vice versa bug report is filed in bug #222486: uw-imap - 2006d-1.fc7.i386 File conflict with: /etc/pam.d/imap File conflict with: /etc/pam.d/pop File conflict with: /usr/share/man/man8/imapd.8.gz => Package conflicts with: cyrus-imapd - 2.3.7-6.fc7.i386
The manpage conflict could be easily solved by adding a prefix like: /usr/share/man/man8/imapd.8cyrus.gz And I think we might possibly solve the pam.d one by unifying the contents of the files -- that would mean cyrus having the additional entries uw-imapd has. Or would you rather rename them, Rex?
I like both of your suggestions. Patching for renamed pam file sounds a little scary, though I'm not sure how to manage having shared/common pam files rpm-wise though, that may be even more pain.
Further, someone/somewhere may be crazy enough to want separate/different pam configs for cyrus-imapd vs. uw-imap\ Hmm... I'll go scrounging around other distros packaging (debian, mandriva, pld, suse) to see if they've hit this, and how they dealt with it.
I think that having those files binary identical will make rpm not complaint. And since your pam config just adds something that shouldn't break cyrus, it can probably be solved just by using your pam config in cyrus. Anyway, I'll be happy to hear what you found out.
At PLD cyrus-imap simply conflicts uw-imap but not the other way round as far as I could see. At Debian it looks like they're just sharing the common files, because I can't detect any conflicts there, but maybe I'm wrong. At SuSE, the cyrus-imap conflicts with imap but not vice versa. And at Mandriva the imap package conflicts with cyrus-imapd, but not the other way round. So none of the other distributions solved this "problem", yet.
So what do you suggest? Doing it the (probably) debian way -- making the files look the same, or spend the time renaming the pam services? The first way is probably very quick, but Fedora rules like the other one :)
Ping.
Let's try the "making the files look the same" approach. I'll get to work on this.
tested a local build, looks like we have a winner. %changelog * Wed Mar 19 2008 Rex Dieter <rdieter@fedoraproject.org> - 2.3.9-12 - cyrus-imapd conflicts with uw-imap (#222506)
Okay, thanks :)