Re: Status of Testing
On Mon, 24 Mar 2003, Travis Crump wrote:
> Bill Moseley wrote:
> > Can someone fill me in on the status of Testing -- I have not updated my
> > Testing/Unstable machine for a while (IIRC the glibc issue??).
> >
>
> The glibc issue is resolved, if you upgrade now than you will probably
> upgrade on the order of 100-200 packages depending on how many were
> already the unstable version and how many you have installed. It is
> doubtful that that will fix the mozilla issue though...
Well, for my testing/unstable machine:
bumby:/home/moseley/swish-e# apt-get -s dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Done
The following packages will be REMOVED:
audacity galeon galeon-common libsdl-mixer1.2 libvorbis0 timidity timidity-patches tuxracer
The following NEW packages will be installed:
bc gcc-3.2-base gkrellm libart-2.0-2 libaudio2 libdvdread3 libgcc1 libnetpbm9 libpaper-utils
libpaper1 libqt3c102-mt libstdc++5 libvorbis0a netpbm xlibmesa3-glu
The following packages have been kept back
kmail ogle-mmx sylpheed-claws
176 packages upgraded, 15 newly installed, 8 to remove and 3 not
upgraded.
I have always thought the "kept back" packages were because they were from
unstable and I'm running testing. But, if I comment my line from
apt.conf
// APT::Default-Release "testing"
and run dist-upgrade I sill have packages that are held back, but I also
still see that galeon will be removed.
What's conflicting with galeon to force it to be removed?
bumby:/etc/apt# apt-get -s dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Done
The following packages will be REMOVED:
audacity galeon galeon-common libdigest-md5-perl liblcms libmagick5 libstorable-perl
libtime-hires-perl libvorbis0 timidity timidity-patches
The following NEW packages will be installed:
bc bonobo-activation cpp-3.2 dictionaries-common foomatic-db g++-3.2 gawk gcc-3.2 gcc-3.2-base
gconf2 gkrellm gkrellm-common gnome-desktop-data libacl1 libart-2.0-2 libarts1 libasn1-6-heimdal
libattr1 libaudio2 libbonobo-activation4 libbonobo2-0 libbonobo2-common libcomerr1-kerberos4kth
libcompress-zlib-perl libdb4.0 libdb4.1 libdns8 libdvdread3 libgcc1 libgconf2-4 libgcrypt1
libgd-gd1-perl libgd1-xpm libglade2-0 libgnome2-common libgnomecanvas2-0 libgnomecanvas2-common
libgnomeui-common libgnutls5 libidn9 libkrb-1-kerberos4kth libkrb5-17-heimdal libkrb53 liblcms1
liblinc1 liblzo1 libmagick5.5.5 libmetacity0 libnetpbm9 libopencdk4 liborbit2 libpaper-utils
libpaper1 libpcap0.7 libperl5.8 libpq3 libqt3c102-mt libroken16-kerberos4kth
libstartup-notification0 libstdc++5 libstdc++5-dev libtasn1-0 libvorbis0a libwmf0.2-7 netpbm
python2.2 python2.2-optik xemacs21-mule xemacs21-mulesupport xlibmesa-gl-dev xlibmesa-glu-dev
xlibmesa3-gl xlibmesa3-glu xprt-common
The following packages have been kept back
abiword-common gnome-control-center kmail sylpheed-claws
323 packages upgraded, 74 newly installed, 11 to remove and 4 not
upgraded.
So it doesn't really look like upgrading to all unstable will help with my
package conflicts like I imagined. It will solve my segfault with
galeon... because it will be removed! ;)
--
Bill Moseley moseley@hank.org
Reply to: