Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42990

Is PCRE 8.43 bug a production concern?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: 4.2.0
    • Fix Version/s: None
    • Component/s: Build
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Dev Tools 2019-09-09

      Description

      Apologies for creating a new bug.  This is really a follow-up on "Upgrade PCRE to 8.43" at https://jira.mongodb.org/browse/SERVER-40836

      My most recent comment on a different but already closed bug hasn't gotten a response, so I'm not sure if it's just been missed or if like on many bugtrackers that closed bugs never get looked at again.  See https://jira.mongodb.org/browse/SERVER-32773

      Anyways, does this PCRE 8.43 bug merely cause a mongodb test to fail?  Should the failure just be ignored?

      Or, does this mean that PCRE 8.43 shouldn't be used in production with mongodb?

      As the packager of mongodb in the Arch Linux AUR repository, need to know what to do here.  We've always compiled with "--use-system-pcre" and we're running the latest version of PCRE, 8.43.

      As half of the "--use-system-X" flags seem to be currently broken and disabled, and with how frequently they change, I'm starting to wonder if any of them are trustworthy, or if we just need to shrug and sigh, and let mongodb pull in all of its dependencies by source.

      (Currently using system pcre, snappy, yaml, zlib, stemmer, sasl-client, and tcmalloc.  system wiredtiger, asio, icu, boost, and surprisingly mongo-c are broken.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mathew.robinson Mathew Robinson (Inactive)
              Reporter:
              jamespharvey20 James P. Harvey
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: