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

Re: The "c102" libraries want to kill KDE. How do I protect them?



On Tue, Jan 14, 2003 at 09:15:11PM -0500, Phil Edwards wrote:
> 
> In order to get a bug fixed, I'm doing an upgrade.  Dependencies on
> dependencies on dependencies have started to pull in a bunch of the *c102
> transition libraries...

Use aptitude or apt or whatever to just install the 'fixed' packages
then.  Mass upgrades in the middle of a transition are always going to
be troublesome.  Or you could sit back and wait for KDE3 to hit sid, in
which case all these problems will become serious bugs that will
(hopefully) get fixed more quickly.  Sit back and enjoy the ride, this
is sid :)

>     /usr/bin/apt-get -y -d dselect-upgrade
>     Reading Package Lists... Done
>     Building Dependency Tree... Done
>     The following packages will be REMOVED:
>       gnome-applets gnome-control-center gnome-games gnome-media gnome-panel
>       gnome-panel-data gnome-session gnome-terminal gnome-utils kchart
>       kde-theme-qnix kdeartwork-style kdebase kdebase-audiolibs kdebase-libs
>       kdelibs3 kdelibs3-bin kdepasswd kdepim-libs kdevelop kdevelop-data
>       kdf kdm kedit kfind kfloppy kfocus kformula kfract kgeo kghostview
>       khexedit kiconedit kivio kjezz kjots kjumpingcube kleandisk klines klpq
>       kmago kmahjongg kmail kmines kmix kmoon knetload knode knotes kodo
>       koffice koffice-libs konq-plugins konqueror konquest konsole kontour
>       konverse korganizer korn koshell kpackage kpaint kpat kpm kpresenter
>       kprof kreatecd krecord kreversi kruler ksame kscd kscreensaver
>       kshisen ksirc ksmiletris ksnake ksnapshot ksokoban kspaceduel kspread
>       kstars ksysv ktalkd kteatime ktexmaker2 ktimer ktuberling ktux kugar
>       kuser kview kvirc kweather kwin4 kword kworldclock libbonoboui2-0
>       libbonoboui2-common libfam0 libgnome-desktop-0 libgnome2-0
>       libgnomeui-0 libgnomevfs2-0 libgnomevfs2-common libgtk-common
>       libkdegames libkdenetwork1 libkmid libkonq3 libpanel-applet2-0
>       libpango-common libstlport4.5 rep-gtk-gnome yelp
>     The following NEW packages will be installed:
>       fontconfig libast2 libfam0c102 libmagick5.5.3 libssl0.9.7
>       libstartup-notification0 libstlport4.5c102
>     The following packages will be upgraded
>       [ many ]
>     182 packages upgraded, 7 newly installed, 116 to remove and 1  not upgraded.
> 
> How do I tell dselect (or apt-get, if that's what I need to use) to leave k*
> the hell alone?  It bitches at me if I try to put them on hold manually.

Don't upgrade?  Or use aptitude, since it seems to listen more carefully
to me when I say 'don't upgrade this package'.

> Phil
> (Yes, I would love to downgrade to testing, but dselect doesn't know what
> to do when required packages don't exist in "more-stabler" distros.)

Use aptitude or apt?  I bet there's a way to make dselect do it, but
I've no idea how.

-rob

Attachment: pgp47FiytvPtd.pgp
Description: PGP signature


Reply to: