diff options
| author | Xiao Pan <xyz@flylightning.xyz> | 2025-07-30 23:57:48 +0800 |
|---|---|---|
| committer | Xiao Pan <xyz@flylightning.xyz> | 2025-07-30 23:57:48 +0800 |
| commit | 93a3764fb4d6465a16b5be570b00d5d5df5643d3 (patch) | |
| tree | 21b82d53fd376948ff5e4ce563b19dbc031644c9 /etc/pacman.d/gnupg/gpg.conf | |
| parent | 772ea1f2cbb29b5f6585f064059c45c784a1cd83 (diff) | |
hook no need any more
With the hook now linux-megi upgrade seems no problem.
From
https://matrix.to/#/!lmoJhRvQcNTuGtHgry:kde.org/$FWkLUkcTd5zH-8sssWP9p5jT5C9W2BZPlDKVc4WZjcE?via=kde.org&via=matrix.org&via=tchncs.de
: "It seems there's a new way to trigger mkinitcpio after linux-megi
upgrade in
https://github.com/dreemurrs-embedded/danctnix-packages/blob/16b7cd6350d272edf2f6e9ef83afdc481e5d5d37/pine64/linux-megi/PKGBUILD#L110-L113
committed on Apr 4, 2024 in this commit
https://github.com/dreemurrs-embedded/danctnix-packages/commit/5e8caa55c81b916f9cf437082d82843681213311#diff-08b52e5bad72f7ed6fc775bdfb607ab91afca57c0d056750d08ab6bf9b7bbc90R110.
So I guess my old dirty workaround is not needed any more. I will try
next several times linux-megi upgrades."
Diffstat (limited to 'etc/pacman.d/gnupg/gpg.conf')
0 files changed, 0 insertions, 0 deletions