Request #87910 has been Rejected by Auerhuhn [1]:
Can’t accept your request as is. Existing users of noctalia-qs need
more transparency about the fact that upstream has archived the repo
and that they now would be getting your fork instead of the original
product.
Please do the following:
First honestly double-check whether noctalia-legacy-v4 *really* has to
be on the AUR even though there’s extra/noctalia. If you find it
absolutely has to, please evaluate whether you can find a way to
shoehorn in extra/quickshell as a substitute for your noctalia-qs
dependency.
If that’s impossible too, then for transparency, please upload a fresh
PKGBUILD for your noctalia-qs community fork under a new name, ideally
one that makes it very clear to users that they’re getting *a fork of
the legacy version* and not the original noctalia-qs.
Then add a `provides=("noctalia-qs=${pkgver}")` and
`conflicts=("noctalia-qs")` entry to the new PKGBUILD. That way, AUR
users who still have the now-defunct noctalia-qs package installed can
make an informed decision by themselves whether they want to switch to
your fork or uninstall it.
See also PRQ#87905 by Lysec (one of the original upstream developers)
for a second opinion [0].
[0]: https://lists.archlinux.org/archives/list/aur-
[email protected]/thread/GTBRJXFHQIAUWV5TY7372E743PHWK6HM/
[1] https://aur.archlinux.org/account/Auerhuhn/
