[opensuse-factory] zypper and conflicts in multiversion packages
zypper dup du jour yields: Checking for file conflicts: ............................................[error] Detected 3 file conflicts: File /boot/.vmlinuz-3.16.0-1-default.hmac from install of kernel-default-3.16.0-1.2.x86_64(factory) conflicts with file from package kernel-default-3.16.0-1.1.x86_64(@System) [...] File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): This particular issue is because kernels are set to multiversion, which means zypper tries to keep both packages. Arguably that is a losing situation. I guess zypper should show a choice dialog with a third/fourth option: - remove kernel-default-3.16.0-1.1.x86_64 - do not install kernel-default-3.16.0-1.2.x86_64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, 30 Aug 2014 14:49:47 +0200 (CEST) Jan Engelhardt <jengelh@inai.de> wrote:
zypper dup du jour yields:
Checking for file conflicts: ............................................[error] Detected 3 file conflicts:
File /boot/.vmlinuz-3.16.0-1-default.hmac from install of kernel-default-3.16.0-1.2.x86_64(factory) conflicts with file from package kernel-default-3.16.0-1.1.x86_64(@System) [...] File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no):
I have previously noticed this with Tumbleweed, except that zypper just went ahead and did it without asking about the file conflict. I presume this is a case where what is basically the same kernel has been recompiled. The problem I see with this, is that it defeats the idea of multi-version kernel. In effect, my factory system has only one kernel. Yast shows two, but with respect to what is actually in "/boot" and used for booting, there is only one. Before this update, there was an rc-7 kernel, but that was deleted leaving only the one. With Tumbleweed, the purge-kernels service was not working, so I was still left with multiple kernels. I had to manually delete if I wanted to clean up. Personally, I think zypper should have just updated from 3.16.0-1 to 3.16.0.2, keeping only one 3.16.0 kernel. That way, the purge-kernels would not have removed the older "-rc7" kernel, so I would still have a fallback kernel. As to whether this needs fixing -- I'm not so sure it does. I expect that it only affects factory (and Tumbleweed), but is not likely to affect a regular release. And people running factory are expected to be able to deal with this sort of issue. Perhaps I'll change the multiversion setting in "zypp.conf" to also keep "oldest". And then I can manually delete the oldest kernel when I am satisfied that I won't need it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
HI, this seems to be a bug in kernel packaging. Open a bugreport? Ciao, Marcus On Sat, Aug 30, 2014 at 02:49:47PM +0200, Jan Engelhardt wrote:
zypper dup du jour yields:
Checking for file conflicts: ............................................[error] Detected 3 file conflicts:
File /boot/.vmlinuz-3.16.0-1-default.hmac from install of kernel-default-3.16.0-1.2.x86_64(factory) conflicts with file from package kernel-default-3.16.0-1.1.x86_64(@System) [...] File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no):
This particular issue is because kernels are set to multiversion, which means zypper tries to keep both packages. Arguably that is a losing situation. I guess zypper should show a choice dialog with a third/fourth option: - remove kernel-default-3.16.0-1.1.x86_64 - do not install kernel-default-3.16.0-1.2.x86_64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2014-08-31 10:06, Marcus Meissner wrote:
HI,
this seems to be a bug in kernel packaging.
It may very well be a bug in the kernel in that it ships files that end up conflicting, but my report here was about how zypper fails to not meet my expectations _if and when_ such conflict happens [in any package, for that matter] :)
zypper dup du jour yields:
Checking for file conflicts: ............................................[error] Detected 3 file conflicts:
File /boot/.vmlinuz-3.16.0-1-default.hmac from install of kernel-default-3.16.0-1.2.x86_64(factory) conflicts with file from package kernel-default-3.16.0-1.1.x86_64(@System) [...] File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no):
This particular issue is because kernels are set to multiversion, which means zypper tries to keep both packages. Arguably that is a losing situation. I guess zypper should show a choice dialog with a third/fourth option: - remove kernel-default-3.16.0-1.1.x86_64 - do not install kernel-default-3.16.0-1.2.x86_64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 31 of August 2014 10:33:16 Jan Engelhardt wrote:
On Sunday 2014-08-31 10:06, Marcus Meissner wrote:
HI,
this seems to be a bug in kernel packaging.
It may very well be a bug in the kernel in that it ships files that end up conflicting, but my report here was about how zypper fails to not meet my expectations _if and when_ such conflict happens [in any package, for that matter] :)
In this case, the conflict makes sense as 3.16.0-1.1 and 3.16.0-1.2 are only rebuilds without source change so that the resulting kernels have the same uname (3.16.0-1-default). But I'm not sure there is an easy way to prevent zypper from trying to install both. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Jan Engelhardt -
Marcus Meissner -
Michal Kubecek -
Neil Rickert