Comment # 12 on bug 1175967 from Benjamin Zeller

(In reply to Fabian Vogt from comment #11)
> 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125
> job: install rpm.i586
> 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 
> - job Rule #98281:
> 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 
> rpm-4.14.2.1-5.1.i586 [4294] (w1)
> 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 
> rpm-4.15.1-6.2.i586 [84879] (w2)
> 2020-08-27 14:19:07 <1> linux-xkgz(10495) [libsolv] PoolImpl.cc(logSat):125 
> rpm-4.14.2.1-5.1.i586 [119820]I
> 
> That looks a bit suspicious to me, maybe a lock?

I actually have the same in my dup (leap in that case) logs, seems that rule is
injected to make sure rpm stays on the system:

2020-08-25 09:37:04 <1> linux-2ggq(4238) [libsolv] PoolImpl.cc(logSat):125   -
job Rule #90752:
2020-08-25 09:37:04 <1> linux-2ggq(4238) [libsolv] PoolImpl.cc(logSat):125    
rpm-4.14.1-lp152.17.5.x86_64 [54810] (w1)
2020-08-25 09:37:04 <1> linux-2ggq(4238) [libsolv] PoolImpl.cc(logSat):125    
rpm-4.14.1-lp152.17.5.x86_64 [84582]I (w2)

This would be a example for a lock (keyword erase):

2020-08-25 09:37:04 <1> linux-2ggq.suse(4238) [libsolv] PoolImpl.cc(logSat):125
job: erase
texlive-afm2pl-bin-debuginfo-2017.20170520.svn44143-lp152.15.2.x86_64
2020-08-25 09:37:04 <1> linux-2ggq.suse(4238) [libsolv] PoolImpl.cc(logSat):125
  - job Rule #90753:
2020-08-25 09:37:04 <1> linux-2ggq.suse(4238) [libsolv] PoolImpl.cc(logSat):125
    !texlive-afm2pl-bin-debuginfo-2017.20170520.svn44143-lp152.15.2.x86_64
[24111] (w1)