Forwarding this message from the Factory mailing list since it contains some interesting feedback about how YaST handles the conflicts reported by libzypp. On 11/22/18 6:51 PM, Brüns, Stefan wrote:

On Donnerstag, 22. November 2018 17:35:20 CET Ludwig Nussel wrote:

...

Am 20.11.18 um 18:04 schrieb Brüns, Stefan:

...

On Dienstag, 20. November 2018 17:36:10 CET Ancor Gonzalez Sosa wrote:

...

YaST development keeps rolling. Check the latest report at https://lizards.opensuse.org/2018/11/20/yast-sprint-67/

...

with a lot of information about new features in the installer, like: [...]

...

- Easing the network configuration and the usage of online

repositories in openSUSE.

-- Tumbleweed: Add Online Repositories during Installation --

Is it also possible to add community repos (e.g. packman) during the installation? This would avoid the repeated confirmation for repository changes for all the affected packages, which can be a lot.

That is not the goal. The feature is more useful for Leap anyways where the update repo may be included during installation already to avoid having to download packages twice. Once the original from the release and then again an updated one. Anways, why does Packman replace lots of packages? I thought it mostly adds supplemental packages?

This is not always possible. For gstreamer, addon packages are used, but e.g. the ffmpeg libraries (libavcoded, libavutil, libavdevice ...) are monolitic and have to be exchanged.

E.g. the vlc-codecs package requires libavcodec<version>(unrestricted), which is only provided by the libavcodec package from packman. When the packman repo is added after some of the ffmpeg libraries have been installed, this leads to a vendor change.

The current conflict resolution dialog is not very user friendly, but quite low level (and it even has an "Expert mode" button on top).

One problem is the grouping of conflicts (in Yast), each conflict has to be solved indiviually, although the solution may be the same for all (in this case, a vendor change). One can avoid solving some of the conflicts by selecting a solution for one conflict and clicking "Ok - retry", but thats not very intuitive.

If the dialog instead stated: --- Warning - for installing "vlc-codecs" from "packman", some of your currently installed packages have to be replaced with packages from the "packman" repository.

Following packages needs to be replaced: - libavcodec57 - libavdevice57 ...

[x] Show details

[Allow replacement] [Expert mode] [Cancel] --- it would be much more comprehensible for beginners.

Expert mode could show the current dialog. "Show details" would show e.g. versions, repository URLs. Allow replacement would rerun the solver with the accepted changes, and eventually show the next conflict.

Prerequisite for using/showing the dialog would be existance of a common conflict resolution. But a required vendor change is the conflict resolution which I have seen most often, and which is typically the wanted one (On TW, there is the occasional package downgrade, or an incomplete package rename - missing provides/obsoletes - but these are very seldom).

The idea of grouping conflicts to not have to reply the same over and over makes sense. We can claim YaST is not the right place for such grouping, that it should come from libzypp. But maybe there is something we can do about it, like an "apply same decision" checkbox. I don't know. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org