My fault for not catching this. In my development environment, I keep all my patches in /opt/patches/... and the iso files in /opt/iso/... While testing I used the patch directory, /opt/patches/drupal7, instead of the tar.gz file which I didn't create until ready to release and apparently didn't test the final time. The problem is that the tar.gz is extracting to tmp.0GlHPQqfUG/drupal7 instead of tmp.0GlHPQqfUG/turnkey-drupal7-11.x-lucid-x86-patch-beta1 where tklpatch expects to find the extracted patch.
Probably the easiest workaround is to create /opt/patches and manually extract the patch file there. Then issue the tklpatch command as
My fault for not catching
My fault for not catching this. In my development environment, I keep all my patches in /opt/patches/... and the iso files in /opt/iso/... While testing I used the patch directory, /opt/patches/drupal7, instead of the tar.gz file which I didn't create until ready to release and apparently didn't test the final time. The problem is that the tar.gz is extracting to tmp.0GlHPQqfUG/drupal7 instead of tmp.0GlHPQqfUG/turnkey-drupal7-11.x-lucid-x86-patch-beta1 where tklpatch expects to find the extracted patch.
Probably the easiest workaround is to create /opt/patches and manually extract the patch file there. Then issue the tklpatch command as
If that doesn't work, let me know. In the meantime I'll try to rework and test the patch and issue a new release.
Information is free, knowledge is acquired, but wisdom is earned.