Re: WARNING! (was: Re: New Perl Packages Released)
On Sun, Feb 18, 2001 at 01:09:22PM +0000, Julian Gilbey wrote:
>On Fri, Feb 16, 2001 at 09:15:18AM -0500, Daniel Jacobowitz wrote:
>> On Sat, Feb 17, 2001 at 01:12:08AM +1100, Brendan O'Dea wrote:
>> > >Package perl-base has broken dep on perl-5.004-base
>> > > Considering perl-5.004-base 0 as a solution to perl-base 5133
>> > >Fixing perl-base via remove of perl-5.004-base
>> > >Package perl has broken dep on perl-5.004
>> > > Considering perl-5.004 1 as a solution to perl 53
>> >
>> > would suggest that it's either not i386, or your Packages file(s) are
>> > broken. perl-base doesn't depend on perl-5.004-base. Quite the
>> > opposite in fact, it conflicts.
>>
>> That's a conflict in apt-speak. Note that it resolved the "broken dep"
>> by removing perl-5.004-base. The perl-5.004 bit confuses me though.
>
>The problem is still present. I could fix it manually, but I'd prefer
>to see if we can find the problem. Is there any way I can get more
>useful information out of apt about what it thinks it's doing? Is
>there any more information I can provide to anyone to help elucidate
>this mystery?
I think I know what the problem is, but I need to talk to Jason about
it.
I just made the packages conflict/replace/provide libpod-parser-perl
(#86459), and found to my dismay that apt-get chose to resolve the
conflict not by removing libpod-parser-perl, but rather perl and
anything which depended on it.
I believe the same problem is occuring with perl-5.004-base, which
perl-base conflicts with.
This doesn't occur with perl-5.005* or perl-5.6* because they're
versioned conflicts, and a newer (dummy) version is available. I could
perhaps create yet *more* dummy packages for perl-5.004*, but I would
prefer to avoid that.
Regards,
--
Brendan O'Dea bod@compusol.com.au
Compusol Pty. Limited (NSW, Australia) +61 2 9810 3633
Reply to: