PowerShell Core availability on Ubuntu 17.04

[MaximoTrinidad]

Just want to know the plan for supporting PowerShellCore in the upcoming Ubuntu Version 17.04.

I tried to installed it but I getting some library errors:
"Package libicu55 is not installed."

Steps to reproduce

1. Download PowerShell v6.0.0.0-alpha.18-1ubuntu1.16.04.1_amd64.deb
2. sudo dpkg -i powershell v6.0.0.0-alpha.18-1ubuntu1.16.04.1_amd64.deb

Expected behavior

Installation to complete without errors

Actual behavior

"Package libicu55 is not installed."

Environment data

Ubuntu 17.04

> $PSVersionTable

[iSazonov]

A simple rule is - first CoreFX/CoreCLR should add support a platform.

[pcgeek86]

@iSazonov perhaps add the Resolution - External label?

[iSazonov]

@pcgeek86 The Issue is "Waiting external" 😄

[MaximBar]

Hi,
I've chatted with the corefs guys and they said that the latest portable dotnet core 2.0 works fine on Ubuntu 17.04:
https://github.com/dotnet/corefx/issues/20562#issuecomment-305555951
and the PS run (not install) file AppImage PowerShell-6.0.0-beta.1-x86_64.AppImage also works with Ubuntu 17.04

but not the other install .deb files.
So it's now should be possible to port PS to Ubuntu 17,04.

[iSazonov]

@joeyaiello @TravisEz13 @SteveL-MSFT CoreFX team support Ubuntu 17,04. What is a PowerShell team plan?

Update: I see CoreFX team change their support policy. For .Net Core 1.0.1 they support _specific_ versions. For .Net Core 2.0 they indicate the _minimum_ OS version.

[joeyaiello]

Not sure what the problem is here, but we should get this working.

Also, I should read the entirety of an issue before I start adding labels. ;)

[MaximoTrinidad]

So, what's the steps to install PowerShell in Ubuntu 17.04?

As of now, with PowerShell Beta.2, I'm getting the following message with .Net Core 2.0 Preview installed:

The following packages have unmet dependencies:
powershell : Depends: libicu55 but it is not installable
E: Unable to correct problems, you have held broken packages.

:)

[iSazonov]

@joeyaiello I expect that we should have new clear policy in our docs to support different OS versions. Because now dotnet support is based on minimal OS version our current policy "we follow CoreFX" is too vague - unlike a CoreFX, we have OS version dependencies.

[joeyaiello]

Adding context from the duped issue. Apparently, running PowerShell dumps this:

powershell: pal_io.cpp:758: int64_t SystemNative_SysConf(SysConfName): Assertionfalse && "Unknown SysConfName"' failed.`

[TravisEz13]

Talked to @janvorli and by portable, he means targeting runtime id linux-x64 and standalone (specify the runtime id when publishing, which will includes all the assemblies and native shared libraries)

Found docs Publishing a self-contained console application for all platforms

[borgdylan]

When running a generic app on .NET Core 1.1 and 2.0 I get no issues on my 17.04 machine, the same machine of the "duped" issue. The interface for certain system calls gets updated after a few kernel releases. I'd recommend depending on common shell builtins for getting system information or at least using the latest .NET Core at all times which does get tested on newer kernels AFAIK. I do realise that it is hard tracking a kernel that is not maintained in house

[iSazonov]

@TravisEz13 Good catch! Should we create a tracking Issue for linux-x64 ?

[borgdylan]

One of more problematic libraries is ICU which gets updated each year. There are ways to have an older version installed side by side.

[janvorli]

@chuanjiao10 we are already compatible with debian 9.

[janvorli]

@borgdylan CoreCLR is now resilient to ICU version, it should work with any future version up to version number 70, provided there is no breaking change in the interface. But the ICU doc says that stable APIs should stay in the future versions and we are using stable APIs only.

[TravisEz13]

@iSazonov We will try to come up with a plan and get back to you on how to track the work. I changed this issue to an enhancement for now.

[TravisEz13]

@iSazonov I have filed an issue. Thanks.

[iSazonov]

@MaximoTrinidad See https://github.com/PowerShell/PowerShell/issues/3961 with PowerShell team plan.

[borgdylan]

The bug is because an incorrect integer is being passed in: https://github.com/dotnet/corefx/blob/master/src/Native/Unix/System.Native/pal_io.cpp#L844 . The allowed strings are only three based on specific constants. In this case we are hitting the assert in that code.

[SteveL-MSFT]

@borgdylan is there an issue opened for corefx?

[borgdylan]

I have opened an issue against corefx.

[iSazonov]

@borgdylan Please add cross link here to the Issue.

[TravisEz13]

https://github.com/dotnet/corefx/issues/21386