Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails to install packages in Trusty #8317

Closed
ghost opened this issue Aug 30, 2017 · 10 comments
Closed

Fails to install packages in Trusty #8317

ghost opened this issue Aug 30, 2017 · 10 comments

Comments

@ghost
Copy link

ghost commented Aug 30, 2017

It was reported that mupen64plus/mupen64plus-core#377 now fails suddenly in the "apt-get install" step.

A log of the failed install can be found in https://travis-ci.org/mupen64plus/mupen64plus-core/jobs/269748268
But it worked previously flawless - as you can see in https://travis-ci.org/mupen64plus/mupen64plus-core/jobs/266389369#L1

The config can be found in https://github.com/mupen64plus/mupen64plus-core/blob/master/.travis.yml and was not touched between these two builds.

@BanzaiMan
Copy link
Contributor

Did the requirements for these packages change somehow? https://travis-ci.org/mupen64plus/mupen64plus-core/jobs/269437306#L473-L475 says:

The following packages have unmet dependencies:
 libsdl2-dev : Depends: libegl1-mesa-dev
               Depends: libgles2-mesa-dev
E: Unable to correct problems, you have held broken packages.

but these packages were previously installed (https://travis-ci.org/mupen64plus/mupen64plus-core/jobs/266389369#L459-L468).

@BanzaiMan
Copy link
Contributor

Hmm. Perhaps our apt-get defaults changed somehow?

If you add the missing dependencies, it appears to work if you add the packages that apt-get is complaining about. mupen64plus/mupen64plus-core#380

@ghost
Copy link
Author

ghost commented Sep 1, 2017

No, requirements didn't change. And manually specifying these is not the right solution. apt-get was previously able to resolve the dependencies (which are not direct dependencies of mupen64plus-core)

@ghost
Copy link
Author

ghost commented Sep 1, 2017

Interestingly, it works when using the apt addon. See mupen64plus/mupen64plus-core#381

It looks like something broke horrible on your servers and which most likely also effects other projects which did not yet switch to the apt addon

@RICCIARDI-Adrien
Copy link

I confirm @CharlemagneLasse workaround is working on my project https://github.com/RICCIARDI-Adrien/Strage.

Saph32 added a commit to Saph32/Ataboy that referenced this issue Sep 2, 2017
@AI0867
Copy link

AI0867 commented Sep 8, 2017

This bug also affects the Wesnoth project.

AI0867 added a commit to wesnoth/wesnoth that referenced this issue Sep 8, 2017
Found by charlemagnelasse.
damiel added a commit to OpenTechEngine/OpenTechBFG that referenced this issue Sep 30, 2017
* enable sdl2 per default
* fix to work around an issue, take a look here travis-ci/travis-ci#8317
emlai added a commit to emlai/ivan that referenced this issue Oct 10, 2017
to work around package installation failure (see
travis-ci/travis-ci#8317)
emlai added a commit to emlai/ivan that referenced this issue Oct 10, 2017
to work around package installation failure (see
travis-ci/travis-ci#8317). Also remove 'sudo' requirement as it's no
longer needed, which will (hopefully) speed up the builds a bit.
aurhat added a commit to aurhat/AC that referenced this issue Nov 5, 2017
maritim added a commit to maritim/LiteEngine that referenced this issue Nov 12, 2017
probonopd added a commit to probonopd/OpenRCT2 that referenced this issue Nov 12, 2017
ac-stef pushed a commit to ac-stef/AC that referenced this issue Nov 23, 2017
aurhat added a commit to assaultcube/AC that referenced this issue Nov 25, 2017
jedie added a commit to jedie/RunCalculator that referenced this issue Nov 26, 2017
matham added a commit to matham/ffpyplayer that referenced this issue Dec 5, 2017
matham added a commit to matham/ffpyplayer that referenced this issue Dec 5, 2017
@ivanperez-keera
Copy link

Ok, so I just looked at the line that travis runs to install with apt-get, and it is slightly different from what I was running. I was doing:

$ sudo apt-get install <packages>

But travis is doing [1]:

$ sudo -E apt-get -yq --no-install-suggests --no-install-recommends --force-yes install <packages>

Running aptitude gives a bit more info about what's going on:

$ sudo -E aptitude install libsdl2-dev libsdl2-image-dev libsdl2-ttf-dev libsdl2-mixer-dev libsdl2-gfx-dev

The following NEW packages will be installed:
  freepats{a} libasound2-dev{a} libavahi-client-dev{a} 
  libavahi-common-dev{a} libboost-system1.54.0{a} libdbus-1-dev{a} 
  libegl1-mesa-dev{a} libegl1-mesa-drivers-lts-utopic{a} 
  libegl1-mesa-lts-utopic{ab} libfluidsynth1{a} libgbm1-lts-utopic{a} 
  libgl1-mesa-dri-lts-utopic{ab} libglapi-mesa-lts-utopic{ab} 
  libgles2-mesa{a} libgles2-mesa-dev{a} libjack-jackd2-0{a} libllvm3.5{a} 
  libmad0{a} libmirclient-dev{a} libmirclient7{a} 
  libmirclientplatform-mesa{a} libmirprotobuf-dev{a} libmirprotobuf0{a} 
  libmodplug1{a} libopenvg1-mesa-lts-utopic{a} libprotobuf-dev{a} 
  libprotobuf-lite8{a} libprotobuf8{a} libpulse-dev{a} 
  libpulse-mainloop-glib0{a} libsamplerate0{a} libsdl2-2.0-0{a} libsdl2-dev 
  libsdl2-gfx-1.0-0{a} libsdl2-gfx-dev libsdl2-image-2.0-0{a} 
  libsdl2-image-dev libsdl2-mixer-2.0-0{a} libsdl2-mixer-dev 
  libsdl2-ttf-2.0-0{a} libsdl2-ttf-dev libts-0.0-0{a} libts-dev{a} 
  libtxc-dxtn-s2tc0{a} libudev-dev{a} libwayland-dev{a} 
  libwayland-egl1-mesa-lts-utopic{a} libwebp5{a} libxcursor-dev{a} 
  libxi-dev{a} libxinerama-dev{a} libxkbcommon-dev{a} libxrandr-dev{a} 
  libxv-dev{a} mircommon-dev{a} tsconf{a} x11proto-randr-dev{a} 
  x11proto-video-dev{a} x11proto-xinerama-dev{a} 
0 packages upgraded, 59 newly installed, 0 to remove and 15 not upgraded.
Need to get 49.0 MB of archives. After unpacking 114 MB will be used.
The following packages have unmet dependencies:
 libegl1-mesa : Conflicts: libegl1-x11 which is a virtual package.
 libgl1-mesa-dri-lts-utopic : Conflicts: libgl1-mesa-dri but 10.1.3-0ubuntu0.6 is installed.
 libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.6 is installed.
 libegl1-mesa-lts-utopic : Conflicts: libegl1-mesa but 10.1.3-0ubuntu0.6 is installed.
                           Conflicts: libegl1-x11 which is a virtual package.

It's strange (to me) because this is supposed to be a trusty image, but contains utopic packages. But it's been reported before, not just on travis.

I believe the right solution is to use the apt addon for all packages but, if you want to do what travis does, manually, just use --no-install-suggests --no-install-recommends (I removed the latter and the installation failed for me).

This seems to be related to [2]. It's been reported over and over online :(

[1] https://github.com/travis-ci/travis-build/blob/ef82e82457f82c6518d090544bb533dc0faf0063/lib/travis/build/addons/apt.rb#L154-L155

[2] https://bugs.launchpad.net/cloud-images/+bug/1713815

phrohdoh added a commit to ChariotEngine/Chariot that referenced this issue Mar 30, 2018
phrohdoh added a commit to ChariotEngine/Chariot that referenced this issue Mar 30, 2018
@stale
Copy link

stale bot commented Apr 12, 2018

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

@stale stale bot added the stale label Apr 12, 2018
@ghost
Copy link
Author

ghost commented Apr 13, 2018

The last activity was 14 days ago. So keep your stale state for yourself.

Phrohdoh added a commit to ChariotEngine/Chariot that referenced this issue 14 days ago
 @Phrohdoh
ci: Use the apt addon for Travis  …

@stale stale bot removed the stale label Apr 13, 2018
@stale
Copy link

stale bot commented Jul 12, 2018

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 24 hours. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

@stale stale bot added the stale label Jul 12, 2018
@stale stale bot closed this as completed Jul 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants