-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2021-08-17 at 16:17 -0500, -pj wrote: El 2021-08-17 a las 16:17 -0500, -pj escribió:
On 8/9/21 5:16 AM, Carlos E. R. wrote:
On 09/08/2021 09.09, -pj wrote:
On 8/7/21 7:01 PM, Carlos E. R. wrote:
On 08/08/2021 01.41, -pj wrote:
On 8/7/21 3:05 PM, Felix Miata wrote:
-pj composed on 2021-08-07 02:37 (UTC-0500): How can zypper be used to unlock a version string or a package? YaST seems to only allow locking of packages with what are contained in the installed repos, in my case the "tiwai 5.11.xx kernel" repo's packages are able to be locked and unlocked using YaST.
Is there a konsole command to list all locked packages on the machine? Of course: "zypper ll". Compaq-nc6400:/etc/zypp> zypper ll
# | Name | Type | Repository | Comment --+-----------------------------+---------+------------+-------- 1 | kernel-default | package | (any) | 2 | kernel-default-base | package | (any) | 3 | kernel-default-base-rebuild | package | (any) | 4 | kernel-default-devel | package | (any) | 5 | kernel-devel | package | (any) | 6 | kernel-source | package | (any) |
Compaq-nc6400:/etc/zypp>
Do you know why the following repository is: -> https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standar...
Not listed in the repository field above?
Maybe nothing is locked from there :-? Dunno.
Yes, I can see this repository is installed with: System -> Yast -> Software -> Software Repositories -> tiwai_kernel_5.11 (I still have the above 6 listed packages locked obviously).
...
The procedure would be to write an entry then try if it works. Now, how exactly to "try" without destroying the target is the problem.
What is the correct way to locate the exact label/name for the 5.11.xx kernel in konsole? This way I can ensure I am adding the *correct* entry to the suffix of the "multiversion.kernels" entry. Is it the output of "uname -a"? No, the "label" comes from the rpm name.
You mean by executing command (or something of this nature?): > "rpm -qa | egrep 'nel-pae|nel-def'"
cer@Telcontar:~> rpm -qa | grep kernel-def kernel-default-5.3.18-lp152.78.1.x86_64 <==== kernel-default-devel-5.3.18-lp152.75.1.x86_64 kernel-default-5.3.18-lp152.87.1.x86_64 <==== kernel-default-devel-5.3.18-lp152.78.1.x86_64 kernel-default-devel-5.3.18-lp152.87.1.x86_64 cer@Telcontar:~> uname -a Linux Telcontar 5.3.18-lp152.87-default #1 SMP Sun Aug 8 21:53:57 UTC 2021 (44d702a) x86_64 x86_64 x86_64 GNU/Linux cer@Telcontar:~> The arrow indicates the rpm names that I mean. It matches the uname, but it is not the same thing.
Is there a command to list all the installed packages (and their states) similar to "dpkg-l | less" for use with openSUSE that you are aware of?
I don't know what "dpkg-l | less" does...
You can see the service that does it: minas-tirith:~ # systemctl cat purge-kernels.service # /usr/lib/systemd/system/purge-kernels.service [Unit] Description=Purge old kernels After=local-fs.target ConditionPathExists=/boot/do_purge_kernels ConditionPathIsReadWrite=/
[Service] Type=oneshot Nice=19 IOSchedulingClass=idle Environment=ZYPP_LOCK_TIMEOUT=-1 ExecStart=/usr/bin/zypper -n purge-kernels ExecStartPost=/bin/rm -f /boot/do_purge_kernels
[Install] WantedBy=multi-user.target minas-tirith:~ #
Ok, it runs once soon after boot if file "/boot/do_purge_kernels" exists,
I do not think that purge.kernels-service runs after each boot.
The service file evaluates on every boot, and if the file "/boot/do_purge_kernels" exists then it starts the program. If it does not exist, then the command does not run.
Why I am saying this is when I edited /etc/zypp/zypp.conf line 554 to the following: -> multiversion.kernels = 5.13.8-1.1 <- : . Powercycled then in konsole passed the following command as root: -> "zypper -n purge-kernels --dry-run" , I was asked the following: -> "The following package is going to be Removed:" kernel-pae-5.13.6-1.2 with 5.11.xx being locked nothing in reference to 5.11.xx appeared.
There is no "/boot/do_purge_kernels" file living here currently. There is a boot.readme file in /boot though.
Could this be triggered by zypper perhaps? Perhaps I am incorrect completely. :|
zypper creates the flag file "/boot/do_purge_kernels". ...
I have no idea of the limit.
Disabling purge-kernels would not have effect on the menu. Something (zypper?) would see the installed kernels and write the appropriate menu. AFAIK, there is something you can run yourself and write the boot menu solely, but this instant I'm unsure. Could be:
grub2-mkconfig -o /boot/grub2/grub.cfg Now the above command you describe is updating grub, grub2 perhaps? On the laptop here I am using Grub2 with Trusted Boot Support currently.
grub2, of course. Grub1 we can consider that doesn't exist for practical purposes, so when people say "grub" they actually mean version 2. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYSYRSRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVvrsAoIcvVg3Vf1s/1Zkb3LRB h5WxmWP/AJ9UrHueqoFG1Nee2b5HBOWtyeOOzA== =QDU6 -----END PGP SIGNATURE-----