gentoo ~ # layman-updater * Creating layman's repos.conf file * Fatal error: Please run layman-updater, then run layman again * Fatal error(s) - aborting gentoo ~ # I guess there's something wrong with my layman.cfg after the update. I'll attach it to the report. Reproducible: Always
Created attachment 396584 [details] layman config
Removing layman.cfg fixed this.
No, removing your layman.cfg didn't fix it, plus there is nothing wrong with it. I believe what happened is that you did not have any installed overlays, so did not have a /usr/local/portage/layman/installed.xml file. The repos.conf generator tries to load the installed overlay db, then populates the repos.conf/layman.conf with the info. In this case, since there was not an installed.xml, it triggered the upgrade message from the old filename to the new installed.xml filename. Can you please confirm this info from your system? I'll tweak the trigger for that message, to prevent the false start.
No, I had a couple of overlays installed. When updating to 2.3.0 I interactively merged the config file, leaving the old storage dir (/usr/local/portage/layman/) and replacing all the other settings with new values. This didn't work, so I removed the config file, re-emerged layman and re-added all my overlays in the new storage dir (/var/lib/layman). Now it works fine.
Also: in my old layman dir I have overlays.xml, not installed.xml.
This has been fixed in the 9999 version for awhile now.
2.4.1 is out which resolves this issue, therefore, I'm resolving the bug.
