<div dir="ltr"><div><div>I can confirm there is an issue in upgrading on wheezy (stable).<br><br></div>It uses linux-image-openvz-amd64 042+1 instead of the regular version and generates /boot/vmlinuz-2.6.32-openvz-amd64 instead of the prefixed version, i.e.: /boot/vmlinuz-2.6.32-openvz-042stab084.17-amd64<br>
<br></div>Could you guy look into it and fix it completely, so upgrades will go fine and not break anything?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-03-26 21:21 GMT+04:00 Narcis Garcia <span dir="ltr"><<a href="mailto:informatica@actiu.net" target="_blank">informatica@actiu.net</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">These may be alternatives for version numbering (I've tested them with<br>
dpkg --compare-versions):<br>
<br>
As a complete upstream version:<br>
42.85.20<br>
Combining old and new schema:<br>
042+stab085.20<br>
<br>
<br>
El 26/03/14 17:07, Roman Haefeli ha escrit:<br>
<div class="im HOEnZb">> On Mon, 2014-03-24 at 09:40 -0700, Kir Kolyshkin wrote:<br>
</div><div class="im HOEnZb">>> Thank you for detailed position. I have already rolled back to the old<br>
>> versioning scheme,<br>
>> please check packages in wheezy-test and let me know if anything is<br>
>> wrong there.<br>
><br>
</div><div class="im HOEnZb">> Things look pretty good in wheezy-test. Thanks for the work.<br>
><br>
> Two minor issues:<br>
><br>
> * There is still no changelog of the kernel in the package (or<br>
> I cannot find it, usually it goes to something like:<br>
> /usr/share/doc/linux-image-2.6.32-openvz-042stab085.20-amd64/changelog.Debian.gz<br>
><br>
> * The version of the meta package linux-image-openvz-amd64 is higher<br>
> (042+1) in wheezy than in wheezy-test (042stab085.20). When switching<br>
> from wheezy to wheezy-test, one has to remove and re-install the<br>
> package linux-image-openvz-amd64 in order to automatically install the<br>
> newest kernel packagelinux-image-2.6.32-openvz-042stab085.20-amd64<br>
><br>
> I'm not sure how to resolve the latter problem or whether it should be<br>
> addressed at all (switching from wheezy to wheezy-test can considered to<br>
> be one time thing). However, once the the current wheezy-test<br>
> linux-image-openvz-amd64 goes to wheezy, there is a problem because you<br>
> cannot downgrade packages. Either the version needs to be bumped with an<br>
> epoch version [1] like 1:042stab085.20 (ugly) or the versioning scheme<br>
> needs to be adapted (perhaps also ugly), but how? I can't think of a<br>
> truly satisfying solution right now.<br>
><br>
> [1] <a href="https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version" target="_blank">https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version</a><br>
><br>
><br>
> Roman<br>
><br>
><br>
</div><div class="HOEnZb"><div class="h5">>> On 03/24/2014 09:04 AM, Roman Haefeli wrote:<br>
>>> Hi all, Ola<br>
>>><br>
>>> I followed the recent discussion about OpenVZ kernel package management<br>
>>> for Debian. While I don't really have a qualified opinion on the subject<br>
>>> matter (personally, I slightly tend towards a new package for each<br>
>>> release), let me mention problems with the current situation:<br>
>>><br>
>>> * 'uname -r' does not print the actual version (This already has<br>
>>> been mentioned in the other thread)<br>
>>><br>
>>> * If there is a problem with a kernel update, I cannot easily revert<br>
>>> to the previous version. At our institution, we experienced cases<br>
>>> where a switch to the previous kernel because of a bug was necessary.<br>
>>><br>
>>> * I'm trying to upgrade a machine right now from version 042stab084.26<br>
>>> to newest 042stab085.17. I do:<br>
>>><br>
>>> $ apt-get update && apt-get dist-upgrade<br>
>>><br>
>>> and I'm prompted with the following dialog:<br>
>>><br>
>>> $ Configuring linux-image-2.6.32-openvz-amd64<br>
>>> $ -------------------------------------------<br>
>>> $<br>
>>> $ You are attempting to install a kernel image (version 2.6.32-openvz-amd64) However, the directory /lib/modules/2.6.32-openvz-amd64/kernel still exists. If this directory belongs to a previous linux-image-2.6.32-openvz-amd64<br>
>>> $ package, and if you have deselected some modules, or installed standalone modules packages, this could be bad.<br>
>>> $<br>
>>> $ If /lib/modules/2.6.32-openvz-amd64/kernel belongs to an old install of linux-image-2.6.32-openvz-amd64, then this is your last chance to abort the installation of this kernel image (nothing has been changed yet).<br>
>>> $<br>
>>> $ If you know what you are doing, and if you feel that this image should be installed despite this anomaly, Please answer n to the question.<br>
>>> $<br>
>>> $ Otherwise, I suggest you move /lib/modules/2.6.32-openvz-amd64/kernel out of the way, perhaps to /lib/modules/2.6.32-openvz-amd64.kernel.old or something, and then try re-installing this image.<br>
>>> $<br>
>>> $ Stop install since the kernel-image is already installed?<br>
>>><br>
>>> If Debian does in-place kernel upgrades (a.k.a keeping the package<br>
>>> name while upgrading the kernel), they managed to never bother the<br>
>>> user with a question like this. I certainly know too little about<br>
>>> kernel package management to be of any help, but to me that dialog<br>
>>> indicates that something is still odd.<br>
>>><br>
>>><br>
>>> Those issues might be solved while sticking to the in-place upgrade<br>
>>> scheme and are not necessarily an argument against it. I just wanted to<br>
>>> mention them.<br>
>>><br>
>>> Ranting aside, I am more than happy to see someone puts the effort into<br>
>>> making all the great OpenVZ software easily accessible for Debian<br>
>>> systems. For Debian, the situation has never been better before. Thanks<br>
>>> a lot for that work.<br>
>>><br>
>>> Roman<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Users mailing list<br>
>>> <a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
>>> <a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
> <a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://lists.openvz.org/mailman/listinfo/users" target="_blank">https://lists.openvz.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>