New install of Live Build on Buster E: debootstrap - command not found

[Michael .]

Hi everyone
Usually I think when there is no reply to a question people don't know
the answer and I am sure this is probably the case here but this is a
crippling issue for me. It has literally stopped me dead in my tracks.
I don't really want to have to go back to Stretch if I can help it. If
anyone is using an up to date Buster (current testing) system to use
Live Build successfully please let me know otherwise I'll assume Live
Build isn't suitable for Buster and I will revert back to Stretch.
Cheers.
Michael.

Hi.

Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output

***@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb clean
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
***@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb config
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
***@michael-desktop:/home/michael/CobberLive/2019/Mate/i386# lb build
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
/usr/lib/live/build/bootstrap: 35: /usr/lib/live/build/bootstrap:
chroot: not found
***@michael-desktop:/home/michael/CobberLive/2019/Mate/i386#

As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test run). I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

From memory live-build used to detect the version it was installed on

and build an iso based on that unless it had been told to do something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.

Cheers.
Michael.

[Luca Boccassi]

Just tried on a sid chroot, it seems to work just fine, so I'd suggest
to check your configuration:

# lb clean
[2018-11-05 22:29:13] lb clean 
P: Executing auto/clean script.
[2018-11-05 22:29:13] lb clean noauto
P: Cleaning chroot
# lb config
[2018-11-05 22:29:15] lb config 
P: Executing auto/config script.
[2018-11-05 22:29:15] lb config noauto --apt apt --apt-recommends false
--apt-indices false --apt-source-archives false --apt-options --yes -o
Acquire::Check-Valid-Until=false --bootappend-live boot=live components
splash username=root console=tty0 console=ttyS0 --bootappend-live-
failsafe boot=live components username=root debug live-boot.debug
memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
vga=normal console=tty0 console=ttyS0 --bootloaders syslinux,grub-efi
--cache-indices false --checksums md5 sha256 --chroot-filesystem
squashfs --debconf-frontend noninteractive --distribution stable --
parent-distribution stable --firmware-binary false --firmware-chroot
false --ignore-system-defaults --image-name standard_20181105T2229 --
initramfs live-boot --linux-flavours amd64 --mode debian --source false
--security true --updates true --backports false --verbose --onie true
--onie-kernel-cmdline systemd.show_status=1 net.ifnames=1
P: Updating config tree for a debian/stable/amd64 system
P: Symlinking hooks...
# lb build
[2018-11-05 22:29:17] lb build 
P: Executing auto/build script.
[2018-11-05 22:29:17] lb build noauto
P: live-build 1:20180925
P: Building config tree for a debian/stable/amd64 system
[2018-11-05 22:29:17] lb bootstrap 
P: Setting up cleanup function
[2018-11-05 22:29:17] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-05 22:29:17] lb bootstrap_debootstrap 
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem
is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)... 
I: Retrieving InRelease 
I: Retrieving Release 
I: Retrieving Release.gpg 
I: Checking Release signature
I: Valid Release signature (key id
067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages 
I: Validating Packages 
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...

Post by Michael .
Hi everyone
Usually I think when there is no reply to a question people don't know
the answer and I am sure this is probably the case here but this is a
crippling issue for me. It has literally stopped me dead in my
tracks.
I don't really want to have to go back to Stretch if I can help it. If
anyone is using an up to date Buster (current testing) system to use
Live Build successfully please let me know otherwise I'll assume Live
Build isn't suitable for Buster and I will revert back to Stretch.
Cheers.
Michael.

Hi.

Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-
get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
chroot: not found
As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test run). I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

From memory live-build used to detect the version it was installed on

and build an iso based on that unless it had been told to do
something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.
Cheers.
Michael.

...

[Michael .]

Thank you for your reply Luca, now I know it should be working.
As I said in my original message it was a totally new install and
everything was new. I purged the system of live-* packages and
reinstalled them only to have the problem again. I have done the same
thing this morning and still get the same issue. I will continue to
work on it now I know it should be working and when I find what the
issue is I will report back.
Cheers.
Michael.

Post by Luca Boccassi
Just tried on a sid chroot, it seems to work just fine, so I'd suggest
# lb clean
[2018-11-05 22:29:13] lb clean
P: Executing auto/clean script.
[2018-11-05 22:29:13] lb clean noauto
P: Cleaning chroot
# lb config
[2018-11-05 22:29:15] lb config
P: Executing auto/config script.
[2018-11-05 22:29:15] lb config noauto --apt apt --apt-recommends false
--apt-indices false --apt-source-archives false --apt-options --yes -o
Acquire::Check-Valid-Until=false --bootappend-live boot=live components
splash username=root console=tty0 console=ttyS0 --bootappend-live-
failsafe boot=live components username=root debug live-boot.debug
memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
vga=normal console=tty0 console=ttyS0 --bootloaders syslinux,grub-efi
--cache-indices false --checksums md5 sha256 --chroot-filesystem
squashfs --debconf-frontend noninteractive --distribution stable --
parent-distribution stable --firmware-binary false --firmware-chroot
false --ignore-system-defaults --image-name standard_20181105T2229 --
initramfs live-boot --linux-flavours amd64 --mode debian --source false
--security true --updates true --backports false --verbose --onie true
--onie-kernel-cmdline systemd.show_status=1 net.ifnames=1
P: Updating config tree for a debian/stable/amd64 system
P: Symlinking hooks...
# lb build
[2018-11-05 22:29:17] lb build
P: Executing auto/build script.
[2018-11-05 22:29:17] lb build noauto
P: live-build 1:20180925
P: Building config tree for a debian/stable/amd64 system
[2018-11-05 22:29:17] lb bootstrap
P: Setting up cleanup function
[2018-11-05 22:29:17] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-05 22:29:17] lb bootstrap_debootstrap
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem
is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id
067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...

Post by Michael .
Hi everyone
Usually I think when there is no reply to a question people don't know
the answer and I am sure this is probably the case here but this is a
crippling issue for me. It has literally stopped me dead in my tracks.
I don't really want to have to go back to Stretch if I can help it. If
anyone is using an up to date Buster (current testing) system to use
Live Build successfully please let me know otherwise I'll assume Live
Build isn't suitable for Buster and I will revert back to Stretch.
Cheers.
Michael.

Hi.

Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-
get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
chroot: not found
As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test run). I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

From memory live-build used to detect the version it was installed on

and build an iso based on that unless it had been told to do
something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.
Cheers.
Michael.

--
Kind regards,
Luca Boccassi

...

[Michael .]

Ok I thought I'd go through the process again, without reinstalling
the OS itself, and this is the outcome. Everything done via command
line instead of creating the folders via the file manager.

***@michael-desktop:~$ cat /etc/debian_version
buster/sid
***@michael-desktop:~$ mkdir LiveBuild
***@michael-desktop:~$ cd LiveBuild
***@michael-desktop:~/LiveBuild$ mkdir x86-64
***@michael-desktop:~/LiveBuild$ cd x86-64
***@michael-desktop:~/LiveBuild/x86-64$ su
Password:
***@michael-desktop:/home/michael/LiveBuild/x86-64# lb clean
[2018-11-06 10:12:57] lb clean
P: Cleaning chroot
***@michael-desktop:/home/michael/LiveBuild/x86-64# lb config
[2018-11-06 10:13:03] lb config
P: Creating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
***@michael-desktop:/home/michael/LiveBuild/x86-64# lb build
[2018-11-06 10:13:12] lb build
P: live-build 1:20180925
P: Building config tree for a debian/stretch/amd64 system
[2018-11-06 10:13:12] lb bootstrap
P: Setting up cleanup function
[2018-11-06 10:13:12] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-06 10:13:12] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
/usr/lib/live/build/bootstrap: 35: /usr/lib/live/build/bootstrap:
chroot: not found
***@michael-desktop:/home/michael/LiveBuild/x86-64#

Totally new folders, totally new config created by Live Build itself.
My system is Buster but Live Build is reverting to Stretch. I believe
this is what is causing the problem.

Post by Michael .
Thank you for your reply Luca, now I know it should be working.
As I said in my original message it was a totally new install and
everything was new. I purged the system of live-* packages and
reinstalled them only to have the problem again. I have done the same
thing this morning and still get the same issue. I will continue to
work on it now I know it should be working and when I find what the
issue is I will report back.
Cheers.
Michael.

Post by Luca Boccassi
Just tried on a sid chroot, it seems to work just fine, so I'd suggest
# lb clean
[2018-11-05 22:29:13] lb clean
P: Executing auto/clean script.
[2018-11-05 22:29:13] lb clean noauto
P: Cleaning chroot
# lb config
[2018-11-05 22:29:15] lb config
P: Executing auto/config script.
[2018-11-05 22:29:15] lb config noauto --apt apt --apt-recommends false
--apt-indices false --apt-source-archives false --apt-options --yes -o
Acquire::Check-Valid-Until=false --bootappend-live boot=live components
splash username=root console=tty0 console=ttyS0 --bootappend-live-
failsafe boot=live components username=root debug live-boot.debug
memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
vga=normal console=tty0 console=ttyS0 --bootloaders syslinux,grub-efi
--cache-indices false --checksums md5 sha256 --chroot-filesystem
squashfs --debconf-frontend noninteractive --distribution stable --
parent-distribution stable --firmware-binary false --firmware-chroot
false --ignore-system-defaults --image-name standard_20181105T2229 --
initramfs live-boot --linux-flavours amd64 --mode debian --source false
--security true --updates true --backports false --verbose --onie true
--onie-kernel-cmdline systemd.show_status=1 net.ifnames=1
P: Updating config tree for a debian/stable/amd64 system
P: Symlinking hooks...
# lb build
[2018-11-05 22:29:17] lb build
P: Executing auto/build script.
[2018-11-05 22:29:17] lb build noauto
P: live-build 1:20180925
P: Building config tree for a debian/stable/amd64 system
[2018-11-05 22:29:17] lb bootstrap
P: Setting up cleanup function
[2018-11-05 22:29:17] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-05 22:29:17] lb bootstrap_debootstrap
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem
is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id
067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...

Post by Michael .
Hi everyone
Usually I think when there is no reply to a question people don't know
the answer and I am sure this is probably the case here but this is a
crippling issue for me. It has literally stopped me dead in my tracks.
I don't really want to have to go back to Stretch if I can help it. If
anyone is using an up to date Buster (current testing) system to use
Live Build successfully please let me know otherwise I'll assume Live
Build isn't suitable for Buster and I will revert back to Stretch.
Cheers.
Michael.

Hi.

Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-
get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
chroot: not found
As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test run). I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

From memory live-build used to detect the version it was installed on

and build an iso based on that unless it had been told to do
something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.
Cheers.
Michael.

--
Kind regards,
Luca Boccassi

...

[Luca Boccassi]

In a chroot:

# mkdir lb
# cd lb
# lb clean
[2018-11-06 16:54:35] lb clean 
P: Cleaning chroot
# lb config
[2018-11-06 16:54:38] lb config 
P: Creating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
# lb build
[2018-11-06 16:54:40] lb build 
P: live-build 1:20180925
P: Building config tree for a debian/stretch/amd64 system
[2018-11-06 16:54:40] lb bootstrap 
P: Setting up cleanup function
[2018-11-06 16:54:40] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-06 16:54:40] lb bootstrap_debootstrap 
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem
is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)... 
I: Retrieving InRelease 
I: Retrieving Release 
I: Retrieving Release.gpg 
I: Checking Release signature
I: Valid Release signature (key id
067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages 
I: Validating Packages 
...


Are you sure you've got debootstrap installed? Can you run it manually?

Post by Michael .
Ok I thought I'd go through the process again, without reinstalling
the OS itself, and this is the outcome. Everything done via command
line instead of creating the folders via the file manager.
buster/sid
[2018-11-06 10:12:57] lb clean
P: Cleaning chroot
[2018-11-06 10:13:03] lb config
P: Creating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
[2018-11-06 10:13:12] lb build
P: live-build 1:20180925
P: Building config tree for a debian/stretch/amd64 system
[2018-11-06 10:13:12] lb bootstrap
P: Setting up cleanup function
[2018-11-06 10:13:12] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-06 10:13:12] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-
get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
chroot: not found
Totally new folders, totally new config created by Live Build itself.
My system is Buster but Live Build is reverting to Stretch. I believe
this is what is causing the problem.

Post by Michael .
Thank you for your reply Luca, now I know it should be working.
As I said in my original message it was a totally new install and
everything was new. I purged the system of live-* packages and
reinstalled them only to have the problem again. I have done the same
thing this morning and still get the same issue. I will continue to
work on it now I know it should be working and when I find what the
issue is I will report back.
Cheers.
Michael.

Post by Luca Boccassi
Just tried on a sid chroot, it seems to work just fine, so I'd suggest
# lb clean
[2018-11-05 22:29:13] lb clean
P: Executing auto/clean script.
[2018-11-05 22:29:13] lb clean noauto
P: Cleaning chroot
# lb config
[2018-11-05 22:29:15] lb config
P: Executing auto/config script.
[2018-11-05 22:29:15] lb config noauto --apt apt --apt-recommends false
--apt-indices false --apt-source-archives false --apt-options --
yes -o
Acquire::Check-Valid-Until=false --bootappend-live boot=live components
splash username=root console=tty0 console=ttyS0 --bootappend-
live-
failsafe boot=live components username=root debug live-boot.debug
memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
vga=normal console=tty0 console=ttyS0 --bootloaders
syslinux,grub-efi
--cache-indices false --checksums md5 sha256 --chroot-filesystem
squashfs --debconf-frontend noninteractive --distribution stable --
parent-distribution stable --firmware-binary false --firmware-
chroot
false --ignore-system-defaults --image-name
standard_20181105T2229 --
initramfs live-boot --linux-flavours amd64 --mode debian --source false
--security true --updates true --backports false --verbose --onie true
--onie-kernel-cmdline systemd.show_status=1 net.ifnames=1
P: Updating config tree for a debian/stable/amd64 system
P: Symlinking hooks...
# lb build
[2018-11-05 22:29:17] lb build
P: Executing auto/build script.
[2018-11-05 22:29:17] lb build noauto
P: live-build 1:20180925
P: Building config tree for a debian/stable/amd64 system
[2018-11-05 22:29:17] lb bootstrap
P: Setting up cleanup function
[2018-11-05 22:29:17] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-05 22:29:17] lb bootstrap_debootstrap
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem
is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id
067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...

Post by Michael .
Hi everyone
Usually I think when there is no reply to a question people
don't
know
the answer and I am sure this is probably the case here but this is a
crippling issue for me. It has literally stopped me dead in my tracks.
I don't really want to have to go back to Stretch if I can help
it.
If
anyone is using an up to date Buster (current testing) system to use
Live Build successfully please let me know otherwise I'll assume Live
Build isn't suitable for Buster and I will revert back to Stretch.
Cheers.
Michael.

Hi.

Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output
lb
clean
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
lb
config
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
lb
build
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-
get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
chroot: not found
As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test
run).
I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

From memory live-build used to detect the version it was
installed
on

and build an iso based on that unless it had been told to do something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.
Cheers.
Michael.

--
Kind regards,
Luca Boccassi

...

[Michael .]

Yes debootsrap is installed. I have purged it, as well as the Live
Build packages, and reinstalled it a couple of times.
Unfortunately I don't have time to work on this now and probably won't
until the weekend. Thanks for your suggestions so far.
Cheers,
Michael.

Post by Luca Boccassi
# mkdir lb
# cd lb
# lb clean
[2018-11-06 16:54:35] lb clean
P: Cleaning chroot
# lb config
[2018-11-06 16:54:38] lb config
P: Creating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
# lb build
[2018-11-06 16:54:40] lb build
P: live-build 1:20180925
P: Building config tree for a debian/stretch/amd64 system
[2018-11-06 16:54:40] lb bootstrap
P: Setting up cleanup function
[2018-11-06 16:54:40] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-06 16:54:40] lb bootstrap_debootstrap
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem
is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id
067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages
I: Validating Packages
...
Are you sure you've got debootstrap installed? Can you run it manually?

Post by Michael .
Ok I thought I'd go through the process again, without reinstalling
the OS itself, and this is the outcome. Everything done via command
line instead of creating the folders via the file manager.
buster/sid
[2018-11-06 10:12:57] lb clean
P: Cleaning chroot
[2018-11-06 10:13:03] lb config
P: Creating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
[2018-11-06 10:13:12] lb build
P: live-build 1:20180925
P: Building config tree for a debian/stretch/amd64 system
[2018-11-06 10:13:12] lb bootstrap
P: Setting up cleanup function
[2018-11-06 10:13:12] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-06 10:13:12] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-
get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
chroot: not found
Totally new folders, totally new config created by Live Build itself.
My system is Buster but Live Build is reverting to Stretch. I believe
this is what is causing the problem.

Post by Michael .
Thank you for your reply Luca, now I know it should be working.
As I said in my original message it was a totally new install and
everything was new. I purged the system of live-* packages and
reinstalled them only to have the problem again. I have done the same
thing this morning and still get the same issue. I will continue to
work on it now I know it should be working and when I find what the
issue is I will report back.
Cheers.
Michael.

Post by Luca Boccassi
Just tried on a sid chroot, it seems to work just fine, so I'd suggest
# lb clean
[2018-11-05 22:29:13] lb clean
P: Executing auto/clean script.
[2018-11-05 22:29:13] lb clean noauto
P: Cleaning chroot
# lb config
[2018-11-05 22:29:15] lb config
P: Executing auto/config script.
[2018-11-05 22:29:15] lb config noauto --apt apt --apt-recommends false
--apt-indices false --apt-source-archives false --apt-options --
yes -o
Acquire::Check-Valid-Until=false --bootappend-live boot=live components
splash username=root console=tty0 console=ttyS0 --bootappend-
live-
failsafe boot=live components username=root debug live-boot.debug
memtest noapic noapm nodma nomce nolapic nomodeset nosmp nosplash
vga=normal console=tty0 console=ttyS0 --bootloaders
syslinux,grub-efi
--cache-indices false --checksums md5 sha256 --chroot-filesystem
squashfs --debconf-frontend noninteractive --distribution stable --
parent-distribution stable --firmware-binary false --firmware-
chroot
false --ignore-system-defaults --image-name
standard_20181105T2229 --
initramfs live-boot --linux-flavours amd64 --mode debian --source false
--security true --updates true --backports false --verbose --onie true
--onie-kernel-cmdline systemd.show_status=1 net.ifnames=1
P: Updating config tree for a debian/stable/amd64 system
P: Symlinking hooks...
# lb build
[2018-11-05 22:29:17] lb build
P: Executing auto/build script.
[2018-11-05 22:29:17] lb build noauto
P: live-build 1:20180925
P: Building config tree for a debian/stable/amd64 system
[2018-11-05 22:29:17] lb bootstrap
P: Setting up cleanup function
[2018-11-05 22:29:17] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-11-05 22:29:17] lb bootstrap_debootstrap
P: Begin bootstrapping system...
P: If the following stage fails, the most likely cause of the problem
is with your mirror configuration or a caching proxy.
P: Running debootstrap (download-only)...
I: Retrieving InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id
067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...

Post by Michael .
Hi everyone
Usually I think when there is no reply to a question people
don't
know
the answer and I am sure this is probably the case here but this is a
crippling issue for me. It has literally stopped me dead in my tracks.
I don't really want to have to go back to Stretch if I can help
it.
If
anyone is using an up to date Buster (current testing) system to use
Live Build successfully please let me know otherwise I'll assume Live
Build isn't suitable for Buster and I will revert back to Stretch.
Cheers.
Michael.

Hi.

Haven't been around for a while because I haven't come across any
issues, until now. Not sure if this is a bug or if something else is
causing this but on a new (everything is new) install of Buster and
Live-Build I am getting this output
lb
clean
[2018-09-17 07:41:21] lb clean
P: Executing auto/clean script.
[2018-09-17 07:41:21] lb clean noauto
P: Cleaning chroot
lb
config
[2018-09-17 07:41:26] lb config
P: Updating config tree for a debian/stretch/amd64 system
P: Symlinking hooks...
lb
build
[2018-09-17 07:41:36] lb build
P: Executing auto/build script.
[2018-09-17 07:41:36] lb build noauto
P: live-build 1:20180618
P: Building config tree for a debian/stretch/amd64 system
[2018-09-17 07:41:36] lb bootstrap
P: Setting up cleanup function
[2018-09-17 07:41:36] lb bootstrap_cache restore
P: Restoring bootstrap stage from cache...
[2018-09-17 07:41:36] lb bootstrap_debootstrap
E: debootstrap - command not found
I: debootstrap can be obtained from
http://ftp.debian.org/debian/pool/main/d/debootstrap/
I: On Debian based systems, debootstrap can be installed with 'apt-
get
install debootstrap'.
P: Begin unmounting filesystems...
P: Saving caches...
chroot: not found
As already mentioned this is a new install so there is nothing in it
(so you can ignore the i386 folder name as this is just a test
run).
I
have purged both live build, and its associated packages and
deboostrap and installed them again and I still get this same output.
So my questions are
1. Is live build not ready for use on Buster yet? (because it creates
this output "P: Updating config tree for a debian/stretch/amd64
system"
2. Is there a clash with Live-build and debootstrap somewhere making
live-build not "see" debootstrap even though it is installed?

From memory live-build used to detect the version it was
installed
on

and build an iso based on that unless it had been told to do something
different in the auto/config file. This one is reverting back to
stretch even though it is installed on a buster system.
Cheers.
Michael.

--
Kind regards,
Luca Boccassi

--
Kind regards,
Luca Boccassi

...

[Ginger_M]

live-build for buster is not complete.
Missing item for buster on path /usr/share/live/build/data/debian-cd/
There are items for squeeze, jessie, stretch, sid, but not for buster.



--------------------------------------------
Дана Чет, 8. 11. 18, Michael . <***@gmail.com> је написао/ла:

Тема: Re: New install of Live Build on Buster E: debootstrap - command not found
За: "Ginger_M" <***@yahoo.com>
Датум: Четвртак, 8. Новембар, 2018. 10:26

Hi Ginger_M
Thanks for your reply. I'm a little
lost as to what doing this will
achieve, could you explain how this
will fix my problem?
Cheers.
Michael.

Hi,
Create item for buster on path

/usr/share/live/build/data/debian-cd/
--------------------------------------------

Дана Уто, 6. 11. 18,
  Тема: Re: New install of

Live Build on Buster E: debootstrap - command not

found
  Датум: Уторак, 6.

Новембар, 2018. 20:26

  Yes debootsrap is installed.

I

  have purged it, as well as

the Live

  Build
  packages, and reinstalled it

a couple of times.

  Unfortunately I don't have

time to work on

  this now and probably won't
  until the
  weekend. Thanks for your

suggestions so far.

  Cheers,
  Michael.
  On 07/11/2018, Luca Boccassi
  >
  > # mkdir lb
  > # cd lb
  > # lb clean
  > [2018-11-06 16:54:35]

lb clean

  > P: Cleaning chroot
  > #
  lb config
  > [2018-11-06 16:54:38]

lb

  config
  > P: Creating config tree

for a

  debian/stretch/amd64 system
  Symlinking hooks...
  > # lb build
  > [2018-11-06 16:54:40]

lb build

  > P: live-build

1:20180925

  > P: Building config tree

for a

  debian/stretch/amd64 system
  > [2018-11-06
  16:54:40] lb bootstrap
  > P: Setting up
  cleanup function
  > [2018-11-06 16:54:40]
  lb bootstrap_cache restore
  > P: Restoring
  bootstrap stage from

cache...

  >
  [2018-11-06 16:54:40] lb

bootstrap_debootstrap

  > P: Begin bootstrapping

system...

  > P: If the following

stage fails, the most

  likely cause of the problem
  > is with
  your mirror configuration or

a caching proxy.

  > P: Running debootstrap
  (download-only)...
  > I: Retrieving
  InRelease
  > I: Retrieving Release
  > I: Retrieving

Release.gpg

  > I: Checking Release

signature

  > I: Valid Release

signature (key id

  >
 

067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)

  > I: Retrieving Packages
  > I: Validating Packages
  > ...
  >
  >
  > Are you sure
  you've got debootstrap

installed? Can you run it

  manually?
  >
  > On Tue,
  2018-11-06 at 10:18 +1100,
  >> Ok I thought I'd go

through the

  process again, without

reinstalling

  >>
  the OS itself, and this is

the outcome. Everything done via

  command
  >> line instead of

creating

  the folders via the file

manager.

  >>
  cat /etc/debian_version
  >>
  buster/sid
  mkdir LiveBuild
  cd LiveBuild
  mkdir x86-64
  cd x86-64
  su
  lb clean
  >> [2018-11-06

10:12:57] lb

  clean
  >> P: Cleaning chroot
  lb config
  >> [2018-11-06

10:13:03] lb

  config
  >> P: Creating config

tree for

  a debian/stretch/amd64

system

  Symlinking hooks...
  lb build
  >> [2018-11-06

10:13:12] lb

  build
  >> P: live-build

1:20180925

  >> P: Building config

tree for a

  debian/stretch/amd64 system
  >>
  [2018-11-06 10:13:12] lb

bootstrap

  >>
  P: Setting up cleanup

function

  >>
  [2018-11-06 10:13:12] lb

bootstrap_cache restore

  >> P: Restoring

bootstrap stage from

  cache...
  >> [2018-11-06

10:13:12] lb

  bootstrap_debootstrap
  debootstrap - command not

found

  debootstrap can be obtained

from

  >> http://ftp.debian.org/debian/pool/main/d/debootstrap/
  >> I: On Debian based

systems,

  debootstrap can be installed

with 'apt-

  >> get
  >> install
  debootstrap'.
  >> P: Begin
  unmounting filesystems...
  >> P: Saving
  caches...
  >>
 
 
  >>
  chroot: not found
  >>
  >> Totally new
  folders, totally new config

created by Live Build itself.

  >> My system is Buster

but Live Build is

  reverting to Stretch. I

believe

  >>
  this is what is causing the

problem.

  >>
  >>
  >> On 06/11/2018,
  >> > Thank you for

your

  reply Luca, now I know it

should be working.

  >> > As I said in

my original message

  it was a totally new install

and

  >>
  > everything was new. I

purged the system of live-*

  packages and
  >> > reinstalled

them

  only to have the problem

again. I have done the

  >> > same
  >>
  > thing this morning and

still get the same issue. I will

  continue to
  >> > work on it now

I

  know it should be working

and when I find what the

  >> > issue is I

will report back.

  >> > Cheers.
  >>
  > Michael.
  >> >
  >> > On 06/11/2018,

Luca Boccassi

  >> > > Just

tried on a

  sid chroot, it seems to work

just fine, so I'd

  >> > > suggest
  >> > > to check

your

  >> > >
  >> > > # lb

clean

  >> > >

[2018-11-05 22:29:13] lb

  clean

Executing

  auto/clean script.
  >> > >
  [2018-11-05 22:29:13] lb

clean noauto
Cleaning chroot

  >> > > # lb

config

  >> > >

[2018-11-05 22:29:15] lb

  config

Executing

  auto/config script.
  >> > >
  [2018-11-05 22:29:15] lb

config noauto --apt apt

  --apt-recommends
  >> > > false
  >> > >

--apt-indices false

  --apt-source-archives false

--apt-options --

  >> > > yes -o
  >> > >
 

Acquire::Check-Valid-Until=false --bootappend-live

  boot=live
  >> > >

components

  >> > > splash

username=root

  console=tty0 console=ttyS0

--bootappend-

  >> > > live-
  >> > > failsafe

boot=live

  components username=root

debug live-boot.debug

  >> > > memtest

noapic noapm nodma

  nomce nolapic nomodeset

nosmp nosplash

  >> > >

vga=normal console=tty0

  console=ttyS0 --bootloaders
  >> >
  > syslinux,grub-efi
  >> > >
  --cache-indices false

--checksums md5 sha256

  --chroot-filesystem
  >> > >
  squashfs --debconf-frontend

noninteractive --distribution

  stable
  >> > > --
  >> > >

parent-distribution stable

  --firmware-binary false

--firmware-

  >>
  > > chroot
  >> > > false
  --ignore-system-defaults

--image-name

  >> > >

standard_20181105T2229 --

  >> > > initramfs

live-boot

  --linux-flavours amd64

--mode debian --source

  >> > > false
  >> > >

--security true --updates

  true --backports false

--verbose --onie

  >> > > true
  >> > >

--onie-kernel-cmdline

  systemd.show_status=1

net.ifnames=1

  >>
  > > P: Updating config

tree for a debian/stable/amd64

  system

Symlinking

  hooks...
  >> > > # lb

build

  >> > >

[2018-11-05 22:29:17] lb

  build

Executing

  auto/build script.
  >> > >
  [2018-11-05 22:29:17] lb

build noauto
live-build 1:20180925
Building config tree for

  a debian/stable/amd64

system

  >> >
  > [2018-11-05 22:29:17]

lb bootstrap
Setting up cleanup

  function
  >> > >

[2018-11-05

  22:29:17] lb bootstrap_cache

restore
Restoring bootstrap stage

  from cache...
  >> > >

[2018-11-05

  22:29:17] lb

bootstrap_debootstrap

  >>
  > > P: Begin

bootstrapping system...

  >> > > P: If the

following stage

  fails, the most likely cause

of the

  >>
  > > problem
  >> > > is with
  your mirror configuration or

a caching proxy.
Running debootstrap

  (download-only)...
  Retrieving InRelease
  Retrieving Release
  Retrieving Release.gpg
  Checking Release signature
  >> >
  > I: Valid Release

signature (key id

  >> > >
 

067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
Retrieving Packages
Validating Packages
Resolving dependencies of

  required packages...
  Resolving dependencies of

base packages...

  >> > >
  >>
  > > On Tue, 2018-11-06

at 09:08 +1100, Michael .

  >> > > > Hi
  everyone
  >> > > >

Usually I

  think when there is no reply

to a question people

  >> > > >

don't

  >> > > >

know

  >> > > > the

answer and I am

  sure this is probably the

case here but

  >> > > > this

is a

  >> > > >

crippling issue for me.

  It has literally stopped me

dead in my

  >> > > >

tracks.

  >> > > > I

don't really want

  to have to go back to

Stretch if I can help

  >> > > > it.
  >> > > > If
  >> > > >

anyone is using an up

  to date Buster (current

testing) system

  >> > > > to

use

  >> > > > Live

Build successfully

  please let me know otherwise

I'll

  >> > > >

assume Live

  >> > > >

Build isn't

  suitable for Buster and I

will revert back to

  >> > > >

Stretch.

  >> > > >

Cheers.

  >> > > >

Michael.

  >> > > >
  >> > > > >
Hi.
  >> > > >
  >> > > >

Haven't been around

  for a while because I

haven't come across

  >> > > > any
  >> > > >

issues, until now. Not

  sure if this is a bug or if

something

  >> > > > else

is

  >> > > >

causing this but on a

  new (everything is new)

install of Buster

  >> > > > and
  >> > > >

Live-Build I am getting

  this output
  >> > > >
  >> > > > lb
  >> > > >

clean

  >> > > >

[2018-09-17 07:41:21]

  lb clean
  Executing auto/clean

script.

  >> >
  > > [2018-09-17

07:41:21] lb clean noauto
Cleaning chroot

  >> > > > lb
  >> > > >

config

  >> > > >

[2018-09-17 07:41:26]

  lb config
  Updating config tree for a

debian/stretch/amd64 system
Symlinking

  hooks...
  >> > > > lb
  >> > > >

build

  >> > > >

[2018-09-17 07:41:36]

  lb build
  Executing auto/build

script.

  >> >
  > > [2018-09-17

07:41:36] lb build noauto
live-build

  1:20180618
  Building config tree for a

debian/stretch/amd64 system

  >> > > >

[2018-09-17 07:41:36]

  lb bootstrap
  Setting up cleanup function
  >> >
  > > [2018-09-17

07:41:36] lb bootstrap_cache

  restore

Restoring

  bootstrap stage from

cache...

  >> >
  > > [2018-09-17

07:41:36] lb bootstrap_debootstrap
debootstrap -

  command not found
  debootstrap can be obtained

from

  >>
  > > > http://ftp.debian.org/debian/pool/main/d/debootstrap/

On Debian based

  systems, debootstrap can be

installed with

  >> > > >

'apt-

  >> > > > get
  >> > > >

install

  debootstrap'.
  Begin unmounting

filesystems...

  >>
  > > > P: Saving

caches...

  >>
  > > >
  >> > > >
 
  >> >
  > > chroot: not found
  >> >
  >> > > >
  >> > > > As

already mentioned

  this is a new install so

there is nothing

  >> > > > in

it

  >> > > > (so

you can ignore the

  i386 folder name as this is

just a test

  >> > > >

run).

  >> > > > I
  >> > > > have

purged both live

  build, and its associated

packages and

  >> > > >

deboostrap and

  installed them again and I

still get this same

  >> > > >

output.

  >> > > > So

my questions are

  >> > > > 1.

Is live build not

  ready for use on Buster yet?

(because it

  >> > > >

creates

  >> > > > this
  Updating config tree for a

debian/stretch/amd64

  >> > > >

system"

  >> > > > 2.

Is there a clash

  with Live-build and

debootstrap somewhere

  >> > > >

making

  >> > > >

live-build not

  "see" debootstrap even

though it is installed?

  >> > > >
  >> > > > >

From memory

  live-build used to detect

the version it was

  >> > > > >

installed

  >> > > > >

on

  >> > > >
  >> > > > and

build an iso based

  on that unless it had been

told to do

  >> > > >

something

  >> > > >

different in the

  auto/config file. This one

is reverting back

  >> > > > to
  >> > > >

stretch even though it

  is installed on a buster

system.

  >>
  > > >
  >> > > >
  Cheers.
  >> > > >

Michael.

  >> > > >
  >> > >
  >>
  > > --
  >> > > Kind
  regards,
  >> > > Luca

Boccassi

  >
  > --
  > Kind regards,
  > Luca
  Boccassi

[eznix]

I too have experienced this problem. For me, the $PATH was the cause. When
I su in Buster, my $PATH does not contain /sbin and /usr/sbin. debootstrap
is in /usr/sbin/ and hence could not be found when running live-build when
su'ing in the terminal. It worked perfectly when I exported /usr/sbin and
/sbin into my $PATH. Live-build also worked perfectly when I su -l in the
terminal. Hope this helps. It does not appear to be a live-build problem,
but a $PATH problem.

[Michael .]

Thank you eznix. Today is the 1st day since my last message I have had
an opportunity to look at this and it now works. I very much
appreciate your help.

Post by eznix
I too have experienced this problem. For me, the $PATH was the cause. When
I su in Buster, my $PATH does not contain /sbin and /usr/sbin. debootstrap
is in /usr/sbin/ and hence could not be found when running live-build when
su'ing in the terminal. It worked perfectly when I exported /usr/sbin and
/sbin into my $PATH. Live-build also worked perfectly when I su -l in the
terminal. Hope this helps. It does not appear to be a live-build problem,
but a $PATH problem.

[eznix]

Glad to help! I hope my email did not come off condescending. I only wanted
to relay my experience and what I found to help with the problem. Thanks
for the update.

Post by Michael .
Thank you eznix. Today is the 1st day since my last message I have had
an opportunity to look at this and it now works. I very much
appreciate your help.

Post by eznix
I too have experienced this problem. For me, the $PATH was the cause.

When

Post by eznix
I su in Buster, my $PATH does not contain /sbin and /usr/sbin.

debootstrap

Post by eznix
is in /usr/sbin/ and hence could not be found when running live-build

when

Post by eznix
su'ing in the terminal. It worked perfectly when I exported /usr/sbin and
/sbin into my $PATH. Live-build also worked perfectly when I su -l in the
terminal. Hope this helps. It does not appear to be a live-build problem,
but a $PATH problem.

...