Re: Issues playing videos in Firefox with videolan.org repository - missing libavcodec59?
On 2022-07-02 15:10, Kévin Le Gouguec wrote:
Hello folks,
...
$ zypper search -si libavcodec Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository ---+------------------------+---------+-----------+--------+---------------------- i+ | libavcodec58_134 | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec58_134-32bit | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | Main Repository (OSS) i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | openSUSE-20210422-0
As Jason Craig says, you probably want the libavdcodec from packman. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
(Sorry for the duplicate Carlos, Jason; turns out I wasn't subscribed to support@ and my reply was rejected) "Carlos E. R." <robin.listas@telefonica.net> writes:
On 2022-07-02 15:10, Kévin Le Gouguec wrote:
Hello folks,
...
$ zypper search -si libavcodec Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository ---+------------------------+---------+-----------+--------+---------------------- i+ | libavcodec58_134 | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec58_134-32bit | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | Main Repository (OSS) i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | openSUSE-20210422-0
As Jason Craig says, you probably want the libavdcodec from packman.
Thank you both for your insights, and for redirecting the conversation to the correct list. I guess I'll try switching over to the Packman repository. Out of curiosity, do we know why libavcodec59 is absent from the videolan.org repo? https://en.opensuse.org/VLC says that…
Full power VLC and libav/ffmpeg are available in Packman and VLC repository
… but does not elaborate on the differences between those two repositories. Reading this (and the identical installation procedures that follow), I figured that both repos should provide the same capabilities; IIUC this is not the case?
On 2022-07-03 14:42, Kévin Le Gouguec wrote:
(Sorry for the duplicate Carlos, Jason; turns out I wasn't subscribed to support@ and my reply was rejected)
No worries :-)
"Carlos E. R." <> writes:
On 2022-07-02 15:10, Kévin Le Gouguec wrote:
Hello folks,
...
$ zypper search -si libavcodec Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository ---+------------------------+---------+-----------+--------+---------------------- i+ | libavcodec58_134 | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec58_134-32bit | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | Main Repository (OSS) i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | openSUSE-20210422-0
As Jason Craig says, you probably want the libavdcodec from packman.
Thank you both for your insights, and for redirecting the conversation to the correct list. I guess I'll try switching over to the Packman repository.
Reminds me, it was reccomended long ago to not have both videolan and packman repos active.
Out of curiosity, do we know why libavcodec59 is absent from the videolan.org repo? https://en.opensuse.org/VLC says that…
Good question.
Full power VLC and libav/ffmpeg are available in Packman and VLC repository
… but does not elaborate on the differences between those two repositories. Reading this (and the identical installation procedures that follow), I figured that both repos should provide the same capabilities; IIUC this is not the case?
I don't know. It is a question for the videolan people, I think. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a):
On 2022-07-02 15:10, Kévin Le Gouguec wrote:
$ zypper search -si libavcodec Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+-----------+--------+----- ----------------- i+ | libavcodec58_134 | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec58_134-32bit | package | 4.4.2-4.1 | x86_64 | VLC i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | Main Repository (OSS) i | libavcodec59 | package | 5.0.1-1.7 | x86_64 | openSUSE-20210422-0
As Jason Craig says, you probably want the libavdcodec from packman.
I recently came across same issue on up-to-date TW. I have $ zypper se -si libavcodec S | Name | Type | Version | Arch | Repository ---+------------------+---------+-------------+--------+----------- i+ | libavcodec56 | package | 2.8.18-1.35 | x86_64 | Packman i+ | libavcodec57 | package | 3.4.9-1.41 | x86_64 | Packman i+ | libavcodec58_134 | package | 4.4.2-4.11 | x86_64 | Packman i | libavcodec59 | package | 5.1-1.1 | x86_64 | tw-oss Installation of libavcodec59 from Packman fails: $ sudo zypper in --repo Packman libavcodec59 Loading repository data... Reading installed packages... 'libavcodec59' is already installed. There is an update candidate for 'libavcodec59' from vendor 'http:// packman.links2linux.de', while the current vendor is 'openSUSE'. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. There is an update candidate for 'libavcodec59', but it comes from a repository with a lower priority. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. Resolving package dependencies... Nothing to do. $ sudo zypper in --repo Packman libavcodec59-5.1-2.7.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'libjxl.so.0.7()(64bit)' needed by the to be installed libavcodec59-5.1-2.7.x86_64 Solution 1: do not install libavcodec59-5.1-2.7.x86_64 Solution 2: break libavcodec59-5.1-2.7.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c OK, so I manually installed libjxl0_7 and then installation of libavcodec59 from Packman worked. Now, I must just lock the package(s) from that repo so 'zypper dup' doesn't overwrite them every time. And now, as I have... $ LC_ALL=C zypper lr -p # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+---------------------+--------------------+---------+-----------+--------- +--------- 10 | packman | Packman | Yes | (r ) Yes | Yes | 120 14 | tw-non-oss | tw-non-oss | Yes | (r ) Yes | Yes | 99 15 | tw-oss | tw-oss | Yes | (r ) Yes | Yes | 99 16 | tw-update | tw-update | Yes | (r ) Yes | Yes | 99 ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo? -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
On 24.08.2022 14:41, Vojtěch Zeisek wrote: ...
Installation of libavcodec59 from Packman fails:
$ sudo zypper in --repo Packman libavcodec59 Loading repository data... Reading installed packages... 'libavcodec59' is already installed. There is an update candidate for 'libavcodec59' from vendor 'http:// packman.links2linux.de', while the current vendor is 'openSUSE'. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. There is an update candidate for 'libavcodec59', but it comes from a repository with a lower priority. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. Resolving package dependencies... Nothing to do. $ sudo zypper in --repo Packman libavcodec59-5.1-2.7.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'libjxl.so.0.7()(64bit)' needed by the to be installed libavcodec59-5.1-2.7.x86_64
Well, you artificially restricted the list of available repositories for this invocation to just Packman so zypper could not find/use package from standard Tumbleweed. I do not know why you used "--repo Packman" in the first place.
Solution 1: do not install libavcodec59-5.1-2.7.x86_64 Solution 2: break libavcodec59-5.1-2.7.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c
OK, so I manually installed libjxl0_7 and then installation of libavcodec59 from Packman worked. Now, I must just lock the package(s) from that repo so 'zypper dup' doesn't overwrite them every time. And now, as I have...
$ LC_ALL=C zypper lr -p # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+---------------------+--------------------+---------+-----------+--------- +--------- 10 | packman | Packman | Yes | (r ) Yes | Yes | 120 14 | tw-non-oss | tw-non-oss | Yes | (r ) Yes | Yes | 99 15 | tw-oss | tw-oss | Yes | (r ) Yes | Yes | 99 16 | tw-update | tw-update | Yes | (r ) Yes | Yes | 99
...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
zypper does not switch vendors by default so either packages will be updated from Packman or you may get some package dependencies problem (like above) that you need then resolve manually. Unless you changed default configuration and allowed vendor change.
Dne středa 24. srpna 2022 13:51:07 CEST, Andrei Borzenkov napsal(a):
On 24.08.2022 14:41, Vojtěch Zeisek wrote:
Installation of libavcodec59 from Packman fails: $ sudo zypper in --repo Packman libavcodec59 Loading repository data... Reading installed packages... 'libavcodec59' is already installed. There is an update candidate for 'libavcodec59' from vendor 'http://packman.links2linux.de', while the current vendor is 'openSUSE'. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. There is an update candidate for 'libavcodec59', but it comes from a repository with a lower priority. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. Resolving package dependencies... Nothing to do. $ sudo zypper in --repo Packman libavcodec59-5.1-2.7.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'libjxl.so.0.7()(64bit)' needed by the to be installed libavcodec59-5.1-2.7.x86_64
Well, you artificially restricted the list of available repositories for this invocation to just Packman so zypper could not find/use package from standard Tumbleweed. I do not know why you used "--repo Packman" in the first place.
I use "--repo Packman" because otherwise zypper would install it from OSS as that repo has higher priority.
Solution 1: do not install libavcodec59-5.1-2.7.x86_64 Solution 2: break libavcodec59-5.1-2.7.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c OK, so I manually installed libjxl0_7 and then installation of libavcodec59 from Packman worked. Now, I must just lock the package(s) from that repo so 'zypper dup' doesn't overwrite them every time. And now, as I have... $ LC_ALL=C zypper lr -p # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+---------------------+--------------------+---------+-----------+ ---------+--------- 10 | packman | Packman | Yes | (r ) Yes | Yes | 120 14 | tw-non-oss | tw-non-oss | Yes | (r ) Yes | Yes | 99 15 | tw-oss | tw-oss | Yes | (r ) Yes | Yes | 99 16 | tw-update | tw-update | Yes | (r ) Yes | Yes | 99 ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
zypper does not switch vendors by default so either packages will be updated from Packman or you may get some package dependencies problem (like above) that you need then resolve manually. Unless you changed default configuration and allowed vendor change.
zypp.conf has the default "solver.allowVendorChange = false", so this should be fine...? The only issue might be that libjxl0_7 is available only in OSS and not Packman, but this shouldn't be problem, should it...? -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
On 24.08.2022 15:20, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 13:51:07 CEST, Andrei Borzenkov napsal(a):
On 24.08.2022 14:41, Vojtěch Zeisek wrote:
Installation of libavcodec59 from Packman fails: $ sudo zypper in --repo Packman libavcodec59 Loading repository data... Reading installed packages... 'libavcodec59' is already installed. There is an update candidate for 'libavcodec59' from vendor 'http://packman.links2linux.de', while the current vendor is 'openSUSE'. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. There is an update candidate for 'libavcodec59', but it comes from a repository with a lower priority. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. Resolving package dependencies... Nothing to do. $ sudo zypper in --repo Packman libavcodec59-5.1-2.7.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'libjxl.so.0.7()(64bit)' needed by the to be installed libavcodec59-5.1-2.7.x86_64
Well, you artificially restricted the list of available repositories for this invocation to just Packman so zypper could not find/use package from standard Tumbleweed. I do not know why you used "--repo Packman" in the first place.
I use "--repo Packman" because otherwise zypper would install it from OSS as that repo has higher priority.
No. It would have happened only if two version strings were exactly identical. In your case they are different and zypper even helpfully told you what you needed to do. You just needed to request exact version in which case there would be only one match and repo priorities would not matter. ...
...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
zypper does not switch vendors by default so either packages will be updated from Packman or you may get some package dependencies problem (like above) that you need then resolve manually. Unless you changed default configuration and allowed vendor change.
zypp.conf has the default "solver.allowVendorChange = false", so this should be fine...? The only issue might be that libjxl0_7 is available only in OSS and not Packman, but this shouldn't be problem, should it...?
Nothing is wrong with building package in one repository against package in another repository, especially if this "another" repository is the default system repository which is expected to be always available. Which is why you should never arbitrarily restrict repositories to use unless you know exactly what you are doing. I have no idea whether replacement for libjxl0_7 exists in Packman.
Dne středa 24. srpna 2022 14:32:15 CEST, Andrei Borzenkov napsal(a):
On 24.08.2022 15:20, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 13:51:07 CEST, Andrei Borzenkov napsal(a):
On 24.08.2022 14:41, Vojtěch Zeisek wrote:
Installation of libavcodec59 from Packman fails: $ sudo zypper in --repo Packman libavcodec59 Loading repository data... Reading installed packages... 'libavcodec59' is already installed. There is an update candidate for 'libavcodec59' from vendor 'http://packman.links2linux.de', while the current vendor is 'openSUSE'. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. There is an update candidate for 'libavcodec59', but it comes from a repository with a lower priority. Use 'zypper install libavcodec59-5.1-2.7.x86_64' to install this candidate. Resolving package dependencies... Nothing to do. $ sudo zypper in --repo Packman libavcodec59-5.1-2.7.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'libjxl.so.0.7()(64bit)' needed by the to be installed libavcodec59-5.1-2.7.x86_64
Well, you artificially restricted the list of available repositories for this invocation to just Packman so zypper could not find/use package from standard Tumbleweed. I do not know why you used "--repo Packman" in the first place.
I use "--repo Packman" because otherwise zypper would install it from OSS as that repo has higher priority.
No. It would have happened only if two version strings were exactly identical. In your case they are different and zypper even helpfully told you what you needed to do. You just needed to request exact version in which case there would be only one match and repo priorities would not matter.
OK, makes sense.
...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
zypper does not switch vendors by default so either packages will be updated from Packman or you may get some package dependencies problem (like above) that you need then resolve manually. Unless you changed default configuration and allowed vendor change.
zypp.conf has the default "solver.allowVendorChange = false", so this should be fine...? The only issue might be that libjxl0_7 is available only in OSS and not Packman, but this shouldn't be problem, should it...?
Nothing is wrong with building package in one repository against package in another repository, especially if this "another" repository is the default system repository which is expected to be always available.
I'd thought so.
Which is why you should never arbitrarily restrict repositories to use unless you know exactly what you are doing.
I thought I'm. :-)
I have no idea whether replacement for libjxl0_7 exists in Packman.
It's only in OSS. Anyway, locking libavcodec59 solves it, although it kind of lacks elegance... ;-) -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a):
On 2022-07-02 15:10, Kévin Le Gouguec wrote:
...
OK, so I manually installed libjxl0_7 and then installation of libavcodec59 from Packman worked. Now, I must just lock the package(s) from that repo so 'zypper dup' doesn't overwrite them every time. And now, as I have...
$ LC_ALL=C zypper lr -p # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+---------------------+--------------------+---------+-----------+--------- +--------- 10 | packman | Packman | Yes | (r ) Yes | Yes | 120 14 | tw-non-oss | tw-non-oss | Yes | (r ) Yes | Yes | 99 15 | tw-oss | tw-oss | Yes | (r ) Yes | Yes | 99 16 | tw-update | tw-update | Yes | (r ) Yes | Yes | 99
...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80. - -- Cheers, Carlos E. R. (from openSUSE 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYwYTYBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVMoYAn3mUNwZ++ai/ZY2KPuQV xLWNZYeYAKCJwXrLrIZhbXvkG0M5nBEpnPod9g== =bacj -----END PGP SIGNATURE-----
Dne středa 24. srpna 2022 14:02:39 CEST, Carlos E. R. napsal(a):
On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
On 2022-07-02 15:10, Kévin Le Gouguec wrote: OK, so I manually installed libjxl0_7 and then installation of
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a): libavcodec59 from Packman worked. Now, I must just lock the package(s) from that repo so 'zypper dup' doesn't overwrite them every time. And now, as I have... $ LC_ALL=C zypper lr -p # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+---------------------+--------------------+---------+-----------+ ---------+--------- 10 | packman | Packman | Yes | (r ) Yes | Yes | 120 14 | tw-non-oss | tw-non-oss | Yes | (r ) Yes | Yes | 99 15 | tw-oss | tw-oss | Yes | (r ) Yes | Yes | 99 16 | tw-update | tw-update | Yes | (r ) Yes | Yes | 99 ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80.
I normally prefer to install as much as possible from OSS... -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
On 2022-08-24 14:23, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:02:39 CEST, Carlos E. R. napsal(a):
On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
On 2022-07-02 15:10, Kévin Le Gouguec wrote: OK, so I manually installed libjxl0_7 and then installation of
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a): libavcodec59 from Packman worked. Now, I must just lock the package(s) from that repo so 'zypper dup' doesn't overwrite them every time. And now, as I have... $ LC_ALL=C zypper lr -p # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+---------------------+--------------------+---------+-----------+ ---------+--------- 10 | packman | Packman | Yes | (r ) Yes | Yes | 120 14 | tw-non-oss | tw-non-oss | Yes | (r ) Yes | Yes | 99 15 | tw-oss | tw-oss | Yes | (r ) Yes | Yes | 99 16 | tw-update | tw-update | Yes | (r ) Yes | Yes | 99 ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80.
I normally prefer to install as much as possible from OSS...
Except with Packman. When a (multimedia) package is offered by Packman, you really need the Packman version instead. The OSS version is limited by definition. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Dne středa 24. srpna 2022 14:42:52 CEST, Carlos E. R. napsal(a):
On 2022-08-24 14:23, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:02:39 CEST, Carlos E. R. napsal(a):
On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a):
On 2022-07-02 15:10, Kévin Le Gouguec wrote: ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80.
I normally prefer to install as much as possible from OSS...
Except with Packman. When a (multimedia) package is offered by Packman, you really need the Packman version instead. The OSS version is limited by definition.
Of course. But preferably only multimedia from Packman, rest from OSS. -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
* Vojtěch Zeisek <vojtech.zeisek@opensuse.org> [08-24-22 08:47]:
Dne středa 24. srpna 2022 14:42:52 CEST, Carlos E. R. napsal(a):
On 2022-08-24 14:23, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:02:39 CEST, Carlos E. R. napsal(a):
On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a):
On 2022-07-02 15:10, Kévin Le Gouguec wrote: ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80.
I normally prefer to install as much as possible from OSS...
Except with Packman. When a (multimedia) package is offered by Packman, you really need the Packman version instead. The OSS version is limited by definition.
Of course. But preferably only multimedia from Packman, rest from OSS.
zypper -v dup -r packman -- (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
Dne středa 24. srpna 2022 14:51:21 CEST, Patrick Shanahan napsal(a):
* Vojtěch Zeisek <vojtech.zeisek@opensuse.org> [08-24-22 08:47]:
Dne středa 24. srpna 2022 14:42:52 CEST, Carlos E. R. napsal(a):
On 2022-08-24 14:23, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:02:39 CEST, Carlos E. R. napsal(a):
On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a): > On 2022-07-02 15:10, Kévin Le Gouguec wrote: ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80.
I normally prefer to install as much as possible from OSS...
Except with Packman. When a (multimedia) package is offered by Packman, you really need the Packman version instead. The OSS version is limited by definition.
Of course. But preferably only multimedia from Packman, rest from OSS.
zypper -v dup -r packman
This of course works, it just switches everything, which isn't always desired. Otherwise it's of course the easiest solution. :-) -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
On 2022-08-24 14:46, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:42:52 CEST, Carlos E. R. napsal(a):
On 2022-08-24 14:23, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:02:39 CEST, Carlos E. R. napsal(a):
On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a):
On 2022-07-02 15:10, Kévin Le Gouguec wrote: ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80.
I normally prefer to install as much as possible from OSS...
Except with Packman. When a (multimedia) package is offered by Packman, you really need the Packman version instead. The OSS version is limited by definition.
Of course. But preferably only multimedia from Packman, rest from OSS.
When a package does exist in Packman, 99% of the time the OSS version is limited. They don't put a package in Pacman if they are going to be the same thing. There are exceptions some times, as with Lazarus, which is apparently needed for building other packages. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Dne středa 24. srpna 2022 15:02:35 CEST, Carlos E. R. napsal(a):
On 2022-08-24 14:46, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:42:52 CEST, Carlos E. R. napsal(a):
On 2022-08-24 14:23, Vojtěch Zeisek wrote:
Dne středa 24. srpna 2022 14:02:39 CEST, Carlos E. R. napsal(a):
On Wednesday, 2022-08-24 at 13:41 +0200, Vojtěch Zeisek wrote:
Dne sobota 2. července 2022 22:32:31 CEST, Carlos E. R. napsal(a): > On 2022-07-02 15:10, Kévin Le Gouguec wrote: ...how do I keep libavcodec packages from Packman and in other cases give priority to main OSS repo?
I normally give a higher priority (lower number) to packman. Like 80.
I normally prefer to install as much as possible from OSS...
Except with Packman. When a (multimedia) package is offered by Packman, you really need the Packman version instead. The OSS version is limited by definition.
Of course. But preferably only multimedia from Packman, rest from OSS.
When a package does exist in Packman, 99% of the time the OSS version is limited. They don't put a package in Pacman if they are going to be the same thing. There are exceptions some times, as with Lazarus, which is apparently needed for building other packages.
Good point. If changing priority for Packman wouldn't be finally the simplest solution... :-D -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
Kévin Le Gouguec -
Patrick Shanahan -
Vojtěch Zeisek