- Dec 13, 2024
-
- Aug 31, 2024
-
- Apr 13, 2024
-
-
David Runge authored
Signed-off-by:
David Runge <dvzrv@archlinux.org>
-
David Runge authored
Signed-off-by:
David Runge <dvzrv@archlinux.org>
- Mar 11, 2024
-
-
David Runge authored
Remove unneeded django related patch. Consolidate dependencies and use `PDM_BUILD_SCM_VERSION` to not have non-reproducible version for distinfo.
-
- Oct 22, 2023
-
-
David Runge authored
Update patch for django versioned dependency removal. Add all direct dependencies.
-
David Runge authored
Signed-off-by:
David Runge <dvzrv@archlinux.org>
-
David Runge authored
Signed-off-by:
David Runge <dvzrv@archlinux.org>
-
- Jul 01, 2023
-
-
Jelle van der Waa authored
This requires needless bumping every django minor release
-
- Apr 08, 2023
-
- Oct 22, 2022
-
-
David Runge authored
Validate signatures on releases using the upstream project manager's PGP key 541EA0448453394FF77A0ECC9D9B2BA061D0A67C.
-
- Oct 20, 2022
-
-
David Runge authored
Upstream has not done any release in a long time, even after providing them with fixes for django 4.0 and django 4.1 and contacting them about this multiple times. Backporting patches has become extremely cumbersome, as they do not cleanly apply on top of the source tarball (e.g. setuptools seems to change setup.py). So we are permanently switching to git sources and do not bother with backporting commits on top of 0.0.5 for our own sanity. Remove all now included (backported) patches.
-
- Aug 12, 2022
-
-
David Runge authored
Use an up-to-date version of the upstreamed django>=4 support patch. Rebase patch for file-hierarchy compliance against django patch. Add mailman-web-qcluster.service (equivalent to hyperkitty-qcluster.service).
- May 03, 2022
-
-
David Runge authored
Add upstreamed patch for django >= 4.0 support (consolidating with previous django patch). Remove unneeded quotes and curly braces. Switch to PEP517.
-
- Dec 03, 2021
-
- Dec 01, 2021
-