Closed
Description
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:
Package: aspnetcore-runtime-10.0
Version: 10.0.0~
Depends: dotnet-runtime-10.0 (>= 10.0.0-ci)
Description: Microsoft.AspNetCore.App.Runtime 10.0.0~
SDK:
Package: dotnet-sdk-10.0
Version: 10.0.100~ci
Depends: dotnet-runtime-10.0 (>= 10.0.0~ci), dotnet-targeting-pack-10.0 (>= 10.0.0~ci), dotnet-apphost-pack-10.0 (>= 10.0.0~ci), netstandard-targeting-pack-2.1 (>= 2.1.0), aspnetcore-runtime-10.0 (>= 10.0.0~ci), aspnetcore-targeting-pack-10.0 (>= 10.0.0~ci)
Description: Microsoft .NET SDK 10.0.100-ci
Runtime:
Package: dotnet-runtime-10.0
Version: 10.0.0~ci
Depends: dotnet-hostfxr-10.0 (>= 10.0.0~ci), dotnet-runtime-deps-10.0 (>= 10.0.0~ci)
Description: Microsoft.NETCore.App.Runtime.CoreCLR 10.0.0~ci
As a result, aspnetcore-runtime
package cannot be installed with missing dependency error:
dpkg: dependency problems prevent configuration of aspnetcore-runtime-10.0:
aspnetcore-runtime-10.0 depends on dotnet-runtime-10.0 (>= 10.0.0-ci); however:
Version of dotnet-runtime-10.0 on system is 10.0.0~ci.
User can force the installation using --force-all
or similar dpkg
option.
Metadata
Metadata
Assignees
Type
Projects
Status
Done
Status
Done