Why is not present ebuild openvz-sources under 2.6.22 kernel? When it is declared officially support 2007-09-11. Reproducible: Always Steps to Reproduce: example ebuild: ETYPE="sources" CKV="2.6.22" K_USEPV=1 K_NOSETEXTRAVERSION=1 inherit kernel-2 detect_version OVZ_KERNEL="${PV%%.*}" OVZ_REV="2" KEYWORDS="~amd64 ~ia64 ~ppc64 ~sparc ~x86" IUSE="" DESCRIPTION="Full sources including OpenVZ patchset for the ${KV_MAJOR}.${KV_MINOR} kernel tree" HOMEPAGE="http://www.openvz.org" SRC_URI="${KERNEL_URI} ${ARCH_URI} http://download.openvz.org/kernel/branches/${CKV}/${CKV}-ovz${OVZ_KERNEL}.${OVZ_REV}/patches/patch-ovz${OVZ_KERNEL}.${OVZ_REV}-combined.gz" UNIPATCH_STRICTORDER=1 UNIPATCH_LIST="${DISTDIR}/patch-ovz${OVZ_KERNEL}.${OVZ_REV}-combined.gz"
(In reply to comment #0) > Why is not present ebuild openvz-sources under 2.6.22 kernel? When it is > declared officially support 2007-09-11. With respect, the kernel download page on openvz.org lists 2.6.22 as "development", not "stable": OpenVZ 2.6.22 kernel. Status: development, maintained. Latest version: 2.6.22-ovz003.1 AFAIK, the 'openvz-sources' ebuild is for "stable" tree (though I am open to being corrected). That said, we *could* do a bump for the recently-released (2007-10-1) 2.6.18-ovz028stab045.1 patchset.
Notice, I have marked this ebuild as testing version (~), if nevertheless you consider, that for distribution kit this patch unstable it does not mean, that ebuild should not exist. Disguise it and place in portage.
*** Bug 196189 has been marked as a duplicate of this bug. ***
beside that we generally have the stable kernels in portage, upstream changed versioning again, and i'm not in the mood to fix that right now ...
Artem, you missed the point of ~arch or testing branch. It does not mean to be place for unstable software. It's place for unstable ebuilds that are scripts to build or install software. So branch is for unstable ebuilds but not for unstable software. Generally unstable software should be put into overlays. May be http://overlays.gentoo.org/proj/kernel-packages is a good place, but I'm not sure. That's said, there are deviations from this general rule. But this deviations are fully on maintainers discretion. And again, that's said, it's possible to put this sources hard masked in our tree, but version problem should be solved first, of course.
The new release is still testing branch. Please, reopen bug as soon as upstream considers 2.6.22 stable.
*** Bug 204058 has been marked as a duplicate of this bug. ***
For those who interested I've added openvz-sources-2.6.22.005 to the tree. But as I told this sources are considered by upstream as unstable, hence they are hardmasked. You have to unmask them in /etc/portage/package.unmask (see man portage) to use.
(In reply to comment #8) Thanks for that, had already made my own ebuild of it for testing and an uptodate template as well ;-). I just wanna state there are some problems with this kernel. I can get it to run and create VPS's etc. but I can only run one virtual at the time (note: I am not asking for support on this). Further more 2.6.22 is now considered dead and there will be no more fixes or releases of it, as focus now is on 2.6.24. I suggest instead we should try to get a dev version of 2.6.24 into the tree for testing to be "early" (for once) when vanilla 2.6.24 goes stable and I am prepared to help with this. There is a 2.6.24-ovz1 tag created and announced as a "first release" of 2.6.24 in ovz's git repo, but nothing publically visible in ftp yet. I belive with some bumping it should be possible to get it there as I assume they are interested in getting things tested - and isn't that what we gentooer is at best! :-)