[Bug 2072490] Re: [needs-packaging] U-Boot for Microchip PIC64GX

[Łukasz Zemczak]

I have reviewed this package. It seems more or less similar to the
-nezha one structurally, so that's fine. But before I accept it into
Ubuntu I'd like to know a bit more about the orig tarball. Where does
this tarball come from? I see the 20240624 versioning, but on the
repository mentioned in debian/control
(https://github.com/pic64gx/pic64gx-uboot/tags) I only see
v2024.06.tar.gz. Is that this release? Why is the versioning different?
How will we convert those? How can we guarantee that the release tarball
is 1:1 what is officially from upstream if it's repacked and
reversioned?

** Changed in: ubuntu
       Status: New => Incomplete

-- 
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/2072490

Title:
  [needs-packaging] U-Boot for Microchip PIC64GX

Status in Ubuntu:
  Incomplete

Bug description:
  We want to support the upcoming Microchip PIC64GX board. Unfortunately
  upstreaming of U-Boot has not started yet. Due to the number of
  differences between our U-Boot 2024.01 and the vendor U-Boot it is not
  trivial to add board support to our existing U-Boot. The best interim
  solution is packaging the vendor U-Boot. Once upstreaming has occurred
  we can sun-set the vendor U-Boot package and replace it by the u-boot-
  microchip package.

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