I get this error when installing gpgme: pkg-static: gnupg-2.1.0 conflicts with gnupg1-1.4.18_1 (installs files into the same place). Problematic file: /usr/local/man/man1/gpg-zip.1.gz This is not the only conflicting file ...
Maintainers CC'd
Created attachment 149654 [details] This is a patch for secyruty/gnupg. This changes the port not to install man/man1/gpg-zip.1.gz.
I think this is good to fix security/gnupg not to install man/man1/gpg-zip.1.gz. Because security/gnupg doesn't install bin/gpg-zip, so man/man1/gpg-zip.1.gz is not needed.
Created attachment 149656 [details] This is a patch for secyruty/gnupg1. This changes the port to install man/man7/gnupg.7.gz as man/man7/gnupg1.7.gz. security/gnupg now installs man/man7/gnupg.7.gz. This conflicts with man/man7/gnupg.7.gz installed by security/gnupg1. I think that to change man/man7/gnupg.7.gz as man/man7/gnupg1.7.gz looks reasonable. Atattched patch makes security/gnupg1 to install man/man7/gnupg.7.gz as man/man7/gnupg1.7.gz.
attachment 149654 [details] and attachment 149656 [details] fix the conflict problem.
I'm assigning PR (both maintained by same person) I'd say this is fairly high priority.
(In reply to Ting-Wei Lan from comment #5) > attachment 149654 [details] and attachment 149656 [details] fix the conflict > problem. I see two issues with this. 1) You removed it from pkg-plist, but not from stage directory. This would fail stage-qa checks. 2) Not with your patch, with the original port. e.g. %%PORTDOCS%%man/man1/gpg-zip.1.gz man pages are not supposed to be controlled by PORTDOCS. They are supposed to be install unconditionally (the exception is if dependencies are needed to generate the man pages, but if they are already generated they need to be installed *ALWAYS*)
I'm still catching up, it looks like the maintainer already did at least some of this: http://www.freshports.org/commit.php?category=security&port=gnupg&files=yes&message_id=201411220955.sAM9tDfG064853@svn.freebsd.org
The final roadblock to x11/gnome3? Reading the Changelog-2011 in ${WRKSRC}/doc, on 2006-10-12 its do not install gnupg.7 due to a conflict with gpg1. Then on 2010-06-10 "(noinst_MANS): Move gnupg.7 to man_MANS." The file contents appear to be the same between 2.0 and 2.1, so not. The Changelog-2011 file for gnupg20 has entries after this date, but not this one. Was probably branched.... But, did upstream decide gnupg1 was no longer relevant with gnupg 2.1? Seems possible, found a doc commit dated 2014-09-29 "doc: Remove GnuPG-1 related parts". But, the 2.1 release announcement describes there be 3 actively maintained versions (2.1, 2.0 and 1.4). And, that "You may not install "modern" (2.1) and "stable" (2.0) at the same time. However, it is possible to install "classic" (1.4) along with any of the other versions." So an upstream issue....
Looks like its mail/spamassassin that is pulling in security/gnupg1, and its mail/evolution that is pulling mail/spamassassin in. But, looking at the history for mail/p5-Mail-SpamAssassin, at one time it was being patched to use gpg2 (bug 109434)...appears the switch back was done with bug 177359
(In reply to Lawrence Chen from comment #10) > Looks like its mail/spamassassin that is pulling in security/gnupg1, and its > mail/evolution that is pulling mail/spamassassin in. > Hmmm, this is fun. I have two systems, one that has always been pulling double duty as my mail server...so I had spamassassin installed, so didn't see the harm in setting the spamassassin option in evolution. Currently only 2 out the over 2000 ports installed on my home workstation are 'failed' (no skipped or ignored ports.) The ports being x11/gnome3 (currently due to this issue) and ports-mgmt/portrac (which has never built since it was updated to 0.5, haven't had time to dig into it yet.) This system two separate poudriere package repos, one for itself and other for my two headless servers. The headless servers repo has much fewer packages and those systems have already been largely switched for over a month now. (think lsof is the hold out.) I switched this system to my repo the day before gnome3 appeared (what luck....not sure which yet.) While my other system (workstation at work), I have only recently started running spamassassin (since it does a better job with fewer false positives/false negatives than the new cloud provider that work uses), so while spamassassin and gnupg1 are installed, they didn't block gnome3 from building in poudriere as its dependency mail/evolution doesn't depend on spamassassin.... Guess I won't upgrade to gnome3 before the holidays at work.... There are 3 failed ports and 2 skipped ports in my work poudriere....one is ports-mgmt/portrac, the other two are ports I haven't gotten around to cleaning up (and running through testport) the patches to send up.
(In reply to Lawrence Chen from comment #9) > The final roadblock to x11/gnome3? > > Reading the Changelog-2011 in ${WRKSRC}/doc, on 2006-10-12 its do not > install gnupg.7 due to a conflict with gpg1. Then on 2010-06-10 > "(noinst_MANS): Move gnupg.7 to man_MANS." The file contents appear to be > the same between 2.0 and 2.1, so not. The Changelog-2011 file for gnupg20 > has entries after this date, but not this one. Was probably branched.... > > So an upstream issue.... Guess all the thoughts from my narcoleptic brain didn't make it.... gnupg.7 in 1.4 being mostly a subset of the gnupg.7 for 2.0 or 2.1. So, we should patch gnupg1 to stop installing it. Anyways...upstream's response to the issue was as I suspected it would be. They're patching 1.4 to stop installing gnupg.7. https://bugs.g10code.com/gnupg/issue1770
I have disabled installing gnupg.7 from gnupg1 in the mean time I'll leave this open for the maintainer to decide what is the best solution.
Maintainer feedback?
The conflict seems to be gone and nobody has said anything here in more than 4 years. Time to close this I think.