Re: About the intentionally duplicated package wechat-beta-bwrap and wechat-universal and unmaintained orginal package wechat-uos

2025-01-02 Thread Kimiblock Moe
WeChat is indeed different from Weixin. But according to multiple sources[a] they use the same package and switch versions on login depending on your registered phone number. And WeChat on the US Apple App Store has no problem logging in and using a Chinese "Weixin" account. [a]: https://www.z

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread Aaron Liu
Hey, Packages are only considered duplicate if there aren't any actual differences. Packages that have real differences (see official electron app -bin's vs versions that adapt to use Arch's electron) won't be deleted. However, the recent new packages created on the AUR other than Kiwiblock's

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread Aaron Liu
I don't understand what you mean. Kimiblock has been the maintainer of wechat-uos-qt and wechat-bwrap-something since I started using arch a year ago. The merged "wechat" is just one less package, and the vanilla “原汁原味儿” wechat-bin was already restored 4 days ago. I don't understand all the upr

Re: About the intentionally duplicated package wechat-beta-bwrap and wechat-universal and unmaintained orginal package wechat-uos

2025-01-02 Thread S Umple
> Hello, I'm 7Ji, maintainer of wechat-universal-bwrap[a] (wrongly typed as wechat-universal in Kimiblock's original mail), and co-maintainer of wechat-beta-bwrap[b]. leaeasy[c], the maintainer of -beta, is my friend. I think it's necessary for me to clear up some misunderstanding and introduce the

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
(sorry about the formatting. resend) It's good that this is an open discussion so we can get all the facts and misinformation presented for everyone to see and judge. Let's get the main points addressed first. Details are next. This is the subject of this discussion and the main points are abo

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
It's good that this is an open discussion so we can get all the facts and misinformation presented for everyone to see and judge. Let's get the main points addressed first. Details are next. This is the subject of this discussion and the main points are about: ** AUR guideline on `Duplicate` pa

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread Bert Peters
On Thu, 2025-01-02 at 18:05 +0100, Robin Candau wrote: > > As said above, this situation has been going for months and is > particularly difficult to deal with. > We have multiple separate mail threads about the overall situation > and > most comments on the AUR are not written in English which

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread Robin Candau
On 1/2/25 3:57 PM, S Umple wrote: Recently there's been a debacle about the wechat packaging in AUR. "Recently" is an interesting word choice, this "debacle" has been going for months [1]... Essentially there were two competing packages wechat and wechat-bin [1] which are both popular. Pack

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread Actionless Loveless
it's quite sus that such great effort was taken just for the sake of being a maintainer (which is a non-paid volunteer role) of some package. i think some sort of security audit should take place to fully clarify this situation, because such pattern strongly remind some sort of social engineering h

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread Kimiblock Moe
Hello, First, there's no need to shorten our names. It's not something like a prohibited word. aur/wechat was wechat-uos-bwrap and wechat-uos-qt respectively before. They are merged into wechat on that very day because I'm busy doing other stuff before that and rushing will probably result i

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread Merell L. Matlock, Jr.
On Thu, Jan 02, 2025 at 10:11:31AM -0500, S Umple wrote: JFC. All y'all sound like a bunch of petulant teens that got their phones taken away. Simple solution to all of this BS drama: 1. Copy PKGBUILD to your machine. 2. Edit said PKGBUILD to your needs. 3. Build and install it using the Ar

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
Update [4] On Thu, Jan 2, 2025 at 9:57 AM S Umple wrote: > Recently there's been a debacle about the wechat packaging in AUR. > Essentially there were two competing packages wechat and wechat-bin [1] > which are both popular. Package maintainer K(type user in AUR) of wechat > took unbelievable m

AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
Recently there's been a debacle about the wechat packaging in AUR. Essentially there were two competing packages wechat and wechat-bin [1] which are both popular. Package maintainer K(type user in AUR) of wechat took unbelievable measures to try to get rid of wechat-bin from AUR to begin with and w