[Users] OpenVZ kernel RPM name
kolyshkin at gmail.com
Mon Oct 16 19:03:23 EDT 2006
I though that (at least) yum detects "install-only" packages by their
'provides', not by name. I might be wrong with that though...here's a
relevant section of /usr/lib/yum-plugins/installonlyn.py (yum-2.6.1):
for instpkg in conf.installonlypkgs:
for m in mems:
if (m.name == instpkg or instpkg in m.po.getProvidesNames()) \
and m.ts_state in ('i', 'u'):
I'm not yum expert but it seems that 'instpkg in m.po.getProvidesNames()' is
the piece of code which helps in this scenario.
We name our kernel packages as 'ovzkernel...' just because we don't want to
mess with usual non-openvz kernels. OpenVZ and non-OpenVZ kernel should not
be treated uniformly, otherwise yum will "upgrade" OpenVZ
2.6.16-basedkernel with stock
2.6.18 -- which is a wrong thing to do. Well, the fact that vzctl depends on
something that ovzkernel provides might help, but I'm not sure.
So, if yum can handle this, we'd rather not change the ovzkernel package
name. I'm not sure about apt though.
On 10/16/06, Dag Wieers <dag at wieers.com> wrote:
> Yet another mail. The official openvz kernel RPMs are named in such a way
> that it causes problems. Tools like yum and apt make a special case about
> kernel RPM files because multiple of these can be installed next to each
> Because OpenVZ name their kernel ovzkernel, this is not possible. Can we
> change the name of the OpenVZ kernel package from:
> This would make it more clear to people what it is based on and would make
> apt and yum work with those kernels by default.
> Kind regards,
> -- dag wieers, dag at wieers.com, http://dag.wieers.com/ --
> [all I want is a warm bed and a kind word and unlimited power]
> Users mailing list
> Users at openvz.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users