I build dahdi-linux from source for use on the machine I also run rawhide on and currently I can getting an error message "Can't read private key" during the build. Is there some info on where I should look to work around this? I boot using BIOS, so I don't need to have modules signed.
On Fri, Oct 26, 2012 at 01:24:31PM -0500, Bruno Wolff III wrote:
I build dahdi-linux from source for use on the machine I also run rawhide on and currently I can getting an error message "Can't read private key" during the build. Is there some info on where I should look to work around this? I boot using BIOS, so I don't need to have modules signed.
Can you post the full output? We obviously don't ship the private key, and we're still working on 3rd party signing so you're forging new ground here.
josh
On Fri, Oct 26, 2012 at 14:45:30 -0400, Josh Boyer jwboyer@redhat.com wrote:
On Fri, Oct 26, 2012 at 01:24:31PM -0500, Bruno Wolff III wrote:
I build dahdi-linux from source for use on the machine I also run rawhide on and currently I can getting an error message "Can't read private key" during the build. Is there some info on where I should look to work around this? I boot using BIOS, so I don't need to have modules signed.
Can you post the full output? We obviously don't ship the private key, and we're still working on 3rd party signing so you're forging new ground here.
josh
I am attaching the output from running rpmbuild and the specfile. I didn't include the patches or dahdi-linux, so you can't run it yourself based on this.
On Fri, Oct 26, 2012 at 01:55:26PM -0500, Bruno Wolff III wrote:
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.huqckt
<snip>
make -C /lib/modules/3.7.0-0.rc2.git3.1.fc19.i686.PAE/build SUBDIRS=/home/bruno/rpmbuild/BUILD/dahdi-linux-2.6.1/drivers/dahdi DAHDI_INCLUDE=/home/bruno/rpmbuild/BUILD/dahdi-linux-2.6.1/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes INSTALL_MOD_PATH=/home/bruno/rpmbuild/BUILDROOT/dahdi-linux-2.6.1-32.fc19.i386 INSTALL_MOD_DIR=dahdi modules_install
Can you modify that call above to add a V=1 and provide the output of that?
Basically, upstream decided to sign the modules at 'modules_install' time if you have modsign enabled. We'll need to work with that change and figure out how to pass it your own keys.
josh
On Fri, Oct 26, 2012 at 15:34:20 -0400, Josh Boyer jwboyer@redhat.com wrote:
On Fri, Oct 26, 2012 at 01:55:26PM -0500, Bruno Wolff III wrote:
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.huqckt
<snip>
make -C /lib/modules/3.7.0-0.rc2.git3.1.fc19.i686.PAE/build SUBDIRS=/home/bruno/rpmbuild/BUILD/dahdi-linux-2.6.1/drivers/dahdi DAHDI_INCLUDE=/home/bruno/rpmbuild/BUILD/dahdi-linux-2.6.1/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes INSTALL_MOD_PATH=/home/bruno/rpmbuild/BUILDROOT/dahdi-linux-2.6.1-32.fc19.i386 INSTALL_MOD_DIR=dahdi modules_install
Can you modify that call above to add a V=1 and provide the output of that?
The output after that change is attached.
On Fri, Oct 26, 2012 at 03:06:39PM -0500, Bruno Wolff III wrote:
On Fri, Oct 26, 2012 at 15:34:20 -0400, Josh Boyer jwboyer@redhat.com wrote:
On Fri, Oct 26, 2012 at 01:55:26PM -0500, Bruno Wolff III wrote:
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.huqckt
<snip>
make -C /lib/modules/3.7.0-0.rc2.git3.1.fc19.i686.PAE/build SUBDIRS=/home/bruno/rpmbuild/BUILD/dahdi-linux-2.6.1/drivers/dahdi DAHDI_INCLUDE=/home/bruno/rpmbuild/BUILD/dahdi-linux-2.6.1/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes INSTALL_MOD_PATH=/home/bruno/rpmbuild/BUILDROOT/dahdi-linux-2.6.1-32.fc19.i386 INSTALL_MOD_DIR=dahdi modules_install
Can you modify that call above to add a V=1 and provide the output of that?
The output after that change is attached.
I haven't forgotten about this. Was out on PTO and then had to catch up yesterday. I'll reply with some suggestions soon.
josh
On Wed, Oct 31, 2012 at 08:24:56 -0400, Josh Boyer jwboyer@redhat.com wrote:
I haven't forgotten about this. Was out on PTO and then had to catch up yesterday. I'll reply with some suggestions soon.
Thanks for the update. I had been wanting to ping you about this, but I know you guys are busy so I was going to wait until the kernel meeting on Friday.
kernel@lists.fedoraproject.org