>>> Install android-studio-3.2.0.26.181.5014246 into /var/tmp/portage/dev-util/android-studio-3.2.0.26.181.5014246/image/ category dev-util chmod: cannot access '/var/tmp/portage/dev-util/android-studio-3.2.0.26.181.5014246/image/opt/android-studio/bin/*.py': No such file or directory chmod: cannot access '/var/tmp/portage/dev-util/android-studio-3.2.0.26.181.5014246/image/opt/android-studio/bin/*.sh': No such file or directory * ERROR: dev-util/android-studio-3.2.0.26.181.5014246::gentoo failed (install phase): * fperms failed * * If you need support, post the output of `emerge --info '=dev-util/android-studio-3.2.0.26.181.5014246::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-util/android-studio-3.2.0.26.181.5014246::gentoo'`. * The complete build log is located at '/var/log/portage/dev-util:android-studio-3.2.0.26.181.5014246:20181025-174430.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-util/android-studio-3.2.0.26.181.5014246/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-util/android-studio-3.2.0.26.181.5014246/temp/environment'. * Working directory: '/var/tmp/portage/dev-util/android-studio-3.2.0.26.181.5014246/work/android-studio' * S: '/var/tmp/portage/dev-util/android-studio-3.2.0.26.181.5014246/work/android-studio' !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="" JAVA_HOME="" JAVACFLAGS="" COMPILER="" and of course, the output of emerge --info =android-studio-3.2.0.26.181.5014246
# java-config --list-available-vms The following VMs are available for generation-2: 1) IcedTea JDK 3.9.0 [icedtea-bin-8] *) Oracle JDK 1.8.0.192 [oracle-jdk-bin-1.8]
Created attachment 553026 [details] emerge info
Interesting; it works for me with icedtea-bin-8 java installed. I wonder if it would work if the default java is set to that, rather than the oracle java.
It might be worth noting as well that the newest version of android-studio is reported to be 3.2.1 as of this writing. Yet, the latest version available via the ebuild is 3.2.0.
Getting same error. A question was asked about what happens with icedtea-bin-8, which is my setting: # java-config --list-available-vms The following VMs are available for generation-2: 1) IcedTea JDK 3.9.0 [icedtea-8] *) IcedTea JDK 3.9.0 [icedtea-bin-8]
It start working after installing the 3.1.4 version first, and then upgrading to 3.2.0. 1. # emerge -av =android-studio-3.1.4.0.173.4907809 2. # emerge -av android-studio When done in this order, 3.2 builds fine.
Created attachment 555860 [details] corrected ebuild for Android Studio 3.2.0 Android Studio 3.2.0
I can confirm the proposed ebuild works for me.
(In reply to Mateusz Mandera from comment #6) > It start working after installing the 3.1.4 version first, and then > upgrading to 3.2.0. > > 1. # emerge -av =android-studio-3.1.4.0.173.4907809 > 2. # emerge -av android-studio > > When done in this order, 3.2 builds fine. not for me: >>> Installing (5 of 5) dev-util/android-studio-3.1.4.0.173.4907809::gentoo * Package 'dev-util/android-studio-3.1.4.0.173.4907809' has one or more * collisions between symlinks and directories, which is explicitly * forbidden by PMS section 13.4 (see bug #326685): * * /opt/android-studio/jre
>>> Emerging (5 of 5) dev-util/android-studio-3.1.4.0.173.4907809::gentoo * Fetching files in the background. * To view fetch progress, run in another terminal: * tail -f /var/log/emerge-fetch.log * android-studio-ide-173.4907809-linux.zip BLAKE2B SHA512 size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking android-studio-ide-173.4907809-linux.zip to /var/tmp/portage/dev-util/android-studio-3.1.4.0.173.4907809/work >>> Source unpacked in /var/tmp/portage/dev-util/android-studio-3.1.4.0.173.4907809/work >>> Preparing source in /var/tmp/portage/dev-util/android-studio-3.1.4.0.173.4907809/work/android-studio ... * Applying 0001-use-java-home-before-bundled.patch ... [ ok ] removed 'commons-logging-1.2.jar' removed 'log4j.jar' >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-util/android-studio-3.1.4.0.173.4907809/work/android-studio ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-util/android-studio-3.1.4.0.173.4907809/work/android-studio ... >>> Source compiled. >>> Test phase [not enabled]: dev-util/android-studio-3.1.4.0.173.4907809 >>> Install android-studio-3.1.4.0.173.4907809 into /var/tmp/portage/dev-util/android-studio-3.1.4.0.173.4907809/image/ category dev-util >>> Completed installing android-studio-3.1.4.0.173.4907809 into /var/tmp/portage/dev-util/android-studio-3.1.4.0.173.4907809/image/ * Final size of build directory: 1237728 KiB (1.1 GiB) * Final size of installed tree: 1237952 KiB (1.1 GiB)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fd35d61b88bd6ff5b0bbfbf47a9e8b98d5764668 commit fd35d61b88bd6ff5b0bbfbf47a9e8b98d5764668 Author: Jason Zaman <perfinion@gentoo.org> AuthorDate: 2018-12-09 15:49:49 +0000 Commit: Jason Zaman <perfinion@gentoo.org> CommitDate: 2018-12-09 15:50:55 +0000 dev-util/android-studio: bump 3.2.1 Bug: https://bugs.gentoo.org/669616 Signed-off-by: Jason Zaman <perfinion@gentoo.org> Package-Manager: Portage-2.3.51, Repoman-2.3.11 dev-util/android-studio/Manifest | 1 + .../android-studio-3.2.1.0.181.5056338.ebuild | 115 +++++++++++++++++++++ 2 files changed, 116 insertions(+)
I figured out why, the globbing for fperms was referring to things in /opt on the live system not in /var/tmp/portage. this meant if you were installing android-studio for the first time it'd fail. Should be fixed now. please re-open or file a new bug if there are more issues. (In reply to Michal Plichta from comment #9) > not for me: > > >>> Installing (5 of 5) dev-util/android-studio-3.1.4.0.173.4907809::gentoo > * Package 'dev-util/android-studio-3.1.4.0.173.4907809' has one or more > * collisions between symlinks and directories, which is explicitly > * forbidden by PMS section 13.4 (see bug #326685): > * > * /opt/android-studio/jre Did you change things around with your ebuild? /jre hasn't been a dir in years im pretty sure. Try uninstalling completely and make sure nothing is left in /opt/android-studio then install it.
(In reply to Jason Zaman from comment #12) > I figured out why, the globbing for fperms was referring to things in /opt > on the live system not in /var/tmp/portage. this meant if you were > installing android-studio for the first time it'd fail. Should be fixed now. > please re-open or file a new bug if there are more issues. > > (In reply to Michal Plichta from comment #9) > > not for me: > > > > >>> Installing (5 of 5) dev-util/android-studio-3.1.4.0.173.4907809::gentoo > > * Package 'dev-util/android-studio-3.1.4.0.173.4907809' has one or more > > * collisions between symlinks and directories, which is explicitly > > * forbidden by PMS section 13.4 (see bug #326685): > > * > > * /opt/android-studio/jre > > Did you change things around with your ebuild? /jre hasn't been a dir in > years im pretty sure. Try uninstalling completely and make sure nothing is > left in /opt/android-studio then install it. It was my fault I had installed from bin package in /opt and then portage complain. No more issue.
