8000 [DSR] - Debian 12 x64 · Issue #24334 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]

Skip to content

[DSR] - Debian 12 x64 #24334

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

Closed
4 of 14 tasks
masterflitzer opened this issue Sep 23, 2024 · 11 comments
Closed
4 of 14 tasks

[DSR] - Debian 12 x64 #24334

masterflitzer opened this issue Sep 23, 2024 · 11 comments
Labels
Distribution-Request Request for a new distribution support

Comments

@masterflitzer
Copy link

Name of the Distribution

Debian

Version of the Distribution

12

Package Types

  • Deb
  • RPM
  • Tar.gz
  • Snap - Stop! Please file your issue in PowerShell-Snap instead.

Processor Architecture

amd64

.NET Core Support

Distribution Requirements

  • The version of the Distribution is supported for at least one year.
  • The version of the Distribution is not an interim release or equivalent.

Exemption Justification

No response

Progress

For PowerShell Team ONLY

  • Docker image created
  • Docker image published
  • Distribution tested
  • Update packages.microsoft.com deployment
  • Lifecycle updated
  • Documentation Updated
@masterflitzer masterflitzer 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 Sep 23, 2024
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@masterflitzer
Copy link
Author
masterflitzer commented Sep 23, 2024

#19889 was in fact not solved, because instead of deb (apt repo on packages.microsoft.com) a docker distribution was published (even though the docker checkbox was not checked)

@kasini3000
Copy link
kasini3000 commented Sep 23, 2024

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

apt install libicu72
curl  https://github.com/PowerShell/PowerShell/releases/download/v7.4.5/powershell_7.4.5-1.deb_amd64.deb
dpkg -i ./powershell_7.4.5-1.deb_amd64.deb
echo 'Subsystem powershell /usr/bin/pwsh -sshs -NoLogo -NoProfile' >>  /etc/ssh/sshd_config
echo 'UseDNS no' >>  /etc/ssh/sshd_config
echo 'PermitRootLogin yes' >>  /etc/ssh/sshd_config
systemctl restart ssh.service

kasini3000:
powershell win,linux devops automation batch script framework.(It is similar to Puppet,Ansible,pipeline)
Open source, free, cross-platform,Transferring PowerShell objects through Winrm and SSH between multiple clouds

English manual:
https://gitee.com/chuanjiao10/kasini3000/blob/master/docs/kasini3000_manual.xlsx

tech:
https://www.cnblogs.com/piapia/p/16534765.html

@AndrewSav
Copy link

echo 'PermitRootLogin yes' >> /etc/ssh/sshd_config

This can potentially be a groundwork for an exploit, as this appears in a highly visible repo. I suggest removing the unsafe code from this post

@masterflitzer
Copy link
Author

@kasini3000 this is off-topic as it has nothing to to with this issue, this issue is a DSR (distribution support request)

@kasini3000
Copy link

@masterflitzer
1 see firest ai bot post, DSR does not receive a return in a short period of time, so the best way is 'off-topic ' now.

2 It seems that you are not here to seek third-party help ,
right and normal way is: so please do not REPEATED submission the DSR.

@masterflitzer
8000 Copy link
Author

issues are for tracking project related tasks, not for seeking help

the issue was wrongfully closed as completed without being completed, it's reasonable to make a new issue for tracking purposes, if this is not wished by powershell team they can close this

what you are showing has nothing to do with distribution, ssh is off topic this is the pwsh repo, the current best way is to use debian 11 repo on debian 12 and then apt install powershell (apt preferences allow to change priority to -1 for everything other than the powershell package to limit side effects)

(also these last few messages including this one should be hidden as off topic by a repo maintainer, but that's what happens when people like you @kasini3000 don't know how to behave on github)

@kasini3000
Copy link

hi all:
kasini3000 offline installations, it's so powerful that I:
1 It is based on tar.gz file and does not need to consider differences in rpm and apt package.
2 tar.gz files do not need to consider subtle version differences between debian11 and debian12
3 No need to request DSR from PS team!!!, There is no need to wait for the release package on package.microsoft.com, even support future releases (eg:debian13).
I'm not going to ask for something from PSTeam, but rather provide a solution
You should do the same. The PS team has limited energy, don't let them trouble you.
4 Installing to 1000 linux server only requires one download.
Write a script and call my script, Used to add the following features:
5.1 Can be multi-threaded, multi process,
5.2 Can control the number of concurrent installations.
5.3 Add some minor adjustments, such as installing pre installed libraries.
6 There are two scripts here, one for root password and the other for ssh key:
https://gitee.com/chuanjiao10/kasini3000/blob/master/zkj_install_powershell_offline_win2linux_keyfile.ps1
https://gitee.com/chuanjiao10/kasini3000/blob/master/zkj_install_powershell_offline_win2linux_pwd_winscp.ps1

Don't tell me that the topic is irrelevant , Once you use it, you don't need to request DSR(it seems to be most new, unsupported Linux distributions),
and installing multiple devices doesn't require any bandwidth usage on package.microsoft.com.
So I think this is the best way.

May I ask those who oppose me, What solution have you provided?

@mbentley
Copy link

@kasini3000 - you're not being helpful here so I would suggest that you stop. It is irrelevant because they do provide packages through common software repositories and in case you missed it, they have a specific issue template for a GitHub issue to request a new package repository. You're opposing that by providing workarounds. There is a purpose to package managers and handling updates in a single, common way. If you had to handle all of your software updates as one offs, you lose the benefit of a package manager. Why not just run Linux from Scratch at that point.

Does your solution work? I guess - I haven't looked because it's irrelevant. Your claim of "You should do the same. The PS team has limited energy, don't let them trouble you." is strange and just incorrect. If someone in the community could just create a pull request with whatever is needed to create the repository, it probably would have been done day 1 but that doesn't seem to be the case. So please stop wasting everyone's time with your workarounds because they are just that - workarounds that nobody cares about and nobody asked for as the same concepts have already been discussed in #19889

@masterflitzer
Copy link
Author

closed in favor of the reopened #19889

Copy link
Contributor
microsoft-github-policy-service bot commented Oct 1, 2024

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

🔗 https://aka.ms/PSRepoFeedback

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Triage The issue is new and needs to be triaged by a work group. label Oct 1, 2024
This was referenced Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Distribution-Request Request for a new distribution support
Projects
None yet
Development

No branches or pull requests

4 participants
0