Multilib/arch rpms may fail the "is this an update" test

[LukeHandle]

It's possible that multilib/multiarch packages that share certain files might never get updated. This is because they fail the "is this an update" test:

auter/auter.yumdnfModule

Line 134 in 88fe862

rpm -U --nodeps --test "$_package" &>/dev/null && rpms+=("$_package")

# rpm -q libstdc++
libstdc++-4.8.5-36.el7.x86_64
libstdc++-4.8.5-36.el7.i686

# rpm -U --nodeps --test /var/cache/auter/default/libstdc++-4.8.5-39.el7.x86_64.rpm; echo -e "\n\nExit: $?"
	file /usr/share/gcc-4.8.2/python/libstdcxx/v6/printers.pyc from install of libstdc++-4.8.5-39.el7.x86_64 conflicts with file from package libstdc++-4.8.5-36.el7.i686
	file /usr/share/gcc-4.8.2/python/libstdcxx/v6/printers.pyo from install of libstdc++-4.8.5-39.el7.x86_64 conflicts with file from package libstdc++-4.8.5-36.el7.i686


Exit: 2

# rpm -q pam
pam-1.1.8-22.el7.x86_64
pam-1.1.8-22.el7.i686

# rpm -U --nodeps --test /var/cache/auter/default/pam-1.1.8-23.el7.x86_64.rpm; echo -e "\n\nExit: $?"
	file /usr/share/doc/pam-1.1.8/Linux-PAM_SAG.txt from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/doc/pam-1.1.8/html/sag-pam_loginuid.html from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/doc/pam-1.1.8/html/sag-pam_wheel.html from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/doc/pam-1.1.8/txts/README.pam_loginuid from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/doc/pam-1.1.8/txts/README.pam_tty_audit from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/doc/pam-1.1.8/txts/README.pam_wheel from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man5/access.conf.5.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man5/limits.conf.5.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man5/pam_env.conf.5.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/PAM.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/faillock.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_access.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_env.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_exec.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_faillock.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_loginuid.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_tty_audit.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_unix.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_userdb.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pam_wheel.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686
	file /usr/share/man/man8/pwhistory_helper.8.gz from install of pam-1.1.8-23.el7.x86_64 conflicts with file from package pam-1.1.8-22.el7.i686


Exit: 2

[mark-hyde]

Thanks Luke,

My first thought is 'multilibs are tricky' :D

I'll keep this open for now and see if we can work out what to do with them.