The command “sudo apt-get install -qq dotnet-sdk-2.2” failed and exited with 100 during .
It would be great to detail how the community can help add the releases to travis. I am copying over an issue from github that was never addressed for the asp previews.
I am interested in testing the new dotnet preview and it appears that travis is not configured to download/install this sdk.
Does someone need to add this version to apt-get?
6.01s16.32sSelecting previously unselected package liburcu1.
Selecting previously unselected package dotnet-runtime-deps-2.2.
Selecting previously unselected package dotnet-hostfxr-2.2.
Selecting previously unselected package dotnet-runtime-2.2.
Selecting previously unselected package dotnet-sdk-2.2.
The command "sudo apt-get install -qq dotnet-sdk-2.2" failed and exited with 100 during .
Same issue here. Any suggestions for a workaround?
Is there any estimate time to support for net core 2.2 ?
Could you post or link to an example yml file? I do not know travis nor ubuntu enough to know what “use xenial of bionic” fully means or how to do it.
This error suggests that either the package is incorrect, or – which is extremely more likely – that it uses the syntax of a newer dpkg version that the older version in trusty doesn’t understand.
So, the workaround is indeed to use Xenial.
https://dotnet.microsoft.com/download/linux-package-manager/ubuntu14-04/runtime-current, does claim Trusty support but lists a different set of steps.
https://github.com/travis-ci/travis-build/blob/12634169f0b886123b2e219f05f07cb38decd0d5/lib/travis/build/script/csharp.rb doesn’t follow these steps but invents its custom ones that make their own assumptions about URLs and such (how much they are equivalent is up for debate; the important thing is, MS doesn’t promise that any other steps would work).
So this looks like Travis’ issue; could possibly be MS’ issue, too, if the package fetched with correct steps also couldn’t be parsed.
They said as a workaround to update manually dpkg but in this case, I haven’t find any way to run the update command before Travis tries to install .NET Core. The before_install and apt addons seems to run in a later step.
In my case, I’m updating the dist from trusty to xenial as recommended before.
this is still an issue?
@Kritner yes, that’s still in issue. You have to set the dist in your yaml-file to either use xenial or bionic.
What’s this “dist” property? And how does using it over dist: trusty make the difference? I’m very new to this, so apologies if that’s a dumb question.
That’s a build-environment as well.
and you are good to go. You can find here a sample of mine.