From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Mp599-00064I-IQ for garchives@archives.gentoo.org; Sat, 19 Sep 2009 18:58:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 85079E080E; Sat, 19 Sep 2009 18:58:58 +0000 (UTC) Received: from www01.badapple.net (www01.badapple.net [64.79.219.163]) by pigeon.gentoo.org (Postfix) with ESMTP id 6426CE080E for ; Sat, 19 Sep 2009 18:58:58 +0000 (UTC) Received: from [10.13.213.102] (unknown [76.14.71.183]) (Authenticated sender: ramin@badapple.net) by www01.badapple.net (Postfix) with ESMTPSA id D340741906F for ; Sat, 19 Sep 2009 11:58:57 -0700 (PDT) Message-ID: <4AB529F1.5090601@badapple.net> Date: Sat, 19 Sep 2009 11:58:57 -0700 From: kashani User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] trying to track down broken dependency References: <4AB40C62.1090204@badapple.net> <58965d8a0909181549n5fa37e65s27331a683178d2ff@mail.gmail.com> <4AB438B3.1070107@badapple.net> <20090919093854.2689f2c3@lappy.evolone.org> In-Reply-To: <20090919093854.2689f2c3@lappy.evolone.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 28e6cb71-1c3a-43af-b309-33ecccee7f95 X-Archives-Hash: 3be8662001f868f716ace9d9d1762f96 Michael Higgins wrote: > Perl 5.8 is at end-of-life. > > Gentoo volunteers are *very* (PAINFULLY) slow in getting 5.10 into the > official tree. They unfortunately need all the help they can get, since > this is a major failure of Gentoo to "keep up" with the upstream > developers and (FWIW) other "distros". This isn't news, BTW... > > Please report the error on b.g.o., so the perl herd (or whoever is > really doing the work now) can fix the problem. Also, #gentoo-perl is > the only place to get any real help on these gentoo-perl issues... > (devolution to IRC "chat" being yet another systemic failure, IMO, but > that's the place the folks making these mistakes may communicate with > users). > > Better yet, take the plunge and go on to install 5.10.1 from the > perl-experimental overlay (good luck with *that*) and report how you > fixed any issues you come across. It's only going to get to be a worse > mess unless everyone who is able picks up the slack for these guys. And > you will have to upgrade eventually anyway... so why not now? > > My $.02, not terribly helpful though, I suppose. :( FWIW I'm also running RT and it's 200 odd Perl module dependencies on the same machine. I can assure you that I have no interest in updating the whole stack to perl-5.10 and the QA nightmare that will require. I solved this the old fashioned way after a bit of coffee this morning. Still seems like Portage should be smart enough to tell about the missing dep if I asked it correctly. 1. created fake perl-5.10 ebuild which was really just renaming perl-5.8.8-r2 and commenting out any {$PN} patches so I didn't need to make a bunch of fake patch files in files/. This allowed portage to tell me what was requiring perl-5.10 instead of bombing out. 2. Figured out that while the virtual/perl packages weren't specifying perl 5.10 the actual perl-core were which is why it didn't make sense earlier. 3. Doctored up portage.mask to mask the errant virtuals >=virtual/perl-Digest-SHA-5.47 >=virtual/perl-Test-Harness-3.17 Thought grumpy thoughts at developers who let packages into ~x86 with completely broken deps. Hard mask that crap next time. 4. Add the needed packages in portage.keywords and make it pretty and organized. # bugzilla and deps for bugzilla-3.4.1-r1, added 20090919 www-apps/bugzilla dev-perl/Daemon-Generic dev-perl/DateTime-TimeZone dev-perl/Data-ObjectDriver dev-perl/File-Flock dev-perl/TheSchwartz perl-core/Module-Build perl-core/Test-Harness virtual/perl-Module-Build virtual/perl-Test-Harness And now I've got a fancy new bugzilla. kashani