On 30 April 2024 10:42:08 GMT+02:00, not...@aur.archlinux.org wrote: >MarsSeed [1] filed a deletion request for graphite-web [2]: > >It is not viable to keep this broken package. > >Upstream hasn't released a new version since 2022 [a], and since then >they stopped developing it and only accepted no-impact third party >PR's to the master branch, mostly cosmetic / typo-fix / documentation >fix / minimal config adjustment etc. [b] > >The problem is that this is not compatible with current >Arch/extra/python-django v4, let alone the upcoming v5 (v5.0.4 is in >PyPI, and Arch/extra/python-django is already flagged). > >I've considered the viability of a git package, but this one is >already a VCS build in disguise, and it doesn't help make this work. > >Similarly, the (wrongly named) python3-django-tagging is not >compatible with current python-django v4 (first released in 2021). >That package has been abandoned by its upstream for 4 years. [c] > >No one seems to be using this package off of AUR: 0 votes, 0.000000 >popularity. > >@eggz is not a competent maintainer, he just dismissed my earlier >packaging feedback as irrelevant "chatter". > >There is no testing in PKGBUILD check() so this package passes as if >it was functional. > >[a]: https://github.com/graphite-project/graphite-web >[b]: https://github.com/graphite-project/graphite-web/commits/master/ >[c]: https://github.com/Fantomas42/django-tagging > >[1] https://aur.archlinux.org/account/MarsSeed/ >[2] https://aur.archlinux.org/pkgbase/graphite-web/ Package submitter's account has been deleted (@eggz).
Safe to delete this broken, unused abandonware.
