[opensuse-factory] desktop kernel file conflict during recent large update
Hello, I started using Tumbleweed this January, so this is new to me. During this recent large update I get a few file conflicts, for example: File /boot/vmlinuz-3.18.3-1-desktop from install of kernel-desktop-3.18.3-1.3.x86_64(openSUSE 20150115-0) conflicts with file from package kernel-desktop-3.18.3-1.1.x86_64(@System) The update is supposed to install kernel-desktop-3.18.3-1.3 (I assume). Currently kernel-desktop-3.18.3-1.1 is installed, so I am confused as to why installing kernel*-1.3 would appear to install a file labeled *-1.1. If I continue (choose "yes") and the old content is replaced, is this the correct action to resolve this conflict? Choosing "no" just aborts the install process. The command I used to update was: "zypper -n update --auto-agree-with-licenses" The repos used are just the ones described in the Tumbleweed installation page, plus the Packman Tumbleweed repo. Thank you for any guidance. -- David Cooper -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2015-02-05 at 11:58 +0000, David Cooper wrote:
Hello,
I started using Tumbleweed this January, so this is new to me. During this recent large update I get a few file conflicts, for example:
File /boot/vmlinuz-3.18.3-1-desktop from install of kernel-desktop-3.18.3-1.3.x86_64(openSUSE 20150115-0) conflicts with file from package kernel-desktop-3.18.3-1.1.x86_64(@System)
The update is supposed to install kernel-desktop-3.18.3-1.3 (I assume). Currently kernel-desktop-3.18.3-1.1 is installed, so I am confused as to why installing kernel*-1.3 would appear to install a file labeled *-1.1.
The files are all ending in 3.18.3-1 (not 1.1); thus conflict
If I continue (choose "yes") and the old content is replaced, is this the correct action to resolve this conflict? Choosing "no" just aborts the install process.
Difficult to say what's right and what's wrong. It mainly happens due to two factors: - The kernel package does not use the exact release number for the file list - Your system is configured to keep multiple versions of the kernel installed (/etz/zypp/zypp.conf)
The command I used to update was: "zypper -n update --auto-agree-with-licenses"
The repos used are just the ones described in the Tumbleweed installation page, plus the Packman Tumbleweed repo.
Nothing you do wrong; I'd say it's a bug in the kernel packaging. Would
you mind raising a bug request for this?
Cheers
--
Dimstar / Dominique Leuenberger
On Thursday 05 of February 2015 13:03:27 Dimstar / Dominique Leuenberger
The kernel package does not use the exact release number for the file list
...
Nothing you do wrong; I'd say it's a bug in the kernel packaging.
That's intentional, AFAIK. Last component of the release string (i.e. the one incremented on spontaneous rebuilds) is not included in uname and therefore also in directory names. Which is not a problem as 3.18.3-1.1 and 3.18.3-1.3 are actually the same kernel. Installing both doesn't make sense; unfortunately the multiversion implementation doesn't expect this and tries to install both. This has never been a problem before as noone would put just a spontaneously rebuilt kernel package into update repository. With Tumbleweed rolling nature, this can apparently happen and some special handling will be needed to avoid this kind of conflicts. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/02/15 23:38, Michal Kubecek wrote:
On Thursday 05 of February 2015 13:03:27 Dimstar / Dominique Leuenberger
The kernel package does not use the exact release number for the file list ...
Nothing you do wrong; I'd say it's a bug in the kernel packaging. That's intentional, AFAIK. Last component of the release string (i.e. the one incremented on spontaneous rebuilds) is not included in uname and therefore also in directory names. Which is not a problem as 3.18.3-1.1 and 3.18.3-1.3 are actually the same kernel. Installing both doesn't make sense; unfortunately the multiversion implementation doesn't expect this and tries to install both.
This has never been a problem before as noone would put just a spontaneously rebuilt kernel package into update repository. With Tumbleweed rolling nature,
In this instance it has nothing to do with Tumbleweed - I am not using Tumbleweed but struck the same problem in 13.2 where I am an using kernels in download.opensuse.org/repositories/Kernel:/stable/standard.
this can apparently happen and some special handling will be needed to avoid this kind of conflicts.
Michal Kube�ek
BC -- Using openSUSE 13.2, KDE 4.14.3 & kernel 3.18.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 06 of February 2015 11:51:37 Basil Chupin wrote:
This has never been a problem before as noone would put just a spontaneously rebuilt kernel package into update repository. With Tumbleweed rolling nature,
In this instance it has nothing to do with Tumbleweed - I am not using Tumbleweed but struck the same problem in 13.2 where I am an using kernels in
download.opensuse.org/repositories/Kernel:/stable/standard.
In case of a repository automatically created by OBS, it's much more frequent (someone might even say "to be expected") and I'm rather surprised you haven't encountered this before. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/02/15 17:16, Michal Kubecek wrote:
On Friday 06 of February 2015 11:51:37 Basil Chupin wrote:
This has never been a problem before as noone would put just a spontaneously rebuilt kernel package into update repository. With Tumbleweed rolling nature, In this instance it has nothing to do with Tumbleweed - I am not using Tumbleweed but struck the same problem in 13.2 where I am an using kernels in
download.opensuse.org/repositories/Kernel:/stable/standard. In case of a repository automatically created by OBS, it's much more frequent (someone might even say "to be expected") and I'm rather surprised you haven't encountered this before.
Michal Kube�ek
I WAS going to add in the reply (although in my post in opensuse-kernel I did state "never, ever, before...") that I have seen similar upgrades of the kernel in the past but they NEVER resulted in this mischief. BC -- Using openSUSE 13.2, KDE 4.14.3 & kernel 3.18.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 2015-02-06 07:27, Basil Chupin wrote:
In case of a repository automatically created by OBS, it's much more frequent (someone might even say "to be expected") and I'm rather surprised you haven't encountered this before.
I WAS going to add in the reply (although in my post in opensuse-kernel I did state "never, ever, before...") that I have seen similar upgrades of the kernel in the past but they NEVER resulted in this mischief.
It did happen before. But before, zypper did not do conflict analysis, and did not ask rpm to do so either. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Fri, 6 Feb 2015 10:54:18 +0100 (CET)
Jan Engelhardt
On Friday 2015-02-06 07:27, Basil Chupin wrote:
In case of a repository automatically created by OBS, it's much more frequent (someone might even say "to be expected") and I'm rather surprised you haven't encountered this before.
I WAS going to add in the reply (although in my post in opensuse-kernel I did state "never, ever, before...") that I have seen similar upgrades of the kernel in the past but they NEVER resulted in this mischief.
It did happen before. But before, zypper did not do conflict analysis, and did not ask rpm to do so either.
Do you mean it effectively did "rpm --replacefiles"? I am not aware how to tell RPM to not check for conflicts, but you can tell it to ignore them. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 2015-02-07 12:26, Andrei Borzenkov wrote:
It did happen before. But before, zypper did not do conflict analysis, and did not ask rpm to do so either.
Do you mean it effectively did "rpm --replacefiles"? I am not aware how to tell RPM to not check for conflicts, but you can tell it to ignore them.
Remember zypper uses --force (which includes --replacefiles). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 06/02/15 00:51, Basil Chupin wrote:
On 05/02/15 23:38, Michal Kubecek wrote:
On Thursday 05 of February 2015 13:03:27 Dimstar / Dominique Leuenberger
The kernel package does not use the exact release number for the file list ...
Nothing you do wrong; I'd say it's a bug in the kernel packaging. That's intentional, AFAIK. Last component of the release string (i.e. the one incremented on spontaneous rebuilds) is not included in uname and therefore also in directory names. Which is not a problem as 3.18.3-1.1 and 3.18.3-1.3 are actually the same kernel. Installing both doesn't make sense; unfortunately the multiversion implementation doesn't expect this and tries to install both.
This has never been a problem before as noone would put just a spontaneously rebuilt kernel package into update repository. With Tumbleweed rolling nature,
In this instance it has nothing to do with Tumbleweed - I am not using Tumbleweed but struck the same problem in 13.2 where I am an using kernels in
download.opensuse.org/repositories/Kernel:/stable/standard.
this can apparently happen and some special handling will be needed to avoid this kind of conflicts.
Michal Kube�ek
BC
I reported this issue as requested: https://bugzilla.opensuse.org/show_bug.cgi?id=916424 where a further comment has been added. -- David Cooper -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op donderdag 5 februari 2015 11:58:23 schreef David Cooper:
Hello,
I started using Tumbleweed this January, so this is new to me. During this recent large update I get a few file conflicts, for example:
File /boot/vmlinuz-3.18.3-1-desktop from install of kernel-desktop-3.18.3-1.3.x86_64(openSUSE 20150115-0) conflicts with file from package kernel-desktop-3.18.3-1.1.x86_64(@System)
The update is supposed to install kernel-desktop-3.18.3-1.3 (I assume). Currently kernel-desktop-3.18.3-1.1 is installed, so I am confused as to why installing kernel*-1.3 would appear to install a file labeled *-1.1.
If I continue (choose "yes") and the old content is replaced, is this the correct action to resolve this conflict? Choosing "no" just aborts the install process.
I just answered yes as I did not anticipate any ill effects and all went well. I later removed 3.18.3-1.1 -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/02/15 23:18, Freek de Kruijf wrote:
Op donderdag 5 februari 2015 11:58:23 schreef David Cooper:
Hello,
I started using Tumbleweed this January, so this is new to me. During this recent large update I get a few file conflicts, for example:
File /boot/vmlinuz-3.18.3-1-desktop from install of kernel-desktop-3.18.3-1.3.x86_64(openSUSE 20150115-0) conflicts with file from package kernel-desktop-3.18.3-1.1.x86_64(@System)
The update is supposed to install kernel-desktop-3.18.3-1.3 (I assume). Currently kernel-desktop-3.18.3-1.1 is installed, so I am confused as to why installing kernel*-1.3 would appear to install a file labeled *-1.1.
If I continue (choose "yes") and the old content is replaced, is this the correct action to resolve this conflict? Choosing "no" just aborts the install process. I just answered yes as I did not anticipate any ill effects and all went well.
A reasonable solution to one who either: 1) has lady luck on his side; or 2) has nothing to lose; or 3) knows what he is doing, but it is simply a heart-stopper to a newbie who has been led to believe that openSUSE doesn't release into its repositories something which hasn't been fully tested (except for Factory that is) :-) .
I later removed 3.18.3-1.1
STOP PRESS! I just realised something! *I* am using and making comments about kernel *3.18.5-1* - repeat 3.18.5-1 - and NOT 3.18.3.1 which this thread is all about! I went thru kernel 3.18.3-1 quite some time ago and did not have the hassle mentioned in this thread. But I did have/am having a hassle with 3.18.5-1.1 => 3.18.5-1.2. This should give someone a clue as to when or what has changed to cause this problem with "file conflicts". BC -- Using openSUSE 13.2, KDE 4.14.3 & kernel 3.18.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Andrei Borzenkov -
Basil Chupin -
David Cooper -
Dimstar / Dominique Leuenberger -
Freek de Kruijf -
Jan Engelhardt -
Michal Kubecek