Dapper: maintaining sources.list

[Brian Fahrlander]

Thilo Six wrote:
> Brian Fahrlander wrote the following on 28.07.2007 18:34
>   
>>     The other day I was blessed: my home server (fahrlander.net) was 
>> given a new version of Logwatch that is SPECTACULAR at dealing with the 
>> mail/spam details.  It's a real nice  upgrade to logwatch, version 7.3 
>> with "Feisty" in it's name- I'm pretty sure it was a backport.
>>
>>     So I go to my other clients running Dapper and expect it to be 
>> there: nope.
>>
>>     I forced an update and an upgrade: nope.
>>     
>
> Start to investigate what´s going on with:
>
> $ apt-cache policy logwatch
>
> That will tell you which version is available, and from where.
>
>   
>>     Then I went so far as to scp my sources.list from my server to the 
>> client, did the update/upgrade: nope.
>>
>>     Tell me how this is possible?  Both Dapper servers are using the 
>> same repo list...
>>     
>
>
> bye
>   

    Yikes!  That's an eye-opener. (It's also something I've not yet 
grown used to, since I was previously a Redhat-guy).

    It looks like I was using Feisty-backports for a short time, (by 
accident) and now I'm not.  In that time, the new logwatch, and any 
required packages got installed.

    Call me crazy, but I just might try this accident again!

    Thanks so much for the help!