Age | Commit message (Collapse) | Author |
|
|
|
The NEWS file had a temporary version so it was never shown to users.
Fix it.
Gbp-Dch: Ignore
|
|
Fixes Lintian Error.
Gbp-Dch: Ignore
|
|
The binary_onie script needs a few programs to run, and it uses them on
the host rather than in the chroot, so add them to the Recommends list.
|
|
Set urgency to low to allow for more time in unstable
|
|
|
|
|
|
|
|
|
|
|
|
/sbin/mkfs.nfts -> /sbin/mkfs.ntfs
|
|
Closes: #887278
|
|
|
|
[hertzog@debian.org:
- Fix conflicts due to renamed variables
]
Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
|
|
Now grub.cfg shows all the kernel options. Before this patch when you
had more than two kernels it only showed the auto option.
Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
|
|
old 486 one.
[hertzog@debian.org:
Also rename the variables for consistency.
]
Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
|
|
|
|
Thanks to Daniel Reichelt <debian@nachtgeist.net> for the patch.
Closes: #881941
|
|
Signed-off-by: Raphaël Hertzog <hertzog@debian.org>
|
|
This makes the package reproducible at build time.
Closes: #879169
|
|
|
|
As done by the linux source package since its version 4.4.
|
|
To generate an hdd image, binary_hdd first estimates the needed size of
the image using du. By default, when du finds multiple hardlinked copies
of a file, it counts them only once. However, when the target filesystem
is FAT, which does not support hardlinks, these files will take up more
space when finally copying the contents, breaking the build:
P: Copying binary contents into image...
cp: error writing 'chroot/binary.tmp/live/initrd.img-4.9.0-3-amd64': No space left on device
cp: error writing 'chroot/binary.tmp/efi/boot/bootx64.efi': No space left on device
cp: error writing 'chroot/binary.tmp/efi/boot/bootia32.efi': No space left on device
cp: cannot create directory 'chroot/binary.tmp/boot/grub': No space left on device
cp: cannot create directory 'chroot/binary.tmp/isolinux': No space left on device
To fix this, pass --count-links to du when the target is FAT, to make
the space estimation correct.
This problem is exposed by commit 9c974b26b (Instead of renaming kernel
for syslinux, create hardlinks), which might need to be separately fixed
(to not waste space on FAT targets), but binary_hdd should at least
handle hardlinks more gracefully.
|
|
|
|
Recent versions of Linux, parted or some other bit of software cause
partition devices, like /dev/loop0p1 to be created when running parted
mkpart. However, these devices are not cleaned up when running
losetup -d to remove /dev/loop0 later, so they linger around and confuse
mkfs (which refuses to make a filesystem, thinking there are partitions):
mkfs.fat 4.1 (2017-01-24)
mkfs.vfat: Partitions or virtual mappings on device '/dev/loop0', not making filesystem (use -I to override)
To prevent this behaviour, pass --partscan to losetup when adding a new
partition, to clean up any lingering partitions. It seems losetup does not
accept --partscan when deleting a loop device, to clean up at that point, but
since binary_hdd mounts the partition last, there should not be any lingering
partition devices after live-build is done.
The --partscan option is available since util-linux 2.21 (released in 2012), so
it should be fairly safe to pass it unconditionally.
|
|
|
|
|
|
|
|
Also fix the version string in the manual pages.
Closes: #859290
|
|
That way we always have a valid UTF-8 locale even when we don't have
the "locales" (or "locales-all") package installed.
|
|
Thanks to Thomas Schmitt <scdbackup@gmx.net> for the suggestion.
|
|
|
|
|
|
Thanks to Daniel Reichelt <debian@nachtgeist.net> for the patch.
Closes: #864386
|
|
|
|
4.9.
|
|
|
|
* Update the manual page with the missiong --bootappend-live-failsafe
option.
* Keep supporting the former --bootloader (without s).
|
|
grub-pc configuration.
|
|
|
|
* Use only long kernel names.
* Put advanced options in a submenu.
* Use distro-agnostic labels.
* Don't generate entries with kernel version when we have a single
version.
|
|
|
|
Now we generate the VERSION file at install time or at package build time.
|
|
|
|
picture.
|
|
|
|
|
|
|
|
|
|
|