Building a new system, trying to put in the monstrosity that is squeezecenter I had a build fail. Poked at it and the Module-Signature perl subcomponent build dies if it cannot find/use gpg. Manually installing app-crypt/gnupg allowed the aforementioned build to complete. So this is a missing dependency IMHO. Just getting into gentoo, so while this is probably a one-line edit somewhere I don't have a patch. 8-) Reproducible: Always Steps to Reproduce: 1. start with bare bones system 2. emerge dev-perl/Module-Signature 3. Notice fail 4. emerge gnupg 5. emerge dev-perl/Module-Signature 6. Notice Success.
Added cc@lavajoe@gentoo.org as he maintains media-sound/squeezeboxserver
Created attachment 250945 [details] Squeezebox Server 7.5.1 dependency tree As producer of the Squeezebox Server ebuild, I have to agree...! However, on my test 'bare' Gentoo VM I don't have app-crypt/gnupg installed and I find the ebuild installs OK, including building Module-Signature. The build dependency tree is as attached. I don't think this is anything particularly to do with the media-sound/squeezeboxserver ebuild, but I don't think there's necessarily a problem with Module-Signature either. The start of emerge --info on my test VM (where I'm not having this problem) is as follows: Portage 2.1.8.3 (default/linux/x86/10.0, gcc-4.4.3, glibc-2.11.2-r0, 2.6.31-gent oo-r10 i686) ================================================================= System uname: Linux-2.6.31-gentoo-r10-i686-QEMU_Virtual_CPU_version_0.12.5-with- gentoo-1.12.13 Timestamp of tree: Sat, 16 Oct 2010 20:15:02 +0000 app-shells/bash: 4.0_p37 dev-lang/python: 2.4.4-r6, 2.5.4-r3, 2.6.5-r3, 3.1.2-r4 sys-apps/baselayout: 1.12.13 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.65 sys-devel/automake: 1.10.3, 1.11.1 sys-devel/binutils: 2.20.1-r1 sys-devel/gcc: 4.4.3-r2 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b sys-devel/make: 3.81-r2 virtual/os-headers: 2.6.30-r1 ACCEPT_KEYWORDS="x86"
Hrm, I have tried to re-reproduce the problem and now its gone. I don't know what it was that was giving me the "gpg command not found" message that started this bug report. I do know that there was some gcc stuff going on near that message, and that when I unmerge gnupg and then emerge --oneshot Module-Signature I don't see any gcc invocations at all. I've already carried on with putting other stuff on this server so I cannot find my way back to the original error. ASIDE: I still also havn't managed to get squeezeboxserver to start. Some of my other work has led me to have versions of components newer than squeseboxserver cares to use, and I get freaky messages like "The following CPAN modules were found but cannot work with Squeezebox Server: File::BOM (loaded <not found>, need 0.13)" And a "found and loaded version <not found> instead of <number>" error message is somewhere very near my "this thing is crazy" threshold. I need the server for more that this one app and this one app "just worked" on another distro but isn't important enough for me reverse several days work. Might as well close the bug since I can no longer make it happen nor trace it back to its real cause. I know more about gentoo now so next-bug my initial data should be more hepful. 8-/
Interesting Factoid: the number of dev-perl/*.ebuild(s) that don't actually depend on dev-lang/perl is somewhat surprising. The fairly simple test script below had some interesting things to say for AA in /usr/portage/dev-perl/*/*.ebuild do if grep --quiet dev-lang/perl ${AA}; then echo ${AA} okay else echo ${AA} broken fi done | grep broken Spot checking the results with emerge --info bore out the results. I was inspired to check when I noticed perl itself was missing from your Module-Signature info burst above. This was borne out by my wipe of everything perl5 from a test box and then an attempt at emerge squeezeboxserver just to see if I could get a working sbs after a radical revert of what I'd updated via cpan.
(In reply to comment #4) > Interesting Factoid: the number of dev-perl/*.ebuild(s) that don't actually > depend on dev-lang/perl is somewhat surprising. You shouldn't ignore the inherited eclasses.
(In reply to comment #0) > Building a new system, trying to put in the monstrosity that is squeezecenter I > had a build fail. Poked at it and the Module-Signature perl subcomponent build > dies if it cannot find/use gpg. Manually installing app-crypt/gnupg allowed the > aforementioned build to complete. So this is a missing dependency IMHO. > > Just getting into gentoo, so while this is probably a one-line edit somewhere I > don't have a patch. 8-) > > Reproducible: Always > > Steps to Reproduce: > 1. start with bare bones system > 2. emerge dev-perl/Module-Signature > 3. Notice fail > 4. emerge gnupg > 5. emerge dev-perl/Module-Signature > 6. Notice Success. > Something is amiss with your problem: upon grepping the source, it appears it should be perfectly fine as long as Crypt::OpenPGP is installed, as it only uses gpg if that is not installed. as Crypt::OpenPGP is a DEPEND, you should have no issue. The other possibility is your using FEATURES="test" so we need a little more info on how you produced the problem. 1. What version of Module-Signature are you installing? Stable's 0.55 or Testings 0.66? 2. Please post (as an attachment ) a copy of the exact output of the problem you are encountering, from the start to the finish of the installation of Module-Signature. 3. Please post (as an attachment) your output of emerge --info Side evidence: 0.66's grep for 'gpg' : http://search.cpan.org/grep?cpanid=FLORA&release=Module-Signature-0.66&string=gpg&i=1&n=1&C=3 0.55's grep for 'gpg' : http://search.cpan.org/grep?cpanid=FLORA&release=Module-Signature-0.55&string=gpg&i=1&n=1&C=3 nb. You may have to blow away a few things in order to replicate your problem. As it is, it looks like this bug might drift towards closing as NEEDINFO.
I'll close this myself. I lost track of the bug after I did the manual step of adding gpg the problem was resolved. I wasn't good enough with portage at the time to get the information needed and then this bug fell off my radar. I don't know why I needed to put gpg in manually and I only have the one machine to test if the condition still holds and it is not a machine I can afford to gut right now. I tried to reproduce the problem in a qemu-kvm instance but as of this date, I couldn't make it happen again. Must have been making some obscure noob mistake that I can no longer make.
