Update the EGL headers as per AMD-Xilinx's request

[ethan.hsieh]

[Impact]
Update the EGL headers as per AMD-Xilinx's request

[Where problems could occur]
Update the EGL headers as per AMD-Xilinx's request

[Test Case]
jammy + Xilinx Kria board: Pass
System can boot to desktop with the new package.

[Regression Potential]
https://github.com/Xilinx/mali-userspace-binaries/tree/xilinx_v2022.1
Update libegl-mali-xlnx to tag xilinx_v2022.1.
AMD-Xilinx has reviewed the change and verified xilinx_v2022.1

[Other Info]
See LP: #1971665

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "kinetic.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

[ethan.hsieh (ethan.hsieh)]

Re-create debdiff based on 9p0.01rel0-1ubuntu2 for jammy

[Łukasz Zemczak (sil2100)]

hm, any reasons why both the kinetic and jammy version numbers have a debian revision number? I don't see this package in Debian. Is it there with a different version number?

By 'debian revision number' I mean the X part in the -XubuntuY version. The general versioning scheme is as follows: <UPSTREAM VERSION>-<DEBIAN REVISION>ubuntu<UBUNTU REVISION>. For packages that are not available in Debian or, if they are but Ubuntu has an upstream version that Debian does not, the <DEBIAN REVISION> needs to be 0. Otherwise it's just confusing.

Am I missing something here?

[ethan.hsieh (ethan.hsieh)]

@Łukas

Sorry. I didn't aware that the second field is <DEBIAN REVISION>.
What I thought is <UPSTREAM VERSION>-<AMD-Xilinx REVISION>ubuntu<UBUNTU REVISION>.

AMD-Xilinx got libraries and header files from ARM. The version number is 9p0.01rel0. AMD-Xilinx updated one header file but the upstream version number in github[1] is still the same. The header file was not modified by Canonical. So, I updated the version number to 9p0.01rel0-1ubuntu1 instead of 9p0.01rel0-0ubuntu6.

The version number in kinetic is already 9p0.01rel0-1ubuntu2. Any suggestion to correct it?

---
[1] https://github.com/Xilinx/mali-userspace-binaries/tree/xilinx_v2022.1

[ethan.hsieh (ethan.hsieh)]

@Łukas

Bump libegl-mali-xlnx's version on kinetic from 9p0.01rel0-1ubuntu2 to 9p0.01rel0-1-0ubuntu2 and then backport it to jammy. Any concern about it?

[Łukasz Zemczak (sil2100)]

Hey Ethan! If the -1 is part of the upstream version, then I am +1 on the proposed versioning of 9p0.01rel0-1-0ubuntu2 for the kinetic version. The final dash always denotes the 'downstream' revisions in non-native packages, so it should all be good this way.

Let's proceed.

[ethan.hsieh (ethan.hsieh)]

@Łukasz
I uploaded debdiff to bump version. Please see the attached file.

[Łukasz Zemczak (sil2100)]

Hello ethan.hsieh, or anyone else affected,

Accepted libegl-mali-xlnx into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libegl-mali-xlnx/9p0.01rel0-1-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.

[Łukasz Zemczak (sil2100)]

Sponsored for both kinetic and jammy.

[ethan.hsieh (ethan.hsieh)]

Can boot to desktop and run es2gears_x11 without any problems after upgrading libegl-mali-xlnx to 9p0.01rel0-1-0ubuntu1~22.04.1.

$ apt-cache policy libegl-mali-xlnx | grep Installed
  Installed: 9p0.01rel0-1-0ubuntu1~22.04.1

---
Board: KR260

[Launchpad Janitor (janitor)]

This bug was fixed in the package libegl-mali-xlnx - 9p0.01rel0-1-0ubuntu1~22.04.1

---------------
libegl-mali-xlnx (9p0.01rel0-1-0ubuntu1~22.04.1) jammy; urgency=medium

  * SRU to jammy (LP: #1976225).

libegl-mali-xlnx (9p0.01rel0-1-0ubuntu1) kinetic; urgency=medium

  * Bump version to 9p0.01rel0-1-0ubuntu1

    The package is not available in Debian. AMD-Xilinx got files from ARM.
    The source of this packages is AMD-Xilinx public git repo.
    9p0.01rel0-1: <ARM version>-<AMD-Xilinx version>

libegl-mali-xlnx (9p0.01rel0-1ubuntu2) kinetic; urgency=medium

  * Use an upstream for non-native package; this one is based on the GitHub
    generated tarball for the xilinx_v2021.1_update1 tag.
  * debian/copyright: replace tabs with spaces per policy.
  * preinst/postrm: add #DEBHELPER# stanza.
  * environment.d: move to debian/ as this is part of the packaging.
  * install: avoid unofficial brace expansion.

libegl-mali-xlnx (9p0.01rel0-1ubuntu1) kinetic; urgency=medium

  * Rebuild for kinetic
  * EGL: eglplatform.h: Update the EGL headers from khronos. Files from
    https://github.com/Xilinx/mali-userspace-binaries/tree/xilinx_v2022.1
    xilinx_v2022.1 git tag, based on based r9p0-01rel0 release.

 -- Ethan Hsieh <email address hidden> Tue, 07 Jun 2022 05:13:45 +0000

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for libegl-mali-xlnx has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.