Bug 219137 - security/openvpn: correct or drop conflict with self
Summary: security/openvpn: correct or drop conflict with self
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Matthias Andree
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-08 06:45 UTC by Franco Fichtner
Modified: 2017-05-11 22:52 UTC (History)
0 users

See Also:
mandree: maintainer-feedback+

Attachments
CONFLICTS_INSTALL (497 bytes, patch)
2017-05-08 06:45 UTC, Franco Fichtner 		mandree: maintainer-approval-
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Franco Fichtner 2017-05-08 06:45:16 UTC 
Created attachment 182393 [details]
CONFLICTS_INSTALL

Hi,

Package cannot conflict with itself.  Instead, either conflict with openvpn23 as originally intended or drop the mention.


Cheers,
Franco
Comment 1 Matthias Andree freebsd_committer freebsd_triage 2017-05-11 21:53:33 UTC 
Hi Franco, while there is an issue, it is NOT a conflict with itself as long as the version is 2.4 - re-read the pattern.

Since openvpn23 no longer exists in the head branch, I don't intend to change anything, 2017Q2 will expire in 6...7 weeks and pkg will flag the conflict as someone would try to install openvpn23 and openvpn at the same time.
Comment 2 Franco Fichtner 2017-05-11 22:04:15 UTC 
I am aware that it checks to the version, but it needs to be adapted when 2.5 is out... It has for us caused problems in quarterly builds so I thought I mention it.  I can work around all this stuff, but others might not.  ;)
Comment 3 Matthias Andree freebsd_committer freebsd_triage 2017-05-11 22:52:19 UTC 
I suppose a CONFLICTS* line isn't the only thing that needs to change when this piece of software hits 2.5... ;)