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
Comments
Did the requirements for these packages change somehow? https://travis-ci.org/mupen64plus/mupen64plus-core/jobs/269437306#L473-L475 says:
but these packages were previously installed (https://travis-ci.org/mupen64plus/mupen64plus-core/jobs/266389369#L459-L468). |
Hmm. Perhaps our If you add the missing dependencies, it appears to work if you add the packages that |
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) |
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 |
I confirm @CharlemagneLasse workaround is working on my project https://github.com/RICCIARDI-Adrien/Strage. |
This bug also affects the Wesnoth project. |
Found by charlemagnelasse.
* enable sdl2 per default * fix to work around an issue, take a look here travis-ci/travis-ci#8317
to work around package installation failure (see travis-ci/travis-ci#8317)
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.
Ok, so I just looked at the line that travis runs to install with
But travis is doing [1]:
Running
It's strange (to me) because this is supposed to be a I believe the right solution is to use the This seems to be related to [2]. It's been reported over and over online :( |
This is a workaround for travis-ci/travis-ci#8317
This is a workaround for travis-ci/travis-ci#8317
This is a workaround for travis-ci/travis-ci#8317
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 |
The last activity was 14 days ago. So keep your stale state for yourself.
|
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 |
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.
The text was updated successfully, but these errors were encountered: