Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 633426 - sys-kernel/genkernel-3.5.2.1 fails to detect latest sources version
Summary: sys-kernel/genkernel-3.5.2.1 fails to detect latest sources version
Status: RESOLVED DUPLICATE of bug 635266
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Genkernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-04 03:30 UTC by Anton Kochkov
Modified: 2017-10-25 14:44 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
genkernel.log (genkernel.log,311.08 KB, text/x-log)
2017-10-10 14:47 UTC, Anton Kochkov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Kochkov 2017-10-04 03:30:47 UTC
I have installed both sys-kernel/gentoo-sources and sys-kernel/git-sources
Gentoo sources are of 4.13* versions, while git-sources has also 4.14-{rc1,rc2,rc3} installed. Eselect kernel set to the 4.14-rc3, symlink of /usr/src/linux points to 4.14-rc3 sources too.
Running 4.13-rc4 git-sources (from uname)

But if I run "genkernel all" - it starts to build 4.13 somehow, instead of 4.14-rc3 one.
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2017-10-06 18:32:45 UTC
Please attach genkernel output with loglevel 5. 

What might be the case is that prior to running make prepare, genkernel can't always detect the exact version of the new kernel sources (if you broke out after it updated the config and tried again, it would print correctly)
Comment 2 Anton Kochkov 2017-10-10 14:47:57 UTC
Created attachment 498302 [details]
genkernel.log

ls -l /usr/src:

total 92
drwxr-xr-x  3 root root 4096 Sep 17 02:27 debug
lrwxrwxrwx  1 root root   14 Oct  1 10:44 linux -> linux-4.14-rc2
drwxr-xr-x 26 root root 4096 Jun 20 01:17 linux-4.11.6-gentoo
drwxr-xr-x 25 root root 4096 Jun 25 13:12 linux-4.11.7-gentoo
drwxr-xr-x 25 root root 4096 Sep  3 08:35 linux-4.12.10-gentoo
drwxr-xr-x 25 root root 4096 Jul 16 22:45 linux-4.12.1-gentoo
drwxr-xr-x 25 root root 4096 Jul 22 01:19 linux-4.12.2-gentoo
drwxr-xr-x 25 root root 4096 Jul 23 13:19 linux-4.12.3-gentoo
drwxr-xr-x 25 root root 4096 Aug 13 02:46 linux-4.12.6-gentoo
drwxr-xr-x 25 root root 4096 Aug 20 13:31 linux-4.12.8-gentoo
drwxr-xr-x 25 root root 4096 Aug 26 14:20 linux-4.12.9-gentoo
drwxr-xr-x 25 root root 4096 Jun 27 01:12 linux-4.12-rc6
drwxr-xr-x 24 root root 4096 Jul 17 00:07 linux-4.12-rc7
drwxr-xr-x 25 root root 4096 Sep  5 02:50 linux-4.13.0-gentoo
drwxr-xr-x 25 root root 4096 Sep 15 01:41 linux-4.13.2-gentoo
drwxr-xr-x 25 root root 4096 Sep 23 13:51 linux-4.13.3-gentoo
drwxr-xr-x 25 root root 4096 Oct  1 01:48 linux-4.13.4-gentoo
drwxr-xr-x 24 root root 4096 Jul 22 01:18 linux-4.13-rc1
drwxr-xr-x 25 root root 4096 Aug 13 14:18 linux-4.13-rc4
drwxr-xr-x 24 root root 4096 Aug 20 13:30 linux-4.13-rc5
drwxr-xr-x 24 root root 4096 Aug 25 01:32 linux-4.13-rc6
drwxr-xr-x 24 root root 4096 Sep  3 08:45 linux-4.13-rc7
drwxr-xr-x 24 root root 4096 Sep 23 18:37 linux-4.14-rc1
drwxr-xr-x 25 root root 4096 Oct 10 22:38 linux-4.14-rc2

eselect kernel list:

Available kernel symlink targets:
  [1]   linux-4.11.6-gentoo
  [2]   linux-4.11.7-gentoo
  [3]   linux-4.12-rc6
  [4]   linux-4.12-rc7
  [5]   linux-4.12.1-gentoo
  [6]   linux-4.12.2-gentoo
  [7]   linux-4.12.3-gentoo
  [8]   linux-4.12.6-gentoo
  [9]   linux-4.12.8-gentoo
  [10]  linux-4.12.9-gentoo
  [11]  linux-4.12.10-gentoo
  [12]  linux-4.13-rc1
  [13]  linux-4.13-rc4
  [14]  linux-4.13-rc5
  [15]  linux-4.13-rc6
  [16]  linux-4.13-rc7
  [17]  linux-4.13.0-gentoo
  [18]  linux-4.13.2-gentoo
  [19]  linux-4.13.3-gentoo
  [20]  linux-4.13.4-gentoo
  [21]  linux-4.14-rc1
  [22]  linux-4.14-rc2 *

Currently running kernel is 4.13.0-rc4
Comment 3 Anton Kochkov 2017-10-17 14:43:28 UTC
So, any ideas? Should I provide more info? Or any clues why this can happen?
Comment 4 Anton Kochkov 2017-10-25 14:44:53 UTC
Closed in favor of the bug with the valid product field.

*** This bug has been marked as a duplicate of bug 635266 ***