Backport .NET 8 to jammy

Bug #2046133 reported by Dominik Viererbe
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dotnet8 (Ubuntu)
Fix Released
Undecided
Dominik Viererbe
Jammy
Fix Released
Undecided
Dominik Viererbe

Bug Description

[Impact]

As part of the Ubuntu LTS startegy we want to backport .NET 8 to jammy from mantic.

This is a tracking bug.

[Test Case]

Checking that dotnet8 is usable in jammy.

[Regression Potential]

None, new package.

Changed in dotnet8 (Ubuntu):
status: New → In Progress
assignee: nobody → Dominik Viererbe (dviererbe)
Changed in dotnet8 (Ubuntu Jammy):
status: New → In Progress
assignee: nobody → Dominik Viererbe (dviererbe)
Revision history for this message
Dominik Viererbe (dviererbe) wrote :
tags: added: foundations-todo
Revision history for this message
Graham Inggs (ginggs) wrote :

I uploaded the backport from 8.0.100-8.0.0-0ubuntu1~23.10.1 in mantic with changes to the changelog (as discussed with dviererbe):

dotnet8 (8.0.100-8.0.0-0ubuntu1~22.04.1) jammy; urgency=medium

  * Backport to Ubuntu 22.04 LTS Jammy Jellyfish (LP: #2046133).
    - d/control: change dotnet-runtime-8.0 Depends from libicu72 to libicu70

 -- Dominik Viererbe <email address hidden> Mon, 11 Dec 2023 08:02:06 +0200

Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Dominik, or anyone else affected,

Accepted dotnet8 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dotnet8/8.0.100-8.0.0-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

description: updated
Changed in dotnet8 (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Changed in dotnet8 (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Dominik Viererbe (dviererbe) wrote :

Added block-proposed-jammy as the next security update (8.0.2) will release on February 13th. Ian will use the build in proposed to build 8.0.1 and 8.0.2 in a security PPA. Therefore 8.0.2 will be the GA of dotnet8 on jammy.

tags: added: block-proposed-jammy
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (dotnet8/8.0.100-8.0.0-0ubuntu1~22.04.1)

All autopkgtests for the newly accepted dotnet8 (8.0.100-8.0.0-0ubuntu1~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dotnet6/6.0.126-0ubuntu1~22.04.1 (amd64, arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#dotnet8

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Changed in dotnet8 (Ubuntu):
status: Fix Committed → Fix Released
Changed in dotnet8 (Ubuntu Jammy):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.