| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This reverts commit b7ba2dd97822e5b2725e2311afeb54839dcfd71f.
Arch linux arm does not have this config yet.
|
|
|
|
|
|
https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/f02d4d01cc9bcaf566e72dbb769250f8c2752e9e
https://gitlab.archlinux.org/pacman/pacman/-/commit/71764b6d4cdee1f74cfc603050ced59009950169
https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/319671cc720a31cfaa81e25354d58699a1bedf6c
|
|
Commit
https://gitlab.archlinux.org/pacman/pacman/-/commit/71764b6d4cdee1f74cfc603050ced59009950169
and
https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/099295fdcb33c875d0659510dc8e82969463a7c4
migrate rustflags to /etc/makepkg.conf.d/rust.conf.
Note I also change opt-level to 3 because
https://doc.rust-lang.org/cargo/reference/profiles.html shows opt-level
3 is all optimization which I want.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If client use alacritty, after ssh into this remote server, ls doesn't
show color. Can be workarounded by server sshd accept COLORTERM and
client sshd send env. More see my comments in alacritty.toml config.
|
|
|
|
|
|
|
|
workaroud ALARM build key is sha1 and rejected by new gpg
With newer version of gpg, pacman will error `Error: Signature is
marginal trust` for Arch Linux ARM Build System key. It seems because
Arch Linux ARM Build System key is sha1 and rejected by new versions
of gpg. Need to reset all keys by:
```sh
sudo rm -rf /etc/pacman.d/gnupg
sudo pacman-key --init
echo 'allow-weak-key-signatures' | sudo tee -a /etc/pacman.d/gnupg/gpg.conf > /dev/null
sudo pacman-key --populate
```
Note, need to add `allow-weak-key-signatures` in /etc/pacman.d/gnupg/gpg.conf
before `sudo pacman-key --populate`.
More See https://archlinuxarm.org/forum/viewtopic.php?f=9&t=16762
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
config unchanged
In the past, `chmod a-w ~/.config/htop/htoprc` is sufficient to let htop not able to write to htoprc. So configs keeps the same if I press anything in htop. But it seems htop new version 3.3.0 makes it not working. I'm not sure why. I suspect "Write configuration to temporary file first" in changelog is the reason <https://github.com/htop-dev/htop/blob/main/ChangeLog#L19>. Luckily, `chmod a-w ~/.config/htop` still works by making htop config dir not writable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
anymore
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://matrix.to/#/!lmoJhRvQcNTuGtHgry:kde.org/$6FmAgi789_7BO-AJzgU7G0t075ozyjuD_EJw0f8-_bE?via=kde.org&via=matrix.org&via=tchncs.de
|
|
|
|
|
