Package: live-build
Version: 1:20230131
Severity: normal
X-Debbugs-Cc: t...@cantab.net
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I wanted to build a 'live' iso with an ext4 file system instead of squashfs,
a
A full log of the failing build is here
http://tjcw.freeshell.org/live-build/basic-bookworm.nohup.out . The
error message is a few lines before the end of this.
I get the same failure if I try 'ext2' or 'ext3' for filesystem type.
This patch (to /usr/lib/live/build/binary_rootfs) resolves the problem
when building bookworm live isos on a bookworm host system. I don't
know if it is right for other environments.
109,113c109,113
< if ! Chroot chroot "test -s /etc/mtab"
<
As coded, there is a test '-s /etc/mtab'. This tests whether the item
is a socket; it looks like the test should be '-l /etc/mtab' which
tests whether the item is a symbolic link.
I had my test parameters wrong; '-s' tests for size > 0, '-S' tests
for socket, '-L' tests for sym-link. I think the intended test is
'-e', file exists; and so the required patch is
tjcw@debian:/usr/lib/live/build$ git diff binary_rootfs.0 binary_rootfs
diff --git a/binary_rootfs.0 b/binary_rootf
Package: live-build
Version: 1:20230131
Severity: normal
X-Debbugs-Cc: tjc...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I installed a debian bookworm system from 'netinst' on 20 February 2023
I tri
he problem.
I have added log files from more runs in
http://tjcw.freeshell.org/live-build/ showing the failures when I try
to package anything based on bookworm or sid.
Chris Ward
lding an SBOM for the ISO. When I am building for bullseye rather
than bookworm, I don;t get these messages. Is live-build responsible
for this behaviour, or should I report it against some other package ?
Chris Ward
fails, the build gives a message
ln: failed to create symbolic link '/etc/mtab': File exists
Chris Ward
Package: open-infrastructure-system-build
Version: 20190202-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I am trying to build a 'live' debian image for usb stick
* What exactly did you do
I have tried this on Debian 'testing' and 'sid' installations ( i.e. making
a 'buster' iso both times ) and I get the same result.
I set up ubuntu 20.04 . The problem still happened. But then I added a
'sleep 10' to chroot_devpts , so it now reads
remove)
Echo_message "Begin unmounting /dev/pts..."
sleep 10
# Checking lock file
Check_lockfile .lock
and th
Package: debian-installer
Version: buster
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempted to install debian 10.3 in a virtual machine with a Ubuntu 19.10 host
* What exactly did you d
I have just noticed that the virtual disk for the system was allocated with
qemu-img create -f qcow Debian10.qcow 200G
where the intended allocation would be with
qemu-img create -f qcow2 Debian10.qcow2 200G
When I allocated the disk in the intended way, formatting proceeded much
faster. This
Package: live-build
Version: 1:20190311
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I am trying to create a live usb stick. This is the first time I am using
live-build.
I am running in a Deb
tempt I have removed
linux-base
linux-image-4.19.0-6-amd64
linux-image-amd64
from the desktop.list.chroot and issued 'lb clean;lb build'. This is
currently running.
--
Chris Ward
That 'lb build' again finished early with no iso, but unmounting the pts
and reissuing the 'lb build' resulted in an iso. So now I have my live
system, but there is still some problem with live-build which prevents a
clean run first time for me.
--
Chris Ward
Package: open-infrastructure-system-build
Version: 20190202-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempted to make a live debian iso using a script that worked anout 3 weeka ago
*
Package: live-build
Version: 1:20230502
Severity: important
X-Debbugs-Cc: t...@cantab.net
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I installed debian 12.1 in a VM and installed the live-build package
* W
FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
/usr/lib/live/build/installer_debian-installer- #fi
/usr/lib/live/build/installer_debian-installer-
tjcw@debian:~/lb$
and now I can run the live builds that I want to run
Chris Ward.
The following fixes the bug for me. It may need adjusting so that it
can work both for debian 12.0 and previous, and for debian 12.11 where
'firmware-linux' is no longer a separate item.
The patch to binary_rootfs fixes a bug that I reported previously.
diff --git a/./binary_rootfs b/home/tjcw/li
# 20230806 tjcw Already in base linux with debian 12.1
+ #if [ $(apt-cache show "^firmware-linux$" 2> /dev/null
| grep "^Package:" | wc -l) -eq 1 ]
+ #then
+ # FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
+ #fi
Firmware_List_From_Contents
"${LB_PARENT_MIRROR_CHROOT}" "${LB_PARENT_DISTRIBUTION_CHROOT}"
"${LB_PARENT_ARCHIVE_AREAS}"
Chris Ward
, or that something
here should be done a different way; I just hunted for
"firmware-linux" and dummied out all the references that I found.
Chris Ward.
On Sun, 6 Aug 2023 at 17:54, Roland Clobus wrote:
>
> Hello Chris,
>
> On 06/08/2023 17:19, Chris Ward wrote:
> >
23 matches
Mail list logo
