Created attachment 489118 [details] emerge --info layman I have layman built with sync-plugin-portage, but env-update prints me a dozen of messages like this: !!! Repository 'deter' has sync-type attribute set to unsupported value: 'laymansync' !!! Installed sync-types are: '['cvs', 'git', 'rsync', 'svn', 'webrsync']'
Similar issue with science overlay. I think main issue is that it is unclear how to address this. Maybe error message could clarify that?
So this module is only installed for the python targets layman supports. Currently this does _NOT_ include python 3.7 and this is my default python target. If you run into this make sure to either 1) switch to a python target that is supported by layman with eselect python 2) modify the ebuild and update PYTHON_COMPAT to include 3_7 for the maintainer, please add python 3.7, it works fine for me.
app-portage/layman-2.4.2-r2 now supports Python 3.7 Unfortunately it is no longer possible to add any overlay. They all quit with: -------- * CLI: Errors occurred processing action add * Exception caught installing repository "kde": * unterminated character set at position 1 -------- So it seems layman isn't fully compatible with Python 3.7, yet?
Ok, what about now?
Same story when python3.8 is the preferred system-wide choice. To avoid having to switch the default python interpreter version system-wide (in my case from 3.8 down to 3.6), I ended up overriding the version just for portage with a shell alias: alias emerge='EPYTHON=python3.6 emerge' alias ebuild='EPYTHON=python3.6 ebuild' May add the above to ~/.bashrc for automatic setup upon shell startup.
layman for Py 3.7,8 is broken. I have a fix and will be releasing 2.4.3 soon. As for the original problem, I think what has happened is that portage was updated and installed to a new version of python that layman was not re-installed to as well. That would cause emerge to puke the error you are reporting. If you check. a way to confirm this is to eselect python to a version layman is installed to. emerge should not complain then.
It sounds like it's easier to re-install layman than change python and maybe break other packages.
It may be possible for portage use changes to python_targets to trigger rebuilds for tools dep'ing on it. That or add code to detect the imbalance and report it on the commandline
layman-2.4.3 is released with python 3.7 and 3.8 properly supported and working
I can confirm the same behavior today after updating to the latest stable portage. With the re-install suggestion above I was able to get it to working again. Thanks! I wonder if there is a way to trigger an automatic layman reinstall when a new version of portage is installed?
Hello , I have installed , app-portage/layman version 2.4.3 and with eselect python 3.9 , all works well, but ,I belive that soon we should move to pyhton 3.10 , then , when I change to eselect python 3.10 , all the emerge --sync , shows problems with layman overlays sync pentoo@pentoo ~ $ sudo emerge --sync !!! Repository 'sattvik' has sync-type attribute set to unsupported value: 'laymansync' !!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']' !!! Repository 'stefantalpalaru' has sync-type attribute set to unsupported value: 'laymansync' !!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', 'webrsync']' >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... * Using keys from /usr/share/openpgp-keys/gentoo-release.asc * Refreshing keys via WKD ... [ ok ] >>> Starting rsync with rsync://89.238.71.6/gentoo-portage... >>> Checking server timestamp ... Welcome to turnstone.gentoo.org / rsync.gentoo.org Thanks,
(In reply to ea3hqj from comment #11) > Hello , > I have installed , app-portage/layman version 2.4.3 > and with eselect python 3.9 , all works well, > > but ,I belive that soon we should move to pyhton 3.10 , then , when I > change to eselect python 3.10 , all the emerge --sync , shows problems with > layman overlays sync > > pentoo@pentoo ~ $ sudo emerge --sync > !!! Repository 'sattvik' has sync-type attribute set to unsupported value: > 'laymansync' > !!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', > 'webrsync']' > !!! Repository 'stefantalpalaru' has sync-type attribute set to unsupported > value: 'laymansync' > !!! Installed sync-types are: '['cvs', 'git', 'mercurial', 'rsync', 'svn', > 'webrsync']' > >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... > * Using keys from /usr/share/openpgp-keys/gentoo-release.asc > * Refreshing keys via WKD ... [ > ok ] > >>> Starting rsync with rsync://89.238.71.6/gentoo-portage... > >>> Checking server timestamp ... > Welcome to turnstone.gentoo.org / rsync.gentoo.org > > Thanks, Re-emerge layman with the SAME PYTHON_TARGETS setting as portage. Alternatively set it to use portage's git for sync.
Thanks, current layman use flags are already for Python 3.9 and 3.10 * Found these USE flags for app-portage/layman-2.4.3: U I - - cvs : Support dev-vcs/cvs based overlays + + git : Support dev-vcs/git based overlays + + gpg : Support app-crypt/gnupg signed overlays lists and manifests + + mercurial : Support dev-vcs/mercurial based overlays + - python_targets_python3_10 : Build with Python 3.10 - - python_targets_python3_8 : Build with Python 3.8 + + python_targets_python3_9 : Build with Python 3.9 + + sqlite : Add support for sqlite - embedded sql database - - squashfs : Support mounting squashfs image overlays locally read-only + + subversion : Support dev-vcs/subversion based overlays + + sync-plugin-portage : Install the sys-apps/portage sync module - - test : Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently) Then maybe , re-emerge will not work. But I can try ... When you said , re-emerge , with the SAME PYTHON_TARGETS setting as portage. what you mean ? emerge layman:3.10 ? Now my current portage is , * Found these USE flags for sys-apps/portage-3.0.30-r3: U I + + python_targets_python3_10 : Build with Python 3.10 - - python_targets_python3_8 : Build with Python 3.8 + + python_targets_python3_9 : Build with Python 3.9 + + rsync-verify : Enable full-tree cryptographic verification of Gentoo Maybe i need to try to re-sync those overlays , or delete them and add again ???
(In reply to ea3hqj from comment #13) > Thanks, > current layman use flags are already for Python 3.9 and 3.10 > * Found these USE flags for app-portage/layman-2.4.3: > U I > + - python_targets_python3_10 : Build with Python 3.10 > - - python_targets_python3_8 : Build with Python 3.8 > + + python_targets_python3_9 : Build with Python 3.9 > > Then maybe , re-emerge will not work. But I can try ... > When you said , re-emerge , with the SAME PYTHON_TARGETS setting as portage. > what you mean ? emerge layman:3.10 ? > Now my current portage is , > * Found these USE flags for sys-apps/portage-3.0.30-r3: > U I > + + python_targets_python3_10 : Build with Python 3.10 > - - python_targets_python3_8 : Build with Python 3.8 > + + python_targets_python3_9 : Build with Python 3.9 > + + rsync-verify : Enable full-tree cryptographic verification > of Gentoo > > Maybe i need to try to re-sync those overlays , or delete them and add again > ??? As you can see, you have portage (emerge) installed to (I column) 3.9 and 3.10, but layman is only installed to 3.9. So if you switched to python 3.10, then it won't have the layman sync module installed in portage. It is best to set PYTHON_TARGETS in make.conf, and do # emerge -uvNDa --changed-use --changed-deps @world as a normal routine. That will help keep all programs installed synced to each other (for cases like portage and layman. No, re-installing the overlays will not help. Re-emerging layman with the same PYTHON_TARGET setting as portage will fix it.
Great thanks for your help ! Before reading your feedback , I switched to python 3.10 , and send that command sudo emerge layman, And after that , >>> Verifying ebuild manifests >>> Running pre-merge checks for app-portage/layman-2.4.3 >>> Emerging (1 of 2) dev-python/ssl-fetch-0.4-r1::gentoo >>> Installing (1 of 2) dev-python/ssl-fetch-0.4-r1::gentoo >>> Emerging (2 of 2) app-portage/layman-2.4.3::gentoo >>> Installing (2 of 2) app-portage/layman-2.4.3::gentoo >>> Jobs: 2 of 2 complete Load avg: 2.22, 3.66, 2.95 Now the "emerge --sync" , or "emerge pentoo-updater" it is not showing the previous errors ! It seems that now is really updating again ...I will leave all tonight to see , if update many packages or not ... Anyway still sometimes it shows a red error message, but it does not stop the update process. ------------------------------- Error during set creation: Could not import 'smartliverebuild.sets.SmartLiveRebuildSet' for section 'smart-live-rebuild' ------------------------------ So at the moment , I will not interrupt the pentoo-updater process,hopefully now it is updating well with python 3.10 . Thank you very much , let's see !!!
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=805fe7c0495e1bf3a34d518041e466258944b82b commit 805fe7c0495e1bf3a34d518041e466258944b82b Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2023-06-22 13:15:09 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2023-06-22 13:15:09 +0000 app-portage/layman: treeclean Closes: https://bugs.gentoo.org/761199 Closes: https://bugs.gentoo.org/609720 Closes: https://bugs.gentoo.org/627930 Closes: https://bugs.gentoo.org/700742 Closes: https://bugs.gentoo.org/649766 Closes: https://bugs.gentoo.org/681144 Closes: https://bugs.gentoo.org/648374 Closes: https://bugs.gentoo.org/545568 Closes: https://bugs.gentoo.org/581890 Closes: https://bugs.gentoo.org/539336 Closes: https://bugs.gentoo.org/590132 Closes: https://bugs.gentoo.org/574190 Closes: https://bugs.gentoo.org/578992 Closes: https://bugs.gentoo.org/540012 Closes: https://bugs.gentoo.org/412883 Closes: https://bugs.gentoo.org/443880 Closes: https://bugs.gentoo.org/480884 Closes: https://bugs.gentoo.org/567386 Closes: https://bugs.gentoo.org/454604 Closes: https://bugs.gentoo.org/567384 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> app-portage/layman/Manifest | 1 - app-portage/layman/layman-2.4.3.ebuild | 100 --------------------------------- app-portage/layman/layman-9999.ebuild | 100 --------------------------------- app-portage/layman/metadata.xml | 24 -------- profiles/package.mask | 5 -- 5 files changed, 230 deletions(-)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=abfaed0b3460e638410c0fd74783f8d292d63afc commit abfaed0b3460e638410c0fd74783f8d292d63afc Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2023-09-08 00:41:10 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2023-09-08 00:42:07 +0000 app-portage/layman: treeclan Closes: https://bugs.gentoo.org/761199 Closes: https://bugs.gentoo.org/609720 Closes: https://bugs.gentoo.org/627930 Closes: https://bugs.gentoo.org/700742 Closes: https://bugs.gentoo.org/649766 Closes: https://bugs.gentoo.org/681144 Closes: https://bugs.gentoo.org/648374 Closes: https://bugs.gentoo.org/545568 Closes: https://bugs.gentoo.org/581890 Closes: https://bugs.gentoo.org/539336 Closes: https://bugs.gentoo.org/590132 Closes: https://bugs.gentoo.org/574190 Closes: https://bugs.gentoo.org/578992 Closes: https://bugs.gentoo.org/540012 Closes: https://bugs.gentoo.org/412883 Closes: https://bugs.gentoo.org/443880 Closes: https://bugs.gentoo.org/480884 Closes: https://bugs.gentoo.org/567386 Closes: https://bugs.gentoo.org/454604 Closes: https://bugs.gentoo.org/567384 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> app-portage/layman/Manifest | 1 - app-portage/layman/layman-2.4.3.ebuild | 100 --------------------------------- app-portage/layman/layman-9999.ebuild | 100 --------------------------------- app-portage/layman/metadata.xml | 24 -------- profiles/package.mask | 5 -- 5 files changed, 230 deletions(-)
