layman -S does not detect linux-sabayon-2.6.26 [Solved]

[Fitzcarraldo]

sys-kernel/linux-sabayon-2.6.26 is in the SL SVN repo but for some reason my installation does not see it:

# layman -S
* Running command "/usr/bin/svn update "/usr/local/portage/layman/sabayon""...
At revision 2475.
*
* Success:
* ------
*
* Successfully synchronized overlay "sabayon".

# emerge -s linux-sabayon
Searching...
[ Results for search key : linux-sabayon ]
[ Applications found : 2 ]

* sys-kernel/linux-sabayon
Latest version available: 2.6.25-r1
Latest version installed: 2.6.25-r1
Size of files: 47,650 kB
Homepage: http://www.sabayonlinux.org
Description: Official Sabayon Linux kernel images and sources
License: GPL-2

* sys-kernel/linux-sabayon-modules
Latest version available: 2.6.23-r1
Latest version installed: [ Not Installed ]
Size of files: 0 kB
Homepage: http://www.sabayonlinux.org/
Description: Sabayon Linux kernel modules meta package
License: GPL-2


Any ideas?


BTW, I've already tried several times doing:
# layman -d sabayon
# layman -a sabayon
which completes without hitches but makes no difference.

[wolfden]

usually deleting the overlay and re-adding it takes care of issues like that. that is weird.

[Fitzcarraldo]

OK, this is getting annoying. I tried again just now:

First delete the overlay:

Code: Select all

# layman -d sabayon
* Successfully deleted overlay "sabayon".

Now add it again, but this time save the list of files downloaded in a text file so I can check it afterwards:

Code: Select all

# layman -a sabayon > /tmp/list_of_packages.txt

Now check the list to see if the 2.6.26 kernel files were included:

Code: Select all

# cat /tmp/list_of_packages.txt | grep 2.6.26
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.26-amd64.config
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/linux-sabayon-2.6.26-x86.config
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/linux-sabayon-2.6.26-at76.patch
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/linux-sabayon-2.6.26-tuxonice-3.0-rc7.patch.bz2
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/linux-sabayon-2.6.26-atl2.patch
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/genpatches
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/genpatches/4300_squashfs-3.3.patch
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/genpatches/2600_evdev-compat-ioctl-force-feedback.patch
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/genpatches/4200_fbcondecor-0.9.4.patch
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/linux-sabayon-2.6.26-from-ext4dev-to-ext4.patch
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/files/2.6.26/linux-sabayon-2.6.26-aufs.patch
A    /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/linux-sabayon-2.6.26.ebuild

So it looks like they were. But, to be sure, let's actually look:

Code: Select all

# cd /usr/local/portage/layman/sabayon/sys-kernel/linux-sabayon/
# ls
files  linux-sabayon-2.6.23-r1.ebuild  linux-sabayon-2.6.24.ebuild  linux-sabayon-2.6.25-r1.ebuild  linux-sabayon-2.6.26.ebuild  Manifest
# cd files
# ls
2.6.23  2.6.26                             linux-sabayon-2.6.24-amd64.config  linux-sabayon-2.6.25-r1-amd64.config  linux-sabayon-2.6.26-amd64.config
2.6.24  linux-sabayon-2.6.23-amd64.config  linux-sabayon-2.6.24-x86.config    linux-sabayon-2.6.25-r1-x86.config    linux-sabayon-2.6.26-x86.config
2.6.25  linux-sabayon-2.6.23-x86.config    linux-sabayon-2.6.25-amd64.config  linux-sabayon-2.6.25-x86.config
# cd 2.6.26
# ls
genpatches                       linux-sabayon-2.6.26-atl2.patch  linux-sabayon-2.6.26-from-ext4dev-to-ext4.patch
linux-sabayon-2.6.26-at76.patch  linux-sabayon-2.6.26-aufs.patch  linux-sabayon-2.6.26-tuxonice-3.0-rc7.patch.bz2
# cd genpatches
# ls
2600_evdev-compat-ioctl-force-feedback.patch  4200_fbcondecor-0.9.4.patch  4300_squashfs-3.3.patch
#

Yes, the 2.6.26 ebuild and associated files are there, all right. So let's merge it then:

Code: Select all

# emerge -1v =linux-sabayon-2.6.26

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy "=sys-kernel/linux-sabayon-2.6.26".

#

So what on Earth is going on?

[eMxyzptlk]

First let's try to isolate the problem, so install eix, and search with it

Code: Select all

# emerge -av app-portage/eix
# echo '*' > /etc/eix-sync.conf
# update-eix
# eix sys-kernel/linux-sabayon


does it work?

If yes:
- emerge -s shouldn't be affected by masked packages, but no harm checking it, check if you have masked the package in /etc/portage/package.mask if yes, unmask it and try again.. works => Gentoo bug...

if The above didn't work, neither did the eix one, oh well we'll get to that...

[Fitzcarraldo]

I already have eix installed, but purposely did not use it in my previous post to avoid questions about whether I had done an "update-eix" (I had). In any event, I had already ascertained eix does not show linux-sabayon-2.6.26 either:

Code: Select all

# eix linux-sabayon
[I] sys-kernel/linux-sabayon [1]
     Available versions:
        (2.6.23)        2.6.23-r1
        (2.6.24)        (~)2.6.24
        (-r0/}) (~)2.6.25-r1
        {dmraid grub no_sources only_sources splash}
     Installed versions:  2.6.25-r1(-r0/})(16:42:41 30/06/08)(symlink -build -dmraid -grub -no_sources -only_sources -splash)
     Homepage:            http://www.sabayonlinux.org
     Description:         Official Sabayon Linux kernel images and sources

* sys-kernel/linux-sabayon-modules [1]
     Available versions:  2.6.23-r1
     Homepage:            http://www.sabayonlinux.org/
     Description:         Sabayon Linux kernel modules meta package

[1] "sabayon" /usr/portage/local/layman/sabayon

Found 2 matches.

Anyway, I created the file /etc/eix-sync.conf as you suggested, but it made no difference:

Code: Select all

# echo '*' > /etc/eix-sync.conf
# update-eix
Reading Portage settings ..
Building database (/var/cache/eix) ..
[0] "gentoo" /usr/portage/ (cache: metadata)
     Reading 100%
[1] "sabayon" /usr/portage/local/layman/sabayon (cache: parse)
     Reading 100%
Applying masks ..
Calculating hash tables ..
Writing database file /var/cache/eix ..
Database contains 13101 packages in 151 categories.
# eix linux-sabayon
[I] sys-kernel/linux-sabayon [1]
     Available versions:
        (2.6.23)        2.6.23-r1
        (2.6.24)        (~)2.6.24
        (-r0/}) (~)2.6.25-r1
        {dmraid grub no_sources only_sources splash}
     Installed versions:  2.6.25-r1(-r0/})(16:42:41 30/06/08)(symlink -build -dmraid -grub -no_sources -only_sources -splash)
     Homepage:            http://www.sabayonlinux.org
     Description:         Official Sabayon Linux kernel images and sources

* sys-kernel/linux-sabayon-modules [1]
     Available versions:  2.6.23-r1
     Homepage:            http://www.sabayonlinux.org/
     Description:         Sabayon Linux kernel modules meta package

[1] "sabayon" /usr/portage/local/layman/sabayon

Found 2 matches.

Just for good measure, as I had eix-0.13.1 installed, I upgraded to the latest version in portage (0.13.2) but that makes no difference: no linux-sabayon-2.6.26 reported.

(Also, linux-sabayon is not masked in /etc/portage/package.mask)

[wolfden]

do you have entropy installed and updated?

does equo find it?

[Fitzcarraldo]

Never used Entropy/Equo/Spritz and don't want to on this machine. I've always done the regular "emerge --sync", "emerge portage" when "emerge --sync" tells me to, and then "layman -S". I've never touched anything to do with Entropy, Equo or Spritz.

[Fitzcarraldo]

OK, I've found the cause of the problem. Looking through the Gentoo Bugzilla I came across the following bug report: app-portage/eix-0.13.1 looks for layman repos make.conf in wrong place.

If you look at the poster's description of the problem, he writes "I have added sunrise and java-overlay repos, they were added to /usr/local/portage/layman (instead of /usr/portage/local/layman...) by "layman -a repository", my /etc/make.conf was changed to the new location of make.conf, but eix is still looking for old".

Forget eix, that's a red herring. So it appears that the Gentoo devs have changed the default location for overlays on your HDD. The way the above-mentioned poster has written it, it could be inferred that his /etc/make.conf was automatically changed to reflect the new location. But it could equally be taken to mean that he changed it himself. Why do people use the passive voice, I ask myself. Anyway, my /etc/make.conf was most certainly not changed automatically by any merges of portage or any other package that I performed (and I'm up-to-date on everything). So I edited my /etc/make.conf as follows:

Code: Select all

# source /usr/portage/local/layman/make.conf
# Above line commented out by me on 01.08.08 and the following line added (I noticed in Gentoo Bugzilla Bug 230788 that directory has changed):
source /usr/local/portage/layman/make.conf

and then I did another "layman -d sabayon", followed by another "layman -a sabayon", and now portage sees linux-sabayon-2.6.26:

Code: Select all

# emerge -s linux-sabayon
Searching...
[ Results for search key : linux-sabayon ]
[ Applications found : 2 ]

*  sys-kernel/linux-sabayon
      Latest version available: 2.6.26
      Latest version installed: 2.6.25-r1
      Size of files: 48,360 kB
      Homepage:      http://www.sabayonlinux.org
      Description:   Official Sabayon Linux kernel images and sources
      License:       GPL-2

*  sys-kernel/linux-sabayon-modules
      Latest version available: 2.6.23-r1
      Latest version installed: [ Not Installed ]
      Size of files: 0 kB
      Homepage:      http://www.sabayonlinux.org/
      Description:   Sabayon Linux kernel modules meta package
      License:       GPL-2

Now, if /etc/make.conf was supposed to be updated automatically but wasn't, my question is: Why not? And if it was not supposed to be updated automatically and the Gentoo devs expected the user to edit it manually, then I think that is bad practice. Either way, yet again I'm not impressed with the Gentoo QA.

For those of you who use Portage (rather than Entropy), what does your /etc/make.conf contain? The new "source /usr/local/portage/layman/make.conf" or the old "source /usr/portage/local/layman/make.conf"?

[wolfden]

OMG, I should have known that. When I set up my directory structure for my local overlay I ran into that issue. I had to edit my make.conf to point to local overlay to get things working. I had ran into a thread on the gentoo forum as I was confused and a guy was having same issues and he pointed out the directory location differeneces and sure enough that was the deal.

At least now we are aware of this and it is effecting others.

[dunsurfin]

For those of you who use Portage (rather than Entropy), what does your /etc/make.conf contain? The new "source /usr/local/portage/layman/make.conf" or the old "source /usr/portage/local/layman/make.conf"?

I mainly use Entropy but occasionally use Portage and checked out of interest. Mine is definitely the old but then that is where my source is. I just did an emerge --sync, emerge portage and Layman -S and the source is still in the same place.