Today this command failed in my local overlay : $>ebuild vanilla-sources-2.6.33.16.ebuild digest although the file could be downloaded from here : http://www.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.33/patch-2.6.33.16.bz2 Maybe the download location "*/logterm/*" should be added to the eclass too ? Reproducible: Always
Why should it be added?
(In reply to comment #1) > Why should it be added? Oops - forget to mention the issue - because emerged didn't found that file.
vanilla-sources-2.6.33-* and gentoo-sources-2.6.33-* have been removed from Portage. We don't support all the -longterm kernels available at kernel.org atm. 2.6.32 is in Portage, as well as 2.6.34 - 2.6.39. So, you can downgrade/upgrade to any of those kernels. Thanks.
(In reply to comment #3) > vanilla-sources-2.6.33-* and gentoo-sources-2.6.33-* have been removed from > Portage. yes - therefore I've it in my overlay > We don't support all the -longterm kernels available at kernel.org atm. 2.6.32 > is in Portage, as well as 2.6.34 - 2.6.39. yes, each vanilla kernel is unsupported by the ewarn message > So, you can downgrade/upgrade to any of those kernels. ofc, I can manually download the tarball. Wwat I'm wondering is, whether it harms the official ebuild to add that location URI too to the ebuild or not
Support for this is already in the eclass. You would need to modify the ebuild and add: K_LONGTERM="1" see sys-kernel/vanilla-sources-2.6.32.42.ebuild for an example. The ebuild you referenced was probably not a longterm kernel when we stopped supporting it.
(In reply to comment #5) > K_LONGTERM="1" Ah - thx for clarifying this.
