-
Notifications
You must be signed in to change notification settings - Fork 132
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
[VMR] aspnetcore packages produced in VMR have incorrect prerelease versioning #4895
Comments
I've found the root cause, but I'm not sure what is the best option for a fix as it is related to the order of importing of Arcade SDK targets. The issue is that arcade SDK targets are imported late, so This is all caused by an override of
There are no such overrides in I think the following might be the options:
|
Yes, those two overrides are wrong: https://github.com/dotnet/aspnetcore/blob/9c410aaf1ef3db65374bf237589ae8bc6910d37c/Directory.Build.props#L282-L283 They should append to the property, not overwrite it, i.e. |
Thanks. I think they intentionally want their targets file to be imported before arcade SDK, so I'll keep theirs first and append the current property value:
|
This could be the case with repo produced packages as well - to be investigated.
For the repro build I've used this command:
./build.sh -t --ci --online /p:CrossBuild=true /p:TargetOS=linux /p:TargetArchitecture=x64 /bl
Docker container and command:
Here's a comparison of versioning for package and dependencies when prerelease versioning is used, i.e.
ci
. Notice a difference between-
and~
.Aspnet runtime:
SDK:
Runtime:
As a result,
aspnetcore-runtime
package cannot be installed with missing dependency error:User can force the installation using
--force-all
or similardpkg
option.The text was updated successfully, but these errors were encountered: