Already there.
Thatās exactly what i was getting to that the lts kernel wonāt stay forever where it is. So it would have been nice to try to figure it out.
Edit: @jonathon saves the day!
Sure, I got your point.
I just wanted to assure the OP that 5.4 will be maintained so they donāt have to worry.
Thatās great! Thanks!
Dear jonathan,
Please pardon the elementary question but will you tell me (or point me to a link explaining) how to add your (or any) repository to the system?
Thank you.
Lawrence
This is from the post of @jonathon (see link above):
Add this to your /etc/pacman.conf
:
[kernel-lts]
Server = https://repo.m2x.dev/current/$repo/$arch
Import my key:
sudo pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-key 76C6E477042BFE985CC220BD9C08A255442FAFF0
sudo pacman-key --lsign 76C6E477042BFE985CC220BD9C08A255442FAFF0
then install whichever kernel takes your fancy:
(But before installing any of the kernels, run sudo pacman -Syyu
).
I did all of that but it doesnāt work; I cannot import the keys.
Hereis what my pcaman.conf file looks like. Please tell me what I have done wrong.
**#**
**# /etc/pacman.conf**
**#**
**# See the pacman.conf(5) manpage for option and repository directives**
**#**
**# GENERAL OPTIONS**
**#**
**[options]**
**# The following paths are commented out with their default values listed.**
**# If you wish to use different paths, uncomment and update the paths.**
**#RootDir = /**
**#DBPath = /var/lib/pacman/**
**#CacheDir = /var/cache/pacman/pkg/**
**#LogFile = /var/log/pacman.log**
**#GPGDir = /etc/pacman.d/gnupg/**
**#HookDir = /etc/pacman.d/hooks/**
**HoldPkg = pacman glibc**
**#XferCommand = /usr/bin/curl -C - -f %u > %o**
**#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u**
**#CleanMethod = KeepInstalled**
**#UseDelta = 0.7**
**Architecture = auto**
**#IgnorePkg =**
**#IgnorePkg =**
**#IgnoreGroup =**
**#NoUpgrade =**
**#NoExtract =**
**# Misc options**
**#UseSyslog**
**Color**
**ILoveCandy**
**#TotalDownload**
**# We cannot check disk space from within a chroot environment**
**#CheckSpace**
**#VerbosePkgLists**
**# By default, pacman accepts packages signed by keys that its local keyring**
**# trusts (see pacman-key and its man page), as well as unsigned packages.**
**SigLevel = Required DatabaseOptional**
**LocalFileSigLevel = Optional**
**#RemoteFileSigLevel = Required**
**# NOTE: You must run `pacman-key --init` before first using pacman; the local**
**# keyring can then be populated with the keys of all official Arch Linux**
**# packagers with `pacman-key --populate archlinux`.**
**#**
**# REPOSITORIES**
**# - can be defined here or included from another file**
**# - pacman will search repositories in the order defined here**
**# - local/custom mirrors can be added here or in separate files**
**# - repositories listed first will take precedence when packages**
**# have identical names, regardless of version number**
**# - URLs will have $repo replaced by the name of the current repo**
**# - URLs will have $arch replaced by the name of the architecture**
**#**
**# Repository entries are of the format:**
**# [repo-name]**
**# Server = ServerName**
**# Include = IncludePath**
**#**
**# The header [repo-name] is crucial - it must be present and**
**# uncommented to enable the repo.**
**#**
**# The testing repositories are disabled by default. To enable, uncomment the**
**# repo name header and Include lines. You can add preferred servers immediately**
**# after the header, and they will be used before the default mirrors.**
**#[testing]**
**#Include = /etc/pacman.d/mirrorlist**
**[core]**
**Include = /etc/pacman.d/mirrorlist**
**[extra]**
**Include = /etc/pacman.d/mirrorlist**
**#[community-testing]**
**#Include = /etc/pacman.d/mirrorlist**
**[community]**
**Include = /etc/pacman.d/mirrorlist**
**# If you want to run 32 bit applications on your x86_64 system,**
**# enable the multilib repositories as required here.**
**#[multilib-testing]**
**#Include = /etc/pacman.d/mirrorlist**
**[multilib]**
**Include = /etc/pacman.d/mirrorlist**
**[endeavouros]**
**SigLevel = PackageRequired**
**Include = /etc/pacman.d/endeavouros-mirrorlist**
**# An example of a custom package repository. See the pacman manpage for**
**# tips on creating your own repositories.**
**#[custom]**
**#SigLevel = Optional TrustAll**
**#Server = file:///home/custompkgs**
**Server = https://repo.m2x.dev/current/$repo/$arch**
You will see that I added jonathanās line at the end of the file.
I am not any sort of computer āexpert.ā I CAN follow explicit instructions. I hope that someone will please tell me exactly what to do in this case.
Thank you.
Lawrence
Well, I tried something else. I added the [kernel-lts] prior to adding the ```
Server = https://repo.m2x.dev/current/$repo/$arch
Then I rebooted, and then, in the Terminal, ran sudo -Syyu
Then I tried to add the key but it would not work.
[alienware@alienware ~]$ sudo pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-key 76C6E477042BFE985CC220BD9C08A255442FAFF0
**[sudo] password for alienware: **
gpg: keyserver receive failed: Server indicated a failure
==> ERROR: Remote key not fetched correctly from keyserver.
[alienware@alienware ~]$
Then I again ran pacman -Syyu
Then I ran sudo pacman -S linux-lts419
and here is what I got:
[alienware@alienware ~]$ sudo pacman -Syyu
[sudo] password for alienware: **
:: Synchronizing package databasesā¦
** kernel-lts 16.5 KiB 0.00 B/s 00:00 [--------------------------------] 100%
** core 132.3 KiB 1654 KiB/s 00:00 [--------------------------------] 100%**
** extra 1646.3 KiB 2.20 MiB/s 00:01 [--------------------------------] 100%**
** community 5.3 MiB 2.03 MiB/s 00:03 [--------------------------------] 100%**
** multilib 152.0 KiB 1899 KiB/s 00:00 [--------------------------------] 100%**
** endeavouros 14.9 KiB 149 KiB/s 00:00 [--------------------------------] 100%**
:: Starting full system upgradeā¦
** there is nothing to do**
[alienware@alienware ~]$ sudo pacman -S linux-lts419
resolving dependenciesā¦
looking for conflicting packagesā¦
Packages (1) linux-lts419-4.19.167-1
Total Installed Size: 69.34 MiB
**:: Proceed with installation? [Y/n] **
(1/1) checking keys in keyring [--------------------------------] 100%
downloading required keysā¦
**:: Import PGP key 9C08A255442FAFF0, āJonathon Fernyhough jonathon@m2x.devā? [Y/n] **
error: key ā9C08A255442FAFF0ā could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
[alienware@alienware ~]$ ^C
[alienware@alienware ~]$
Obviously I have done something wrong but I cannot figure out what it is or what to do. The linux-lts 4.19 (plus 4.14, etc.) shows up (I can see then in pamac as well as in yay), but they won't install.
I hope someone can set me straight.
Thank you.
Lawrence
For some reason fetching the key marked for @jonathon does not work.
Maybe @jonathon can see the reason? Maybe a typo in the key?
The command is correct, so try again. If keyserver.ubuntu.com is down for whatever reason then try a different keyserver (though this one does tend to be one of the more reliable HKPS-enabled keyservers).
Without this key the packages will fail to verify, so thereās no point continuing to try installing them until you have imported the key.
Dear jonathan,
I just tried again today (Jan. 14) and I got this message:
**[alienware@alienware ~]$ sudo pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-key 76C6E477042BFE985CC220BD9C08A255442FAFF0**
**[sudo] password for alienware: **
**gpg: keyserver receive failed: Server indicated a failure**
**==> ERROR: Remote key not fetched correctly from keyserver.**
**[alienware@alienware ~]$**
Is there any other way of importing the key? Can you give me the command(s) using another keyserver?
Iām certain that this is as frustrating to you as it is to me.
Thank you.
Lawrence
I could do, but do I have to? Either trying with the default keyserver (by not including "--keyserver hkps://keyserver.ubuntu.com
in the command), or replacing the address with another server (e.g. hkp://pool.sks-keyservers.net
) should be fairly straightforward to try?
I just did this earlier today and the key was imported with no issue.
I did the same as pebcak - ran the command with no issues.
Iāve read a few posts on different forums where people had issues if they were behind firewalls. Some were able to work around by adding a port specification to the keyserver url (ie appending :80 ā¦ or maybe :443 for hkps).
Thanks to all who have responded here but I have spent enough time with this computer and I now say to Hell with it.
Here is what I just got in my latest attempts to install jonathanās keys:
**[alienware@alienware ~]$ sudo pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-key 76C6E477042BFE985CC220BD9C08A255442FAFF0**
**[sudo] password for alienware: **
**gpg: keyserver receive failed: Server indicated a failure**
**==> ERROR: Remote key not fetched correctly from keyserver.**
**[alienware@alienware ~]$ sudo pacman-key --keyserver hkp://pool.sks-keyservers.net --recv-key 76C6E477042BFE985CC220BD9C08A255442FAFF0**
**gpg: keyserver receive failed: Server indicated a failure**
**==> ERROR: Remote key not fetched correctly from keyserver.**
**[alienware@alienware ~]$**
and here is how I had my Firewall configured:
(I have since set it back to its default.)
I guess I am not going to be able to proceed further without spending an inordinate amount of time doing things that I just donāt understand.
Thank you all again but, as far as I am concerned, thatās enough. One of these days Iāll just buy a new computer for the purposes for which I used this Alienware one.
Lawrence
Please try (if you feel like to):
sudo pacman-key --recv-key 76C6E477042BFE985CC220BD9C08A255442FAFF0
This worked for me before.