[Bug 1761611] [NEW] Incorrect dtb backup file

[Adam Smith]

Public bug reported:

Testing the latest 18.04 raspberry server image on my pi 3.  I upgraded
the kernel to the proposed version (from 4.13* to 4.15*).  Backups of
the vmlinuz, initrd.img and dtb files were made on the system-boot
partition automatically by flash-kernel.

However, on closer inspection the bcm2709-rpi-2-b.dtb and
bcm2709-rpi-2-b.dtb.bak files were the same file.  Similarly the
bcm2710-rpi-2-b.dtb and bcm2710-rpi-2-b.dtb.bak were the same.  These
files had changed between the 4.13* and 4.15* kernels and so they
shouldn't be the same.  Both the .dtb and .dtb.bak are from the latest
kernel (4.15*).

The vmlinuz.bak and initrd.img.bak were correct.

** Affects: flash-kernel (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  Incorrect dtb backup file

Status in flash-kernel package in Ubuntu:
  New

Bug description:
  Testing the latest 18.04 raspberry server image on my pi 3.  I
  upgraded the kernel to the proposed version (from 4.13* to 4.15*).
  Backups of the vmlinuz, initrd.img and dtb files were made on the
  system-boot partition automatically by flash-kernel.

  However, on closer inspection the bcm2709-rpi-2-b.dtb and
  bcm2709-rpi-2-b.dtb.bak files were the same file.  Similarly the
  bcm2710-rpi-2-b.dtb and bcm2710-rpi-2-b.dtb.bak were the same.  These
  files had changed between the 4.13* and 4.15* kernels and so they
  shouldn't be the same.  Both the .dtb and .dtb.bak are from the latest
  kernel (4.15*).

  The vmlinuz.bak and initrd.img.bak were correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1761611/+subscriptions