I cannot reproduce the problem. I've tried:
1) With git master using `--debian-installer live` only.
2) The same with the sid version.
3) The sid version with the full set of options you specified.
4) The same but setting the build directory to 775 to see if this
would get inherited by subdirec
I've downloaded the amd64 live 2020.2 image and I have no such problem
in a VM, both for BIOS and EFI modes.
Is it the amd64 version you tried? BIOS or EFI? Do you have Secure Boot
enabled? If enabled, any difference if you disable it?
On Tue, 2020-05-19 at 21:51 +0530, raman taak wrote:
> Hello,
On Fri, 2020-06-26 at 20:11 +0530, Vineet Kumar wrote:
> Hi,
> I am trying to add my own repository in the normal iso file but i am
> not able to do so. When i am adding my directory in
> config/chroot.include/var/vpn , I can see that the /var/vpn folder is
> only getting created for the live image
On Fri, 2020-06-26 at 17:38 +0100, Lyndon Brown wrote:
> On Fri, 2020-06-26 at 20:11 +0530, Vineet Kumar wrote:
> > Hi,
> > I am trying to add my own repository in the normal iso file but i
> > am not able to do so. When i am adding my directory in
> > config/chroot.
It's still correct as of the current stable release, however this has
been improved in git master for the next release - you'll only have to
have copies of the files you modify.
On Wed, 2020-07-01 at 02:26 -0400, Juergen Fiedler wrote:
> I have a setup that uses ISOLINUX to boot from CD in 'Legacy
The correct thing to do is to simply run `lb config` after an `lb
clean`. This is what the error "E: the following stage is required to
be done first: config" means. I accept that the error text is perhaps
not as helpful as it could be, but it relates to the architecture of
the program.
Hacking th
The live-build `--mode` option was for allowing for any variations
necessary for building images for derivative distros, like Ubuntu and
"Progress" (which is/was a distro produced by the original live-build
author Daniel B).
In part this includes adjusting labels and filenames. Furthermore it
impa
est to stop systemd-sysv from being
> pulled in at all as while I do not mind systemd I do not want to
> force
> it on people.
>
> Cheers.
> Michael.
>
> On 24/08/2021, Lyndon Brown wrote:
> > The live-build `--mode` option was for allowing for any variations
> > n
Package: live-build
Version: 1:20210407
As just discussed on the mailing list (see the thread starting at [1]),
the author of the thread would like to use the sysvinit init system
instead of systemd. We already provide an option for selecting this (`-
-initsystem`), however it does not work. All i
ian.org/cgi-bin/bugreport.cgi?bug=992916
[2]: https://salsa.debian.org/live-team/live-build/-/merge_requests/257
On Tue, 2021-08-24 at 23:17 +0100, Lyndon Brown wrote:
> I see. As I said, I'm very busy with little to no time to spare for
> live-build work / support currently, so I'm afraid
Hi,
The problem actually seems to be because you're putting your bootloader
customisations in the wrong place in your config. You're supposed to
put them under `config/bootloaders/` not `config/includes.binary/`.
Stuff placed into the latter is just simply copied directly into the
filesystem being
t I will test
> it over the next few days and let you know how it goes.
> Cheers.
> Michael.
>
> On 25/08/2021, Lyndon Brown wrote:
> > Just to update you since my previous reply:
> > - I've filed a bug report for this issue - #992916 ([1]).
> > - I've prod
t; > I: Validating udev 247.3-6
> > I: Retrieving initscripts 2.96-7
> > I: Validating initscripts 2.96-7
> > I: Retrieving sysv-rc 2.96-7
> > I: Validating sysv-rc 2.96-7
> > I: Retrieving sysvinit-core 2.96-7
> > I: Validating sysvinit-core 2.96-7
> > I
I took a look and can see that your build has failed whilst running
debootstrap during the initial bootstrapping stages (that particular
block of lines beginning with "I:" and "E:" where it's fetching,
verifying and extracting packages is coming from debootstrap).
I suggest that you first try addi
With the --image-name option.
If you run:
lb config --help
you'll find information about all of the available configuration
options.
On Wed, 2021-10-13 at 18:22 -0500, Jerome IBt wrote:
> Dear all
>
> I've notice a change between the Debian version 10.x and 11.x.
>
> In the 10.x, doing the "lb
23.50% of uncompressed inode table size (2210058 bytes)
> > Directory table size 580264 bytes (566.66 Kbytes)
> > 34.13% of uncompressed directory table size (1700072 bytes)
> > Xattr table size 40 bytes (0.04 Kbytes)
> > 100.00% of uncompressed xattr
There's only so much customisation that you can get done with the
configuration options alone, as you have surmised, however this is
completely the wrong file to edit to achieve your goal.
The menus are created from templates kept in
/usr/share/live/build/bootloaders.
You are supposed to copy stu
;s only the grub menu labels, that too only for uefi installs, that
> doesn't seem to be working.
>
> From: Lyndon Brown
> Sent: Tuesday, December 14, 2021 12:31 PM
> To: Anindya Chaudhuri ; debian-
> l...@lists.debian.org
> Subject: Re: Debian live-build: Specifiying grub
18 matches
Mail list logo
