Hi, first my layman.cfg have set: repos_conf : /etc/portage/repos.conf/layman.conf conf_type : repos.conf auto_sync : Yes bit when add some overlay the file layman.conf show off the option like: [gentoo-zh] priority = 50 location = /var/lib/layman/gentoo-zh layman-type = git auto-sync = No Thx
Created attachment 410826 [details] emerge --info
Ok, just to confirm, auto_sync was set to yes, before you added the overlay? and if you run "layman-updater -R", is the new file correct? or still set to no?
Hi, when i add the overlay auto_sync was set to Yes, but for some reason the file show no. Running layman-updater -R it seems fix the problem but for some reason this its likes random, at the beginning layman add incorrectly the auto_sync value but next time it set correctly, and other times error again, i try adding and removing the same overlay but i don't have any conclusion, some times works and other not. i'll try a cleaning layman and readding overlays to test it...
thank you, at least we know it is intermittent now, so we will have to look for that type of possibility in the code...
Hi, i try reproduce the error with a clean installation of layman (unmerging and removing the folders) but i can't reproduce it. I remeber this happend before, with specify clear systems its more probable, when i install a system the feature don't works correctly (the random problems), but in a while or may be with change of something start working fine. The same with this bug: https://bugs.gentoo.org/show_bug.cgi?id=559284
I have just installed layman 2.3.0 upgrading from an older 2.0.0. At the same time I have migrated to repos.conf so after installation I have executed "layman-updater -R". In the layman.cfg I have auto_sync set to Yes but all the overlays in repos.conf/layman.conf have auto_sync set to No. The same happens when adding a new overlay, auto_sync will be always set to No. If I manually change auto_sync to Yes in repos.conf/layman.conf then "layman-updater -R" resets to No
I have just noticed that I was missing the USE=sync-plugin-portage. When layman is installed with the above mentioned useflag then the repos.conf/layman.conf file is updated correctly. So the behaviour seems correct, i.e. without the sync-plugin-portage module layman-updater must disable the auto_sync so it correctly sets it to No.
mm, this is very confusing, the layman doc says: sync-plugin-portage: Install the sys-apps/portage sync module i at least interpret like if the use is enabled layman can be sync via emaint, but i don't expect change in that way the conf file, because the expected is the configuration of repos.conf go with the conf of layman... may be some way is specify in the doc this things.
(In reply to Lagu from comment #8) > i at least interpret like if the use is enabled layman can be sync via > emaint, but i don't expect change in that way the conf file, because the > expected is the configuration of repos.conf go with the conf of layman... layman indeed manages repos.conf/layman.conf, then you can choose if the sync is done by portage during "emerge --sync" (auto_sync set to Yes) or separately by layman with "layman -S" (auto_sync set to No). Everything works as expected but I was missing the useflag sync-plugin-portage for layman so the syncing done by emerge or emaint was not working
okis thx, a little dudes its posible add to the doc this info? and, following https://wiki.gentoo.org/wiki/Layman it specify in >=layman-2.3.0 comes with repos.conf by default, why sync-plugin-portage don't is enabled by default?
As portage > 2.2.16 is stable on all archs and given the fact that PORTAGE_OVERLAY is considered obsolete (i.e. repos.conf is the default way to manage overlays), it'd make sense to change the layman ebuild with: --- /usr/portage/app-portage/layman/layman-2.3.0.ebuild 2015-08-09 22:34:50.000000000 +0200 +++ /usr/portage/app-portage/layman/layman-2.3.0.ebuild.new 2015-10-19 10:17:59.000000000 +0200 @@ -16,7 +16,7 @@ LICENSE="GPL-2" SLOT="0" KEYWORDS="~amd64 ~arm ~hppa ~mips ~ppc ~ppc64 ~s390 ~x86" -IUSE="bazaar cvs darcs +git gpg g-sorcery mercurial squashfs subversion sync-plugin-portage test" +IUSE="bazaar cvs darcs +git gpg g-sorcery mercurial squashfs subversion +sync-plugin-portage test" DEPEND="test? ( dev-vcs/subversion ) >=dev-python/ssl-fetch-0.2[${PYTHON_USEDEP}]
*** Bug 559284 has been marked as a duplicate of this bug. ***
Force enabling the sync plug-in would directly contradict the point of the USE flag. Some individuals might not want it installed by default. Who? Dunno. But some might not want it. Either way, thank you all for reporting the bug and assisting in resolving it as well. I'm going to go ahead and mark this as resolved.
