[Bug 2075185] Re: [SRU] Enable ppc64el for .NET 8 on Noble

Mateus Rodrigues de Morais 2075185 at bugs.launchpad.net
Wed Aug 14 12:36:57 UTC 2024


** Description changed:

  Upload available in PPA: https://launchpad.net/~dotnet-
- bootstrap/+archive/ubuntu/dotnet8.0.107-noble-stage2
+ bootstrap/+archive/ubuntu/dotnet8.0.108-noble-stage2
  
  [ Impact ]
  
-  * This SRU aims to enable the ppc64el architecture on .NET 8 targeting Ubuntu
-    24.04 (Noble Numbat). This architecture has already been enabled for .NET
-    8 on Oracular Oriole.
+  * This SRU aims to enable the ppc64el architecture on .NET 8 targeting Ubuntu
+    24.04 (Noble Numbat). This architecture has already been enabled for .NET
+    8 on Oracular Oriole.
  
-  * This came up as a request from IBM [0] and is now part of the .NET team's
-    roadmap for the Oracular Oriole cycle.
+  * This came up as a request from IBM [0] and is now part of the .NET team's
+    roadmap for the Oracular Oriole cycle.
  
-  * Per the changelog, the changes introduced in this upload are only related
-    to the enablement of ppc64el, with the exception of a d/copyright clean-up
-    to fix some lintian warnings.
+  * Per the changelog of the package in the PPA, the changes introduced in this 
+    upload are only related to the enablement of ppc64el.
  
  [ Test Plan ]
  
-  * On a ppc64el machine, run the steps outlined in the .NET SRU Test Plan
-    document [0].
+  * On a ppc64el machine, run the steps outlined in the .NET SRU Test Plan
+    document [1].
  
  [ Where problems could occur ]
  
-  * The changes introduced in this upload have already been tested by IBM [0]
-    in a PPA upload made available to them.
+  * The changes introduced in this upload have already been tested by IBM [0]
+    in a PPA upload made available to them.
  
-  * ppc64el has also been enabled for .NET 8.0.7 / 8.0.107 on Oracular.
+  * ppc64el has also been enabled for .NET 8 on Oracular.
  
-  * The patches introduced to fix various FTBFS and autopkgtest failures on
-    ppc64el are only modifying parameters in unit test projects within the .NET
-    code-base as well as the autopkgtest testrunner code-base and its related
-    libraries. These should impact no "shippable" product that lands in the
-    final binary packages.
+  * The patches introduced to fix various FTBFS and autopkgtest failures on
+    ppc64el are only modifying parameters in unit test projects within the .NET
+    code-base as well as the autopkgtest testrunner code-base and its related
+    libraries. These should not impact "shippable" products that land in the
+    final binary packages.
  
-  * If a problem occurs, it would be limited to .NET on ppc64el and will show
-    up when using the product with normal day-to-day operations, which the test
-    plan should be able to cover.
+  * If a problem occurs, it would be limited to .NET on ppc64el and will show
+    up when using the product with normal day-to-day operations, which the test
+    plan should be able to reproduce.
  
  [ Other Info ]
  
-  * The ppc64el build will require a bootstrap once it hits -proposed. The
-    bootstrap package has been prepared and is available in a PPA [2]. It will
-    be uploaded to the Ubuntu Bootstrap PPA by an Archive Admin once we're
-    ready to bootstrap.
+  * The ppc64el build will require a bootstrap once it hits -proposed. The
+    bootstrap package has been prepared and is available in a PPA [2]. It will
+    be uploaded to the Ubuntu Bootstrap PPA by an Archive Admin once we're
+    ready to bootstrap.
  
-  * When this upload hits -proposed, the ppc64el build will stay in dependency
-    wait status until the bootstrap package is uploaded and the Launchpad team
-    triggers the bootstrap. The .NET team (Toolchains/Foundations) will drive
-    the coordination of these tasks once we're there.
+  * When this upload hits -proposed, the ppc64el build will stay in dependency
+    wait status until the bootstrap package is uploaded and the Launchpad team
+    triggers the bootstrap. The .NET team (Toolchains/Foundations) will drive
+    the coordination of these tasks once we're there.
  
  [0] https://bugs.launchpad.net/ubuntu/noble/+source/dotnet8/+bug/2064530
- [1] https://launchpad.net/~dotnet-bootstrap/+archive/ubuntu/dotnet8.0.107-noble-stage1-ppc64el
- [2] https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md
+ [1] https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md
+ [2] https://launchpad.net/~dotnet-bootstrap/+archive/ubuntu/dotnet8.0.107-noble-stage1-ppc64el

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dotnet8 in Ubuntu.
https://bugs.launchpad.net/bugs/2075185

Title:
  [SRU] Enable ppc64el for .NET 8 on Noble

Status in dotnet8 package in Ubuntu:
  New
Status in dotnet8 source package in Noble:
  New

Bug description:
  Upload available in PPA: https://launchpad.net/~dotnet-
  bootstrap/+archive/ubuntu/dotnet8.0.108-noble-stage2

  [ Impact ]

   * This SRU aims to enable the ppc64el architecture on .NET 8 targeting Ubuntu
     24.04 (Noble Numbat). This architecture has already been enabled for .NET
     8 on Oracular Oriole.

   * This came up as a request from IBM [0] and is now part of the .NET team's
     roadmap for the Oracular Oriole cycle.

   * Per the changelog of the package in the PPA, the changes introduced in this 
     upload are only related to the enablement of ppc64el.

  [ Test Plan ]

   * On a ppc64el machine, run the steps outlined in the .NET SRU Test Plan
     document [1].

  [ Where problems could occur ]

   * The changes introduced in this upload have already been tested by IBM [0]
     in a PPA upload made available to them.

   * ppc64el has also been enabled for .NET 8 on Oracular.

   * The patches introduced to fix various FTBFS and autopkgtest failures on
     ppc64el are only modifying parameters in unit test projects within the .NET
     code-base as well as the autopkgtest testrunner code-base and its related
     libraries. These should not impact "shippable" products that land in the
     final binary packages.

   * If a problem occurs, it would be limited to .NET on ppc64el and will show
     up when using the product with normal day-to-day operations, which the test
     plan should be able to reproduce.

  [ Other Info ]

   * The ppc64el build will require a bootstrap once it hits -proposed. The
     bootstrap package has been prepared and is available in a PPA [2]. It will
     be uploaded to the Ubuntu Bootstrap PPA by an Archive Admin once we're
     ready to bootstrap.

   * When this upload hits -proposed, the ppc64el build will stay in dependency
     wait status until the bootstrap package is uploaded and the Launchpad team
     triggers the bootstrap. The .NET team (Toolchains/Foundations) will drive
     the coordination of these tasks once we're there.

  [0] https://bugs.launchpad.net/ubuntu/noble/+source/dotnet8/+bug/2064530
  [1] https://github.com/canonical/dotnet-source-build/blob/main/docs/SRUTestPlan.md
  [2] https://launchpad.net/~dotnet-bootstrap/+archive/ubuntu/dotnet8.0.107-noble-stage1-ppc64el

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dotnet8/+bug/2075185/+subscriptions




More information about the foundations-bugs mailing list