Alright. Mattbas disabled the push from master for now. I want to emphasize, that we did that because users came to the gitlab repo and complained that the version in the -git repo is older than the pure glaxnimate aur package. For us it is just a bit alien why the -git packages have version numbers visible in the AUR web UI, but are supposed to build the latest master anyway. That being said I request to be removed as maintainer from this package. It was a mistake that I made it in the first place. I'm not using Arch based distros anymore so I'm really a bad fit. I can stay contributor and provide advice, even though I'm not even involved with the glaxnimate project at all anymore, but please find a maintainer for this package or indeed orphan it. Muflone <muflone@archlinux.org> schrieb am Di., 7. Nov. 2023, 02:27:
Il 07/11/23 00:18, dersyth@gmail.com ha scritto:
Neither me nor glax are using arch linux anymore and we'd need a packager with experience. I can talk to him removing the bot and we can stale this until a packager is found.
We set the pkgver, because the git repo looks outdated else, or how do other -git packages handle this issue?
On 07.11.23 00:07, Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
But @xiota was right about this package. Only CI bot AUR user @mattbas pushes unnecessary version bumps with a bogus version quoted in commit message, and no one is resolving the actual packaging issues present in this.
@Muflone, I think this package should either be orphaned in the hope that someone adopts it before the next automated CI bump, or @mattbas bot user should also be restricted/banned.
@Marcell I already asked mattbas to stop auto-bumping the version [1] If he insists on doing so his account will be temporarily suspended.
Among the two missing dependencies, qt6-declarative was properly added to the PKGBUILD, while the clang dependency is still missing. Would someone help the maintainer in fixing this package?
@Sythelux in my previous comment and in the page linked in the package comments [2] there's explained how the VCS (e.g. -git) packages work. You can leave the fixed version, until a real fix is required and the rebuild (done whenever someone installs/upgrades the package) will automatic upgrade the version before the build accordingly. Flooding the users with continuous updates is boring, the users will update the package whenever they want and they always get the latest version (pkgver will be automatically updated).
In other words: don't touch the package until it's really needed with real updates, it will be automatically managed.
[1] https://aur.archlinux.org/packages/glaxnimate-git#comment-942370
[2] https://wiki.archlinux.org/title/VCS_package_guidelines
-- Fabio Castelli aka Muflone