[DSR] - Debian 12 x64 #19889

Chouffy · 2023-07-04T10:15:50Z

Chouffy · 2023-07-04T10:17:00Z

Note on possible workaround: It's possible to install Powershell on Debian 12 via Snap, but it's not ideal :)

237dmitry · 2023-07-04T11:44:50Z

As a linux user I recommend to install from tarball (not dpkg, not snap (!!!) or another package manager). Unpack pwsh distribution to /opt/pwsh Make simlink of pwsh to the path. Set additional permission for Test-Connection cmdlet:

sudo setcap cap_net_raw=eip /opt/pwsh/pwsh     # the real path to executable pwsh

You can change installation path as you want.

kasini3000 · 2023-07-04T15:00:19Z

mark. i will update my script when here down.

https://gitee.com/chuanjiao10/kasini3000_agent_linux#debian12-kernel61-release-day-2023-06-17-

tsugliani · 2023-09-01T14:36:28Z

Very interested for this, as we are upgrading to Debian 12 (Bookworm)

Seems to be missing in the microsoft bookworm repo, available on debian 10/11

[ ] Update packages.microsoft.com deployment

❯ cat /etc/apt/sources.list.d/microsoft.list
deb [arch=amd64 signed-by=/usr/share/keyrings/microsoft.gpg] https://packages.microsoft.com/repos/microsoft-debian-bookworm-prod bookworm main

Erich-Chen · 2023-09-21T04:53:33Z

It works by following Microsoft installation guide for bullseye, then manually editing file /etc/apt/sources.list.d/microsoft.list before install.

# Save the public repository GPG keys
curl https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --yes --dearmor --output /usr/share/keyrings/microsoft.gpg

# Register the Microsoft Product feed
sudo sh -c 'echo "deb [arch=amd64 signed-by=/usr/share/keyrings/microsoft.gpg] https://packages.microsoft.com/repos/microsoft-debian-bullseye-prod bullseye main" > /etc/apt/sources.list.d/microsoft.list'

# Edit file /etc/apt/sources.list.d/microsoft.list
# deb [arch=amd64 signed-by=/usr/share/keyrings/microsoft.gpg] https://packages.microsoft.com/repos/microsoft-debian-bookworm-prod bookworm main

# Install PowerShell
sudo apt update && sudo apt install -y powershell

# Start PowerShell
pwsh

prakashguru · 2023-10-18T13:57:52Z

+1 for this.

@TravisEz13 Will it possible for you to have a look at this? Something similar we have to do like debian 11 #10923

ExNought · 2023-10-31T12:27:46Z

I am biting nails to get PowerShell on Debian 12. This is affecting my work since I am already on Debian 12 and VSC does not recognize PowerShell anymore. I currently use PowerShell from the legacy sources.

rhubarb-geek-nz · 2023-11-22T19:01:04Z

What is the issue with downloading the Debian package directly from the releases page?

https://github.com/PowerShell/PowerShell/releases/download/v7.4.0/powershell_7.4.0-1.deb_amd64.deb

eliminmax · 2023-11-25T00:29:13Z

What is the issue with downloading the Debian package directly from the releases page?

https://github.com/PowerShell/PowerShell/releases/download/v7.4.0/powershell_7.4.0-1.deb_amd64.deb

It won't get updated with APT that way, and there's no guarantee that it will work on any particular version of Debian.

prakashguru · 2023-11-25T08:32:58Z

Dear @eliminmax I dont think there will be an issue to download manually the powershell and install it on my machine.

But some of our customers using our application which has powershell as a dependency unable to install it on debian 12 because powershell is not published for debian 12.

There are heavily restricted environments where installing packages outside of the official repositories are prohibited.

So it is important and required to be published!

AndrewSav · 2023-11-25T09:24:35Z

@rhubarb-geek-nz for anyone who had ever worked in an enterprise environment it is obvious why this would not be very manageable. MS start to provide those for a reason, and for the same reason we ask them to continue to do so.

rhubarb-geek-nz · 2023-11-25T10:22:46Z

@rhubarb-geek-nz for anyone who had ever worked in an enterprise environment it is obvious why this would not be very manageable. MS start to provide those for a reason, and for the same reason we ask them to continue to do so.

Absolutely true but it is not a show stopper. The published debian file does work and it is not a rebuild required, just an addition to the packages.microsoft.com. If you are in an enterprise environment you may be hosting your own APT repositories or using downloads directly with curl when creating docker images.

If you check the recent debian packages on packages.microsoft.com they are the same file

#!/bin/sh -e

for o in debian ubuntu
do
        for v in 10 11 12 18.04 18.10 19.04 19.20 20.04 20.10 21.04 21.10 22.04 22.10 23.04 23.10
        do
                if curl https://packages.microsoft.com/$o/$v/prod/pool/main/p/powershell/powershell_7.4.0-1.deb_amd64.deb --output powershell_7.4.0-1.$o.$v.deb_amd64.deb --location --fail --silent
                then
                        sha256sum powershell_7.4.0-1.$o.$v.deb_amd64.deb
                fi
        done
done

550331e243a7311e1bf0ca83d8c96c5e78ba82a765c4a9ba34aa0db6eb9a9f22  powershell_7.4.0-1.debian.10.deb_amd64.deb
550331e243a7311e1bf0ca83d8c96c5e78ba82a765c4a9ba34aa0db6eb9a9f22  powershell_7.4.0-1.debian.11.deb_amd64.deb
550331e243a7311e1bf0ca83d8c96c5e78ba82a765c4a9ba34aa0db6eb9a9f22  powershell_7.4.0-1.ubuntu.18.04.deb_amd64.deb
550331e243a7311e1bf0ca83d8c96c5e78ba82a765c4a9ba34aa0db6eb9a9f22  powershell_7.4.0-1.ubuntu.20.04.deb_amd64.deb
550331e243a7311e1bf0ca83d8c96c5e78ba82a765c4a9ba34aa0db6eb9a9f22  powershell_7.4.0-1.ubuntu.22.04.deb_amd64.deb

The packages.microsoft.com repository for Ubuntu 22.04 amd64 is problematic because the dotnet-sdk-6.0 conflict with those distributed by ubuntu themselves. They have different version suffixes and install in different directories.

$ dpkg -l | grep "dotnet
> aspnet"
ii  aspnetcore-runtime-6.0                6.0.125-0ubuntu1~22.04.1                amd64        ASP dotNET Core runtime
ii  aspnetcore-runtime-7.0                7.0.114-0ubuntu1~22.04.1                amd64        ASP dotNET Core runtime
ii  aspnetcore-targeting-pack-6.0         6.0.125-0ubuntu1~22.04.1                amd64        Internal - targeting pack for Microsoft.AspNetCore.App 6.0
ii  aspnetcore-targeting-pack-7.0         7.0.114-0ubuntu1~22.04.1                amd64        Internal - targeting pack for Microsoft.AspNetCore.App 7.0
ii  dotnet-apphost-pack-6.0               6.0.125-0ubuntu1~22.04.1                amd64        Internal - targeting pack for Microsoft.NETCore.App 6.0
ii  dotnet-apphost-pack-7.0               7.0.114-0ubuntu1~22.04.1                amd64        Internal - targeting pack for Microsoft.NETCore.App 7.0
rc  dotnet-host                           6.0.125-0ubuntu1~22.04.1                amd64        dotNET host command line
ii  dotnet-host-7.0                       7.0.114-0ubuntu1~22.04.1                amd64        dotNET host command line
ii  dotnet-hostfxr-6.0                    6.0.125-0ubuntu1~22.04.1                amd64        dotNET host resolver
ii  dotnet-hostfxr-7.0                    7.0.114-0ubuntu1~22.04.1                amd64        dotNET host resolver
ii  dotnet-runtime-6.0                    6.0.125-0ubuntu1~22.04.1                amd64        dotNET runtime
ii  dotnet-runtime-7.0                    7.0.114-0ubuntu1~22.04.1                amd64        dotNET runtime
ii  dotnet-sdk-6.0                        6.0.125-0ubuntu1~22.04.1                amd64        dotNET 6.0 Software Development Kit
ii  dotnet-sdk-7.0                        7.0.114-0ubuntu1~22.04.1                amd64        dotNET 7.0 Software Development Kit
ii  dotnet-targeting-pack-6.0             6.0.125-0ubuntu1~22.04.1                amd64        Internal - targeting pack for Microsoft.NETCore.App 6.0
ii  dotnet-targeting-pack-7.0             7.0.114-0ubuntu1~22.04.1                amd64        Internal - targeting pack for Microsoft.NETCore.App 7.0
ii  dotnet-templates-6.0                  6.0.125-0ubuntu1~22.04.1                amd64        dotNET 6.0 templates
ii  dotnet-templates-7.0                  7.0.114-0ubuntu1~22.04.1                amd64        dotNET 7.0 templates
$ ls -ld /usr/bin/dotnet
lrwxrwxrwx 1 root root 20 Nov 13 14:08 /usr/bin/dotnet -> ../lib/dotnet/dotnet

I have asked for a couple of years for armhf and aarch64 debian files but them not existing does not prevent me creating my own APT repository with repackaged files for armhf/aarch64.

prakashguru · 2023-11-25T10:47:40Z

@rhubarb-geek-nz No it is a show stopper!

We do have an apt repo. Technically I can host the powershell.deb package into it and distribute. But practically I can't due to the following reasons,

Have to go through license, compliance and security review to host a third party package into my company repository. That will be a nightmare.
Security updates! Whenever MS releases security updates, I have to keep track of those and constantly update and again go through those reviews.

So practically it is a no no.

rhubarb-geek-nz · 2023-11-25T10:54:14Z

@rhubarb-geek-nz No it is a show stopper!

That is your call, you do have the existing work around mechanisms but you chose not to use them.

Other workarounds including using the tool via the sdk from apt.

$ sudo apt-get install dotnet-sdk-8.0
...
$ dotnet tool install --global powershell
...
You can invoke the tool using the following command: pwsh
Tool 'powershell' (version '7.4.0') was successfully installed.
$ PATH=$PATH:$HOME/.dotnet/tools
$ pwsh --version
PowerShell 7.4.0

Daverd-GM · 2024-02-07T18:33:40Z

It would be nice to add the PowerShell.deb versions to the https://packages.microsoft.com/debian/12/prod/
for it to be available in the Extrepo-Data Project, which is the Debian tool for managing external repositories from the command line

Index of /debian/12/prod/

GitLab
External repositories team / extrepo · GitLab
Debian Salsa Gitlab

kallisti5 · 2024-03-13T18:17:34Z

LiNUx sUpPorT for pOwERsHeLL iS fIrsT cLass

https://packages.microsoft.com/debian/11/prod/ -- powershell packages
https://packages.microsoft.com/debian/12/prod/ -- no powershell packages over a year later

Index of /debian/11/prod/

Index of /debian/12/prod/

nanonyme · 2024-03-15T10:02:15Z

It's not really the delay itself. Debian makes releases fairly reliably every two years and it's frustrating customers have to keep creating these tickets rather than it being baked into Powershell maintenance process.

kallisti5 · 2024-03-15T12:57:02Z

Yeah.. it's just frustrating because it's a time suck to everyone when Microsoft doesn't maintain this stuff. Wasted around 2 hours debugging microsoft's repos and lack of powershell until I realized that it was in 11's repo, but not 12's

I don't even want to mess with powershell, it's someones request to install it on a workstation 😆

nanonyme · 2024-03-15T14:25:53Z

Please don't get me wrong, I understand Microsoft has processes here where apparently supporting new Debian releases are tied to PowerShell releases which makes things awkward. Regardless, Debian releases are reasonably predictable in when they happen and there should be nothing preventing releasing PowerShell even before Debian actual release date if it's convenient.

eliminmax · 2024-03-15T16:53:33Z

Please don't get me wrong, I understand Microsoft has processes here where apparently supporting new Debian releases are tied to PowerShell releases which makes things awkward. Regardless, Debian releases are reasonably predictable in when they happen and there should be nothing preventing releasing PowerShell even before Debian actual release date if it's convenient.

I was almost done opening a separate issue asking them to do that, but then I couldn't figure out a way to programmatically check if the latest Debian release hit its soft freeze period, so I am not sure if it's as simple as I'd assumed, and I'm sure the PowerShell maintainers have a lot of other responsibilities as is. It would be nice if they'd have been quicker about addressing this issue, but, while new Debian releases are every odd-numbered years, sometime in the Summer, that's not a hard rule, so I don't know how simple it would be to do this.

prakashguru · 2024-09-18T04:16:31Z

This distribution has published. https://mcr.microsoft.com/product/powershell/tags

**Microsoft Artifact Registry**Microsoft Artifact Registry (also known as Microsoft Container Registry or MCR) Discovery Portal

That is the incorrect location to publish the deb file. It should be in the debian 12 microsoft repo. https://packages.microsoft.com/debian/12/prod

Microsoft Artifact Registry
Microsoft Artifact Registry (also known as Microsoft Container Registry or MCR) Discovery Portal

GABRIELNGBTUC · 2024-09-23T07:16:29Z

It's hard to understand what is preventing them to add the deb files to the microsoft repository.

Ok you tested the package on debian 12 and created a docker image (that no one on this issue asked for).

Now that it is tested, there shouldn't be any blockers left to just drop the deb file into the package repository.

I'm sure no one here would even mind if it was marked as an "unstable" package or something. Many have been using the direct method install because of this issue and didn't encounter any problem. If it's a case of "we don't want to support it", still give us the option to use the package repository but explicitly say so that support will be non-existent / best-effort.

nanonyme · 2024-09-23T08:00:55Z

@theJasonHelmick, p 9E88 lease take a look at @masterflitzer and @kallisti5 comments above. We still need an apt repository for Debian 12! So, please, keep it open.

I suggest opening new ticket and link to this one if nothing happens soon. It seems important to have open ticket to ensure this hits appropriate queues.

masterflitzer · 2024-09-23T08:41:04Z

opened one over here: #24334

theJasonHelmick · 2024-09-23T14:50:45Z

Hey Folks -- thanks for the feedback. We are finishing some internal pipeline work and will post the deb files to Packages - PMC - shortly. (hopefully this week)

quaeryth · 2024-10-04T13:47:19Z

Looking forward to seeing this resolved soon. I'd also like to second the concern in part of @kallisti5's comment:

The current pace means Microsoft will be releasing powershell for versions of Debian less than 6 months from the next major version of Debian (13, early 2025)

nanonyme · 2024-10-04T14:21:54Z

Looking forward to seeing this resolved soon. I'd also like to second the concern in part of @kallisti5's comment:

Debian has statistically usually released during Summer. It's around half a year of stabilization from the point new release gets frozen.

xenadmin · 2024-10-07T15:05:51Z

@theJasonHelmick Any news on this?
We are now roughly ~9 months away from the release of Debian 13 and we urgently need PowerShell 7 support on Debian 12.

kallisti5 · 2024-10-07T16:23:47Z

I just double checked, Vegas odds on Powershell deb's getting released before Debian 13 is out are -5.2

AndrewSav · 2024-10-09T02:55:00Z

March 16 - "in the next couple of months"
June 5 - "this is priority 1 on our backlog"
August 24 - "planning to begin to release new distros at the beginning of September"
September 18 - "this distribution has published" - it was not and the issue was closed
Sepetmber 24 - "hopefully this week" - the issue remains closed
October 2 - the issue is reopened

Two weeks after the last communication there is still nothing. My prediction: they will soon realise that it's not feasible making any commitments and then looking like this, so they will keep silent in the future. It's much easier to ignore, does not make any worse of an impression than it has already and good for one's health.

The current pace means Microsoft will be releasing powershell for versions of Debian less than 6 months from the next major version of Debian (13, early 2025)

I wish I could excercise optimism with such abandon!

24mu13 · 2024-10-10T09:08:31Z

What's about to maintain the Debian package in their ecosystem?
https://www.debian.org/doc/manuals/debmake-doc/index.en.html

Do you think is feasible from licensing perspective?

Guide for Debian Maintainers

nanonyme · 2024-10-10T10:10:54Z

Hey Folks -- thanks for the feedback. We are finishing some internal pipeline work and will post the deb files to Packages - PMC - shortly. (hopefully this week)

Hey, would it be possible to provide any visibility over the work? If there are blockers, it would be useful to know exactly what and see their resolution's progress. Currently for us outsiders it looks very much like nothing's happening.

mbentley · 2024-10-10T11:34:16Z

What's about to maintain the Debian package in their ecosystem? https://www.debian.org/doc/manuals/debmake-doc/index.en.html

Do you think is feasible from licensing perspective?

Guide for Debian Maintainers

That would likely increase the difficulty of maintenance for them and not really add any value; plus Debian has different support lifecycles than what I would guess that Microsoft likely would want to follow. When you have software that updates pretty frequently and may evolve quickly, having their own package repo would allow them to more easily get packages for new versions available in a wider number of distros and not have to go through backports.

Guide for Debian Maintainers

24mu13 · 2024-10-12T07:43:09Z

What's about to maintain the Debian package in their ecosystem? https://www.debian.org/doc/manuals/debmake-doc/index.en.html
Do you think is feasible from licensing perspective?

Guide for Debian Maintainers

That would likely increase the difficulty of maintenance for them and not really add any value; plus Debian has different support lifecycles than what I would guess that Microsoft likely would want to follow. When you have software that updates pretty frequently and may evolve quickly, having their own package repo would allow them to more easily get packages for new versions available in a wider number of distros and not have to go through backports.

Guide for Debian Maintainers

I meant the community (us) would maintain it, not Microsoft; we saw in fact that Microsoft is not able neither to keep the very slow Debian lifecycle... I really appreciate their effort to embrace (and somehow "buy" actually) the open-source culture, but this doesn't necessarily mean to control every aspect of it: Debian has his own ecosystem, and I don't really see the value of having a separate Microsoft repository for maintaining various package systems...

Guide for Debian Maintainers

rhubarb-geek-nz · 2024-10-12T07:48:41Z

I am happy that Ubuntu repackages the dotnet-sdk and provides regular updates. I have asked Canonical to Add PowerShell to APT repository

Given Debian is a base for so many distributions and its pace, I don't think it is appropriate for either dotnet-sdk or PowerShell. The packages.microsoft.com generally does a good job providing up to date packages for Debian.

24mu13 · 2024-10-12T07:53:38Z

I am happy that Ubuntu repackages the dotnet-sdk and provides regular updates. I have asked Canonical to Add PowerShell to APT repository

Given Debian is a base for so many distributions and its pace, I don't think it is appropriate for either dotnet-sdk or PowerShell. The packages.microsoft.com generally does a good job providing up to date packages for Debian.

I don't get the point: are you happy with Ubuntu packages or Microsoft repository (or both)?

rhubarb-geek-nz · 2024-10-12T07:56:31Z

I don't get the point: are you happy with Ubuntu packages or Microsoft repository?

I am happy with packages.microsoft.com for Debian. But for Ubuntu, given it has already diverged by hosting dotnet-sdk and this project is very reluctant to produce a working Ubuntu package for 24.04, I suggest Ubuntu would be better for Ubuntu.

24mu13 · 2024-10-24T07:04:44Z

We've got the package finally! Thank you Microsoft

theJasonHelmick · 2024-10-29T17:35:00Z

This package is now available at PMC. For more information see the PMC Readme:
https://packages.microsoft.com/docs/readme.txt

We are still working on the docker image pipeline. I will post an update when we have published
images to the MCR.

theJasonHelmick · 2025-01-07T16:27:45Z

The Debian 12 distribution is released to PMC and MCR.

microsoft-github-policy-service · 2025-01-07T16:27:55Z

📣 Hey @Chouffy, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms

Chouffy added Distribution-Request Request for a new distribution support Needs-Triage The issue is new and needs to be triaged by a work group. labels Jul 4, 2023

Chouffy changed the title ~~Distribution Support Request~~ Distribution Support Request - Debian 12 Jul 13, 2023

StevenBucher98 mentioned this issue Nov 27, 2023

Distribution Support Request #20762

Closed

14 tasks

theJasonHelmick added this to Distribution Requests Feb 29, 2024

theJasonHelmick moved this to Requests in Distribution Requests Feb 29, 2024

theJasonHelmick self-assigned this Feb 29, 2024

theJasonHelmick removed the Needs-Triage The issue is new and needs to be triaged by a work group. label Feb 29, 2024

theJasonHelmick moved this from Requests to Backlog in Distribution Requests Feb 29, 2024

theJasonHelmick changed the title ~~Distribution Support Request - Debian 12~~ [DSR] - Debian 12 x64 Mar 7, 2024

similar-issues-ai bot mentioned this issue Sep 23, 2024

[DSR] - Debian 12 x64 #24334

Closed

14 tasks

theJasonHelmick reopened this Oct 1, 2024

theJasonHelmick added the KeepOpen The bot will ignore these and not auto-close label Oct 1, 2024

24mu13 mentioned this issue Oct 18, 2024

Make Powershell Core suitable for inclusion in Debian #5869

Open

This was referenced Nov 6, 2024

[DSR] - Alpine 3.20 x64 #24551

Closed

[DSR] - Alpine 3.20 arm64 #24552

Closed

theJasonHelmick closed this as completed Jan 7, 2025

github-project-automation bot moved this from Backlog to Done in Distribution Requests Jan 7, 2025

microsoft-github-policy-service bot removed the KeepOpen The bot will ignore these and not auto-close label Jan 7, 2025

[DSR] - Debian 12 x64 #19889

[DSR] - Debian 12 x64 #19889

Comments

Name of the Distribution

Version of the Distribution

Package Types

Processor Architecture

.NET Core Support

Distribution Requirements

Exemption Justification

Progress

For PowerShell Team ONLY

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!