On 2020-03-11 03:52, jnq...@gmail.com wrote:
On Tue, 2020-03-10 at 15:38 +, jnq...@gmail.com wrote:
```
LB_BOOTLOADERS="syslinux,grub-efi"
echo "${LB_BOOTLOADERS}" | while IFS="," read -r BOOTLOADER; do
echo "bootloader: ${BOOTLOADER}"
done
```
this code always fails to split the com
On 2020-03-02 07:12, jnq...@gmail.com wrote:
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
there are lots of checks being done that tools are available and
executable. this is done with a mixture of use of `which` and fixed
paths, redirection of output to /dev/n
On 2020-03-12 11:41, jnq...@gmail.com wrote:
On Thu, 2020-03-12 at 11:11 +0900, John Crawley wrote:
On 2020-03-02 07:12, jnq...@gmail.com wrote:
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
there are lots of checks being done that tools are available and
On 2020-03-12 12:21, jnq...@gmail.com wrote:
On Thu, 2020-03-12 at 11:50 +0900, John Crawley wrote:
On 2020-03-12 11:41, jnq...@gmail.com wrote:
On Thu, 2020-03-12 at 11:11 +0900, John Crawley wrote:
On 2020-03-02 07:12, jnq...@gmail.com wrote:
Package: live-build
Version: 1:20191221
Owner
On 2020-03-12 11:41, jnq...@gmail.com wrote:
On Thu, 2020-03-12 at 11:11 +0900, John Crawley wrote:
On 2020-03-02 07:12, jnq...@gmail.com wrote:
Package: live-build
Version: 1:20191221
Owner: jnq...@gmail.com
Severity: minor
there are lots of checks being done that tools are available and
s=''
fi
printf 'v=%s\n' "${v}"
done
The above demo code tested produces output:
v=a1
v=a2
v=a3
v=a4
Thankyou, I appreciate the effort you've put into this but an
explanation of why the existing implementation did not work was
supplied by John Cra
On 2020-03-28 09:20, jnq...@gmail.com wrote:
On Fri, 2020-03-20 at 17:50 +, Witold Baryluk wrote:
I want all instances of apt in the chroot during lb build, to have
few extra
environment variables, for example:
export NEEDRESTART_SUSPEND=1
export APT_LISTCHANGES_FRONTEND=none
I am not sure
On 2020-05-02 08:40, jnq...@gmail.com wrote:
I presume that what you really mean is the text at the top of the screen
in the bootloader? Like "Debian GNU/Linux 10 (buster)".
If that's what you mean, it's a part of the background image (splash),
automatically generated from an SVG, with the text
On 2020-05-03 04:16, Michael . wrote:
Grub 2 reads various files for its naming system. Files such as
/etc/issue, /etc/lsb-release, /etc/debian-version, and various others
all contribute to what you are refereing to. There is a page somewhere
written by Paul (pabs) maybe in the census that tells
On 2020-08-17 01:30, andy pugh wrote:
On Sun, 16 Aug 2020 at 17:13, Fernando Toledo wrote:
you can put in files:
config/archives/your-repo.list.chroot
config/archives/your-repo.list.binary
config/archives/your-repo.key
Yes, and I am doing that for our own packages.
But is it appropriate or
On 2020-08-18 16:47, andy pugh wrote:
On Tue, 18 Aug 2020 at 01:46, John Crawley wrote:
I think you might be missing --mirror-binary and possibly (see 'man
lb_config') --mirror-binary-security lines in auto/config.
I am, but the docs seem to suggest that these are only relevant to
On 30/12/2021 05:13, Roland Clobus wrote:
On 28/12/2021 09:20, Daniel Lewart wrote:
3) Hook scripts
You could change all instances of:
if [ ! -e FILE ];
then
exit 0
fi
to:
[ -e FILE ] || exit 0
It is more compact. However, I'd rather read if-statements, simil
On 12/02/2022 11:02, Steve McIntyre wrote:
Roland Clobus wrote:
The Debian installer installs from scratch, you can select any desktop
environment and other settings, even though they are not present on the
live image.
Calamares installs a copy of the live environment on your hard disk, and
remo
Live-build installs several packages intended for live systems only, eg
live-boot, live-configs, and allows custom live-only packages to be listed in
config/package-lists/*list.chroot_live
If there are no custom live packages, then the live-* packages are removed at
installation time by
li
On 31/07/2023 06:43, Kelvin Lee wrote:
During the installation, I was prompted to enter a superuser password and I
skipped this step. I know then the first user I created will have administrator
privileges by using the sudo command
However, when I tried running any commands with sudo after the
I have read that i386 Debian installer images will cease to be available from
Debian 13 (Trixie):
https://lists.debian.org/debian-cd/2023/08/msg00014.html
https://lists.debian.org/debian-cd/2023/08/msg4.html
But that d-i daily images will continue to be built:
https://lists.debian.org/debian
On 29/08/2023 00:41, Roland Clobus wrote:
On 28/08/2023 07:22, John Crawley wrote:
I have read that i386 Debian installer images will cease to be available from
Debian 13 (Trixie):
...
Does this mean that it will still be possible to build Trixie i386 images with
live-build?
i386 support
On 29/08/2023 08:53, John Crawley wrote:
On 29/08/2023 00:41, Roland Clobus wrote:
i386 support is not explicitly removed from the code, but it is not tested.
Keeping up with 9 images for amd64 alone is a big enough maintenance task,
unless you volunteer to monitor all i386 images :-)
But
On 02/01/2024 22:26, Anindya Chaudhuri wrote:
My /config/includes.installer/preseed.cfg file seems to be working, except $USER is not being added
to groups specified in the Account Setup portion for the installed image. So, after installing with
the user MyName, if I run "groups $USER", it only
On 04/01/2024 01:22, Anindya Chaudhuri wrote:
So obvious. Many thanks. PS: John Raff, fellow crunchbanger, I presume?
Ex-crunchbanger indeed! Now part of BunsenLabs: https://www.bunsenlabs.org/
On 06/02/2024 20:02, Robert Spiteri wrote:
I have copied all the contents of the bootloaders directory from /usr/share/live/build
into my config directory. I have also changed the first 3 entries from the
syslinux_common file. However there seem to be files for the installer: install_gui and
i
On 08/02/2024 13:03, Robert Spiteri wrote:
However, what if I do not want sub-menus and want just a single menu entry called
"Start Installer GUI" for example?
If you look at the default files it should be possible to see what is creating
the sub-menus.
Also if I delete the install_text.cf
On 08/02/2024 20:00, andy pugh wrote:
There appears to be a problem with the raspi-firmware package being
incorrectly installed on non-Pi systems, causing a problem (because
for most platforms it does not exist)
This is a well-known issue that was fixed in a commit to live-build:
https://salsa.
On 24/03/18 13:18, Leandro Doctors wrote:
(Please reply with CC to be, as I am not on the list)
I am learning to build Debian Live images using live-build.
My next step is to reproduce the unofficial images from [1].
[1]:
https://cdimage.debian.org/images/unofficial/non-free/images-including-
24 matches
Mail list logo
