Skip to content
Snippets Groups Projects
  1. Oct 16, 2023
  2. Aug 21, 2023
  3. Aug 20, 2023
  4. Aug 18, 2023
  5. Aug 13, 2023
  6. Jul 23, 2023
  7. Jul 20, 2023
  8. May 26, 2023
  9. May 24, 2023
  10. May 23, 2023
  11. May 22, 2023
  12. May 20, 2023
  13. May 06, 2023
  14. Feb 27, 2023
  15. Jan 13, 2023
  16. Jan 08, 2023
  17. Nov 12, 2022
  18. Nov 03, 2022
  19. Oct 14, 2022
  20. Sep 28, 2022
    • Kristian Klausen's avatar
      Kill the mailman2 server and put the mailman3 server in its place · 893a95f3
      Kristian Klausen authored
      With the final lists migrated to mailman3[1], the mailman2 server can
      finally be killed.
      
      When the mailman3 server was initially setup[2], it was done on a
      separate server because the mailman and mailman3 packages conflicted,
      and the traffic was routed over wireguard (HTTP, LMTP and SMTP).
      
      Instead of installing mailman3 on the original lists.al.org server and
      transferring the data, it was easier just to install the missing pieces
      (basically Postfix and adjusting the Nginx configuration) on the ml3
      server and move the IPs (to keep the IP mail reputation).
      
      So basically the following was done:
      - The IPs for the original lists.al.org was moved to the mailman3.al.org
        server
      - The mailman2 datadir was transferred to mailman3.al.org server, so we
        can keep the pipermail links alive, and import missing mails if needed
      - The original lists.al.org server was decommissioned
      - The mailman3.al.org server was renamed to lists.al.org
      - The missing pieces was added to the mailman3 role (basically Postfix +
        Nginx adjustments)
      - The mailman role was deleted and the mailman3 role renamed to mailman
      
      [1] 75ac7d09 ("mailman: Fourth and final batch of mailman3 migrated lists")
      [2] 9294828f ("Setup mailman3 server")
      
      Fix #59
      Verified
      893a95f3
    • Evangelos Foutras's avatar
      Combine sync{archive,debug,riscv} into mirrorsync · 43eb814b
      Evangelos Foutras authored
      These roles are very similar and can be merged into a single new role.
      
      Note: The archive mirror is changed from a 4-hour sync to minutely for
      conformity with the other two mirrors. In practice this doesn't matter
      as it was already taking over 4 hours to finish and was starting again
      right after its previous run.
      Verified
      43eb814b
  21. Sep 20, 2022
  22. Sep 16, 2022
  23. Sep 01, 2022
  24. Aug 23, 2022
  25. Jul 29, 2022
  26. Jul 23, 2022
    • nl6720's avatar
      Use C.UTF-8 as the default locale · e74066e3
      nl6720 authored
      The glibc 2.35-6 package ships with the C.UTF-8 locale included which
      means there is now a usable UTF-8 locale available by default.
      
      en_US.UTF-8 will still be generated because PostgreSQL clusters are
      created with that locale. Migrating the clusters to C.UTF-8 is
      possible, but that requires dumping and recreating them.
      Unverified
      e74066e3
  27. Jul 10, 2022
  28. Jun 08, 2022
  29. May 14, 2022
  30. May 09, 2022
Loading