Update of security/gnupg fails because of conflict with security/dirmngr
=== Registering installation for gnupg-2.1.0_1 as automatic pkg-static: gnupg-2.1.0_1 conflicts with dirmngr-1.1.0_12 (installs files into the same place). Problematic file: /usr/local/bin/dirmngr UPDATING has no info about this. Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Update of security/gnupg fails because of conflict with security/dirmngr
Yuri wrote: === Registering installation for gnupg-2.1.0_1 as automatic pkg-static: gnupg-2.1.0_1 conflicts with dirmngr-1.1.0_12 (installs files into the same place). Problematic file: /usr/local/bin/dirmngr Yes, that sort of thing seems to be happening a lot lately. I found out that it often helps if you temporarily uninstall the offending port, then install the other one and finally reinstall the uninstalled one. Or in your case: 1. delete dirmngr (remember if it takes anything else with it!) 2. install gnupg; 3. reinstall dirmngr again (as well as anything that got deleted with it). Hope that helps. However, considering that this sort of thing occurs commonly these days, I suspect there must be something wrong in the ports infrastructure. What I also find somewhat mindboggling is how ports are built, staged and packaged entirely, only THEN to discover there's a conflict. Couldn't that have been detected way earlier? AvW -- Imbibo, ergo sum. pgptO3GaHd719.pgp Description: PGP signature
Re: Update of security/gnupg fails because of conflict with security/dirmngr
On 11/29/2014 04:56, A.J. 'Fonz' van Werven wrote: Yes, that sort of thing seems to be happening a lot lately. I found out that it often helps if you temporarily uninstall the offending port, then install the other one and finally reinstall the uninstalled one. Or in your case: 1. delete dirmngr (remember if it takes anything else with it!) 2. install gnupg; 3. reinstall dirmngr again (as well as anything that got deleted with it). Hope that helps. However, considering that this sort of thing occurs commonly these days, I suspect there must be something wrong in the ports infrastructure. What I also find somewhat mindboggling is how ports are built, staged and packaged entirely, only THEN to discover there's a conflict. Couldn't that have been detected way earlier? AvW I think, what typically happens is that one package depends on another, and that dependency package is just imported in the dependent one, while keeping the same file names installed. In this case it looks like gnupg requires dirmngr, and parts of it were imported into gnupg, while dirmngr keeps living its own life in the system. This is really an evil practice, but people do this, usually without causing conflicts. Chrome has a whole lot of packages included, and also mplayer has. In this case gnupg port should rename offending files, nothing else would solve the problem. Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Update of security/gnupg fails because of conflict with security/dirmngr
On Sat, 29 Nov 2014 13:56:31 +0100 A.J. 'Fonz' van Werven free...@skysmurf.nl wrote: Yuri wrote: === Registering installation for gnupg-2.1.0_1 as automatic pkg-static: gnupg-2.1.0_1 conflicts with dirmngr-1.1.0_12 (installs files into the same place). Problematic file: /usr/local/bin/dirmngr Yes, that sort of thing seems to be happening a lot lately. I found out that it often helps if you temporarily uninstall the offending port, then install the other one and finally reinstall the uninstalled one. Or in your case: 1. delete dirmngr (remember if it takes anything else with it!) 2. install gnupg; 3. reinstall dirmngr again (as well as anything that got deleted with it). Hope that helps. However, considering that this sort of thing occurs commonly these days, I suspect there must be something wrong in the ports infrastructure. What I also find somewhat mindboggling is how ports are built, staged and packaged entirely, only THEN to discover there's a conflict. Couldn't that have been detected way earlier? AvW -- Imbibo, ergo sum. The issue was reported[1], mentionned[2], without action being taken yet... Is gnupg such an obscure and unused port? [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195489 [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195206 -- Matthieu Volat ma...@alkumuna.eu pgp2JGZEgOsXg.pgp Description: OpenPGP digital signature
Re: Update of security/gnupg fails because of conflict with security/dirmngr
On Sat, 29 Nov 2014 14:39:00 +0100, Matthieu Volat stated: The issue was reported[1], mentionned[2], without action being taken yet... Is gnupg such an obscure and unused port? [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195489 [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195206 The nvidia-driver port had a similar problem. That problem has been corrected. Perhaps applying the same methodology here would be fruitful. -- Jerry ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Update of security/gnupg fails because of conflict with security/dirmngr
Jerry wrote: The nvidia-driver port had a similar problem. That problem has been corrected. Perhaps applying the same methodology here would be fruitful. If doing that would fix it, then at least I think it's good news that the problems are with individual ports and not with the ports infrastructure itself (pkg, portmaster, /usr/ports/Mk/*, etc.). AvW -- Imbibo, ergo sum. pgpYQeZOCT1km.pgp Description: PGP signature
Re: Update of security/gnupg fails because of conflict with security/dirmngr
Here is the workaround: sqlite3 /var/db/pkg/local.sqlite delete from deps where name = 'dirmngr' pkg delete dirmng Then gnupg would update successfully. security/dirmngr moved into gnupg, and should be labeled as deleted. Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
