This was originally posted on#73 a couple of days ago. I've moved it here to separate the 2 issues.

Unfortunately, the below is not working as I suggested it might, but I've added more info further down; as acomment.

I have just uploadedluks andtheme-zukitwo pacakges to my dev-test repo. They are the 2 packages you'll need if you want to have a look at building BitKey for v15.0. There will almost certainly be some work needed to get BitKey working with v15.0, but this would be a start.

I may be able to free up@qq7 to help you out a bit, but ideally I'd like to keep him on TurnKey v15.0 a little further along though, before I get him helping you out.

FWIW, you'll first need the v15.0 bootstrap:

cd /turnkey/fab/bootstrapsmkdir stretchwget http://mirror.turnkeylinux.org/turnkeylinux/images/bootstrap/bootstrap-stretch-amd64.tar.gztar -xvf bootstrap-stretch-amd64.tar.gz -C stretch

Then this would be the start for trying to build v15.0 BitKey (it will likely fail the first time due to missing packages; but it might work?):

cd commongit fetch origingit checkout stretch-dev

Then to build, you'll need to do something like this:

cd bitkeyexport RELEASE=debian/stretchexport DEV_TEST=y # please see notes belowmake

FWIW, I suggest of you do have a go at this, that you start a new branch of bitkey for testing and playing with this, that way it won't interfere with your current v14.x based work and you can go back and forth between the 2 branches as you wish.

Please feel free to post any stretch related issues here in the bitkey tracker. Please note if they're specifically Debian Stretch (i.e. v15.x) related though, so they don't get confused with other issues.

Caution on use ofDEV_TEST=y

DO NOT release any ISOs that are built withDEV_TEST=y! My personal repo is only for development and testing. It shouldn't contain anything malicious and should generally be safe and ok and would likely even be ok for your own (short term) usage. But things in there can change rapidly and breakages are always a possibility. There will be no security updates published there (or for any packages installed from there).

Also it's hosted from my own personal AWS account, so I pay for network traffic (it's pretty cheap so no need to worry about using it; but the charges rise exponentially the more people using it). So bottom line is, we don't want anyone running images that include that repo, unless they build them themselves and understand the situation!