1. 17 May, 2019 2 commits
  2. 13 May, 2019 4 commits
  3. 26 Apr, 2019 1 commit
  4. 25 Apr, 2019 2 commits
  5. 18 Apr, 2019 2 commits
    • Simon McVittie's avatar
      Merge branch 'msys2-chmod' into 'master' · 6ee63e3a
      Simon McVittie authored
      build: Don't assume we can set permissions on a directory
      Closes #216
      See merge request !110
    • Simon McVittie's avatar
      bus: Try to raise soft fd limit to match hard limit · 7eacbfec
      Simon McVittie authored
      Linux systems have traditionally set the soft limit to 1024 and the hard
      limit to 4096. Recent versions of systemd keep the soft fd limit at
      1024 to avoid breaking programs that still use select(), but raise the
      hard limit to 512*1024, while in recent Debian versions a complicated
      interaction between components gives a soft limit of 1024 and a hard
      limit of 1024*1024. If we can, we might as well elevate our soft limit
      to match the hard limit, minimizing the chance that we will run out of
      file descriptor slots.
      Unlike the previous code to raise the hard and soft limits to at least
      65536, we do this even if we don't have privileges: privileges are
      unnecessary to raise the soft limit up to the hard limit.
      If we *do* have privileges, we also continue to raise the hard and soft
      limits to at least 65536 if they weren't already that high, making
      it harder to carry out a denial of service attack on the system bus on
      systems that use the traditional limit (CVE-2014-7824).
      As was previously the case on the system bus, we'll drop the limits back
      to our initial limits before we execute a subprocess for traditional
      (non-systemd) activation, if enabled.
      systemd activation doesn't involve us starting subprocesses at all,
      so in both cases activated services will still inherit the same limits
      they did previously.
      Reviewed-by: Lennart Poettering's avatarLennart Poettering <lennart@poettering.net>
      [smcv: Correct a comment based on Lennart's review, reword commit message]
      Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
  6. 17 Apr, 2019 6 commits
  7. 25 Mar, 2019 3 commits
  8. 15 Mar, 2019 3 commits
  9. 14 Mar, 2019 2 commits
    • Ralf Habacker's avatar
      Merge branch 'cal-fix-cmake-pkgconfig' into 'master' · 82e08479
      Ralf Habacker authored
      cmake: Avoid overwriting PKG_CONFIG_PATH env var
      See merge request !96
      Reviewed-by: @rhabacker
    • Clemens Lang's avatar
      cmake: Avoid overwriting PKG_CONFIG_PATH env var · 3525cc04
      Clemens Lang authored
      The CMake config file installed by DBus will run in the context of other
      projects. Consequently, changing the value of the PKG_CONFIG_DIR,
      PKG_CONFIG_PATH or PKG_CONFIG_LIBDIR environment variables will affect
      any further calls to pkg-config made by such projects, which can cause
      A common case of this happening are pkg-config files installed in
      usr/share/pkgconfig for .pc files that are architecture-independent, as
      for example systemd does.
      Avoid clobbering the environment variables by saving and restoring their
      values. Note that for some of the variables, setting them to an empty
      string is different from not setting them at all.
      Signed-off-by: 's avatarClemens Lang <clemens.lang@bmw-carit.de>
  10. 13 Mar, 2019 15 commits