| 1 |
On 21 Apr 2016 13:48, Leno Hou wrote: |
| 2 |
> On Thu, Apr 21, 2016 at 1:42 PM, Mike Frysinger wrote: |
| 3 |
> > On 15 Apr 2016 09:54, Marco Gigante wrote: |
| 4 |
> > > I got a problem with catalyst and latest version of genkernel, installed |
| 5 |
> > > with genkernel-9999 ebuild. |
| 6 |
> > > genkernel --version returns v3.5.0.1 (with the 'v' prefix) and catalyst |
| 7 |
> > > fails to check the minimal required version. |
| 8 |
> > |
| 9 |
> > is this new to 3.5.0.1 ? or did it happen with 3.5.0.0 ? i don't think |
| 10 |
> > it was intentional, so we can always just change genkernel ... |
| 11 |
> |
| 12 |
> Faced the problem only in v3.5.0.1. Not happen in v3.5.0.0 |
| 13 |
> |
| 14 |
> leno@localhost ~ $ genkernel --version |
| 15 |
> |
| 16 |
> v3.5.0.1 |
| 17 |
|
| 18 |
i made the 3.5.0.1 release and def did not mean to make that change. |
| 19 |
but in looking at the git history, i'm not seeing anything since the |
| 20 |
3.5.0.0 tag that looks relevant. |
| 21 |
|
| 22 |
that said, i'm not seeing this behavior: |
| 23 |
$ genkernel --version |
| 24 |
3.5.0.1 |
| 25 |
|
| 26 |
and when i look at the source, it's OK: |
| 27 |
$ tar xf /usr/portage/distfiles/genkernel-3.5.0.1.tar.xz |
| 28 |
$ grep ^GK genkernel-3.5.0.1/genkernel |
| 29 |
GK_V='3.5.0.1' |
| 30 |
|
| 31 |
so where are you guys getting that "v" from ? if your GK_V var is |
| 32 |
also set correctly, send over the output from running: |
| 33 |
$ bash -x genkernel --version |
| 34 |
-mike |
Archives