Received: from lavabit.com (lavabit.com [38.147.122.66]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 33749780DE8 for <~alpine/devel@lists.alpinelinux.org>; Fri, 26 Nov 2021 17:12:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by doris.lavabit.com (Postfix) with ESMTP id 287A9FAE0797 for <~alpine/devel@lists.alpinelinux.org>; Fri, 26 Nov 2021 11:12:11 -0600 (CST) To: ~alpine/devel@lists.alpinelinux.org From: Ladar Levison Subject: Alpine 3.15.0 Installer is Broken... Message-ID: Date: Fri, 26 Nov 2021 09:36:37 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------0C13AC7E2D5FD3ED53FD8DBA" Content-Language: en-US This is a multi-part message in MIME format. --------------0C13AC7E2D5FD3ED53FD8DBA Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Keep calm and carry on. The issue only appears to break automated installs. Specifically, the setup-alpine install script isn't loading, or using answer files. I actually think the bug isn't with the installer but with the shell. When I ran the script using sh -x I noticed it was sourcing the file, but the variables were still empty. As a short term workaround, I placed an export in front of each variable in my answer file, and was able to get it working again with the command "source generic.alpine314.vagrant.cfg ; sh /sbin/setup-alpine -f /root/generic.alpine315.vagrant.cfg" ... I don't know if the sh in front setup-alpine, or the fully qualified paths are necessary. I added them during troubleshooting, and haven't checked to see if it still works once they're removed. Like I said, I think the issue has to do with the shell environment. L~ --------------0C13AC7E2D5FD3ED53FD8DBA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit

Keep calm and carry on. The issue only appears to break automated installs. Specifically, the setup-alpine install script isn't loading, or using answer files. I actually think the bug isn't with the installer but with the shell. When I ran the script using sh -x I noticed it was sourcing the file, but the variables were still empty.

As a short term workaround, I placed an export in front of each variable in my answer file, and was able to get it working again with the command "source generic.alpine314.vagrant.cfg ; sh /sbin/setup-alpine -f /root/generic.alpine315.vagrant.cfg" ... I don't know if the sh in front setup-alpine, or the fully qualified paths are necessary. I added them during troubleshooting, and haven't checked to see if it still works once they're removed.

Like I said, I think the issue has to do with the shell environment.

L~

--------------0C13AC7E2D5FD3ED53FD8DBA--