Skip to content

Build .rpm's for Mariner 2#40456

Merged
wtgodbe merged 2 commits intodotnet:mainfrom
wtgodbe:wtgodbe/mariner
Mar 1, 2022
Merged

Build .rpm's for Mariner 2#40456
wtgodbe merged 2 commits intodotnet:mainfrom
wtgodbe:wtgodbe/mariner

Conversation

@wtgodbe
Copy link
Member

@wtgodbe wtgodbe commented Feb 28, 2022

@wtgodbe wtgodbe requested a review from a team February 28, 2022 23:26
@wtgodbe wtgodbe requested a review from Pilchie as a code owner February 28, 2022 23:26
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Feb 28, 2022
Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

More broadly, what is the value of .deb and .rpm files with different names and no other changes❔ That is, is the requirement primarily a release issue❔

Comment on lines 16 to +17
<CblMarinerTargetFileName>$(RuntimeInstallerBaseName)-$(SharedFxVersion)-cm.1-x64.rpm</CblMarinerTargetFileName>
<CblMariner2TargetFileName>$(RuntimeInstallerBaseName)-$(SharedFxVersion)-cm.2-x64.rpm</CblMariner2TargetFileName>
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Might be worth setting $(CblMarinerTargetFileName), $(CblMariner2TargetFileName), $(CblMarinerTargetPath), and $(CblMariner2TargetPath) in the Directory.Build.props file. Could go further and elminate most of this <PropertyGroup/>, just set a $(RpmBaseName) property in the project files.

Copy link
Member Author

Choose a reason for hiding this comment

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

The arch is involved there for SharedFx but not Targeting Pack - I'll do that in the follow-up Linux Arm64 .rpm PR since that'll be dealing with arch anyways

@wtgodbe
Copy link
Member Author

wtgodbe commented Mar 1, 2022

More broadly, what is the value of .deb and .rpm files with different names and no other changes❔ That is, is the requirement primarily a release issue❔

Yeah, it's a release requirement. @NikolaMilosavljevic may be able to provide more detail

@wtgodbe
Copy link
Member Author

wtgodbe commented Mar 1, 2022

/backport to release/6.0

@github-actions
Copy link
Contributor

github-actions bot commented Mar 1, 2022

Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1918018830

@github-actions
Copy link
Contributor

github-actions bot commented Mar 1, 2022

@wtgodbe backporting to release/6.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Build .rpm's for Mariner 2
Using index info to reconstruct a base tree...
M	src/Installers/Rpm/Directory.Build.targets
M	src/Installers/Rpm/TargetingPack/Rpm.TargetingPack.rpmproj
Falling back to patching base and 3-way merge...
Auto-merging src/Installers/Rpm/TargetingPack/Rpm.TargetingPack.rpmproj
CONFLICT (content): Merge conflict in src/Installers/Rpm/TargetingPack/Rpm.TargetingPack.rpmproj
Auto-merging src/Installers/Rpm/Directory.Build.targets
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Build .rpm's for Mariner 2
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@wtgodbe wtgodbe merged commit 98641b0 into dotnet:main Mar 1, 2022
@ghost ghost added this to the 7.0-preview3 milestone Mar 1, 2022
@wtgodbe wtgodbe deleted the wtgodbe/mariner branch March 1, 2022 18:39
@NikolaMilosavljevic
Copy link
Member

More broadly, what is the value of .deb and .rpm files with different names and no other changes❔ That is, is the requirement primarily a release issue❔

Yeah, it's a release requirement. @NikolaMilosavljevic may be able to provide more detail

It gives on option for different signing certificate - an external requirement.

@ghost
Copy link

ghost commented Mar 1, 2022

Hi @NikolaMilosavljevic. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable packages for Mariner 2.0

3 participants