Disregard my previous message. New maintainer repurposed package. aur/crush now packages a different project. @vcalv Consider closing the deletion request. On Wed, Jul 30, 2025 at 1:23 PM xiota <aur@mentalfossa.com> wrote:

Problem is caused by package using different pkgbase (crush) and pkgname (python-crush). Should be deleted on basis that it is not useful. Nothing depends on it. There is no evidence of active users, with pkgstats dropping to zero late 2019. Current maintainer has not pushed any change.

On Wed, Jul 30, 2025 at 12:32 PM <notify@aur.archlinux.org> wrote:

...

vcalv [1] filed a deletion request for crush [2]:

I don't understand what's happening here.

there is a `crush` project in aur git @

ssh://aur@aur.archlinux.org/crush.git

That doesn't show up in any AUR pages.

This is apparently a mistakenly/renamed uploaded package that should have been `python-crush`

But is preventing the upload of the source version of `crush-bin` since any push to `crush` is denied.

I'm requesting a deletion that should not be problematic since effectively the package was never even alive.

If merge is a better alternative, feel free to do that.

It makes no sense that python-crush (which apparently exists) is blocking the creation of the crush package.

Thank you.

[1] https://aur.archlinux.org/account/vcalv/ [2] https://aur.archlinux.org/pkgbase/crush/