[Yum] Debug message worthy of Yoda reward

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mar 4, 2004, at 10:52, seth vidal wrote:

> On Thu, 2004-03-04 at 13:43, Karsten Jeppesen wrote:
>> BTW:
>>
>> Seth, where did you get the --conflicts from?
>
> I just knew it.

Show-off

>
>
>> I see it if I do a bland rpm, but the man page doesn't mention it.
>> I can see its purpose, but what does the output mean?
>> Ex: cipe < 1.4.5
>
> that means that package conflicts with cipe of versions less than 1.4.5
>> spamassassin < 2.44-4.8.x
>
>
> here's your culprit.
>
> where did you get this kernel?

I just made it :-)


It is a hack from RedHats srpm.  I just checked the spec file. I wonder 
why they have spamassassin listed:

%{expand: %%define kernel_conflicts  ppp <= 2.3.15, pcmcia-cs <= 
3.1.20, isdn4k-utils <= 3.0, mount < 2.10r-5, nfs-utils < 0.3.1, cipe < 
1.4.5, tux < 2.1.0, kudzu <= 0.92, e2fsprogs < 1.22, initscripts < 
6.41, dev < 3.2-7, iptables < 1.2.5-3, bcm5820 < 1.81, nvidia-rh72 <= 
1.0, oprofile < 0.4, SysVinit < 2.84-5, pam < 0.75-48, vixie-cron < 
3.0.1-69, privoxy < 3.0.0-8, spamassassin < 2.44-4.8.x,  cups < 
1.1.17-13}

Doesn't matter - I'll just make the newer 2.63. That should kill that 
then.
Is there a reason why yum doesn't tell what the conflict is? Output 
cluttering?

karsten


[Index of Archives]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux