Package: release.debian.org Severity: normal Tags: buster User: release.debian....@packages.debian.org Usertags: pu
Back in March, I uploaded to Buster version 1.20190215-1+deb10u3 of raspi3-firmware, stating it fixed "unbootableness" on several systems. I assumed it was all done, and went on with my life. Some time later (kernel / firmware updates are not *that* common), I started getting reports of b0rkenness again. Thorsten Glaser found and fixed (#961377) a very small and silly typo in my last upload, and fixed it: I used a wrong variable name when installing the new set of DTBs. Please allow this package, version 1.20190215-1+deb10u4, to enter Stable. The fix is found at: https://salsa.debian.org/debian/raspi-firmware/-/commit/2bf38f62de0514c2759f2c33d147c935e4d044bf Other than that, it's just minor administrativia (fixing VCS links, targetting the upload at the right suite). Thanks a lot, -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled