Search results for "wechat" - Aur-requests

Re: [PRQ#68164] Deletion Request for wechat-universal-bwrap

by 7Ji

MarsSeed: Please don't file requests to a package that mainly Chinese are using with only researches done in English-focused Internet searching. > 'universal' is not a relevant pkgname qualifier. It is just a directory name on upstream's distribution server. "Universal" IS the upstream marketing name, search "微信 Universal" and you'll see relevant CHINESE news, one example is ithome's news report[a] posted in March 2024 and you can see the listed name in UOS (a Linux distro owned and maintained by Chinese company ChinaUOS for to-business usage) and KylinOS (another Linux distro owned and maintained by Chinese company GalaxyKylin for to-business usage) are definitely "微信 (Universal)". And it's still the case if you get a copy of these distros. Tencent does not use randomly "Universal" in the download link without a reason: it is their marketing name for this version of client from the beginning and they've switched both their Windows and MacOS versions to the same base and thus it is also "universal" in the real sense. They've been sticking with the strict "Universal" spelling with an upper case U and lower case "niversal" and they just don't market it publicly in their own website as it's already the name used in fact. > Duplicate of AUR/wechat, which uses the same download URL. > The latter package is also configured in a way that lets users choose whether they want to use it with or without bwrap. wechat-universal-bwrap provides bubblewrap sandboxing and its behaviour is much different from the official wechat-universal client. Please read through the wrapper[b] and it's not hard to figure out the reason why that sandboxing is needed: 1. Tencent is greedily collecting user data and an open root or home folder should be avoided if you don't want your data to be scanned over and over again; 2: Tencent is not following FHS and they put the data everywhere and the wrapper centralizes the user data into a single folder definable by user 3: Tencent is using a hard-coded order to implement their "Open in Folder" functionality and it needs to be wrapped around unless you want deepin-file-manager/nautilus to be popped up on your KDE session or vice-versa. 4: Tencent is doing device verification and a shared library workaround[c] is needed if user want to login freshly on a non-UOS non-Kylin non-TencentOpenCloud Linux distro and do not have their account marked on Tencent server as valid Linus users. 5. It provides the functionality to close the app in App-Right-click menu the official app does not provide and it's essential if users do not have a tray e.g. when they're using a WM instead of a DE. It is not a duplicate and it has its own meaning and usage and it's also why it has gotten 112 votes: the package is not even the first recommendation by AUR helpers if you search wechat, a huge amount of Chinese Arch users are actively, explicitly searching and installing wechat-universal-bwrap, users would be frustrated if you just delete wechat-universal-bwrap and expect them happily migrate to AUR/wechat. If anything, it is AUR/wechat that's not sticking to what it should provide: a binary-only package should only provide simply the repackaged binary, not doing anything more. But it is in fact using a different way[d] to start Wechat instead of the official way, and many users hate the way how that's handled. The favored AUR/wechat-bin way [e] (just use a fixed .Application file to start the binary) is what it should be using, and that's why people are contantly re-pushing AUR/wechat-bin even after you've sent a request to delete it. If you really want a cleaner AUR, go find a way to fix AUR/wechat to improve the situation, otherwise you're just worsening the situation. [a]: https://ithome.com/0/755/450.htm [b]: https://github.com/7Ji-PKGBUILDs/wechat-universal-bwrap/blob/master/wechat-… [c]: https://github.com/7Ji-PKGBUILDs/wechat-universal-bwrap/blob/master/libuosd… [d]: https://aur.archlinux.org/cgit/aur.git/tree/wechat.sh?h=wechat&id=3fd2d1ede… [e]: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wechat-bin&id=f865b1…

11 months, 3 weeks

[PRQ#68164] Deletion Request for wechat-universal-bwrap

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for wechat-universal-bwrap [2]: 'universal' is not a relevant pkgname qualifier. It is just a directory name on upstream's distribution server. [a] Duplicate of AUR/wechat, which uses the same download URL. The latter package is also configured in a way that lets users choose whether they want to use it with or without bwrap. [a]: https://dldir1v6.qq.com/weixin/Universal/Linux/WeChatLinux_arm64.deb [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/wechat-universal-bwrap/

11 months, 3 weeks

Re: [PRQ#68193] Deletion Request for wechat

by Marcell Meszaros

On 31 December 2024 07:09:29 GMT+01:00, notify(a)aur.archlinux.org wrote: >davy0710 [1] filed a deletion request for wechat [2]: > >The package submitter is monopolizing the AUR community by taking >advantage of name uniqueness, and has added over 40 unnecessary >dependencies to the official WeChat package, force using bwrap for a >long time! Moreover, it only supports KDE, and ignores bug reports >from other environments, forcibly occupying the WeChat aur and >deleting other contributors' official and clean packages!‌ > >[1] https://aur.archlinux.org/account/davy0710/ >[2] https://aur.archlinux.org/pkgbase/wechat/ Spammer user account @davy0710 no longer exists, but the same person created multiple fake new AUR accounts @Cinnamon, @Hyprland, @i3WM, @Xfce, and submitted the exact same message in separate deletion requests from each account: PRQ#68192, PRQ#68194, PRQ#68195, PRQ#68196.

11 months, 3 weeks

Re: [PRQ#68247] Deletion Request for wechat

by Kimiblock Moe

Hi, 1. I haven't received your reply in the comments section. 2. You have a Matrix DM with me at room !5HXi8KCP0VAkE3Hi98:tether.kimiblock.top and supposedly your mxid @shinka:mozilla.org and I haven't received a single message after Fri 22 Nov 2024 15:08:55 CST. 3. Logs are needed to troubleshoot. 4. aur/wechat still contains several fixes, still designed for WeChat like HiDPI, input method. 5. The wechat package along with dependencies still builds perfectly fine in a clean chroot package. Hope to see your reply soon. -- Sincerely, Kimiblock

11 months, 2 weeks

[PRQ#60974] Deletion Request for wechat-uos-bwrap

by notify＠aur.archlinux.org

7Ji [1] filed a deletion request for wechat-uos-bwrap [2]: The upstream name is Wechat (Universal), and it's released onto both the UOS app store and Kylin OS app store with such name. As its official usage is not limited to UOS it shall not bear uos in its name. As it also uses a mixed tech stack and -[GUI framework] suffix is conventionally used for GUI split package (e.g. transmission-qt is the GUI part of tranmission PKGBUILD) it shall also not bear qt in its name. There're already a lot of packging using wechat-universal as the name base, examples on AUR include -universal-privileged and -universal (without suffix) by lihe07 and -appimage by yifwon; examles outside AUR include -universal-flatpak ( https://github.com/web1n/wechat- universal-flatpak ) by web1n. For a complete history about official WeChat builds and why wechat- universal was chosen, please check the previous reply I made to the related aur-general thread: https://lists.archlinux.org/archives/list/aur- general(a)lists.archlinux.org/message/CFBKZH23X2ZP4VWEXR5HU4FL3ADAIQNL/ . About why deletion instead of merge: as the maintainer of -universal- bwrap and the co-maintainer of -beta-bwrap, I don't want unrelated comments in the history of -universal, neither its votes. While -beta- bwrap was created by leaeasy initially as a fork of -uos-bwrap, the packaging went a different way after I joined to help improving it and it became its own thing, their history is completely different as they had completely different user bases from day 1, and -universal-bwrap, created as a workaround for the AUR limitation that PKGBUILD could not be renamed (PRQ#57762 to merge -beta-bwrap to -universal-bwrap was filed as soon as I pushed the PKGBUILD), would want no history from -uos-bwrap. [1] https://aur.archlinux.org/account/7Ji/ [2] https://aur.archlinux.org/pkgbase/wechat-uos-bwrap/

1 year, 6 months

[aur-requests] [PRQ#10938] Deletion Request for wechat-web-devtools-git

by notify＠aur.archlinux.org

bruceutut [1] filed a deletion request for wechat-web-devtools-git [2]: Package is duplicated. [1] https://aur.archlinux.org/account/bruceutut/ [2] https://aur.archlinux.org/pkgbase/wechat-web-devtools-git/

7 years, 9 months

[aur-requests] [PRQ#12227] Deletion Request for deepin-wechat

by notify＠aur.archlinux.org

Skywol [1] filed a deletion request for deepin-wechat [2]: 恶意合并软件 [1] https://aur.archlinux.org/account/Skywol/ [2] https://aur.archlinux.org/pkgbase/deepin-wechat/

7 years, 4 months

[aur-requests] [PRQ#22176] Deletion Request for deepin.com.wechat

by notify＠aur.archlinux.org

SamLukeYes [1] filed a deletion request for deepin.com.wechat [2]: Duplicate of deepin.com.wechat2 [1] https://aur.archlinux.org/account/SamLukeYes/ [2] https://aur.archlinux.org/pkgbase/deepin.com.wechat/

5 years, 1 month

[aur-requests] [PRQ#22818] Deletion Request for deepin-wine-wechat

by notify＠aur.archlinux.org

taotieren [1] filed a deletion request for deepin-wine-wechat [2]: 失效 [1] https://aur.archlinux.org/account/taotieren/ [2] https://aur.archlinux.org/pkgbase/deepin-wine-wechat/

4 years, 11 months

[aur-requests] [PRQ#22883] Deletion Request for wechat-kylinos

by notify＠aur.archlinux.org

SiHuan [1] filed a deletion request for wechat-kylinos [2]: My test token is included in PKGBUILD by mistake. [1] https://aur.archlinux.org/account/SiHuan/ [2] https://aur.archlinux.org/pkgbase/wechat-kylinos/

4 years, 11 months

Aur-requests search results for query "wechat"