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

Re: How to handle "unofficial package" upgrade



You probably won't have to do anything special.  What is the 'fairly 
common source' you speak of?

A month ago, I upgraded from potato (stable) to woody (testing, and 
soon to be stable).  In potato, my KDE 2.1 packages came from 
kde.tdyc.com.  The KDE packages are part of woody, so I only had one 
soure for all my woody packages.  (By 'source', I basically mean a line 
in /etc/apt/sources.list)

The upgrade had no problems whatsoever.  Though the sources changed, it 
didn't matter because the KDE source (kde.tdyc.com) was designed to 
work with the official debian distros.  So the upgrade worked as 
smoothly as if KDE was in potato. 

My experience above is slightly different from what you're asking 
about, since I went from KDE 2.1 in potato to KDE 2.1 in woody.  But it 
will be the same: apt will automagically replace older packages with 
newer ones, regardless of their sources.  

Best,
Aaron

On Thursday 06 September 2001 10:03, Greg Wiley wrote:
> Good day all-
>
> On a Debian Potato, I am using KDE 2.1 packages that
> are, obviously, not part of Potato but are from a fairly
> common source.
>
> Since KDE 2.2 is slated for inclusion in the upcoming
> Debian release, what is the best way to prepare for the
> upgrade?  I cannot assume that the new packages will
> be aware of the old and will upgrade them automatically
> ( will they?).  So, am I best off finding every trace of
> the non-Debian KDE and eradicating or will things just
> sort of work out if I leave it all alone?  Any suggestions?
>
> Thanks,
>
>   -=greg



Reply to: