On 2025-03-06 01:28, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: [oS-en] YaST2 update conflict Message-ID : <831d9f08-a4fa-4837-98ee-1c0f1ae26fbe@telefonica.net> Date & Time: Wed, 5 Mar 2025 12:58:47 +0100
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
[...] MN> > I wonder if they're telling you to install python3.12 on Leap 15.6 MN> > too... (_ _?
CER> Dunno. I have:
CER> Telcontar:~ # rpm -qa | grep yt-dlp CER> python312-yt-dlp-2025.02.19-150600.3.pm.1.noarch CER> yt-dlp-2025.02.19-150600.2.pm.1.noarch CER> python311-yt-dlp-2024.08.01-bp156.2.3.1.noarch CER> Telcontar:~ #
Please uninstall python311-yt-dlp-2024.08.01-bp156.2.3.1.noarch.
Done.
CER> All deps satisfied, and there is available CER> yt-dlp-2025.02.19-150600.3.pm.1.noarch. This update can not be installed, it CER> triggers the conflict.
CER> I have "python312 - Python 3 Interpreter" installed.
CER> I got a reply on the packman mail list:
CER> <https://lists.links2linux.de/pipermail/packman/2025-March/018054.html>
CER> I don't understand if I have to do something.
For a while, the maintainer was building the yt-dlp source and rpm for python310, python311 and python312 at the same time, and providing the results.
But, now the maintainer has changed to a method of building and providing the source and rpm specifically for python312.
Neverthless, the maintainer has not modified the dependency relationships in the spec file, so they are still the same as before, and unnecessary conflict messages are now being issued.
%if 0%{?suse_version} < 1600 Requires: python312-yt-dlp = %version %else Requires: python3-yt-dlp = %version %endif
This is the correct dependency now, and you can ignore the current conflict message.
I tried "zypper up" (and aborted) just to see if it complains; it doesn't. No conflicts. :-) -- Cheers / Saludos, Carlos E. R. (from 15.6 x86_64 at Telcontar)