FIrstly sorry for slow response. I've got my head down trying like mad to get the pieces in place for the first step of the v17.0 release.
Anyway, for some reason it looks like you don't have the bootstrap?! It should have been downloaded and set up during firstboot! Although TBH, once you get past that, you may hit more issues as I recently merged the v17.0 development code (Friday last week). I did try to make it backwards compatible, but it's quite possible I overlooked something?!
There are a few different options moving forward. But before I go into how to how you might fix that, please note that there is a v17.0rc1 (release candidate #1) of TKLDev sitting on the mirror. I haven't announced it yet as I've discovered a fairly major issue with it (or perhaps somewhat ironically, moreso an issue with the bullseye bootstrap). So I have held off announcing it until I've fixed the bullseye bootstrap (should be published by early next week).
IMO it would have more value for everyone if you used the 17.0rc1 TKLDev, rather than the old v16.1. The 17.0rc1 is based on the newer Debian 11/Bullseye base, so using that will help us testing. It will also mean that automatically, your test Bookstack build will also be Bullseye based (and will include common v17.0 code that we've developed - although it will still say that it's 16.0).
So to explicitly share the options moving forward:
Fix your current v16.1 TKLDev and build v16.x Bookstack ISO.
Fix your current v16.1 TKLDev and build a v17.x Bookstack ISO (RC).
Download the current v17.0rc1 TKLDev, build your own bootstrap and build a v17.x Bookstack ISO (RC).
Wait until next week and download the v17.0rc1 TKLDev and build a v17.x Bookstack ISO (RC).
1. Fix your current v16.1 TKLDev and build v16.x Bookstack ISO
I would expect that just running:
tkldev-setup
should work to fix the bootstrap. It will probably update common to the latest though, so you'll want to check out the v16.x branch. I.e.:
cd common
git remote set-branches origin '*'
git fetch origin
git checkout 16.x
To be on the safe side, you will also need to do the same for cdroots (although this one is named after the Debian codename - so you want 'buster'). I.e.:
I suggest that you double check things are working by building core. You don't need to build it all to iso, building to root.patched should be enough to prove it works. E.g.:
cd core
make clean
make root.patched
Assuming that works, then move on the Bookstack build.
2. Fix your current v16.1 TKLDev and build a v17.x Bookstack ISO (RC)
This is what we've been doing for the last month or so behind the scenes. Except now, everything is in the master branch.
Unfortunately because the bootstrap has issues, you'll need to build your own. So do that first:
cd /turnkey
git clone https://github.com/turnkeylinux/bootstrap.git
cd bootstrap
export RELEASE=debian/bullseye
make clean
make removelist
rsync --delete -Hac build/bootstrap/ $FAB_PATH/bootstraps/$(basename $RELEASE)/
Once that's done, then just follow the steps above, except checkout the master branch. E.g. the checkout commands:
git checkout master
Once you've done that, then again, I suggest trying to build core to 'root.patched'. The only difference this time is you need to have RELEASE set. If this is in a single shell session, then you already did that when you built the bootstrap (i.e. 'export RELEASE=debian/bullseye') but it won't hurt if you do it again. Then the same commands to build core to root.patched.
3. Download the current v17.0rc1 TKLDev, build your own bootstrap and build a v17.x Bookstack ISO (RC)
You can find the v17.0rc1 ISO (and the hash file if you wish) on the mirror.
Again you'll need to build your own bootstrap. It will download one at firstboot time, but as I said, it's broken. So remove that first:
rm -rf $FAB_PATH/bootstraps/bullseye*
Then follow the instructions above. You don't need to set RELEASE this time though. You also shouldn't need to change the common and cdroots git branches either. Finally, again test by building core to 'root.patched'.
4. Wait until next week and download the v17.0rc1 TKLDev and build a v17.x Bookstack ISO (RC)
This one is the easiest for me, as I don't need to explain anything... :)
Good luck with it no matter which way you go. Please post back if you have troubles and I'll try to post back ASAP (within the next 18-20 hours) but I'll be away over the weekend, so likely won't get a chance to post after that.
It looks like you don't have the bootstrap?!
FIrstly sorry for slow response. I've got my head down trying like mad to get the pieces in place for the first step of the v17.0 release.
Anyway, for some reason it looks like you don't have the bootstrap?! It should have been downloaded and set up during firstboot! Although TBH, once you get past that, you may hit more issues as I recently merged the v17.0 development code (Friday last week). I did try to make it backwards compatible, but it's quite possible I overlooked something?!
There are a few different options moving forward. But before I go into how to how you might fix that, please note that there is a v17.0rc1 (release candidate #1) of TKLDev sitting on the mirror. I haven't announced it yet as I've discovered a fairly major issue with it (or perhaps somewhat ironically, moreso an issue with the bullseye bootstrap). So I have held off announcing it until I've fixed the bullseye bootstrap (should be published by early next week).
IMO it would have more value for everyone if you used the 17.0rc1 TKLDev, rather than the old v16.1. The 17.0rc1 is based on the newer Debian 11/Bullseye base, so using that will help us testing. It will also mean that automatically, your test Bookstack build will also be Bullseye based (and will include common v17.0 code that we've developed - although it will still say that it's 16.0).
So to explicitly share the options moving forward:
1. Fix your current v16.1 TKLDev and build v16.x Bookstack ISO
I would expect that just running:
should work to fix the bootstrap. It will probably update common to the latest though, so you'll want to check out the v16.x branch. I.e.:
To be on the safe side, you will also need to do the same for cdroots (although this one is named after the Debian codename - so you want 'buster'). I.e.:
I suggest that you double check things are working by building core. You don't need to build it all to iso, building to root.patched should be enough to prove it works. E.g.:
Assuming that works, then move on the Bookstack build.
2. Fix your current v16.1 TKLDev and build a v17.x Bookstack ISO (RC)
This is what we've been doing for the last month or so behind the scenes. Except now, everything is in the master branch.
Unfortunately because the bootstrap has issues, you'll need to build your own. So do that first:
Once that's done, then just follow the steps above, except checkout the master branch. E.g. the checkout commands:
Once you've done that, then again, I suggest trying to build core to 'root.patched'. The only difference this time is you need to have RELEASE set. If this is in a single shell session, then you already did that when you built the bootstrap (i.e. 'export RELEASE=debian/bullseye') but it won't hurt if you do it again. Then the same commands to build core to root.patched.
3. Download the current v17.0rc1 TKLDev, build your own bootstrap and build a v17.x Bookstack ISO (RC)
You can find the v17.0rc1 ISO (and the hash file if you wish) on the mirror.
Again you'll need to build your own bootstrap. It will download one at firstboot time, but as I said, it's broken. So remove that first:
Then follow the instructions above. You don't need to set RELEASE this time though. You also shouldn't need to change the common and cdroots git branches either. Finally, again test by building core to 'root.patched'.
4. Wait until next week and download the v17.0rc1 TKLDev and build a v17.x Bookstack ISO (RC)
This one is the easiest for me, as I don't need to explain anything... :)
Good luck with it no matter which way you go. Please post back if you have troubles and I'll try to post back ASAP (within the next 18-20 hours) but I'll be away over the weekend, so likely won't get a chance to post after that.