Skip to content
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

Make universal Deb package based on deb package spec #14681

Merged
merged 2 commits into from
Feb 2, 2021

Conversation

TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Jan 29, 2021

PR Summary

Try to make universal Deb package based on deb package spec

PR Context

Maybe?
fixes #13759

https://www.debian.org/doc/debian-policy/ch-relationships.html

the package names listed may also include lists of alternative package names, separated by vertical bar (pipe) symbols |

PR Checklist

@TravisEz13
Copy link
Member Author

verified on buster and 20.04.

@TravisEz13 TravisEz13 changed the title Try to make universal Deb package based on deb package spec Make universal Deb package based on deb package spec Jan 29, 2021
@anmenaga
Copy link
Contributor

Restarted CI for failed 'RemoteSession.Disconnect.Tests.ps1'

"zlib1g"
"zlib1g",
"libicu72|libicu71|libicu70|libicu69|libicu68|libicu67|libicu66|libicu65|libicu63|libicu60|libicu57|libicu55|libicu52",
"libssl1.1|libssl1.0.2|libssl1.0.0"
Copy link
Member

@JamesWTruher JamesWTruher Jan 29, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with this change it looks like we are eliminating the unsupported error when faced with a platform we don't understand. Does that mean we are relying on an error generated when the dependency is not found rather than a specific version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, basically, but that was only a build time error. Since the attempt here is to build a universal, package, keeping the error didn't make since.

If we hit a platform that has a missing dependency, then we should add it to the list if supported or not if the platform is not.

Copy link
Contributor

@anmenaga anmenaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving as maintainer based on Jim's review.

@anmenaga anmenaga merged commit 00b4b83 into PowerShell:master Feb 2, 2021
@TravisEz13 TravisEz13 deleted the fix-deb-11 branch February 2, 2021 22:47
@iSazonov iSazonov added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Feb 6, 2021
@iSazonov iSazonov added this to the 7.2.0-preview.3 milestone Feb 6, 2021
@ghost
Copy link

ghost commented Feb 12, 2021

🎉v7.2.0-preview.3 has been released which incorporates this pull request.:tada:

Handy links:

@ghost
Copy link

ghost commented Mar 11, 2021

🎉v7.0.6 has been released which incorporates this pull request.:tada:

Handy links:

@ghost
Copy link

ghost commented Mar 11, 2021

🎉v7.1.3 has been released which incorporates this pull request.:tada:

Handy links:

WamWooWam pushed a commit to WamWooWam/PowerShell that referenced this pull request Mar 16, 2021
WamWooWam added a commit to WamWooWam/PowerShell that referenced this pull request Mar 16, 2021
[7.1.3] - 2021-03-11

*** Engine Updates and Fixes

- Remove the 32K character limit on the environment block for `Start-Process` (PowerShell#14111)
- Fix webcmdlets to properly construct URI from body when using `-NoProxy` (PowerShell#14673)

*** General Cmdlet Updates and Fixes

- Fix `PromptForCredential()` to add `targetName` as domain (PowerShell#14504)

*** Build and Packaging Improvements

<details>

<summary>

Bump .NET SDK to 5.0.4

</summary>

<ul>
<li>Bump .NET SDK to 5.0.4 (Internal 14775)</li>
<li>Disable running markdown link verification in release build CI (PowerShell#14971, PowerShell#14974, PowerShell#14975)</li>
<li>Use template that disables component governance for CI (PowerShell#14938)</li>
<li>Declare which variable group is used for checking the blob in the release build (PowerShell#14970)</li>
<li>Add suppress for nuget multi-feed warning (PowerShell#14893)</li>
<li>Disable code signing validation where the file type is not supported (PowerShell#14885)</li>
<li>Install wget on <code>CentOS</code> 7 docker image (PowerShell#14857)</li>
<li>Fix install-dotnet download (PowerShell#14856)</li>
<li>Make universal Deb package based on deb package spec (PowerShell#14681)</li>
<li>Fix release build to upload global tool packages to artifacts (PowerShell#14620)</li>
<li>Update <code>ini</code> component version in test <code>package.json</code> (PowerShell#14454)</li>
<li>Add manual release automation steps and improve changelog script (PowerShell#14445)</li>
<li>Update markdown test packages with security fixes (PowerShell#14145)</li>
<li>Fix a typo in the <code>Get-ChangeLog</code> function (PowerShell#14129)</li>
<li>Disable global tool copy to unblock release</li>
</ul>

</details>

[7.1.3]: PowerShell/PowerShell@v7.1.2...v7.1.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport-7.0.x-Done BackPort-7.1.x-Done Backport to 7.1.x completed CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Debian 11 package has unsatisfied dependencies
5 participants