'layman -S' fails with: root@lynx:/root(12)# layman -S * Fetching remote list... * XML DBHandler - ET.ParseError: mismatched tag: line 5627, column 4 * DbBase; error, Failed to read database at "/var/lib/layman/cache_ac494f50f5736be7871962c0dec7b3bb.xml" * Hint: If you manually set db_type. Please reset it and let layman-updater * migrate it. Otherwise layman's database is not initialized, nor populated * with any existing data. * Run the following: "layman-updater -m <db_type>" root@lynx:/root(13)# 'emerge -v1 layman' fails as well with: root@lynx:/root(20)# emerge -v1 layman These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] app-portage/layman-2.4.2-r1::gentoo USE="git mercurial sqlite subversion -bazaar -cvs -darcs -g-sorcery -gpg -squashfs -sync-plugin-portage -test" PYTHON_TARGETS="python2_7 python3_6 -pypy -python3_4 -python3_5" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB >>> Verifying ebuild manifests >>> Running pre-merge checks for app-portage/layman-2.4.2-r1 >>> Emerging (1 of 1) app-portage/layman-2.4.2-r1::gentoo * layman-2.4.2.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking layman-2.4.2.tar.gz to /var/tmp/portage/app-portage/layman-2.4.2-r1/work >>> Source unpacked in /var/tmp/portage/app-portage/layman-2.4.2-r1/work >>> Preparing source in /var/tmp/portage/app-portage/layman-2.4.2-r1/work/layman-2.4.2 ... python3.6 setup.py setup_plugins running setup_plugins * Adjusting to prefix / * layman.cfg ... [ ok ] * config.py ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/app-portage/layman-2.4.2-r1/work/layman-2.4.2 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/app-portage/layman-2.4.2-r1/work/layman-2.4.2 ... * python2_7: running distutils-r1_run_phase distutils-r1_python_compile python2.7 setup.py build : python_wrapper_setup: python2.7 is not supported by python3.6 (PYTHON_COMPAT) * ERROR: app-portage/layman-2.4.2-r1::gentoo failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 124: Called src_compile * environment, line 4408: Called distutils-r1_src_compile * environment, line 1299: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' * environment, line 445: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3877: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3033: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 3031: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' * environment, line 716: Called distutils-r1_run_phase 'distutils-r1_python_compile' * environment, line 1290: Called distutils-r1_python_compile * environment, line 1165: Called esetup.py 'build' * environment, line 1788: Called die * The specific snippet of code: * "${@}" || die "${die_args[@]}"; * * If you need support, post the output of `emerge --info '=app-portage/layman-2.4.2-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=app-portage/layman-2.4.2-r1::gentoo'`. * The complete build log is located at '/var/log/portage/app-portage:layman-2.4.2-r1:20180918-194853.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-portage/layman-2.4.2-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-portage/layman-2.4.2-r1/temp/environment'. * Working directory: '/var/tmp/portage/app-portage/layman-2.4.2-r1/work/layman-2.4.2' * S: '/var/tmp/portage/app-portage/layman-2.4.2-r1/work/layman-2.4.2' >>> Failed to emerge app-portage/layman-2.4.2-r1, Log file: Seems to be similar to https://bugs.gentoo.org/show_bug.cgi?id=666474 and https://bugs.gentoo.org/show_bug.cgi?id=666468
Introduced in: https://gitweb.gentoo.org/data/api.git/commit/?id=ae92c34c4305d194ced04cfe5e12c41af57fd6a6 Fixed in: https://gitweb.gentoo.org/data/api.git/commit/?id=9c06d7a6dbc8a01c1360c3f68855ec94553d24e2
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #1) > Introduced in: > https://gitweb.gentoo.org/data/api.git/commit/ > ?id=ae92c34c4305d194ced04cfe5e12c41af57fd6a6 > > Fixed in: > https://gitweb.gentoo.org/data/api.git/commit/ > ?id=9c06d7a6dbc8a01c1360c3f68855ec94553d24e2 How can I use the patch in https://gitweb.gentoo.org/data/api.git/commit/?id=9c06d7a6dbc8a01c1360c3f68855ec94553d24e2 ? I did not find a file repositories.xml under /var/tmp/portage/app-portage/layman-2.4.2-r1/ .
(In reply to Juergen Rose from comment #2) > (In reply to Arfrever Frehtes Taifersar Arahesis from comment #1) > > Introduced in: > > https://gitweb.gentoo.org/data/api.git/commit/ > > ?id=ae92c34c4305d194ced04cfe5e12c41af57fd6a6 > > > > Fixed in: > > https://gitweb.gentoo.org/data/api.git/commit/ > > ?id=9c06d7a6dbc8a01c1360c3f68855ec94553d24e2 > > How can I use the patch in > https://gitweb.gentoo.org/data/api.git/commit/ > ?id=9c06d7a6dbc8a01c1360c3f68855ec94553d24e2 ? > > I did not find a file repositories.xml under > /var/tmp/portage/app-portage/layman-2.4.2-r1/ . Layman downloads repositories.xml at runtime and caches it at /var/lib/layman/cache_${hash_value}.xml Remove your cache files and it will work as expected.
(In reply to Brian Evans from comment #3) > (In reply to Juergen Rose from comment #2) > > (In reply to Arfrever Frehtes Taifersar Arahesis from comment #1) > > > Introduced in: > > > https://gitweb.gentoo.org/data/api.git/commit/ > > > ?id=ae92c34c4305d194ced04cfe5e12c41af57fd6a6 > > > > > > Fixed in: > > > https://gitweb.gentoo.org/data/api.git/commit/ > > > ?id=9c06d7a6dbc8a01c1360c3f68855ec94553d24e2 > > > > How can I use the patch in > > https://gitweb.gentoo.org/data/api.git/commit/ > > ?id=9c06d7a6dbc8a01c1360c3f68855ec94553d24e2 ? > > > > I did not find a file repositories.xml under > > /var/tmp/portage/app-portage/layman-2.4.2-r1/ . > > Layman downloads repositories.xml at runtime and caches it at > /var/lib/layman/cache_${hash_value}.xml > > Remove your cache files and it will work as expected. Thanks, worked.
