Pardon me if I should know this but: I'm a bit puzzled. I recently did
a dist-upgrade on my notebook machine (previously running woody with
the backported KDE3.1) in order to get openoffice 1.1. Everything went
smoothly. I copied the sources.list from my office machine which for
some months has been running testing together with the woody backport
of KDE3.1 (this prevents upgrading a few packages - centring IIRC
around libvorbis0/libvorbis0a, which stops me installing sox - but is
otherwise very smooth), did an update then a dist-upgrade and all was
hunky-dory. 

I told my wife I'd upgrade her machine (also running woody with the
backported KDE3.1), because she wants OO1.1 too, so I once more copied
the sources.list from my desktop.

However: when I did the apt-get upgrade although it hit the KDE3.1
backport site it Ign[ored] the package list.

When I tried to do a dist-upgrade it threatened to remove some 82
packages including KDE3.1  and all the KDE applications.

Can someone explain why it does this? I assume that, because of the
ingored package list, the KDE stuff wasn't in the cache and so apt
thought (reasonably) that it should be remoced. But why ignore in the
first place? I couldn't easily find an option to any apt-command which
would tell me this.

If it's any help I eventually did a plain upgrade, which upgraded a
fair few packages to the testing version, the apt-get install
openoffice.org, which worked just fine.

However I still can't do a dist-upgrade without removing KDE3.1, so
currently I'm typing this on my wife's machine, running a mixture of
woody and testing. Not quite what I'd intended.

Any help gratefully received.
-- 
|Deryk Barker, Computer Science Dept. | Music does not have to be understood|
|Camosun College, Victoria, BC, Canada| It has to be listened to.           |
|email: [EMAIL PROTECTED]         |                                     |
|phone: +1 250 370 4452               |         Hermann Scherchen.          |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to