ghc9.0-common-9.0.2-alt2.noarch	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/bin/ghc is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghc is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghc is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghc-pkg is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghc-pkg is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghc-pkg is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghci is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghci is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/ghci is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/haddock is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/haddock is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/haddock is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hp2ps is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hp2ps is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hp2ps is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hpc is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hpc is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hpc is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hsc2hs is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hsc2hs is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/hsc2hs is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/runghc is different from the same symlink in the package ghc8.10.7-common-8.10.7-alt6.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/runghc is different from the same symlink in the package ghc8.6.4-common-8.6.4-alt12.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/bin/runghc is different from the same symlink in the package ghc9.2-common-9.2.8-alt1.noarch. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
ghc9.0-debuginfo-9.0.2-alt2.x86_64	rpm-filesystem-conflict-symlink-symlink	warn	value of symlink /usr/lib/debug/.build-id/35/33c0af6afa895d1d31d7edfe20d112fb04c0fc is different from the same symlink in the package ghc8.10.7-debuginfo-8.10.7-alt6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/.build-id/35/33c0af6afa895d1d31d7edfe20d112fb04c0fc.debug is different from the same symlink in the package ghc8.10.7-debuginfo-8.10.7-alt6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/.build-id/f3/7353e22cfe08d0d6eb4eb94d439afe827fb87f is different from the same symlink in the package ghc8.10.7-debuginfo-8.10.7-alt6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; value of symlink /usr/lib/debug/.build-id/f3/7353e22cfe08d0d6eb4eb94d439afe827fb87f.debug is different from the same symlink in the package ghc8.10.7-debuginfo-8.10.7-alt6.x86_64. Moreover, the packages have no explicit conflicts with each other. You should add explicit conflicts, or, if conflicts are avoidable, consider using alternatives.; 
ghc9.0-doc-9.0.2-alt2.x86_64	arch-dep-package-consists-of-usr-share	info	The package consists of architecture-independent data in /usr/share, while it is an architecture-dependent package. This is wasteful of mirror space and bandwidth, as we then end up with multiple copies of this data, one for each architecture. If the data in /usr/share is not architecture-independent, it is a policy violation, and in this case, you should move that data elsewhere.;