Hello,
On Tue, 29 Aug 2017, Matthijs Kooijman wrote:
> I also ran into this same error a while ago. It is caused by partition
> devices being created when parted creates partitions, which are not
> cleaned up when the loop devices are cleaned up. I'm attaching a patch
> that fixes this, by
Package: live-build
Version: 1:20170807
Followup-For: Bug #865586
Hi,
I also ran into this same error a while ago. It is caused by partition
devices being created when parted creates partitions, which are not
cleaned up when the loop devices are cleaned up. I'm attaching a patch
that fixes this,
Hi,
it would be nice to have the simple fix suggested by Grégory DAVID
(binary_hdd-mkfs.vfat-error.patch) in stretch so that we can build hdd
images again.
Ciao,
Thierry
Hi,
i fall into the same bug while upgrading from jessie to stretch.
Note however that, with the version of live-build shipped with stretch
(20170213) and the '--distribution' set to 'jessie', there is no problem,
so the issue seems to come from a difference of behaviour between both
version of
Seems like I'm hitting the same issue with hdd image. iso-hybrid is working
fine.
config (not hook or any other modification after this) :
lb config --distribution stretch --binary-images hdd --architectures amd64
--linux-flavours amd64 \
--archive-areas "main contrib non-free" --apt-indices
On Thu, 22 Jun 2017, Grégory DAVID wrote:
>With a simple live-build config,
What is your simple live-build config? Please share your config directory
and/or the command line options that you are using.
Thank you!
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS:
Package: live-build
Version: 1:20170213
Severity: important
Dear Maintainer,
The 'lb binary_hdd' script halt with a mkfs.vfat error when build a FAT32 or
FAT16 hdd image
With a simple live-build config, I launched the whole building process that
halt with this error (that is not
7 matches
Mail list logo
