[PRQ#81631] Orphan Request for cursor-bin
oech3 [1] filed an orphan request for cursor-bin [2]: Package is broken due to bot and maintainer actually does not use this. co-maintainer cannot remove maintaner. [1] https://aur.archlinux.org/account/oech3/ [2] https://aur.archlinux.org/pkgbase/cursor-bin/
On 2026-05-11 19:23, notify@aur.archlinux.org wrote:
oech3 [1] filed an orphan request for cursor-bin [2]: Package is broken due to bot and maintainer actually does not use this. co-maintainer cannot remove maintaner.
What's wrong with this package? The git history looks like a joke:
commit 15f3e1ffee0fdc5bfc433988bc9a2a2db21b2cd4 (HEAD -> master, origin/master, origin/HEAD) Author: g.schulz <mail@guntherschulz.de> Date: Fri May 15 10:51:58 2026 +0000
Update to version 2.4.20 (commit 20b56586b0785b8843487045393c57c6d89b7103)
commit 25ed82b9d2877bc8a97d131ab0059250b9e7467d Author: oech3 <79379754+oech3@users.noreply.github.com> Date: Fri May 15 18:17:54 2026 +0900
bump
commit 8a8b60a40a898249d9ade8cd0bc620262f5facc2 Author: oech3 <79379754+oech3@users.noreply.github.com> Date: Fri May 15 18:17:06 2026 +0900
bump
commit fb859b057428d32f54a38571db90366e83fa2162 Author: g.schulz <mail@guntherschulz.de> Date: Fri May 15 07:16:32 2026 +0000
Update to version 2.4.20 (commit 20b56586b0785b8843487045393c57c6d89b7103)
commit e27f992baca4d5e0aa92fdef520f7f29972cd4d9 Author: g.schulz <mail@guntherschulz.de> Date: Wed May 13 23:28:46 2026 +0000
Update to version 3.4.17 (commit 93e603f703cd553a6bb3644711a3379bbbb3118f)
commit 50e33f92ac606fc7d2adf9c372621c39afc007b3 Author: g.schulz <mail@guntherschulz.de> Date: Wed May 13 19:36:56 2026 +0000
Update to version 3.4.16 (commit f736016b0aa20ba1f99b7eec1dda48579fa4c295)
commit 59618a6d34a86788716d0774717e6f69efee309d Author: g.schulz <mail@guntherschulz.de> Date: Wed May 13 16:52:44 2026 +0000
Update to version 3.3.30 (commit 3dc559280adc5f931ade8e25c7b85393842acf34)
commit 645f9a812a572adf35a3e415942ad620d8a2d86c Author: g.schulz <mail@guntherschulz.de> Date: Wed May 13 13:47:30 2026 +0000
Update to version 3.4.13 (commit e8e175702dcdf6cb24df72c1e94133748d0c5e86)
commit 8b4381d8495998f653cf7db55231958745f1e564 Author: g.schulz <mail@guntherschulz.de> Date: Sat May 9 21:19:49 2026 +0000
Update to version 3.3.30 (commit 3dc559280adc5f931ade8e25c7b85393842acf34)
commit eaae1bc8347514b1ae8dbe7b926eb4f97fab7a3b Author: g.schulz <mail@guntherschulz.de> Date: Fri May 8 06:43:37 2026 +0000
Update to version 3.3.27 (commit 80b138a7a0a948e1a798e9ed7867d76a1ba9a318)
First it gets updated from 3.3.27 to 3.3.30, then to 3.4.13, then downgraded to 3.3.30, then 3.4.16+, then all the way back to 2.4.20, then again to 3.4.20, then back again to 2.4.20. Is this a joke or what? Niccolo' Belli
participants (2)
-
Niccolò Belli
-
notify@aur.archlinux.org