Please reject deletion requests: PRQ#46635, PRQ#46640, and PRQ#46940.

They are all opened by the same user, xavierbaez, against motivewave-latest-bin.

PRQ#46635:

Falsely stated motivewave package brakes. Causes conflicts.

The state of another package is not relevant to whether motivewave-latest-bin should be deleted.

Regardless, motivewave was broken for over four months, when 6.7.0 was released on 2023-04-17, until the package was updated on 2023-08-25 (over four months). This can be confirmed by reviewing the commit log.

Build log showing the broken state of the package: motivewave.log.

The relevant error is:

==> Validating source files with sha512sums...
    motivewave-6.6.15.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

PRQ#46640:

Issue here guy created a package with the files because he wants to duplicate packages instead of helping with code 👨🏻‍💻 Not working open source but pushing his package. He created an issue that doesn’t exist. He merged his own code in those repositories. He approved his own issue. What’s the point of creating the exact same package as motivewave but with a different maintainer. It is based on the file we download from motivewave anyway.

These concern internal Chaotic AUR package selection and build policies. None of it is relevant to whether a package should be deleted from AUR proper.

PRQ#46940:

This guy Xiota is a stalked.

This is a false accusation. Rather, evidence of xavierbaez’s behavior in violation of Arch Linux Code and Chaotic AUR code of conduct may be seen in the aurweb comments of motivewave and motivewave-latest-bin, as well as in the Chaotic AUR GitHub repository. The Chaotic AUR owner issued a “final warning” (prior to ban) to user xavierbaez for his conduct.

He is flagging out of date to AUR for no reason.

Whether another package is flagged has no bearing on whether this package should be deleted. Regardless, the purpose of the flag on motivewave was to encourage the maintainer to fix the package after refusing to do so after notification via ordinary comments.

motivewave has a chmod syntax error (PKGBUILD line 17, 61d4efc)
`.SRCINFO was manually edited for unknown purpose in 294195, fe66229.

Even with the exact same lines of code, he has nothing better to do to try to bring motivewave down.

It is perfectly reasonable to ask package maintainers to maintain their packages. Those who do not wish to do so should disown the packages so someone who is willing to maintain them can do so.

motivewave-latest-bin has diverged from motivewave in the following ways:

motivewave-latest-bin checks for upstream releases (-latest-bin) before building the package.
Dependencies have been updated.
chmod syntax error was never introduced.
.SRCINFO is generated by makepkg --printsrcinfo, not manually edited.

I have already asked him to focus on his duties with other packages.

Review of xavierbaez’s previous comments at aforementioned locations show no such request.

He also works for Chaotic AUR, where he removed motivewave…

motivewave was removed from Chaotic AUR for poor maintainership, including refusal to correct defects that were identified by Chaotic AUR maintainers. As an independent package repository, Chaotic AUR activities have no bearing on whether a package should be deleted from AUR proper.