well chrome 126+ not supporting CentOS7.9 alike os.
According:
Yum update on RHEL 7.9 fails: google-chrome-stable-126.0.6478.55 Requires: libc.so.6(GLIBC_2.25)
Beyond The Data
well chrome 126+ not supporting CentOS7.9 alike os.
According:
Yum update on RHEL 7.9 fails: google-chrome-stable-126.0.6478.55 Requires: libc.so.6(GLIBC_2.25)
After fedora upgraded from 38->39, new kernel not listed in grub list.
According to this post, because the entry in /boot/efi/xxxxxxxxxxxxxxxx directory, the new kernel initrd file was generated in a wrong place.
FIX:
1. remove the folder:
#rm /boot/efi/xxxxxxxxxxxxxxxx
like : rm -rf /boot/efi/a169b9c4383646aebda5f63e812b9c24/
2. re-install kernel:
#dnf reinstall kernel
New kernel versions get stored in /boot/efi and dont show in grub after fedora 39 update
My OEL7 XFCE4 desktop has no weather updates for a long while.
Seems it’s a bug from upstream with API outdated.
BUG: currently no data available
https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/27
while EL7 doesnt have latest support packages, fetch fedora src_rpm instead.
SRPM: xfce4-weather-plugin-0.11.0-1.fc34.src.rpm
https://koji.fedoraproject.org/koji/buildinfo?buildID=1708630
After build successfully:
[suse@EL7 ~/Desktop]$rpm -qi xfce4-weather-plugin-0.11.0-1.el7.x86_64
Name : xfce4-weather-plugin
Version : 0.11.0
Release : 1.el7
Architecture: x86_64
Install Date: Sat Aug 19 21:56:59 2023
Group : Unspecified
Size : 5399645
License : BSD
Signature : (none)
Source RPM : xfce4-weather-plugin-0.11.0-1.el7.src.rpm
Build Date : Sat Aug 19 21:44:54 2023
Build Host : EL7.SUSE
Relocations : (not relocatable)
URL : http://goodies.xfce.org/projects/panel-plugins/xfce4-weather-plugin
Summary : Weather plugin for the Xfce panel
Description :
A weather plugin for the Xfce panel. It shows the current temperature and
weather condition, using weather data provided by xoap.weather.com.
the RPMS for EL7 (or EL7 compatible) is here:
http://pan.baidu.com/s/1o6OB8ro
PATH: EL7->RPMS->X86_64
xfce4-weather-plugin-0.11.0-1.el7.x86_64.rpm
xfce4-weather-plugin-debuginfo-0.11.0-1.el7.x86_64.rpm
REFERENCE:
https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/27
只要VIM还活着,Bram Moolenaar就还活着。
看到这句话特别有触动,VIM改变了我们很多,成为十几年的VIM重度用户,我们一点点的小努力也能让VIM变得更好用。
这个PO文的主要内容,是介绍如何让VIM YouCompleteMe插件在基于华为麒麟990芯片的LINUX系统上跑起来, 让这样的设备成为VIM工作和开发利器 。
ENV:
MACHINE: HUAWEI LAPTOP L410/L420
CPU: KIRIN 990/9006c, aarch64
作为特别受欢迎的VIM插件,YCM已经在Ubuntu20.04 AARCH64架构上验证能安装了,这也是很好的消息,预计可以在其他类Debian/Ubuntu系统上完美运行,当然也期待这个设备 驱动可以充分开放给社区,可以适配Fedora就最好了。
https://github.com/ycm-core/YouCompleteMe#installation-1
存在的主要困难/BUG:
1. 旧版本的VIM没有编译启用PYTHON支持。
以L410使用的操作系统版本为例,VIM版本低且没有启用PYTHON支持,直接没有办法启用YCM。L420使用的新版本已经启用该PYTHON3支持,可以按第2个问题方案解决 。
解决办法:卸载自带VIM, 自行编译最新版本。
2. 最新的YCM插件不支持低版本的VIM。
作为Ubuntu 1804LTS, CENTOS 8.2类似的系统,不再支持Vim 8.1.2269+以下版本。
https://github.com/ycm-core/YouCompleteMe/issues/3764
解决办法:使用旧的YCM, 或升级VIM到最新。
示例,在.vimrc中更新使用旧的YCM commit:
1 |
Plug 'Valloric/YouCompleteMe', { 'commit':'d98f896' } |
3. VIM 8.1版本编译不识别PYTHON 3.10更新。
版本编译时,验证PYTHON 3.10会被识别为3.1, 该问题在更新版本中修复。
https://github.com/vim/vim/issues/8356
解决办法:卸载自带VIM, 自行编译最新版本。
SOLUTION:
pyenv install 3.11
apt remove vim*
git clone https://github.com/vim/vim.git
cd vim
./configure --enable-python3interp=yes
make
make install
python3 ./install.py --clang-completer --system-libclang --verbose
题外, 重新翻了一下几年前的文章,发现很多年前就在和VIM/YOUCOMPLETEME打交道了,很幸运很多年前还能帮到别人,长久以来我的工具也一直没怎么改变,过了很多很多年,更新一下,愿大家的VIM更好。
Install cmake-2.8.12 on EL7
https://www.shisaihua.com/install-cmake-2-8-12-on-el7/
Fedora15 VIM安装Vundle和YouCompleteMe
https://www.shisaihua.com/fedora15-vim-install-vundle-and-youcompleteme/
hit this error on windows 7 pc.
1 2 3 4 |
[2016-10-25 09:40:57] System.MissingMethodException: Method not found: 'Void System.Security.Cryptography.RandomNumberGenerator.GetBytes(Byte[], Int32, Int32)'. at Shadowsocks.Encryption.IVEncryptor.randBytes(Byte[] buf, Int32 length) at Shadowsocks.Encryption.IVEncryptor.Encrypt(Byte[] buf, Int32 length, Byte[] outbuf, Int32& outlength) at Shadowsocks.Controller.TCPHandler.PipeConnectionReceiveCallback(IAsyncResult ar |
according to msdn,
https://msdn.microsoft.com/en-us/library/dn823306%28v=vs.110%29.aspx
this api was introduced in .NET Framework Available since 4.6
Im currently using .NET Framework 4.5.
fix is to upgrade .NET Framework.
https://www.microsoft.com/en-us/download/details.aspx?id=53344