Package Details: mihomo 1.19.15-1

Git Clone URL: https://aur.archlinux.org/mihomo.git (read-only, click to copy)
Package Base: mihomo
Description: Mihomo Kernel by MetaCubeX, formerly known as Clash.Meta
Upstream URL: https://github.com/MetaCubeX/mihomo
Licenses: GPL3
Conflicts: clash-meta
Provides: clash-meta
Submitter: handsomexdd1024
Maintainer: Kizumi
Last Packager: Kizumi
Votes: 16
Popularity: 0.29
First Submitted: 2023-12-02 15:01 (UTC)
Last Updated: 2025-10-21 13:33 (UTC)

Dependencies (3)

Required by (14)

Sources (6)

Pinned Comments

sukanka commented on 2023-02-15 01:05 (UTC)

If you want use tun mode, add the following pacman hook.

➜  ~ cat /etc/pacman.d/hooks/clash-meta.hook
[Trigger]
Operation = Install
Operation = Upgrade
Type = Path
Target = usr/bin/clash-meta

[Action]
When = PostTransaction
Exec = /usr/bin/setcap 'cap_net_admin,cap_net_bind_service=+ep' /usr/bin/clash-meta

Latest Comments

1 2 3 4 Next › Last »

Xarth commented on 2025-09-21 16:54 (UTC) (edited on 2025-09-21 16:58 (UTC) by Xarth)

Please add the following to build() function to enable native optimizations on x86_64:

GOAMD64=v1
flags=$(grep -o -E 'avx512|avx2|sse4_2' /proc/cpuinfo || true)
if [[ $flags == *avx512* ]]; then
    GOAMD64=v4
elif [[ $flags == *avx2* ]]; then
    GOAMD64=v3
elif [[ $flags == *sse4_2* ]]; then
    GOAMD64=v2
fi
export GOAMD64

texsd commented on 2025-06-04 14:45 (UTC)

mihomo doesn't strongly rely on clash-geoip, it can be configured to download from custom urls. It should be remove from dependencies.

brownpaperbag666 commented on 2025-05-22 22:09 (UTC)

I think there is a problem with metacubex/quic-go required version. I am not a GO developer so I don't understand how metacubex/quic-go required when this package declares its name as quic-go/quic-go.

@yinzsw I had the same issue and solved it when set GOPROXY to emptry string. I don't know why it works.

yinzsw commented on 2025-05-14 01:43 (UTC) (edited on 2025-05-14 01:43 (UTC) by yinzsw)

mihomo build() error occurred go version go1.24.3 linux/amd64

  -> 正在解压缩 mihomo-1.19.8.tar.gz，使用 bsdtar
==> 源代码已就绪。
==> 正在创建软件包：mihomo 1.19.8-1 (2025年05月14日 星期三 09时19分10秒)
==> 正在检查运行时依赖关系...
==> 正在检查编译时依赖关系
==> 警告： 使用现存的 $srcdir/ 树
==> 正在删除现存的 $pkgdir/ 目录...
==> 正在开始 build()...
go: downloading github.com/metacubex/quic-go v0.51.1-0.20250511032541-4e34341cf18b
component/sniffer/quic_sniffer.go:20:2: github.com/metacubex/quic-go@v0.51.1-0.20250511032541-4e34341cf18b: invalid version: unknown revision 4e34341cf18b
dns/doh.go:24:2: github.com/metacubex/quic-go@v0.51.1-0.20250511032541-4e34341cf18b: invalid version: unknown revision 4e34341cf18b
dns/doh.go:25:2: github.com/metacubex/quic-go@v0.51.1-0.20250511032541-4e34341cf18b: invalid version: unknown revision 4e34341cf18b
transport/hysteria/congestion/brutal.go:4:2: github.com/metacubex/quic-go@v0.51.1-0.20250511032541-4e34341cf18b: invalid version: unknown revision 4e34341cf18b
==> 错误： 在 build() 中发生一个错误。
    正在放弃...
 -> 生成时出错: mihomo-exit status 4
 -> 无法安装以下软件包, 需要手动介入处理:
mihomo - exit status 4

negimaho commented on 2025-05-13 13:04 (UTC)

mihomo has been packed for archlinux. the download url is

https://github.com/MetaCubeX/mihomo/releases/download/v1.19.8/mihomo-linux-amd64-v1.19.8.pkg.tar.zst

and it's name is mihomo too. https://github.com/MetaCubeX/mihomo/blob/Alpha/.github/release/.fpm_systemd

so the problem is if I installed the package from github release, then archlinux will assume that is aur/mihomo.

Any idea about how to fix it?

LittFlower commented on 2025-05-11 16:50 (UTC)

When I was installing mihomo 1.19.6 with the 5.10 update, the local build failed and the error log is here. Is there any solution? https://pastebin.com/XYGFnWvi

handsomexdd1024 commented on 2024-06-15 00:24 (UTC)

Dependency clash-geoip can be removed, since clash-meta supports upgrading databases. Let the meta kernel manage databases for itself.

MiketsuSmasher commented on 2024-06-10 16:52 (UTC) (edited on 2024-06-10 16:53 (UTC) by MiketsuSmasher)

当前较新的版本（1.18.5-4，通过 archlinuxcn 源安装）的进程分流功能不生效，查看日志可以看到：

level=debug msg="[Process] find process 157.240.20.18 error: process of uid(1000),inode(96671) not found"

这个AUR包版本老一点，但我找不到更合适的地方来反馈。问题似乎是 clash-meta 默认以专属的用户身份运行，无法获取 UID=1000 的用户的进程信息。

1 2 3 4 Next › Last »