[Bug 2058594] Re: Sync rocr-runtime 5.7.1-2 (universe) from Debian unstable (main)

[Benjamin Drung]

This bug was fixed in the package rocr-runtime - 5.7.1-2
Sponsored for Cory Bloor (slavik81)

---------------
rocr-runtime (5.7.1-2) unstable; urgency=medium

  * Migrate to unstable.

 -- Cordell Bloor <cgmb at slerp.xyz>  Mon, 18 Mar 2024 18:46:07 -0600

rocr-runtime (5.7.1-2~exp1) experimental; urgency=medium

  * Add d/p/0003-expand-endian-detection.patch to fix arm64 and ppc64el
    endianness detection logic.
  * Add d/p/0006-initialize-chip-revision.patch to fix failing assertions
    on Rembrandt hardware.
  * Add d/gbp.conf to ensure use of pristine-tar.

 -- Cordell Bloor <cgmb at slerp.xyz>  Sun, 17 Mar 2024 23:51:29 -0600

** Changed in: rocr-runtime (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2058594

Title:
  Sync rocr-runtime 5.7.1-2 (universe) from Debian unstable (main)

Status in rocr-runtime package in Ubuntu:
  Fix Released

Bug description:
  Please sync rocr-runtime 5.7.1-2 (universe) from Debian unstable
  (main)

  The 5.7.1-2 version of the package should allow rccl to build
  successfully on arm64 and ppc64el. It should also fix HIP on Rembrandt
  APUs (gfx1035), which was completely broken in 5.7.1-1 (as illustrated
  on Debian by the rocblas test history
  https://ci.rocm.debian.net/packages/r/rocblas/unstable/amd64+gfx1035/).

  
  # Debian changes from sync

  rocr-runtime (5.7.1-2) unstable; urgency=medium

    * Migrate to unstable.

   -- Cordell Bloor <cgmb at slerp.xyz>  Mon, 18 Mar 2024 18:46:07 -0600

  rocr-runtime (5.7.1-2~exp1) experimental; urgency=medium

    * Add d/p/0003-expand-endian-detection.patch to fix arm64 and ppc64el
      endianness detection logic.
    * Add d/p/0006-initialize-chip-revision.patch to fix failing assertions
      on Rembrandt hardware.
    * Add d/gbp.conf to ensure use of pristine-tar.

  
  # Changes in noble-proposed that would be lost from sync

  rocr-runtime (5.7.1-1build1) noble; urgency=medium

    * No-change rebuild against libelf1t64

  It should be fine to lose this Ubuntu revision, as the sync will cause
  a rebuild anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rocr-runtime/+bug/2058594/+subscriptions