apt-rpm vs. apt4rpm

[Klaus-Peter Schrage]

Tim Wunder wrote:

>On Saturday 16 August 2003 10:55 am, someone claiming to be Klaus-Peter 
>Schrage wrote:
>  
>
>>Tim Wunder wrote:
>>    
>>
>>>On Saturday 16 August 2003 9:45 am, someone claiming to be Michael Hipp 
>>>      
>>>
>wrote:
><snip>
>  
>
>>>>Does apt preclude the continued use of RedHat's up2date tool?
>>>>        
>>>>
>>>No, but you'll need to execute up2date -p to update the package list on
>>>RHN. Also, if you do what I did and install kde-redhat.sf.net's KDE
>>>packages, they're named differently. So RHN will think KDE will need to
>>>be updated even when it doesn't. I have that problem with kde and gaim.
>>>The more current packages that I have installed are named differently
>>>than RHN's, so RHN will think they need to be updated.
>>>      
>>>
>>Sorry, but I can't confirm that. This week I installed kde v. 3.1.2 from
>>kde-redhat.sf.net, and I just did an "up2date" which only gave me a new
>>unzip package. No kde packages were marked as to be updated, although
>>Redhat have put up a new set recently due to a security issue.
>>Klaus
>>
>>    
>>
>
>Hmmm...
>Have you ever executed 'up2date -p'?
>
>  
>
Yes, I do from time to time, after having applied several fixes manually 
(via downloading the resp. rpms from one of RH's mirrors) or by way of apt.
As I understand it, up2date -p  synchronizes RHN's list  of  fixes that 
are pending on my box with the actual state of my rpm database.
According to "my" RHN, there is only one erratum pending: the kernel, 
which I never update via up2date.
Klaus