Zypper dup: problem with libsox3, sox
I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510): Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Solution 1: install libsox3-14.4.2-6.1.x86_64 from vendor openSUSE replacing libsox3-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete libsox3-14.4.2-1599.7.pm.137.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): s Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64 Solution 1: install sox-14.4.2-6.1.x86_64 from vendor openSUSE replacing sox-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete sox-14.4.2-1599.7.pm.137.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): c (4) Thu May 11 12:52:45 PDT 2023 There was nothing in the New Tumbleweed snapshot announcements nor the known defects reports about libsox3 or sox. What to do? Switch vendors? -- Robert Webb
* Robert Webb <webbdg@verizon.net> [05-11-23 16:43]:
I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510):
Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64
Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Solution 1: install libsox3-14.4.2-6.1.x86_64 from vendor openSUSE replacing libsox3-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete libsox3-14.4.2-1599.7.pm.137.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): s Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64 Solution 1: install sox-14.4.2-6.1.x86_64 from vendor openSUSE replacing sox-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete sox-14.4.2-1599.7.pm.137.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): c (4) Thu May 11 12:52:45 PDT 2023
There was nothing in the New Tumbleweed snapshot announcements nor the known defects reports about libsox3 or sox. What to do? Switch vendors?
I see the same and it is your choice which to do. I prefer packman versions, so I choose to wait for packman to update "solution 2". sometimes it takes a day or three. you loose nothing by waiting. the reason I prefer packman here is due to restrictions on video and audio due to copyrites. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On Thu, 11 May 2023 17:39:07 -0400, Patrick Shanahan <paka@opensuse.org> wrote:
* Robert Webb <webbdg@verizon.net> [05-11-23 16:43]:
I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510):
Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64
Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Solution 1: install libsox3-14.4.2-6.1.x86_64 from vendor openSUSE replacing libsox3-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete libsox3-14.4.2-1599.7.pm.137.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): s [...]
I see the same and it is your choice which to do. I prefer packman versions, so I choose to wait for packman to update "solution 2". sometimes it takes a day or three.
you loose nothing by waiting. the reason I prefer packman here is due to restrictions on video and audio due to copyrites.
Ah, thanks. I'm glad I asked. I was assuming the obvious thing was to let the vendor change. -- Robert Webb
On 12.05.2023 01:02, Robert Webb wrote:
On Thu, 11 May 2023 17:39:07 -0400, Patrick Shanahan <paka@opensuse.org> wrote:
* Robert Webb <webbdg@verizon.net> [05-11-23 16:43]:
I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510):
Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64
Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Solution 1: install libsox3-14.4.2-6.1.x86_64 from vendor openSUSE replacing libsox3-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete libsox3-14.4.2-1599.7.pm.137.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): s [...]
I see the same and it is your choice which to do. I prefer packman versions, so I choose to wait for packman to update "solution 2". sometimes it takes a day or three.
you loose nothing by waiting. the reason I prefer packman here is due to restrictions on video and audio due to copyrites.
Ah, thanks. I'm glad I asked. I was assuming the obvious thing was to let the vendor change.
It is. sox for Tumbleweed does not exist in Packman, nor does it exist in PBS. The package was not changed for several years, and the reason it suddenly springs out is that spec file was cleaned up in Tumbleweed.
On Fri, 12 May 2023 06:51:30 +0300, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On 12.05.2023 01:02, Robert Webb wrote:
On Thu, 11 May 2023 17:39:07 -0400, Patrick Shanahan <paka@opensuse.org> wrote:
* Robert Webb <webbdg@verizon.net> [05-11-23 16:43]:
I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510):
Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64
Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Solution 1: install libsox3-14.4.2-6.1.x86_64 from vendor openSUSE replacing libsox3-14.4.2-1599.7.pm.137.x86_64 from vendor http://packman.links2linux.de Solution 2: keep obsolete libsox3-14.4.2-1599.7.pm.137.x86_64
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): s [...]
I see the same and it is your choice which to do. I prefer packman versions, so I choose to wait for packman to update "solution 2". sometimes it takes a day or three.
you loose nothing by waiting. the reason I prefer packman here is due to restrictions on video and audio due to copyrites.
Ah, thanks. I'm glad I asked. I was assuming the obvious thing was to let the vendor change.
It is. sox for Tumbleweed does not exist in Packman, nor does it exist in PBS. The package was not changed for several years, and the reason it suddenly springs out is that spec file was cleaned up in Tumbleweed.
Wow, OK. But, it shouldn't have been obvious to me because I didn't know that those packages had been dropped from Packman. Now, I have belatedly checked and yes, the installed packages came from packman and packman doesn't contain them anymore: # zypper if libsox3 |grep -i vendor Vendor : http://packman.links2linux.de # zypper if sox |grep -i vendor Vendor : http://packman.links2linux.de # zypper se -s --match-words libsox3 sox S | Name | Type | Version | Arch | Repository ---+---------------+---------+----------------------+--------+---------------------- i+ | libsox3 | package | 14.4.2-1599.7.pm.137 | x86_64 | (System Packages) v | libsox3 | package | 14.4.2-6.1 | x86_64 | Main Repository (OSS) | python39-sox | package | 1.4.1-1.12 | noarch | Main Repository (OSS) | python310-sox | package | 1.4.1-1.12 | noarch | Main Repository (OSS) | python311-sox | package | 1.4.1-1.12 | noarch | Main Repository (OSS) i+ | sox | package | 14.4.2-1599.7.pm.137 | x86_64 | (System Packages) v | sox | package | 14.4.2-6.1 | x86_64 | Main Repository (OSS) | sox-devel | package | 14.4.2-6.1 | x86_64 | Main Repository (OSS) In the future, I can check this available info. Thanks, Andrei. What is "PBS", though? So, running zypper dup again and choosing the vendor change: [...] The following 2 packages are going to be downgraded: libsox3 sox The following 2 packages are going to change vendor: libsox3 http://packman.links2linux.de -> openSUSE sox http://packman.links2linux.de -> openSUSE [...] Is it true that versions of the "same" package from two different vendors are not comparable, and that therefore, "downgraded" here doesn't mean anything? -- Robert Webb
On Fri, May 12, 2023 at 1:57 PM Robert Webb <webbdg@verizon.net> wrote: ...
What is "PBS", though?
Packman Build Service. The reason is, a package may not be published but still exist in the build system. https://pmbs.links2linux.org/ OK, they abbreviate it as PMBS, sorry. ...
Is it true that versions of the "same" package from two different vendors are not comparable, and that therefore, "downgraded" here doesn't mean anything?
Yes.
Am Donnerstag, 11. Mai 2023, 22:39:23 CEST schrieb Robert Webb:
I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510):
Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64
and additionally (for today's snapshot) Problem: the to be installed gcc11-11.3.1+git2076-3.1.x86_64 requires 'libtsan0 >= 11.3.1+git2076-3.1', but this requirement cannot be provided not installable providers: libtsan0-gcc11-11.3.1+git2076-3.1.x86_64[repo-oss] Solution 1: Following actions will be done: keep obsolete gcc11-11.3.1+git2076-2.3.x86_64 keep obsolete cpp11-11.3.1+git2076-2.3.x86_64 keep obsolete libtsan0-11.3.1+git2076-2.3.x86_64 Solution 2: deinstallation of gcc11-11.3.1+git2076-2.3.x86_64 Solution 3: deinstallation of libtsan0-11.3.1+git2076-2.3.x86_64 Solution 4: break gcc11-11.3.1+git2076-3.1.x86_64 by ignoring some of its dependencies (causing a lot of additional dpendencies) Cheers Axel
* Axel Braun <docb@opensuse.org> [05-12-23 13:00]:
Am Donnerstag, 11. Mai 2023, 22:39:23 CEST schrieb Robert Webb:
I tried to 'zypper dup' from openSUSE Tumbleweed 20230508 to current (20230510):
Computing distribution upgrade... 2 Problems: Problem: problem with the installed libsox3-14.4.2-1599.7.pm.137.x86_64 Problem: problem with the installed sox-14.4.2-1599.7.pm.137.x86_64
and additionally (for today's snapshot)
Problem: the to be installed gcc11-11.3.1+git2076-3.1.x86_64 requires 'libtsan0 >= 11.3.1+git2076-3.1', but this requirement cannot be provided not installable providers: libtsan0-gcc11-11.3.1+git2076-3.1.x86_64[repo-oss] Solution 1: Following actions will be done: keep obsolete gcc11-11.3.1+git2076-2.3.x86_64 keep obsolete cpp11-11.3.1+git2076-2.3.x86_64 keep obsolete libtsan0-11.3.1+git2076-2.3.x86_64 Solution 2: deinstallation of gcc11-11.3.1+git2076-2.3.x86_64 Solution 3: deinstallation of libtsan0-11.3.1+git2076-2.3.x86_64 Solution 4: break gcc11-11.3.1+git2076-3.1.x86_64 by ignoring some of its dependencies (causing a lot of additional dpendencies)
I do not get that and currently have: gcc11-11.3.1+git2076-3.1.x86_64 cpp11-11.3.1+git2076-3.1.x86_64 libtsan0-gcc11-11.3.1+git2076-3.1.x86_64 so apparently you have a mirror that is not up-2-date you *can* add more than one mirror to your repo file(s). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On Fri, 12 May 2023 18:58:39 +0200, Axel Braun <docb@opensuse.org> wrote:
[...] and additionally (for today's snapshot)
Problem: the to be installed gcc11-11.3.1+git2076-3.1.x86_64 requires 'libtsan0 >= 11.3.1+git2076-3.1', but this requirement cannot be provided not installable providers: libtsan0-gcc11-11.3.1+git2076-3.1.x86_64[repo-oss] Solution 1: Following actions will be done: keep obsolete gcc11-11.3.1+git2076-2.3.x86_64 keep obsolete cpp11-11.3.1+git2076-2.3.x86_64 keep obsolete libtsan0-11.3.1+git2076-2.3.x86_64 Solution 2: deinstallation of gcc11-11.3.1+git2076-2.3.x86_64 Solution 3: deinstallation of libtsan0-11.3.1+git2076-2.3.x86_64 Solution 4: break gcc11-11.3.1+git2076-3.1.x86_64 by ignoring some of its dependencies (causing a lot of additional dpendencies)
Ha. Thanks for the warning. No 'zypper dup' today for me. For these "this requirement cannot be provided"'s, my SOP is to keep the obsoletes, wait, and cross fingers. Although, in one case I chose to break an app I didn't need at the moment (not a compiler!), and zypper fixed that in a later update. -- Robert Webb
participants (4)
-
Andrei Borzenkov -
Axel Braun -
Patrick Shanahan -
Robert Webb