Debian Linux 11 PIP 安裝遇到 site-packages is not writeable 解法

Debian Linux Python PIP 在安裝某些套件的時候(pip install package),遇到這個錯誤訊息:

defaulting to user installation because normal site-packages is not writeable normal site-packages is not writeable

於是直接把這個資料夾搬走看看(chmod 777 這些當然都測試過了)

mv ~/.local/lib/python3.9/site-packages ~/.local/lib/python3.9/site-packages2

然後在重新安裝之類的,都遇到一樣無法寫入的問題~

閱讀全文〈Debian Linux 11 PIP 安裝遇到 site-packages is not writeable 解法〉

Linux APT Signing EXPKEYSIG 簽名無效 修正

Debian Linux 遇到 NO_PUBKEY GPG error 的解法可見此篇:Linux APT 遇到 NO_PUBKEY 的 GPG error 解法

若已經新增卻還是遇到簽名無效的錯誤,可以怎麼做呢?

閱讀全文〈Linux APT Signing EXPKEYSIG 簽名無效 修正〉

Linux APT 遇到 NO_PUBKEY 的 GPG error 解法

Debian / Ubuntu Linux 若使用外部套件(Apt sources.list 有額外增加),apt update 常常會遇到下述訊息:

由於無法取得它們的公鑰,以下簽章無法進行驗證: NO_PUBKEY 9334A25F8507EFA5

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9334A25F8507EFA5

W: GPG error: http://repo.percona.com/apt stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9334A25F8507EFA5

要怎麼解決呢?

閱讀全文〈Linux APT 遇到 NO_PUBKEY 的 GPG error 解法〉

Linux Mutt 寄信出現 GPGME: CMS protocol not available 修復

Linux CLI 使用 Mutt 寄信、收信蠻方便的,Debian 升級到 Stretch 後,寄信就會出現下述訊息:

GPGME: CMS protocol not available

註:於 CLI 界面使用 Cron 寄信,命令參數:mutt -s "This is Title" root < $content_file

閱讀全文〈Linux Mutt 寄信出現 GPGME: CMS protocol not available 修復〉

Linux 修正大量 GPG error BADSIG 的問題

Debian / Ubuntu Linux 遇到大量的 GPG error (BADSIG) 要怎麼解決呢?

錯誤訊息如下述:

問題1

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com stable Release: 以下簽名無效: BADSIG A040830F7FAC5991 Google, Inc. Linux Package Signing Key \<[email protected]\>
W: 無法取得 http://dl.google.com/linux/mod-pagespeed/deb/dists/stable/Release,
W: Some index files failed to download. They have been ignored, or old ones used instead.

問題2

W: GPG error: http://dl.google.com stable Release: The following signatures were invalid: BADSIG A040830F7FAC5991 Google, Inc. Linux Package Signing Key \<[email protected]\>
W: GPG error: http://security.ubuntu.com precise-security Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key \<[email protected]\>
W: GPG error: http://extras.ubuntu.com precise Release: The following signatures were invalid: BADSIG 16126D3A3E5C1192 Ubuntu Extras Archive Automatic Signing Key \<[email protected]\>
W: GPG error: http://ppa.launchpad.net precise Release: The following signatures were invalid: BADSIG 531EE72F4C9D234C Launchpad webupd8
W: GPG error: http://in.archive.ubuntu.com precise Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key \<[email protected]\>
W: GPG error: http://in.archive.ubuntu.com precise-updates Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key \<[email protected]\>

閱讀全文〈Linux 修正大量 GPG error BADSIG 的問題〉