1. 17 Jun, 2021 3 commits
  2. 16 Jun, 2021 1 commit
  3. 15 Jun, 2021 2 commits
  4. 14 Jun, 2021 2 commits
  5. 10 Jun, 2021 1 commit
  6. 01 Jun, 2021 1 commit
  7. 27 May, 2021 1 commit
  8. 26 May, 2021 7 commits
  9. 25 May, 2021 1 commit
  10. 24 May, 2021 6 commits
  11. 21 May, 2021 7 commits
  12. 20 May, 2021 2 commits
  13. 18 May, 2021 4 commits
  14. 17 May, 2021 2 commits
    • Antonio Terceiro's avatar
      Merge branch 'lava-scheduler-log-keep' into 'master' · fe5b5b76
      Antonio Terceiro authored
      Reintroduce wrongly removed /etc/logrotate.d/lava-scheduler-log
      
      See merge request lava/lava!1508
      fe5b5b76
    • Antonio Terceiro's avatar
      Reintroduce wrongly removed /etc/logrotate.d/lava-scheduler-log · 115b387f
      Antonio Terceiro authored
      This was a tricky one. What happened:
      
      - The version in stretch had /etc/logrotate.d/lava-scheduler-log
      - The version in buster dropped that configuration file, but didn't
        remove it correctly (i.e. it was removed from the filesystem, but was
        still in the dpkg database.
      - The version in bullseye adds that file again.
      
      In a stretch -> buster -> bullseye upgrade scenario, the user gets
      prompted about changes to the file even if they didn't touch the file
      before upgrading to buster, because it was removed incorrectly in the
      buster version. We could fix this in buster first, but then the upgraded
      would only work if the user is using the very latest stable update
      before upgrading.
      
      Instead, on the buster -> bullseye upgrade, if the file is known by dpkg
      -S (meaning it was installed by the stretch version) and missing from
      the filesystem (i.e. it was removed by the upgrade to buster), we
      reinstate the file with its original contents from stretch, so that the
      bullseye upgrade will detect it hasn't been changed and just override it
      with the new version.
      
      I tested both stretch -> buster -> bullseye and buster -> bullseye
      upgrades and both cases are handled correctly.
      
      Closes Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988362
      115b387f