Hello, Sorry for mistake. In the Message; Subject : Re: [oS-en] YaST2 update conflict Message-ID : <87o6yhiqre.wl-nomiya@lake.dti.ne.jp> Date & Time: Tue, 04 Mar 2025 09:27:49 +0900 [MN] == Masaru Nomiya <nomiya@lake.dti.ne.jp> has written: MN> Hello, MN> In the Message; MN> Subject : [oS-en] YaST2 update conflict MN> Message-ID : <77bc44e1-d3df-22e0-e6dd-34e5a729dc7d@telefonica.net> MN> Date & Time: Mon, 3 Mar 2025 20:33:11 +0100 (CET) MN> [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: CER> Hi, CER> I get this conflict: CER> #### YaST2 conflicts list - generated 2025-03-03 20:23:52 #### CER> nothing provides 'python3-yt-dlp = 2025.02.19' needed by the to be installed yt-dlp-2025.02.19-150600.3.pm.1.noarch CER> [ ] break yt-dlp-2025.02.19-150600.3.pm.1.noarch by ignoring some of its dependencies CER> [ ] do not install yt-dlp-2025.02.19-150600.3.pm.1.noarch MN> I checked and found. MN> The conflict message is about yt-dlp-2025.02.19-lp156.7.1.noarch.rpm, MN> but it also applies to yt-dlp-2025.02.19-150600.3.pm.1.noarch. but MN> YaST2 should request that python312-yt-dlp=2025.02.19 be installed, MN> not python3-yt-dlp=2025.02.19, because the python3-yt-dlp package MN> does not exist now. MN> In other words, yt-dlp is built with python3.12, and for that reason, MN> the python3,12-yt-dlp module needs to be installed. python312-yt-dlp=2025.02.19h naturally requires python3.12, so you need to install python3.12. I wonder if they're telling you to install python3.12 on Leap 15.6 too... (_ _? Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --

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. 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. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --

On 2025-03-06 03:45, Carlos E. R. wrote:

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. :-)

I got the conflict again. :-( -- Cheers / Saludos, Carlos E. R. (from 15.6 x86_64 at Telcontar)

On Tue, 11 Mar 2025 17:57:15 +0000 (UTC), Robert Webb via openSUSE Users <users@lists.opensuse.org> wrote:

On Tue, 11 Mar 2025 13:02:25 +0100, "Carlos E. R." <robin.listas@telefonica.net> wrote:

...

On 2025-03-06 03:45, Carlos E. R. wrote:

...

On 2025-03-06 01:28, Masaru Nomiya wrote:

...

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. :-)

I got the conflict again. :-(

What if you remove '*yt-dlp*', and then try installing 'yt-dlp'?

Never mind.  I tried installing yt-dlp on Leap 15.6 and got your original problem:   Problem: 1: nothing provides 'python3-yt-dlp = 2025.02.19' needed by the to be installed yt-dlp-2025.02.19-150600.3.pm.1.noarch    Solution 1: do not install yt-dlp-2025.02.19-150600.3.pm.1.noarch    Solution 2: break yt-dlp-2025.02.19-150600.3.pm.1.noarch by ignoring some of its dependencies As has been laid out by Masaru and in [1], on 15.6 with the Packman repo active: The packages yt-dlp, python311-yt-dlp, and python312-yt-dlp are available.  There is no python3-yt-dlp package. yt-dlp requires:   /usr/bin/python3.12   python3-yt-dlp = 2025.02.19 python311-yt-dlp provides:   python311-yt-dlp = 2024.08.01-bp156.2.3.1 python312-yt-dlp provides:   python312-yt-dlp = 2025.02.19-150600.3.pm.1 It seems reasonable, agreeing with Masaru, to install python312-yt-dlp, and hope that yt-dlp is happy.  Since the dependencies aren't properly connected, I tried installing python312-yt-dlp first (no problem). Then 'zypper in yt-dlp', and for the problem, chose:   Solution 2: break yt-dlp-2025.02.19-150600.3.pm.1.noarch by ignoring some of its dependencies yt-dlp seems functional now. [1]  https://lists.links2linux.de/pipermail/packman/2025-March/018054.html -- Robert Webb

Hello, In the Message; Subject : Re: [oS-en] YaST2 update conflict Message-ID : <75fdb70b-e037-4a67-babd-ec31ceba26bc@telefonica.net> Date & Time: Tue, 11 Mar 2025 13:02:25 +0100 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: CER> On 2025-03-06 03:45, Carlos E. R. wrote: CER> > On 2025-03-06 01:28, Masaru Nomiya wrote: [...] CER> > I tried "zypper up" (and aborted) just to see if it complains; CER> it doesn't. No conflicts. :-) CER> I got the conflict again. :-( Wouldn't this happen in your environment? $ rpm --eval %{suse_version} 150600 If it does, it's a bug in the spec file, and you'll be greatly admired by the maintainers. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --

On 2025-03-05 18:28, Masaru Nomiya wrote:

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.

So what are we supposed to do with this?

On 2025-03-11 00:25, Masaru Nomiya wrote:

[DG] == Darryl Gregorash <raven@accesscomm.ca> has written:

MN> > %if 0%{?suse_version} < 1600 MN> > Requires: python312-yt-dlp = %version MN> > %else MN> > Requires: python3-yt-dlp = %version MN> > %endif

MN> > This is the correct dependency now, and you can ignore the current MN> > conflict message.

DG> So what are we supposed to do with this?

If you are not using Tumbleweed, you don't need to do anything, just leave it to the installer.

I'm runninng 15.6, and actually the problem exists there also.

On Wed, 12 Mar 2025 19:28:01 +0900, Masaru Nomiya <nomiya@lake.dti.ne.jp> wrote:

Hello, Sorry for late reply.

In the Message;    Subject    : Re: [oS-en] YaST2 update conflict    Message-ID : <6f8d7044-02ca-4ce1-9068-e10742d1d29e@accesscomm.ca>    Date & Time: Tue, 11 Mar 2025 16:44:56 -0600 [DG] == Darryl Gregorash <raven@accesscomm.ca> has written:

DG>  On 2025-03-11 00:25, Masaru Nomiya wrote: [...] MN> > If you are not using Tumbleweed, you don't need to do anything, just MN> > leave it to the installer.

DG>  I'm runninng 15.6, and actually the problem exists there also.

After reading your email and Carlos's email, I think I understand why you are confused.

I think the maintainer of the package you are trying to use created it in a way that all openSUSE users can use it.

Naturally, since the environment is different for each user's distro, I thought that the following script could control those differences in environment.

     %if 0%{?suse_version} < 1600           Requires: python312-yt-dlp = %version      %else       Requires: python3-yt-dlp = %version      %endif   However, my hypothesis is that this script is wrong. In other words, I think that the maintainer created the script assuming that, except for Tumbleweed, the value of $ rpm --eval %{suse_version} would be less than 1600, but in reality a large value is returned and the installer works in a way that is different from the maintainer's intention.

If you run $ rpm --eval %{suse_version} in your environment, it should return a value greater than 1600, right?

On a Leap 15.6 Live system:   $ rpm --eval '%{suse_version}'   1500   $ cat /etc/os-release   NAME="openSUSE Leap"   VERSION="15.6"   ID="opensuse-leap"   ID_LIKE="suse opensuse"   VERSION_ID="15.6"   PRETTY_NAME="openSUSE Leap 15.6"   ANSI_COLOR="0;32"   CPE_NAME="cpe:/o:opensuse:leap:15.6"   BUG_REPORT_URL="https://bugs.opensuse.org"   HOME_URL="https://www.opensuse.org/"   DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap"   LOGO="distributor-logo-Leap"

I asked Google, but I couldn't find the value of suse_version after Leap 15.

Incidentally, this is the current Tumbleweed;

     $ rpm --eval %{suse_version}      1699

My Tumbleweed system reports the same.

As you can see from the above, the maintainer believes that if you use the package, python312-yt-dlp = %version will be installed on Leap 15.6, and that Tumbleweed users will install python3XX-yt-dlp on their own choice.

On Leap 15.6, with Packman: The value of %{suse_version} does not look wrong. The conditional logic above for it does not look wrong. But the packaging is incorrect still. yt-dlp requires "python3-yt-dlp = 2025.02.19" python312-yt-dlp provides "python312-yt-dlp = 2025.02.19-150600.3.pm.1"   $ zypper if --provides --requires --recommends --suggests --conflicts --obsoletes --supplements \   > yt-dlp python3\*-yt-dlp   Loading repository data...   Reading installed packages...   Information for package yt-dlp:   -------------------------------   Repository     : packman   Name           : yt-dlp   Version        : 2025.02.19-150600.3.pm.1   Arch           : noarch   Vendor         : http://packman.links2linux.de   Installed Size : 270.9 KiB   Installed      : Yes   Status         : up-to-date   Source package : yt-dlp-2025.02.19-150600.3.pm.1.src   Upstream URL   : https://github.com/yt-dlp/yt-dlp   Summary        : Enhanced fork of youtube-dl, a video site downloader for offline watching   Description    :       yt-dlp is a command-line program to retrieve videos from       YouTube.com and other video sites for later watching.   Provides       : [4]       yt-dlp = 2025.02.19-150600.3.pm.1       yt-dlp-bash-completion = 2025.02.19-150600.3.pm.1       yt-dlp-fish-completion = 2025.02.19-150600.3.pm.1       yt-dlp-zsh-completion = 2025.02.19-150600.3.pm.1   Requires       : [2]       /usr/bin/python3.12       python3-yt-dlp = 2025.02.19   Conflicts      : ---   Obsoletes      : [3]       yt-dlp-bash-completion < 2025.02.19-150600.3.pm.1       yt-dlp-fish-completion < 2025.02.19-150600.3.pm.1       yt-dlp-zsh-completion < 2025.02.19-150600.3.pm.1   Recommends     : ---   Suggests       : ---   Supplements    : ---   Information for package python312-yt-dlp:   -----------------------------------------   Repository     : packman   Name           : python312-yt-dlp   Version        : 2025.02.19-150600.3.pm.1   Arch           : noarch   Vendor         : http://packman.links2linux.de   Installed Size : 30.1 MiB   Installed      : Yes   Status         : up-to-date   Source package : yt-dlp-2025.02.19-150600.3.pm.1.src   Upstream URL   : https://github.com/yt-dlp/yt-dlp   Summary        : yt-dlp Python library   Description    :       The direct Python interface into yt-dlp.   Provides       : python312-yt-dlp = 2025.02.19-150600.3.pm.1   Requires       : [2]       ffmpeg       python(abi) = 3.12   Conflicts      : ---   Obsoletes      : ---   Recommends     : ---   Suggests       : ---   Supplements    : ---   Information for package python311-yt-dlp:   -----------------------------------------   Repository     : Update repository of openSUSE Backports   Name           : python311-yt-dlp   Version        : 2024.08.01-bp156.2.3.1   Arch           : noarch   Vendor         : openSUSE   Installed Size : 22.8 MiB   Installed      : No   Status         : not installed   Source package : yt-dlp-2024.08.01-bp156.2.3.1.src   Upstream URL   : https://github.com/yt-dlp/yt-dlp   Summary        : yt-dlp Python library   Description    :       The direct Python interface into yt-dlp.   Provides       : python311-yt-dlp = 2024.08.01-bp156.2.3.1   Requires       : [2]       ffmpeg       python(abi) = 3.11   Conflicts      : ---   Obsoletes      : ---   Recommends     : ---   Suggests       : [5]       python311-Brotli       python311-certifi       python311-mutagen       python311-pycryptodomex       python311-websockets   Supplements    : --- -- Robert Webb

On 2025-03-12 04:28, Masaru Nomiya wrote:

Hello,

Sorry for late reply.

In the Message;

Subject : Re: [oS-en] YaST2 update conflict Message-ID : <6f8d7044-02ca-4ce1-9068-e10742d1d29e@accesscomm.ca> Date & Time: Tue, 11 Mar 2025 16:44:56 -0600

[DG] == Darryl Gregorash <raven@accesscomm.ca> has written:

DG> On 2025-03-11 00:25, Masaru Nomiya wrote: [...] MN> > If you are not using Tumbleweed, you don't need to do anything, just MN> > leave it to the installer.

DG> I'm runninng 15.6, and actually the problem exists there also.

After reading your email and Carlos's email, I think I understand why you are confused.

I think the maintainer of the package you are trying to use created it in a way that all openSUSE users can use it.

Naturally, since the environment is different for each user's distro, I thought that the following script could control those differences in environment.

%if 0%{?suse_version} < 1600 Requires: python312-yt-dlp = %version %else Requires: python3-yt-dlp = %version %endif

However, my hypothesis is that this script is wrong. In other words, I think that the maintainer created the script assuming that, except for Tumbleweed, the value of $ rpm --eval %{suse_version} would be less than 1600, but in reality a large value is returned and the installer works in a way that is different from the maintainer's intention.

If you run $ rpm --eval %{suse_version} in your environment, it should return a value greater than 1600, right?

In Leap 15.6, hadron:~ # rpm --eval %{suse_version} 1500

I asked Google, but I couldn't find the value of suse_version after Leap 15.

Incidentally, this is the current Tumbleweed;

$ rpm --eval %{suse_version} 1699

As you can see from the above, the maintainer believes that if you use the package, python312-yt-dlp = %version will be installed on Leap 15.6, and that Tumbleweed users will install python3XX-yt-dlp on their own choice.

Here are the requires for the yt-dlp version that is to be installed: /usr/bin/python3.12 python3-yt-dlp = 2025.02.19 and the provides for the proposed python3-yt-dlp: Provides: python312-yt-dlp = 2025.02.19-150600.3.pm.1

On 2025-03-12 23:05, Masaru Nomiya wrote:

Hello,

[...] MN> > As you can see from the above, the maintainer believes that if you use MN> > the package, python312-yt-dlp = %version will be installed on Leap MN> > 15.6, and that Tumbleweed users will install python3XX-yt-dlp on their MN> > own choice.

DG> Here are the requires for the yt-dlp version that is to be installed:

DG> /usr/bin/python3.12 DG> python3-yt-dlp = 2025.02.19

DG> and the provides for the proposed python3-yt-dlp:

DG> Provides: DG> python312-yt-dlp = 2025.02.19-150600.3.pm.1

I'm sorry, but I don't understand what you're trying to say. These are the requires for the available (upgrade) version of yt-dlp and the provides for the available version of python312-yt-dlp. They are trivially available in Yast/Package Management.

I built it by making the following changes to the spec file for yt-dlp-2025.02.19-150600.3.pm.1.src.rpm.

OK, so am I expected to start compiling my own rpm's now, whenever a problem like this arises? That's sure as heck not going to happen.

Here, python3-yt-dlp = 2025.02.19 is a mistake in the spec file, and it should be python312-yt-dlp = 2025.02.19, which is the result of the build.

After writing that, you then ask me this..???

By the way, what are you basing this on?

DG> and the provides for the proposed python3-yt-dlp:

DG> Provides: DG> python312-yt-dlp = 2025.02.19-150600.3.pm.1

Hello, In the Message; Subject : Re: [oS-en] YaST2 update conflict - and a new one. Message-ID : <1f1c9920-4a36-4e40-956e-77a5d1f61dd6@telefonica.net> Date & Time: Fri, 14 Mar 2025 20:04:01 +0100 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: [...] CER> #### YaST2 conflicts list END ### CER> I'll choose break. There is an update for python. CER> Repository | Name | Category | Severity | Interactive | Status | Since | Summary CER> -------------------------------------------------------------+----------------------------+----------+-----------+-------------+--------+-------+------------------------------------- CER> Update repository with updates from SUSE Linux Enterprise 15 | openSUSE-SLE-15.6-2025-856 | security | important | reboot | needed | - | Security update for the Linux Kernel CER> Update repository with updates from SUSE Linux Enterprise 15 | openSUSE-SLE-15.6-2025-857 | security | important | --- | needed | - | Security update for build CER> Update repository with updates from SUSE Linux Enterprise 15 | openSUSE-SLE-15.6-2025-861 | security | low | --- | needed | - | Security update for python CER> Found 3 applicable patches: CER> 3 patches needed (3 security patches) CER> yt-dlp seems to be working after the update. Interesting!!! Could you explain to the members of this ML what logic the three patches used to get yt-dlp working properly? Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: m.nomiya+suse @ gmail.com ┃＼／彡 ┗━━┛ "In the Americas and Europe, excluding South Korea, smartphone addiction among youth is not as serious as alcoholism or drug addiction and is not of high concern." 　　 -- Chosun Online --

On 2025-03-25 21:10, Masaru Nomiya wrote:

Hello,

In the Message;

Subject : Re: [oS-en] YaST2 update conflict Message-ID : <8c957164-753a-4e46-8722-5c1acbe34fa3@telefonica.net> Date & Time: Tue, 25 Mar 2025 14:21:06 +0100

[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:

CER> I see today an update of yt-dlp (2025.03.21-150600.2.pm.1) and CER> python312-yt-dlp (2025.03.21-150600.2.pm.1), and no conflict.

Thanks.

This is because yt-dlp.spec has been restored to the same as before, as shown below;

About time, too.