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 <bl...@debian.org> wrote: > 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... > > On Tue, 2018-11-06 at 09:08 +1100, Michael . wrote: >> 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 >> >> root@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 >> root@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... >> root@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 >> root@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. >> > -- > Kind regards, > Luca Boccassi
