Il 05/09/23 00:56, Xavier Baez ha scritto:
I want to maintain the package. motivewave-latest-bin was supposed to be deleted yesterday.
If that package is removed then motivewave wouldn’t have any conflicting packages.
motivewave-latest-bin package was removed in order to make you sleep well. Apart this, when an Arch Linux staff member (I always used my @archlinux.org email address to communicate with you) there are no hidden traps.
motivewave has motivewave-latest-bin listed as conflicts (which is accurate) Andmotivewave-latest-bin has motivewave listed as conflicts (which is accurate)
this is not accurate at all. motivewave doesn't need to have motivewave-latest-bin conflicts as they are mutually exclusive and the newer/different package has to specify any conflicts, not the opposite.
Xiota claims the motivewave-latest-bin package will be deleted, but only after I remove motivewave-latest-bin as a conflict.
I wonder what’s the interest in me removing motivewave-latest-bin first, and why does he even cares about that.
Xiota demonstrated me he's able, has the skills, cares about the package and he's also helpful in solving your packaging issues. So in the end, I deleted the duplicated package to assure you there's nothing wrong or hidden or to fear (unfortunately you ignored also this point so far). So please, make this as my last message about this package: This is my reviewed PKGBUILD https://paste.muflone.com/view/tEy5-7M (not sure about the dependencies, this has gone too far) Follow my instructions I left you in https://aur.archlinux.org/packages/motivewave#comment-932399 and PLEASE don't require me to intervene with this package anymore. -- Fabio Castelli aka Muflone