Uploaded image for project: 'MongoDB Shell'
  1. MongoDB Shell
  2. MONGOSH-1125

We may want to package separately for Suse 12 & Suse 15

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • 1.4.1
    • Affects Version/s: None
    • Component/s: Packaging
    • None
    • 2
    • Not Needed

      See HELP-31453.

      • This isn’t being caught by our docker tests because we explicitly add the Suse 15.1 repository that does contain libcrypto 1.0.0 in them.
      • The libcrypto requirement is not coming from mongosh itself, it’s coming from mongocryptd. If the customer doesn’t need automatic CSFLE, they can ignore this.
      • We currently use the same package for suse 12 and suse 15, using the suse 12 mongocryptd executable, the “proper” solution here would probably involve packaging for both separately (we do this for other distros already — this would not add much complexity)
      • This is somewhat similar to MONGOSH-1082 in nature (the difference being that here the trouble happens during installation), where we decided against making changes until we do the CSFLE shared library replacement (MONGOSH-949)
      • Using the shared library will make this problem go away (if/when SERVER-63703 is fixed), we could potentially even go back to having a single .deb and a single .rpm package (assuming that what’s written in the shared library’s tech design is true)

            Assignee:
            Unassigned Unassigned
            Reporter:
            anna.henningsen@mongodb.com Anna Henningsen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: