CentOS - Nov 2008 - Problem building kernel (gpg problem) - 2.6.18-92.1.17

With new kernel, appeared some problems with build proccess here.

After many minutes waiting for rpmbuild were over, a gpg problem appears!!:

...
scripts/modsign/mod-extract.c:311: warning: format '%lx' expects type
'long unsigned int', but argument 3 has type 'Elf64_Xword'
+ KEYFLAGS='--no-default-keyring --homedir ..'
+ KEYFLAGS='--no-default-keyring --homedir .. --secret-keyring
../kernel.sec'
+ KEYFLAGS='--no-default-keyring --homedir .. --secret-keyring
../kernel.sec --keyring ../kernel.pub'
+ export KEYFLAGS
++ cat modnames
+ for i in '`cat modnames`'
+ sh ./scripts/modsign/modsign.sh
/var/tmp/kernel-2.6.18-92.1.17.1.el5_ArcosCom-root/lib/modules/2.6.18-92.1.17.1.el5_ArcosCom/kernel/sound/i2c/snd-cs8427.ko
CentOS
gpg: WARNING: unsafe permissions on homedir `..'
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
error: Bad exit status from /var/tmp/rpm-tmp.66856 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.66856 (%build)
...


With previous kernels I have no problem.

Taking a look into kernel-2.6.spec I saw this lines:

%if %{signmodules}
    gcc -o scripts/modsign/mod-extract scripts/modsign/mod-extract.c -Wall
    KEYFLAGS="--no-default-keyring --homedir .."
    KEYFLAGS="$KEYFLAGS --secret-keyring ../kernel.sec"
    KEYFLAGS="$KEYFLAGS --keyring ../kernel.pub"
    export KEYFLAGS

    for i in `cat modnames`
    do
      sh ./scripts/modsign/modsign.sh $i CentOS
      mv -f $i.signed $i
    done
    unset KEYFLAGS
%endif

I don't know how to correct this problem or if I need to configure gpg
with something. Or perhaps I need some "buildrequire" because the
build
process not found anything.

Any help?

Thanks!!

On Fri, Nov 7, 2008 at 1:09 AM, ArcosCom Linux User <linux at
arcoscom.com> wrote:
> With new kernel, appeared some problems with build proccess here.
>
> After many minutes waiting for rpmbuild were over, a gpg problem appears!!:
> gpg: WARNING: unsafe permissions on homedir `..'
> gpg: no default secret key: secret key not available
> gpg: signing failed: secret key not available
> error: Bad exit status from /var/tmp/rpm-tmp.66856 (%build)
This is a known issue and has been corrected.  If you download the
srpm again, you will get the fixed version.  The genkey file had an
incorrect entry.

Akemi

ArcosCom Linux User wrote:
> With new kernel, appeared some problems with build proccess here.
> 
> After many minutes waiting for rpmbuild were over, a gpg problem appears!!:
> 
> ...
> scripts/modsign/mod-extract.c:311: warning: format '%lx' expects
type
> 'long unsigned int', but argument 3 has type 'Elf64_Xword'
> + KEYFLAGS='--no-default-keyring --homedir ..'
> + KEYFLAGS='--no-default-keyring --homedir .. --secret-keyring
../kernel.sec'
> + KEYFLAGS='--no-default-keyring --homedir .. --secret-keyring
> ../kernel.sec --keyring ../kernel.pub'
> + export KEYFLAGS
> ++ cat modnames
> + for i in '`cat modnames`'
> + sh ./scripts/modsign/modsign.sh
>
/var/tmp/kernel-2.6.18-92.1.17.1.el5_ArcosCom-root/lib/modules/2.6.18-92.1.17.1.el5_ArcosCom/kernel/sound/i2c/snd-cs8427.ko
> CentOS
> gpg: WARNING: unsafe permissions on homedir `..'
> gpg: no default secret key: secret key not available
> gpg: signing failed: secret key not available
> error: Bad exit status from /var/tmp/rpm-tmp.66856 (%build)
> 
> 
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.66856 (%build)
> ...
> 
> 
> With previous kernels I have no problem.
> 
> Taking a look into kernel-2.6.spec I saw this lines:
> 
> %if %{signmodules}
>     gcc -o scripts/modsign/mod-extract scripts/modsign/mod-extract.c -Wall
>     KEYFLAGS="--no-default-keyring --homedir .."
>     KEYFLAGS="$KEYFLAGS --secret-keyring ../kernel.sec"
>     KEYFLAGS="$KEYFLAGS --keyring ../kernel.pub"
>     export KEYFLAGS
> 
>     for i in `cat modnames`
>     do
>       sh ./scripts/modsign/modsign.sh $i CentOS
>       mv -f $i.signed $i
>     done
>     unset KEYFLAGS
> %endif
> 
> I don't know how to correct this problem or if I need to configure gpg
> with something. Or perhaps I need some "buildrequire" because the
build
> process not found anything.
> 
> Any help?
> 
> Thanks!!
> 
I believe there was a problem with the initial .src.rpm file which has 
now been corrected. Can you try pulling down a fresh copy of the 
.src.rpm and try building it again.

Ned