Mailinglist Archive: zypp-devel (52 mails)

[Dave Plater <dplater@xxxxxxxxxxxxxxxx>]

I'm busy debugging the lilypond build in home:plater:lilypond and this involves adding various packages to the sub project to try to get 
the same build results in 11.3, 11.4 and factory repos. To avoid network noise I use an unattended cron job to do a zypper dup of KDF and 
the above mentioned repo to my x86_64 11.4 system. A test "zypper -v dup -r plalily" today has alarmed me as it wanted to install all the 
i586 ghostscript rpms from the ghostscript-library package. I went through /etc/zypp/zypp.conf and couldn't find any option to prevent this 
from happening. There is something wrong with the repo as even after deleting the i586 binaries from 11.4 the i586 directory still has 
ghostscript but x86_64 has nothing, this is not a libzypp problem the problem is that if this happens in KDE:Distro:Factory for instance 
I'll end up with a whole bunch of i586 rpms installed. Why is libzypp allowed to change x86_64 packages to i586 silently? I understand the 
reasoning behind having i586 packages that have never had x86_64 versions and are supported by 32 bit x86_64 libs but allowing an i586 
package to replace an x86_64 one without asking has no logic in it at all and there should be a mechanism in place to allow a user to 
prevent this.

Thanks
Dave P


--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx