I added 'ca-certificates' to the Build-Depends, and although on sbuild got stuck again (I have it configured to not use internet), I was able to build your package inside the chroot.
Checking the log, the nuget packages that are being downloaded are:
Therefore, for future buildings using latest dotnet packages, you should update your dotnet-cli-home.tar file with those nuget packages according to the runtime/sdk you can/want to use for building.
I hope this will help you with your following buildings.
I'm going to mark the bug as Invalid because it doesn't appear to be a bug, but if I'm wrong, please change it back to "New" and add some more info to point me in the right direction. Use this link as a guide: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Hi Maia,
I went deeper into debugging, out of curiosity.
I added 'ca-certificates' to the Build-Depends, and although on sbuild got stuck again (I have it configured to not use internet), I was able to build your package inside the chroot.
Checking the log, the nuget packages that are being downloaded are:
(jammy- amd64-sbuild) root@Camelot- TITAN:/ build/xivlaunch er-core- G9yMNb# grep GET rules-build.log | grep nupkg
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. netcore. app.host. osx-x64/ 6.0.11/ microsoft. netcore. app.host. osx-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. netcore. app.host. linux-x64/ 6.0.11/ microsoft. netcore. app.host. linux-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. netcore. app.host. win-x64/ 6.0.11/ microsoft. netcore. app.host. win-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. aspnetcore. app.runtime. osx-x64/ 6.0.11/ microsoft. aspnetcore. app.runtime. osx-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. aspnetcore. app.runtime. linux-x64/ 6.0.11/ microsoft. aspnetcore. app.runtime. linux-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. aspnetcore. app.runtime. win-x64/ 6.0.11/ microsoft. aspnetcore. app.runtime. win-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. netcore. app.runtime. osx-x64/ 6.0.11/ microsoft. netcore. app.runtime. osx-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. netcore. app.runtime. linux-x64/ 6.0.11/ microsoft. netcore. app.runtime. linux-x64. 6.0.11. nupkg (TaskId:56)
GET https:/ /api.nuget. org/v3- flatcontainer/ microsoft. netcore. app.runtime. win-x64/ 6.0.11/ microsoft. netcore. app.runtime. win-x64. 6.0.11. nupkg (TaskId:56)
If you check your nuget tarball, you have predownloaded those packages there, but for the previous runtime version (in your case, the 8th):
❯ tar -tf dotnet-cli-home.tar | grep -E "6.0.8.nupkg$"
dotnet- cli-home/ .nuget/ packages/ microsoft. aspnetcore. app.runtime. win-x64/ 6.0.8/microsoft .aspnetcore. app.runtime. win-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. netcore. app.host. win-x64/ 6.0.8/microsoft .netcore. app.host. win-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. aspnetcore. app.runtime. osx-x64/ 6.0.8/microsoft .aspnetcore. app.runtime. osx-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. netcore. app.runtime. win-x64/ 6.0.8/microsoft .netcore. app.runtime. win-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. netcore. app.host. linux-x64/ 6.0.8/microsoft .netcore. app.host. linux-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. aspnetcore. app.runtime. linux-x64/ 6.0.8/microsoft .aspnetcore. app.runtime. linux-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. netcore. app.runtime. osx-x64/ 6.0.8/microsoft .netcore. app.runtime. osx-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. netcore. app.runtime. linux-x64/ 6.0.8/microsoft .netcore. app.runtime. linux-x64. 6.0.8.nupkg cli-home/ .nuget/ packages/ microsoft. netcore. app.host. osx-x64/ 6.0.8/microsoft .netcore. app.host. osx-x64. 6.0.8.nupkg
dotnet-
dotnet-
dotnet-
dotnet-
dotnet-
dotnet-
dotnet-
dotnet-
Therefore, for future buildings using latest dotnet packages, you should update your dotnet-cli-home.tar file with those nuget packages according to the runtime/sdk you can/want to use for building.
I hope this will help you with your following buildings.
I'm going to mark the bug as Invalid because it doesn't appear to be a bug, but if I'm wrong, please change it back to "New" and add some more info to point me in the right direction. Use this link as a guide: http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html