-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Distribution Support Request for Debian 11 #10923
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
Comments
I'll add Docker image in a few minutes |
waiting for this to be out officially |
@TravisEz13 Since debian 11 is out couple of months back, Can we push the package to packages.microsoft.com ? |
PR created, and I moved the file that maps the packages into the repos into the PowerShell/PowerShell repo so people can update this themselves. |
Thanks for the swift response @TravisEz13. I don't get this part "so people can update this themselves.". Will the next version of powershell automatically pushed to packages.microsoft.com debian 11 repo? |
When we release, packages are pushed. the mapping file, says which repo's to release to. It was in a private repo and the code to push still is, but this file says which package to push to which repo and the repo names are usually just the codename for the distribution. If all the check boxes are checked before |
For reference, this is the only entry that is new in the mapping file: https://github.com/PowerShell/PowerShell/blob/master/tools/packages.microsoft.com/mapping.json#L38-L41
|
For this to be supported, we still need to test the mapping file 😮💨. So, we will release it in 7.3.0-preview.1 and verify that packages.microsoft.com didn't do anything wrong. If they did, we will probably fix it during that release. Then we can backport to 7.2. |
@sdwheeler We have been shipping this distro for some time now. We should add documentation for this in the install docs. We have it supported for PowerShell version 7.2.0+. |
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
2 similar comments
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you. |
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes. |
Details of the Distribution
Please write a justification for any exception where these criteria are not met and
the PowerShell comittee will review the request.
Progress - For PowerShell Team ONLY
packages.microsoft.com
deploymentThe text was updated successfully, but these errors were encountered: