how to get a local overlay working

[mauricev]

I want to use the latest version of autossh, which isn't yet in the portage tree. I followed the instructions at https://www.funtoo.org/Local_Overlay, but what are the next steps? Do I recreate the kits directory hierarchy in /var/git/overlay/local-overlay. ( I tried that and it had no effect.) My updated autossh ebuild is not being seen.

[cafaia]

Hi, Mauricev!

After you create the local repository, did you do that:

# ebuild /var/git/overlay/local-overlay/cat/pkg/autossh-version.ebuild digest

I hope this is what is missing.

Best regards!

[mauricev]

Yes, I did that.  But one thing that wasn't not stated in the docs is that path where the packages must reside. I would have never guessed it.

[cafaia]

Hi, Mauricev!

I'm glad to hear that you found the mistake.

Best regards!

[mauricev]

That was a mistake, not the mistake. It still doesn't work.

[palica]

paste output of

tree /var/git/overlay

 

[mauricev]

sudo: tree: command not found

 

[palica]

this is easy to fix (with bit of searching on your part). hint:

[I] app-text/tree [1]
     Available versions:  1.7.0 (~)1.7.0-r1
     Installed versions:  1.7.0-r1(12:16:50 AM 11/22/2017)
     Homepage:            http://mama.indstate.edu/users/ice/tree/
     Description:         Lists directories recursively, and produces an indented listing of files

[1] "text-kit" /var/git/meta-repo/kits/text-kit

 

[mauricev]

/var/git/overlay
└── local-overlay
    ├── COPYRIGHT.txt
    ├── LICENSE.txt
    ├── README.rst
    ├── cat
    │   └── autossh
    │       ├── Manifest
    │       ├── autossh-1.4f.ebuild
    │       └── metadata.xml
    ├── metadata
    │   └── layout.conf
    └── profiles
        └── repo_name

 

[palica]

why don't you simply copy the directory structure from the package already in portage. That means in your case:

 

net-misc/autossh

 

didn't emerge warn you about non-existent category "cat"?

[mauricev]

Ah, the word cat was not meant to be taken literally, but it refers to the category of the package, which, in this case, is net-misc. That fixed it. And, no, there were no warnings from emerge. Thanks!

[palica]

well, there are at least two warnings displayed on my computer, after replicating your setup.

root@sucellus /usr/local/portage/cat/autossh # ebuild autossh-1.4f.ebuild digest

!!! 'cat/autossh' has a category that is not listed in /etc/portage/categories
>>> Creating Manifest for /usr/local/portage/cat/autossh
!!! File b'/var/cache/portage/distfiles/autossh-1.4f.tgz' doesn't exist, can't update Manifest
root@sucellus /usr/local/portage/metadata # cat layout.conf
repo-name = local
thin-manifests = true
sign-manifests = false
profile-formats = portage-2
cache-formats = md5-dict
masters = core-kit
root@sucellus /usr/local/portage/metadata # emerge -pv cat/autossh

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

Calculating dependencies /
!!! 'cat/autossh' has a category that is not listed in /etc/portage/categories
... done!

emerge: there are no ebuilds to satisfy "cat/autossh".

emerge: searching for similar names...
emerge: Maybe you meant net-misc/autossh?

it is just helpful to paste any error or warning message, besides saying "it doesn't work for me ..."

 

[Oleg Vinichenko]

is "cat" literally used in overlay setup. It's not a valid category name for the autossh ebuild. Have to be something like net-misc/autossh
 

[mauricev]

I didn't get those warnings because when I built the digest I gave it the full path and when I attempted to emerge autossh, I just told it emerge -v autossh. I never referenced "cat" itself.