I've installed Gentoo prefix using this manual (https://wiki.gentoo.org/wiki/Project:Android/tarball) on arm64 LineageOS, started it, synced emerge and tried to upgrade emerge. This is the result: localhost / # emerge -av1 portage * IMPORTANT: 6 news items need reading for repository 'gentoo'. * Use eselect news read to view new items. These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy ">=dev-lang/python-3.6.10:3.6[bzip2(+),threads(+)]" have been masked. !!! One of the following masked packages is required to complete your request: - dev-lang/python-3.9.0_alpha5::gentoo (masked by: EAPI 7) - dev-lang/python-3.9.0_alpha4::gentoo (masked by: EAPI 7) - dev-lang/python-3.8.2-r1::gentoo (masked by: EAPI 7) - dev-lang/python-3.7.7-r1::gentoo (masked by: EAPI 7) - dev-lang/python-3.7.6::gentoo (masked by: EAPI 7) - dev-lang/python-3.6.10-r1::gentoo (masked by: EAPI 7) The current version of portage supports EAPI '6'. You must upgrade to a newer version of portage before EAPI masked packages can be installed. (dependency required by "sys-apps/portage-9999::gentoo[python_targets_python3_6]" [ebuild]) (dependency required by "portage" [argument]) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. I think, this shouldn't happen and I don't know, how to solve it. Reproducible: Always
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
The bug is not only on one system. Every new instance of Gentoo prefix on Android created using the only available arm64 tarball and the manual will have same problem. So I think the problem is specific enough: It is not possible to install the arm64 Android Gentoo...blocker bug. It should be easy to confirm if you have rooted arm64 Android phone. Just try to emerge --sync and run emerge -aUuD @world. (In reply to Jonas Stein from comment #1) > It is sad to read that you have problems with the software. The situation > seems to be a bit more complicate and requires some analysis. > We can not help you efficiently via bug tracker. The bug tracker aims rather > on specific problems in .ebuilds and less on individual systems. > > I have had very good experience on the gentoo IRC [1] with questions like > this. Of course there are also forums and mailing lists [2,3]. > I hope you understand, that I will close the bug here therefore and wish you > good luck on one of the mentioned channels [4]. > Please reopen the ticket in order to provide an indication for an specific > error in an ebuild or any gentoo related product. > > [1] https://www.gentoo.org/get-involved/irc-channels/ > [2] https://forums.gentoo.org/ > [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html > [4] https://www.gentoo.org/support/
please do not make fullquotes. I did not say that there is no such bug. However we have ~30k bug reports/year and we want to get your bug fixed. Chances are best, if you elaborate a bit more on the report. Improve the summary, provide more details. We help you on the IRC chat, if you want. I suggest to open a new ticket with our help based on this one. No developer wants to scroll 5 pages down and ask for missing details.
