-
Notifications
You must be signed in to change notification settings - Fork 34
build-package.sh fails to extract deb package with beta channel on Travis CI with Ubuntu Trusty #94
Comments
See atom/ci#94 for more info
* ci: move travis to using xenial to fix extract issues See atom/ci#94 for more info * ci: add libgconf-2-4 to apt packages
* ci: move travis to using xenial to fix extract issues See atom/ci#94 for more info * ci: add libgconf-2-4 to apt packages
* ci: move travis to using xenial to fix extract issues See atom/ci#94 for more info * ci: add libgconf-2-4 to apt packages
This issue started occurring after we transitioned from Ubuntu 14 to Ubuntu 18 in our build infrastructure. Initially, we thought it would have been fine to just switch all package builds to a newer Ubuntu distro, but during the last railcar release we realized that building on a newer distro would prevent people using older kernels from launching Atom at all. We have opened atom/atom#19617 to go back to building Atom on Ubuntu 14 and we're actively working on releasing a hotfix on beta and stable. Once that's done, triggering a re-build should automatically fix the problem. Apologies for the oversight on this problem. |
atom/atom#19617 is merged, and we've published Atom 1.39.1 and 1.40.0-beta1 with that fix in place. I think that resolves this problem, so I'm going to close this issue. If you continue to experience this problem, please let us know. 🙇 |
Description
CI tests with Travis and Ubuntu Trusty fails for atom beta channel.
Expected behavior:
Test passes.
Actual behavior:
Reproduces how often:
Always.
Versions
atom-amd64.deb
Travis
dist: trusty
Additional Information
I tryed to fix the issue based on the solution provided on travis-ci/travis-ci#9361, upgrade to dpkg >= 1.17.5ubuntu5.8, which fixes https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/173062
with no success
I can confirm that changing the distro to
dist: xenial
(needslibgconf-2-4
to run atom) builds the package and runs the tests without any problem so looks like the problem is not directly related to the build script.The text was updated successfully, but these errors were encountered: