atom / ci

Build your Atom packages

Home Page:https://atom.io/packages

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

build-package.sh erroring with new TravisCI default distro

mschuchard opened this issue · comments

For Travis CI, the default distro of Trusty is currently being phased out in favor of Xenial. When testing a package on Xenial in Travis:

Running specs...
/home/travis/atom/usr/share/atom/atom: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
The command "curl -s https://raw.githubusercontent.com/atom/ci/master/build-package.sh | sh" exited with 127.

When I check for Atom's library links, I hit:

ldd `which atom`
not a dynamic executable

so I cannot seem to determine myself if this is a link target issue for Atom, or if a dependency needs to be added for TravisCI.

Thanks for any assistance/fix.

I encountered the same problem. As described here, I just added libgconf-2-4 to the packages to be installed by apt.

addons:
  apt:
    packages:
    - build-essential
    - fakeroot
    - git
    - libsecret-1-dev
    - libgconf-2-4

Afterwards, the build script works like a charm.

Good stuff.
Can we please get this fix upstreamed?

I've opened atom/atom#19358 to get the dependency added to Atom proper.

Well that answers that question: this is a link target issue for Atom and not a TravisCI env issue. Good to know.

Note that Electron 3 (which just got merged to master, let's see if it makes it to a beta branch this time!) removes this requirement, so for the moment updating your CI scripts is the best option.

Interestingly I haven't seen this yet on any of the repositories I run through Travis CI.

My assumption to that end is that Travis has not migrated them yet. However, they have officially announced that Trusty is now deprecated.

Turns out that all of my repositories included this line, and thus weren't seeing the issue:

ci/.travis.yml

Line 37 in 25b0406

dist: trusty

At some point this started working on Xenial, so closing this issue.