aegypius / overlay

Gentoo overlay
http://aegypius.github.io/overlay/
31 stars 8 forks source link

atom-shell ebuild fails to install #14

Closed SkeLLLa closed 10 years ago

SkeLLLa commented 10 years ago

Hello, I've tried to merge atom shell from your overlay and it's failed during install phase with such error:

ninja: Entering directory `out/Release'
ninja: fatal: chdir to 'out/Release' - No such file or directory
/tmp/portage/dev-util/atom-shell-0.13.3/temp/environment: line 6329: out/Release/version: No such file or directory
cp: cannot create regular file 'out/Release': No such file or directory
>>> Source compiled.
>>> Test phase [not enabled]: dev-util/atom-shell-0.13.3

>>> Install atom-shell-0.13.3 into /tmp/portage/dev-util/atom-shell-0.13.3/image/ category dev-util
/tmp/portage/dev-util/atom-shell-0.13.3/temp/environment: line 6343: cd: out/Release: No such file or directory
doexe: warning, skipping directory atom
!!! doexe: libchromiumcontent.so does not exist
!!! doexe: libffmpegsumo.so does not exist

I've tried to emerge with sandbox feature disabled, but it not helped.

aegypius commented 10 years ago

Thanks for your report it seems that something is broken now.

I will run tests for 0.13.3 in a vanilla environment to try to reproduce this failure.

On ven. 25 juil. 2014 11:30:54 CEST, Alexander wrote:

Hello, I've tried to merge atom shell from your overlay and it's failed during install phase with such error:

|ninja: Entering directory `out/Release' ninja: fatal: chdir to 'out/Release' - No such file or directory /tmp/portage/dev-util/atom-shell-0.13.3/temp/environment: line 6329: out/Release/version: No such file or directory cp: cannot create regular file 'out/Release': No such file or directory

Source compiled. Test phase [not enabled]: dev-util/atom-shell-0.13.3

Install atom-shell-0.13.3 into /tmp/portage/dev-util/atom-shell-0.13.3/image/ category dev-util /tmp/portage/dev-util/atom-shell-0.13.3/temp/environment: line 6343: cd: out/Release: No such file or directory doexe: warning, skipping directory atom !!! doexe: libchromiumcontent.so does not exist !!! doexe: libffmpegsumo.so does not exist |

I've tried to emerge with sandbox feature disabled, but it not helped.

— Reply to this email directly or view it on GitHub https://github.com/aegypius/overlay/issues/14.

SkeLLLa commented 10 years ago

I've tried to create this directory manually, it copied there LICENSE and version files but also failed:

ninja: Entering directory `out/Release'
ninja: error: loading 'build.ninja': No such file or directory
>>> Source compiled.
>>> Test phase [not enabled]: dev-util/atom-shell-0.13.3

>>> Install atom-shell-0.13.3 into /tmp/portage/dev-util/atom-shell-0.13.3/image/ category dev-util
!!! doexe: atom does not exist
!!! doexe: libchromiumcontent.so does not exist
!!! doexe: libffmpegsumo.so does not exist

May be it's something with my environment. If you need any info - just tell what you need.

aegypius commented 10 years ago

Building is running at the moment, llvm and clang are quite long to compile on my testing env (docker container) but as soon as its compiled I may need some logs from you.

At the moment, I am running an atom-shell-0.13.3 version on my desktop but I may have some missing dependencies installed. So running in a clean, isolated container seems the best way to find what it is happening.

aegypius commented 10 years ago

It seems I missed a lot of dependencies... I am trying to fix that.

SkeLLLa commented 10 years ago

@aegypius Ok, I'll also try to build it after you push a fix for that. Also don't forget about gnome-base/libgnome-keyring dependency. I've installed it manually (I have KDE, so only few gnome libraries were installed) after reading some issues about atom in ubuntu (node-keytar requires it). And according to node-keytar github page it may be replaced with more efficient tool later, and this dependency will not be required.

aegypius commented 10 years ago

This is one of the missed ones.

aegypius commented 10 years ago

Dependencies are good now. I can reproduce the failure you add with a missing out/Release directory.

It seems to be related to bootstrap script.

... Continuing tests.

aegypius commented 10 years ago

Bootstrap script fails with an error :

Traceback (most recent call last):
  File "./script/bootstrap.py", line 7, in <module>
    from lib.config import LIBCHROMIUMCONTENT_COMMIT, BASE_URL
  File "/var/tmp/portage/dev-util/atom-shell-0.13.3/work/atom-shell-0.13.3/script/lib/config.py", line 15, in <module>
    }[sys.platform]
KeyError: 'linux'
aegypius commented 10 years ago

My mistake I was using python 3 :(

SkeLLLa commented 10 years ago

@aegypius I used python 2.7. But I run Funtoo (gentoo-based distribution). May be if you need some emerge info or another info, I can provide it.

aegypius commented 10 years ago

I managed to fix the bootstrap phase but build fails when linking atom-shell with libchromiumcontent.so...

aegypius commented 10 years ago

I used python 2.7. But I run Funtoo (gentoo-based distribution). May be if you need some emerge info or another info, I can provide it.

I use a gentoo gnome desktop, I missed most gnome dependencies because they were allready installed.

I never tried Funtoo, I don't know exactly what is different from a gentoo.

aegypius commented 10 years ago

Build succeeded in my testing env, If you want you can give it a try following theses steps:

git clone https://github.com/aegypius/overlay $HOME/overlay-testing
cd $HOME/overlay-testing
git checkout 14-atom-shell-ebuild-fails-to-install

Then edit /etc/portage/make.conf and add new overlay dir (absolute path) to PORTDIR_OVERLAY env var.

I may merge theses fixes to master branch during the week end with the atom-shell-0.14.2.ebuild

aegypius commented 10 years ago

It's merged into master now

SkeLLLa commented 10 years ago

Thanks @aegypius. Now atom shell merged. There were some issues, but i think it was on my side: I hadn't clang in /usr/bin folder, but package was installed according to emerge. Reinstalling clang and llvm resolved issue (may be it was caused by llvm that was merged without clang flag, may be it worth to check this in ebuild too).

Also there an issue with atom editor ebuild. It's manifest has wrong file size data:

!!! Digest verification failed:
!!! /var/lib/layman/aegypius/app-editors/atom/files/0001-fix-atom.sh.patch
!!! Reason: Filesize does not match recorded size
!!! Got: 1002
!!! Expected: 1004
aegypius commented 10 years ago

OK I will fix manifest. I'm glad it's fixed for you too.