vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 66839c4346c63e8c48d7eba6b3d1ca99f1dd691f
Author: Luca Boccassi <bluca@debian.org>
Date: Thu Sep 20 12:01:33 2018 +0100
Bump Standards-Version to 4.2.1.
commit b2a760de575c1439e996cb895deb575c611ddf15
Author: Luca Boccassi <bluca@debian.org>
Date: Thu Sep 20 12:01:02 2018 +0100
Add Rules-Requires-Root: no.
commit 4db6471248223ffec7ea1a028b929cd819abd490
Author: Luca Boccassi <bluca@debian.org>
Date: Thu Sep 20 11:59:50 2018 +0100
Build-Depend on debhelper >= 10~ to facilitate backports.
Not used at the moment, but it will be in the future when we bump it,
so that we don't forget
commit f108fdfa71c9d66a5ef9dfe7f1f48c170c7f228e
Author: Luca Boccassi <bluca@debian.org>
Date: Fri Sep 14 16:38:33 2018 +0100
UEFI: remove the EFI/debian/grub.cfg, not necessary anymore
Turns out gcd works fine after adding /boot/grub/grub.cfg in the img,
as that's the path that gets hardcoded, and adding the EFI/debian/
grub.cfg was not necessary, so remove it.
commit c22f1f5b71745922ae28df0ebf4b7d1a49d89f55
Author: Steven Shiau <steven@nchc.org.tw>
Date: Wed Aug 22 11:43:40 2018 +0800
Use gcd{x64.aa64}.efi.signed for amd64/arm64 arch.
For secured boot in binary_grub-efi, the gcdx64.efi.signed is
the boot loader for removable device, like CD or USB flash drive,
while grubx64.efi.signed is for hard drive. Therefore for live system,
use gcdx64.efi.signed for amd64 and gcdaa64.efi.signed for arm64.
commit 8403487d4e3bda65cdd2ea6081399f7977325adb
Author: Marcel Partap <mpartap@gmx.net>
Date: Wed Sep 12 18:00:20 2018 +0200
copy keys to /etc/apt/trusted.gpg.d with appropriate extension for them to not be ignored.
commit 52908422880f8d5cfa18c577d4138d5449af37f6
Author: Raphaël Hertzog <hertzog@debian.org>
Date: Fri Jul 27 09:46:55 2018 +0200
Handle includes.chroot files installed over symlinked directories
With the merged /usr feature now enabled in debootstrap, we have
/bin and /lib which are symlinks to /usr/bin and /usr/lib. If
the live-build configuration provides files in
config/includes.chroot/lib/ or config/includes.chroot/bin/ then
lb chroot_includes will replace the /lib or /bin symlink with real
directories having only the content provided in chroot.includes and
problems will follow... the build will usually fail later with a
cryptic error message (for example a hook failing to execute
/usr/bin/env).
Work around the issue by creating a tarball of the files to install
and by unpacking that tarball from within the chroot with appropriate
options.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/l/live-build.png){kind=link}