[yast/yast-yast2] e1b1c7: Fixed libzypp initialization (related to bsc#1199840)
![](https://seccdn.libravatar.org/avatar/9181eb84f9c35729a3bad740fb7f9d93.jpg?s=120&d=mm&r=g)
Branch: refs/heads/master Home: https://github.com/yast/yast-yast2 Commit: e1b1c7f6eb140ca8a582f019ad348cbd29eb1489 https://github.com/yast/yast-yast2/commit/e1b1c7f6eb140ca8a582f019ad348cbd29... Author: Ladislav Slezák <lslezak@suse.cz> Date: 2022-07-27 (Wed, 27 Jul 2022) Changed paths: M library/packages/src/modules/PackageSystem.rb M package/yast2.changes M package/yast2.spec Log Message: ----------- Fixed libzypp initialization (related to bsc#1199840) In the YaST container read the configured repositories from the host - 4.5.8 Details: It turned out that the problem is in the Pkg.GetSolverFlags call which is called before initializing libzypp. In that case libzypp automatically initializes itself, but it uses by default the system root (/) which is the container. The libzypp initialization later done from YaST does not change anything as libzypp is already initialized. Also it initialized the libzypp in a wrong order. The libzypp target always needs to be initialized before initializing the libzypp sources. The reason is that the target defines which GPG keys and config file (zypp.conf) are used. When initializing in wrong order you might get GPG signature errors. Commit: 1ce6c5d2f2188f757b73550e738a188bdd8c1d1c https://github.com/yast/yast-yast2/commit/1ce6c5d2f2188f757b73550e738a188bdd... Author: Ladislav Slezák <lslezak@suse.cz> Date: 2022-07-27 (Wed, 27 Jul 2022) Changed paths: M library/packages/src/modules/PackageSystem.rb M package/yast2.changes M package/yast2.spec Log Message: ----------- Merge pull request #1263 from yast/packages_in_container Compare: https://github.com/yast/yast-yast2/compare/03e8ef6deed3...1ce6c5d2f218
participants (1)
-
Ladislav Slezák