Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 704854 - app-portage/esearch: eupdatedb brakes on a melpa ebuild
Summary: app-portage/esearch: eupdatedb brakes on a melpa ebuild
Status: RESOLVED UPSTREAM
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage Tools Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-06 08:19 UTC by CaptainBlood
Modified: 2020-02-22 15:13 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description CaptainBlood 2020-01-06 08:19:06 UTC
eupdatedb
 * indexing: 21418 ebuilds to goTraceback (most recent call last):
  File "/usr/lib/python-exec/python3.6/eupdatedb", line 5, in <module>
    main()
  File "/usr/lib64/python3.6/site-packages/esearch/update.py", line 268, in main
    success = updatedb(config)
  File "/usr/lib64/python3.6/site-packages/esearch/update.py", line 183, in updatedb
    pkgv = portage.portdb.xmatch("bestmatch-visible", pkg)
  File "/usr/lib64/python3.6/site-packages/portage/dbapi/porttree.py", line 1093, in xmatch
    self.async_xmatch(level, origdep, loop=loop))
  File "/usr/lib64/python3.6/site-packages/portage/util/_eventloop/EventLoop.py", line 833, in run_until_complete
    return future.result()
  File "/usr/lib64/python3.6/site-packages/portage/util/futures/compat_coroutine.py", line 107, in _next
    future = next(self._generator)
  File "/usr/lib64/python3.6/site-packages/portage/dbapi/porttree.py", line 1178, in async_xmatch
    aux_keys, myrepo=cpv.repo, loop=loop))))
  File "/usr/lib64/python3.6/site-packages/portage/dbapi/porttree.py", line 702, in async_aux_get
    proc.start()
  File "/usr/lib64/python3.6/site-packages/_emerge/AsynchronousTask.py", line 30, in start
    self._start()
  File "/usr/lib64/python3.6/site-packages/_emerge/EbuildMetadataPhase.py", line 117, in _start
    fd_pipes=fd_pipes, returnpid=True)
  File "/usr/lib64/python3.6/site-packages/portage/package/ebuild/doebuild.py", line 821, in doebuild
    use_cache, mydbapi)
  File "/usr/lib64/python3.6/site-packages/portage/package/ebuild/doebuild.py", line 288, in doebuild_environment
    _("Invalid ebuild path: '%s'") % myebuild)
portage.exception.IncorrectParameter: Invalid ebuild path: '/var/lib/layman/melpa/app-emacs/lsp-elixir.el/lsp-elixir.el-20190105.2059.ebuild'
--------------------------------------------------------------------------------
ls /var/lib/layman/melpa/app-emacs/lsp-elixir.el/lsp-elixir.el-20190105.2059.ebuild
/var/lib/layman/melpa/app-emacs/lsp-elixir.el/lsp-elixir.el-20190105.2059.ebuild


Reproducible: Always
Comment 1 CaptainBlood 2020-01-06 08:39:01 UTC
For those such as me, who are uncortable reading tracestack:
eupdatedb calls equery which triggers the error
 -------------------------------------------------------------------------------
equery w -e lsp-elixir.el-20190105.2059
--- Invalid atom in /etc/portage/package.keywords/04-stage4-stapler-monolithic.conf: dev-python/stapler-9999
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.6/equery", line 38, in <module>
    equery.main(sys.argv)
  File "/usr/lib64/python3.6/site-packages/gentoolkit/equery/__init__.py", line 356, in main
    loaded_module.main(module_args)
  File "/usr/lib64/python3.6/site-packages/gentoolkit/equery/which.py", line 111, in main
    in_installed=False
  File "/usr/lib64/python3.6/site-packages/gentoolkit/query.py", line 197, in find
    matches = portage.db[portage.root]["porttree"].dbapi.match(self.query)
  File "/usr/lib64/python3.6/site-packages/portage/dbapi/porttree.py", line 1225, in match
    return self.xmatch("match-visible", mydep)
  File "/usr/lib64/python3.6/site-packages/portage/dbapi/porttree.py", line 1093, in xmatch
    self.async_xmatch(level, origdep, loop=loop))
  File "/usr/lib64/python3.6/site-packages/portage/util/_eventloop/EventLoop.py", line 833, in run_until_complete
    return future.result()
  File "/usr/lib64/python3.6/site-packages/portage/util/futures/compat_coroutine.py", line 107, in _next
    future = next(self._generator)
  File "/usr/lib64/python3.6/site-packages/portage/dbapi/porttree.py", line 1178, in async_xmatch
    aux_keys, myrepo=cpv.repo, loop=loop))))
  File "/usr/lib64/python3.6/site-packages/portage/dbapi/porttree.py", line 702, in async_aux_get
    proc.start()
  File "/usr/lib64/python3.6/site-packages/_emerge/AsynchronousTask.py", line 30, in start
    self._start()
  File "/usr/lib64/python3.6/site-packages/_emerge/EbuildMetadataPhase.py", line 117, in _start
    fd_pipes=fd_pipes, returnpid=True)
  File "/usr/lib64/python3.6/site-packages/portage/package/ebuild/doebuild.py", line 821, in doebuild
    use_cache, mydbapi)
  File "/usr/lib64/python3.6/site-packages/portage/package/ebuild/doebuild.py", line 288, in doebuild_environment
    _("Invalid ebuild path: '%s'") % myebuild)
portage.exception.IncorrectParameter: Invalid ebuild path: '/var/lib/layman/melpa/app-emacs/lsp-elixir.el/lsp-elixir.el-20190105.2059.ebuild'
Comment 2 CaptainBlood 2020-01-06 10:13:20 UTC
Likely to be a gentoo MELPA integration issue:
github bug report 4 lsp-elixir:
https://github.com/elixir-lsp/lsp-elixir.el/issues/11

Will close this bug as soon as upstream confirm integration issue.
Thks 4 ur attention.
Comment 3 Zac Medico gentoo-dev 2020-01-06 20:12:02 UTC
(In reply to CaptainBlood from comment #0)
>   File
> "/usr/lib64/python3.6/site-packages/portage/package/ebuild/doebuild.py",
> line 288, in doebuild_environment
>     _("Invalid ebuild path: '%s'") % myebuild)
> portage.exception.IncorrectParameter: Invalid ebuild path:
> '/var/lib/layman/melpa/app-emacs/lsp-elixir.el/lsp-elixir.el-20190105.2059.
> ebuild'

It's invalid because you're not allowed to have '.' in package names according to PMS, the only allowed characters are [A-Za-z0-9+_-]:

https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-180003.1.2
Comment 4 CaptainBlood 2020-02-22 15:13:20 UTC
(In reply to CaptainBlood from comment #2)
> Likely to be a gentoo MELPA integration issue:
> github bug report 4 lsp-elixir:
> https://github.com/elixir-lsp/lsp-elixir.el/issues/11
> 
> Will close this bug as soon as upstream confirm integration issue.
> Thks 4 ur attention.

Seems fixed, RESOLVED