[gentoo-user] trying to track down broken dependency

[gentoo-user] trying to track down broken dependency

[kashani]

kashani@www01 ~ $ emerge -pvt bugzilla
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!

emerge: there are no ebuilds to satisfy "~dev-lang/perl-5.10.1".
(dependency required by "perl-core/Module-Build-0.35" [ebuild])
(dependency required by "dev-perl/DateTime-TimeZone-0.98" [ebuild])
(dependency required by "www-apps/bugzilla-3.4.1-r1" [ebuild])
(dependency required by "bugzilla" [argument])

	I don't see anything in man emerge that would help me track down the 
missing dependency. Is there any easy way to do this or do I have to 
track it down the Modeule-Build dependency tree which looks to be the 
culprit.

kashani

Re: [gentoo-user] trying to track down broken dependency

[Paul Hartman]

On Fri, Sep 18, 2009 at 5:40 PM, kashani <kashani-list@badapple.net> wrote:
> kashani@www01 ~ $ emerge -pvt bugzilla
> These are the packages that would be merged, in reverse order:
> Calculating dependencies... done!
>
> emerge: there are no ebuilds to satisfy "~dev-lang/perl-5.10.1".
> (dependency required by "perl-core/Module-Build-0.35" [ebuild])
> (dependency required by "dev-perl/DateTime-TimeZone-0.98" [ebuild])
> (dependency required by "www-apps/bugzilla-3.4.1-r1" [ebuild])
> (dependency required by "bugzilla" [argument])
>
>        I don't see anything in man emerge that would help me track down the
> missing dependency. Is there any easy way to do this or do I have to track
> it down the Modeule-Build dependency tree which looks to be the culprit.
>
> kashani

What version of bugzilla are you trying to emerge? That perl is newer
than any I see in my portage. Are you using an overlay?
www-apps/bugzilla-3.4.1-r1 seems to emerge fine and works with perl
5.8 here.

Re: [gentoo-user] trying to track down broken dependency

[Paul Hartman]

On Fri, Sep 18, 2009 at 5:49 PM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Fri, Sep 18, 2009 at 5:40 PM, kashani <kashani-list@badapple.net> wrote:
>> kashani@www01 ~ $ emerge -pvt bugzilla
>> These are the packages that would be merged, in reverse order:
>> Calculating dependencies... done!
>>
>> emerge: there are no ebuilds to satisfy "~dev-lang/perl-5.10.1".
>> (dependency required by "perl-core/Module-Build-0.35" [ebuild])
>> (dependency required by "dev-perl/DateTime-TimeZone-0.98" [ebuild])
>> (dependency required by "www-apps/bugzilla-3.4.1-r1" [ebuild])
>> (dependency required by "bugzilla" [argument])
>>
>>        I don't see anything in man emerge that would help me track down the
>> missing dependency. Is there any easy way to do this or do I have to track
>> it down the Modeule-Build dependency tree which looks to be the culprit.
>>
>> kashani
>
> What version of bugzilla are you trying to emerge? That perl is newer
> than any I see in my portage. Are you using an overlay?
> www-apps/bugzilla-3.4.1-r1 seems to emerge fine and works with perl
> 5.8 here.

Oops, I see you're trying the same bugzilla. So I wonder what kind of
overlays or unmasking might be going on to want a version of perl
that's not in portage.

Re: [gentoo-user] trying to track down broken dependency

[kashani]

Paul Hartman wrote:
> On Fri, Sep 18, 2009 at 5:40 PM, kashani <kashani-list@badapple.net> wrote:
>> kashani@www01 ~ $ emerge -pvt bugzilla
>> These are the packages that would be merged, in reverse order:
>> Calculating dependencies... done!
>>
>> emerge: there are no ebuilds to satisfy "~dev-lang/perl-5.10.1".
>> (dependency required by "perl-core/Module-Build-0.35" [ebuild])
>> (dependency required by "dev-perl/DateTime-TimeZone-0.98" [ebuild])
>> (dependency required by "www-apps/bugzilla-3.4.1-r1" [ebuild])
>> (dependency required by "bugzilla" [argument])
>>
>>        I don't see anything in man emerge that would help me track down the
>> missing dependency. Is there any easy way to do this or do I have to track
>> it down the Modeule-Build dependency tree which looks to be the culprit.
>>
>> kashani
> 
> What version of bugzilla are you trying to emerge? That perl is newer
> than any I see in my portage. Are you using an overlay?
> www-apps/bugzilla-3.4.1-r1 seems to emerge fine and works with perl
> 5.8 here.
> 

	I'm trying to get bugzilla-3.4.1-r1 (or 3.4.1) to work which is just 
~x86 and not any overlay. I'm planning to update a system in Nov and 
wanted to play with the latest build at home. Mostly interested in 3.4.1 
since the API is a bit newer and not completely backwards compatible. 
Has a few nice things in it though.

	Module-Build-0.35 doesn't seem to require perl 5.10 in the ebuild so it 
must be a dependency of a dependency. Same in DateTime-TimeZone. I'd 
like portage to tell me where the dependency tree is breaking, ie which 
package is asking for perl-5.10, so I can mask or futz with the ebuild 
for that package appropriately.

kashani

Re: [gentoo-user] trying to track down broken dependency

[Michael Higgins]

On Fri, 18 Sep 2009 18:49:39 -0700
kashani <kashani-list@badapple.net> wrote:

> Paul Hartman wrote:
> > On Fri, Sep 18, 2009 at 5:40 PM, kashani
> > <kashani-list@badapple.net> wrote:
> >> kashani@www01 ~ $ emerge -pvt bugzilla
> >> These are the packages that would be merged, in reverse order:
> >> Calculating dependencies... done!
> >>
> >> emerge: there are no ebuilds to satisfy "~dev-lang/perl-5.10.1".
> >> (dependency required by "perl-core/Module-Build-0.35" [ebuild])
> >> (dependency required by "dev-perl/DateTime-TimeZone-0.98" [ebuild])
> >> (dependency required by "www-apps/bugzilla-3.4.1-r1" [ebuild])
> >> (dependency required by "bugzilla" [argument])
> >>
> >>        I don't see anything in man emerge that would help me track
> >> down the missing dependency. Is there any easy way to do this or
> >> do I have to track it down the Modeule-Build dependency tree which
> >> looks to be the culprit.
> >>
> >> kashani
> > 
> > What version of bugzilla are you trying to emerge? That perl is
> > newer than any I see in my portage. Are you using an overlay?
> > www-apps/bugzilla-3.4.1-r1 seems to emerge fine and works with perl
> > 5.8 here.

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. :(

Cheers,

-- Michael Higgins

Re: [gentoo-user] trying to track down broken dependency

[Volker Armin Hemmann]

On Samstag 19 September 2009, Michael Higgins wrote:

> 
> 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).

the devolution are the forums - with irc and mailing lists being the original 
forms to find help.

[gentoo-user] Re: trying to track down broken dependency

[Torsten Veller]

* Michael Higgins <linux@evolone.org>:
> 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).

This is nonsense, Michael.

https://bugs.gentoo.org/show_bug.cgi?id=280726
https://bugs.gentoo.org/show_bug.cgi?id=219889#c24
https://bugs.gentoo.org/show_bug.cgi?id=283795

"I needed to add the perl-core packages for Module-Build and
Test-Harness, as well as the virtuals [to package.keywords]" (#219889)

> My $.02, not terribly helpful though, I suppose. :(

No, it was not helpful :(

Re: [gentoo-user] trying to track down broken dependency

[kashani]

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

[gentoo-user] Re: trying to track down broken dependency

[Torsten Veller]

* kashani <kashani-list@badapple.net>:
> 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.

There are no broken deps and there is no crap that should be masked.

Re: [gentoo-user] Re: trying to track down broken dependency

[kashani]

Torsten Veller wrote:
> * kashani <kashani-list@badapple.net>:
>> 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.
> 
> There are no broken deps and there is no crap that should be masked.
> 

	When building bugzilla-3.4.1-r1 which requires ~x86 I have to unmask a 
number of perl modules. Two of those modules, listed above, attempt to 
pull in perl-5.10.1 which isn't in portage. Hardmasking packages that 
require dependencies that don't exist makes sense. If you'd like to 
explain otherwise a little more data other than "cause I said so" is 
required.

kashani

kashani@www01 /usr/portage/dev-lang/perl $ cat 
/usr/portage/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild
# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: 
/var/cvsroot/gentoo-x86/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild,v 
1.2 2009/08/25 10:56:52 tove Exp $

DESCRIPTION="Virtual for Test-Harness"
HOMEPAGE="http://www.gentoo.org/proj/en/perl/"
SRC_URI=""

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 
~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd"
IUSE=""

DEPEND=""
RDEPEND="|| ( ~dev-lang/perl-5.10.1 ~perl-core/Test-Harness-${PV} )"

kashani@www01 /usr/portage/dev-lang/perl $ ls
ChangeLog  Manifest  files  metadata.xml  perl-5.8.8-r5.ebuild 
perl-5.8.8-r6.ebuild

[gentoo-user] Re: trying to track down broken dependency

[Torsten Veller]

* kashani <kashani-list@badapple.net>:
> 	When building bugzilla-3.4.1-r1 which requires ~x86 I have to
> unmask a number of perl modules. Two of those modules, listed above,
> attempt to pull in perl-5.10.1 which isn't in portage. Hardmasking
> packages that require dependencies that don't exist makes sense. If
> you'd like to explain otherwise a little more data other than "cause
> I said so" is required.

Let's have a look at the ebuild:

> kashani@www01 /usr/portage/dev-lang/perl $ cat
> /usr/portage/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild
> # Copyright 1999-2009 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
> # $Header: /var/cvsroot/gentoo-x86/virtual/perl-Test-Harness/perl-Test-Harness-3.17.ebuild,v
> 1.2 2009/08/25 10:56:52 tove Exp $
> 
> DESCRIPTION="Virtual for Test-Harness"
> HOMEPAGE="http://www.gentoo.org/proj/en/perl/"
> SRC_URI=""
> 
> LICENSE="GPL-2"
> SLOT="0"
> KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64
> ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd"
> IUSE=""
> 
> DEPEND=""
> RDEPEND="|| ( ~dev-lang/perl-5.10.1 ~perl-core/Test-Harness-${PV} )"

The ebuild depends on dev-lang/perl-5.10.1 or perl-core/Test-Harness-3.17.
The second one is in the tree so there is no need for hardmasking.

So if you add virtual/perl-Test-Harness to package.keywords you should
also add perl-core/Test-Harness.

If you wonder why portage doesn't report both possibilities, visit the
bugs in my other mail in this thread.

Thanks