I contacted hodong a few days ago to request inclusion of credits for previous maintainer and contributors. He rejected to add credits because he think it doesn’t make any sense to add credits in PKGBUILD. He also said that he never saw the case of adding credits of previous maintainers and contributors in PKGBUILD. And I found a shocking fact that he tried to run “git push -f” on package repository for nimf-git to delete or overwrite with his new local repository. Important thing is, It was intended not a mistake. If he successfully ran “git push -f”, previous commit logs created by previous maintainers and contributors would be just disappeared, and it would be a huge chaos. I can’t predict what the hell this new maintainer will do with nimf-git in the future. Are there any ways to stop this new maintainer from maintaining this package? Best regards. Youngbin Han.
2018. 6. 22. 오후 12:44, Eli Schwartz via aur-requests <aur-requests@archlinux.org> 작성:
On 06/21/2018 11:31 PM, "한영빈 (Youngbin Han)" via aur-requests wrote:
Hi, I’m Youngbin Han. (sukso96100 on AUR) [0] I’d maintained the package nimf-git [1] until last month. And disowned it for many reasons. Then, hodong [2] grabbed it and started to maintaining it. And He/She removed the credits of previous maintainer(me) and contributors from PKGBUILD of the package with this commit [3]. Whether it was mistake or intended. Basically, It’s no respect for previous contributors. The commit [3] must be rolled back or the new maintainer must add a commit to include credits of previous contributors in PKGBUILD.
[0] https://aur.archlinux.org/account/sukso96100 [1] https://aur.archlinux.org/packages/nimf-git/ [2] https://aur.archlinux.org/account/hodong [3] https://aur.archlinux.org/cgit/aur.git/commit/?h=nimf-git&id=0b3e9e20be7050016ab86c2f279a4481ed91085d Archive of [3] - In case of commit removal or force push : http://web.archive.org/web/20180622020133/https://aur.archlinux.org/cgit/aur.git/commit/?h=nimf-git&id=0b3e9e20be7050016ab86c2f279a4481ed91085d
That's entirely bizarre, but I'm more concerned that somehow, this jokester decided to add, for example, the ldconfig command to package().
Given makepkg will not ever allow you to run as root, it's difficult for this to ever work out successfully... the PKGBUILD currently cannot and will not ever successfully run.
Also seems like they've nuked the github repo and replaced it with gitlab, but did not migrate issues. So much for your links in the package comments.
-- Eli Schwartz Bug Wrangler and Trusted User