From: Marco Gigante <m.gigante@nextworks.it>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] genkernel version parsing problem
Date: Thu, 21 Apr 2016 08:34:00 +0200 [thread overview]
Message-ID: <57187458.3020106@nextworks.it> (raw)
In-Reply-To: <CAGQVrL8Jg4HurK2MQ-ZLjsUXysdCNuYdryPEPUs5V8OaSVWmCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On 21/04/2016 07:48, Leno Hou wrote:
> On Thu, Apr 21, 2016 at 1:42 PM, Mike Frysinger <vapier@gentoo.org
> <mailto:vapier@gentoo.org>> wrote:
>
> On 15 Apr 2016 09:54, Marco Gigante wrote:
> > I got a problem with catalyst and latest version of genkernel,
> installed
> > with genkernel-9999 ebuild.
> > genkernel --version returns v3.5.0.1 (with the 'v' prefix) and
> catalyst
> > fails to check the minimal required version.
>
> is this new to 3.5.0.1 ? or did it happen with 3.5.0.0 ? i don't
> think
> it was intentional, so we can always just change genkernel ...
>
I looked at genkernel before writing and GK_V is "3.5.0.1". Couldn't
quickly figure out where the 'v' comes from.
I just analysed the issue, and it is the genkernel-9999 ebuild which
modifies the GK_V into src_prepare(), by picking the git tag as version
number.
Not sure which is better, change genkernel or catalyst. I guess
protecting version check in catalyst will make it more reliable anyway.
-marco
> -mike
>
>
> Faced the problem only in v3.5.0.1. Not happen in v3.5.0.0
>
> leno@localhost~ $ genkernel --version
>
> v3.5.0.1
>
>
> -Leno Hou
[-- Attachment #2: Type: text/html, Size: 3744 bytes --]
next prev parent reply other threads:[~2016-04-21 6:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 7:54 [gentoo-catalyst] genkernel version parsing problem Marco Gigante
2016-04-21 5:41 ` Leno Hou
2016-04-21 5:42 ` Mike Frysinger
2016-04-21 5:48 ` Leno Hou
2016-04-21 6:21 ` Mike Frysinger
2016-04-21 6:29 ` Leno Hou
2016-04-21 6:34 ` Leno Hou
2016-04-21 16:43 ` Mike Frysinger
2016-04-21 6:34 ` Marco Gigante [this message]
2016-04-21 17:05 ` Mike Frysinger
2016-04-22 6:49 ` Marco Gigante
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57187458.3020106@nextworks.it \
--to=m.gigante@nextworks.it \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox