1. 18 Aug, 2020 3 commits
  2. 08 Aug, 2020 1 commit
  3. 07 Aug, 2020 2 commits
  4. 22 Jun, 2020 1 commit
  5. 04 May, 2020 1 commit
  6. 29 Apr, 2020 4 commits
  7. 24 Apr, 2020 1 commit
  8. 24 Mar, 2020 3 commits
  9. 23 Dec, 2019 1 commit
  10. 20 Dec, 2019 1 commit
  11. 09 Dec, 2019 1 commit
    • Dridi Boukelmoune's avatar
      rpm: Require redhat-rpm-config at run time for el8 · 4851d822
      Dridi Boukelmoune authored
      Starting with el8 annobin is used to annotate ELF binaries and this is
      set up via the %configure RPM macro. As a result annobin becomes a
      requirement of the default cc_command in varnishd but it relies on GCC
      spec files that are provided by redhat-rpm-config.
      
      So, similar to how we explicitly require GCC at run time we now also
      need to bring the annobin setup.
      4851d822
  12. 05 Dec, 2019 1 commit
    • Dridi Boukelmoune's avatar
      rpm: Rely on the configure step to find doc tools · e21f52a1
      Dridi Boukelmoune authored
      There was already a hint in b2ea64fd
      that we lack some packaging stability from the platforms we support
      and this is another occurrence. The configure script of a supported
      Varnish release will find the tools we need.
      
      This enables build support for el8 in addition to el7.
      e21f52a1
  13. 27 Nov, 2019 1 commit
  14. 21 Nov, 2019 3 commits
  15. 20 Nov, 2019 1 commit
  16. 23 Oct, 2019 1 commit
  17. 05 May, 2019 1 commit
    • Dridi Boukelmoune's avatar
      Polish Debian packaging · ef90bd19
      Dridi Boukelmoune authored
      I was finally able to use sbuild on Fedora for all Varnish 6 Debian and
      derivatives. I was able to confirm that the configure script doesn't
      need help to find our documentation tools. Or rather, I was no longer
      running in that error when I rushed the Python 3 transition.
      ef90bd19
  18. 04 May, 2019 2 commits
  19. 28 Mar, 2019 2 commits
  20. 12 Mar, 2019 2 commits
    • Dridi Boukelmoune's avatar
      Bring backward compatibility back with vcl.list · 10913583
      Dridi Boukelmoune authored
      In current trunk or soon-to-be Varnish 6.2 the format of vcl.list
      changed and broke the varnishreload script. Because the temperature
      and state column was split into two columns, field offsets became
      off by one.
      
      The forward slash character previously used inside the single column
      is now part of the field separator when the output of vcl.list is
      handled by awk, working for both Varnish 6.2 and previously supported
      versions.
      
      Refs #121
      10913583
    • Dridi Boukelmoune's avatar
      Complete change from #121 · e0b5794e
      Dridi Boukelmoune authored
      This broke the discard and label logic, since its column handling was also
      off by one.
      
      Refs #121
      e0b5794e
  21. 07 Mar, 2019 1 commit
  22. 15 Feb, 2019 1 commit
  23. 14 Feb, 2019 1 commit
    • Dridi Boukelmoune's avatar
      RPM packaging polish · 2e53ac0a
      Dridi Boukelmoune authored
      Instead of hand-rolling our own systemd integration, we can rely on RPM
      macros maintained for us. This results in the following changes in the
      main package's scriptlets:
      
          --- scripts.old	2019-02-14 10:50:21.039974337 +0100
          +++ scripts.new	2019-02-14 10:49:24.649144061 +0100
          @@ -12,14 +12,24 @@
      
           exit 0
           postinstall scriptlet (using /bin/sh):
          -/bin/systemctl daemon-reload >/dev/null 2>&1 || :
          -chown varnishlog:varnish /var/log/varnish/
           /sbin/ldconfig
          +
          +if [ $1 -eq 1 ] ; then
          +        # Initial installation
          +        systemctl preset varnish varnishncsa >/dev/null 2>&1 || :
          +fi
           preuninstall scriptlet (using /bin/sh):
          -if [ $1 -lt 1 ]; then
          -  # Package removal, not upgrade
          -  /bin/systemctl --no-reload disable varnish.service > /dev/null 2>&1 || :
          -  /bin/systemctl stop varnish.service > /dev/null 2>&1 || :
          -  /bin/systemctl stop varnishncsa.service > /dev/null 2>&1 || :
          +
          +if [ $1 -eq 0 ] ; then
          +        # Package removal, not upgrade
          +        systemctl --no-reload disable varnish varnishncsa > /dev/null 2>&1 || :
          +        systemctl stop varnish varnishncsa > /dev/null 2>&1 || :
           fi
          -postuninstall program: /sbin/ldconfig
          +postuninstall scriptlet (using /bin/sh):
          +/sbin/ldconfig
          +
          +systemctl daemon-reload >/dev/null 2>&1 || :
          +if [ $1 -ge 1 ] ; then
          +        # Package upgrade, not uninstall
          +        systemctl try-restart varnish varnishncsa >/dev/null 2>&1 || :
          +fi
      
      The only major change is that the varnish and varnishncsa services will
      be restarted during a varnish upgrade. This is needed because otherwise
      reloading a VCL that uses vmod_std after the upgrade (and without
      restarting) would fail because the running varnishd wouldn't recognize
      the shared object's expected ABI.
      
      One unrelated change is the handling of /var/log/varnish/ ownership. As
      it was done until now a fresh install would yield a corrupted package:
      
          $ rpm --verify varnish
          .....UG..    /var/log/varnish
      
      Since we already create the users and group before installing the files,
      we can already ask RPM to chown the directory itself.
      2e53ac0a
  24. 04 Feb, 2019 3 commits
  25. 01 Feb, 2019 1 commit