[opensuse-factory] TW : multiversions of kernel-default & zypper dup
Hello List , this evening , zypper dup -d produces : " The following 2 NEW packages are going to be installed: kernel-default-4.2.3-1.4 The following package is going to be REMOVED: kernel-default-4.2.3-1.1 in /etc/zypp/zypp.conf the following line is un-commented : multiversion = provides:multiversion(kernel) ......................... calling " zypper dup ' , after the TW change from kernel-desktop to kernel-default , zypper requires the removal of the old kernel-default when installing new kernel-default . . . How can one have zypper dup keep multiversions ? .............. thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
26.10.2015 22:33, ellanios82 пишет:
Hello List ,
this evening , zypper dup -d produces :
" The following 2 NEW packages are going to be installed: kernel-default-4.2.3-1.4
The following package is going to be REMOVED: kernel-default-4.2.3-1.1
in /etc/zypp/zypp.conf the following line is un-commented :
multiversion = provides:multiversion(kernel)
.........................
calling " zypper dup ' , after the TW change from kernel-desktop to kernel-default , zypper requires the removal of the old kernel-default when installing new kernel-default
. . . How can one have zypper dup keep multiversions ?
Multiple rebuilds of the same version cannot be installed in parallel anyway, they overwrite each other. So only the last installed package will be physically present. So this is a bug fix. It resulted in RPM conflict in the past. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
26.10.2015 22:45, Andrei Borzenkov пишет:
26.10.2015 22:33, ellanios82 пишет:
Hello List ,
this evening , zypper dup -d produces :
" The following 2 NEW packages are going to be installed: kernel-default-4.2.3-1.4
The following package is going to be REMOVED: kernel-default-4.2.3-1.1
in /etc/zypp/zypp.conf the following line is un-commented :
multiversion = provides:multiversion(kernel)
.........................
calling " zypper dup ' , after the TW change from kernel-desktop to kernel-default , zypper requires the removal of the old kernel-default when installing new kernel-default
. . . How can one have zypper dup keep multiversions ?
Multiple rebuilds of the same version cannot be installed in parallel anyway, they overwrite each other. So only the last installed package will be physically present. So this is a bug fix. It resulted in RPM conflict in the past.
But now I ask myself why "zypper up" does not install it ... 10:~ # zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW package is going to be installed: kernel-default-4.2.3-1.4 The following package is going to be REMOVED: kernel-default-4.2.3-1.1 The following package is going to be downgraded: gnu-unifont-bitmap-fonts 1 package to downgrade, 1 new, 1 to remove. Overall download size: 47.5 MiB. Already cached: 0 B. After the operation, 485.7 KiB will be freed. Continue? [y/n/? shows all options] (y): n 10:~ # zypper up Loading repository data... Reading installed packages... The following package update will NOT be installed: kernel-default Nothing to do. 10:~ # What is the difference? Also "zypper info kernel-default" says "out of date" which is correct; why "zypper up" ignores it? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Oct 26, Andrei Borzenkov wrote:
But now I ask myself why "zypper up" does not install it ...
Because both contain filenames ending with "4.2.3-1", rather than "4.2.3-1.4" vs. "4.2.3-1.1". Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Oct 27, 2015 at 9:47 AM, Olaf Hering <olaf@aepfle.de> wrote:
On Mon, Oct 26, Andrei Borzenkov wrote:
But now I ask myself why "zypper up" does not install it ...
Because both contain filenames ending with "4.2.3-1", rather than "4.2.3-1.4" vs. "4.2.3-1.1".
Could you elaborate? How filenames inside RPM are related to comparing two RPM versions and choosing one with higher version? I just try to understand what zypper logic is based on. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Oct 27, Andrei Borzenkov wrote:
On Tue, Oct 27, 2015 at 9:47 AM, Olaf Hering <olaf@aepfle.de> wrote:
On Mon, Oct 26, Andrei Borzenkov wrote:
But now I ask myself why "zypper up" does not install it ...
Because both contain filenames ending with "4.2.3-1", rather than "4.2.3-1.4" vs. "4.2.3-1.1".
Could you elaborate? How filenames inside RPM are related to comparing two RPM versions and choosing one with higher version? I just try to understand what zypper logic is based on.
I do not know the logic inside libzypp. Most likely it has some knowledge to prevent the resulting filename conflicts. Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* ellanios82 <ellanios82@gmail.com> [10-26-15 15:36]: [...]
. . . How can one have zypper dup keep multiversions ?
try applying locks to the present kernels (+ devel...), then zypper -v up -d kernel*** then rpm -Uvh kernel* should work, I am presently doing that but dl appears somewhat slow today :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 10/26/2015 09:45 PM, Patrick Shanahan wrote:
. . . How can one have zypper dup keep multiversions ?
* ellanios82 <ellanios82@gmail.com> [10-26-15 15:36]: [...] try applying locks to the present kernels (+ devel...), then zypper -v up -d kernel***
then rpm -Uvh kernel*
should work, I am presently doing that but dl appears somewhat slow today :) ...........
- thank you Patrick : tried this , added zypper al kernel-default-4.2.3-1.1.x86_64 but, i guess i did something wrong , because after commanding : rpm -Uvh kernel-default-4.2.3-2.1.g202286f.x86_64.rpm nevertheless , the locked kernel-default-4.2.3-1.1.x86_64 got removed anyway :( ................ regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* ellanios82 <ellanios82@gmail.com> [10-26-15 16:43]:
On 10/26/2015 09:45 PM, Patrick Shanahan wrote:
. . . How can one have zypper dup keep multiversions ?
* ellanios82 <ellanios82@gmail.com> [10-26-15 15:36]: [...] try applying locks to the present kernels (+ devel...), then zypper -v up -d kernel***
then rpm -Uvh kernel*
should work, I am presently doing that but dl appears somewhat slow today :) ...........
- thank you Patrick : tried this , added zypper al kernel-default-4.2.3-1.1.x86_64
but,
i guess i did something wrong , because after commanding :
rpm -Uvh kernel-default-4.2.3-2.1.g202286f.x86_64.rpm
nevertheless , the locked kernel-default-4.2.3-1.1.x86_64 got removed anyway :(
The explanation, iiuc, is that you still have the same kernel, 4.2.3, just a maintenance update of the existing, not a *new* kernel and version. But the same thing occurred with the switch to kernel-default..... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Montag, 26. Oktober 2015 schrieb ellanios82:
On 10/26/2015 09:45 PM, Patrick Shanahan wrote:
* ellanios82 <ellanios82@gmail.com> [10-26-15 15:36]: [...]
. . . How can one have zypper dup keep multiversions ?
try applying locks to the present kernels (+ devel...), then zypper -v up -d kernel***
then rpm -Uvh kernel*
should work, I am presently doing that but dl appears somewhat slow today> :)
...........
- thank you Patrick : tried this , added zypper al kernel-default-4.2.3-1.1.x86_64
but,
i guess i did something wrong , because after commanding :
rpm -Uvh kernel-default-4.2.3-2.1.g202286f.x86_64.rpm
nevertheless , the locked kernel-default-4.2.3-1.1.x86_64 got removed anyway :(
You are mixing high-level tools (zypper/libzypp) and low-level tools (rpm). rpm does not know anything about zypper locks [1], therefore it's not surprising that it follows the Obsoletes: [2] and uninstalls the other kernel - which is just an older build of the same code. As Andrei already wrote in another mail, multiple rebuilds of the same kernel version can't be installed in parallel because they would overwrite each other's files. Regards, Christian Boltz [1] if you want locks on the rpm level, you might try installing a dummy rpm with proper Requires: or Conflicts: in its spec. [2] I didn't check, but that's my guess about how it is implemented in the kernel spec/rpm. -- Und da Du mit der Installation so wenig Probleme hast, könntest Du doch die gesparte Zeit in ein paar Großbuchstaben investieren. Liest sich besser am Bildschirm. Danke. [Helga Fischer in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Christian Boltz -
ellanios82 -
Olaf Hering -
Patrick Shanahan