Bug 200008 - mail/spamassassin sa-update depending on gpg executable even when the option GNUPG2 is selected during make config
Summary: mail/spamassassin sa-update depending on gpg executable even when the option ...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Adam Weinberger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-06 19:58 UTC by Trond Endrestøl
Modified: 2015-05-08 16:58 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (adamw)


Attachments
Patch for sa-update whenever the option GNUPG2 is selected during make config (472 bytes, text/plain)
2015-05-06 19:58 UTC, Trond Endrestøl
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Trond Endrestøl 2015-05-06 19:58:21 UTC
Created attachment 156442 [details]
Patch for sa-update whenever the option GNUPG2 is selected during make config

Please patch sa-update to look for the gpg2 executable whenever the option GNUPG2 is selected during make config.
Comment 1 Trond Endrestøl 2015-05-08 06:29:50 UTC
(In reply to Trond.Endrestol from comment #0)

Sorry for the noise, Just disregard this PR.

I had both security/gnupg1 and security/gnupg installed along with mail/spamassassin. The latter has since been reconfigured to depend on security/gnupg, thus making security/gnupg1 obsolete. The removal of security/gnupg1 also removed the /usr/local/bin/gpg symlink making sa-update complain.

Some days later I reinstalled security/gnupg after upgrading the system from stable/9 to stable/10, and now all is well.

Or maybe this PR is somewhat misplaced, as security/gnupg1 and security/gnupg should watch out for each other and in particular watch out for the /usr/local/bin/gpg symlink.

At any rate, I guess the morale is to reinstall security/gnupg after removing security/gnupg1.
Comment 2 Adam Weinberger freebsd_committer freebsd_triage 2015-05-08 16:58:04 UTC
The pkg-install for gnupg* should already be looking out for the gpg symlink, though that depends on the age of your ports tree.

I'm glad the issue is essentially resolved for you. I'm going to close out the PR at this point.