Open joshmedeski opened 2 months ago
Hey @sclu1034, we added an official goreleaser action for AUR but I see the package is showing your name as the maintainer.
Can you help me transfer the maintainer name to "joshmedeski" and make sure it's connected to GoReleaser? I shipped @alcb1310's PR a few minutes ago and we can't tell if it worked: https://github.com/joshmedeski/sesh/pull/177/files
Feels a bit weird that I was only pinged after the fact, to be honest.
I have no experience with GoReleaser and cannot help you with that. I can disown the package for another account to claim, or I can add co-maintainers. But that's about as much as I can do here. Either way, I'd first like to know whether GoReleaser maintains previous history for an already existing package like this, or whether my past contributions will be erased by a force-push or other destructive action.
Also, glancing at those changes, are you certain the generated PKGBUILD works?
The separate _pkgname
is a common practice in manually written ones, but GoReleaser's docs don't mention using that variable.
I happen to be using it in my PKGBUILD, and I guess that's where you got the install
lines from, but I they probably don't work here.
Apologies @sclu1034 I don't remember communicating with you when submitted this to the AUR registry.
I'd be alright with being named co-maintainer for now, my thought is if we can set up goreleaser properly Arch users would receive updates sooner. But I'm don't fully understand this workflow between the AUR registry and how goreleaser works.
What would you like sesh to do?
Set a the AUR maintainer name to
joshmedeski
https://aur.archlinux.org/packages/sesh-bin