Summary: | sys-apps/portage-9999 fails with unsupported value: 'laymansync' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Helmut Jarausch <jarausch> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | atoth, jstein, matthew |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Helmut Jarausch
2018-08-31 10:32:06 UTC
Sorry, I was on holiday when you submitted this bug. I missed seeing it till now. Please ensure layman is emerge with the "sync-plugin-portage" use flag. That use flag controls the installation of the laymansync plugin. The other possibility is that portage was re-emerged and is now using a python version that layman was not installed to. Then portage will not find the laymansync module installed to that python version. I have this message with the latest unstable portage-2.3.78-r2, although I've emerged layman with the suggested use flag. Layman -S works as it should. (In reply to Brian Dolbec from comment #1) > Sorry, I was on holiday when you submitted this bug. I missed seeing it > till now. > > Please ensure layman is emerge with the "sync-plugin-portage" use flag. > That use flag controls the installation of the laymansync plugin. > > The other possibility is that portage was re-emerged and is now using a > python version that layman was not installed to. Then portage will not find > the laymansync module installed to that python version. Started seeing this problem on ~amd64 recently, despite having previously built layman with the required flag. So, going with the second suggestion, I re-installed both portage and layman, initially without resolving the problem. It was only when the PYTHON_TARGETS were exactly aligned were things fixed; i.e. it was necessary to build portage without python-3.8 support as this target is not (yet) supported by layman. Filing this in case it helps somebody, else. Merry Christmas! I believe the problem is due to portage being updated and installed to an new python version that layman has not yet been re-installed to. I think I will look into having layman rebuilt when portage is updated. That will likely prevent the problem. I don't think this is something we can fix in portage. |