[opensuse-factory] zypp multiarch question
Hi, a very simple question about zypp multiarch handling. How does zypp deal with the following situations: 1) A package is available in the base installation source for both x86_64 and i586, and in the update repo there is just an i586 package. The x86_64 package is currently installed and the i586 package in the update repo has a higher version number. Does it "upgrade" (wrt. the version) resp. "downgrade" (wrt. the architecture)? Or will it keep the installed package? 2) Quite the same as 1), but during a system upgrade: Any differences in this respect between a system upgrade and an online update? Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* Andreas Hanke <andreas.hanke@gmx-topmail.de> [Aug 29. 2006 23:15]:
zypp does not change the architecture of an installed package. When checking for 'best' (or 'better') package - architecture is compared first - then edition (epoch, version, release)
2) Quite the same as 1), but during a system upgrade: Any differences in this respect between a system upgrade and an online update?
Yes. System upgrade might change (upgrade) the architecture of a package. Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Klaus Kaempf schrieb:
OK, sounds reasonable. The reason why I'm asking is opera. opera is currently available for i586 and x86_64, but the x86_64 package contains i586 binaries. In fact, both packages' content is identical. The zypp behaviour described above means that the x86_64 package cannot be dropped for further 10.1 updates because zypp would keep the installed x86_64 package and not install updates which are available for i586 only. But it can be done for 10.2, because zypp will switch to the i586 package during the system upgrade. This would save ~6MB in inst-source-extra and even more in the update tree because opera is updated often. Just filed: https://bugzilla.novell.com/show_bug.cgi?id=204729 Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006-08-29 23:15:16 +0200, Andreas Hanke wrote:
thats just a design bug in smart. known upstream. pascal has a patch in his package that stops it. but upstream doesnt like the solution. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcus Rueckert wrote:
Note that it's still partial. It works 100% for the package you want to install (e.g. if you say "smart install foo") but not yet always for the packages smart installs to fulfill dependencies. I have to investigate that further. I'll try to discuss an optimal implementation with Gustavo Niemeyer, to get it merged upstream. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFE+IP4r3NMWliFcXcRAkd6AKCD6TL5WajB9TLprlTyB1LMtejoXgCfZfC8 SpWf72JGQtSZY3wSVs7Ib1s= =D0nk -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Andreas Hanke
-
Klaus Kaempf
-
Marcus Rueckert
-
Pascal Bleser