> > What do you talk about exactly? > > > Did you see my last post?
yes > pve-kernel-3.10.0-15-pve (3.10.0-41) <-- todays update That update was Sun, 17 Jan (not today) > pve-kernel-3.10.0-16-pve (3.10.0-42) > > pve-kernel-3.10.0-16-pve already contains the patch 3.10.0-41 so why backport > fixes to a kernel version which is superseded by a newer release in the same > kernel line? What backport do you talk about? Current version is pve-kernel-3.10.0-16-pve (3.10.0-43): pve-kernel-3.10.0 (3.10.0-43) unstable; urgency=low * update to kernel-3.10.0-327.4.5.el7.src.rpm * remove CVE-2016-0728-fix-keyring-ref-leak.patch (upstream) -- Proxmox Support Team <supp...@proxmox.com> Tue, 09 Feb 2016 17:45:35 +0100 pve-kernel-3.10.0 (3.10.0-42) unstable; urgency=low * update to kernel-3.10.0-327.4.4.el7.src.rpm * fix CVE-2016-0728 -- Proxmox Support Team <supp...@proxmox.com> Thu, 21 Jan 2016 09:28:43 +0100 Note: 3.10.0-42 is exactly the same code, so I did not upload 3.10.0-43 to enterprise repo. _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
