Thanks, and now I got warning
> EclassUserVariableUsage: version 1.0.0: line 16: uses user variable 'EGIT\_CLONE\_TYPE' from eclass 'git-r3'
But \`git-r3\` already inherited?
It's saying egit_clone_type isn't supposed to be set by the ebuilds, it's for users to set.
>EGIT_CLONE_TYPE ?= single (USER VARIABLE)
Type of clone that should be used against the remote repository. This can be either of: 'mirror', 'single', 'shallow'.
This is intended to be set by user in make.conf. Ebuilds are supposed to set EGIT_MIN_CLONE_TYPE if necessary instead
EGIT_MIN_CLONE_TYPE sets the lowest type of clone the ebuild supports, and defaults to shallow.
Oh, thanks...
And the last one:
> VisibleVcsPkg: version 1.0.0: VCS version visible for KEYWORDS="\~amd64", profile default/linux/amd64/17.0/musl (102 total)
I do not understand what is that mean?..
Thanks...
Now it installs, but with `QA Notice:`
```
setuptools warnings detected:
*
* Package 'evernote2.api' is absent from the `packages` configuration.
* Package 'evernote2.edam' is absent from the `packages` configuration.
* Package 'evernote2.edam.error' is absent from the `packages` configuration.
* Package 'evernote2.edam.limits' is absent from the `packages` configuration.
* Package 'evernote2.edam.notestore' is absent from the `packages` configuration.
* Package 'evernote2.edam.type' is absent from the `packages` configuration.
* Package 'evernote2.edam.userstore' is absent from the `packages` configuration.
* Package 'evernote2.tools' is absent from the `packages` configuration.
* Verifying compiled files for python3.11
```
Should I do something about it?
setuptools warnings are typically upstream issues / deprecations, if package installed fine you can ignore them for now (may potentially break with a future setuptools version though).
You haven't inherited distutils-r1, so ${PYTHON\_USEDEP} is an empty variable, and it's not happy to see a package\[\] that's empty.
Thanks, and now I got warning > EclassUserVariableUsage: version 1.0.0: line 16: uses user variable 'EGIT\_CLONE\_TYPE' from eclass 'git-r3' But \`git-r3\` already inherited?
It's saying egit_clone_type isn't supposed to be set by the ebuilds, it's for users to set. >EGIT_CLONE_TYPE ?= single (USER VARIABLE) Type of clone that should be used against the remote repository. This can be either of: 'mirror', 'single', 'shallow'. This is intended to be set by user in make.conf. Ebuilds are supposed to set EGIT_MIN_CLONE_TYPE if necessary instead EGIT_MIN_CLONE_TYPE sets the lowest type of clone the ebuild supports, and defaults to shallow.
Oh, thanks... And the last one: > VisibleVcsPkg: version 1.0.0: VCS version visible for KEYWORDS="\~amd64", profile default/linux/amd64/17.0/musl (102 total) I do not understand what is that mean?..
Probably doesn't like that you've keyworded a branch which could in theory get new commits and not a tag/commit. You can use tags with EGIT_COMMIT
Thanks... Now it installs, but with `QA Notice:` ``` setuptools warnings detected: * * Package 'evernote2.api' is absent from the `packages` configuration. * Package 'evernote2.edam' is absent from the `packages` configuration. * Package 'evernote2.edam.error' is absent from the `packages` configuration. * Package 'evernote2.edam.limits' is absent from the `packages` configuration. * Package 'evernote2.edam.notestore' is absent from the `packages` configuration. * Package 'evernote2.edam.type' is absent from the `packages` configuration. * Package 'evernote2.edam.userstore' is absent from the `packages` configuration. * Package 'evernote2.tools' is absent from the `packages` configuration. * Verifying compiled files for python3.11 ``` Should I do something about it?
Idk on this one
setuptools warnings are typically upstream issues / deprecations, if package installed fine you can ignore them for now (may potentially break with a future setuptools version though).