Package Details: mihomo 1.19.9-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: 9
Popularity: 0.86
First Submitted: 2023-12-02 15:01 (UTC)
Last Updated: 2025-05-25 13:42 (UTC)

Dependencies (3)

Required by (17)

Sources (6)

Latest Comments

1 2 Next › Last »

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/[email protected]: invalid version: unknown revision 4e34341cf18b
dns/doh.go:24:2: github.com/metacubex/[email protected]: invalid version: unknown revision 4e34341cf18b
dns/doh.go:25:2: github.com/metacubex/[email protected]: invalid version: unknown revision 4e34341cf18b
transport/hysteria/congestion/brutal.go:4:2: github.com/metacubex/[email protected]: 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

Xarth commented on 2024-12-09 06:04 (UTC)

The application mihomo requires the following capabilities to ensure all its features work correctly:

CAP_NET_ADMIN CAP_NET_RAW CAP_NET_BIND_SERVICE CAP_SYS_TIME CAP_SYS_PTRACE CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE

handsomexdd1024 commented on 2023-12-14 10:29 (UTC)

@chust Thanks for the reminder. ldflags have been updated.

chust commented on 2023-12-14 06:21 (UTC)

The buildtime and version ldflags in the build function should be updated since the package name renamed.

-X "github.com/metacubex/mihomo/constant.Version=$(VERSION)" \
-X "github.com/metacubex/mihomo/constant.BuildTime=$(BUILDTIME)"

chenx_dust commented on 2023-12-08 17:59 (UTC)

Since mihomo renamed from clash-meta, you should replace the conflict package and provide package to mihomo as well.

JohanChane commented on 2023-12-06 08:32 (UTC)

Thanks, man.

1 2 Next › Last »