Your message dated Thu, 29 Nov 2018 01:07:23 +0000
with message-id <[email protected]>
and subject line Bug#910790: fixed in raspi3-firmware 1.20181112-1
has caused the Debian Bug report #910790,
regarding new initrd file was not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
910790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910790
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20180619-1
Severity: normal

Hi!

When installing linux-image-4.18.0-2-arm64 having installed
linux-image-4.18.0-1-arm64 I ended up without the proper -2 initrd  on
/boot/firmware, only the -1 initrd was seen by raspi3-firmware, so after the
installation I was left with:
# grep initrd /boot/firmware/config.txt
initramfs initrd.img-4.18.0-1-arm64
# ls /boot/firmware/initrd.img*
/boot/firmware/initrd.img-4.18.0-1-arm64

I believe this is because of the order of the scripts at 
/etc/kernel/postinst.d/:
# ls /etc/kernel/postinst.d/
50raspi3-firmware  apt-auto-removal  initramfs-tools  unattended-upgrades

The output of the apt-get install linux-image-4.18.0-2-arm64 command was:
Selecting previously unselected package linux-image-4.18.0-2-arm64.
(A ler a base de datos ... 27832 files and directories currently installed.)
Preparing to unpack .../linux-image-4.18.0-2-arm64_4.18.10-2_arm64.deb ...
Unpacking linux-image-4.18.0-2-arm64 (4.18.10-2) ...
A configurar linux-image-4.18.0-2-arm64 (4.18.10-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.18.0-2-arm64
raspi3-firmware: deferring update via initramfs-tools (hook will be called 
later by the kernel

Hope this helps.

Regards.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 4.18.0-1-arm64 (SMP w/4 CPU cores)
Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=gl_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages raspi3-firmware depends on:
ii  dosfstools  4.1-2

raspi3-firmware recommends no packages.

raspi3-firmware suggests no packages.

-- Configuration Files:
/etc/kernel/postinst.d/50raspi3-firmware changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: raspi3-firmware
Source-Version: 1.20181112-1

We believe that the bug you reported is fixed in the latest version of
raspi3-firmware, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gunnar Wolf <[email protected]> (supplier of updated raspi3-firmware package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 27 Aug 2018 19:00:06 -0500
Source: raspi3-firmware
Binary: raspi3-firmware
Architecture: source
Version: 1.20181112-1
Distribution: unstable
Urgency: medium
Maintainer: pkg-raspi <[email protected]>
Changed-By: Gunnar Wolf <[email protected]>
Description:
 raspi3-firmware - Raspberry Pi 2 and 3 GPU firmware and bootloaders
Closes: 897234 903543 910790
Changes:
 raspi3-firmware (1.20181112-1) unstable; urgency=medium
 .
   [ Gunnar Wolf ]
   * Added support for installing the 3B+ firmware
   * Add configurable options for cmdline.txt (Closes: #903543)
   * Add brcm80211/brcmfmac43430-sdio.txt,
     brcm80211/brcmfmac43455-sdio.txt  and brcm80211/brcmfmac43455.clm_blob
     via a quilt patch, to solve the issue of uscan not providing a full
     tarball to work from. Thanks to Romain Perier for his help! (Closes: 
#897234)
   * Make sure that firmware hooks get triggered after initrd hooks
     (Closes: #910790). Thanks to Matthias Lüscher!
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/rules: Remove trailing whitespaces
 .
   [ Romain Perier ]
   * Encode the files to be excluded from the orig.tar.gz in d/copyright so
     that uscan produces a suitable tarball
Checksums-Sha1:
 7eb377d9336d5126859334656191cd7a6ea41eae 2095 raspi3-firmware_1.20181112-1.dsc
 0a36e65bdd9575ea9cb3b869c9daf8d9fa5adbd6 16578608 
raspi3-firmware_1.20181112.orig.tar.gz
 653249a3049420097c6a2ccfd9f3c375e3256bcf 22492 
raspi3-firmware_1.20181112-1.debian.tar.xz
 7d319607c3e0ab9c73d4c38ae3f6a6ece99e7b7d 6922 
raspi3-firmware_1.20181112-1_source.buildinfo
Checksums-Sha256:
 099b4edf44e1c48ee706463f01e552257bd566461b56b78e5d6c42977184e0ad 2095 
raspi3-firmware_1.20181112-1.dsc
 08511cf9117858e47a5ef8c6b9601a4edcb95541082fc525a6cb436da6167032 16578608 
raspi3-firmware_1.20181112.orig.tar.gz
 9d91e1f4ba39f0439274f61c9a3a76036390cf9e2096a09f61f60b35c61dfa2c 22492 
raspi3-firmware_1.20181112-1.debian.tar.xz
 a853ae87a689c1e74447b2183dadca4482bfa170f0776b24952c35e1bcccb6ba 6922 
raspi3-firmware_1.20181112-1_source.buildinfo
Files:
 9e414d3e4505c77d7b6c4f79032aa10a 2095 non-free/misc optional 
raspi3-firmware_1.20181112-1.dsc
 8c9ec39a1f38bbb1f6d057b3ac41541a 16578608 non-free/misc optional 
raspi3-firmware_1.20181112.orig.tar.gz
 418b0a6cf219518a79ef5318ab1d7cf4 22492 non-free/misc optional 
raspi3-firmware_1.20181112-1.debian.tar.xz
 b457643ba81b0c373f9a427f8c8399bd 6922 non-free/misc optional 
raspi3-firmware_1.20181112-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEfHleU5lojd9m99YgSd0qTkl5YZwFAlv/NeYACgkQSd0qTkl5
YZzEaA//WqpzCqlAf8fdFQuzJDRKv7a2zoFoMl5tv/4VSfemanccG4MnHA7mhcGZ
no23yMx1D+dW+483r53NkP6/FEhiaDJ6yoZ5LbWuWds6jTmFghR/PK6rZwM6Q7RN
BOCtfnV+D5b15eqrKyAvfMnn/6fTYxtGvwgBkOAOX0Q/V9tzB4fWwYRVbS5to6l+
1NTUVoECSPRAghen5YreVBa4ouqGt708kNdttCZX4o7jm/zHBpHUqaCEgOukyxbW
RWdJW4DUTN3Oq0Js0ifnEoF5/MvRSZsr48UK3lOYQ04x/Z6xEtW2jsNNQbx4Iib1
te8qRuWRrFK5IsjbaXsvaUydzLwiwglrAayyY/l3UU4x+EPu0xCIt4hqfqd6QOMV
whYtUXtPLwASPE3rcT/G/clIJBXiL/PaSsX9MfZuYiAN/4dRJ8Rk96Aq/UJAJIQQ
iJQkcRyEpX8JwPlJb8M84G/oPQ2KnRFJ3cBRvbE5YsT9b4KwOCUt0PrcQ7ktKcw0
eO9BzHQxmr2mffCxpygqPMQeGy5ekfNf5kXP32pquZOryOPOu26NhaCe+TOMaeu4
IV4rVu2yWxea7FJ7Od4GgVOg7aGphF8tGQ9DRha6ajri5e2lsjDKpy6caeXivU9o
pVEMp1K3AFj6BgiPHZJQQUyZ+r4kSVhlNhHshIzNKSYlqiOHrJQ=
=9Ky3
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to