hashicorp / boundary

Boundary enables identity-based access management for dynamic infrastructure.
https://boundaryproject.io
Other
3.84k stars 287 forks source link

Debian package conflict between boundary and boundary-enterprise #3322

Open stumyp opened 1 year ago

stumyp commented 1 year ago

Describe the bug

I see you published new .deb package for boundary-enterprise which is great :+1: However, it conflicts with boundary package, as they have the overlapping files in them.

To Reproduce Steps to reproduce the behavior:

  1. Install boundary ( "apt install boundary")
  2. try to install boundary-enterprise ("apt install boundary-enterprise")
  3. See error:
dpkg: error processing archive /var/cache/apt/archives/boundary-enterprise_0.13.0+ent-1_amd64.deb (--unpack):
 trying to overwrite '/etc/boundary.d/boundary.env', which is also in package boundary 0.13.0-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Expected behavior

Usually this situation is handled by either introducing mutual conflict between the packages. e.g.:

Conflict: boundary

in boundary-enterprise package and

Conflict: boundary-enterprise

in boundary package

Or use more advanced techniques with dpkg-divert

psekar commented 1 year ago

Hey @stumyp Thanks for taking time in raising the issue.

Your findings are correct about the conflicting files which might not allow installing one package over the other. We do not foresee a user installing boundary and boundary-enterprise in the same system. Do you have a specific situation that requires this ?

stumyp commented 1 year ago

Hey @psekar, this is mostly for conflict management and best practice. I just happened to try it locally and saw this error. I can foresee this to be a source of support requests to HashiCorp in the future. I understand that current template doesn't support Conflicts field in the linux packaging process and this is not a trivial change. If you think this is expected and you can always instruct users to use one of these packages explicitly, then feel free to close this issue.