[gentoo-user] Could not emerge "app-crypt/gnupg-1.4.2-r2" due to new kernel being emerged too

[gentoo-user] Could not emerge "app-crypt/gnupg-1.4.2-r2" due to new kernel being emerged too

[Jules Colding]

Hi,

Todays "emerge -vauDN world" failed with gnupg not being emerged. The
reason seems to be that I am emerging a new kernel too. This new kernel
has obviously not been configured/build yet which makes gnupg unable to
find .config in "/usr/src/linux/". I expect this problem to go away when
the new kernel is up and running. emerge output below.


Best regards,
  jules


################### emerge output ####################
>>> emerge (12 of 14) app-crypt/gnupg-1.4.2-r2 to /
>>> Downloading http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/distfiles/gnupg-1.4.2.tar.bz2
--10:56:58--  http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/distfiles/gnupg-1.4.2.tar.bz2
           => `/usr/portage/distfiles/gnupg-1.4.2.tar.bz2'
Resolving ftp.belnet.be... 193.190.198.20, 2001:6a8:3c80:0:203:baff:fe39:f931
Connecting to ftp.belnet.be|193.190.198.20|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,891,177 (2.8M) [application/x-tar]

100%[=========================================================================================================================================================>] 2,891,177    284.97K/s    ETA 00:00

10:57:10 (251.27 KB/s) - `/usr/portage/distfiles/gnupg-1.4.2.tar.bz2' saved [2891177/2891177]

>>> md5 files   ;-) gnupg-1.4.2-r2.ebuild
>>> md5 files   ;-) gnupg-1.2.6.ebuild
>>> md5 files   ;-) gnupg-1.4.2-r1.ebuild
>>> md5 files   ;-) gnupg-1.9.19.ebuild
>>> md5 files   ;-) gnupg-1.4.1-r1.ebuild
>>> md5 files   ;-) gnupg-1.4.1.ebuild
>>> md5 files   ;-) gnupg-1.9.18.ebuild
>>> md5 files   ;-) files/digest-gnupg-1.2.6
>>> md5 files   ;-) files/digest-gnupg-1.4.1
>>> md5 files   ;-) files/digest-gnupg-1.4.1-r1
>>> md5 files   ;-) files/digest-gnupg-1.4.2-r1
>>> md5 files   ;-) files/digest-gnupg-1.4.2-r2
>>> md5 files   ;-) files/gnupg-1.4.2-badruman.patch
>>> md5 files   ;-) files/gnupg-1.2.6-ppc64.patch
>>> md5 files   ;-) files/gnupg-1.4.2-keyserver.patch
>>> md5 files   ;-) files/digest-gnupg-1.9.18
>>> md5 files   ;-) files/digest-gnupg-1.9.19
>>> md5 files   ;-) files/gnupg-1.4.2-selftest.patch
>>> md5 files   ;-) files/gnupg-1.4.1-selftest.patch
>>> md5 files   ;-) files/gnupg-1.4.2-jari.patch
>>> md5 src_uri ;-) gnupg-1.4.2.tar.bz2
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     2.6.14-gentoo-r2

 * getfilevar requires 2 variables, with the second a valid file.
 *    getfilevar <VARIABLE> <CONFIGFILE>
 * Could not find a usable .config in the kernel source directory.
 * Please ensure that /usr/src/linux points to a configured set of Linux sources.
 * If you are using KBUILD_OUTPUT, please set the environment var so that
 * it points to the necessary object directory so that it might find .config.

!!! ERROR: app-crypt/gnupg-1.4.2-r2 failed.
!!! Function linux-info_pkg_setup, Line 526, Exitcode 1
!!! Unable to calculate Linux Kernel version
!!! If you need support, post the topmost build error, NOT this status message.


################### emerge --info ####################
omc-2 ~ # emerge --info
Portage 2.0.51.22-r3 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.13-gentoo-r3 x86_64)
=================================================================
System uname: 2.6.13-gentoo-r3 x86_64 AMD Opteron(tm) Processor 252
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://pandemonium.tiscali.de/pub/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo http://mirror.gentoo.no/ http://gentoo.prz.rzeszow.pl http://ftp.du.se/pub/os/gentoo ftp://mirror.pudas.net/gentoo"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="amd64 X aac aalib alsa audiofile avi berkdb bitmap-fonts browserplugin bzip2 cdr crypt cups curl dvd dvdr dvdread eds emacs emboss encode esd exif expat fam fbcon foomaticdb fortran gdbm gif glut gnome gstreamer gtk gtk2 hal iconv imlib ipv6 java jpeg lcms ldap libwww lua lzw lzw-tiff mad mng motif mozilla mp3 mpeg ncurses nls nptl nptlonly nsplugin nvidia ogg opengl oss pam pdflib perl png python quicktime readline recode sdl slang spell ssl symlink tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales vorbis xine xml2 xmms xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Could not emerge "app-crypt/gnupg-1.4.2-r2" due to new kernel being emerged too

[Holly Bostick]

Jules Colding schreef:
> Hi,
> 
> Todays "emerge -vauDN world" failed with gnupg not being emerged. The
>  reason seems to be that I am emerging a new kernel too. This new 
> kernel has obviously not been configured/build yet which makes gnupg 
> unable to find .config in "/usr/src/linux/". I expect this problem to
> go away when the new kernel is up and running. emerge output below.
> 
> 
> Best regards, jules
> 

Or, you could just change the /usr/src/symlink back to your
currently-configured kernel, emerge gnupg, then change it (the symlink)
back to point at the new, unconfigured kernel.

I take it you're using the 'symlink' USE flag, which does this
automatically. I usually do too, and had a similar problem with a
different program just a week or two ago. Fortunately, I noticed that it
was going to happen before the emerge proceeded (I was getting a new
kernel, and upgrading the ati-drivers package, which I know must compile
against a configured kernel), so I just disabled the 'symlink' USE flag
for the new, about-to-be-downloaded kernel *only* (and learned that you
can manage specific versions of an app in /etc/portage/package.use), so
that the symlink was not changed, and the ati-drivers emerged normally
against my current, configured kernel.

Then I manually redirected the /usr/src/linux symlink to the new,
uncompiled kernel for the later kernel upgrade. So I only had to do the
redirect once, and it all worked out fine. Of course I had to re-emerge
the ati-drivers, but that's normal anyway when upgrading a kernel.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Could not emerge "app-crypt/gnupg-1.4.2-r2" due to new kernel being emerged too

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 645 bytes --]

On Thu, 24 Nov 2005 12:49:04 +0100, Holly Bostick wrote:

> Fortunately, I noticed that it
> was going to happen before the emerge proceeded (I was getting a new
> kernel, and upgrading the ati-drivers package, which I know must compile
> against a configured kernel), so I just disabled the 'symlink' USE flag
> for the new, about-to-be-downloaded kernel *only* (and learned that you
> can manage specific versions of an app in /etc/portage/package.use),

Couldn't you have achieved the same with less effort with

USE="-symlink" emerge world -blah

?


-- 
Neil Bothwick

Please rotate your phone 90 degrees and try again.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Could not emerge "app-crypt/gnupg-1.4.2-r2" due to new kernel being emerged too

[Holly Bostick]

Neil Bothwick schreef:
> On Thu, 24 Nov 2005 12:49:04 +0100, Holly Bostick wrote:
> 
> 
>> Fortunately, I noticed that it was going to happen before the 
>> emerge proceeded (I was getting a new kernel, and upgrading the 
>> ati-drivers package, which I know must compile against a configured
>>  kernel), so I just disabled the 'symlink' USE flag for the new, 
>> about-to-be-downloaded kernel *only* (and learned that you can 
>> manage specific versions of an app in /etc/portage/package.use),
> 
> 
> Couldn't you have achieved the same with less effort with
> 
> USE="-symlink" emerge world -blah
> 
> ?

Yes (qualified yes), but

1) I'm training myself out of changing USE flags on the command line
(though it would have been OK in this case, the reason I have a general
policy is to keep to it, not except it :-) )

2) I learned something (because I don't want to use USE= on the command
line, I "had to" use package.use, which I didn't know up to that moment
allowed specification of package versions. But I found that

=sys-kernel/gentoo-sources-2.6.13-r5 -symlink

is actually valid, which is useful information, enabling me to turn the
USE flag off for just this one emerge, without disturbing later kernels
for which I want to keep the 'symlink' flag default enabled.

Since this situation is not terribly likely to occur again-- an upgrade
to the ati-drivers being offered in the same operation as a new kernel,
given that the ati-drivers don't update that terribly often, and on a
schedule, and since I often mask shiny-new kernels because the
ati-drivers are generally unlikely to compile against them lately--
knowing that a 'oneshot mask' is possible in package.use is handy).

So yes, it would have been easier to do it the way you say, but I find
taking unexpected opportunities to explore the capabilities of Portage
more valuable than doing things the easy way (sometimes).

Holly



-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Could not emerge "app-crypt/gnupg-1.4.2-r2" due to new kernel being emerged too

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

On Thu, 24 Nov 2005 13:52:44 +0100, Holly Bostick wrote:

> > Couldn't you have achieved the same with less effort with
> > 
> > USE="-symlink" emerge world -blah

> Yes (qualified yes), but
> 
> 1) I'm training myself out of changing USE flags on the command line
> (though it would have been OK in this case, the reason I have a general
> policy is to keep to it, not except it :-) )

Changing USE flags on the commands line generally is frowned uponi
because the effect is transient, only affecting that one emerge. But this
is exactly what is needed in this case.

> =sys-kernel/gentoo-sources-2.6.13-r5 -symlink
> 
> is actually valid, which is useful information, enabling me to turn the
> USE flag off for just this one emerge, without disturbing later kernels
> for which I want to keep the 'symlink' flag default enabled.

Except it's not really "just this one emerge" but all emerges of that
package and version, although the two are likely to coincide.

> So yes, it would have been easier to do it the way you say, but I find
> taking unexpected opportunities to explore the capabilities of Portage
> more valuable than doing things the easy way (sometimes).

Fair comment.


-- 
Neil Bothwick

Do radioactive cats have 18 half-lives?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]