[opensuse-packaging] file conflicts kernel update on Tumbleweed
HI! The second kernel update after upgrading to Tumbleweed results in file conflicts: File /boot/.vmlinuz-3.19.2-1-desktop.hmac from install of kernel-desktop-3.19.2-1.2.x86_64(openSUSE-20150311-0) conflicts with file from package kernel-desktop-3.19.2-1.1.x86_64(@System) File /boot/vmlinux-3.19.2-1-desktop.gz from install of kernel-desktop-3.19.2-1.2.x86_64(openSUSE-20150311-0) conflicts with file from package kernel-desktop-3.19.2-1.1.x86_64(@System) File /boot/vmlinuz-3.19.2-1-desktop from install of kernel-desktop-3.19.2-1.2.x86_64(openSUSE-20150311-0) conflicts with file from package kernel-desktop-3.19.2-1.1.x86_64(@System) What's going on here? Ciao, Michael.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30.03.2015 Michael Ströder wrote:
What's going on here?
This is being discussed on the factory list:
http://lists.opensuse.org/opensuse-factory/2015-03/msg00423.html
In short: The kernel packages are still not adapted to multiversion, i.e. having multiple kernel packages installed. Some files do not have complete release string (?) in their name. And thus when package kernel-xyz-3.19.2 is being rebuilt and changes the part after the dash from 1.1.x86_64 to 1.2.x86_64, these files conflict. Nasty, scary, and a complete no-go for unexperienced users or those trying out Tumbleweed for example. Normally just installing the package and uninstalling the other package works. fup2 factory Regards, Johannes - -- null -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlUZeG4ACgkQzi3gQ/xETbLHrACgknQHQak45gzZoqO9yIpLRIm+ aAsAnA05INmL4F5uPYUnwpafwpfUYFOT =EvRu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Monday 30 of March 2015 18:23:15 Johannes Kastl wrote:
In short: The kernel packages are still not adapted to multiversion, i.e. having multiple kernel packages installed.
Not true. Multiple kernel packages work fine, I remember having over 20 different kernel RPM's installed at once while working on a bug. The only exception is the case when "newer" kernel is only a spontaneous rebuild of already installed one and both are actually the same. But then there is absolutely no reason to have both installed. So IMHO the way to go here is not using full release in file/directory names but (if possible) preventing zypper from trying to install both at once. Or, if that is not possible, ignoring a file conflict if the "conflicting" files are identical. Michal Kubeček -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Mar 31, 2015 at 12:31 PM, Michal Kubecek <mkubecek@suse.cz> wrote:
Or, if that is not possible, ignoring a file conflict if the "conflicting" files are identical.
I thought it happens already; but I suspect most executable will at least get different timestamp and so will be different, especially after compressing them. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31.03.2015 Michal Kubecek wrote:
The only exception is the case when "newer" kernel is only a spontaneous rebuild of already installed one and both are actually the same.
How is that any different than what I wrote?
But then there is absolutely no reason to have both installed.
Don't tell me, tell zypper... Regards, Johannes -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlUa9P4ACgkQzi3gQ/xETbLabgCfcFYhpEmc4yfVh9icoMBiFFeC a0oAn21XQ4bq7G+EcbUOs3/2nU3pk/9r =OuCt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Johannes Kastl -
Michael Ströder -
Michal Kubecek